REPAIR ALL YOUR PARTITIONS USING 4BASH.ZIP by PURISHNIT

[ivan1...@gmail.com]

After months of struggles Speeduploop managed to convince me: I repaired my v12 using clean partitions from its MagentaCLOUD.

It took us a whole night, but in the end I was able to update to the latest firmware (16.00.17.00).

You can find the guide on the main page of the BACKUP section of the BANANAHACKERS website (which is why I removed Repairv12_signed.zip from the section):

https://sites.google.com/view/bananahackers/backup

Everything is based on the use of the 4bash.zip + bash4zip.sh tool from Purishnit, download the RESTORE-8110.7z archive from here , extract it and you'll found:

• 4bash.zip, which you will need to boot from recovery;
• bash4zip.sh, which I have already compiled for you on a v12 firmware;
• "new-dumps", that is an empty folder in which you will have to insert your clean dumps (or get them from here).

BASH4ZIP.SH is compiled in this way:

/tmp/busybox dd if=/sdcard/new-dumps/aboot.img of=/dev/block/bootdevice/by-name/aboot
/tmp/busybox dd if=/sdcard/new-dumps/abootbak.img of=/dev/block/bootdevice/by-name/abootbak
/tmp/busybox dd if=/sdcard/new-dumps/boot.img of=/dev/block/bootdevice/by-name/boot
/tmp/busybox dd if=/sdcard/new-dumps/fsg.img of=/dev/block/bootdevice/by-name/fsg
/tmp/busybox dd if=/sdcard/new-dumps/modem.img of=/dev/block/bootdevice/by-name/modem
/tmp/busybox dd if=/sdcard/new-dumps/rpm.img of=/dev/block/bootdevice/by-name/rpm
/tmp/busybox dd if=/sdcard/new-dumps/rpmbak.img of=/dev/block/bootdevice/by-name/rpmbak
/tmp/busybox dd if=/sdcard/new-dumps/sbl1.img of=/dev/block/bootdevice/by-name/sbl1
/tmp/busybox dd if=/sdcard/new-dumps/sbl1bak.img of=/dev/block/bootdevice/by-name/sbl1bak
/tmp/busybox dd if=/sdcard/new-dumps/splash.img of=/dev/block/bootdevice/by-name/splash
/tmp/busybox dd if=/sdcard/new-dumps/system.img of=/dev/block/bootdevice/by-name/system
/tmp/busybox dd if=/sdcard/new-dumps/tz.img of=/dev/block/bootdevice/by-name/tz
/tmp/busybox dd if=/sdcard/new-dumps/tzbak.img of=/dev/block/bootdevice/by-name/tzbak

WARNING! READ IN YOUR CACHE IFIS NEEDED THIS SOLUTION BEFOR PROCEEDING!

An error that often occurs when you don't have a "pure" 8110 is the OTA update that returns an error in the form of a log.

You can view the logs in the partition / cache, if you are root users you can copy the partition like this:

dd if=/dev/block/bootdevice/by-name/cache of=/sdcard/cache.img bs=2048

And quickly copy it to your PC. You can read it by renaming it as a .zip archive, and in the "recovery" folder you will find all the messages regarding the error. Most of the time the error concerns a faulty partition. Useless to replace it with the command to the system started, there could be a partition that restores it (for example aboot.img and abootbak.img).

Below I attach how to place them exactly on the SD card, along with the .7z file to be unpacked.

And now reboot the phone and start the update from SDcard.You canget dumps for TA-1059 and 1048 from here:https://sites.google.com/view/bananahackers/backup/dumps

[ivan1...@gmail.com]

NOTE: it is advisable to install only the partitions of your firmware version, a complete manual update has not been tested yet, so I cannot say exactly what you would go against.

Do it at your own risk!

[Tangy Tomm]

will give it a try

[Tangy Tomm]

Tried. Got v12 but still failed to get v16. Dont know whats going wrong

[ivan1...@gmail.com]

WARNING! READ IN YOUR CACHE IF IS NEEDED THIS SOLUTION BEFOR PROCEEDING!

An error that often occurs when you don't have a "pure" 8110 is the OTA update that returns an error in the form of a log.

You can view the logs in the partition / cache, if you are root users you can copy the partition like this:

dd if=/dev/block/bootdevice/by-name/cache of=/sdcard/cache.img bs=2048


