Database Info

[Q] Problems with Nandroid advanced restore

I actually have two questions here.
I'm trying to do an advance restore of the data from a previous backup using CWM. recovery 5.0.2.7 and having some problems.
In recovery, when I click on 'advanced restore' I am told there are no files. I then choose the regular 'restore' option and it shows the files to choose from.
I can then go back one screen and select 'advanced restore' again and it will now display the list of backups. When I select a backup and try to restore the data, I get a MD5 mismatch error. This happens when I try to do an advanced restore with any of my backups, not just a certain one. Also, I can do a normal restore without any problems.
I tried this:
http://www.geekdevs.com/2011/10/solved-md5-mismatch-error-on-clockworkmod/
Then this:
http://forum.xda-developers.com/showthread.php?t=1606047
I've read several threads but most of them seem to be solved after trying one of the above methods. I also haven't seen any that describe the backup list not displaying at first.
Secondly, I found this problem because I'm running Pyr'o'Ice ICS Desensed 1.1.3 and stupidly tried to tether with wifi and my phone got stuck in a reboot loop. I want to restore the userdata via Nandroid recovery, but will that also restore the tether setting that causes that bug?
My main issue is with the Nandroid recovery, but I thought someone reading this might also know the answer to that question also.
Any help is greatly appreciated.

Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again

This doesn't appear to do anything
xmc wildchild22 said:
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
Click to expand...
Click to collapse
I'm having exactly the same problem as the OP, and I'm not sure how this will help as all md5sum does is give the md5s listed in the nandroid.md5 file. Using this method, all one is doing is putting the exact same md5s over what is there in the nandroid.md5 file.
I really need a method to make the Nandroid Advance Restore work in order to get back my data after updating to 1.63.531.2.
Any other suggestions? --
--
KingCheetah

y do u guys need to advanced restore...just restore

xmc wildchild22 said:
y do u guys need to advanced restore...just restore
Click to expand...
Click to collapse
Heh, well, in my case, I'm trying not to have to restore my phone from scratch after updating to 1.63.531.2, as well as keep the update. A straight restore will just take me back to DS Mod 1.55.531.3. Advanced Restore would allow restoration of data without overwriting the boot.img, system, etc.
So, no further methods to try to address this error?
--
KingCheetah

then take the system.img from the 1.63 update and put in replace of the nandroids one....then redo the md5 checksum for the system.img like i had showed before

