[TESTING] - NAND OMGB (1.2.3) - Page 6

**arrrghhh** · #51 (**permalink**) 10-07-2011, 10:11 AM

Quote:

Originally Posted by a460162314

the blue screen show : Devices not support .=>42
??

what this?
the nbh not support Rhod210?

i want test this thread.

The thread title says CDMA ONLY.

So maybe it only works for CDMA devices at this time... Just a thought, I know - crazy world. Reading thread titles.

You should be glad it didn't work, and brick your damned phone. Sheesh...

PedroDaGr8 · #52 (**permalink**) 10-07-2011, 12:54 PM

Ugh I can't get recovery to load properly. It keeps dumping me into fastboot after erroring out trying read recovery.

The log goes through the startup stuff like welcome to minipooploader and the the PLL Modes
it then says

nandid 0x5501bcec maker=0xec device=0xbc page_size=2048
a bunch of stuff about nandcfg and ptn (longer so I don't want to type them out unless I need to)

then it says
Boot reason: reset
calling apps_init()
Boot reason: reset
flash_read misc partition
flash read: misc 800 800
flash_read_image: failed (191 errors)
ERROR: Cannnot read recovery header
flash read: boot 0 800
flash_read_image: failed (2048 errors)
ERROR: Cannot read boot image header
ERROR: Could not do normal boot. Reverting to fastboot
htcrhodium_usb_enable
USB init ept @ 0x1c4000
USB ID 0042fa05
fastboot_init()
udc_start()

and then it stops there.

I have tried redownloading recovery.img several times as well as trying to reflash dozens of times.

**arrrghhh** · #53 (**permalink**) 10-07-2011, 01:04 PM

Quote:

Originally Posted by PedroDaGr8

Ugh I can't get recovery to load properly. It keeps dumping me into fastboot after erroring out trying read recovery.

The log goes through the startup stuff like welcome to minipooploader and the the PLL Modes
it then says

nandid 0x5501bcec maker=0xec device=0xbc page_size=2048
a bunch of stuff about nandcfg and ptn (longer so I don't want to type them out unless I need to)

then it says
Boot reason: reset
calling apps_init()
Boot reason: reset
flash_read misc partition
flash read: misc 800 800
flash_read_image: failed (191 errors)
ERROR: Cannnot read recovery header
flash read: boot 0 800
flash_read_image: failed (2048 errors)
ERROR: Cannot read boot image header
ERROR: Could not do normal boot. Reverting to fastboot
htcrhodium_usb_enable
USB init ept @ 0x1c4000
USB ID 0042fa05
fastboot_init()
udc_start()

and then it stops there.

I have tried redownloading recovery.img several times as well as trying to reflash dozens of times.

Pull the battery, boot again.

NAND is finnicky at best for me. I usually have to reboot a few times to get fastboot to detect the device, then I have to reboot a few times to get recovery to pickup so I can boot into CWM.... then CWM works great, but I usually have to reboot a few more times before it'll boot into Android correctly... then I keep getting freezes while in the system.

So this really is a developer preview. If you're not going to develop on this platform, there's really no point in any end-users flashing it.

**[ACL]** · #54 (**permalink**) 10-07-2011, 02:08 PM

Quote:

Originally Posted by PedroDaGr8

Ugh I can't get recovery to load properly. It keeps dumping me into fastboot after erroring out trying read recovery.

The log goes through the startup stuff like welcome to minipooploader and the the PLL Modes
it then says

nandid 0x5501bcec maker=0xec device=0xbc page_size=2048
a bunch of stuff about nandcfg and ptn (longer so I don't want to type them out unless I need to)

then it says
Boot reason: reset
calling apps_init()
Boot reason: reset
flash_read misc partition
flash read: misc 800 800
flash_read_image: failed (191 errors)
ERROR: Cannnot read recovery header
flash read: boot 0 800
flash_read_image: failed (2048 errors)
ERROR: Cannot read boot image header
ERROR: Could not do normal boot. Reverting to fastboot
htcrhodium_usb_enable
USB init ept @ 0x1c4000
USB ID 0042fa05
fastboot_init()
udc_start()

and then it stops there.

I have tried redownloading recovery.img several times as well as trying to reflash dozens of times.

save your energy. All you need to see is that it couldnt find a recovery header on the partition.
How are you flashing the recovery? The flashing never fails for me so you must be messing up the fastboot flash somehow. Also when you flash, does it actually tell you it flashed successfully?

Also keep an eye on the buttons you press. The message will tell you when it recognizes your button press (either power button or end key).

PedroDaGr8 · #55 (**permalink**) 10-07-2011, 03:52 PM

Quote:

Originally Posted by [ACL]

save your energy. All you need to see is that it couldnt find a recovery header on the partition.
How are you flashing the recovery? The flashing never fails for me so you must be messing up the fastboot flash somehow. Also when you flash, does it actually tell you it flashed successfully?

Also keep an eye on the buttons you press. The message will tell you when it recognizes your button press (either power button or end key).

Yeah it does say it flashed successfully. Here is the cmd prompt log and it says success on the phones screen.

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4176 KB)...
OKAY [ 1.109s]
writing 'recovery'...
OKAY [ 1.234s]
finished. total time: 2.359s

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4176 KB)...
OKAY [ 1.125s]
writing 'recovery'...
OKAY [ 1.969s]
finished. total time: 3.094s

C:\android-sdk-windows\tools>fastboot reboot
rebooting...

finished. total time: 0.641s

I'll likely play with this some this weekend just for fun. If it doesn't work at that point. I'll just chock it up as unsurmountable user error.

muziling · #56 (**permalink**) 10-07-2011, 07:43 PM

Quote:

Originally Posted by PedroDaGr8

Yeah it does say it flashed successfully. Here is the cmd prompt log and it says success on the phones screen.

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4176 KB)...
OKAY [ 1.109s]
writing 'recovery'...
OKAY [ 1.234s]
finished. total time: 2.359s

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4176 KB)...
OKAY [ 1.125s]
writing 'recovery'...
OKAY [ 1.969s]
finished. total time: 3.094s

