Help - Search - Members - Calendar
Full Version: Uboot Fails To Install
OESF Forums > Distros, Development, and Model Specific Forums > Distro Support and Discussion > pdaXrom
conundrum
I've tried installing uboot several times now, and I can't figure out what's going wrong.

I bring up the normal japanese service menu (battery unlock, ok, lock, on), update from my 128 mb CF card. The japenese boot menu pops up, the screen fills with "Writing [hex address], then freezes on "Rebooting the system..."

I've tried waiting various amounts of time, and it never leaves the screen. I pull the power and battery, and the Z is bricked. I have to restore the NAND from a backup.

Any insight?
Chero
QUOTE(conundrum @ Nov 12 2006, 12:28 AM)
I've tried installing uboot several times now, and I can't figure out what's going wrong.

I bring up the normal japanese service menu (battery unlock, ok, lock, on), update from my 128 mb CF card.  The japenese boot menu pops up, the screen fills with "Writing [hex address], then freezes on "Rebooting the system..."

I've tried waiting various amounts of time, and it never leaves the screen.  I pull the power and battery, and the Z is bricked.  I have to restore the NAND from a backup.

Any insight?
*


please read this thread : http://www.oesf.org/forums/index.php?showtopic=21960

Chero
conundrum
QUOTE(Chero @ Nov 12 2006, 10:32 AM)
QUOTE(conundrum @ Nov 12 2006, 12:28 AM)
I've tried installing uboot several times now, and I can't figure out what's going wrong.

I bring up the normal japanese service menu (battery unlock, ok, lock, on), update from my 128 mb CF card.  The japenese boot menu pops up, the screen fills with "Writing [hex address], then freezes on "Rebooting the system..."

I've tried waiting various amounts of time, and it never leaves the screen.  I pull the power and battery, and the Z is bricked.  I have to restore the NAND from a backup.

Any insight?
*


please read this thread : http://www.oesf.org/forums/index.php?showtopic=21960

Chero
*



I've already had to restore the NAND to the original a few times (two restores, three failed uboot installs now, I believe). My question is not how to undo the damage, but how to properly install uboot.

Is it really just a matter of trying enough times?
Chero
QUOTE(conundrum @ Nov 12 2006, 06:43 PM)
QUOTE(Chero @ Nov 12 2006, 10:32 AM)
QUOTE(conundrum @ Nov 12 2006, 12:28 AM)
I've tried installing uboot several times now, and I can't figure out what's going wrong.

I bring up the normal japanese service menu (battery unlock, ok, lock, on), update from my 128 mb CF card.  The japenese boot menu pops up, the screen fills with "Writing [hex address], then freezes on "Rebooting the system..."

I've tried waiting various amounts of time, and it never leaves the screen.  I pull the power and battery, and the Z is bricked.  I have to restore the NAND from a backup.

Any insight?
*


please read this thread : http://www.oesf.org/forums/index.php?showtopic=21960

Chero
*



I've already had to restore the NAND to the original a few times (two restores, three failed uboot installs now, I believe). My question is not how to undo the damage, but how to properly install uboot.

Is it really just a matter of trying enough times?
*



It seems to be a matter of having a really clean formatted card.
I don't think you have to do a nand restore in between trials (at least, I didn't)

Chero.
conundrum
I've tried several times and still no success. The uboot I'm trying to use is this one from the front page.

The contents of my CF card before trying are as follows:
CODE
u-boot.bin
updater.pro
updater.sh
autoboot.sh
emergenc.img


I have a C-860, I've tried installing uboot from both a 128 CF card and a 64mb SD card. In every case the installer stops at "Rebooting the system" and I have to unplug it and remove the battery to turn it off.

EDIT: Both cards have been completely empty and freshly formatted before placing the install files on them.
InSearchOf
QUOTE(conundrum @ Nov 20 2006, 08:47 PM)
I've tried several times and still no success.  The uboot I'm trying to use is this one from the front page.

The contents of my CF card before trying are as follows:
CODE
u-boot.bin
updater.pro
updater.sh
autoboot.sh
emergenc.img


I have a C-860, I've tried installing uboot from both a 128 CF card and a 64mb SD card.  In every case the installer stops at "Rebooting the system" and I have to unplug it and remove the battery to turn it off.

EDIT: Both cards have been completely empty and freshly formatted before placing the install files on them.
*



Have you tried a fresh download of the installer files?

Have you checked to verify that you don't have any bad blocks on your nand?

Late
conundrum
How can I check for bad blocks in NAND?
InSearchOf
it is in the D+M mode...

