Been using TWRP for years on my now 6T and Nexus 6, nexus 5. However I read somewhere for 6T that we need to do backup/restore of either System System Image /System and Vendor/Vendor Image.
I cannot remember if we need to backup both System and or system image and vendor and or vendor image. Can someone clarify? Thank you in advance.
ozzmanj1 said:
Been using TWRP for years on my now 6T and Nexus 6, nexus 5. However I read somewhere for 6T that we need to do backup/restore of either System System Image /System and Vendor/Vendor Image.
I cannot remember if we need to backup both System and or system image and vendor and or vendor image. Can someone clarify? Thank you in advance.
Click to expand...
Click to collapse
A lot of people said to back up system and vendor images but when I did that and restored, I ha dto go through the setup process all over again and reinstall all of my apps. I just did a backup with system and vendor and system and vendor images and everything excluding data (since I get errors when trying to backup data).
TheKnux said:
A lot of people said to back up system and vendor images but when I did that and restored, I ha dto go through the setup process all over again and reinstall all of my apps. I just did a backup with system and vendor and system and vendor images and everything excluding data (since I get errors when trying to backup data).
Click to expand...
Click to collapse
Ah gotcha. I just tried to do a restore with syste/vendor and system/vendor images and got the red exclamation point and could not boot. Had to reflash the oxygen zip I have of 9.0.7, oddly my data was still there and everything. Problem now I am facing is when I reboot I get the red exclamation, it reboots, get red exclamation, reboots and then its fine.... odd. Not sure what happened.
ozzmanj1 said:
Ah gotcha. I just tried to do a restore with syste/vendor and system/vendor images and got the red exclamation point and could not boot. Had to reflash the oxygen zip I have of 9.0.7, oddly my data was still there and everything. Problem now I am facing is when I reboot I get the red exclamation, it reboots, get red exclamation, reboots and then its fine.... odd. Not sure what happened.
Click to expand...
Click to collapse
Backup everything.. just to be safe.. soon as I formatted my phone and didn't restore apps or anything from Google, I reflashed twrp and don't have the 255 error when restoring backups
jacksummers said:
Backup everything.. just to be safe.. soon as I formatted my phone and didn't restore apps or anything from Google, I reflashed twrp and don't have the 255 error when restoring backups
Click to expand...
Click to collapse
I always copy my backups to my laptop. I'm back to normal in the sense that my phone will boot up. Issue is, now, is that when I reboot. I get the red exclamation point, instead of orange. I press power button to continue, red exclamation point, press power button to continue, then it shows the red exclamation point again but then boots up. Phone still functions once booted up. It's just when I reboot. I have tried restoring a previous twrp but still same. My prior backups has both the following:
System partition
System image
Vendor partition
Vendor image
I did those as o read, somewhere, that we needed to back them up. But when I redtored my most recent backup yesterday morning, that was when the red exclamation point stuff happened. I had to reflash the 9.0.7 zip I had to just even get it to boot, but again it's doing the red exclamation point but after three power button presses it will both up. Not sure what happened. Also, that was my first restore on the 6t since getting twrp installed.
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
ozzmanj1 said:
I always copy my backups to my laptop. I'm back to normal in the sense that my phone will boot up. Issue is, now, is that when I reboot. I get the red exclamation point, instead of orange. I press power button to continue, red exclamation point, press power button to continue, then it shows the red exclamation point again but then boots up. Phone still functions once booted up. It's just when I reboot. I have tried restoring a previous twrp but still same. My prior backups has both the following:
System partition
System image
Vendor partition
Vendor image
I did those as o read, somewhere, that we needed to back them up. But when I redtored my most recent backup yesterday morning, that was when the red exclamation point stuff happened. I had to reflash the 9.0.7 zip I had to just even get it to boot, but again it's doing the red exclamation point but after three power button presses it will both up. Not sure what happened. Also, that was my first restore on the 6t since getting twrp installed.
Click to expand...
Click to collapse
U have broken verity. Only fix at the moment is to use the tool and start over.. none of that matters. U can try copying your data to another external, but u could still have persisting corruption. I would go freshie all the way.none of the other stuff matters, this phone is easy to break verity. If u flash a kernel that it doesn't like while not on stock kernel, it can break verity. U make too many changes in system. Break verity.. I would copy pics and important shi t and run the tool.
jacksummers said:
U have broken verity. Only fix at the moment is to use the tool and start over.. none of that matters. U can try copying your data to another external, but u could still have persisting corruption. I would go freshie all the way.none of the other stuff matters, this phone is easy to break verity. If u flash a kernel that it doesn't like while not on stock kernel, it can break verity. U make too many changes in system. Break verity.. I would copy pics and important shi t and run the tool.
Click to expand...
Click to collapse
Ok. Good thing I've already backed up my internal storage. Did it just start few days ago. I have the tool downloaded but never used it. I believe there may be a newer version of the tool. Downloaded the one for tmo right when it leaked and was available. And I haven't had much time these last few weeks to really follow the op6t forums on any updates. I will have to wait till the weekend to look into this. Appreciate the help. Thank you
Sent from my ONEPLUS A6013 using XDA-Developers Legacy app
I also get the same error. Is there a solution?
GuestK00177 said:
Backup everything.. just to be safe.. soon as I formatted my phone and didn't restore apps or anything from Google, I reflashed twrp and don't have the 255 error when restoring backups
Click to expand...
Click to collapse
I also get the same error. Is there a solution?
Related
So I decided to try and flash Ubuntu last night... I booted into recovery made a backup 15min and 2.5 GB later it was done... wiped flashed no go would not boot... so back to recovery I choose my restore file... system says it was successful but when restoring the data it fails... I'm on twrp 2.5 ...then I tried to just restore the system when booting up I get that static image you see on cm flash every 5 sec but never boot nor goes inyo the boot animation...is there anyway to use this restore file... I just need the data part.. I have messages that i need to show my lawyer and numbers that I need... TiB won't restore my messages either....
Sent from my XT907 using xda app-developers app
You will need TWRP 2.6.3 / PhilZ / or a newer CWM that supports adb in recovery (not sure is 2.5 does)
First off, all of your pictures and other stuff are stored at "/data/media" or "/data/media/0" and are not "wiped" unless picked. These are both accessible in recovery, and you could do an "adb pull ....." to get those files to a PC. At this point you should have your pictures.
Sounds like Ubuntu messed some things up, and when you restored "/system" only it won't boot because of missing data. I once had a problem like this bouncing back and forth between 4.3 and 4.2. Assuming you were on a custom ROM, maybe try wiping completely including "/data/media" DO NOT WIPE "/DATA/MEDIA" IF YOU HAVEN"T BEEN ABLE TO PULL THE FILES VIA ADB IN RECOVERY!!! YOUR PHOTOS WILL BE GONE!!! Sorry for the bold caps, I just didn't want you to miss it. Next install your custom ROM, boot, and do enough setup to get to the home screen. Now go back to recovery and your backup should restore. From here you could "adb push ..." your files back.
Updating TWRP is one way to solve this in the future, like JB already posted. However, to remedy on 2.5, do a clean wipe prior to restore, mounting system prior. Then, restore only the boot.img from the ROM you want and then restore the full ROM you want. This is how I was able resolve this same issue. Hopefully, it will work for you.
I was on stock deodexed debloated prior to all this... after a few tries at the restore I just flashed that same ROM and used TiB to restore what I had on last back up... tonight I'll try and restore that twrp backup ... but either way I guess I'll be updating my recovery... I'm not worried about all my pics n what not I keep all that on the external SD card now...
Sent from my XT907 using xda app-developers app
I was bootloader unlocked, latest TWRP installed, systemless root with SuperSU 2.6, cataclysm rom, ex kernel, layers, xposed. I had made a ton of backups and even kept some of them backed up in another locations. I needed to restore a backup in TWRP. At first it wouldn't let me, kept saying that phone system was mounted as read only.
this is my question #1 - How do you mount system for read in TWRP? I see there's an option called "mount," I go in there, i see settings I can select, but I don't see any option to "execute" or "apply" settings (like TWRP has on other screens - swipe to backup, swipe to restore, etc). There's no "clicke here to mount option." what do you do here?
#2 - it finally mounted rw, i think, but after picking my latest backup, it started and then when it got to 19% it reboot the phone. Phone is softbricked.
#3 - I'm very confused about all the checkboxes to restore, and all the checkboxes to wipe.
What should I be wiping and what should I be restoring? When making backups I checked all the boxes.
I had the galaxy nexus before and I knew that phone and clockworck mod inside out. TWRP is confusing and glitchy to me. I'm stuck and work with a phone without an OS and I'm starting to freak out, and don't have A to C cables with me.
Please explain where I went wrong here and how to do things correctly. I want to understand what I'm doing better, not just follow steps.
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
dontbeweakvato said:
When you restored, with all the check boxes did you click "system image" for restore?
You should wipe then restore only system, data, and boot.
Click to expand...
Click to collapse
Yes, I selected all the boxes, including system image I believe.
I did a wipe. I selected all the boxes. Went back into TWRP and now all my backups are gone. I said reboot, and TWRP said there's no OS installed. I think I deleted everything. I should not have wiped. I do have a backup saved on a computer, it's a folder with lots of .img files inside. How can I get that onto my phone with only having fastboot and TWRP modes available? I mean how can I place it on the phone in a way that TWRP would recognize it and restore from it.
I ended up just flashing the stock google image and that at least gave me a working phone back.
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
dontbeweakvato said:
Yes. You beat me to it, that's what I was going to say. You have to reflash. Just remember for future references you only need to backup boot, system, and data( and efs etc). But Not "system image" that'll Bork your stuff up.
Click to expand...
Click to collapse
I'd like to really understand this better. Do you know why system image borks the phone? Also, when you say efs etc., do you mean "absolutely everything except system image"? (I actually didn't see EFS listed there)
Well boot system and data. But you also need efs cause thats your imei. So just look around and familiarize with what youve found so far. Right now Im trying to flash 6.0.1 with a systemless root. Its kinda goin ridiculous right now because there aren't any directions or suggestions.
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
zgroten said:
If you get to "no OS installed" restoring system image, then system will get you back
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Did you mount system in TWRP before attempting to restore?
Sent from my Nexus 6P using Tapatalk
mistermojorizin said:
After it said no OS installed, I tried to restore system image from my TWRP backup, and the restore failed and the phone reboot itself at 19% restored. I had to ADB flash the factory system image from google. This brings me back to the original question.
Why was the restore in TWRP failing?
Click to expand...
Click to collapse
actually in twrp you could of wiped, then restored boot, system , data and it would of restored everything
I woke up this morning and in a daze decided to flash beanstalk6.17. For what ever reason it seemed to have made apps disappear and was lagging out my 6p. I was rushing out the door and in a state of panick I flash purenexus back on. This caused constant booklooping. I restored from a nandroid backup from earlier today but now I can pulldown my settings from the top and constantly have "Unfortunately, the process android.process.acore has stoppped. I reset all apps and it stopped for a while but as soon as I went into any app it began again.
Any help will be appreciated.
Clear the cache for Contacts and Contacts Storage. That should do it.
Sent from my Nexus 6P using XDA-Developers mobile app
Cleared contact cache and still get the notification when I open phone or messages. Also cant slide down to view my quick settings.
Have you tried doing a full wipe, and fresh install of a ROM?
https://www.youtube.com/watch?v=TlvKydE0EVA
pepsal said:
I woke up this morning and in a daze decided to flash beanstalk6.17. For what ever reason it seemed to have made apps disappear and was lagging out my 6p. I was rushing out the door and in a state of panick I flash purenexus back on. This caused constant booklooping. I restored from a nandroid backup from earlier today but now I can pulldown my settings from the top and constantly have "Unfortunately, the process android.process.acore has stoppped. I reset all apps and it stopped for a while but as soon as I went into any app it began again.
Any help will be appreciated.
Click to expand...
Click to collapse
Did you clean flash? Sounds to me like you didn't wipe properly.
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
pepsal said:
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
Click to expand...
Click to collapse
Taking a guess, but I think you need to flash proper Vendor img. Can you adb reboot bootloader while phone is in TWRP? If so then at boot loader, reflash the vendor.img.
pepsal said:
Okay so I managed to resolve the issue but now have created a even greater one. I needed to update my vendor image and when installing I accidentaly chose boot image. Now my 6p boots straight to recovery and my twrp data is encrypted and it wont accept my unlock code so I cant access my data to recover. I have a copy of a backup on my pc if that helps. Any guidance would be apprieciated.
Click to expand...
Click to collapse
dratsablive said:
Taking a guess, but I think you need to flash proper Vendor img. Can you adb reboot bootloader while phone is in TWRP? If so then at boot loader, reflash the vendor.img.
Click to expand...
Click to collapse
You'll need to flash the correct boot.img back to the device.
EDIT: Unless I'm misunderstanding you. Did you flash the boot.img to the vendor partition or flash the vendor.img to the boot partition?
Heisenberg said:
You'll need to flash the correct boot.img back to the device.
EDIT: Unless I'm misunderstanding you. Did you flash the boot.img to the vendor partition or flash the vendor.img to the boot partition?
Click to expand...
Click to collapse
I flashed the vendor.img to the boot partition.
Edit: Going to attempt flashing the boot.img now
Edit2: Worked! Thanks for your help
I'm having issues with restoring the factory image of stock Android 6.0.1, I'm using
@Heisenberg guide to create the fresh back up image on TWRP-3.0.2-0. Once I create
the back up, I boot into the OS and perform a factory reset, when i do that the phone resets
into TWRP, and performs the wipe to the device, when i go to do the restore, it freezes
at about 39%, and reboots fully trying to enter the OS, but its corrupt due to TWRP restarting
in the middle of the recovery.
I did at one point upgrade to Android N, but reverted back to android 6.0.1 if that makes a difference.
TL;DR - Created a fresh factory image of 6.0.1 using TWRP, cannot recover with it, TWRP freezes at 39% every time.
What options are you selecting to backup/restore?
Heisenberg said:
What options are you selecting to backup/restore?
Click to expand...
Click to collapse
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
DeathSentinels said:
I'm doing a back up selecting the system/data/boot/vendor boxes, leaving everything else unchecked, and a second back up with only the EFS,
When i go to restore, I'm just using the first back up, leaving the EFS alone unless ever needed, and am selecting the system/data/boot/vendor boxes
Click to expand...
Click to collapse
I can only think that your backup is corrupt. Also, instead of booting into Android and performing a factory reset that way, just go into the advanced wipe section of TWRP and wipe only data. Maybe you'll just need to flash the factory images to get the phone booting up fresh again.
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
DeathSentinels said:
That's where it gets interesting, I've flashed the factory 6.0.1 image, then flashed twrp, created the back up again, did the advanced wipe as you said, did the restore again, and same result, at around 39% of the recovery the phone reboots and the back up gets corrupt. My main goal is to make sure this back up absolutely works before I root and start playing around with flashing xposed modules, but I'm unable to do a successful restore for the life of me.
Click to expand...
Click to collapse
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Heisenberg said:
I'm stumped, I really don't know why it wouldn't be working if you're performing the backup the way you say you are. Sorry I can't be more helpful. If it's any consolation, a backup probably isn't strictly necessary because you can always get back to stock by flashing the factory images.
Click to expand...
Click to collapse
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
i had a similiar problem , but when i got into the stock image , i went into settings and did a factory reset from there , no worries your BL stays unlocked , once thats done get whatever apps you want back , disable fingerprint /security junk , then boot into bl just like the guide says , youll be able to fastboot install recovery , (boot back into bl, then scroll to recovery and start a gain) then make your backups yor OG & EFS , then reboot , get su reboot into recovery install and yould be be fine , i think you can also try fastboot format userdata , as well
DeathSentinels said:
I'm stumped too, I've been able to do this effortlessly in the past with this phone, my Nexus 9 and m8 GPE, it wasn't until I upgraded to N and reverted back to 6.0.1 this started to happen. I've even gone as far as trying different versions of twrp, but have had the same result.
I'm just worried in a worst case scenario I'm away from a comp, something crashes and I can't do a restore via twrp, I could be SOL until I get to a comp with adb.
Click to expand...
Click to collapse
Just keep a ROM zip + gapps on your phone at all times, if you run into trouble you can flash that.
That definitely makes sense , i always dk that
Sent from my Nexus 6P using XDA-Developers mobile app
I'm not sure what happened, I was flashing a kernel, and suddenly my device stopped booting, getting stuck at the OnePlus logo, with 'Powered by android". TWRP was installed, so I tried restoring a backup, but that didn't help. I tried flashing the stock 4.5.5 full zip, it would still stay at the OP logo screen. I tried wiping the phone, flashing the stock full zip, still stuck at boot. I tried going back to the stock recovery (I know, risky), and it succeeded in flashing, but when I boot to recovery, the screen just goes black, and I have to hard-reboot. I can however flash TWRP back, and it seems to work fine. When I look in the file manager on TWRP, I can see things in the system partition, but I still can't boot to it.
I'm starting to panic now, so any help would be appreciated.
To clarify, even doing fastboot boot OP5_recovery.img brings be to the black screen
It may be that you have an issue with encrypted data partition which you cannot recover otherwise
Try flashing TWRP, then in TWRP select "Wipe", "Format data" and answer with "yes" when asked for confirmation.
NOTE: when doing the steps above the whole data partition will be erased, including internal storage - so when in doubt back up your data before proceeding
s3axel said:
It may be that you have an issue with encrypted data partition which you cannot recover otherwise
Try flashing TWRP, then in TWRP select "Wipe", "Format data" and answer with "yes" when asked for confirmation.
NOTE: when doing the steps above the whole data partition will be erased, including internal storage - so when in doubt back up your data before proceeding
Click to expand...
Click to collapse
I had already done that a few times.
However, wiping fixed it, but not in TWRP. doing fastboot -w fixed it, and the phone was able to boot to stock recovery. After that I flashed system zip, and TWRP again, and I'm back up (just got it working 15 mins ago)
Thanks for the answer, though!
0xTJ said:
I had already done that a few times.
However, wiping fixed it, but not in TWRP. doing fastboot -w fixed it, and the phone was able to boot to stock recovery. After that I flashed system zip, and TWRP again, and I'm back up (just got it working 15 mins ago)
Thanks for the answer, though!
Click to expand...
Click to collapse
Please change the title of this thread to: "[SOLVED] Soft-Bricked OnePlus 5, TWRP works, but nothing else". That will help others who may get into a similar plight.