TL;DR: Tried updating OS using flashable zip thru TWRP, didn't work so used fastboot method, got it working on stock but can't restore nandroid backup (not even /data partition), have app data that I need, what can I do?
Background
I picked up the Nexus 6 not too long ago and I soon decided to unlock the bootloader, install a custom recovery, and root it. Thanks to the info here on XDA, that was painless. A few weeks ago, I got a notification for an OTA update. Having read that OTA updates no longer work for modified /system partitions, I knew that I wouldn't be able to update it.
I ignored the update for a while until I finally decided to look into how I could make the update yesterday. I really didn't want to deal with setting up the device the way I like it again so I was hoping to find a method that didn't nuke the /data or /data/media partitions. I found what looked to be the easiest method which entailed flashing a zip from TWRP.
What I Did
I ran a nandroid backup before doing anything and naively figured that would be enough. Afterwards, I wiped the system and caches for what I thought would be "good measure", flashed the zip, and was surprised to see that TWRP was reporting no OS was installed. I was under the impression that the system partition was going to be overwritten.
To make it short, I tried restoring from the nandroid backup but it would fail at the system part with TWRP reporting something along the lines of 'Cannot restore System -- mounted read only'. I hopped on fastboot, flashed the images provided by Google, and was back on stock. I tried restoring the backup once again but to no avail. I even tried restoring just the data partition but that didn't go well either.
Much Regret Section
Now, I know I should have backed up the apps separately with something like Titanium Backup but I had a lapse in judgement and assumed I could just revert back if anything went wrong. Unfortunately, I have applications with data that I can't easily get back. I tried using Nandroid Manager to restore applications from the backup but, as with past experience with the app, not all data is recovered.
Is there anything that I could try to either revert back to that backup or at least get the applications in data back the way they were prior to updating?
Wow, I feel like a doofus. After quite some digging on Google and XDA, I found the remedial solution to my problem in this post. For simplicity's sake, here's a quote:
Nevermind, I finally figured it out. In TWRP under MOUNT you have to uncheck "make system partition read only". Now my restore is working.
Click to expand...
Click to collapse
If that isn't clear enough, he's referring to the first page/menu of TWRP which has the 'Mount' button that leads you to a page with a checkbox at the bottom that is ticked and makes the system partition read only.
EDIT: As it turns out, this was only my first problem. After trying to restore the backup, I receive the same error message that I got when I attempted to only recover /data. I get the following error: 'extractTarFork() process ended with ERROR: 255'. From what I gathered online, it looks like some file may have been modified? The only thing that I did to the backup was move it from the phone over to my computer before flashing the image. Other than that, Nandroid Manager I believe decompressed it. However, now I'm stumped and I'm not sure how to proceed here.
EDIT 2: This was likely due to Nandroid Manager decompressing the backup. Luckily, I still had the uncompressed copy on my computer. I restored the backup but the phone would get stuck loading. I tried flashing the older images that I had before updating and then restoring the backup but that didn't make a difference. Finally, I gave up and salvaged what I could from the backup using Titanium Backup.
Related
I wouldn't think so, but I'm really clueless about what's going on...
I have Cyanogen 3.9.8
I want 4.0.2
When I use the CM Updater, I get the dreaded acore Force Close.
So I try the manual approach, putting the 4.0.2 zip file on my SD card's root, then I reboot into recovery, and I perform a Nandroid backup (I run Linux on my computer, and don't use ADB).
Then I do a wipe, before I install the 4.0.2 zip.
Finally, I do I Nandroid restore.
Rebooting takes a long time, which tells me something has been done in the ROM department.
But when I have it up and running, everything seems just as they were before the operation, and when I start CM Updater it says "Running version: CyanogenMod-3.9.8"
I tried again, this time I booted the phone before I did the Nandroid restore, was met with the "factory fresh" Google account login screen (so it looked wiped to me...), then did a reboot to recovery and a Nandroid restore, reboot, checked CM Updater: "Running version: CyanogenMod-3.9.8".
Maybe I need to tweak my ROM updating routines..?
I have 3 partion SD card, so apps2sd is running.
Any help is highly appreciated.
Thanks,
Christopher
I'm kinda confused here, it's Monday morning. Since your trying to upgrade why do you keep doing a nandroid restore? You only want to restore nandroid if you want to go back to that previous point when you made the restore point. If you are just upgrading, just upgrade without restoring nandroid.
do exactly what you did without doing the nandroid restore at the end
Nandroid Restore is pretty simple.
Say you have ROM1 installed and there is an experimental ROM2beta out. So you want to try it.
Do a nandroid backup and it saves it to your sdcard.
The files that are saved are:
recovery.img
data.img
system.img
cache.img
misc.img
boot.img
This is almost every part of your phone except the spl and radio.
When you do a ROM upgrade MOST of the time it only updates the system and boot (some ROMs like Hero wipe/update the system, data, cache and boot.) But if your going from Cyan1 to Cyan2 then the only things being changed are system.img and boot.img. Unless you wipe, everything else should remain the same.
With all that said... you flash from ROM1 to ROM2beta and then do a restore from the ROM1 backup. So what does that mean for your phone? Is it possible to have ROM2beta ROM with the ROM1 system.img and boot.img? No. Since system.img is restoring the key elements for the ROM1 over your newly flashed ROM2beta. Bottom line. You'd be right back to where you started.
Binary100100 said:
With all that said... you flash from ROM1 to ROM2beta and then do a restore from the ROM1 backup. So what does that mean for your phone? Is it possible to have ROM2beta ROM with the ROM1 system.img and boot.img? No. Since system.img is restoring the key elements for the ROM1 over your newly flashed ROM2beta. Bottom line. You'd be right back to where you started.
Click to expand...
Click to collapse
Which explains what I am experiencing.
Thanks, 36!
That means I have misunderstood what Nandroid does.
I thought it would just take a backup of "user changed" files, like application data, configurations, call logs, that sort of things - like MyBackup Pro, more or less.
Guess I will get back to using MyBackup Pro before I upgrade my ROM.
Thanks, this really clarified things - I'm sorry I had to post such a n00b question, but I haven't found any other Nandroid postings telling me in such details what Nandroid backs up (and restores) - but then again I probably haven't looked hard enough! ;-)
~Christopher
Seems I had the same misconception and it seems that Nandroid is not nearly as useful as I had been led to believe by all the posts harping on about it. What I want is a backup of all my user data which I can restore to the updated ROM. Luckily I suspected Nandroid wasn't going to do this and used MyBackup Pro too
MikLSP said:
Seems I had the same misconception and it seems that Nandroid is not nearly as useful as I had been led to believe by all the posts harping on about it. What I want is a backup of all my user data which I can restore to the updated ROM. Luckily I suspected Nandroid wasn't going to do this and used MyBackup Pro too
Click to expand...
Click to collapse
nandroid can do this you just have to do a backup flash youre rom then push youre data.img
I understand you push the data.img but.....
how...
please
Perform a nandroid backup
Locate the backup on your sdcard under the foler "Nandroid"
Navigate to the last folder (this should be your latest)
Copy all or at least the folder that you want to push back (in this case just data.img to a directory say c:\nandroidbackup)
Open the cmd prompt and make sure that you have your fastboot.exe file in your pc's system32 directory.
If your phone is already on type "adb shell reboot recovery" in the cmd prompt to get to the bootloader and ready for FASTBOOT and then type "exit" to quit the adb shell.
If not then power on your phone while holding the camera button to get to the bootloader and then press the back button on your handset to get to FASTBOOT mode.
On your cmd prompt type "cd" along with the location of the data.img file (example cd c:\nandroidbackup) to move the command prompt to the backup location.
On the cmd prompt type fastboot flash userdata data.img and hit enter.
You should see "sending" followed by "writing" once complete type fastboot reboot and hit enter.
That should do it.
Now mind you that pushing your data across different builds may not work. If you are trying to restore your data on Hero that was previously saved from Cupcake then you're wasting your time. And vice versa. Always store a backup or two on your pc for quick and easy access in case something doesn't work.
In the event that it does not work simply wipe and follow the above directions to restore.
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
Thanks great thanks mate!!
On the cmd prompt type fastboot flash userdata data.img and hit enter.
Click to expand...
Click to collapse
This step fails for me during the "verifying signature" phase. I believe this is todo with my spl.
Is it possible to use adb to do this? or will the spl still prevent it?
Long story short: When restoring via Nandroid it hangs, when using advanced restore the data portion says
E:Can't mount /dev/block/mmcblk0p2
(file exists)
Error mounting DATA:!
Click to expand...
Click to collapse
This afternoon I tried running the Voodoo zip, but the one I downloaded from their site isn't for the Captivate. I ended up with a phone that was constantly displaying 90 degrees off from what it should have been (holding it straight up had the phone thinking I had it on its side).
I decided to uninstall voodoo by creating the "disable lagfix" folder on my card. I rebooted and the phone hung and remained hung at the spinning progress wheel for an hour. I pulled the battery since I couldn't get out of that screen. Rebooting after that had me in what appeared to be the stock version and showed a few of my non-stock apps as "com.etc..." apps.
More reading on here and I found the Captivate-specific version of Voodoo. I figured I'd try to install that before restoring from the Nandroid backup I ran before installing the Voodoo. However, when in recovery mode I couldn't "click" anything with the power button. I tried using adb reboot recovery which didn't fix the problem and instead put me into a non-stop cycle of non-functioning recovery modes after boots.
So I used Odin to get back to stock. Now I'm trying to restore back to where I was before Voodoo. I tried to just run a simple Restore but it hung and after 90 minutes it hadn't completed. So I tried to run an advanced restore and all sections restored except for Data. When I try to restore Data i get the error at the top of this post. I've googled for an answer and everything I've read so far is Cyanogen specific and appears to require Cyanogen to fully fix it. Anyone know how to fix this on a Captivate? Anyone have a link that I'm missing?
Thanks!
If you can boot the phone, then go into android terminal emulator (you may have to download it from the market first) and type mount in the terminal. See what type of partition /data is. If it's ext 4, the disable lagfix was not finished before you pulled the battery. Your best bet then is to download the Captivate voodoo beta 4 kernel version 1.6, which is sticky post in the Captivate development forum here, remove the disable lagfix folder/file from /sdcard/Voodoo/ and let it boot. It will then get you to the point where you should have been at first without having rotation issues and with a kernel that understand ext4. After that, restore your phone to the way it needs to be with Titanium, or by manually downloading and reinstalling any apps that got deleted by your premature battery pull. When ready to do a nandroid backup, do a disable lagfix and let it fully reboot to convert the ext4 to RFS. Then you can do a nandroid backup of restore, as clockwork recovery does not understand ext4 (yet).
Thanks Rajendra! I'll try that and follow up with the results.
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Duplicate post (no way to delete I guess?)
RobertDeBord said:
I used Odin again to bring it back to stock, which appears to have given it back RFS formatting on data which means I'm able to restore to it now.
However, my restore is hung on one file and has been for a good 25 minutes now. Is it normal for it to sit on a file? Anything I can do to skip/bypass the problem file or find out what it is? All it says is '-274738110' for the file.
Click to expand...
Click to collapse
Try this - once the phone boots - then go to internal sd card and see if there is a Voodoo folder (which there still should be) inside the Voodoo folder make a folder called disable-lagfix - reboot and it should go through the reverse process of creating the lagfix (robot voice). After it finishes reboot go to rom manager and restore.
Hope This Helps....
I can tell you, I've never had a successful restore from rom manager/clockwork recovery. Not once! The only thing that program is good for is as a replacement recovery reboot, it lets you select which zip you want to install from, rather than having to manually name everything to "update.zip". I can't honestly think of anything else its good for. I've tried literally dozens of restores on my captivate and everyone of them has crashed or frozen at some point during the restore. Worthless!!
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
ImMrBS said:
Hi,
I have an HTC One m7 on T-Mobile, rooted and running Android Revolution 82.0.
I messed up, now I need help to dig myself out of this hole. I do not understand some of this, this could be partly due to my stupidity.
I backed up my system and boot in twrp before i had done any of this.
Last night I wanted to update TWRP. I downloaded "TWRP manager" through the play store, I opened the app and went down to "install twrp" - i installed TWRP 2.8.1.0 through the app, it said flashing successful. Everything was fine. I rebooted my phone into recovery to verify that it had worked. The correct twrp version was displayed at the top. I rebooted my phone into system. After the boot sequence it loaded into the first time run set up manager (by this i mean the thing that comes on when you turn on your phone for the very first time). This shocked me. I went through the procedure to "set up" my phone. All my apps were gone, all settings, everything. It looked as if it were brand new. Even the pre-loaded apps for android revolution were gone. I rebooted back into twrp recovery, went to the file manager and went to the main directory "/". I looked for the folder "/storage" but it wasnt there. I went to go restore my phone to the backups i had made before i tried updating twrp to see if that would help. Nothing changed. after this, I reinstalled the rom through TWRP without wiping anything. All my apps were still gone, all settings were gone, yet all my photos were still there. All of my files for the apps are all there, they are all in the internal storage, all the folders are still in /data , i do not understand what happened. I am also concerned that when I am in recovery and i am in the file manager i cannot see "/storage", as if it is hidden from the recovery file manager. Also, when i select "backup" and it gives me options to backup system, data, etc., under data it only shows 756 mb of data, i have at least 2000 mb, I am wondering if my phone is accessing the storage somewhere else? Please help me find out how to fix my errors. I wish to go back to where i was, or at least figure out what happened to increase my knowledge and NEVER do something like this again.
for some reason which i do not know, my sdcard files are saved in different places? i assume this is just how it's supposed to be. these loacations are : "/storage/emulated/0" - "/storage/emulated/legacy" - "/storage/sdcard0" - "/sdcard" (all of these folders have all of the same files etc.)
Thank you,
Evan
Click to expand...
Click to collapse
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Danny201281 said:
The answer to your mysterious factory reset lies here in this link. For further information see the link in this link
http://forum.xda-developers.com/showpost.php?p=55741117&postcount=83118
When in the TWRP file manger your /storage is a Folder called /sdcard.
And the multiple storage locations. Not all of these are actually physical locations you only have one memory chip with one set of files, the other locations are just emulated/virtual copies of your main storage
If you found my post helpful, no need to say thanks. There's a button for that
Click to expand...
Click to collapse
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
ImMrBS said:
So what I've gathered from this, is that all my apps are gone forever because I forgot to backup the data. And that is because "Then along comes the recent TWRP builds (2.7.1.2+) that read the bcb on boot. You flash it and boot into recovery, TWRP starts, reads the wipe_data command out of the bcb and proceeds to wipe the /data partition."? Also should I run the reset script in this post? http://forum.xda-developers.com/showpost.php?p=54370858&postcount=492
since I have a non-sprint htc one I'm not sure if this would do me harm or not. The reason I am asking all these questions is because I want to make sure I don't do something stupid again.
Click to expand...
Click to collapse
Yep that's about right. Running the script shouldn't do any harm but since you already experienced the Factory reset. The command should no longer be in your bcb anyway. As far as I'm aware this only happens once after a new flash and shouldn't repeat every time you use recovery.
But using the zip to clear your bcb is not a bad idea for piece of mind.
Hit that software update.
Wow thanks for the late news
my phone is upgrading now
Don't know if anybody else had trouble connecting their m9 with their Roku 3 before the update but the miracast feature now works with my Roku 3
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
nickmgray said:
Anyone have any suggestions on how to force the update? Still have not gotten the notification to download the update and I get the standard "There are no updates available for your phone" message when I got into settings and check for the update manually.
Click to expand...
Click to collapse
If you are 100% stock update using the ota from stock recovery.
Download and read here
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
AaronM7 said:
So I ran into a small issue. I was rooted with TWRP, and i re-flashed the system image that i created when I first installed TWRP. This took, as I was prompted to reinstall SuperSu. I did not reinstall, then flashed the stock recovery back to the phone.
All good so far.
Then I went to install the OTA, and received the error message
E:unknown command [set_err_msg]
/dev/block/bootdevice/by-name/system has been remounted R/W
reflash device to reenable OTA updates
Did my reinstall of the system image not take? As far as i could tell, everything worked properly until installing the OTA.
Thanks in advance for any help.
Click to expand...
Click to collapse
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
darll said:
I had this same issue and finally figured it out yesterday. The reason is because in older versions of twrp, the minute the recovery is booted it mounts system as read/write. So any backup done after that was potentially flawed.
First you need to download a system and boot image from http://forum.xda-developers.com/tmobile-one-m9/general/please-read-rooting-using-twrp-t3069022. Note that the backup was created with a beta version of twrp so you have to modify the name of system file from system.emmc.win to system_image.emmc.win. Once this is done put it in your twrp folder.
The way i rectified the issue was to first flash the latest twrp recovery v2.8.7.0. The developer added a mount system as read only option in the mount section of twrp. Once you click on the checkbox. Go to restore the system backup, This time it will show up as a system image backup. Once restored, flash stock recovery and boot into os download the system update and it should go through without any hiccups.
Let me know if you have any questions
Click to expand...
Click to collapse
Thanks. I kind of figured it out by following the thread about how to take the phone back to stock for OTAs, and used fastboot to flash the system.emmc.win file (wihtout modifying it.) After that, the phone wouldn't boot properly (probably because I didn't edit the filename,) so I flashed my system backup file. That made it so I could boot. I then flashed the stock recovery and it installed just fine.
Only really outlining what I did in case anyone else has the same issues- they can do what I did to get it up and running again.
kc6wke said:
If you are 100% stock update using the ota from stock recovery.
Download and read here
Click to expand...
Click to collapse
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
nickmgray said:
Thanks for sharing. I've tried this method on two different stock T-Mobile M9 phones, but both return an "E: Failed to map file" error message when selecting apply from phone storage.
Any suggestions?
Click to expand...
Click to collapse
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
kc6wke said:
Are you placing the ota zip on internal or external sd?
It needs to be on the internal.
Click to expand...
Click to collapse
It's loaded to internal storage.
I made an ADB backup via TWRP of each partition (boot, system, data, cache) individually direct to my PC prior to flashing a new ROM. After flashing the new ROM, I realized I forgot to backup texts and wifi netwroks via Titanium Backup. I tried to restore each partition so I could go back and copy the texts and wifi networks but it didn't work. TWRP reported no OS installed and it didn't boot either. I did update the bootloader after I created the backup and am not sure if that's why it's failing.
Is there a way to extract the texts and wifi networks from the backed up file(s)? Do I need to flash a previous bootloader to get the backup to work?
Thanks
pongolo said:
I made an ADB backup via TWRP of each partition (boot, system, data, cache) individually direct to my PC prior to flashing a new ROM. After flashing the new ROM, I realized I forgot to backup texts and wifi netwroks via Titanium Backup. I tried to restore each partition so I could go back and copy the texts and wifi networks but it didn't work. TWRP reported no OS installed and it didn't boot either. I did update the bootloader after I created the backup and am not sure if that's why it's failing.
Is there a way to extract the texts and wifi networks from the backed up file(s)? Do I need to flash a previous bootloader to get the backup to work?
Thanks
Click to expand...
Click to collapse
I would say no but I'm drunk at the moment:laugh:. WiFi and text should be a part of data part of the backup. I see that you backup data so it should be there but I don't think you can do it the way you tried. Let's see what smarter people have to say.
pongolo said:
I made an ADB backup via TWRP of each partition (boot, system, data, cache) individually direct to my PC prior to flashing a new ROM. After flashing the new ROM, I realized I forgot to backup texts and wifi netwroks via Titanium Backup. I tried to restore each partition so I could go back and copy the texts and wifi networks but it didn't work. TWRP reported no OS installed and it didn't boot either. I did update the bootloader after I created the backup and am not sure if that's why it's failing.
Is there a way to extract the texts and wifi networks from the backed up file(s)? Do I need to flash a previous bootloader to get the backup to work?
Thanks
Click to expand...
Click to collapse
Nope, I've never heard of a way to extract anything from a TWRP backup file without restoring it. I've never had to flash a different bootloader to get a TWRP restore to work, even after the bootloader was upgraded by the new ROM I installed. I assume that the bootloader is restored when restoring the TWRP backup. How did you restore the backup? Did you restore the entire backup (all of the partitions) at the same time or try to do them one at a time? I've only had luck with restoring the entire backup at the same time.
alryder said:
Nope, I've never heard of a way to extract anything from a TWRP backup file without restoring it. I've never had to flash a different bootloader to get a TWRP restore to work, even after the bootloader was upgraded by the new ROM I installed. I assume that the bootloader is restored when restoring the TWRP backup. How did you restore the backup? Did you restore the entire backup (all of the partitions) at the same time or try to do them one at a time? I've only had luck with restoring the entire backup at the same time.
Click to expand...
Click to collapse
The first backup I made which had all the partitions in one file didn't seem to work properly as it did not copy the file locally to the PC. I tried it again but created a separate file for each partition which seemed to work so I have 4 files in total. I restored the files in this order: boot, system, data, cache. When it finished I got a message when exiting TWRP that there was no OS installed. I rebooted anyway and it failed.
Is there any way of restoring it to an emulator running on the PC?
pongolo said:
The first backup I made which had all the partitions in one file didn't seem to work properly as it did not copy the file locally to the PC. I tried it again but created a separate file for each partition which seemed to work so I have 4 files in total. I restored the files in this order: boot, system, data, cache. When it finished I got a message when exiting TWRP that there was no OS installed. I rebooted anyway and it failed.
Is there any way of restoring it to an emulator running on the PC?
Click to expand...
Click to collapse
It's likely too late for this now but I've backed up to and restored from a single file on my PC by following this guide quite a few times in the past without any issue. My thoughts are if the files won't restore to your phone they probably won't restore to an emulator either but I honestly have no experience with emulators.
Hi, I recently made an adb backup through twrp and now want to open the file with droid explorer. It asks for a password, when entering the one I had on the phone it doesn't open, I even tried restoring it through twrp -> didn't work, with booted phone it asked too for a password -> also didn't work. Do you guys know if twrp has a password which it sets automatically?
alryder said:
It's likely too late for this now but I've backed up to and restored from a single file on my PC by following this guide quite a few times in the past without any issue. My thoughts are if the files won't restore to your phone they probably won't restore to an emulator either but I honestly have no experience with emulators.
Click to expand...
Click to collapse
In the recovery terminal with the restored backup, delete "/data/system/locksettings.db". That should allow you to boot to system without a password. There is a benefit to removing PIN/pattern locks before making backups.