Related
I heard about it on my incredible but never experienced it... I just tried to restore a back up and both my back ups say md5 mismatch...
cwm 3.0.2.4
I am just trying to not have to redo all my stuff but I guess I"ll start now... just looking to see if I can prevent it in the future
Thank god, no. It caused havoc on my Inc but not now.
Sent from my ADR6400L using XDA App
Has anyone else experienced this? I have tried making backups before flashing, but have this problem. It creates the backup and if I try to go back to it, the MD5 mismatch error comes up. This is frustrating. Any help?
happened to me one time...i copied the file onto my laptop and then back to my sd card and it worked! not sure if just a coincidence but worth a try
patdroid1 said:
happened to me one time...i copied the file onto my laptop and then back to my sd card and it worked! not sure if just a coincidence but worth a try
Click to expand...
Click to collapse
Thanks, I'll try that, but if I have to do that every time, it's gonna get old. There has to be something going on that I can fix, I hope. Anyone else?
certainly not a fix if happening often...like i said only happened once to me...let me know if it works.
No luck. Copying to PC, deleting, and replacing didn't change the outcome. Thanks for the idea though. Anyone else run into this?
did you guys rename the files? The names CANNOT have spaces
Of all the backups I ever made this did happen one time. I tried everything I could think of and nothing worked. Sometimes the file is just corrupt and there is nothing you can do about it.
the only time i ever got md5 mismatch was when I renamed the file. returning it to original name and it flashed.
This issue has become a pain in my butt!! everytime i rename a backup, even without spaces, i got an MD5 mismatch upon trying to restore. Is there a solution? Ive already wiped the phone, reflashed the stock RUU and still no luck. I even formatted my sd card and left it completely blank.
Any help is appreciated!
bmerrill63 said:
This issue has become a pain in my butt!! everytime i rename a backup, even without spaces, i got an MD5 mismatch upon trying to restore. Is there a solution? Ive already wiped the phone, reflashed the stock RUU and still no luck. I even formatted my sd card and left it completely blank.
Any help is appreciated!
Click to expand...
Click to collapse
What are you renaming it to? I always rename my backups, and have never had issues. I usually name them something along the lines of: "20110519_BAMF_Remix_1-6-3."
I've heard of people having issues with ROM Manager. Are you creating and restoring your backups from there, or are you booting into clockwork to do them?
TheStick13 said:
What are you renaming it to? I always rename my backups, and have never had issues. I usually name them something along the lines of: "20110519_BAMF_Remix_1-6-3."
I've heard of people having issues with ROM Manager. Are you creating and restoring your backups from there, or are you booting into clockwork to do them?
Click to expand...
Click to collapse
I rename to something similar to what you do.
Typically I never create or restore from RM cause I've heard of others having issues. I really only use RM to rename the backups. I prefer to do it manually through CWM.
However since I haven't successfully been able to rename a backup, I have been using RM to do backups.
Sent by the Tbolt
bmerrill63 said:
I rename to something similar to what you do.
Typically I never create or restore from RM cause I've heard of others having issues. I really only use RM to rename the backups. I prefer to do it manually through CWM.
However since I haven't successfully been able to rename a backup, I have been using RM to do backups.
Sent by the Tbolt
Click to expand...
Click to collapse
Stupid question, I'm sure, but you aren't changing the names of any files INSIDE the backup folder, are you? Only the folder name needs to be changed.
I don't mean that to be insulting your intelligence, at all. Just verifying.
TheStick13 said:
Stupid question, I'm sure, but you aren't changing the names of any files INSIDE the backup folder, are you? Only the folder name needs to be changed.
I don't mean that to be insulting your intelligence, at all. Just verifying.
Click to expand...
Click to collapse
No offense taken, no I am only renaming the folder name itself. I don't get it.
Sent by the Tbolt
I have never been able to restore any backups. Even when I dont rename them. The only one that always works is the original backup of the original rom. Really annoying. Any fix yet?
Turb0wned said:
I have never been able to restore any backups. Even when I dont rename them. The only one that always works is the original backup of the original rom. Really annoying. Any fix yet?
Click to expand...
Click to collapse
I don't think there is any "fix" because I've never heard of anyone else with that problem. Maybe you are renaming the backups with spaces in the file names or you just got a bad SD card.
dirtyfingers said:
I don't think there is any "fix" because I've never heard of anyone else with that problem. Maybe you are renaming the backups with spaces in the file names or you just got a bad SD card.
Click to expand...
Click to collapse
I've had a similar problem with renaming the files. I'll usually add something like: (BAMF_1.7_imo2.5.1) right on to the end of the file name -without spaces- and I also get an md5 mismatch. If I go back and delete the section I added it works fine. I actually ran into this problem when I was reverting from gingerbread back to froyo once all the brick warnings were coming out, and I foolishly cleared data/factory reset, and then tried restoring my backup, which I hadn't yet removed my (addition) at the end and got the md5 error. Luckily I had a copy of an older version of the ROM which I flashed, and then went in with EStrongs and renamed my backup to its original name.
Cmotion said:
I've had a similar problem with renaming the files. I'll usually add something like: (BAMF_1.7_imo2.5.1) right on to the end of the file name -without spaces- and I also get an md5 mismatch. If I go back and delete the section I added it works fine. I actually ran into this problem when I was reverting from gingerbread back to froyo once all the brick warnings were coming out, and I foolishly cleared data/factory reset, and then tried restoring my backup, which I hadn't yet removed my (addition) at the end and got the md5 error. Luckily I had a copy of an older version of the ROM which I flashed, and then went in with EStrongs and renamed my backup to its original name.
Click to expand...
Click to collapse
Thats the thing, I haven't been renaming them anymore and I still always get the same error. Only one that doesn't give me the error is my original rom backup.
Turb0wned said:
Thats the thing, I haven't been renaming them anymore and I still always get the same error. Only one that doesn't give me the error is my original rom backup.
Click to expand...
Click to collapse
I had a buddy have the same thing happen to him. The only backup that would work was the original one that I made for him when I helped root his phone. After that he bought a cheap class 10 SD card off eBay and no backups from that card would work, md5 mismatch every time. It ended up just being a bogus card from a shady seller and after he got a new SD card everything worked well again.
Initial phone stats: DS Mod 1.55.531.3, hboot 1.45.0013, s-on/unlocked via HTC unlocker.
I'm trying to update my own phone to 1.63.531.2 via the PG59IMG.zip file found here, http://forum.xda-developers.com/showpost.php?p=17424340&postcount=24 , but I'm running into problems applying this update and keeping it after restoring a Nandroid backup. It would be a huge amount of work to set up my phone from square one, and I'd like to avoid the process if at all possible.
The steps I've followed (twice, now, with no joy) are the following:
* apply the update through the PG59IMG.zip
* flash CWM 5.0.2.7
* flash Superuser
* restore most recent Nandroid backup
* flash 1.63.531.2 boot image (for wi-fi fix)
And this puts me back at my starting point, with the 1.63.531.2 update not applied.
I know I'm going about this the wrong way, but I can't figure out the correct method to make this work. The fact that I flashed the DS Mod 1.55.531.3 ROM back after unlocking might have something to do with this, however, I just can't nail down why. Really could some help to make this work.
TIA for any suggestions --
--
KingCheetah
hey, real quick, after flashing the 1.63.531.2 update, instead of restoring your full nandoid of 1.55.531.3, go to 'advanced restore', choose that nandroid, and choose only 'restore data'. that will put all your apps and data onto the new update, rather than flashing you all the way back to what you had before.
you could also backup and restore your data with an app called Mybackup Root, or some people use Titanium Backup. I personally like using the advanced data restore in CWM, or else Mybackup.
Yogi, I thought your suggestion would be a smoking gun. However, I'm having the same problem as described in this thread: http://forum.xda-developers.com/showthread.php?p=25431819#post25431819
Might you have any suggestions for addressing the md5 problem? I'm coming up empty...
Thanks for your help --
--
KingChetah
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested? also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
good luck and keep us posted!
yogi2010 said:
yeah, come to think of it, I've had that problem before as well. did you try what xmc suggested?
Click to expand...
Click to collapse
Yes, and for the backup I want to restore, all the md5s are the same between the files and what is listed in the nandroid.md5 file. So, the method XMC suggested really doesn't do anything.
yogi2010 said:
also, perhaps try the Modaco 4.0.0.9 version of CWM to do the advanced data restore... if my memory serves me, I have had more success overall with that version. unfortunately that's about all I got!
Click to expand...
Click to collapse
Hmm, okay, I'll give that a try. Weird that CWM 5.0.2.7 has this problem. Also frustrating.
yogi2010 said:
the other sugestion would be to flash your full nandroid, then use Mybackup Root to back everything up. then after updating, DL the app again and restore.
Click to expand...
Click to collapse
I'll keep this as the last resort, because I'd rather not have to download an app for just this purpose. Nandroid backups have served me fine so far. Call me a minimalist.
I'll try Modaco and see what happens. Thanks much for the idea to try.
--
King Cheetah
Sadness
Using Modaco didn't work. Although the Advanced Restore sees the file and appears to run successfully, it says it can't find a data.img file and an Android.img file, so it doesn't restore the info.
So, I guess it's down to trying Mybackup Root and see what happens. Getting tired of redoing this process over and over.
Why can't things "just work" in these situations?
--
KingCheetah
check the other thread....problems with restoring backup
---------- Post added at 05:11 PM ---------- Previous post was at 05:08 PM ----------
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
xmc wildchild22 said:
or actually...just flash the data.img through fastboot....its ten times easier
but the data.img in the same directory as adb and fastboot....then run the two commands with your phone in the bootloader
fastboot erase data
fastboot flash data data.img
Click to expand...
Click to collapse
The problem with this is the file "data.img" doesn't exist in a Nandroid backup. As I stated in my previous message, the Advanced Restore process tossed up a message that the file didn't exist (which is correct).
The files within a given Nandroid backup folder are the following:
.android_secure.vfat.tar
boot.img
cache.ext4.tar
data.ext4.tar
nandroid.md5
recovery.img
system.ext4.tar
From the Advanced Restore problem thread (http://forum.xda-developers.com/showthread.php?t=1624319):
xmc wildchild22 said:
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
Click to expand...
Click to collapse
I would love to try this, but since the 1.63 update is a PM59IMG.zip, I can't open it with a zip file manager--it throws up a "central directory not found" error. Unless there's another program besides 7zip that's needed to handle this type of zip file...
Edit: I just realized that, as you can see from the file list above, a Nandroid backup also doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
Banging one's head against the keyboard does little constructive good, but it's really tempting at this point --
--
KingCheetah
just try opening it with a plain windows explorer
xmc wildchild22 said:
just try opening it with a plain windows explorer
Click to expand...
Click to collapse
Using the "Explore" option from the right-click context menu in Windows Explorer gives the following error: "The Compressed (zipped) Folder is invalid or corrupted." (Since archive files on my laptop are associated with 7zip, this is the only method by which I can access Win XP's native archive file handling.)
This has been the case with all PM59IMG.zip files--they don't register as normal zip files.
Thanks for the suggestion, though --
--
KingCheetah
hmm...maybe tht zip is corrupted because it works for me....DL this --> http://tinyw.in/Mzg2
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
KingCheetah said:
Nope, not corrupted because it works just fine to update my phone to 1.63 (as stated before, I've done this twice now). Also, that's the exact same source from whence I downloaded my copy of the file. The PM59MG.zip for 1.55.531.3 gives exactly the same error, and I used that without difficulty as well.
Click to expand...
Click to collapse
Use winrar to open the PG59IMG.zip files - that's what I used to make all the custom ones with, and also what I used to open the leaked ones we started from.
You won't be able to edit existing leaked ones, because they are locked and have an HTC signature.
Sent from a digital distance.
Thanks for the pointer, Blue, and I'll keep this in mind. But as I added to my previous post (#8), I realized that a Nandroid backup doesn't have a "system.img" file--it has a "system.ext4.tar," but not "system.img." So being able to pull anything from a PM59IMG.zip file is a moot point at this juncture.
I think I'm going to have to wait for a 1.63 ROM that can be installed through CWM rather than the PM59IMG.zip method. The DS Mod 1.55.531.3 worked well for me, and all apps/data were just there after I flashed it. Maybe I just got lucky with the process I followed previously, who knows? (http://forum.xda-developers.com/showthread.php?t=1508406&page=4 post #39)
At any rate, I've got a truly mean headache from working on this all day. Time for a break with a bit of ice on ye old cervical vertebrae.
Thanks again for chiming in --
--
KingCheetah
No prob, didn't read through and shot from the hip on the last post I saw, out at dinner and skimming the forums on smoke breaks
Sent from a digital distance.
does anyone know the deal with the implementation of tar backups? I think that came into play at some point, and I wonder if that has anything to do with anything.
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery. it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
anyway, hopefully we'll get this all sorted out. take it easy!
well .tar are used ever since cwm started working with ext4....maybe imgs are only ext3 or lower or its just inefficient
On that note, I did use the modaco 4.0.0.9 recovery to make the nandroids I pulled the system images from to get the bases from which I de-odexed, and when finished I uploaded to my host and they are the de-odexed bases I posted in dev.
I am pretty sure I went with modaco recovery for that because cwm 5.0.2.7 output tar files and it just saved a step in the process.
If you are working with the .tar files then jump on linux to unarchive them if that's what you are trying to do.
I just ran the deodex process using windows, because the first working deodex tool I found was a windows tool.
Generally I use modaco .9 for nandroids I want to work with in windows, and cwm 5 for nandroids I want to work with in linux.
We're probably leaving the restaurant soon, if we split up I'll actually read back through the thread when I get home and see if I have anything else to add.
Sent from a digital distance.
Yogi, you're brilliant!
yogi2010 said:
I just checked a backup I made with the Modaco CWM, and the files in it are all .img files, including data. and I know for a fact I have done backups and advanced data restores with that recovery.
Click to expand...
Click to collapse
[facepalm] Of course! This is why my Advanced Restore attempt with Modaco failed--because I used the CWM 5.0.2.7 backup, which did not have the files Modaco would have referenced. Duh! I wasn't even thinking along the lines of a file type mismatch between the two recoveries. Baka baka baka...
yogi2010 said:
it would be a hassle, but if you get re-energized you might make the backup and do the restore with Modaco. definitely would be a hassle if it didn't work, but you could also make a backup with Mybackup, and have that ready too, as well as probably have a data.img to try and flash thru fastboot like xmc suggested.
Click to expand...
Click to collapse
At this point, not a hassle, but the best chance to accomplish this thing with a minimum of fuss and bother. I'll give this a shot right after a bit 'o java. Thank you, Yogi, for highlighting something that should have been obvious to me when Modaco gave the error message that "data.img" didn't exist. Oy!
However, this still leaves unanswered the question of why CWM 5.0.2.7 is tossing up the md5 mismatch error when one tries to use Advance Restore, and that files aren't seen by CWM via Advance Restore until one accesses regular Restore. Paperskye is having the exact same problem in this thread: http://forum.xda-developers.com/showthread.php?t=1624319 . Should this be brought to the attention of the CWM devs? It really seems like a rather show-stopping error for CWM...unless Advanced Restore isn't really used with 5.0.2.7 and the MT4GS. There just doesn't seem to be a good reason for the observed behavior.
Many thanks for your encouragement. I'll report back with results on the next try with Modaco --
--
KingCheetah
It's a beautiful thing!
Using Modaco for my backup prior to the update, then Advanced Restore of data afterward = perfect restore of my phone environment with 1.63 on board. Done with as little fuss as I was hoping to encounter. Yogi, you get the prize. The only thing I had to manually put back was my custom boot animation, but that's trivial.
I think I'll just leave Modaco on as my recovery for now, since AR is functional with it and CWM 5.0.2.7 is not. Makes me wonder, from just an everyday backup standpoint, is there any real advantage of CWM over Modaco? I wish there was more information on how the recovery module functions on the CWM website--I'd like to read up on it for educational purposes. Guess I'll do a Google to find more.
So ridiculously happy right now. In a stew of things going wrong, at least something went right.
Big rumbling purr of gratitude --
--
KingCheetah
Hello,
I recently rooted and installed a custom ROM CM10 nightly onto my transformer, and proceeded to wipe data as normal. I went to do it, and it was taking a long time, 5-6-7-8 mins passed and I thought something is wrong. So I force turned it off. Not that all it said for that time was "formatting /data..." or something.
Well, it failed to boot as expected, so I tried wiping again with no luck. Went and flashed TWRP recovery and it's showing errors:
E:Unable to mount '/data' (tw_mount)
E:failed to mount /data (Invalid argument)
I'm not sure how to proceed due to lack of knowledge. I noticed there's a file manager and terminal on this recovery so perhaps it can be fixed using those, or ADB or something.
Either way, I would like to request help from the TF300T community.
Thanks in advance,
Kris
Problem solved. Made a new blob without the bootloader included and flash it, then the system told me the data was unreadable and it fixed itself after that.
linkandzelda said:
Problem solved. Made a new blob without the bootloader included and flash it, then the system told me the data was unreadable and it fixed itself after that.
Click to expand...
Click to collapse
Greetings. I did, so far as I can tell, this exact same thing. I feel like I'm taking crazy pills.
Kind of wandering if someone put a "wipe data" label on the "destroy your transformer" button by mistake.
Can you please elaborate on what you mean by "made a new blob without the bootloader included"?
Are you meaning new zip without the boot.blob? I'm tripping over the words. Or maybe I simply do not understand what you are meaning.
I would be so grateful if I could get anywhere with this.
ogredeschnique said:
Greetings. I did, so far as I can tell, this exact same thing. I feel like I'm taking crazy pills.
Kind of wandering if someone put a "wipe data" label on the "destroy your transformer" button by mistake.
Can you please elaborate on what you mean by "made a new blob without the bootloader included"?
Are you meaning new zip without the boot.blob? I'm tripping over the words. Or maybe I simply do not understand what you are meaning.
I would be so grateful if I could get anywhere with this.
Click to expand...
Click to collapse
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
linkandzelda said:
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
Click to expand...
Click to collapse
i had the same problem during flashing cm10 on my brandnew tf300t.
the system could not mount /data...
...solved this problem with the "wipe -> format data" command in TWRP.
sounds too easy?
How can you Wipe Data, if the /data isn't/can't be mounted?
I'm having this same issue with my RazrMaxx...
I posted my issue here: http://forum.xda-developers.com/showthread.php?p=35222826#post35222826
Z1013 said:
i had the same problem during flashing cm10 on my brandnew tf300t.
the system could not mount /data...
...solved this problem with the "wipe -> format data" command in TWRP.
sounds too easy?
Click to expand...
Click to collapse
Well, in my opinion, I think the rom wasn't readable or working. If you have taken a backup before flashing the nightly rom, you can restore it.
linkandzelda said:
I don't remember the specifics, but are you familiar with using fastboot to flash .blob files? You use this to flash the new recoveries over, etc. First off I used the blob tools I found around here to extract the various parts of the stock blob I got from the ASUS site. After that, I rebuilt it simply containing the system and the kernel. Then I flashed that .blob file to the device, and it decided to boot up and tell me my data was ruined and gave me the option of fixing it. So, I let it fix itself and that's how I got out if it.
Click to expand...
Click to collapse
Just did this with my tf300t last night. Do you still have the blob files?
I'm noticing that FlashFire has the option to backup the system parition file based. I'm wondering if someone who has flashed the PR ROM could simply do a restore of a STOCK ATT system partition backed up this way and if it would work? If anyone wants to try, I can make a backup and upload it and post a link.. Let me know!
petermg said:
I'm noticing that FlashFire has the option to backup the system parition file based. I'm wondering if someone who has flashed the PR ROM could simply do a restore of a STOCK ATT system partition backed up this way and if it would work? If anyone wants to try, I can make a backup and upload it and post a link.. Let me know!
Click to expand...
Click to collapse
Sounds like a hard brick waiting to happen.
uly609 said:
Sounds like a hard brick waiting to happen.
Click to expand...
Click to collapse
Yeah.. probably right. It was real late when I posted that LOL
Actually doing a system restore via file based shouldn't hard brick the phone. Only if it was raw based possibly, but either way it would only be the system position so the kdz/tot would still be able to be flashed to the phone as before. This might work! Or at least be a good base to try.
petermg said:
Actually doing a system restore via file based shouldn't hard brick the phone. Only if it was raw based possibly, but either way it would only be the system position so the kdz/tot would still be able to be flashed to the phone as before. This might work! Or at least be a good base to try.
Click to expand...
Click to collapse
I agree with this theory. It should only flash the system over the system. You would have to make sure the boot loader is correct for the system rom. So say a 10b bootloader for an equivalent 10bPR rom.
(If any of the above is confusing or slightly off, I blame it on the fact I have been battling a bad virus this week with a bad headache.)
I just warrantied my PR rom device a few weeks ago, or else I would have tried this for you.
Edit: You would also have to edit the script in the file to flash to designate the correct partition to flash the system to.
CAG-man said:
I agree with this theory. It should only flash the system over the system. You would have to make sure the boot loader is correct for the system rom. So say a 10b bootloader for an equivalent 10bPR rom.
(If any of the above is confusing or slightly off, I blame it on the fact I have been battling a bad virus this week with a bad headache.)
I just warrantied my PR rom device a few weeks ago, or else I would have tried this for you.
Edit: You would also have to edit the script in the file to flash to designate the correct partition to flash the system to.
Click to expand...
Click to collapse
Unless it just extracts the tar'd files it copied from the system partition of the stock device. Still some ambiguity regarding that app. For example, it shows no option to allow me to make backups on the external SD card...
petermg said:
Unless it just extracts the tar'd files it copied from the system partition of the stock device. Still some ambiguity regarding that app. For example, it shows no option to allow me to make backups on the external SD card...
Click to expand...
Click to collapse
I would think it still needs an address as to where to put the extracted files.
I will look and see if I have any twrp backups on my computer from some of the roms I made. I have never fully looked through and studied the backups as much as I used them for system dumps. It just seems to make since that the recovery would need to know where to write the system files. Just flashing an app is alright without the address.
In writing the flashing script for ROMs, I have always had to give the recovery the address as to where to write the system files or else it would result in a flash failure or soft brick.
I may be writing my scripts wrong too. I just know what works for me.
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
mark7807 said:
So I tried my first Nandroid backup today using TWRP and a howtogeek - "How to Back Up and Restore Your Android Phone with TWRP" guide I found off a quick google search.
Basically TWRP, backup(boot,system,data), reboot to android, shut down, twrp-restore then reboot.
When I would reboot after TWRP-restore, it shows the typical bootloader corrupt error msg.
Shuts down again, shows the bootloader msg, then goes into TWRP, asks for my decrypt password, then begins to run an openrecovery script (I think?) of some sort. I then go to reboot my phone again, bang factory reset mode.
I hope I'm not alone here.:cyclops: I'd just really love to be able to backup/image my phone entirely so I can try out a few custom roms, and for general knowledge sake.
thanks!:silly:
Click to expand...
Click to collapse
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
exad said:
What version of TWRP have you been using? I understand, RC2 has issues with properly restoring a backup. (RC is release candidate and is not considered fully stable, however, works well enough to flash custom roms and such).
The partitions on the pixel are set up in a more complex way than previously seen on many android phones, which is why there's no perfectly stable version of TWRP yet. You could try using RC1 to see if you get better luck backing up and restoring, however, you should assume that you may run into other issues and be prepared to deal with them should they arise.
Click to expand...
Click to collapse
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
mark7807 said:
I'm running 3.1.0-0RC2 so maybe I'll try RC1. Normally I'd just go off and try everything but unfortunately I'm not in a situation I can simply play with my Pixel and potentially brick it leaving me without a phone for who knows how long.
I don't think there would be any harm with playing with RC1 but I'll research a little bit more into it and see what I can find out first. I heard the partitions are split for redundancy(?) for firmware upgrades and dual-booting. That's something all else on it's own as I've REALLY wanted to get my phone ultimately on a Multi-Rom setup but it seems way too complicated for me at the moment to try on my own even though I'm generally good with this stuff..
Thanks exad for the insight. Any other help is greatly appreciated.
Click to expand...
Click to collapse
RC1 and backup system image, vendor image, data and boot.
robocuff said:
I would say use RC1 too. I've used it and never had a problem with it other than the occasional failure to decrypt which is no big deal. Just reboot back into recovery. I would add though, instead of backing up system, backup system image. Also vendor image. If you back up system instead of system image you'll more than likely run into battery drain problems. I'm not sure what causes it but it'll cut your battery life down to only several hours. Using system image doesn't cause that problem.
If you should happen to accidentally backup system instead of system image it's not a huge deal to fix it though. If you're on stock just download the factory image that you are currently on, extract the system.img file and flash it using fastboot. If you're on a custom rom, a dirty flash of the rom will fix it.
Click to expand...
Click to collapse
TheBurgh said:
RC1 and backup system image, vendor image, data and boot.
Click to expand...
Click to collapse
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
mark7807 said:
Thanks again guys,
I ran a
fastboot boot twrp.zip to boot to what I thought was like a "live cd" version of twrp
with the rc1 .img and .zip in the sdcard directory I installed the .zip
booted my phone and it forces to recovery everytime now.
did I upset something?
I mean at this point, I could factory reset the google pixel all from the very beginning of time. boot/system the whole shabang, but I think this could be a good lesson from me if I could boot back to system out of this..
Okay. I have RC1 on here and have backed up to USB. I'm extremely tired and going to bed. I'll report back on how the restore goes. THANK YOU ALL!!!
Click to expand...
Click to collapse
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
mark7807 said:
Okay so, I stayed up a little late and tried a restore. I got this error near the end of the restore "extractTarFork() process ended with error: 255" in which resulted in corruption of files and a failed restore. Was I supposed to unmount data? Is there any reason I can't backup all partitions?
Click to expand...
Click to collapse
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
TheBurgh said:
Not sure where to direct you at this point. I have always used RC1 and backed up system image, vendor image, data and boot and never had a problem restoring. Someone with better knowledge will come around.
Click to expand...
Click to collapse
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
mark7807 said:
Yeah very strange I did exactly what you told me to do as well. Any changes to partitions I backup if my phone is rooted by chance??
Click to expand...
Click to collapse
Not that I am aware of. Mine is rooted and backups have been smooth sailing.
I recently attempted creating a nandroid backup via TWRP on my rooted Pixel and I'm consistently getting an error: 'cannot create [path]\backup file" message from TWRP. Is there a permission issue that I've overlooked here or does anyone have any thoughts as to why my rooted Pixel would be denying TWRP authority to create the backup?
Thanks
What version of twrp ?
I only use rc1, never seen this.
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
pstgh said:
Yep- RC1. I'm thinking it's in 'read only' mode or something because as soon as it attempts to create the folder/file- no-go.
Click to expand...
Click to collapse
When you boot into TWRP did it ask for your unlock PIN? If it doesn't/didn't, either keep rebooting into recovery or turn the phone off and go back into recovery until TWRP does ask for your encryption PIN. Sometimes TWRP doesn't ask, and without the PIN being entered, it can't write to the internal storage.
If you click "Install" in TWRP and see a bunch of gobbledygook it's because the internal storage is still encrypted so TWRP can't do anything with it.
You could probably use USB OTG through the USB-C connector, though, to do a backup to it, if you need to.
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
pstgh said:
Tried it again and it worked flawlessly.... it seems sort of buggy in that sometimes it presents the 'pattern' security lock that I use and sometimes it doesn't. After booting up in the bootloader and fastbooting the TWRP boot image slowly and methodically, the security pattern came up and all is perfect- thanks.
---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------
Now I'm wondering how to best move that backup folder (or a copy of it) over to Google Drive? I have root explorer, but not sure if it is capable of mounting to Google Drive.. any thoughts on best practices here would be appreciated.
Thanks
Click to expand...
Click to collapse
I can't confirm since I've yet to do a successful backup but... Flashify Pro version looks like an option???
also
Anyone know when TWRP 3.1.0-0 will be out for Pixel? Looks like it addresses boot slots which off first glance seems like quite a fundamental feature no?
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
pstgh said:
Thanks... I'm thinking I'll just adb pull the file over to my desktop... not sure.
Click to expand...
Click to collapse
Root Explorer does have support for Google Drive. In Root Explorer touch the plus sign in the lower right corner and in the menu that opens choose Google Drive tab.
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
pstgh said:
Can get Root Explorer to connect to Google Drive, but when I select all of the backup files from my Pixel's TWRP backup folder, my only choices are to cut or copy them- so I tried both and then RE creates this little clipboard icon that you presumably click on to paste them once you've opened the proper GD folder.... so I tried that and in both cases (cut and copy) it says 'fail'.... ? Thoughts? I've given RE permission to manage folders and files in GD.
Click to expand...
Click to collapse
It sounds like you've got the right idea. Cut will move the files, copy will do just that. You choose one of the two and browse to the Google Drive tab, find the folder you want to use and then use the little clipboard thing to transfer the files to that folder. If that's what you're doing, the only thing I can think of right off the top of my head would be that you don't have enough space left on Google Drive for the size of the files you're trying to transfer. Try a picture or something and see if it takes that. If so, I'd suspect lack of Drive space is the reason it fails.