Galaxy S4 (9500) Imei backup about - Galaxy S 4 Q&A, Help & Troubleshooting

Hi with which method Healthy imei (EFS) backup How do i get it?

If your IMEI is present and accounted for, download this app from the Play Store, install it, and run it to back up your IMEI and EFS. You can also use this app, which has the added advantage of being able to back up the hidden partitions on the device where the IMEI tends to be stored.

TWRP recovery EFS Would you recommend backup

I always back up EFS when making a nandroid backup. However, that will not be sufficient to restore things if you have an issue with the IMEI.

Both through applications and TWRP recovery If i back up When there is a problem Will backups resolve the issue?

If you have used the apps I provided links to in order to back up things, you will almost certainly be able to restore your device to working condition if there is an issue. Just make sure you store a copy of the backup somewhere other than your S4. For example, send a copy to Google Drive or your favorite cloud storage service, as well as send a copy to your PC's hard drive.
Note: I tend to recommend using the second link I provided over the first, as backing up the hidden partitions really can be a game changer if something happens.

Related

[Q] Question about Nandroid backups

I've never used a Nandroid backup to recover everything. I usually just stick with Titanium Backup. Lets say I decide to replace my TF because of light bleed. Can I recover from a Nandroid backup I created on my first TF? Will the backup from the old device work on the new device or are these backups tied to a specific serial number?
sigh... The only time anyone answers my questions is when I hijack someone else's thread and ask it when it's unrelated.
Its generally not a good idea to use nandroid backups across devices. You could muck some things up. Titanium backup would be a better way to go.
Sent from my Transformer TF101 using XDA Premium App
I'm not an expert by any means, perhaps someone with more knowledge will make sure that I'm correct or wrong here?
My understanding is that a nandroid will take an exact image of your device at that given point in time and it'll create a checksum for the backup, so as long as the backup and the checksum match and your devices hardware is the same I can't see a problem restoring to an identical machine.
That's all presuming that you've got the new device rooted and have CWM on it and that you have copied the clockworkmod backup/restore folder to your SD card/PC.
Edit: I should have clarified what exactly it is that you want to back up, if it's just apps and their settings then I'd go for Titanium too. Doesn't your Google account backup and restore apps too?
Nandroid backups do work across devices, and if you really wanted, you could restore them on new devices. Not the best idea, but it is possible.
If you use a nandroid backup, I would install the same rom as the first, then advance restore data only

[Q] What do i have to backup before changing rom?