xmc wildchild22 said:
Edit: (didn't read whole post)
1. Open your sdcard on pc (usb mounted)
2. ensure there is a folder in clockworkmod/backup (ex: 2011-08-10.02.40.28)
if your sure the nandroid isn't corrupted and you want to restore it anyway, you can modify the md5sum.
1. go get a md5sum checker
2.With your phone mounted on your pc...go into the clockworkmod/backups/(yourbackups folder)
3. md5 sum all the images in there (write it down somewhere)
4. open the nandroid.md5 with a text editor
5. replace the md5s with the ones you wrote down
6. Try restoring it again
Click to expand...
Click to collapse
The md5s are already the same.
That also doesn't address the issue why I am told that there are no files found when I try the advanced restore option without first going to the regular restore and backing out.

Investigation ongoing, but an idea to help
paperskye said:
The md5s are already the same.
That also doesn't address the issue why I am told that there are no files found when I try the advanced restore option without first going to the regular restore and backing out.
Click to expand...
Click to collapse
This may have something to do with the way in which CWM 5.0.2.7 saves the majority of data to tar files instead of img files. This behavior of CWM is part of the discussion in this thread: http://forum.xda-developers.com/showthread.php?t=1624516
Yogi2010 made the suggestion of using the Modaco 4.0.0.9 recovery for backups that can be successfully used with Advanced Restore. I believe Modaco's AR works because it saves all data to img files.
I'm going to attempt an update to 1.63 using Modaco for backup and then AR of data afterward. If successful, we know that Modaco is the key for utilizing AR due to the file type it uses for data storage.
Why CWM 5.0.2.7 behaves as it does regarding AR remains an open question.
I'll report back to this thread with results after my update attempt --
--
KingCheetah

Modaco functional with Advanced Restore
I used the Modaco 4.0.0.9 recovery for my backup prior to updating to 1.63, then followed with an Advanced Restore of data afterward, which successfully restored my phone environment. So AR is functional with Modaco, but not CWM 5.0.2.7. I don't know for certain if the fact that CWM uses tar files has something to do with its inability to execute AR, but it certainly seems like this is a contributing factor.
I'm going to Google this and see if I can come up with any further info on CWM that might explain its behavior.
So far, it's Modaco FTW. Itz on my fone, reestoring my data --
--
KingCheetah

Did you use this to get Modaco? I noticed it says you must have s-off but in your thread you said you have s-on.
http://forum.xda-developers.com/showthread.php?t=1179125
My problem is that with the data I want to restore, my phone gets stuck in a boot loop. I am thinking that I might be able to install Modaco, restore the data where I can't start up my phone and then do a Modaco backup while still in recovery. Then restore a functioning backup (so my phone boots up) and finally do an advanced restore where I only restore the data I need from the bootloop backup.

paperskye said:
Did you use this to get Modaco? I noticed it says you must have s-off but in your thread you said you have s-on.
http://forum.xda-developers.com/showthread.php?t=1179125
Click to expand...
Click to collapse
That's the original thread Paul (Modaco's creator) posted. I downloaded my copy via Blue's invaluable Developers Reference: http://forum.xda-developers.com/showpost.php?p=17384145&postcount=7. Scroll down to the Recovery section, and under Clockworkmod 4.0.0.9 Recovery there's a download link; but it's the same file.
As to being s-off, I think that's how things used to be. Obviously, all you need now is the bootloader to be unlocked so you can fastboot flash the recovery img file. Otherwise, I couldn't have been doing all the monkeying I've been doing recently.
paperskye said:
My problem is that with the data I want to restore, my phone gets stuck in a boot loop. I am thinking that I might be able to install Modaco, restore the data where I can't start up my phone and then do a Modaco backup while still in recovery. Then restore a functioning backup (so my phone boots up) and finally do an advanced restore where I only restore the data I need from the bootloop backup.
Click to expand...
Click to collapse
My experience is limited, but from your description, I'm not sure if the Advanced Restore option will be the smoking gun for your problem. The way I understand it, ClockworkMod recovery--of which Modaco is an unofficial flavor--takes the equivalent of a disk image of your phone while the OS is inactive (like many disk imaging programs for the PC). If you've got some ratty data causing the boot looping, that data is going to be stored along with everything else in the snapshot during backup. It will also be restored using regular restore or Advanced. So, I'm not certain how using a different recovery module will accomplish your goal of stopping the boot loop. Also, remember that any backups made with CWM 5.0.2.7 will be incompatible with Modaco recovery since it uses only img files.
This definitely needs to go to someone more experienced in troubleshooting Android, I think. Maybe you could edit the title of this thread to reflect the boot looping problem. This will hopefully get someone like Blue involved to help out. Sorry not to have a definitive answer for this. I suppose you could flash Modaco (same as you flashed CWM 5.0.2.7) and see if it does what you're hoping it will do. Best advice I can give.
Apologies for not having a concrete solution, and best of luck --
--
KingCheetah

Same problem, with ANY restore
I'm running cwm 5.0.2.7 and can't restore any previous backups. When I run restore it restores a few things, but then it just stops and cwm recovery seems to abruptly reset. After that I get stuck on the splash screen after rebooting.I verified the md5s in the backup folder, also. All match.
I DID change the backup filename so I could find it easily in my backup folder, but it was doing the same thing even before I changed it.
Anyone else have the same issue?
Also, is there a way to restore the images through adb/fastboot, even though they were created by cwm recovery?

