This is insane. I never had issues with my backups back in the clockwork mod days.
But with both my old note 2 and this moto z, TWRP backups always have issues when restored.
I just got through flashing to stock, letting it update all the way to 7.0 and latest patches.
Then fastboot boot twrp.img to get into twrp and made a complete backup. I even checked the system image option to have that just in case.
Now comes time to restore and it doesn't work. It goes through the motions of restoring and says it was successful, but it didn't actually restore everything. My rom is still rooted, still broken, and after several attempts it wont even boot.
Why do they even put in a backup option if it isn't even a bit-by-bit backup that works? There is no such thing as nandroid in twrp as it isn't making any kind of nand dump.
I guess we are just not to expect to have valid backups? So useless.
xamindar said:
This is insane. I never had issues with my backups back in the clockwork mod days.
But with both my old note 2 and this moto z, TWRP backups always have issues when restored.
I just got through flashing to stock, letting it update all the way to 7.0 and latest patches.
Then fastboot boot twrp.img to get into twrp and made a complete backup. I even checked the system image option to have that just in case.
Now comes time to restore and it doesn't work. It goes through the motions of restoring and says it was successful, but it didn't actually restore everything. My rom is still rooted, still broken, and after several attempts it wont even boot.
Why do they even put in a backup option if it isn't even a bit-by-bit backup that works? There is no such thing as nandroid in twrp as it isn't making any kind of nand dump.
I guess we are just not to expect to have valid backups? So useless.
Click to expand...
Click to collapse
I believe that it has to do with the encryption. The stock room encrypts the /data partition.
lollyjay said:
I believe that it has to do with the encryption. The stock room encrypts the /data partition.
Click to expand...
Click to collapse
Reading up on system image it was my understanding that it backed up everything in one huge chunk to work with encryption. But apparently even that doesn't work.
So am I screwed now? Looks like the only roms I can use are custom roms. I have tried flashing a few different stock nougats but they all get errors about security downgrade from fastboot.
I don't understand why they make it so once you upgrade, it blocks downgrading. Sounds like something Apple would do.
xamindar said:
Reading up on system image it was my understanding that it backed up everything in one huge chunk to work with encryption. But apparently even that doesn't work.
So am I screwed now? Looks like the only roms I can use are custom roms. I have tried flashing a few different stock nougats but they all get errors about security downgrade from fastboot.
I don't understand why they make it so once you upgrade, it blocks downgrading. Sounds like something Apple would do.
Click to expand...
Click to collapse
Try here for nougat stock ROM
https://mirrors.lolinet.com/firmware/moto/griffin/official/
Related
I cannot for the life of me coax my Rezound into creating a nandroid backup. I kind of a n00b, so I'll give you my info and how I rooted.
ROOT
I rooted by following Scotty's noob friendly root guide: http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html
I followed his instructions for "temporary recovery" which installed Amon RA 3.14
MY CURRENT SOFTWARE
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
FIRST ATTEMPT
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were.
I selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection.
It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
SECOND ATTEMPT
I installed ROM Manager.
I selected "Flash ClockworkMod Recovery" ... not realizing exactly what I was doing. None the less ...
I booted into CWM.
CWM freezes while making a nandroid backup. Every time. Battery pull. Every time.
THIRD ATTEMPT
I followed Scotty's "temporary recovery" instructions to install Anon RA 3.15 (different version this time)
The md5 in the command window did not match the md5 at download site (http://forum.xda-developers.com/showthread.php?p=23781936)
Seeing no alternatives, I flashed it anyway ... Nothing catastrophic happened.
Did same thing I did in the first attempt, and it gave me the same message.
Anyone have any other ideas?
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
You realize that after the OTA your backup won't work right? If you're just trying to cover yourself between now and then, maybe just copy your whole system and data partitions manually??
bloodymurderlive said:
Well, the reason was that I didn't want to lose the ability to receive OTA updates. This is why Scotty provided instructions for both the temporary flash, which allows OTA updates, and the permanent flash, which breaks OTA updates.
Does it matter, as far as nand backups are concerned?
Click to expand...
Click to collapse
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
I don't understad why I can't enjoy these things and create a nandroid backup of my current ROM in case I decide to try other ROMs.
Are you saying that a permanent recovery is the difference between it working and not working?
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
bloodymurderlive said:
Ok, maybe someone can just answer that last question for me:
Are you saying that a permanent recovery is the difference between it working and not working?
Click to expand...
Click to collapse
I can't say for certain because I've never gone through that situation before, but if you want to be stock...Why not just let the OTA update you to ICS stock and keep it as it is? Do you really like Gingerbread Stock that much? I guess I just don't understand your reasoning behind all of this. If you were flashing a new ROM after wiping everything in a recovery I would understand your need to nandroid...
---------- Post added at 12:19 PM ---------- Previous post was at 12:13 PM ----------
bloodymurderlive said:
MrSmith
Couldn't I flash Amon RA after OTA (rooted, of course), and then restore the nandroid? I thought nand backups work independently of whatever ROM you're running ...
uToTMeH8
But I want to keep my current stock ROM backed up, not just my apps and data. And why not flash a temporary to make nandroid backups?
Maybe I need to explain better ...
I want to be rooted.
I like Sense.
I like that OTA updates are automatically pushed to my phone.
Click to expand...
Click to collapse
The firmware that is updated with an OTA update will most likely break Gingerbread compatibility if you try to restore a temporary nandroid backup.
With S-Off none of this would be a problem because we would just flash old radios and kernels right from recovery. HTC makes it difficult to downgrade
uToTMeH8
I want to have the option to return to whatever ROM I want.
If I OTA-update to ICS, I want the option to return to GB (especially given how notoriously buggy OTAs are).
If I install a custom ROM, I want the option to return to stock if I don't like it.
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
bloodymurderlive said:
So you're saying that I can't just backup any ROM and switch between them at will? That kinda sucks ...
I might just try a permanent recovery anyway, it seems to be the only thing anyone can think of to try to get Amon RA nandroid working ...
Click to expand...
Click to collapse
This is why everyone is going mental about s-off in this thread:
http://forum.xda-developers.com/showthread.php?t=1578449
Honestly unlocking your bootloader, flashing Amon-Ra and backing up your stock is the way to go. I've had my phone unlocked for 3 months with no problems and the devs on this site are amazing! You're going to want to try every gingerbread ROM once you get really good at backups and flashing. I was getting around 6-8 hours on the stock ROM for battery life. I flashed NilsP's Business Ginger Sense and I hit 30 hours. It's ridiculous how much better battery life is after stripping the ROM down and adding tweaks.
This Toolkit really makes it very easy...Good Luck!
http://forum.xda-developers.com/showthread.php?t=1504824
The error is commonly not enuff space on the SD,or insufficient battery charge.
It has nothing to do with leaving the stock recovery in place.
The only reason you won't be able to restore your gb backup after ics is the fact that it takes a different hboot and.radio,and until the s off method is released,there is no way to revert those. With htcdev,you can only go fwd,not back.
MrSmith317 said:
Why are you using temporary recovery? Why not just flash AmonRa "fastboot flash recovery <whatever_your_amonra_image_file.img>" ? It works perfectly fine as the recovery partition for almost everyone else.
Click to expand...
Click to collapse
uToTMeH8 said:
Why would you even want to flash a temporary to make nandroid backups? If you are getting the OTA then your best bet would be to backup everything with MyBackup, then copy and paste it from your sdcard to computer.
Click to expand...
Click to collapse
the reason for leaving the stock recovery is simple: a custom recovery will not install an OTA.
if you leave the stock recovery in place,the OTA will happen,quite naturally,and without isrupting your personal data. sure,it will break root,and anything youve frozen will pop back up,so you do have the minor inconvenience of re-freezing some bloat,and re-launching the temp recovery to flash root files. not a big deal,IMO. remember,htcdev is more like s-off in that you will always be able to root,or re-root. its not an exploit that will disapear.
even if a person wishes to permanently install a recovery,i strongly recomend to get into the habit of launching recovery from fastboot when messing with your phone. as we know,htcdev only unlocks boot,recovery,and system,and we cannot write 'boot' from 'recovery'.
however,launching recovery from fastboot(what ive been calling a 'temporary' recovery) does allow recovery to write to boot. it doesnt do much good(yet) for flashing,as rom devs are still not including the neccessary scripts to install the kernel,but it does allow you to restore nandroids without a seperate kernel flash,making them quicker and easier.
until you switch to ICS firmware(i.e.,install the leaked ruu,or take an OTA) you can flash,backup,and restore any gingerbread roms,and GB firmware based ICS roms,as you desire.
again,what the guys were trying to say when the said you cant restore the GB backups after ICS is simply because the hboot and radio are different. sure,you can physically power up your recovery and restore a GB backup with ICS hboot and radio(firmware),and it will restore,and even boot. you will just have issues due to the incompatible firmware,such as the disapearance of your SD card
hope that helps clear a few things up for you. sorry the above reply was short,i was trying to reply on my phone at work
edit:
one last thing: since youve downlooaded rom manager and used it to flash clockwork recovery,you now have a permanently installed clockwork recovery. you can still temp launch amon with cw in place,but you now are missing the stock recovery,and as such will not be recieving OTAs. if this is important to you,you need to download the stock recovery,and permanently install it(fastboot flash recovery recoveryname.img)
http://www.mediafire.com/?wb21d2gdurui2c6
Thanks Scotty!
First, I'm a complete moron and assumed that my 32GB microSD had enough space. I deleted a movie and made my backup.
One question though about the CWM recovery ... I was concerned that it was permanently installed. However, I attempted to boot into recovery from my phone (power + volume down), and it booted into what looked like the stock recovery ... No dark Amon or CWM recoveries ... Is it possible that CWM didn't permanently flash after all? I know that I have been in both Amon and CWM, and CWM was installed from within the ROM Manager app ...
Are you sure you were in recovery, because power and volume down boots to the bootloader, called boot, which is entirely different.
Sent from my ADR6425LVW using xda premium
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
bloodymurderlive said:
Yup, you're right ... I even experienced the won't-charge-or-boot-if-battery-is-low issue with CWM. Fortunately, my wife has the Thunderbolt which was able to charge my battery for me.
So ... Even though I can't receive OTA updates, I can still manually install them, right?
Click to expand...
Click to collapse
Yes, Once and OTA is released it should not be long till someone posts here the zip install of the same OTA. Give it another day and I say you will see a cleaned up debloated, rooted etc... zip of the same OTA. These days there is really no need to rush for the OTA downloads, let the Dev's do their magic and offer you something better than Big Red will offer.
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
undegaard said:
Hello, I need some help with restoring via CWM on the Galaxy S3.
On the S2 I pretty much always used CM9 and jumped back and forth between versions and backing up/ restoring was never an issue.
Now however I am using the stock ROM and its rooted of course.
I made a back up of my stock rom 'cause I wanted to try and install some stuff.
I tried installing the jelly bean transition effects but the install failed, the device felt kinda sluggish (maybe my imagination) afterwards so I decided to restore my phone. The restoring went good but the last ting that happens is that CWM says that restoring /Data failed.
I reboot my phone and I come to the first start up screen where I get to choose language and so on. Everything but photos has been deleted. I try to install CM9, and I do that without any issues. Then I trie to backup my stock backup but I get the same error message and I get back to stock setup page.
My backup is a staggering 6GB, and I read somewhere that CWM can only restore 2GB?
I've deleted that backup and done another one but that is also 6GB.
Does anyone know how to restore from that first restore or how to make future restores work?
Click to expand...
Click to collapse
I had this problem with my sisters Xperia X8,couldn't restore anything that i backed up.It goes for a while and stops.But she had bootloader locked.I was shore that i unlocked her bootloader but i didn't,so i unlocked bootloader,and tried to backup and restore and it worked fine.
I'm not 100% and i don't know is that the way CWM works,but i think in order to restore your data,that you backed up,you have to unlock your bootloader.But it's the best to wait someone who knows this for 100% sure.
If you haven't unlocked bootloader try that,or you don't won't to lose your warranty!?
Good luck!
I don't think that CWM has size limitation but i can be wrong.
Have you made sure that your CWM is up-to-date? if in doubt flash the latest CF-root.
was there ever a resolution to this problem? I did the same thing, rooted the galaxy s 3 and unlock the bootloader. Get a backup of my stock set up using clockwork recovery mod. Now when I try to restore, it does not restore the data. All of my apps look like they are there, but none of them are really installed. I think I can just reinstall all of the apps by hand, I would like to know how to get over this.
Searched, but found nothing specifically related to this. I was on CM10 and flashed back to stock until they get the bugs worked out. Flashed back to stock via Odin with Samsung toolkit v. 2.1. I had backups for TB so I decided to restore missing apps with data and system data, however whenever I did, the device would get stuck at the samsung logo. I suppose this is due to conflicting system files, so the device doesnt know what to boot from, but how can i avoid this in the future? I thought TB was the ultimate answer when switching roms to transfer data, this is the first time I've had trouble with boot issues with TB.
emoandy said:
Searched, but found nothing specifically related to this. I was on CM10 and flashed back to stock until they get the bugs worked out. Flashed back to stock via Odin with Samsung toolkit v. 2.1. I had backups for TB so I decided to restore missing apps with data and system data, however whenever I did, the device would get stuck at the samsung logo. I suppose this is due to conflicting system files, so the device doesnt know what to boot from, but how can i avoid this in the future? I thought TB was the ultimate answer when switching roms to transfer data, this is the first time I've had trouble with boot issues with TB.
Click to expand...
Click to collapse
You're getting boot loops from restoring system data, thats a big no, no. Missing apps and data, I usually dont have any problems with that. The only "ultimate" is do a nandroid backup in CWM
True, but nandroid replaces system so it wouldn't be best when switching roms, correct?
So, my OnePlus 7t Pro McLaren (HD1913) has stucked in bootloop. I want to access my files but the device is encrypted. I tried unofficial TWRP but it doesn't support decryption. I also tried adb backup in stock recovery and also in TWRP, but ofcourse, no luck. Is there any way to access my files?
It's very secure... especially now.
Your only hope is to break the boot loop and get the current OS load to boot up.
Thank you for the fast reply!
blackhawk said:
It's very secure... especially now.
Your only hope is to break the boot loop and get the current OS load to boot up.
Click to expand...
Click to collapse
The problem about that is that I don't have the right boot.img which is from the latest 11.0.3.1HD01BA, all I could find is the previous 11.0.2.1HD01BA. Maybe you can help me with that? I was thinking about asking that in a separate thread, but it didn't seem like a good idea. I suppose that it will be available somewhere on xda in the coming weeks but in that case, I would rather flash the previous stock ROM even if I would lose my files.
momir64 said:
Thank you for the fast reply!
The problem about that is that I don't have the right boot.img which is from the latest 11.0.3.1HD01BA, all I could find is the previous 11.0.2.1HD01BA. Maybe you can help me with that? I was thinking about asking that in a separate thread, but it didn't seem like a good idea. I suppose that it will be available somewhere on xda in the coming weeks but in that case, I would rather flash the previous stock ROM event if I would lose my files.
Click to expand...
Click to collapse
You better tread very carefully here. How and where is the encryption stored? I would think your safest course of action be to find exactly what boot looped it and correct it by editing, line by line.
It's likely a 3rd party app that boot looped it.
Launchers and power management apps are likely candidates.
You're already way beyond my skillset. I run stock unencrypted devices in part because of disasters like this.
For all you know it could be a hardware failure or malware induced corruption. Those encryption keys are your only hope... if they are still intact and accessible.
Always redundantly backup critical data and NEVER encrypt backup drives. Do not clone copy media ie music files, cut/paste etc only.
Ok, I got lucky this time.
I have totally forgotten about Oxygen Updater app which is apparently great when it comes to keeping it up to date, so I downloaded the latest stock ROM with it, flashed boot.img, and bang, it booted perfectly! It took some time to download tho, but in the end, everything is great!
Hi guys!
I somehow messed up my system with LSPosed in Gravitybox. A conflict made my phone unworkable (screen just kept flashing). No worries since I kept a Nandroid. After just putting this back (I ticked literally ALL the boxes) my phone goes trhough the OnePlus-loader (dot turning into square) and then says only "turning off" in the screen. Nothing else works. So I can only re-access the device via PC-Terminal in TWRP.
Fact is... Nandroid was taken BEFORE LSPosed was installed, Nandroid gave no errors when taking and gave no errors when "putting back". But device just kind of softbricks AFTER boot. Very strange. Any ideas?
Could it have to do with DM-Verity?
Just wondering: did anyone actually MAKE a NANDroid (ticket all the boxes) and tried to put it back? Questions:
- when putting it back: do I need all the boxes ticked, or just a few?
- when making a NANDroid - do I need to disable PIN, fingerprints etc.? Or can it stay active?
- did anyone succeed so far? - I am wondering why mine doesn't work?
Please share your experiences!
Can confirm neither my Nandroid backups are working.
Dunno if any security pin or measure needs to be disabled first, but it shouldn't.
So far, the most safe way I've found to make a full device backup, is through adb:
While booted in TWRP use the adb commands:
Bash:
adb shell
ls -la $(find /dev/block/platform -type d -name by-name)
to list all partitions.Then you can use
Bash:
mkdir /sdcard/PartitionsBackup
dd if=/dev/block/sdc"partition number" of=/sdcard/PartitionsBackup/"partition name".img
to backup every partition in your internal storage.To flash them back you can use fastboot:
Bash:
fastboot flash "partition name" "partition name".img
# Example
fastboot flash boot boot.img
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Can anyone help me in overcoming that kind of a problem .?
I've tried recovering with TWRP, I suspect the problem there is encryption, because when I factory reset the data, I can start fresh.
If you just want to have a working phone, try doing a restore and factory reset (also try reformatting the data partition if a factory reset does not work).
Just let us know if this worked for you.
exis_tenz said:
Wow, that's is almost out of league for me :-(
Anyone can help fix this? How is everyone doing?
Click to expand...
Click to collapse
I've created a Tool that could help, if you're still able to backup the original working firmware.
Anyway, I personally suggest to go with multiple type of backups (TitaniumBackup + Nandroid + PartitionsBackupper) first.
And when it's time to restore, wipe everything with the stock recovery and start fresh. Restoring the userdata partition for last, checking if everything works before flashing it.
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Raygen said:
If you backup everything before hand (IMEI partitions included), you can pretty much wipe anything without worries (by personal experience at least).
To revert back to stock you can easely flash the stock boot and stock recovery partitions via fastboot.
Or, in case you just want to backup them, just download them directly without need to touch the phone.
Click to expand...
Click to collapse
As i always say: Dont flash around without backups
exis_tenz said:
Awesome. After my 4th (!) factory flash comming Friday at a OnePlus service center I will try!
I am now rooted with TWRP, A12 Version (EU). Is there a simple way to return to stock recovery? Or can I do the entire wiping in TWRP? I was warned not to wipe partition / files with IMEI.
Click to expand...
Click to collapse
4th factory flash???? I think u shouldnt flash somerhing anymore
Well, when I started with this phone, I made a NANDroid of stock rom, just plain, rooted. During the adventure setting it up, I kept making NANDroids.
Then when I was done (phone in use for 2 days) I installed LSPosed and Gravitybox. WARNING: if you mod the clock position in Gravitybox to middle: your phone will not work anymore (some framework error I guess). Then I decides to put back a 2 hours before made NANDroid back... Which got no errors when making and none when putting back... But the phone bootlooped. Actually it started through the loader, started Android and then only showed "switching off" in the screen. Which it didn't.
Then I needed a factory flash. The first factory flash gave me a "serial nummer incorrect", the second one a battery drain (no sim, wifi and bluetooth off, lost 50 percent battery in 9 hours without finding out what caused it). The next factory flash worked without the serialnumber error but also gave the battery drain AND did not let me enter a pinlock neither a fingerprint.
So tomorrow we'll try again.
What I noticed that even when a factoryflash @oneplus servicepoint was done... Some data survived (!) in the phone (which shouldn't). I still had a TWRP-folder there so I guess it's like more junk just survices. That probably causes all the trouble.
It's time OnePlus releases the firmware!
I've been in the same situation (even twice ) For me just deleting the Gravitybox.apk from system folders did the job.