I'm having an issue restoring Nandroid's in both TWRP and PhilZ. In both systems the backups fully restore, but when I reboot I no longer have the phone app. There must be something I'm not setting correctly?? New to the Note5, but have used TWRP extensively in the past on multiple phones and haven't encountered this before. As mentioned, even tried Philz recovery and same thing happened........what the hell??
re: nandroid backup
tkacer said:
I'm having an issue restoring Nandroid's in both TWRP and PhilZ. In both systems the backups fully restore, but when I reboot I no longer have the phone app. There must be something I'm not setting correctly?? New to the Note5, but have used TWRP extensively in the past on multiple phones and haven't encountered this before. As mentioned, even tried Philz recovery and same thing happened........what the hell??
Click to expand...
Click to collapse
What exact rom did you make the Nandroid backup from?
Good luck,
Happy New Years
Interesting you mentioned that - it was ForeverLoco's Breakdown. I flashed HD RLS5 and was able to backup and restore successfully, so something in that rom on my phone is borked. The only mod I flashed is one of the UI themes - perhaps I'll reflash and attempt a backup/restore without a theme to see what happens........nothing like this is mentioned in that thread, so more than likely it's user(that's me!) caused!
tkacer said:
Interesting you mentioned that - it was ForeverLoco's Breakdown. I flashed HD RLS5 and was able to backup and restore successfully, so something in that rom on my phone is borked. The only mod I flashed is one of the UI themes - perhaps I'll reflash and attempt a backup/restore without a theme to see what happens........nothing like this is mentioned in that thread, so more than likely it's user(that's me!) caused!
Click to expand...
Click to collapse
happens to me as well. i backup twice a week (rotating nandroids), test my backup via restore and the phone app is not accessible. i just flash loco's theme remove/undo zip, reboot once, confirm phone is available and then reflash the theme i want to use and all is well.
cortez.i said:
happens to me as well. i backup twice a week (rotating nandroids), test my backup via restore and the phone app is not accessible. i just flash loco's theme remove/undo zip, reboot once, confirm phone is available and then reflash the theme i want to use and all is well.
Click to expand...
Click to collapse
Good to know - thanks! Thought I was going crazy there for a little while!
Related
Hello all,
I have successfully installed CM7 on my Nexus One. However, I have the following problem with CWM: if I ask it to make a backup from within the recovery or from RomManager, CWM (3.0.0.5, latest version available apparently for Nexus One) makes the backup, but after restarting, I am stuck on the CM7 splashscreen: I see the blue Android on his skateboard and the arrow goes around in circles (left it going for 15 minutes just to be sure).
Also, on a sidenote, when I made the initial nandroid backup in CWM from my stock Froyo, after the backup was done I had to go in RomManager and "fix permissions", because all my resident apps kept crashing with "forced close" errors. No idea where that came from. Restoring that backup did the same thing as well. I did not investigate that issue any more though as I was on my way to a CM7 upgrade anyways.
So I now have a perfectly good install of CM7 running, but I am scared of doing a CWM backup. This is far from an ideal situation, and I would love to be able to resolve this
Thanks for any help
Anyone? I really am quite upset with this situation
Use this instead?
http://forum.xda-developers.com/showthread.php?t=611829
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
yannack said:
Thanks, I will try it... though I have to admit I am nervous at the idea of having to again reinstall everything. Crossing my fingers!
Click to expand...
Click to collapse
Uh oh? It is just a custom recovery, no need to reinstall everything. You only flash the recovery and do the backup you cannot now with the broken CWM. (For my phone, there are even flashable zip files so you can switch b/w CWM and AmonRA "on the fly" via flash zip from recovery, not sure there are some for N1, try to search. )
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Which is why I am nervous at the idea of trying to make such a backup.
On a sidenote, RomManager is indeed able to flash both CWM and RA recoveries for N1 directly, which is quite nice indeed.
yannack said:
Actually, the current problem I have is that after performing a backup, my phone doesn't boot anymore. The only solution I have at that point is to re-flash a complete ROM (flashing the backup doesn't work either), thus losing everything.
In short: making a backup means I then have to format and said backup is unworkable...
Click to expand...
Click to collapse
I still do not understand why all this. Just flash a working recovery from fastboot (should press power and trackball IIRC on your phone). (And obviously do not use CWM to perform backups when it bricks your phone.)
On another note, flashing removery via ROM Manager resulted in bricked phones for many users, would avoid it personally.
Hi Folks.
Ok here is my situation, I have a rooted and unlocked TF700.
I flashed Zeus 4 and all worked well, then flashed (after full wipe) PARANOIDANDROID 2.15 and again everything was great,
Yesterday I flashed Baked Bean 4 (again after a full wipe) and apart from some SD issues all seemed ok,
I then decided to restore my TWRP backup of Zeus as I needed to use my 64gig msd card.
After a full wipe and restore Zeus started up but the dpi was messed up (160) I think (way small)
I was seeing loads of FC's and file manager showed my internal SD as being empty. Rebooted to recovery and tried the "Format Data" option
It failed right away with this message "E: Unable to format data."
I have tried flashing the stock .26 rom via TWRP and I have the same issue, dpi set to 160 and internal sd not mounted.
It seems my Internal sd is corrupt
What is the procedure to reformat it via ADB or fastboot? (I have searched but the results I found relate to other devices and I dont want to simply follow instructions that might cause further harm to my TF700)
I have followed the NVflash brick proof procedure and have all relevant files backed up (I did this before flashing the last 2 roms)
Please can some one point me in the right direction
Thanks a lot
Jules
I always wipe cache, system, internal, davic and then do a factory reset.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right? What rom you have on your device right now?
Pretoriano80 said:
When you said that you tried to flash the stock .26 you meant installing not restoring a backup, right. What rom you have on your device right now?
Click to expand...
Click to collapse
Yip extracted the zip from the zip file and copied it to my ext sd and flashed it via TWRP
I have an unusable Zeus4,
Im about to try a full wipe again and then flash .26 again
EDIT
After flashing .26 and selecting reboot I get the "No OS installed! Are you sure you wish to reboot?" message
Looks like the system partition is corrupted, but i'm not sure. I think you should come here on IRC and maybe someone with more experience will help you - - http://webchat.freenode.net/?channels=asus-transformer
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
ZaJules said:
Thanks so much Pretoriano80!
With his help on IRC I was able to solve the problem,
In the end I had to return to complete stock, It seems CM10 caused some problems,
You are a a legend dude Thanks!!
:good:
Click to expand...
Click to collapse
This same thing happened to me with my Prime when I was getting ready to send it off for RMA because of a broken HDMI port. Since I was unlocked I was advised to restore to stock before sending it in. However, before I got the chance to do that I started getting the "E: Unable to format data." error that you were. I ended up erasing all partitions from fastboot and putting a note in the box that it wouldn't boot after an OTA. I managed to get away with it and wasn't charged for fixing it
For future reference it would be really helpful to know how you fixed this. Did you do something like what is in this thread: http://forum.xda-developers.com/showthread.php?t=1803343.
Did you ever figure out how CM10 messed up your Infinity? I was running CM9 on my Prime when I got this error. Thanks!
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Pretoriano80 said:
It's hard to say if it was CM10 (or any other custom rom) or TWRP to mess the things up but we managed to get back to stock by replacing the twrp with CWM recovery and installing a modified .30 update package. Was a tricky one but we didn't had to mess with the partitions and that's good.
Click to expand...
Click to collapse
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
paddycr said:
Why did you switch to CWM? Do you have any thoughts on the advantages and disadvantages of TWRP vs CWM?
Click to expand...
Click to collapse
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Pretoriano80 said:
Switched to CWM just to make sure it wasn't twrp recovery that somehow was failing to flash the partitions correctly. Tbh so far both do their job and both share the same limitation so far, meaning both fail to restore the boot partition (kernel) so in order to restore successfully (from a nandroid backup) you need to flash the right kernel after restoring is done. Otherwise i like TWRP better and never had issues with it, but i miss the advanced option from CWM, the one that let you format each partition individually.
Click to expand...
Click to collapse
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
okantomi said:
I'm not certain what you're referring to here. I've restored many times from different TWRP backups (for each custom rom that successfully boots and is half-decent, I make and keep a backup in case I want to jump around and try new things) and I've never had any issues. I am still on the .26 firmware update because I plan to do the nvflash thing. Are you saying that between Zeus v4 (ICS) and various Jelly Bean roms I've been on the same kernel? I gues I just haven't checked.
Anyway, I really love the TWRP recovery and use it with Xoom and Nexus 7 as well. It's so easy to use and always has been reliable.
Click to expand...
Click to collapse
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Pretoriano80 said:
For me moving between various roms by just restoring a backup never worked like it should. Let's say i'm on CM10 and i want to restore from a stock rom backup, the restore process is done, after reboot the device gets stuck to the first Asus screen and will stay there. Now if i get back to recovery and flash an update. zip containing the stock kernel the device will boot just fine, so definitely the boot image doesn't get restored in my case (with . 26 bootloader ).
Edit: @okantomi: You are using the internal storage or a MicroSD for backup / restoring? I'm really curious how this could work for some and not work for others, i mean same device, same recovery, same bootloader version...
Click to expand...
Click to collapse
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
okantomi said:
Ok, I only flash a new zip from the internal storage...made myself a "Flashworthy" folder which I keep stocked with newest versions of roms/gapps. I save my TWRP backups to my external microsdcard, as well as my TiBu backups. I have never had a problem restoring from TWRP this way, honestly.
Click to expand...
Click to collapse
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Pretoriano80 said:
Well, in this case i really have no clue why restoring works for some users but not for all.Dees_Troy, the dev behind Twrp recovery told me that .26 bootloader is to blame for the recovery failing to restore the boot partition, but looks like you have that bootloader version and restoring works good for you... interesting.
Click to expand...
Click to collapse
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
okantomi said:
It is a mystery. Is there any other info that might be relevant to see why the difference in results? I ask because I would like to understand this device better, as well as potentially help others.
Click to expand...
Click to collapse
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Pretoriano80 said:
I don't know, maybe the twrp version and the backup options, like if you are using compression or not, which partitions do you backup (boot, system, data, recovery, cache)...
Click to expand...
Click to collapse
I'm using TWRP 2.2.2.1, I back up boot, system and data only, and I don't use compression.
I am about to flash my 1st ROM on my S3 and I had made a nandroid of my phone a cpl months ago when it was running great, I was copying that nandroid to my PC prior to flashing the new ROM and notice it is quite small, about 21MB. Is that the complete nandroid or is it in the "blobs"? I have 3300 folders in my blobs directory consisting of 7000 files and it is 3.27GB.
Do I need to backup that blobs folder and carry it everywhere the "nandroid" backup goes?
Lastly, if I flash TWRP will it overwrite CWM and does TWRP make reliable nandroids?
Thanks
the blobs folder is indeed specific to the nandroid backup you created...if you try to restore your backup with a different blobs folder, you will be greeted with a system error. i prefer cwm 6.0.1, it works with everything for this device. oh and yea you can flash back and fourth between recoveries, one just overwrites the other.
droidstyle said:
the blobs folder is indeed specific to the nandroid backup you created...if you try to restore your backup with a different blobs folder, you will be greeted with a system error. i prefer cwm 6.0.1, it works with everything for this device. oh and yea you can flash back and fourth between recoveries, one just overwrites the other.
Click to expand...
Click to collapse
Thanks, I have 6.0.1.2, does the 6.0.1 you reference NOT have blobs?
TWRP makes perfectly fine nandroids. The blobs crap is what prevents you from moving/deleting individual nandroid backups. This is the reason I ditched CWM and only use TWRP now. When you frequently make backups, you need the ability to delete individual ones. What I did was load my stock nandroid that I wanted to keep, then flashed TWRP and made a new nandroid in that, and then flashed CWM again so i could go back to my current rom. Flashed TWRP once more and made another nandroid.
droidstyle said:
the blobs folder is indeed specific to the nandroid backup you created...if you try to restore your backup with a different blobs folder, you will be greeted with a system error. i prefer cwm 6.0.1, it works with everything for this device. oh and yea you can flash back and fourth between recoveries, one just overwrites the other.
Click to expand...
Click to collapse
apacseven said:
TWRP makes perfectly fine nandroids. The blobs crap is what prevents you from moving/deleting individual nandroid backups. This is the reason I ditched CWM and only use TWRP now. When you frequently make backups, you need the ability to delete individual ones. What I did was load my stock nandroid that I wanted to keep, then flashed TWRP and made a new nandroid in that, and then flashed CWM again so i could go back to my current rom. Flashed TWRP once more and made another nandroid.
Click to expand...
Click to collapse
Sounds like a perfect plan, I'll give it a go.
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Sent from a GlaDos Baked Potato
No I did not realize that. When I was frustrated with CWM and was looking for a way to get rid of blobs, I couldnt find any info about this. Too late I'm afraid, no turning back from TWRP for me.
Legato Bluesummers said:
You guys realize you can stop making blob backups and go back to normal tar right? Under back up go to advanced settings or whatever its called and choose the other option. Now you won't make back ups in blobs,but now you do them the old way. One folder for the whole back up, about 1-2 GB in size. Blobs are just nice as the backup takes under 5 min. Doing it the old way takes a bit longer.
Sent from a GlaDos Baked Potato
Click to expand...
Click to collapse
yes i know, but i like the blobs folder because backing up/ restoring is so much faster...its nice for bouncing back and forth between roms.
What the Blob files do is they keep copies individually of everything the nandroid backs up.... and when you go to do another backup it will read both blobs and current setup to see what, if anything is the same. Then it will only back up the differences and make reference to all the data that is the same.
And I dunno yet if I like the blob system better than the old way or not yet. Usually I only keep nandroids of the latest version of different ROMs.
Which is best for Samsung Galaxy Nexus (toro)
apacseven said:
TWRP makes perfectly fine nandroids. The blobs crap is what prevents you from moving/deleting individual nandroid backups. This is the reason I ditched CWM and only use TWRP now. When you frequently make backups, you need the ability to delete individual ones. What I did was load my stock nandroid that I wanted to keep, then flashed TWRP and made a new nandroid in that, and then flashed CWM again so i could go back to my current rom. Flashed TWRP once more and made another nandroid.
Click to expand...
Click to collapse
Use Safestrap on Droid Razr for 2+ years ,and loved it! the ability to immediately revert to Stock saved me many times while learning the ropes about roms, rooting, and flashing. I just got my hands on an old but new Samsung Galaxy Nexus (Toro). Owner installed KitKat Shiny Rom for GNex, via CWM Touch, but is now redeployed and difficult to reach UGH! So I have no way of knowing "what's next?" Rom works well, but I must say that Cm10.2 and CM10.3 were more inclusive than this AOSP version of pure Kitkat. But, is slim and sleek, and I want to get used to it, but I want to blow it up forst and start from scratch.
With my Raxr, I performed every step so I am familiar with installing TWRP and Safestrap for Razr, but have not tried it on a GNex? Can u advise if u have? Should I go from newest CMW to TWEP. The main reason I like TWRp is the ability too boot to stock if issues with Rom appear, ability to create "nandroid" backup, the ability to install several Roms on one system.
So, do ya think it's safe? Worthwhile? Thanks!
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
mercenaryhmster said:
my one s recently developed a strange issue, where if i try to run a nandroid backup, it will mostly finish, then reboot itself without fully completing the process, leaving me with a bunk backup and stuck on one rom for now. also, and the more important of my 2 concerns, is that i don't know if it will do this during a rom flash, nor do i want to find out, seeing as i have no current working backup. doe's anyone have any ideas as to how i could fix this?
Click to expand...
Click to collapse
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Darknites said:
At a guess you got a high Hboot so that means when you restore its not restoring the boot.img. You need to flash that in fastboot.
Click to expand...
Click to collapse
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
mercenaryhmster said:
nope, i have hboot 1.06, and either way that wouldn't, and shouldn't, cause a nandroid to fail during backup, nor for the phone to reboot by itself.
Click to expand...
Click to collapse
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Darknites said:
Oh if you mean you cant make a backup try a newer recovery or if its already up to date try an old one.
Edit, just to add I use TWRP 2.2.2.0 and it works fine.
Click to expand...
Click to collapse
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
mercenaryhmster said:
tried using twrp 2.3, 2.2, cwm touch, regular cwm, does it on all of them.
Click to expand...
Click to collapse
Not sure then sorry.
Do you have enough free space on your sdcard partition?
You can also try (un?)mounting /data and /system before you start the backup.
Just as an update, I solved my problem. It seems that there were some corrupted files on my data partition, and they were causing nandroid to fail and reboot randomly. So, since I was planning on wiping anyway, I wiped and set up viper again, and successfully made a nandroid after.
Hi --
Nexus 5 on Sprint.
I'm running into a boot loop issue when trying to restore a Nandroid Backup built on a fresh N5 about an hour after a clean install.
Details are:
I just this week updated from Stock KK (4.4.4 I think) to Stock LP (5.0.1) -- I've been waiting because of needing/wanting XPosed framework....
After unrooting and returning to stock recovery on KK 4.4.4,
I did the LP OTA followed by a Full Erase after the OTA to start fresh. (Note: I have subsequently experienced the same exact problem after installing the LP using the flash-all.bat from the Nexus 5 image extracted to the SDK/platform-tools folder.)
After completing the login and google's restore process perfectly... All things LP appear to be working well and my phone is set up the way I want. So...
I then installed CWM recovery 6.0.4.5 using fastboot.
I then used the CWM recovery to root with SuperSU v2.40
I then used CWM recovery to make a Nandroid backup... (after completing a rooted power up and returning to the recovery)
Long story short (kind of), within the first several hours I messed something up (install of Nine email app AFTER the Nandroid didn't work and was leading to android.process.acore stopping issues. Nine has since told me that the app is not compatible with my company's MDM security solution Maas36). So , I wanted to return to the Nandroid point in time and just put my company exchange email into GMAIL - Acore issues continued after removing Nine.-- but were NOT happening at the time point where I created the backup. So I booted into CWM Recovery and selected to restore and picked the backup I had made of the fresh device.
Restore via CWM recovery proceeds fine and completes. However, it goes into the flying circles boot loop (I tried leaving it go for upwards of 2.5 hours at the longest time
I can easily recover from this with a flash-all.bat in fastboot
I have done this numerous times today and it is completely repeatable. Same thing happens each time.
I have definitely restored from Nandroid previously using this process on KK. But so far no Nandroid restore possible for me on LP. To be clear, the LP install works fine, but just can't be recovered from the Nandroid backup. I guess I'm OK with that, but I'd rather not fly without a backup safety net.
Hopefully that's enough detail for someone to comment. If I've missed any helpful details, let me know.
So, have I done anything wrong? The only thing I can think of at this second is possibly needing to unroot before attempting the restore? Is that it? I don't think I've done that before.
Thanks in advance for any help that anyone can provide.
greenawayj
One quick addition. I figured someone would suggest using TWRP instead of CWM, so I'm going through that process now. I'll update the post if I find different results. I'm also making my TWRP first backup pre-root just in case that matters...