What about samsung e60

[dogsballs]

yes if someone has already done this then it should be possile to make it available to others as an update file. yes/no?

[Miles Prower]

Just figured out I was not using mksquashfs properly, and succeeded to create my firmware.*However this resulted in a bricked device.

Is there a recovery mode on the E60?

[sorg]

Originally Posted by Miles Prower

The reader sees this update fine, once its magic number changed, and agrees to install it (version is 1006.*However, on reboot, I'm still on the regular 1002 firmware with no changes whatsoever.*Any clue?

Same test and same problem here:
I have simply packed the supplied root.bin and kernel.bin, then changed the magic number and updated the devices.
Everithing went weel, but at the end of the process, i have still the same firmware (1002 instead of 1006).

I guess something did not worked during the update (even if ther is no error message) and i can find on the udb devie a file called: $RFS_LOG.LO$

This file is 128Ko and full of garbage (binary stuff).

[pierrev]

Having the capability to bypass the official library site is nice
so we can go anywhere on internet
yes but the E60 or any ebook reader has difficulty to render the web pages
i am lokking for sites of interest
so far I have found only one which is wiki mobile
i have tried various google sites but it is always flickering !!
any advice ?

[quedificil]

Originally Posted by Miles Prower

Just figured out I was not using mksquashfs properly, and succeeded to create my firmware.*However this resulted in a bricked device.

Is there a recovery mode on the E60?

You tell a posts before, that your E60 runs ok after firmware upgrade but with the same firmware 1002 ? How you bricked the ereader ??

My ereader is a E65 , and got no problems to replace the original firmware for the new one with the www.google.com,

Then in the image directory, type mksquashfs ./squashfs-root rootfs.bin

run the make-e60FR.sh and install the new firmware

[Miles Prower]

I modified a few lines in AppMain then created a modified firmware.*And messed up while editing the file (deleted a byte or something).*make-E60fr reported no mistakes though, and the E60 was able to see this new update and tried to apply it, resulting in a brick.

[Miles Prower]

BTW, does such an edit seem correct to you?

[quedificil]

You can't fill with hex 3D ! , you need to Fill with hex 32 (space blank) and leave the 00 at the same position 10F8F1F

[pierrev]

Originally Posted by Miles Prower

I modified a few lines in AppMain then created a modified firmware.*And messed up while editing the file (deleted a byte or something).*make-E60fr reported no mistakes though, and the E60 was able to see this new update and tried to apply it, resulting in a brick.

so what has happened then at the loading of you new firmware ?
where you able to recover ?

[Miles Prower]

I used 3D since I thought it was already a filler in this binary for some reason.

Blank space, hex code = 32. You mean… like this?



Seems kinda weird to me…

00 at 0x10F8F1F is mandatory then?*I guess I have to remove the one I placed at 10F8F08 (change this offset to a regular blank space?)



Did you mean 32 (decimal) ↔ 20 (hexa)?

Originally Posted by pierrev

so what has happened then at the loading of you new firmware ?
where you able to recover ?

Stuck on the initial Samsung loading screen, with a progress bar filled to 100% and nothing happening.*I asked for a refund of my E60*and bought a new one in the store.


And why does this board keep adding random * to my posts?

[quedificil]

OH, sorry !! 20, not 32, and replace the 00 after google.fr for another space (20 hex)

[Miles Prower]

Oh, just when I edited my post

Seems ok to you?

[quedificil]

Originally Posted by Miles Prower

00 at 0x10F8F1F is mandatory then?*I guess I have to remove the one I placed at 10F8F08 (change this offset to a regular blank space?)

Correct.

[Miles Prower]

Ok, so, tried it (flashed it) and the results are IN!

The E60*was using a 1000.1*firmware prior to the update operation.*It found a 1006.0 update - so I ran it, it rebooted fine (yay!) and now appears to be running with a 1002.0 firmware (wtf).

At least it's not bricked.*Good enough.

Accessing the Bookstore does not work at all.*After entering my Adobe ID, I only see a blank page - no default store but no Google either.*So, yup, something has changed. Well, I guess.

Weird thing is that I tried to modify what I think was the Bookstore icon too (/squashfs-root/usr/local/Trolltech/QtEmbedded-4.5.1-arm/Images/02_Home/home_icon_03.bmp), but it still shows the default icon and not the black & white bitmap I put in.

[quedificil]

Originally Posted by Miles Prower

Weird thing is that I tried to modify what I think was the Bookstore icon too (/squashfs-root/usr/local/Trolltech/QtEmbedded-4.5.1-arm/Images/02_Home/home_icon_03.bmp), but it still shows the default icon and not the black & white bitmap I put in.

home_icon_bookstore and home_icon_bookstore_sel