[TESTING] - NAND OMGB (1.2.3)

[[ACL]]

Originally Posted by argenisaz

Hi! Thanks a lot for your great work. I installed the new LK and, although it does recognize my phone as a RHOD500, It doesn't recognize the variant. So, my keyboard layout is still off from the start.

I do have a problem, I run the cat command and it says the directory doesn't exist. I checked under the htc_hw directory and I don't see cid. Am I missing something?

ahh sorry, you need to the the htc_hw inside the recovery since it contains a newer kernel than is on android. So boot into recovery, and adb into the phone to get the CID. Once i have that, then i can add it to the next OMGB..

[argenisaz]

Originally Posted by [ACL]

ahh sorry, you need to the the htc_hw inside the recovery since it contains a newer kernel than is on android. So boot into recovery, and adb into the phone to get the CID. Once i have that, then i can add it to the next OMGB..

Got It! Thanks!

CID: UTSI_001

[[ACL]]

Originally Posted by argenisaz

Got It! Thanks!

CID: UTSI_001

nice, so the logic for kb detection will change like this

Nice so if UTSI_001 and rhod500, then use rhod400 KB. Should be ready next release. Now i just need those rhod100 folk

[milda25]

Originally Posted by [ACL]

Partial Update (2-21-2012)

This recovery also includes a piece of code that will help me identify some of the sub variants. So if you have a tellus or one of the rhod100's who has the broken keyboard, you need to do the following

adb shell
#cat /sys/class/htc_hw/cid
CWS_001

Note the output above is from the test rhod300 i have. You should have a different value. Goal here is for the rhod500 tellus users to see what their CID is and if its not the default verizon, then use a diff keyboard. Same logic applies to rhod100 folk

Hi ACL, my Rhod100 giving me this value: HTC__032 (two underscores).
I'm not sure, but guy from previous post is from NL and KB layout rhod100_nl exists. If his variant HTC__E11 is for NL country, let setup rhod100_nl for this variant, I think. Jelmer, correct?
For my variant HTC__032 let setup rhod100_uk (if we can say, that HTC__032 is for Czech market, I don't know, but rhod100_cz doesn't exist )
One note - my keyboard is working correct now, with rhod100_uk layout.

[muziling]

Does this NBH safe? Just use RIFFBOX to repaired my phone from RHOD100 to RHOD400.

[[ACL]]

Originally Posted by muziling

Does this NBH safe? Just use RIFFBOX to repaired my phone from RHOD100 to RHOD400.

yea, safe as it can get from a guy reverse engineering proprietary code that was never publicly documented.

The big fix I did was to make sure what happened to you wouldn't happen again. I'm checking nand as well as memory now. So unless something goes out of its way to overwrite your nand with a 1 instead of 4, should not happen.

This is the actual commit that shows the checking.
https://gitorious.org/~acl/lk-msm720...5054a742601904

[arrrghhh]

Originally Posted by muziling

Does this NBH safe? Just use RIFFBOX to repaired my phone from RHOD100 to RHOD400.

Interesting... didn't know they had one for the TP2.

[muziling]

Originally Posted by arrrghhh

Interesting... didn't know they had one for the TP2.

I got my TP2 back ,three color screen show "RIFFBOX RESURRECTED" instead of 1.00.OliNex

[arrrghhh]

Originally Posted by muziling

I got my TP2 back ,three color screen show "RIFFBOX RESURRECTED" instead of 1.00.OliNex

Oh, you sent it in? I see.

[muziling]

My god, flash new NBH,... my phone turn to RHOD100 again...
Does git code is the neweast?

After flash NBH, i did this

Fastboot erase recovery
Fastboot erase boot
Fastboot erase misc
Fastboot erase system
::Fastboot erase data
Fastboot erase cache
::Fastboot flash recovery recovery.img
Fastboot erase userdata
Fastboot erase TPCAL
Fastboot erase WIFI
::Fastboot reboot
Fastboot flash recovery cwm_recovery.img
fastboot boot cwm_recovery.img
pause