My 'dumpall.zip' for dumping all partitions of Nokia 8110

[speeduploop]

It's quite nice to have dumps of your flash -- in case you kill something you shouldn't...

(this should have been my first zip... but I couldn't wait back then)

If you dump before rooting/bootstrapping then you have a chance to unroot cleanly ;)

As always (with script-zips) first mount /system.

The zip will then dump a bunch of images to /sdcard/dumps (you need about 4GB!)

--> this will take some time - be patient!

[Menno Wormsbecher]

Hi

thanks for this info

can you please tell me how to "restore " the phone ?

how to make it back to its original state.

i successfully made all dumps

thanks in advance

Op zondag 9 december 2018 03:22:19 UTC+1 schreef speeduploop:

[matvey]

Let me ask what is your firmware version? Will dumpall work on version 13?

[speeduploop]

No -- a 'normal' update to v13 will exchange signing keys --> no known way back.

[SWong]

Hi speeduploop, 

what is the step to restore if I have created the dump folder?

[PuriShnit]

@SWong, the dumpall.zip dumps ALL partitions (including userdata), which you shouldn't restore.

You can use the 4bash.zip & bash4zip.sh found in the "how to flashing my phone" thread, by writing in the bash4zip.sh the desired partitions to restore and their path.

[SWong]

Thanks PuriShnit, that's a bit tricky for me. Let me figure it out.

[Hossain Mohammed Shoaib]

Hi 

Speeduploop

is your dumpall.zip work on v13?

[speeduploop]

On stock-v13 --> no...

You would need a v13 with v12-recovery or a patched v13-recovery.

At the moment both things aren't possible if you are already on v13 -- only if you do it while updating...

[Ivan]

Thank you for the info

[speeduploop]

We REALLY need a way to flash the 8110 'externally'... then we could flash every device with custom-versions.

At the moment you can only keep the test-keys (install v13 without the recovery-part - re-root - update recovery - switch keys back to test-keys).

But we don't have a way back from stock-v13.

[PuriShnit]

Infinity CM2 box claim they will soon support 8110 read/write firmware, [from the past experience, I truly trust them :) ]

Although I do have their box, this still doesn't help the public with flashing (may still be helpful for easily publicizing stock & patched partitions). Unless someone can read their protocol and publicize a similar tool.

--
You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/1b07df04-4c2c-4f1d-b4bb-a7ae0fce6122%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[PuriShnit]

@speeduploop, I would like to modify your dumpall script to do the opposite:
restore any *.img from /sdcard/restore/ and dd to it's partition.

How can I tell the bash to programmatically use any "filename.img" and dd to his same name leaving out the ".img"

Thanks,

[speeduploop]

you could use 'basename'...

busybox basename /sdcard/restore/recovery.img .img

wil result in just 'recovery'.

(basename returns the filename without path -- if you give an extension as second parameter this extension will be stripped also)

[PuriShnit]

So, I do something like this:

for P in $(ls /sdcard/restore/)
...
if=/sdcard/restore/$P
of=/dev/block/bootdevice/by-name/$(basename $P .img)

Correct?

[speeduploop]

Yes... but double/tripple-check ;)

(some partitions shouldn't be touched unless really, really necessary -- this can get quite dangerous)

[PuriShnit]

My intention was to create a restore-partitions.zip, that will take any .img from that folder and restore it. Then it's up to the user to decide which partitions to place there, to have them restored.

However, if you suggest not to offer such a tool, as it might be used wrongly, and then damage the phone, I am thinking of simply stating a list of the possibly required partitions, and the bash should restore them if they're present.

[Ivan]

Hi, I had used this tool provided by Luxferre to restore my system to a clean v12, but inside it also has other partitions. I do not know if I made things worse if I had to install a future rom.

https://drive.google.com/file/d/1-_GC2g6CDAHz3DriOX6H2GpROr06KkBt/view

I think you know it. Take a look in.

[PuriShnit]

If I remember correctly, it has all partitions, but the script only restores the system.img (which is usually the only patched one).

So you haven't damaged anything :)

[speeduploop]

I thought of such a tool myself... but sometimes I tink that dangerous things shouldn't be too easy... :D

(if you have to create and sign a zip for your flash - then you're forced to think about what you are doing...)

So if you create such a zip - just make clear that it should be handled with care...

[Ivan]

ok, but if there are those files there will surely be a reason. Reading the scripts it seems like an overwriting has occurred. The Rom is for the east Europe, I live in the west, 

12.00.17.06 firmware version against my 12.00.17.10

[speeduploop]

The big differences between the regions/countries aren't on the system-partition... the differences are on the modem/wlan partitions. (frequencies, allowed channels...)

I don't know if there are any real different system-partitions. The version numbering is for the firmware as a whole.

(I think I also used a eastern-european system-image to clear before I updated to a pre-downloaded v13.00.17.01 --> western-european/german)

[Pavel Melnik]

New recovery from Luxferre with adbd makes update and recover easy. I don't need update.zip, wrtiting, signing...

С уважением, Павел.

--

You received this message because you are subscribed to the Google Groups "comp.mobile.nokia.8110" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bananahacker...@googlegroups.com.
To post to this group, send email to banana...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/bananahackers/24d3a1ee-3a3b-455e-b5cd-6e403bc52ba3%40googlegroups.com.

[Luxferre]

Oh, I forgot to announce it here, yep. Some alpha testing was announced on 4PDA but here it is: https://cloud.disroot.org/s/3ojAfcF6J2jQrRg/download

[Ivan]

hi, how i must use this?

[speeduploop]

It's like a custom-recovery... flash it to your recovery-partition.

Then you have adb-root in recovery -- meaning that you can do nearly everything over adb.

(flashing / dumping images -- repairing your system and more)

[Ivan]

uhm...interesting!
but can i using it to update my personal Rom then? or have i to have a clean v12?

[speeduploop]

for an update of your v12 to v13 you need a clean v12-image plus fota-zip or dumps of the v13-partitions (only those which changed between v12 and v13)

--> some of the changed partitions might be related to your region - so be carefull.

But yes: you can use adb in recovery to manually flash images to phone's partitions -- so as long as the recovery isn't changed you can repair nearly everything.

(even if you accidently wiped your phone - if the recovery is in place you could re-flash the system)

[Ivan]

ok, thank you :)

[speeduploop]

I could give you the images for the v12/v13 with '.01' at the end (western-europe -- dual-sim)

(my system-image could work on your's - not sure about the rest)


On Friday, January 18, 2019 at 8:07:09 PM UTC+1, Ivan wrote:

ok, thank you :)

[Ivan]

are you talking about the system.img of a v13? If I flash my phone with it I could upgrade directely?

[speeduploop]

Yes - if you can get the v13-images for your device/region (I think you only need 4-5 of the whole - the rest didn't change from v12) and flash them with a zip or manually with a custom-recovery everything should work.

(but this update had images for cellular/wlan - so you really need the right ones for your device/region)

[Subhajit Seth]

sir your name speeduploop..... ummm in JB its speeeuploop