A small suggestion
IBtokin said:
I'm running cwm 5.0.2.7 and can't restore any previous backups. When I run restore it restores a few things, but then it just stops and cwm recovery seems to abruptly reset. After that I get stuck on the splash screen after rebooting.I verified the md5s in the backup folder, also. All match.
I DID change the backup filename so I could find it easily in my backup folder, but it was doing the same thing even before I changed it.
Click to expand...
Click to collapse
Check your backup filenames and make sure they don't have any spaces. If that isn't an issue, you might try reflashing CWM and see if that resolves its difficulties. CWM shouldn't be behaving as you describe if it has been installed properly. Only other thing I can think of is looking into any item installed on your phone that could possible not play nice with CWM. I don't know of any myself, but it's a possibility.
IBtokin said:
Also, is there a way to restore the images through adb/fastboot, even though they were created by cwm recovery?
Click to expand...
Click to collapse
Not that I know of; hopefully someone with more CWM knowledge will chime in on this thread.
Purrs --
--
KingCheetah

Hmm...I'll have to check to see if the old fastboot method can still be used.
---------------------------------------------------------------------------
Nope. Nandroid used to save the files in .img format instead of the current one. This means no fastboot restore.
Sent from Spaceball One.

{TIP] Restoring TWRP backup after complete data wipe

Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!

Or you could just copy the whole twrp folder to your hdd. thats what I do anyway and restore without a problem.

Yep that would have prevented me ending up in that predicament for sure.
So would not flashing roms. The point of the post is really about what to do if you find yourself in that situation and the value of keeping a cool head and thinking through a solution rationally, using your own resources.
The way I see it is: it's my mess I got into it, how am I going to solve it....
Sent from my HTC One S using xda app-developers app

Lost my Backup
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?

matrixmainframe said:
Good advice which I'm trying to follow but my TWRP Recovery cannot see the TWRP ROM Backups that I created with ROM Customizer which ROM Customizer has placed in the folder
/data/media/0/TWRP/Backups/4df1bd936aae7f4b
but when my Samsung Galaxy S3 i9300 is in Recovery Mode it is obviously looking somewhere else........I just can't figure out where because then I can just move the backup to where ?Recovery Mode is looking.
Anyone any ideas please?
Click to expand...
Click to collapse
Do what the op says and do a backup and you will know where to put it.
Sent from my HTC One S using Tapatalk 2

Plz HELP!!!
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.

abdullah.imran2158 said:
ACtually im in deep deep trouble please i would be really grateful to the person who helps me. OK so last night i flashed cyanogen mod10 on my htc one x and when i did everything booted the boot.img and all i factory reseted from cm10 because it gave me the error that unfortunately android.process.phone has stopped nevertheless now everythings gone and no supersu root file is gone which is obvious that i dont have root now. Plz tell me how to go back to my factory settings with htc sense on it now i just want my phone back, i did another factory reset wiping off the rom but it says no OS installed and it gets stuck on htc quitly brilliant screen plz plz plz plz help me any one plz.
Click to expand...
Click to collapse
1. wrong forum, if you have a one x device
2. calm down
3. relock your bootloader (fastboot oem lock)
4. download and run latest ruu for your phone (search for a suitable one for your cid and carrier if you are branded)
5. you also can flash a custom sense based rom, which gives you sense back (viper one s or trickdroid or android revolution hd)
6. if you want to flash one of these,dont forget to flash the boot.img too
7. before flashing a rom, wipe system, data and cache 3xtimes to be sure you do a clean install

Thanks Man
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
Thanks Man, been stuck in TWRP for about two hours now, thought I soft bricked my Droid Dna forever. I had a backup, and adb pushed it to the /sdcard directory, but it wouldn't show up in the restore section. This empty-backup method worked fine. Thanks, you saved me $400.:good:

