Develop Bugs

[Q] [TMobile] IMEI Back up/ Restore

Simply put, do you have a verifiable way to do this?

Currently there is not. There is a thread in general discussing this problem. I hope we find a way soon. Take caution when flashing.
Sent from my SGH-T999 using xda premium

This is from the SGSII I9100 General section. I thought that since my phone was messed up, I'd give it a try,
but it was a no go. This does tell me a couple of things though. 1. CWM does copy the efs folder, and 2. I do not think the IMEI is there, but since I'm unsure when I lost my IMEI it is of course a guess.
[GUIDE] Recover your IMEI in 9 steps.
1. Running on a stock rooted ROM. Used Rom Toolbox. Created a folder called tempefs. copied the efs folder into tempefs.
2. Deleted the efs folder...rebooted the phone got a message that Factory Mode was on.
3. Went to restore the efs folder from my tempefs and it was GONE! I did not copy it to my external SD!
Phone still worked fine, but now a big box with System information is displayed.
4. Did a CWM recovery and back to normal except this time it restored CM9...so, the efs folder IS included, however, my IMEI # is still 0.
5. Started over...this time copied the efs folder to my external sd card.
6. Deleted the efs folder and rebooted phone. Note: Phone did not come back up into Factory Mode...running CM9.
Further, this "4) go to EFS folder using root explorer, and delete "nv_data.bin", "nv_data.bin.md5"." did not
apply.
7. Copied my imei folder from my external sd to the efs folder.
8. Copied my redata.bin file from my external sd to the efs folder.
9. copied my redata.bin file again
10. renamed my redata Copy.bin to redata.bak
11. Used Terminal and typed the following:
su <enter>
chown 1001:radio /efs/redata.bin <enter>
gave me this error message: Unable to chown redata.bin : Read only file system 10
12. I went in an changed the permissions of the file to all read all write and all execute and tried again.
same error message.
So, there ya have it. I have now received my replacement phone, so if any of you very smart dudes out there have any suggestions, I can compare stock vs. screwed at this point.