same place where you do your NAND restores... I believe it is in the extra menu... I'm using my Z right now to type this... so... someone can remember off hand... post away... or have fun finding it :-)

Late
conundrum
CODE
NAND Bad Count

Blk    Init    After    Total
-----------------------------
 1       2        0        2
 2       0        0        0
 3       0        0        0
 4       1        0        1
 5       0        0        0
 6       0        0        0
 7       0        0        0
 8       0        0        0
-----------------------------
Total Bad Block = 3

Partition Info
(1)BOOT: 0000000-0000000
(2)FSRO: 0000000-0000000
(3)FSRW: 0000000-0000000
-----------------------------
 1       0        0        0
 2       0        0        0
 3       0        0        0
-----------------------------
NG!
code=(622)
InSearchOf
there you go... thats your issue...

ok... I'm going to bed now... :-/

Late

PS. Search for tips on doing full scans that tag bad blocks... that may fix your issue....
grog
QUOTE(InSearchOf @ Nov 20 2006, 11:29 PM)
there you go... thats your issue...
PS. Search for tips on doing full scans that tag bad blocks... that may fix your issue....
*

I too have the same problem with 2 bad blocks on my boxer. My search came up with this and this & I found & ran the NAND Flash Erase in the EXTRA menu, but that made no difference for me. I also get the dreaded red NG spoken about in this post.

The only workable solution might be increasing the root size as stbrock says he does, but I don't think there's a way to do that here, is there?

HTH
InSearchOf
I think the NG is fine... I think that is because you dont have the Sharp Rom still loaded...

Now... the issue is the 2 (in grog's case) and the 4 (in conundrum's case) bad blocks...

I notices one thing is with it looks like the bad block for him are in the the INIT column which I *think* holds the boot loader data... (I'm not expert with the NAND blocks and how they are allocated)... so if some wants to correct me... feel free...

Late
InSearchOf
Ohhh and the bad blocks aren't going to go away... I dont think that full nand erase fixes them... it just flags them as bad... and tries its best to avoid them with any writes... but we all know how that works...

Computers are smart... but not that smart when you want it to be...

Late
grog
QUOTE(InSearchOf @ Nov 21 2006, 12:18 PM)
I notices one thing is with it looks like the bad block for him are in the the INIT column which I *think* holds the boot loader data... (I'm not expert with the NAND blocks and how they are allocated)... so if some wants to correct me... feel free...
*

Both of mine are in INIT as well.

QUOTE(InSearchOf @ Nov 21 2006, 12:20 PM)
Ohhh and the bad blocks aren't going to go away... I dont think that full nand erase fixes them... it just flags them as bad... and tries its best to avoid them with any writes... but we all know how that works...
*

figured, but shouldn't we be able to flash after they're marked? seems not. What bugs me is that I had r121 installed & working before I flashed back to beta2. Just my luck if the blocks went bad in the mean time. sad.gif
InSearchOf
So you were able to flash uboot and run RC121? prior to you going back to beta2...

But have you tried flashing to rc121 since?

If so... did you have any problems?

Late
conundrum
Well, I did a NAND erase, installed the original Japanese again and then tried to install uboot as described for the first time install. Still locks up on "rebooting the system," I think I'll just go back to Beta2, although I was really hoping I could stay up to date.

Anyone know of any work arounds, etc?
grog
QUOTE(InSearchOf @ Nov 21 2006, 01:20 PM)
So you were able to flash uboot and run RC121? prior to you going back to beta2...
Correct. It worked pretty good & was very fast, but not being able to restore a NAND backup scared me back to beta2.

QUOTE
But have you tried flashing to rc121 since?
If so... did you have any problems?
*

Yes I've tried, but I haven't been able to reflash it, encountering the same error that conundrum's been having. I can actually see the write errors as the script tries to install u-boot.
grog
QUOTE(conundrum @ Nov 21 2006, 03:42 PM)
Well, I did a NAND erase, installed the original Japanese again and then tried to install uboot as described for the first time install.  Still locks up on "rebooting the system,"
*

I had the same problem, but when I manually reset it it booted up just fine. Now of course I can't even get that far sad.gif.
conundrum
QUOTE(grog @ Nov 21 2006, 08:47 PM)
I had the same problem, but when I manually reset it it booted up just fine. Now of course I can't even get that far sad.gif.
*


Yeah, it wouldn't boot for me after manually shutting it down. The power indicator wouldn't even turn on when plugged in.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2015 Invision Power Services, Inc.