Saved my HTC One!
ATSPerson said:
Ok so I had a problem recently and found a solution which might help. I googled, looked in this and a bunch of other android forums and didn't find the solution I had, so maybe my way is not the best way to do it - but it solved my problem maybe it might help you.
When I flash a new rom with a different framework to the rom I'm currently on I take care to make a full TWRP back-up of my current system move that across to my PC, then proceed to wipe everything on my phone, data, system, factory reset and numerous cache and dalvik wipes. (I use the Awesome scripts superwipe and kernel cleaners which do the trick really well).
Anyway recently I installed a rom which really didn't work for me, so i wanted to get back to where I was before I installed it. I booted into TWRP cleaned the data, system factory reset wiped the caches. I mount my PC move my nandroid across to my SDcard and go to restore. But of course TWRP looks in the restore folder for the backup and I have wiped this so the file structure does not exist.
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
I'd just like to say a MASSIVE THANK YOU for this post! I had a major issue and thought I'd lost my 1-day old HTC One (M7). I wasn't so much panicking as I knew i'd find a way, but a cold sweat had started to break!
The biggest lesson I can take from this is simply this... MAKE SURE YOU BACKUP YOUR ORIGINAL ROM BEFORE YOU DO ANYTHING! It's such an obvious thing, but without this simple step, I'd be in trouble right now as HTC haven't an RUU for my specific device yet (plus I'm on a Mac, making running .exe files more painful still)
What had happened was that as a result of a corporate email policy, I had to encrypt my device. I did this after flashing to a new ROM. Unfortunately after I had done so, the new ROM wasn't playing nicely with Exchange (using native HTC Mail app). Of course the issue here is that when you so into TWRP, you can't see the files to restore (because TWRP is opened before the device asks you for the passcode to decrypt... another learning!). To remove the encryption, I had no choice but to do a full format of the device, so I was basically left with a brick
Anyway, once again, thank you for this post, you just saved me AU$700!

Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?

So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
Click to expand...
Click to collapse
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.

:good:

cheyennemtn said:
So I had to do a complete restore of my default Samsung Note 2 Sprint L900 firmware after an unsuccessful Rom flash of Goodness Noteworthy 1.8.1 (numerous flashes and it wouldn't boot up past opening war video, just went to black screen and hung endlessly)
-OK so I then got back to root and installed TWRP 2.6 and I had already had several backup ROMS I saved to my computer. So I placed Goodness Noteworthy 1.7 in my backup folder in TWRP on my sdcard. I then reboot into TWRP recovery and go to restore and I can't see anything there. I have the sdcard mounted and checked and after clicking the restore button I'm not seeing anything. ? When I click install it see's everything on my sdcard ? I don't get it. What am I doing wrong.
---------- Post added at 01:20 PM ---------- Previous post was at 12:42 PM ----------
Solved.. Copied my backup stock ROM from the TWRP folder on the phone and placed it on the SDcard, then I placed my Goodness Noteworthy 1.7 backup rom I had that I had on my computer and copied and placed that on the SDcard in the TWRP folder next to the Stock Rom backup I made. Booted back into recovery and clicked RESTORE and I was able to see both the backup rom and the Goodness Noteworthy ROM. I then wiped and did a restore and I'm back in business.
Click to expand...
Click to collapse
Deleted comment

Hei guys,
Please help!!!! I tried to install MaximusHD 10.0.0 | JB 4.2.2 | Sense 5.0 on my HTC One s,i got storage issue. Now my sd card is just 48MB. I have installed TWRP v2.6.3.0 and i did backup before flashing room. I decided to do factory restore by TWRP and wiped OS from MY device.Now when i do backup i get failed error: not enough free space on storage. Total size of all data 203MB, available space 48 MB.I see my sd card on pc through TWRP, but i cannot make backup and even put any new rom into my sd card to flash it because of 48MB...Is it any chance to get back any OS on my HTC One s....?

This post might help
http://forum.xda-developers.com/showthread.php?p=47744972.
Sent from my One S using xda app-developers app

StifflerServices said:
Ok so, in not so many words, ur saying " to restore a nanBU":
1. Wipe: data factory reset/cache/ delvic
Wipe system (but not sure which one(s) cause I was used to cwm and it looks diff in twrp
2. Flash the Rom that the nanbu is based from
3. Flash the nanbu
4 reboot
It's this the correct way to restore a nanbu from a diff or upgraded rom?
Click to expand...
Click to collapse
EDIT: oops, somehow thought this was a recent post. Never mind
Not really.
If you are S-off,
Restore Backup,
Wipe Caches
S-On
Restore Backup
Wipe Caches
(if the rom you were previously on had a different Boot.img you will need to fastboot your boot.img) In the backup
Assumes you are not trying to restore a backup to 2.15 if you were just on 2.16. You will need to RUU + factory reset/clear storage for that.

I'm sry not sure what "RUU" means... Probably will remember once u tell me I'm sure. But Ya I kinda just winged it, didn't flash the Rom to do the NanBU and all went fine, which is odd cause on my S2 w cwm it out me in a boot loop and had to start over, but I think TWRP may be a diff setup when restoring nanbu's. But either way it's always nice to know and find a "step by step" guide to restoring NanBU's from previous / updated / or different ROMs. For noobs that was one of the confusing things to do due to lack of that info in threads or utube vids out there.

Got a question. I've made my backup files but restore shows nothing but storage... No files to chose, no more options to restore. Is it normal?
Sent with my One S C2 Sense 5 using Taptalk

brilliant!
ATSPerson said:
So after telling myself what an idiot I was for not remembering what the file system was, here's what I did:
1 - Stopped panicking!
2 - Ran the back-up utility in TWRP - this recreates the file structure for the back-ups and places a back-up of your empty system in the folder
3 - Move the original full back-up I placed in the empty SDcard into the file system next to the empty back-up I'd just created
4 - Go to restore and the full back-up is there. Swiped to restore it and my One S is back to it's old self
Lessons learnt: Don't panic - there is an answer. Just think about it.
Good luck!
Click to expand...
Click to collapse
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.

metropical said:
you my friend, are a genius! I have been so screwed trying all kind of crazy stuff the last few days.
Brilliant! May I suggest you run for Pres of the Colonies.
Click to expand...
Click to collapse
From one Clash fan to another, thanks for the thanks ☺
¡La lucha continua!

[Q] Upgrading to 4.4.3, couple of questions

Hey all
I wanna update to 4.4.3 but I want to wipe everything, then restore some things I want cause the battery life on my phone is pretty bad even using greenify for just about everything I can...
I'm running stock rom with Xposed and Franco kernel, I have Titanium backup pro and a backup I took with my CWM recovery.
How do I go about this? I want everything deleted with the option to restore my apps and their data ,What'sApp conversations, PvZ level progress, and my Xposed settings are the important ones.
Does the Titanium backup I have save these things? Do I need to copy tyhat backup off the phone before doing anything cause it will be deleted in the process?

Pretty sure this has been answered in one of the million duplicate threads posted yesterday. Did you read them / use search?
Sent from my Nexus 5 using Tapatalk

Yes but most asked how to upgrade without wiping, I want to wipe everything then restore some stuff. This is my first Android upgrade so I'm a bit :?
Like restoring Xposed settings with all my modules and stuff, I have no idea how to do that.
Also, do I need to revert to the stock kernel before doing all of this? I'm a bit scared of all this.

Titanium backup is your best bet for backup / restore. Don't wipe your sdcard.
Sent from my Nexus 5 using Tapatalk

Well went ahead and downloaded factory 4.4.3, installed with flash-all and now I'm rebuilding it. Hopefully Titanium has everything I was hoping for it to have...

SonicAngel said:
Well went ahead and downloaded factory 4.4.3, installed with flash-all and now I'm rebuilding it. Hopefully Titanium has everything I was hoping for it to have...
Click to expand...
Click to collapse
Doesn't "flash-all" flash userdata which wipes /sdcard?
I wouldn't ever recommend using those batch files. You only needed to:
Code:
fastboot flash system system.img
fastboot flash boot boot.img

rootSU said:
Doesn't "flash-all" flash userdata which wipes /sdcard?
I wouldn't ever recommend using those batch files. You only needed to:
Code:
fastboot flash system system.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
It does which is exactly what I wanted. I wanted a complete overhaul that deletes everything, like a new phone.
I saved my TitaniumBackup folder from /sdcard to my PC and now I restored it, this is pretty much what I wanted and TB really backs up almost everything. I'm happy so far

SonicAngel said:
It does which is exactly what I wanted. I wanted a complete overhaul that deletes everything, like a new phone.
I saved my TitaniumBackup folder from /sdcard to my PC and now I restored it, this is pretty much what I wanted and TB really backs up almost everything. I'm happy so far
Click to expand...
Click to collapse
Ah ok fine.
There was no benefit to wiping the /sdcard though

rootSU said:
Ah ok fine.
There was no benefit to wiping the /sdcard though
Click to expand...
Click to collapse
The only benefit was that this is my first Android phone and I tried a lot of stuff before settling with what I like. That left a whole lot of mess on the phone and even in /sdcard there was a lot of crap that I have no idea what it was and weather or not it's necessary. Now I can take another look and if anything is back I know it's needed.

[XT1032] CM 12 - Flashing TWRP v2.8.6.0 has caused bootloop

Hello,
XT1032 CM 12 latest nightly (I think)
I flashed TWRP v2.8.6.0 using their manager app. I entered recovery mode and everything seemed to work fine. I made a NANDroid backup then rebooted. Unfortunately the device was then stuck at the bootlogo and kept looping. I can still access recovery and fastboot but for some reason adb doesn't see the device, nor can my device's data be access under Windows 7. I don't recall if I had USB debugging on or not. I would like to try to backup a few files to my computer (the backup for instance) but I am unable to since I can't use adb as the device is not recognized. MTP through TWRP doesn't seem to work either. I do have the Universal drive pack installed already on Windows.
Any help would be greatly appreciated. Thanks for your time.

To start with, let's make sure the files you want still exist.
1. Boot into TWRP recovery
2. Go to "Mount" and check that your "Data" partition is selected
3. Go back and then go to "Advanced" and then to "File Manager"
4. Navigate around (maybe /sdcard/ ? Depends what you're looking for) and find the files you need
If you can't find your file, you'll need some more help. Let's say you do see your file. Do you have a USB-OTG cable? You could plug a USB drive into your phone and mount that. Then you could copy your file to that drive. If you don't have the cable you do have some other options, but let us know how far you get.
EDIT: I know I haven't addressed the problem of the bootloop at all. Many of those solutions involve wiping so we need to make sure you've backed up all the files you need first.

First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:

frustratedwhiteman said:
First of all thanks for the help. :good:
I've been trying to find a solution and in fact flashing CWM worked. I was able to adb pull all the files and make a backup.
I backed up the content of the sdcard. I tried restoring the CWM nandroid with data only so it did reinstall the apps but unfortunately all their data and settings are gone. Making a full restore just goes back to bricking. So I have the nandroid and the data manually backed up to a computer but no idea how to restore it.
I've tried pushing the nandroid back to /mnt/shell/emulated/clockworkmod/backup after an unsuccessful restore but now it doesn't even work. (protocol failure, the push command fails)
honestly at this point I think the best solution is just to make a clean install. In fact it would be a good idea to just reset the whole phone and start with a clean slate with CM13 including wiping system files and maybe manually restore some key files and configuration (I've got all the .com files of relevant apps)
Do you know how to do that? :laugh:
Click to expand...
Click to collapse
I'm not really a Nandroid expert, but I can take a few shots in the dark. When you did your backup you got a TAR file for System and one for Data, etc., right? Then you convert those to IMGs? If you upgraded and then restored the system backup I can see why that would result in a boot loop. Restoring the data image shouldn't cause such problems though. Is this what you've tried so far? You're right, though. The safest method is to manually restore the data of just the apps where you need that data, and do it one at a time. This would allow you to pinpoint what is causing the issue. Of course, I may have no idea what I'm talking about. I've never actually needed to restore a Nandroid backup! Hopefully someone with more experience there will chime in.

I thought to hell with it I went and solved the issue by installing CM13
Thanks for taking the time to help and see you next time

Oneplus 6 bootloop after upgrade to 9.0.4 (+failed to restore the nandroid backup!)

So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.

b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.

Thank you for making the time writing this, it is relief to hear that you figure this out. Will try this first in the morning.

I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.

tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
This guide can also be used to restore from other roms;

b217260 said:
I did a bad mistake running the flash-all.bat thinking it will only flash the partitions of the system.
Well it is all gone now...Dam if only I wait until the morning I might not made this mistake.
Click to expand...
Click to collapse
What did you do?
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
petran07 said:
This guide can also be used to restore from other roms;
Click to expand...
Click to collapse
I guess so. I never had to use a backup to restore on a custom ROM yet.

tabletalker7 said:
What did you do?
Click to expand...
Click to collapse
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.

b217260 said:
After extracting the stock zip flasher, there is file "flash-all.bat" on the root of the folder. (Guess I needed to use the "flash-all-partitions-fastboot.bat)
Thinking it will only flash the android system partitions I've run it and realize that my internal stoarge was formatted.
Really stupid mistake from my part, sorry for couldn't verify your guide.
Hoping that someone who read this in the future won't do my mistake.
Click to expand...
Click to collapse
It's my bad. I always store my backups on an SD card with my OTG card reader. I forget others don't think like I do sometimes

tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.

b217260 said:
So I have the OP6 for a while now. Everytime a new version released I download the new official zip file and then flash it with twrp. (follow this post - https://forum.xda-developers.com/showpost.php?p=76596833&postcount=3)
So I did it for 9.0.4, I first took nandroid backup, flash the new firmware, flash twrp, reboot to recovery, flash magisk. And then when I tried to reboot the system I got a message "Shutting down..." when the android system tried to load so I was stuck at bootlooping.
I thought that maybe something in the installation went wrong, so I might just get it restored. I did the restore using the latest twrp (v9.91) and now the system is completly corrupt, the phone no longer able to load anyhing (no oneplus loading screen with the rolling dot) and I when it boot to twrp it no longer can decrypt the filesystem (doesn't ask for my password).
I don't know I could I meesed this up, I did the same step every new upgrade. Apperiate any insight to my situasion.
What do you think caused this? Can I decrypt the files on my phone somehow and restore them?
Thank you in advanced.
Click to expand...
Click to collapse
Had faced this many times. ...after trying diff options and failed Qualcome MSM method works perfectly.
Yep, You cant restore data i think as it being already formated as per knowd based on your steps above on diff posts

ahacker said:
tabletalker7, can you please explain a little technical detail? If i follow your procedure, what is the difference from me just restoring boot, system and data from a Nandroid backup of a system that used to boot? What causes the restored system to no longer boot?
Because you seem to be suggesting a solution for the the problem I had. I normally do plenty of backups and play around with the system quite a lot, but Op6 burned me: I was unable to restore from a backup like I always did on other phones. I tried suggestions from other posters to no avail. So I set up a clean system from a fastboot rom and reinstalled everything from Titanium. I wonder, after I set pretty much identically, should I just risk and to once more try to restore from that Nandroid that was failing to restore (that only had system and data btw)? I'd greatly appreciate if you can enlighten.
Click to expand...
Click to collapse
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.

tabletalker7 said:
1. Changing Android security updates makes changes to phone encryption. It will make the data itself on the backup unreadable to the operating system. That is why people playing with many different custom ROMs had problems with data stored on their phones.
2. By using the fastboot rom you ensure that both partitions have the same operating system. A/B partitioning seems like a great idea on paper but it seems to be executed in the most horrible way possible.
Click to expand...
Click to collapse
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.

ahacker said:
Thanks a lot. It is plausible and I remeber seeing folder names to which random hex strings were appended (I did not see file contents though). But after last restores I verified that the folder names in /data/data folder were looking allright. Twrp apparently could decrypt the data partition, but the system would still not boot. If I were to encypr the data partition I'd use the whole partition as one encrypted block and not bother doing it on file or folder basis, which is more error-prone. Another sourse of doubt is that I never played with OS version upgrades nor with installing other roms.
Can you also please answer the following? Do you think I can try to restore my boot+system to a different slot and then come back to my original slot if my playing there is unsuccesfull? Being scared that restoring a previous state can fail is a major problem.
Click to expand...
Click to collapse
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble

tabletalker7 said:
I would not recommend doing that. While you may have different roms on different partitions you only have one data partition. That is asking for trouble
Click to expand...
Click to collapse
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.

ahacker said:
I would have data backed up, sure.
What bothers me is that an essential property of a digital automaton is that if you start it from the same state it will continue the same. Nandroid used to capture all that mattered for identical runs. It no longer does, something is missing, such as some encryption keys for data partition, as you seem to suggest. This bothers me.
Click to expand...
Click to collapse
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.

tabletalker7 said:
What bothers you here are things I call "security". If the nandroid backup has the encryption keys to decrypt it, then the data is not secure.
Click to expand...
Click to collapse
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.

ahacker said:
Nandroid backups should be encrypted when created with a user supplied key. Twrp allowed this since ages ago. Not allowing the user to restore a backup is not a right substitution for this.
Click to expand...
Click to collapse
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.

tabletalker7 said:
TWRP didn't do this. Android didn't do this. Ya know, if this is anywhere near as horrible for you as you are making it sound, my advise for you would be to buy Apple products. Bottom line is a new feature was added to Android, and your backup does work.
Click to expand...
Click to collapse
-It is as horrible as not being able to restore a full backup. No more, no less.
-Twrp has an ability to encrypt your backups, with your experience you must know this.
-You are suggesting someone to switch to iphone only because they point out that the things are wrong or dont add up.
-It is quite a common knowlege that you get good security out of encryption if you make things explicit and clear. And not how you may think it is. Cause you don't seem to know where the keys are stored for the data partition. Obviousely, because the phone eventually decrypts your data, the keys must be stored somewhere or derived from you swipe pattern.

tabletalker7 said:
Ok this is a giant pain in the backside but I have done this before and I know it works. Here is a step by step guide to restore.
1. https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 go here and download the fastboot rom for the rom YOU HAD ON THE PHONE WHEN YOU MADE THE NANDROID BACKUP. Step by step on how to install it is there.
2. Install the rom and boot up the phone. Don't bother signing in to google or downloading apps or any of that. Just get through all the menus.
3. Install TWRP. Bluspark TWRP is recommended.
4. Install Magisk, but make sure IT IS THE SAME VERSION OF MAGISK AS WAS INSTALLED IN THE NANDROID BACKUP
5. Reboot to system and make sure the phone still works, then reboot to TWRP
6. Restore Nandroid backup.
I know this is a giant hassle, but it works every time. I haven't found a better way to restore a backup since this whole A/B partitioning started.
Click to expand...
Click to collapse
Following these instructions seems to be the only way of restoring a nandroid backup (at least for my Op6 bought on AliExpress from China). Important: step 1 wipes your sdcard, so the backup you want to restore must be on otg usb stick.
After spending many hours I managed to restore a backup at least once. Fortunately for me I have no plans of upgarding Android and will likely forever stick with the following set:
1) 5.1.11-OREO-OnePlus6Oxygen_22_OTA_015_all_1808102118_770880-FASTBOOT.zip (found here)
2) twrp-3.2.3-x_blu_spark_v9.85_op6.img + twrp-3.2.3-x_blu_spark_v9.85_op6.zip (found here)
3) Magisk-v18.1.zip (found here)
My plan is to fully debloat the phone and then I will keep everything unchanged for years, because nowadays updates are more about twisting your arms than giving you usefull features. I almost got to that state, but one little glitch forced me to roll back and the whole hell with the Nandoid backups on Op6 started.
PS: It's very interesting what is really going on with this A/B system. There must be a storage where the encryption keys are stored (if it is the encryption that does prevent the phone from restoring. Which I doubt because Twrp sees the files fine). There also probbaly stored what slot is used. That information does not get captured by the Nandroid backup.

(Btw, It seems that blu_spark Twrp is really NOT encrypting your backups with the passwod you supply. Official Twrp does. I have plenty of old encypted backups, from wich I could not extract any personal data (/data/data folder) but yesterday I could extract my private information from a backup done by blu_spark Twrp. This is serious iussue. I'll double check and will post if confirmed.)
Not confirmed, I was looking at unencrypoted file.