If you are willing to do some experimentation, we may be able to validate a backup/restore. Try doing this just as a proof-of-concept, though it may or may not be illegal (modifying an IMEI is illegal in several countries). You should only need to be rooted on the old phone for all the below
Without your SIM card in the old phone (we dont want the carrier knowing this happened :angel
1. Backup your old phones current /efs with the following command:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/external_sd/efs_backup.img
(If you arent on a CM rom, you might need a different path for /external_sd/
2. Backup your new phones /efs with the same command. Done with the new phone (I aint trying to get that one messed up to )
3. Copy both files somewhere
4. Copy the new phone's efs backup to your old phone to something like /external_sd/efs_new.img and run the following to restore the new phones efs to your old phone:
Code:
dd if=/external_sd/efs_new.img of=/dev/block/platform/msm_sdcc.1/by-name/efs
Reboot (without the SIM) the old phone and see if it shows up with the new phone's IMEI info. If it does then I think we can say the above command can successfully backup and restore the efs data. At that point, restore the corrupted efs back over the old phone so that you dont have two phones with the same IMEI.
And use adb, not terminal emulator. You really do not want to make a typo with those dd commands. I strongly suggest people get a putty binary that has adb connectivity. And use bash on the phone.

I will check this out...I have 6 days to return my phone. Too damn tired tonight though. Thanks!
Sent from my SGH-T999 using xda premium

lumbu said:
If you are willing to do some experimentation, we may be able to validate a backup/restore. Try doing this just as a proof-of-concept, though it may or may not be illegal (modifying an IMEI is illegal in several countries). You should only need to be rooted on the old phone for all the below
Without your SIM card in the old phone (we dont want the carrier knowing this happened :angel
1. Backup your old phones current /efs with the following command:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/external_sd/efs_backup.img
(If you arent on a CM rom, you might need a different path for /external_sd/
2. Backup your new phones /efs with the same command. Done with the new phone (I aint trying to get that one messed up to )
3. Copy both files somewhere
4. Copy the new phone's efs backup to your old phone to something like /external_sd/efs_new.img and run the following to restore the new phones efs to your old phone:
Code:
dd if=/external_sd/efs_new.img of=/dev/block/platform/msm_sdcc.1/by-name/efs
Reboot (without the SIM) the old phone and see if it shows up with the new phone's IMEI info. If it does then I think we can say the above command can successfully backup and restore the efs data. At that point, restore the corrupted efs back over the old phone so that you dont have two phones with the same IMEI.
And use adb, not terminal emulator. You really do not want to make a typo with those dd commands. I strongly suggest people get a putty binary that has adb connectivity. And use bash on the phone.
Click to expand...
Click to collapse
Awesome idea, but it did not work. Any other ideas?

zonly1 said:
Awesome idea, but it did not work. Any other ideas?
Click to expand...
Click to collapse
We can go through each block device one by one to try to find where the data is stored. But this could lead to an actual brick of the old phone, and I dont want you to do anything that might cause T-Mobile to charge you for something that they say voided the warranty. The rest of the backup commands (excluding /system, /data, /cache and recovery) would be:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/external_sd/aboot_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/backup of=/external_sd/backup_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/external_sd/boot_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/external_sd/fota_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/external_sd/fsg_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/grow of=/external_sd/grow_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/external_sd/modem_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/external_sd/modemst1_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/external_sd/modemst2_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/external_sd/pad_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/external_sd/param_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/external_sd/persist_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/external_sd/rpm_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/external_sd/sbl1_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl2 of=/external_sd/sbl2_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl3 of=/external_sd/sbl3_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/external_sd/ssd_backup.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/external_sd/tz_backup.img
I really dont know what each of these does, so if I were you I wouldnt listen to me or try this. But if you want to experiment and are not worried about what T-Mobile might do, backing each of these up on the new phone and going through restoring one by one on the old one should let us figure out what device actually needs to be backed up.
Or we could wait for some people smarter than me who can figure this out without risking a brick.
------
Edit
-----
Before trying to restore, try backing them up on both phones. Then do an md5sum on each image to see which might be the same between the two. Cross those off the list of what to try restoring.

There's a user names Geek that is working on a fix...looks promising! Thanks for all the help!
Sent from my SGH-T999 using xda premium

[Q] adb restore doesn't restore everything

Hey,
I've created a backup with this command:
Code:
./adb backup -f fullbackup_2013-03-28.ab -apk -shared -all -system
The resulting file was 11 GB which was expected. After this I unlocked my bootloader. Restoring the backup hung two times. FIrst at com.android.chrome then at com.google.android.googlequicksearchbox. These two were also mentioned in Android issue report #34311 (sorry can't post link, I'm under 10 posts). Both times I rebooted my phone and restarted the restore. The third restore went through.
Now my problem is I'm missing a lot of data. My storage is only at 6 GB, that's at least 5 GB missing. My music folder for example was only partially restored. How can this be? Is there anything I can do?
I'm running 4.2.2 stock. My adb version is 1.0.31.
Update: I've now extracted the backup and I can say for sure that there are files in there that don't get restored.

Has nobody else experienced such a behavior?

AW: [Q] adb restore doesn't restore everything
yes i have done that with my nexus 7.. it seemed to restored my file structure but when i tried to open files nothing would happen... u really cant rely on that thing
Sent from my Galaxy Nexus using xda app-developers app

It's safer to use adb pull and adb push to backup and restore the sdcard, and only use adb backup for user apps and data. Also, it's not generally a good idea to backup and restore system apps and data. So -noshared and -nosystem for adb backup, and pull and push for the sdcard might work better. As for the data you already backed up, maybe Titanium Backup would help. I understand it can access adb .ab files, though I haven't used it for that myself.

Replacement phone restore twrp backup

I had to have my note2 replaced I did a twrp backup placed it on new phone in the backup twrp folder but it is not recognized. Anyone have any possible solutions? Really all I'm after is game data that was backed up,and I'm not sure where to find that particular file in the backup thanks.

pretty sure u wouldnt wanna do a full nandroid restore of your partitions to another device... but as far as your game data goes.... you can use titanium backup to recover the apk and the game data by extracting from the nandroid backup file.

I've tried to do this before. It won't work.
Sent from my SGH-T889 using xda premium

Hey buddy. New device just start fresh. Safest way...

Hey,
I was on the same boat as u. I got it to work. I can remember the specifics at the moment but gist of it is that twrp creates a specific backup folder unique to each device. Open up an file browser and navigate over to where u have your backup. If theyre o. Your sd card it should be TWRP > BACKUPS > (Here u should find 2 folders with a bunch of random letters and numbers)
Those 2 folders are your backup folders. One was from your old device and the other is the folder twrp created for your new device.
When u reeboot into recovery, twrp wont recognize the old backup folder since it was unique to your old phone.
Long story short. Lol. Just go into the old folder from the file browser and copy the backup to the new back up folder.
After that, delete the old backup folder. Your backup should then show up when you boot into recovery.
As for which is the old and which is the new folder. My best bet is tbat the new folder is empty and the old folder has your backup.
Hope that helps.
Let me know if you need more help.

[Q] Backing up Z1 Compact from computer?

Hey guys,
The screen on my Z1 Compact just died. Only the screen, so everything else still works - still boots up normally, still rings when I call it, still shows up on my computer drives when I connect it via USB, and can boot into fastboot. It's got CM11 and CWM on it.
My question is, is there anyway for me to perform something like a nandroid backup of my current system from my computer without having to do anything from the phone, so that when I get a new one back from warranty, I can have it exactly as it was?
Thanks!

Boot to CWM and connect to phone with adb. You can
use the builtin adb backup function (will not backup everything)
backup partitions manually like a nandroid backup with dd / tar
make a flashable zip and then do backup_rom("path for backup") (cwm specific command, this should do a nandroid backup)
run nandroid backup in adb shell (I recommend to try this first)

zxz0O0 said:
Boot to CWM and connect to phone with adb. You can
use the builtin adb backup function (will not backup everything)
backup partitions manually like a nandroid backup with dd / tar
make a flashable zip and then do backup_rom("path for backup") (cwm specific command, this should do a nandroid backup)
run nandroid backup in adb shell (I recommend to try this first)
Click to expand...
Click to collapse
Wow thanks! I managed to run nandroid backup via adb. I can't seem to find the backup files though - any idea where they would have been saved?

Check /sdcard/clockworkmod/backup or /storage/sdcard0/clockworkmod/backup

Best way to do a full backup (and restore it)?

Hi, on my previous phones I used TWRP to create full backups of my phone. My A2 lite is rooted with Magisk and I decided to keep the stock recovery to simplify OTA updates (also there is no official TWRP build available supporting encryption). The phone is already setup completely and I don't want to start all over again so formatting is not an option. Still I want to be able to create a full backup in case something goes wrong or the phone gets damaged. Is there a way to do this or do I have to continue with SD and TB backups? Thanks in advance.

nice q >>>waiting for an answer ???

I used Titanium Backup before. But now I'm using Migrate for backups.

My backup is TB and rsync of /sdcard to a server at home (automated overnight).
I never bothered getting anything else setup. I try not to brick my devices
I did have to restore a few times when I first got the phone, until I figures out how to recover from Magisk/xposed errors without factory reset.

i prefer Titanium Backup method with batch file to backup folders i need from phone memory to PC. of course i backup Titanium Backup folder too,
minimal adb&fastboot package is installed (portable) so i can perform below backup:
backup.bat
these example lines inside
adb pull /storage/emulated/0/DCIM
adb pull /storage/emulated/0/Download
adb pull /storage/emulated/0/Pictures
...