NAND Testing - 05-25 Update: New LK, Recovery.img, Kernel Updates through Recovery - Page 81

mpannen · #**801** (**permalink**) 12-31-2010, 07:47 PM

that dll I attached is specifically for rhod400/rhod500 (maybe, I am trying to figure out the difference between 100/400/500 and all of those specific names)

OK I think I understand now, MightyROM is only for CDMA worldphones, and the rhod100 must be only a European GSM.

mpannen · #**802** (**permalink**) 12-31-2010, 07:59 PM

Can a rhod100 be called a touch pro 2? That dll .zip file came from OEM driver folder from MightyRom, and if I am not mistaken, his ROM will work on GSM phones as well. I guess I am not certain what phones are considered 'RHOD100'.

Nevermind I think I understand now. Will not work for RHOD100.

m4f1050 · #**803** (**permalink**) 12-31-2010, 08:28 PM

uhm... the TP2 is my daily phone, what build should I flash so I don't have to keep flashing between nand and wm rom?

MassStash · #**804** (**permalink**) 12-31-2010, 09:51 PM

Quote:

Originally Posted by m4f1050

uhm... the TP2 is my daily phone, what build should I flash so I don't have to keep flashing between nand and wm rom?

not if one exists... but if so, like 11/29??? maaaaybe.

anyhow, had a funny thought today, which i only imagine, has had to have been thought of already by someone IF possible. Is it that we haven't quite figured out full nand? or don't want to do it for test purposes. If its been/being done by you, the panel is stills fussy i take it? I just thought maybe if its full nand, the panel would react better... idk, just a thought/Question

is there wrong with throwin the nbh script at the end of the xip.sh? so the "onestop.sh" can be used?

**natemcnutty** · #**805** (**permalink**) 12-31-2010, 11:31 PM

Quote:

Originally Posted by m4f1050

Touching screen while boot animation does nothing, I tried it many times. Will try the other suggestions though..

Noticed something weird now.... The xdandroid animation at the beginning was flashing (turning on and off very fast, like 4 to 6 times a second)

Pressing both MENU and END got my screen on, went to MENU, SETTINGS, DISPLAY and AUTOMATIC BRIGHTNESS was OFF, turned it on and it stayed on. When I tried turning it off the screen turned off! :O
AUTO BRIGHTNESS is back on...that seemed to fix it...

EDIT: Let it sleep and when tried to turn screen back on it didn't want to, not even with MENU and END.... :/

EDIT 2: Is there a way to reboot android propperly? reboot -f is just a soft reset sort-of... I want it to go through the init and not to leave partition "dirty"...

For now I installed VNC server and DYN IP update utility to connect to phone and be able to see what's on the screen... LOL

I take it you are using the reference build? Do you have the 3D drivers from Tiad's thread or my full package build in the root of your sdcard? I get that flickering without 3D files, but it works nice and smooth with the 3D files there.

As for screen on/off, it is still under development, and I'm sure ACL and Wistilt are working on figuring that part out. We just have to be patient and wait for them to get it ironed out

For the reboot, I thought they added proper shutdown and reboot, but I think something else is causing the partition to be dirty.

Quote:

Originally Posted by mpannen

that dll I attached is specifically for rhod400/rhod500 (maybe, I am trying to figure out the difference between 100/400/500 and all of those specific names)

OK I think I understand now, MightyROM is only for CDMA worldphones, and the rhod100 must be only a European GSM.

rhod100 is a GSM European version of the Touch Pro 2. The rhod400 and rhod500 are US CDMA. You cannot mix/match the ROMs on those devices.

Quote:

Originally Posted by mpannen

Can a rhod100 be called a touch pro 2? That dll .zip file came from OEM driver folder from MightyRom, and if I am not mistaken, his ROM will work on GSM phones as well. I guess I am not certain what phones are considered 'RHOD100'.

Nevermind I think I understand now. Will not work for RHOD100.

MightyRom is CDMA only. Also, I would not recommend grabbing drivers from a cook's kitchen as you never know where they pulled them from. Always disassemble a stock ROM from the manufacturer for that specific phone.

Quote:

Originally Posted by m4f1050