And quickly copy it to your PC. You can read it by renaming it as a .zip archive, and in the "recovery" folder you will find all the messages regarding the error. Most of the time the error concerns a faulty partition. Useless to replace it with the command to the system started, there could be a partition that restores it (for example aboot.img and abootbak.img).

[speeduploop]

That's not really surprising... if you just used it like it was, then you flashed your v13 with clean v12 images... which really wasn't the best idea. No - you really shouldn't have done this ;)

--> a v13 needs to be re-flashed with clean v13 images --> this should have been obvious but was also stated in the how-to...

[Tangy Tomm]

If you can shed some light on that

[ivan1...@gmail.com]

As suggests speeduploop here:

share from a root shell the result of this:

more /cache/recovery/last_log

ENTER --> next line

SPACE --> next page

R --> show rext

Q --> quit

share the content here

[Tangy Tomm]

I tried but couldn’t fetch the logs.

[speeduploop]

Try again -- without logs noone can help you.

[Backwood]

Thanks Ivan, Speeduploop! After going from failure to failure I finally did it. 

Even I managed to get a clean Banana!

I was almost on my way to get a new Kaios phone.

Oh yeah, and Finland confirmed on v16 update, a bit late tought. Dated on 5.2-19

Speeduploop are you running on a boosted v16 with bootstrap and cpu tweaking?

[speeduploop]

Yes - v16, jailbroken, rooted, patched recovery, CPU-Tweaks, swapfile and swappiness adjusted, unistalled google-apps and some other, patched/repaired gallery...

[Ashwin Prakash]

Hi Guys,

I have a couple of doubts to clear.

Currently: 8110 4G India(Jio) running fine on GerdaOS with stock modem.img.

Would I be able to update to Pure V16, If I replace all my partitions with clean ones from the website and then hit update?

My phone is snappy as ever on GerdaOS but since I've been told that V16 is better, curiosity has gotten the best of me.

Cheers,

Ashwin.

[ProgrammAbel]

sorry, but this has not been tested and is highly dangerous. if i were you, i'd just wait it out.

[Ashwin Prakash]

Will wait for the next GerdaOS v16 update, because yesterday tried the V12+UK rom and VoLTE doesn't work, hence had to go back to current GerdaOS.

Since stock OS doesn't have option to manually turn on VoLTE I have no other go. Anyhow GerdaOS is better and has more features, especially slider control. :)

[Sylvain Pirnay]

Hi !

Is there any way to flash recovery test-key without adb ? I'm on v16 and my phone doesn't boot (I get kaios mobile logo then nokia logo then black screen) I can access to the original recovery but it doesn't help to flash any zip file. Thank you !

[speeduploop]

-- if adb was enabled already you could be lucky to get adb access on your mentioned 'black screen' - but that won't help without root.

-- if this happened without mods on system-partition a factory-reset from recovery might help.

Without knowing what you've done it's really hard to help...

But to just answer your question: No - without access to an adb-root shell it's nearly impossible to re-flash the recovery.

(that's the reason why we usually don't mod /system without flashing recovery-testkeys first...)

--> you need recovery-testkeys to flash /system

--> you need adb root to flash recovery-testkeys

