View Single Post
  #2465 (permalink)  
Old 04-26-2011, 07:52 AM
Lmiller1708's Avatar
Lmiller1708
Flashaholic!
Offline
Location: La Crosse, WI
 
Join Date: Aug 2008
Posts: 873
Reputation: 2160
Lmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIPLmiller1708 is a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 04-06: FRX06 on NAND (Testing FRX06 now!)

Quote:
Originally Posted by bobeer86 View Post
New NBH still doesn't let me access recovery, just like the previous one - it throws the same error, but this time with (4096 errors).
Attached zips of mtd0 and mtd1 pulled after fastboot boot recovery.img. adb still cant mount sdcard.
Ok We might be too close. But on your SDcard will not mount for now. Haret is having the same issues I guess.

Quote:
Originally Posted by bobeer86 View Post
Btw. If I manually flash recovery image to recovery partition I am able to access it from lk, which leads to a question: does current GSM or previous universal NBH include recovery at all or should I keep on flashing recovery.img manually via fastboot? Your original instructions didn't mention flashing recovery.img at all and I'm a bit confused here.
That is good. Means the recovery.img is being put in a safe RW memory location. The recovery.img is included on the NBH at a offset. The offset is what I'm trying to figure out for GSM.

Quote:
Originally Posted by bobeer86 View Post
Anyway, upon flashing recovery manually I can boot into it from phone and it seems like it's installing androidupdate.tgz. If I flash boot.img to boot via fastboot I end up with boot loop, but I tried just booting boot.img via fastboot without flashing it and it gets stuck at:
[21.628204] msm72k_udc: ept #2 out max:512 head:ffc0c100 bit:2
[21.696350] mdp irq already on 4 4
[21.714172] mdp_dma: busy


at this point I pulled mtd0 and mtd1 just in case all zips attached - _new_nbh is with new GSM NBH using fastboot boot recovery.img, _fastboot is with manually flashed recovery and fastboot boot boot.img pulled when android got stuck.

Hope it helps.
Not sure about the boot loop of getting stuck...

Anyway Here is another NBH with the recovery.img included. Remember to hold the top button once the blue screen turns on to boot into recovery, if it can.
If you can't boot into recovery use this recovery.img and just run:
Fastboot boot recovery.img

Then once again I will need a dump of the mtd0 and mtd1. This time mtd1 is recovery so it will be a bit larger. I should then know if it's getting inserted at the correct spot. But do not Flash anything from fastboot.

Thanks for your help on this! Glad we finally have a GSM user willing and able to help!
__________________
Reply With Quote
This post has been thanked 2 times.