[TESTING] - NAND OMGB (1.2.3)

[arrrghhh]

Originally Posted by muziling

with LK.BIN, now my NBH can be flash by USB.
same problem with arrrghhh, make a call, com.android.phone FC, and need to reboot, otherwise phone can't be use.

Did you change anything in order to flash via USB?

Can you still flash via SD?

Would be nice if both methods worked, so that way people can use whatever method they prefer .

Oh, the RIL needs some lovin. Thanks for the logs, they should help ACL out!

[muziling]

Originally Posted by arrrghhh

Did you change anything in order to flash via USB?

Can you still flash via SD?

Would be nice if both methods worked, so that way people can use whatever method they prefer .

Oh, the RIL needs some lovin. Thanks for the logs, they should help ACL out!

ACL send me file LK.bin, so I can create new NBH which can be flash via USB , my SD card can't be used to flash NBH, usb is the only way for me.

[arrrghhh]

Originally Posted by muziling

ACL send me file LK.bin, so I can create new NBH which can be flash via USB , my SD card can't be used to flash NBH, usb is the only way for me.

You need to make sure the SD is setup to flash....

But anyhoo, I was wondering if you made any changes. He sent me the lk.bin file as well, but I'm curious if you needed any modifications to produce an NBH that can flash via USB....

[[ACL]]

Originally Posted by muziling

ACL send me file LK.bin, so I can create new NBH which can be flash via USB , my SD card can't be used to flash NBH, usb is the only way for me.

ahh that sucks. can you send arg your nbh so he can test on his rhod? The goal is to have an nhb that works for both sdcard and usb.

I'm in a similar situation as you except i can only flash from SD (well not similar but opposite situation). lol

[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.

[arrrghhh]

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]]

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]

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]

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]]

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.