Having recently switched from Spring to Verizon, I'm finding a few differences. On my Sprint E4GT S2, I accomplished root using a cwm recovery. I guess the locked bootloader is the problem.
SafeStrap looks to provide all the same functionality with a better interface. Although I've created 2 backups (still a nandroid?) via SS, I have yet to restore one. With cwm, it was basically like backing up/restoring a system image that would restore the phone to the state it was in at the time of the backup.
So I guess the question would be:
Are the backups and restores basically the same as cwm?
Thanks,
Sam
Sam Sung said:
Having recently switched from Spring to Verizon, I'm finding a few differences. On my Sprint E4GT S2, I accomplished root using a cwm recovery. I guess the locked bootloader is the problem.
SafeStrap looks to provide all the same functionality with a better interface. Although I've created 2 backups (still a nandroid?) via SS, I have yet to restore one. With cwm, it was basically like backing up/restoring a system image that would restore the phone to the state it was in at the time of the backup.
So I guess the question would be:
Are the backups and restores basically the same as cwm?
Thanks,
Sam
Click to expand...
Click to collapse
Yes
I dont believe it counts as a nandroid cause its in SS, but I could be wrong.
Related
Now, I haven't cared too much about Nandroid backups since nothing is too important for me to save, and I'm running a different ROM almost every day... But what do Nandroid backups backup ? Just the ROM? ROM and data + Kernel ? And If I do a full wipe and I have a Nandroid backup, do I have to Flash the ROM first, then flash the Nandroid over it? Or can I just full wipe and flash the nandroid?
Nandroid isn't something I use a lot (or at all), so this is kinda odd to me.
A nandroid backup is essentially an image of your entire phone. The entire OS, phonebook, messages, settings...everything.
Awesome, so I can just flash the nandroid right after a full wipe, correct?
Yep, absolutely. Just don't forget that only CWM 3.0.0.6 can flash and restore anything. The other versions are limited to Froyo or Gingerbread, not both.
Yeah I know, I flashed 3.0.0.6 the second i saw it did both ROMs, I haven't had a problem since ^_^ But thanks !
+2 to your Thanks Meter
Glad you got it worked out.
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
wiredwrx said:
I am on stock, but rooted, nexus 7 4.2.2. I got notification of the software update sometime last week. I decided I would update. First, of course, I made a full nandoid backup, and titannium backup of all my apps and data. I downloaded rootkeeper and using rootkeeper "unrooted" and set about updating.
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
How can I update? What are your thoughts on the update? If I should avoid updating, how can I get rid of the software upgrade nag?
Click to expand...
Click to collapse
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
RMarkwald said:
You would need stock Android recovery for it to work I believe, so if you have a custom recovery, that is why it failed.
Click to expand...
Click to collapse
Thanks. I will look into that. Any thoughts on the update?
wiredwrx said:
Thanks. I will look into that. Any thoughts on the update?
Click to expand...
Click to collapse
You'd have to get stock Android recovery on there somehow, but if you're doing the official update and you removed any /system/app apps with Titanium Backup or anything, it'll also fail. If you flashed a custom kernel, it'll fail as well. Official updates run system checks to see that the stock files are all there and the correct versions.
You could backup everything you want to save on internal sd card (pictures/music etc), and flash the official factory Google images via fastboot. Or flash custom recovery and flash a 4.2.2 ROM. Either way, you'll have to wipe everything so you'll loose apps and app data, which you'll have to re-install again.
wiredwrx said:
The Nexus rebooted, and entered the custom recovery mode (I think it is Amon RA) and then the update failed.
Click to expand...
Click to collapse
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
bftb0 said:
The reason it failed is given in the recovery log file located at /cache/recovery/recovery.log
In general, OTAs are meant for 100% stock devices. When someone attempts an OTA on a rooted device, it can fail for hundreds of independent reasons - usually files in /system that got altered or removed by various root-privileged apps. (Sometimes it is not apparent to the end user that their root-using apps have even made such changes). In the current JOP40D -> JDQ39 OTA, the boot partition is also checked, so the OTA will certainly fail if you are using a custom kernel (in addition to any issues with modified files in /system).
Sounds like you are a person who makes Nandroid backups; good for you. If you have a Nandroid backup taken immediately after rooting (before any of these changes took place), it is possible that you could replace the altered files (by pulling the unaltered versions out of the old Nandroid Backups). Unfortunately, it is hard to know how much work this will be**, because during the initial check sequence that the OTA performs, it halts on the first error encountered. There could be only a single altered file causing trouble, several, or many.
** If you use TWRP recovery, the system (& data) image backups are tar files - you don't even need to restore an old backup to retrieve files from other backups.
As you mentioned TiBu, it sounds like your are farmiliar with all this stuff already. Rather than hand-patching your existing ROM, perhaps the right thing to do is to
- Make your TiBu & Nandroid Backups of your current ROM
- Install 4.2.2 factory image & Re-Root
- Make a Nandroid Backup of this (vanilla stock) ROM before you even boot it
- Boot it and restore your Market Apps. (I'm not a big fan of restoring System Apps or their data).
good luck
Click to expand...
Click to collapse
Thanks for the detailed breakdown. I may just update with your instructions. Are you aware of a way to suppress the nag screen.
I have a n900w8 running cm11. I need to go back to stock.
I have a nandroid of my stock rom and was wondering if i can go back using my backup or if i need to use odin to downgrade?
Just want to make sure there are no issues with bootloaders etc if i restore my backup.
Thanks
Well as technically Nandroid backups are just a clone of your previous OS you should be able to flash it just fine, BUT you should not. Cause in doing that you will face several problems, multiple apps force closing would be one of them. So yes, just wipe the phone first, I mean a complete wipe, then flash a stock ROM of your choice via Odin, root, then restore apps with their data manually using Titanium. I mean the option in Titanium which says install the missing apks only, just hit on that, not the whole system wide restore, cause that will create problem too.
I don't know what model is that though, I have a N9005, so what I said might not even be applicable for your model.
Dyno-droid said:
I have a n900w8 running cm11. I need to go back to stock.
I have a nandroid of my stock rom and was wondering if i can go back using my backup or if i need to use odin to downgrade?
Just want to make sure there are no issues with bootloaders etc if i restore my backup.
Thanks
Click to expand...
Click to collapse
Better to flash the latest stock firmware for your device via Odin.
and restore app(s) later.
rooted and rommed a friend's note 3 to jasmine, and before we did it we upgraded titanium backup to the pro edition via marketplace, without realizing that it had deleted all three backups that were all in separate locations, one in the default location, one on the SD card and one in the phone's internal storage.
before I did anything to the phone rom wise I made a nandroid backup via twrp and I cannot boot it into an emulator successfully AND get the texts from it through installing titanium backup, creating a backup and copying it off, didn't work out.
so now what I need is a way to load up a nandroid backup without corrupting the backup. every time I try to restore the backup into the phone it bootloops, only thing I can think of that would interfere with it is the kernals, NC2/4. jasmine is currently running on NC2 and the stock firmware with the texts on it uses NC4, when I tried reflashing NC4 to the device after reintalling the backup it bootlooped, and vice versa with NC2.
thoughts/suggestions? sol on the texts?
thanks.
Never tried this but worth a shot. https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore
Sent from my SM-N900V using Tapatalk
I'll give it a go.
followed the steps found at: http://forum.xda-developers.com/nexus-s/general/extract-restore-sms-mms-contacts-call-t1370349
and had no success, doing the same via root explorer and nandroid manager to get the original files from the backup, nothing was restored.
I'm assuming that they're just gone after that?
rom manager text restore found nothing, quite a few were backed up though so who knows. not a good thing to lose them all.
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Splice_9 said:
I recently rooted my Moto G5 plus and would like to check out a a few custom ROMs. However, from reading the instructions on a few custom ROM threads it isn't clear to me what to backup in TWRP to be able to recover or go back to the stock ROM if I want to later.
I've read that I should backup Data, logo, and boot, and internal storage, plus all apps and data with Titanium Backup, but what about System, System Image, Recovery, OEM, and EFS? What about persist?
Can someone give me a quick summary of what I need to backup to go back to my current state if I want to experiment with some other ROMs?
Thanks.
Click to expand...
Click to collapse
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
I backed up all 53 partitions and stored in my harddisk. It's less than 5GB.
I left out only the data partition because for that I use Titanium Backup and RSync.
Yet I haven't backed up the partition table, also this is important...
NZedPred said:
Back up everything available in TWRP, including efs and persist. Then store it all on the cloud. You can never have too much backed up.
Too many people have screwed their devices in this forum by not backing up persist and then applying bad modifications. It is unique to your device and you can't use someone else's to guarantee full functionality.
Click to expand...
Click to collapse
if i backup my efs and persist in a custom rom 64 bits that backup won't work in stock right? it is intact
Backup everything... although it may be too late already, but any working backup is better than nothing.
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
nicolap8 said:
Yet I haven't backed up the partition table, also this is important...
Click to expand...
Click to collapse
acejavelin said:
What you should REALLY do is unlock the bootloader, then before you do anything at all one-time boot TWRP, NOT install it, and backup everything and move it off the device and to the cloud. Once you have rooted or modified your device, even installing TWRP, you are not getting a clean backup.
Click to expand...
Click to collapse
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
prokaryotic cell said:
Have anyone backed up and successfully restored a full partition backup before? I mean running dd if=/dev/block/mmcblk0p* of=/sdcard/*.img for all partitions before installing TWRP. Would restoring it later (after flashing roms and such) return your phone to 100% stock state, being able to re-lock BL, take updates and everything?
Click to expand...
Click to collapse
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
acejavelin said:
No... there are some things you cannot write to, period, but the OS can (has to do with encrypted files/partitions I believe), bootloader unlock is one of these things. Many of the mmcblk0 partitions cannot be written to, you can really one write to about 8 or 10 of them via software without having an external writer (for the life of me I can't remember what it's called).
Click to expand...
Click to collapse
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device. There's also all the issues people keep getting in this forum - such as losing their IMEI, 4G, VoLTE - can be those be avoided (and even fixed) by restoring the right backed up mmcblk0 partitions?
Click to expand...
Click to collapse
Yes, you can restore your efi folder to correct this most of the time, if you have a clean backup. Otherwise you need to get it JTAG programmed
prokaryotic cell said:
I see. Wasn't expecting to be able to return the bootloader status to untampered, but what matters most is being able to return to a fully working stock rom and take OTAs without bricking the device.
Click to expand...
Click to collapse
Just to clarify that you understand, you can't return your bootloader status to untampered but you can lock it again. However it really isn't necessary to do that just to get OTAs. All you need to do is return to your stock with stock recovery and no-root (fastboot method not TWRP flashable.) OTAs work fine once you have done so. I have restored a TWRP backup just by booting into TWRP but it seems like I had some issue unrelated to OTA, although I don't recall what they were and is was on my previous phone (Moto G4).