[Q] efs backup went wrong, HELP PLEASE! - T-Mobile Samsung Galaxy S II SGH-T989

i rooted my " sgs2 SGH-T989 " Yesterday and as i was learning more things on this website i found out that i need to do a EFS Backup to stay out of trouble "but i m in it right now " ..so i downloaded the app ( hc-ktool ) used it and this is what it gave me after doing a backup check :
checking current efs backup.....
/sdcard/efs.img found
-------------------------------
mount returned: 255
(unable to mount image-image corrupted?)
/!\ nv_data.bin NOT FOUND in backup!!!
/sdcard/efs.tar.g2 Found
-------------------------------------
/!\nv_data.bin NOT FOUND in backup !!!
plz what to do now , i tried the other methode but i keep getting this "busybox : permission denied"
any help ?

1- are you rooted?
2- why do u need to mess with EFS? I really see no reason to do so at all
what do u mean by u r in trouble right now? is your phone still functioning normally?

thanks for responding, my sgs2 i rooted and i have done a cwm backup and also a titanium backup too, i just wanted to backup my EFS folder too as i heard many people having problems with EFS folder becoming corrupted with the use of some ROMs....so to do the backup i used ’ hc.ktool ' backup did not succeed and phone now is doing all kind of bizar things. .....turns off with just pressing power button for 2 seconds with no meneu showing...lost my contacts ....lost my lockscreen....phone freezez sometimes....but i still have the right EMEI number !! my phone is just rooted still with stockRom.
i think the hcktool messed up my phone is there a way to undo or go to previous state before i used the hcktool ?
any help is welcomed phone is only 3 months old

Read this
http://forum.xda-developers.com/showthread.php?t=1438451