Applications backup but not cache or data?
System backups?
Sms and call logs?
And system backups?
Are those all to do? If i backup those, when i restore, will i be able to have my desktop widgets, desktop icons sorted correctly ?
I think the best answer is "it depends on what you want to restore to".
When I change roms, I make a full backup using CWM, that way, no matter what the new rom breaks, I can go back to exactly where I was before.
But if you really want the new rom and think the problem is in one app or setting, you can backup only the apps .apk, the apps data and the rom settings, then you can restore everything individually and see where the problem is.
This all assuming you are not changing major android versions (like from froyo to gingerbread) or not changing roms "types" (like from stock to CM or to miui). If you are, then the partial backup is not recommended since it may not work.
In this last case, your best hope is to backup the apps .apk and store all other data somewhere where you can import to android (like storing the contacts in google account), since you shouldn't really restore anything else.
paulo_andre said:
I think the best answer is "it depends on what you want to restore to".
When I change roms, I make a full backup using CWM, that way, no matter what the new rom breaks, I can go back to exactly where I was before.
But if you really want the new rom and think the problem is in one app or setting, you can backup only the apps .apk, the apps data and the rom settings, then you can restore everything individually and see where the problem is.
This all assuming you are not changing major android versions (like from froyo to gingerbread) or not changing roms "types" (like from stock to CM or to miui). If you are, then the partial backup is not recommended since it may not work.
In this last case, your best hope is to backup the apps .apk and store all other data somewhere where you can import to android (like storing the contacts in google account), since you shouldn't really restore anything else.
Click to expand...
Click to collapse
I want a full back up; calendars sms call logs applications data system data etc. For sms i use go-sms backup, i hope it will restore without any problem. When i backup with cwm and restore, will my settings (system( be protected as before?
With CWM if you restore you will get all data, including Rom, Kernel, sms, calls, etc All you data that is in internal memory. Don't worry. If you restore it, you will get the phone like it was when you made the backup.
Titanium capabilities
I was wondering if it is possible to backup app (with their data), sms and contacts....all in one go using Titanium (non-pro version) (I think we call it batch backup)? I am totally new to the ROOTING and CUSTOM ROM worlds and I am literally freaking out with all the huge info on this topic on the internet. I am using a CM10 on I9000. Please help!
Yes i wonder too.
Boot in recovery
select backup to ext sd
run...
you have back up everythin like ghost in pc....
( so you can try another rom and if you dont like it restore your back up and you have you old rom
working with all data app contacts etc )
you must youse the same cwm version for restore with the one that you use for backup
Cursed Chico said:
Applications backup but not cache or data?
System backups?
Sms and call logs?
And system backups?
Are those all to do? If i backup those, when i restore, will i be able to have my desktop widgets, desktop icons sorted correctly ?
Click to expand...
Click to collapse
Are you attempting to backup so that you can move the apps/sms/settings to the new ROM or backing up in case you want to restore? Titanium backup is probably the thing you want in the former case and either with cwm backup or with linux dd backup in the latter. Personally I had problem moving system settings between roms, but apps should work just fine.

Be k up data

What's the best way to move apps and data from n5 L to 6p M? Can we just move the Titanium BU folder to the new device and restore data? Google doesn't restore apps and data from Amazon, and seems to miss some other game data. Just restore Titanium app with Google restore? Or does nfc work with all apps and data (never tried it)?
Not sure what spell check did to the title, supposed to be "Back up data".
Sent from my Nexus 5 using Tapatalk
Titanium backup will do the trick, I've found. There are plenty of guides on how to do this. (Seems like you are familiar w/ it though.) http://bfy.tw/29yY
I usually make backups of only the apps I'm concerned about, plus a keyboard.apk I like, plus Amazon stuffs...
Then copy the folder into the SD card area of the new device.
Install TB from Play store on new phone.
Remove apps I'll be restoring, because they auto-installed, and it's kind of annoying but whatever.
Point TB to the folder I copied over, and restore one at a time. I've had some apps go sideways on a batch restore, but I don't know if it was the batch restore or the backup itself which caused the issue. Either way, I do one at a time now.
Enjoy.
More tips:
The First rule of TB is you never restore system apps.
The Second rule of TB is you NEVER restore system apps.
III Commandment : Thou shalt restoreth system apps never, or thy soul shall burn in heck.
If an app you plan on restoring DID NOT AUTO-GOOGLE-RESTORE-thingy during setup, it's a big tip it might not be compatible in some way in your new OS version / device. Go to Play store and check.
Games and other apps that already backup to the cloud - skip those, or at least don't restore them until you install from Play store normally and see how they recover. If they recover fine, then great.
Restore a small # of apps at a time, and test them all.

Samsung S4 I9505 no Whatsapp backup possible

Hi,
I can't perform a Whatsapp backup since January this year, regardless if Google Drive Backup is checked, if the Whatsapp app is stored in the local or on sd card memory, automatic backups are being cancelled, too.
After I hit "Backup", the Dialogue "Messages are being backed up" shows up, which closes after 10 sec without any error message.
I tried to contact the WA Support, but they insist that my S4 is rooted (which it isn't, maybe because of the custom ROM I use).
I have flashed my Samsung I9505 in January this year from CM 12.1 to CM 13. At the beginning, the phone ran smoothless except BT. After a while, WiFi stopped working as well. I tried to flash the CM 12.1 backup and radios without any success, just a new mainboard helped. I installed my CM 12.1 backup from January via TWRP from my old mainboard, which ran without any errors on it (after a fullwipe on the new one).
The phone works great, except the WA backup.
WA gets always updated to the current version, I have ~1,2 GB free internal memory, I tried to update to the latest CM 12.1 5.1.1 version from 12/26/2015, perform a backup via 4G, 3G, Wifi, with an without Google Backup checked, cleared the cache and wiped Dalvic Cache, there is no app deactivated.
I use Baseband I9505XXUHOD7 and Kernel: 3.4.107-cyanogenmod-gab9afd6clyde.
Running a custom ROM means you are rooted.
Now, I don't know why whatsapp wouldn't work on a rooted ROM, but if you want to backup you can use titanium backup.
GDReaper said:
Running a custom ROM means you are rooted.
Now, I don't know why whatsapp wouldn't work on a rooted ROM, but if you want to backup you can use titanium backup.
Click to expand...
Click to collapse
There is no root, please check the screenshot below.
Since there is no root, I can't use Titanium Backup, however, it wouldn't be the most practicable way to backup your Whatsapp history every time with Titanium Backup.
Besides that, I don't think this would work if I would like to transfer my history to a new phone on which WA Backup should work as intended as I won't flash the ROM/install root and void the warranty.
WA backup worked perfect with the old logicboard before flashing CM 13.
m_pa said:
There is no root, please check the screenshot below.
Since there is no root, I can't use Titanium Backup, however, it wouldn't be the most practicable way to backup your Whatsapp history every time with Titanium Backup.
Besides that, I don't think this would work if I would like to transfer my history to a new phone on which WA Backup should work as intended as I won't flash the ROM/install root and void the warranty.
WA backup worked perfect with the old logicboard before flashing CM 13.
Click to expand...
Click to collapse
Root has to be activated from developer options.
That is definitely a whatsapp problem if it worked before.
GDReaper said:
Root has to be activated from developer options.
That is definitely a whatsapp problem if it worked before.
Click to expand...
Click to collapse
Well, I haven't even unlocked the developer options until now..
Any idea how to convince WA doing it's job? Anybody with this problem before?
if you really want a backup it makes more sense that you either activate root or flash superSU yourself rather than wait on whatsapp to change their code just for you. they've already told you effectively that they aren't going to do anything for you and don't have to.
backing up the app and data with TiBu and copying the whatsapp folder achieves everything you want and has worked flawlessly for me many many times.
Well guys, got a new phone but the problem persists when trying to restore my history on the new phone and really need your help.
Got root on the old phone and saved the com.whatsapp folder of it with the key file and databases. How can I encrypt the msgstore.db to msgstore.db.crypt8?
I have tried the app Whatcrypt, which creates a msgstore.db.crypt file, as large as msgstore.db, but Whatsapp on the new phone does not recognize it as a backup file.
When using whatcrypt.com and uploading the key and msgstore.db, it tells me "Encryption failed / Incorrect account?"
Also tried Omni-Crypt app. It creates msgstore.crypt, which Whatsapp ignores as well ("searching for Backups" with waiting triangle for hours)
I don't know any other way and I'm literally stuck now
when i mentioned copying the apps folder i was thinking of the one on the root of your internal storage, not the one in Android/data/...
you can paste that onto a new phone and restore the app and data with titanium.
3mel said:
when i mentioned copying the apps folder i was thinking of the one on the root of your internal storage, not the one in Android/data/...
you can paste that onto a new phone and restore the app and data with titanium.
Click to expand...
Click to collapse
Of course I can copy the Whatsapp folder on the root of the storage but this folder only contains the wa media files of my old phone since there are no msgstore.db.cryptX files created by Whatsapp.
For TiBa I would need to root the new phone which is a S7 Edge and I would like to avoid this until the warranty has expired. It is not as easy to do repairs by yourself as the S4..
fair enough, have you tried copying both folders over and installing from playstore ? or rather, install the app but don't open it, copy over both folders and then try and see what happens...

Backing up our phones?

Any solid way to make a full backup of our phones yet? I know TWRP backups did not work at one point, and I am not sure if that was ever fixed. I want to install a custom ROM but I want a good way to make a backup so I can revert if necessary.
The way I've always done it is backup apps with Titanium Backup, create a backup file for my Nova home screen setup and upload my media (/sdcard) to GDrive via FolderSync Pro.
For switching ROMs, I just wipe and flash the zips in TWRP and go ahead and restore call logs, texts and apps from Titanium, download my stuff from GDrive and restore my home screen setup from the backup file I create with Nova.
I basically just have to reconfigure any system settings and I'm good to go.
I've heard good things about this app called Migrate on the Play Store but I'm going to stick with Titanium Backup for now as I know it works well for me. Maybe I'll give Migrate a shot one day.
That's pretty much how I do it!
Also, I never restore during the initial setup screen. I always setup device as new as I've heard there can be issues with that when switching between ROMs, especially OOS -> AOSP for example.
U must remove screen unlock before making twerp backup or else you get error when u restore. Also must be sure to select vendor_image and system_image instead of vendor and system.
Funk wizard say so https://forum.xda-developers.com/showpost.php?p=77982197&postcount=7
I always used Titanium backup as well but since I've tried Swift Backup I'm using that. It's so much quicker and more convenient. It backups apps + data, wifi Networks, call logs, Messages etc. You can even sync it with your Google drive.

Categories

Resources