Bricking A 3100

[whit]

Please tell me I haven't killed my new 3100.

My 860 suffered screen damage - still working, but....

So I got a 3100 from Pricejapan. Wow that came quickly.

When I went to install pdaXrom (which I'd been running on the 860) I got into the initial menu, and was following the instructions on http://www.pdaxrom.org/index.php?showid=42

I got to:

Enter a desired size - like 45 up to 120 depending on your needs. You have to apply "Fix sharp loader NAND 64MB limit ()" on the SL-C760, 860 models to choose more than 64. For SL-C700, 750 models 46 seems to be good.

I read that as "first choose the size, then apply the fix." (Partly that was because the fix is a later menu option, as well as being mentioned second in that instruction.) But after choosing the size as "120," the system told me I'd have to reflash the ROM - okay I'm expecting to do that, but then went into a reboot without giving me the option to apply the fix. I take it I should have applied the fix before changing to size? But the instructions don't specifically say it has to be before.

Anyway, where I am now is that restarting the 3100 just gets me to the initial SHARP screen. I can't get to the service menu at all to continue the process. Please tell me there's some way beyond this now! (I've searched a bit here - I'll be searching more.)

BTW, I did contribute a few days back.

[bam]

please dont tell me you resized then tried the fix.

On a good note, go get trisoft's rom backup for the 3100, do the DM poweron routine, restore it.

Next to install pdaXrom, fix the loader first then resize.

Thats all, not a major biggie.

[whit]

please dont tell me you resized then tried the fix.

Couldn't try the fix, as resizing was "fatal" before I got to that.

On a good note, go get trisoft's rom backup for the 3100, do the DM poweron routine, restore it.

So I'm looking at
http://www.trisoft.de/en_c3100howto.htm - it has two methods.

Am I to guess that the first method, "Backup for download," doesn't apply, since I can't get to menus at all? Or will having those backup files in place do something magical?

Since you mention DM, which applies to Trisoft's second method - Holding down D & M so far has got me nowhere. It either produces just a blank screen after reconnecting battery and power while holding down D and M, or it goes back to that initial SHARP splashscreen.

What am I missing?

Next to install pdaXrom, fix the loader first then resize.

Thats all, not a major biggie.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106137\"][{POST_SNAPBACK}][/a][/div]

I'm ever indebted to you for giving me hope.

[whit]

Can't for the life of me get to the service menu. I've sequenced though the battery or battery plus adaptor disconnect with D + M firmly pressed while reinstalling, with and without also pressing the On button, and it either stays blank (without the On button), or goes back to the SHARP splashscreen.

This is a fresh unit just shipped by Pricejapan - could Sharp have recently changed the code to get into this?

As a note on the thread, I've found the original Sharp backup at http://downloads.conics.net/pda/zaurus-sl-...iginal-backups/ - but of course that does nothing until I can get to the menu.

Later:

Found the answer here: https://www.oesf.org/forums/index.php?showtopic=12316 - D + M have to be depressed before reinserting the battery or reconnecting the power supply at all. I'd been putting the battery in (or that plus the power supply), and then pressing D + M before switching the battery switch - not early enough in the process. Sigh twice.

Later still:

Working! Now to adjust the feed....

[apink]

Just looking for a little clarification here:  

whit talks about applying the NAND 64MB limit fix.  But in the instructions it says that this fix is for 760 and 860 models.  whit has a C3100.  It would be my interpretation that you don't have to apply the fix on a C3100 (or C1000 in my caase) even if you do want to resize to something like 120MB.

??

Scratching my head.

[whit]

whit talks about applying the NAND 64MB limit fix.  But in the instructions it says that this fix is for 760 and 860 models.

I did see somewhere else where the C1000 and C3100 are added to the list - might have been on the menu itself. In any case not applying the fix was trouble; but after applying the fix (which went alright) I stuck with a smaller root after all (didn't have the patience to take even a small chance by that point).

What got me was not realizing it would insist on rebooting after resizing, before I could also apply the fix. I wonder if that's really necessary? It would make sense to have to reboot to leave the NAND menu. But rebooting after changing any single item? That streamlines the process if you only have one item to change, but for everyone else really lengthens it.

[pgas]

If all this resizing business is a problem, there is a simple solution:
Don't repartition the flash.

I don't repartition and have 0 problem,  you just need to take a bit of extra care not to install all the packages in /.

[Sna]

you can't install a fresh pdaxrom on a C3100 without resizing the rom
the initial partitionning is too little to fit the whole install

[Chero]

you can't install a fresh pdaxrom on a C3100 without resizing the rom
the initial partitionning is too little to fit the whole install
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106368\"][{POST_SNAPBACK}][/a][/div]

I didn't repartition.
The C3100 wasn't new when I got it, but it was running the stock rom.

df tells me :
/dev/mtdblock2 "/"  has 54272 1K-blocks.
/dev/mtdblock3 "/home" has 69632 1K-blocks.

Isn't this the standard partitioning ? I doubt it was repartitionned.

Chero.

[apink]

QUOTE:
df tells me :
/dev/mtdblock2 "/"  has 54272 1K-blocks.
/dev/mtdblock3 "/home" has 69632 1K-blocks.


Those are the numbers for my c1000 also.  But I thought I had repartitioned.  I did not do the fix because I did not think I had to.  Did the Z just ignore the repartition?

[Chero]

QUOTE:
df tells me :
/dev/mtdblock2 "/"  has 54272 1K-blocks.
/dev/mtdblock3 "/home" has 69632 1K-blocks.


Those are the numbers for my c1000 also.  But I thought I had repartitioned.  I did not do the fix because I did not think I had to.  Did the Z just ignore the repartition?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106383\"][{POST_SNAPBACK}][/a][/div]

It depends on how much you tried to assign to "/", if you tried to put it on the max of 121Mb, something went wrong. You should have about 121Mb in / and not about 50Mb like df tells you.

Chero.

[whit]

But I thought I had repartitioned.  I did not do the fix because I did not think I had to.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=106383\"][{POST_SNAPBACK}][/a][/div]

You didn't have to do the fix because you didn't make / large enough to require it. It might be that the stock rom on that other system was installed nonetheless over a previous repartitioning (that is, reverted to without repartitioning smaller again), or it might be that the original partitioning is now larger than it was on the x60's?