Quote:
Originally Posted by steven522
OK.
At work on a completely different PC.
New SD card -> Format to FAT (complete not quick).
Download 0.16 firmware to local drive and uncompress to a Lite16 folder. (Also tested archive with unzip util and got no errors)
Navigate to Lite16 folder in command prompt and use "xcopy *.* /s/v g:\" command to copy to SD card (G: is my SD card).
Insert SD into JBL (no reading screen as unit does not recognize internal mem or SD mem).
use paperclip to press and hold reset until screen completely fades (about 20 secs).
Press and hold power and right arrow until firmware warning shows up.
Screen says press OK when ready -> Press OK button.
The folder to book copy graphics appear and run for about 10 minutes (+/-).
I get a checkmark screen that says the unit has been successfully updated and to power off/on.
I power JBL off.
I power JBL on
Jetbook Lite screen comes up.
Book graphic comes up.
Main menu comes up.
System settings show software: v0.16 / patch v16.
Memory capacity shows Total 0.0KB / Free 0.0KB.
Internal file manager shows no files found.
Backing out of settings to main menu locks down the JBL.
Used paperclip to reset JBL with SD card loaded with books still inserted.
Power up unit and wait while book graphic displays.
Going into Books shows no files found.
Backing out of Books to main menu locks up again.
Paperclip -> reset -> Power -> Wait.
Go into any menu and back out results in locked up unit.
|
The one thing that strikes me from your description is where you varied
from the standard instructions. You are supposes to Reset after the
"check mark" screen, not just turn it off.
Also, using xcopy with switches is an unnecessary complication. You
can just use Ctrl-A to select the contents of your "Lite16" folder and
drag them to your "G:" drive.
It makes no sense that any change to the firmware could not be "undone"
by a later change to the firmware. As long as the update process functions,
you should be able to install a valid working firmware, that overwrites any
faulty firmware.
This loss of user data storage access, both internal and external, also makes
no sense.
I would try again using the 0.15d-b firmware again, on the idea
that you would be forcing some new code. If that fails, I would
RMA it and ask Ectaco for an explaination.
Sorry;
Ken