View Single Post
  #1273 (permalink)  
Old 02-17-2011, 05:42 AM
ndno's Avatar
ndno
VIP Member
Offline
 
Join Date: Jan 2010
Posts: 421
Reputation: 3570
ndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIPndno is still contributing even after becoming a VIP
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
Re: NAND Boot Testing - 01-07: Panel power on/off fixes

Quote:
Originally Posted by natemcnutty View Post
OK, so I highly recommend double checking the size of your NBH before you go flashing :P

I thought I'd go back and do a clean pull of tinboot since I've messed with so much crap. Well, something went wrong with the compile, but the NBH was output at like 1 MB or something instead of 3 MB. The flash never finished and the phone wouldn't boot.

Awesome part, keep a stock ROM on your sd card and flash that. it repaired it for me, but for some reason, I have not been able to get a tinboot to work since. Still looking at why that is.

Edit: OK, so I can boot into WinMo, but none of my tinboot NBH's work anymore. Is it possible I f'd up part of the NAND? Really wish I could Task 29 this stupid thing. LMiller or ACL, would either of you mind upping your most recent NBH for me to test?
Wow, looks like you have it bad. Sounds like you may have a bad NAND block in the area where the NBH resides. I have worked a little with the OMAP processor at my work; our board comes with a POP NAND/RAM combo and once it a while we get a board in which one of the first few blocks is bad; since our bootloader (u-boot) resides in first few blocks, we can't do anything but have to replace the NAND part. Hopefully, the NAND didn't get messed up for you, like MassStash stated, it may be a battery issue.

Last edited by ndno; 02-17-2011 at 05:46 AM.
Reply With Quote