C:\android-sdk-windows\tools>fastboot reboot
rebooting...

finished. total time: 0.641s

I'll likely play with this some this weekend just for fun. If it doesn't work at that point. I'll just chock it up as unsurmountable user error.

flash recovery again, I encount this problem once.

**[ACL]** · #57 (**permalink**) 10-07-2011, 09:44 PM

Quote:

Originally Posted by muziling

flash recovery again, I encount this problem once.

I've been in nand so long I can't replicate. However nate and lmiller always recommended task 29 . Not sure if that helps. The only real way to find out what whent wrong is to debug print every byte written. But that's too much work so if doing it again helps then let's go with that solution for now.

Looks like ill have boost tnight so ill get a new ril out. I need someone to test and see what I'm missing in BT since its currently crashing after phonecalls causing a ril restart.

muziling · #58 (**permalink**) 10-07-2011, 10:13 PM

Quote:

Originally Posted by [ACL]

I've been in nand so long I can't replicate. However nate and lmiller always recommended task 29 . Not sure if that helps. The only real way to find out what whent wrong is to debug print every byte written. But that's too much work so if doing it again helps then let's go with that solution for now.

Last time happend is I do an task29, flash 5/17 version NBH, flash recovery, boot into recovery and flash system, can't boot into android , flash WM, do an task29(I forgot if I did this), then flash newest NBH, flash recovery, occur, flash recovery again, normal.

I don't care this problem, only happened once,

**[ACL]** · #59 (**permalink**) 10-08-2011, 12:40 PM

so got cdma data up. Boost mobile definitely saved the day.

I also made some commits so we i'll be releasing a full release again. Hopefully this one does not crash because of bt.

List of changes:

We dont want to run bluetooth inside phone process.
prepare for kb backlight values and adjust button brightness. Thanks to detule for pointing this out.
experiment with full eri.xml. Unfortunately this is sprint only. Thanks to arrggg for poiting this out.
cdma data is now working.
updated apns-conf.xml from cyanogenmod

It should be up later today when the build finishes.

**kozmo** · #60 (**permalink**) 10-08-2011, 04:58 PM

Awesome news!!! Congrats on the fixes. Can't wait to try it out.