[TOOL] kTool v1.55 - Dump+Flash kernel / Backup+Restore EFS,Check if EFS backup is OK

---

Heya!

Some know my little kTool already, some love it, some hate it.
Well, let's try to get some more love for it




>> Now with support for the Galaxy-Nexus and the Galaxy-S3! <<


So, what does this do?

• Dump current kernel (and recovery on devices having a seperate one)
• Flash kernel from /sdcard/zImage
• Flash recovery from /sdcard/recovery.bin
• Backup EFS
  (as raw .IMG dump and as .TAR archive)
• Check/Verify EFS backup (i.e. compare to "live" EFS)
• Restore EFS from either .IMG or .TAR
• Open stock update .TARs and flash from from it:
  - Modem Firmware
  - PARAM.LFS
  - Kernel
• Reboot device
  - normally
  - to recovery
  - to download mode

*) When you check the EFS backup right after you made it, it should show a 100% match to the current phone's EFS.
However, after a reboot, the EFS *does* start to differ a bit - that seems to be normal, during my tests the EFS differed for 80bytes more after each reboot, my original EFS dump even differed by ~150k already

kTool companion tool market link [ Show ]

Hope you like it.


If anyone has more suggestions on what would need to be checked/verified during the check operation, do tell

After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason? :@

Sent from my GT-I9100 using XDA App

Originally Posted by koolshubh

After doing backup I did efs backup check....
And in that it says nv_data.bin not found..
Whts the reason? :@

For the .img and the .tar or only for one of them?
What does it say for "mount returned:"?

"nv_data.bin not found" means a bad/corrupted backup.

// EDIT

Just saw the screenshot.

Something went wrong making the raw .img dump (weird....).
But the .tar backup is OK (100% match to the phone's one).

Hmm.... gotta investigate the .img issue some more.

Check this;




Sent from my GT-I9100 using XDA App

OK, that helps a lot already.

The efs.img dump might be all fine and OK, it's actually a problem getting it mounted to "look into it".
Dug around some more and also found this:

2: system error (out of memory, cannot fork, no more loop devices)

"2" was the returncode you got during the check, fits with the verbose error message you get when trying the mount from a shell.

Cool, at least I know where to look, not exately sure why this happens, but we'll find out.
Maybe a busybox thing, maybe I'll bundle one with the app....

thanks for updating~~~

I have used the old one from here
f.lui.li/get_99_f13d.html

Updated to v1.21

Everything is working from my end. Thanks for the tool!



Sent from my GT-I9100 using XDA App

Originally Posted by HellcatDroid

Updated to v1.21

it just works!
thx!

Thanks and cheers.