I backed up my phone, tossed it onto my computer, used the flashall.bat to wipe my phone, and tried to use TWRP to restore the backup. But now it says the device is corrupt. How do I fix this?
Spartan117H3 said:
I backed up my phone, tossed it onto my computer, used the flashall.bat to wipe my phone, and tried to use TWRP to restore the backup. But now it says the device is corrupt. How do I fix this?
Click to expand...
Click to collapse
What partitions did you restore from twrp?? And, did you do an Advanced wipe in twrp before you restored your backup? Were you just trying to see if twrp worked or what???
Badger50 said:
What partitions did you restore from twrp?? And, did you do an Advanced wipe in twrp before you restored your backup? Were you just trying to see if twrp worked or what???
Click to expand...
Click to collapse
Boot, system, data, vendor. No, I didn't, I don't remember needing to do that in ages with previous phones. Yeah I was troubleshooting an issue on my phone and I figured I'd just be able to restore back to my backup.
Spartan117H3 said:
Boot, system, data, vendor. No, I didn't, I don't remember needing to do that in ages with previous phones. Yeah I was troubleshooting an issue on my phone and I figured I'd just be able to restore back to my backup.
Click to expand...
Click to collapse
Boot, system, and data are ok to restore. You can get into trouble when trying to restore the vendor. The P2XL has a little bit of a learning curve, but it's doable.
Spartan117H3 said:
Boot, system, data, vendor. No, I didn't, I don't remember needing to do that in ages with previous phones. Yeah I was troubleshooting an issue on my phone and I figured I'd just be able to restore back to my backup.
Click to expand...
Click to collapse
On the pixels I always do, boot, vendor image, system image, and data.
Badger50 said:
Boot, system, and data are ok to restore. You can get into trouble when trying to restore the vendor. The P2XL has a little bit of a learning curve, but it's doable.
Click to expand...
Click to collapse
Ah. That's probably it. Back when I had the N6P you had to have a certain vendor image or else you get an error message.
I skipped the vendor and it restored just fine.
mac796 said:
On the pixels I always do, boot, vendor image, system image, and data.
Click to expand...
Click to collapse
The images take up more space, and do we still have to do vendor? Cause that was what was causing me issues.
Spartan117H3 said:
Ah. That's probably it. Back when I had the N6P you had to have a certain vendor image or else you get an error message.
I skipped the vendor and it restored just fine.
The images take up more space, and do we still have to do vendor? Cause that was what was causing me issues.
Click to expand...
Click to collapse
Yeah I wouldn't do vendor it causes problems vendor image will be okay. Also if you get corrupt device you're probably going to have to do the factory image with the w I haven't found a way around it yet. If you have a backup of stock on your phone you could try that that might get you out of it
Also if you're on stock you can just do factory reset in TWRP and just restore Boot and data that's all you really need
mac796 said:
Yeah I wouldn't do vendor it causes problems vendor image will be okay. Also if you get corrupt device you're probably going to have to do the factory image with the w I haven't found a way around it yet. If you have a backup of stock on your phone you could try that that might get you out of it
Also if you're on stock you can just do factory reset in TWRP and just restore Boot and data that's all you really need
Click to expand...
Click to collapse
Nah my restore worked after not restoring the vendor. I was just wondering if backing up the vendor is even needed anymore. I don't remember what it was for, I just remembered that if it was different from your rom version it'd give you an error. But yeah I'm on stock.
Spartan117H3 said:
Nah my restore worked after not restoring the vendor. I was just wondering if backing up the vendor is even needed anymore. I don't remember what it was for, I just remembered that if it was different from your rom version it'd give you an error. But yeah I'm on stock.
Click to expand...
Click to collapse
Yeah I back it up but on stock I never restore it there's no reason to I just restore Boot and data. Your custom kernel and root and everything will restore
Spartan117H3 said:
I backed up my phone, tossed it onto my computer, used the flashall.bat to wipe my phone, and tried to use TWRP to restore the backup. But now it says the device is corrupt. How do I fix this?
Click to expand...
Click to collapse
This happened to me when i changed the partition.
i wonder if the flash.bat image is a different version of Android than what's on the twrp backup
GridironTrenches said:
i wonder if the flash.bat image is a different version of Android than what's on the twrp backup
Click to expand...
Click to collapse
If your backing up/restoring the system, boot, and data, why would it change?? The flash-all.bat is a script anyway. Not sure I understand what your getting at????
Badger50 said:
If your backing up/restoring the system, boot, and data, why would it change?? The flash-all.bat is a script anyway. Not sure I understand what your getting at????
Click to expand...
Click to collapse
i meant the flashed OTA image could be a different version of Android than what's on the twrp backup. maybe a vendor or bootloader image is mismatched but im not sure
Related
i think i forgot to wipe cache & slavik before i flashed the custom rom
if i will do it now there is a chance i will lose my IMEI or S/N because of it?
i already lost my IMEI twice and i cant take a chance of losing it again
DrCow said:
i think i forgot to wipe cache & slavik before i flashed the custom rom
if i will do it now there is a chance i will lose my IMEI or S/N because of it?
i already lost my IMEI twice and i cant take a chance of losing it again
Click to expand...
Click to collapse
No, it'd not cause any problem. Just take the EFS bakup (You haven't did it before?), and then feel free to do anything on your own. And man, It's Dalvik Cache not salvik.
m.b.jikre said:
No, it'd not cause any problem. Just take the EFS bakup (You haven't did it before?), and then feel free to do anything on your own. And man, It's Dalvik Cache not salvik.
Click to expand...
Click to collapse
i had a backup of the EFS
i tried different ways to backup my EFS folder
but none of them actually worked
DrCow said:
i had a backup of the EFS
i tried different ways to backup my EFS folder
but none of them actually worked
Click to expand...
Click to collapse
Try it with philz recovery, you'd found an option under 'Backup and restore >> Custom backup to sdcard0 / 1', you've to uncheck all options except efs (because it flags a caution/warning there that efs backup must be made seperately).
Otherwise try backing up your efs content with Dr.Ketan's mutitool, download: http://d-h.st/wgy
Description: http://forum.xda-developers.com/showthread.php?t=2445480
m.b.jikre said:
Try it with philz recovery, you'd found an option under 'Backup and restore >> Custom backup to sdcard0 / 1', you've to uncheck all options except efs (because it flags a caution/warning there that efs backup must be made seperately).
Otherwise try backing up your efs content with Dr.Ketan's mutitool, download: http://d-h.st/wgy
Discription: http://forum.xda-developers.com/showthread.php?t=2445480
Click to expand...
Click to collapse
i guess i will do it with Philz
anyway i dont have my phone atm so i cant try that
the reason im thinking i didnt wiped cache is because it's take quite a while for the phone to boot up
DrCow said:
i guess i will do it with Philz
anyway i dont have my phone atm so i cant try that
the reason im thinking i didnt wiped cache is because it's take quite a while for the phone to boot up
Click to expand...
Click to collapse
For first use only, and for optimising apps and cache for same. From second boot it doesn't check.
m.b.jikre said:
For first use only, and for optimising apps and cache for same. From second boot it doesn't check.
Click to expand...
Click to collapse
and if it does take a while to boot after the first time?
it's mean i didnt wiped?
DrCow said:
and if it does take a while to boot after the first time?
it's mean i didnt wiped?
Click to expand...
Click to collapse
I mean when you wipe the cache then it optimises apps for only once, thereafter it'd not needed until you tried to do it. And comin' to point it'd not stuck at boot, it flags, after rebooting action on screen that 'Optimising apps xxx from xxx'. And this definately done if you are used your current rom for a while.
m.b.jikre said:
I mean when you wipe the cache then it optimises apps for only once, thereafter it'd not needed until you tried to do it. And comin' to point it'd not stuck at boot, it flags, after rebooting action on screen that 'Optimising apps xxx from xxx'. And this definately done if you are used your current rom for a while.
Click to expand...
Click to collapse
i only rebooted my phone like twice or so after i flashed the rom
and honestly i dont remember if it did anything or went straight to the language select menu
DrCow said:
i only rebooted my phone like twice or so after i flashed the rom
and honestly i dont remember if it did anything or went straight to the language select menu
Click to expand...
Click to collapse
It does man, maybe you wasn't looking at the phone. And it is no. of applications dependent so for time it'd take less for less apps. I just want to know how you are in need to Wipe cache?
m.b.jikre said:
It does man, maybe you wasn't looking at the phone. And it is no. of applications dependent so for time it'd take less for less apps. I just want to know how you are in need to Wipe cache?
Click to expand...
Click to collapse
Like i said i dont have my phone with me atm
so i cant really check if it actually boot without too many delays
So i got my phone back
It does get stuck about 10 seconds on the samsung logo
Dunno if its should be like this because i dont really remember how it was
Sent from my GT-N7100 using xda app-developers app
Hi guys,
I seem to have this problem where my nandroid backup from TWRP won't boot. I can only get it to boot after flashing the Rom over again after the store (this doesn't erase the data and all my file are still there, I just have to make sure I'm flashing the same Rom version as was part of the backup to avoid issues . But I was wondering if there is something else I should be doing here. I've used TWRP in the past and was just able to back up and restore no problem.
When I back up I make sure my system partition is mounted and I usually backup the default selections (boot/data/system, EFS) . My feeling is somehow the boot partition gets corrupted and won't allow the phone to continue booting, but I'm not sure why?
Any ideas? I'm using TWRP version 3.0.2-0. This happens when restoring nandroid for any rom (so far tried with oxygen/hydrogen/miui and cm14).
Thanks in advance.
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
borijess said:
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
Click to expand...
Click to collapse
Standard factory reset on TWRP will erase data, cache and Calvin cache without wiping internal SD card. That's what most people use.
piotrus22 said:
Hi guys,
I seem to have this problem where my nandroid backup from TWRP won't boot. I can only get it to boot after flashing the Rom over again after the store (this doesn't erase the data and all my file are still there, I just have to make sure I'm flashing the same Rom version as was part of the backup to avoid issues . But I was wondering if there is something else I should be doing here. I've used TWRP in the past and was just able to back up and restore no problem.
When I back up I make sure my system partition is mounted and I usually backup the default selections (boot/data/system, EFS) . My feeling is somehow the boot partition gets corrupted and won't allow the phone to continue booting, but I'm not sure why?
Any ideas? I'm using TWRP version 3.0.2-0. This happens when restoring nandroid for any rom (so far tried with oxygen/hydrogen/miui and cm14).
Thanks in advance.
Click to expand...
Click to collapse
I don't have any solution for you but I can certainly concur. I've seen this behaviour as well but not as consistently as what you are describing. About 1/3rd of the time my restores don't work as you mentioned and I have to dirty flash the rom to get it to boot. Sometimes the restore even errors out while restoring the System partition in which case I just dirty flash. This is like my 9th or so Android device since Samsung released the SGS1 in whatever year that was and this is the first phone I've ever had this problem with. On previous phones it would happen rarely but nothing like it does on the OP3.
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
borijess said:
I have question regarding TWRP. I always had a phone with an external SD card. This will be my first phone with no external memory. When I install a new ROM I always wiped internal, factory reset and cleared cache. Now can't do that anymore cause that will wipe my internal card and lose my nandroid backup. What are you guys wiping right before you install a ROM?
Click to expand...
Click to collapse
You can either not wipe internal storage (that is what I do usually) or you can buy an OTG adapter. I think TWRP supports it for our device. You can always copy off your backups via USB then wipe internal then copy your backups back too I think.
Did you for once try wiping the complete device after backing up nans on external storage and thn trying restoring? That would make a difference
Dr-Hack said:
Did you for once try wiping the complete device after backing up nans on external storage and thn trying restoring? That would make a difference
Click to expand...
Click to collapse
What?
piotrus22 said:
What?
Click to expand...
Click to collapse
I think he is asking to do below procedure -
1.Copy your nandroid backup and other imp stuff to computer
2.boot into TWRP
3.wipe all partitions including internal storage
4.copy nandroid backup to phone
5.restore backup through TWRP
Did you mount system to restore backup?
null0seven said:
Did you mount system to restore backup?
Click to expand...
Click to collapse
Yep of course.
JumboMan said:
I think he is asking to do below procedure -
1.Copy your nandroid backup and other imp stuff to computer
2.boot into TWRP
3.wipe all partitions including internal storage
4.copy nandroid backup to phone
5.restore backup through TWRP
Click to expand...
Click to collapse
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
piotrus22 said:
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
Click to expand...
Click to collapse
its one time procedure. Subsequent restore will be fine.
May be different versions of TWRP will help you with this problem
is this issue had been resolved? because i have also the same problem.. whats the fix for this?
piotrus22 said:
OK. Have not tried this, why would this work and fix my problem? Do I only have to do it once and then all subsequent restores would be fine? Is it a problem with my TWRP? Phone?
Click to expand...
Click to collapse
How did you fix your problem? I cant restore my backup also..
it says restore complete but stock in boot logo after... any fix?
toto_vanir said:
How did you fix your problem? I cant restore my backup also..
it says restore complete but stock in boot logo after... any fix?
Click to expand...
Click to collapse
Hey man. No I never fixed it. Just flash your Rom over it and it should boot fine.
I made a backup of my 5x when it was running rooted/xposed 6.0.1 but then decided to update to 7.1.1 to try out the new features. But now I really miss a lot of xposed modules so I decided that I want to restore my 6.0.1 backup that I made a couple of weeks ago. So I flashed the 6.0.1 factory image from Google's developer website and was able to successfully boot into Marshmallow again. However after installing TWRP I tried restoring the backup (through USB OTG) after wiping system and cache and a doing factory reset but it pauses on "restoring system image" for a brief moment then proceeds to reboot by itself despite that it's only 27% complete. The reboot however does not go to completion and so the phone is stuck in a bootloop. I'm really not sure where the problem is here. Is it TWRP? Or the backup file? What can I do?
Which version of TWRP have you used? By any chance the backup also contained EFS?
marioemp2k7 said:
Which version of TWRP have you used? By any chance the backup also contained EFS?
Click to expand...
Click to collapse
I used version 3.0.2-2.
And isn't EFS supposed to be backed up anyway? I just checked the backup folder and it contains 4 files that begin with "efs". Should I delete those and try again?
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
marioemp2k7 said:
Format everything from TWRP except internal storage. Restore your backup without EFS. Next time you want to come back to another version just be sure that you also backup the vendor or you flash the vendor corresponding to the version you're restoring beforehand.
Click to expand...
Click to collapse
I made the backup while I was running 6.0.1 and I flashed the 6.0.1 factory image so they both should have the same vendor image.
I also tried wiping everything except for internal storage and I unchecked "EFS" when restoring the backup but the same problem still persists, the phone automatically reboots itself before the restoring is complete and gets stuck in a bootloop. I'm not sure where the problem is at this point. I guess I'll just have to start from scratch again
I finally got PN on my PixelXL and just looked at storage and it says the system uses 19.9 GB and I'm wondering if I can clean the alternate slot to free up this space
My 128gb XL on latest update only use 6.79gb system
Sent from my Pixel XL using XDA-Developers Legacy app
You need to flash a factory image which will wipe all data as I had the same issue I believe its the only fix as you need a full wipe to fix and if your going to full wipe your better off to just flash a full factory image and be 100% factory fresh.
M9guy said:
You need to flash a factory image which will wipe all data as I had the same issue I believe its the only fix as you need a full wipe to fix and if your going to full wipe your better off to just flash a full factory image and be 100% factory fresh.
Click to expand...
Click to collapse
I had the same issue. This ^^^ was the only fix.
toknitup420 said:
I had the same issue. This ^^^ was the only fix.
Click to expand...
Click to collapse
Did you try > fastboot format userdata
cam30era said:
Did you try > fastboot format userdata
Click to expand...
Click to collapse
Formatting didn't work for me. I needed fresh system image too
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Yamalito said:
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Click to expand...
Click to collapse
If you are on Verizon, DO NOT LOCK BOOTLOADER! Just a friendly reminder.
Yamalito said:
What I did was flash the new Google image then I locked the boot loader then unlocked it again. When I booted up, my storage was back to normal. After that I flashed the custom ROM. This has happened to me often.
Click to expand...
Click to collapse
That's a silly way of wiping data. Factory reset from os or fastboot erase userdata will accomplish the same thing.
tiny4579 said:
That's a silly way of wiping data. Factory reset from os or fastboot erase userdata will accomplish the same thing.
Click to expand...
Click to collapse
If someone is going to format user data they might as well flash the newest factory image. It just makes sense its also preventative maintenance and can keep your phone running at top performance.
M9guy said:
If someone is going to format user data they might as well flash the newest factory image. It just makes sense its also preventative maintenance and can keep your phone running at top performance.
Click to expand...
Click to collapse
Flashing the image is fine. Locking and unlocking the bootloader is unnecessary and should not be done if you're just trying to format. Locking th bootloader while playing around with a messed up system is the perfect storm for a bricked device.
toknitup420 said:
Flashing the image is fine. Locking and unlocking the bootloader is unnecessary and should not be done if you're just trying to format. Locking th bootloader while playing around with a messed up system is the perfect storm for a bricked device.
Click to expand...
Click to collapse
Oh definitely, I never would recommend to relock the bootloader that would be just asking for trouble. I replied to the guy saying to just wipe user data, which if your going to do that it just makes sense to flash the newest factory image and make good use of wiping user data and get back to factory fresh in the process that is just a no brainer.
I agree that locking and unlocking bootloader is silly, it can cause trouble, I'm aware of that, however that was the ONLY thing that worked for me in this case. I tried everything and the storage was still at 19 GB. I'm sorry if the method that worked for me is silly and unorthodox but for me that is all that worked. It's happened to me three times.
Hello. I am currently on TWRP 3.5.2_9.0, and my phone gets stuck while restoring my system partition. The same problem has persisted over many ROMS and even iwhile using Orangefox Recovery. Any help will be great. Thanks.
0Ananta0 said:
Hello. I am currently on TWRP 3.5.2_9.0, and my phone gets stuck while restoring my system partition. The same problem has persisted over many ROMS and even iwhile using Orangefox Recovery. Any help will be great. Thanks.
Click to expand...
Click to collapse
Are you backing up both system and system image and trying to restore both? Try backing up system image alone and restore (not system).
TNSMANI said:
Are you backing up both system and system image and trying to restore both? Try backing up system image alone and restore (not system).
Click to expand...
Click to collapse
Yes. I have been backing up system and other partitions in the same zip. I will try your method and report when I need to restore again. Thanks
And there is update for TWRP...ver3.6.0_9-0
0Ananta0 said:
Yes. I have been backing up system and other partitions in the same zip. I will try your method and report when I need to restore again. Thanks
Click to expand...
Click to collapse
EFS may also give issues while restoring. So backup everything else you want except system and EFS and try restoring.