(there is one of those rip-off tools for phones which claims to be able to flash a Nokia 8110 4G -- but never tested it. I don't support such scam biut you may google it.)

[Sylvain Pirnay]

Thank for your answer !

I've tried to modify the system app. I must have done something wrong and when I did reboot there was only the status bar that appair.Then I've tried to do a factory reset and I got the black screen after the nokia logo.

I've seen a post here about miracle box https://groups.google.com/forum/#!msg/bananahackers/TBBGHSPA8dg/XBUx5aVhCgAJ

Do you think I can flash the recovery-testkeys with it ? if so I don't really know how.. (I've tried a few thing with it but it didn't work)

[speeduploop]

On Tuesday, June 4, 2019 at 9:15:19 PM UTC+2, Sylvain Pirnay wrote:

Thank for your answer !

I've tried to modify the system app. I must have done something wrong and when I did reboot there was only the status bar that appair.Then I've tried to

do a factory reset and I got the black screen after the nokia logo.

Never do something like that without a 'plan-b' like a recovery with test-keys... you killed your system-app - meaning if you had adb-root (or another permanent root) you could probably repair it through adb. (the adb server is startet before b2g - so it runs even if the GUI doesn't start)

 

I've seen a post here about miracle box https://groups.google.com/forum/#!msg/bananahackers/TBBGHSPA8dg/XBUx5aVhCgAJ

Do you think I can flash the recovery-testkeys with it ? if so I don't really know how.. (I've tried a few thing with it but it didn't work) 

As I already mentioned: I won't support this crap.

--> if you pay them they might support you - if you use a cracked version then you might have oter problems (like a malware infected PC...)

[Sylvain Pirnay]

I see.. do you know if there is an uptade.zip that I could flash with the original recovery ?

[speeduploop]

On Tuesday, June 4, 2019 at 9:45:36 PM UTC+2, Sylvain Pirnay wrote:

I see.. do you know if there is an uptade.zip that I could flash with the original recovery ? 

No there is none.

-- they don't provide us with a factory/stock-installer

-- and we don't have the keys for the stock-ecovery

(that's the reason I patched all the stock-recoveries to use testkeys...)

I know that's bad news - but unless you want to try one of those rip-off tools you need to wait and hope that we find a way to directly flash the device.

(BTW: the only tool which advertises 8110-support seems to be InfinityBox QLM2 - v1.16 -- seems to be pay per use...)

[Sylvain Pirnay]

Ok thank you very much for your help ! you do a great job !

[I Understand I Exist]

hey guyz, i thought i better post this here instead of making a new thread, my question is, do i need something else other than the system.zip when i retrieve from gerda, i still don't get an update for the v16 os even after clean flashing v13, and can someone provide a clean v16 for ta-1059

[Ivan Alex HC]

you come from a v12, I remember well this....you need clean v12 dumps. Them are available on the bananahackers website:

https://sites.google.com/view/bananahackers/backup/dumps

[I Understand I Exist]

but isn't gerda based on v13 ???

[Ivan Alex HC]

yes, but it don't replaces the whole update. Yuo were started from a v12 with OmniSD extreme method and you have installed GerdaOS thinking it was a complete installation to v13. Wrong thinking. Your phone is still a v12 but patched v13 partitions. Checksum talks for the verification.

[I Understand I Exist]

ok im going to flash the system.bin and see where it takes me

[Ivan Alex HC]

I think you have to flash more partitions v12. Put all the dumps into the tool and clean your phone. The scripts will replacing all only the needed partitions.

[I Understand I Exist]

didnt work, system version shown is v13.00.17.01

[speeduploop]

You have to reflash all partitiions the Gerda-Installer changes... system, boot and some others...

(the install instructions of Gerda reminds to backup those files... so there should be a list)

[I Understand I Exist]

oh yea, i just did that and renamed all .bin to .img i think this will work

[I Understand I Exist]

now, system is v12 shown on the device, but still no update 

[speeduploop]

boot to recovery and 'wipe cache'... then re-try.

[I Understand I Exist]

okay now, update is available to v16.00.17.00, dowloading 

[Ashwin Prakash]

Are you using the Gerda Recovery or stock recovery?

[I Understand I Exist]

at this point im on stock recovery, update didnt work shows error 7

[I Understand I Exist]

this was in the log, 

error: 3305

e: error in /data/fota/downloaded/update.zip
(status 7)

installation aborted.

package install result:install failed
dir_name = /data/fota/mounted /system

[Ivan Alex HC]

https://groups.google.com/d/msg/bananahackers/NSqbMOa_mfs/xdTAgQgdBAAJ

[speeduploop]

That's not enough information...

-- usually there is mentioned which partition is still moddified.
(most probably you need to flash additional prtitions with stock versions)

Just look for something like 'partition contains unexpected content' or similar.

[I Understand I Exist]

okay, i have this
contents of partition "/dev/block/bootdevice/by-name/boot didn't match emmc:/dev/block/bootdevice/by-name/boot: "lots of numbers here"

e3305: emmc:/dev/block/bootdevice/by-name/boot: 1508 etc etc has unexpected contents 

[Ivan Alex HC]

OK, the "boot" partition....seems that you haven't done what I sayd to you: put ALL the clean partitions listed on the script into the "new-dumps" folder and start the 4bash.zip tool!!

[I Understand I Exist]

i already did that, im going it again with the boot partition 

[I Understand I Exist]

i flashed the boot file alone, again and got the same error logs shows that the error is in the boot file

[speeduploop]

then either the flashing didn't work - or the boot.img wasn't clean or the boot.img wasn't a dump from/for your device...

[I Understand I Exist]

okay, where to from here

[speeduploop]

flash your dump of your boot-partition...

[I Understand I Exist]

and i have never backed up my device before

[speeduploop]

That's quite bad...

(and the reason every How-To starts with recommending exactly this :D )

--> then you need to find a clean boot-image matching your device and firmware-version...

(which can be hard depending on your region/device-variant)

[I Understand I Exist]

damn, thats what i get for rushing into things, do u think that the boot.img is modifiable 

[speeduploop]

It definetely is - but that won't help you.... you won't be able to get the checksum right.

--> so you need to get a matching image.

[I Understand I Exist]

guys, it worked, i flashed all files from magentacloud that were for ta-1048 v12 rebooted and updated it worked, now i have a v16 os 
thank you speeduploop and Ivan

[I Understand I Exist]

before i proceed i need to back up my os, dump all isn't working, i guess it requires root ??

[speeduploop]

No - it needs a recovery-testkeys... so you can start it through recovery...

(you probably should at least try the search-function of this group... it works quite well!)

[Carlee Garcia]

I tried to repair my partition to update to v16 but no luck it still not working :/

[Carlee Garcia]

I also have questions do I need to wipe the system and mount the system before flashing the 4bash? I'm really not sure so thats why I asked. Thank you.

[Ivan Alex HC]

hi, you only need to mount system and retry. use the speeduploop's fresh dumps to have a clean and sure Nokia (but use ONLY the dumps of your firmware version)

[Carlee Garcia]

Yes I did use only the clean partition but no luck it still not work

[Geek]

I recently faced the same problem, so I installed GerdaOS and than used 4bash.zip and it worked, hope it works for you too.

[Carlee Garcia]

What exactly did you do?
I tried to Flash Gerda again, wipe data, mount system flash 4bash.zip, the new dumps folder contains the v12 clean dumps from the back up section of the banana hackers all files are in bin format and I changed them all to "IMG", now I am on v12 and tried to update then it failed again, error 7.

[speeduploop]

Usually the meaning of 'error 7' is that you flashed the wrong images...

(or not all images you would have needed to flash)

--> read the logs.

Re-flashing the v12 images from 'Banana Hackers' only makes sense if your device was on v12 and has the same device-variant...

--> you were on GerdaOS which is based on v13... if you flashed GerdaOS on top of v12 - reflash v12 images... if you flashed GerdaOS on top of v13 you need to reflash v13 images...

But again --> the log will tell you which partitions are wrong....

[Carlee Garcia]

Yup I flashed it over to v12,on logs it says that boot didnt match simething like that

[speeduploop]

Yes - that's normal...

You flashed parts of it over to v12... that's a bad idea.

--> reflash to clean stock version you had before installing GerdaOS.

(as I already mentioned)

In the worst case you now have a mix of v12, v13 and GerdaOS... this won't work for fota-update.

[Carlee Garcia]

Unfortunately I didnt back up XD

[speeduploop]

Then you would need to find images of the same device-variant as yours...

(dual-/single-sim and region it's build for should match)

[Carlee Garcia]

Yep, I tried to flash the v12/T0159/Asia but didnt work for me.

[speeduploop]

So before you flashed GerdaOS your device was on v12?

-- if yes, and your device was asian/T0159, then that was a good start...

--> now you have to read the logs... it may tell you after every non-working update which partition you have to repair next...

(yes - that's annoying, but there is no other way...)

In the best case it's only about system, splash, boot - but it needs to be exactly the partitions matching your device and version.

(and if you did a 'repair-all' with the wrong images -- then you will have to re-flash a whole lot of images.)

BTW: 'it didn't work for me' is the worst information you can give... because it isn't any information at all.

Without knowing what went wrong (again read the logs - it's in there) no one can help you.

[Carlee Garcia]

I might stick with Gerda OS for now, thanks for the helpmate.

[apatrahil]

Speeduploop, what is your patch for gallery, if is not military secret? I try with downgrade gallery with this from v13 - same, check something in config.js, imagesize.js..., but nothing understandable for me.

[speeduploop]

google won't let me answer here -- again...

--> strange...