thanks xcrazydx
i should try that too, i ll give it a shot tonight, but as one of my friends advised me, i did a " dalvik cleanup + fix permissions " and It seems to have fixed both the lockscreen problem and the power off issue too...( to be honest i have no clue what dalvik clean up & fix permission do exactly to the EFS Folder if anything at all !! but i still have the screen freeze happening every now&then plus some apps forceclose " like opera browser, was using it when suddenly shut down for no reason " still having issues with busybox also
i still dont now if my EFS FOLDER is corrupted or not " my IMEI number is still the same thow...I JUST DONT GET IT ALL THIS HAPPENING AND I M STILL AT STOCKROM DID NOT FLASH A SINGLE ROM YET !!
i hate " hc-ktool"

Related

[Q] Backing up app data before unlock bootloader?!

Hi folks,
I took sometime to check that my phone was working properly for warranty reasons and now I am desperately trying to backup some of my apps (not even everything...) before unlocking the bootloader (which wipes everything, that's the whole problem!) and install a custom ROM. If have tried the following options :
Titanium backup : I am not root so it doesn't work. Other software could save my APK but not the actual data, which is what I am interested in
NANDROID backup : as I am not unlocked so I don't have a custom recovery image so no nandroid backup
adb backup : was my best hope but it really behaves weirdly on this device : it states in logcat that it can't find the specified package or that it can't bind it... really weird :
Code:
D/BackupManagerService( 272): Binding to full backup agent : com.mypackage
W/BackupManagerService( 272): Unable to bind to full agent for com.mypackage
W/ActivityManager( 272): Unbinding backup agent with no active backup
W/ActivityManager( 272): Process/uid not found attempting kill of com.mypackage / 10272
W/ActivityManager( 272): Unbinding backup agent with no active backup
W/ActivityManager( 272): Process/uid not found attempting kill of com.mypackage / 10272
I also tried this script (http://smartmobilehub.com/actionbar/36152/Ultimate-Backup-Tool-No-Root-Required) that automates the process, but as it uses adb backup it doesn't work either.
I am thinking about trying to root the device without unlocking the bootloader (with this tool for instance : Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460) but I am really not confident it will work and will not hurt my device. Did anyone try that ?
Did anyone ran into the same kind of problem ? Has someone got a solution ?
Can someone with stock JB test if adb backup works (very easy command to backup google maps for instance :
Code:
adb backup -f mybackup.ab - apk com.google.android.apps.maps
If the output file is more than 1ko then it probably worked, you can check in titanium backup with the option : "restore from .adb backup") if JB solves this problem, then it's worth waiting for the update, otherwise I could try something else right now.
Thanks in advance for your help!
adb backup should work. I've done it before, but never tried to restore it. None if the other options are viable.
Thanks for your input BenPope! I think you should check your backup with Titanium Backup, you could be surprised...
For me it seemed to work : first I launched the full backup, it did backup the shared part (SD card part) for a long long time and did output a massive several GB file, but it didn't backup all the other packages except for a random few ones (and I ran the backup several times caused it sometimes crashed my phone and overall the output size was always different). I discovered that with Titanium Backup, and therefore tried to backup a single package with logcat which outlined the problem exposed in my previous post.
Can you try backing up a single package if you are still on stock ?
Maybe I'll try tomorrow. I'm not rooted, how far can I get with Titanium to test it?
BenPope said:
Maybe I'll try tomorrow. I'm not rooted, how far can I get with Titanium to test it?
Click to expand...
Click to collapse
You have no other choice than using another device that is rooted as Titanium Backup (TB) won't offer much options on a non rooted one... I used my tab for instance. Also keep in mind that this is a Pro feature that requires you to purchase TB (but if you plan on rooting, this is the best app ever! )
Other option, without TB, you can try running the backup on a single package (use my command or ultimate backup script, see 1st post). If the output is a 1ko file with the -apk option (which determines to backup the apk too), then something went wrong...
Just do nandroid back up in recovery
johnnyk75 said:
Just do nandroid back up in recovery
Click to expand...
Click to collapse
How? I don't have a custom recovery as I am not unlocked
Good news! I just had the JB OTA update today and it solves the adb backup problem : backup is now possible (though with no password and data only it seems, but it works). So I now have back-up my data and unlocked my bootloader, at last!
Thanks for your help folks

imei null on n7100 4.4.2

My phone was working fine before battery drained and it get switched off. But when i restarted the phone imei was null.
I have efs backup of 4.3 ( mj9 modem) but now i am on 4.4.2 . I tried restoring it but did not worked .
any help please..
sachinwadhwa46 said:
My phone was working fine before battery drained and it get switched off. But when i restarted the phone imei was null.
I have efs backup of 4.3 ( mj9 modem) but now i am on 4.4.2 . I tried restoring it but did not worked .
any help please..
Click to expand...
Click to collapse
try what i did here buddy. . post #3512
http://forum.xda-developers.com/showthread.php?p=57661153#post57661153
do it at tour own risk. goodluck!
edong23 said:
try what i did here buddy. . post #3512
http://forum.xda-developers.com/showthread.php?p=57661153#post57661153
do it at tour own risk. goodluck!
Click to expand...
Click to collapse
Thank you for your reply. Please help me to do this step wise
sachinwadhwa46 said:
Thank you for your reply. Please help me to do this step wise
Click to expand...
Click to collapse
this method works for me, but I am not sure if it will work for you. I have to warn you that I am not a dev, I am just a basic android user. I came up with this idea out of desperation because my phone cannot receive and make calls for almost 4 days. so do this at your own risk.
note:
* make sure your phone is rooted.
* make a copy of your old efs backup and all your important files in your computer or in a flash drive.
1. copy and write on a piece of paper your imei # which will be found at the back of your phone. it is 15 digit
2. copy your efs.img (not the folder that contain the efs image) to your internal storage. it is about 20mb. if there are two files then copy both.
3. connect to wifi and go to playstore and then download and install the IMEI Tool N7100 by Dr Ketan
4. download and install xposed installer and make sure to install update.
5. go to this thread and download and install imei changer
http://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
make sure to activate it in exposed. then reboot your phone.
6. using ES File Explorer or any file manager with root privelege, go to /efs and delete all files
7. open imei changer then input your imei # (the one that you copied at the back of your pbone) then save. to make sure that your imei has changed dial *#06#. check if your imei if its the one you have written. if not go again to imei changer and change then make sure to save.
8. open IMEI tool by dr. ketan and restore efs backup. it will ask for root privelege so click grant.
9. after restoring efs, reboot to recovery and wipe cache and dalvik then reboot. check if you have data connection.
10. if its not working then go to recovery and make a full wipe and install new touchwiz rom (i used DN4 when I did this, but its up to you whatever you like). and repeat the steps.
* that's all I did mate. there is no scientific explanation about the process that I made, but when I did those things, my phone is working fine again. hopefully it will work for you brother. Good luck and God bless!
edong23 said:
this method works for me, but I am not sure if it will work for you. I have to warn you that I am not a dev, I am just a basic android user. I came up with this idea out of desperation because my phone cannot receive and make calls for almost 4 days. so do this at your own risk.
note:
* make sure your phone is rooted.
* make a copy of your old efs backup and all your important files in your computer or in a flash drive.
1. copy and write on a piece of paper your imei # which will be found at the back of your phone. it is 15 digit
2. copy your efs.img (not the folder that contain the efs image) to your internal storage. it is about 20mb. if there are two files then copy both.
3. connect to wifi and go to playstore and then download and install the IMEI Tool N7100 by Dr Ketan
4. download and install xposed installer and make sure to install update.
5. go to this thread and download and install imei changer
http://forum.xda-developers.com/xposed/modules/xposed-imei-changer-t2847187
make sure to activate it in exposed. then reboot your phone.
6. using ES File Explorer or any file manager with root privelege, go to /efs and delete all files
7. open imei changer then input your imei # (the one that you copied at the back of your pbone) then save. to make sure that your imei has changed dial *#06#. check if your imei if its the one you have written. if not go again to imei changer and change then make sure to save.
8. open IMEI tool by dr. ketan and restore efs backup. it will ask for root privelege so click grant.
9. after restoring efs, reboot to recovery and wipe cache and dalvik then reboot. check if you have data connection.
10. if its not working then go to recovery and make a full wipe and install new touchwiz rom (i used DN4 when I did this, but its up to you whatever you like). and repeat the steps.
* that's all I did mate. there is no scientific explanation about the process that I made, but when I did those things, my phone is working fine again. hopefully it will work for you brother. Good luck and God bless!
Click to expand...
Click to collapse
I followed the same procedure but did not worked.
One more thing i would like to mention that in recent past i got my complete pcb replaced by samsung service center but imei was same. and the backup of efs which i did was on previous pcb/motherboard. could that be the reason i am not able to restore imei?

"Fix Permissions" causing bootloop Please help!

D855 running blisspop 2.2 (5.0.1)
As above, I had an issue with my G3 losing the home button at the bottom after 5 mins of switching on so I decided to Fix permissions in TWRP
My G3 is stuck in the blisspop boot animation and stupidly I don't have a nandroid backup :crying: . I have then tried to reboot into TWRP and make a nadroid backup of the bootlooping rom so I could try to get data off it, I'm mainly trying to get my SMS and call history data off the bootlooping rom as all my pictures e.c.t are still on the phone. I have dirty flashed the same version of Blisspop 2.2 I had running but no apps or data show up.
I have tried to used Nandroid manager to try getting the SMS and call log off the old rom, but It says file not found.
Can someone please help me, I just want to get my SMS's off the phone
You could try using adb shell commands to pull the sms and mms messages from your phone. See if the commands from this thread are of any help...
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
redduc900 said:
You could try using adb shell commands to pull the sms and mms messages from your phone. See if the commands from this thread are of any help...
http://stackoverflow.com/questions/12266374/backup-full-sms-mms-contents-via-adb
Click to expand...
Click to collapse
I tried doing so, however I seem to have not to have "/data/data/com.android.providers.telephony/databases/mmssms.db" file or the "com.android.providers.telephony" folder in general
I also checked this in TWRP file manager and I don't have the folder let alone the file, it seems other com.android folders are missing too such as dialer, cell broadcast receiver, nfc e.c.t
I've dirtyflashed the same version of the ROM again to see if this also had files missing, however this has "/data/data/com.android.providers.telephony/databases/mmssms.db" and other folders present when I check in TWRP's file explorer and I can use adb pull to get the mmssms file off from the new rom.
Did "Fixing permissions" really cause me to lose all these com.android files?

unable to backup data on twrp

Hello everyone, today while trying to do backup in twrp, I am continuously getting the error message as "createTarFork() process ended with ERROR: 255
Backup Failed.". I tried some solutions mentioned in the forums, but they seem to be having error with different folder. In the log I found that there is error in opening webviewgoogle, but I couldn't found that folder anywhere.
Invalid encryption mode 'ice:aes-256-cts'
Backing up System...
Invalid encryption mode 'ice:aes-256-cts'
Error opening: '/system/app/WebViewGoogle' (Structure needs cleaning)
I:Error in Generate_TarList!
Error creating backup.
I used codeworkx and Blu spark twrp and both seems to have the same issue. Kindly help me in doing a backup. Thanks in advance.
I use blue spark and the copy does it well but restoring a backup gives me an error because I can not mount the system and I also get the phrase that the system needs to be cleaned ... By when a functional twrp???
Princeland said:
I use blue spark and the copy does it well but restoring a backup gives me an error because I can not mount the system and I also get the phrase that the system needs to be cleaned ... By when a functional twrp???
Click to expand...
Click to collapse
I just skipped the back up and did format the data and clean installed the ROM and it worked. Earlier I was unable to restore due to mount system error but I just clicked the system in advanced->mount in twrp and restore the old backup...
Try deleting all paralell apps under the apps Section
galaxy s4 nutjob said:
Try deleting all paralell apps under the apps Section
Click to expand...
Click to collapse
It's not related to parallel apps. I checked this one already.
I had this problem a couple weeks ago:
So the first thing you do to fix the system partition not mounting is to download this tool: https://androidfilehost.com/?a=show&w=files&flid=38683
Tool looks like this: https://i.imgur.com/04L1h9b.png
Step one: Install drivers. Should be straightforward.
Step two: Make sure you device is connected. It detects it in fastboot and everything just press the refresh button a couple of times. In this case you're best off starting in fastboot mode.
Step three: Erase all data / Decrypt internal storage. https://i.imgur.com/2HZN1jK.png
Step four: Flash twrp. Make sure to select your device in the dropdown list. Then select recovery flasher and flash the one shown in screengrab. https://i.imgur.com/80N32db.png
Step five: reboot into recovery and flash what ever you want.
This tool is extremely usefull and quite timesaving. Make sure you explore it's features.
Note: I do not own the tool nor do I know the dev.
Happy to help
pinnekeshaar said:
Step three: Erase all data
Click to expand...
Click to collapse
Seriously, every time I read this, I think to myself, what sort of a pure evil person may hide behind such a malevolent advice?
Really, what's wrong with you, man? Were you, like, tortured as a child? Your loved ones murdered?
To give this sort of advices to people who want to god damn it BACKUP (that means, save and protect, not erase) their data.
lockywolf said:
Seriously, every time I read this, I think to myself, what sort of a pure evil person may hide behind such a malevolent advice?
Really, what's wrong with you, man? Were you, like, tortured as a child? Your loved ones murdered?
To give this sort of advices to people who want to god damn it BACKUP (that means, save and protect, not erase) their data.
Click to expand...
Click to collapse
Well I guess you've been right on time with your part of the advice. You know, three months later. Also, some people have brains and can think of the fact they need to backup their stuff before deleting everything.
Three months later I found this thread in Google.
And also, just in case, the thread is exactly about making backups.

Samsung s20 Ultra imei status goes NG after rooting

I need experts review and help to resolve my issue last night i am update my phone s20 ultra G988B/ds to its original software everything working fine except network i was using root phone it was fine on all networks but after updating my imei status goes to NG(not good) sim accepted phone but shows emergency calls both imei shoes but network not working plz give me suggestions and issue solution. I am again root my phone but still not working networks plz help
S20 ultra imei status NG
Why you experts not solving my issue no comments at all?
Bro i've posted same kind of post just now i hope someone replies soon otherwise i'll try z3x software or chimera and let you know about the results, i think if your imei is not corrupted then cert file will do the wonder.
well hey everyone same issue i have s20 plus phone was rooted and i flash the firmware and now imei is NG i trid the chimera tool but no luck if u find any fix please help me.
did you guys resolve it ?
i may have an idea
Any fix
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin.
That solution work???
juda iskariotsky said:
do you guys even search before asking?
First, do a TWRP backup, all partitions including efs & modem.
Open the root explorer app, open the efs folder, delete the files named nv_data.bin
, nv_data.bin.md5 & the folder called imei. Then open twrp, wipe all partitions. Flash the latest firmware with Odin
Click to expand...
Click to collapse

Categories

Resources