uhm... the TP2 is my daily phone, what build should I flash so I don't have to keep flashing between nand and wm rom?

I would not recommend using any of the NAND builds for your daily phone. It is not ready for full time use, and I really don't feel that Haret is ready yet either. In any case, Haret will be much better for constant daily use than NAND will be.

Quote:

Originally Posted by MassStash

not if one exists... but if so, like 11/29??? maaaaybe.

anyhow, had a funny thought today, which i only imagine, has had to have been thought of already by someone IF possible. Is it that we haven't quite figured out full nand? or don't want to do it for test purposes. If its been/being done by you, the panel is stills fussy i take it? I just thought maybe if its full nand, the panel would react better... idk, just a thought/Question

is it just me that cant get tinboot to work now??

Being on full NAND will not help with the panel stuff. The biggest fear is writing to the wrong parts of the NAND and bricking a device. Maurice says he has it working and has created 4 partitions. I'm also looking into it now that I only have a few months left on my contract before I can get a new phone. I don't mind bricking it as much at this point. Once I get some details from him, I'll start messing around with YANG to move everything to NAND, but I definitely want to do my research rather than ending up with an expensive paperweight

MassStash · #**806** (**permalink**) 01-01-2011, 12:19 AM

icic. Perhaps the HD2 nand will shine light on touching the nand partitions better. so without panel worked out, full nand is as "useless" partial nand... Man, i'ma really try and learn/test what ever i can for the friggin panel. The whole daily use is so close it's rediculous! and i am really getting sick of winmo after skyfire cut the f'in servers for 1.5 as well. checked out some other app and winmo dev had been shut down. winmo has been dead for a long time, i think this is the nail in the coffin for me. However, i am torn now knowing i can't get sense/Htcfacebook to work on rhodadroid

And on the note, f' these phones, i'm close to end of contract too! lol lets twack this thing out til we can cop on the htc sabor or some sh*t

**natemcnutty** · #**807** (**permalink**) 01-01-2011, 06:31 AM

[ACL], I have some more fun for you. I'm still waiting to find out exactly what version of the rhod100 this guy is using, but he has 0x14 for his panel, and I've uploaded his haretconsole output and dmesg. It looks like the rhod100 may use a different NAND than our devices (at least that's what I'm taking this line to mean: msm_nand_read_oob 2500000 2000 0 failed -74, corrected 0)

Anyway, the panel init for the rhod100's with 0x14 is in the haretlog if you want to compare with other init sequences you have saved up

Happy New Year to everyone, and here's looking to a great 2011

**arrrghhh** · #**808** (**permalink**) 01-01-2011, 12:10 PM

Quote:

Originally Posted by MassStash

icic. Perhaps the HD2 nand will shine light on touching the nand partitions better. so without panel worked out, full nand is as "useless" partial nand...

Unfortunately HD2's NAND is called magldr - closed-source crap. They don't use tinboot, so their NAND helps us out zilch.

MassStash · #**809** (**permalink**) 01-01-2011, 02:21 PM

Quote:

Originally Posted by arrrghhh

Unfortunately HD2's NAND is called magldr - closed-source crap. They don't use tinboot, so their NAND helps us out zilch.

yea i saw that, well that's sh*tty eh?

can't wait for nand update! lol

**natemcnutty** · #**810** (**permalink**) 01-02-2011, 07:21 PM

Quote:

Originally Posted by natemcnutty

[ACL], I have some more fun for you. I'm still waiting to find out exactly what version of the rhod100 this guy is using, but he has 0x14 for his panel, and I've uploaded his haretconsole output and dmesg. It looks like the rhod100 may use a different NAND than our devices (at least that's what I'm taking this line to mean: msm_nand_read_oob 2500000 2000 0 failed -74, corrected 0)

Anyway, the panel init for the rhod100's with 0x14 is in the haretlog if you want to compare with other init sequences you have saved up

Happy New Year to everyone, and here's looking to a great 2011

We may want to hold off on having RHOD100 users flash this. There are a few of them who claim their bootloader no longer supports USB after flashing to the NAND builds. I'm really wondering if they have a different NAND module than everyone else, and maybe the memory addresses are different. Any ideas?