It has been months since op5 come out, and the problem is that when restoring data partition from backups will lead to bootloop on OOS.
Has there been any fix on that?(official or non-official)
p.s. I have searched before, none of the recovery works for stock OOS, due to forced file encryption on OOS.
timescaming said:
It has been months since op5 come out, and the problem is that when restoring data partition from backups will lead to bootloop on OOS.
Has there been any fix on that?(official or non-official)
p.s. I have searched before, none of the recovery works for stock OOS, due to forced file encryption on OOS.
Click to expand...
Click to collapse
Not just problems with OOS, custom ROM's give bootloop too
When you do a backup, you have to also backup the system image partition. That will make your backup around 8-10gb in size but then you can restore your data partition and not get a bootloop. I am on TWRP 3.1.1-1 cheeseburger TWRP. Make sure you're at least on that or the k2 version which I'm updating to soon.
Eric214 said:
When you do a backup, you have to also backup the system image partition. That will make your backup around 8-10gb in size but then you can restore your data partition and not get a bootloop. I am on TWRP 3.1.1-1 cheeseburger TWRP. Make sure you're at least on that or the k2 version which I'm updating to soon.
Click to expand...
Click to collapse
So you can confirm it works?
Does this apply to OxygenOS too or just custom ROMs?
Jonathanve said:
Not just problems with OOS, custom ROM's give bootloop too
Click to expand...
Click to collapse
I restore data on custom ROMs without issue when using K2 (with or without backing up the system partition). Not sure about OOS since I haven't used it in a very long time. I've been using RR-Official successfully for a few months.
sjamie said:
I restore data on custom ROMs without issue when using K2 (with or without backing up the system partition). Not sure about OOS since I haven't used it in a very long time. I've been using RR-Official successfully for a few months.
Click to expand...
Click to collapse
I've personally try to backup and restore stock oos with the k3 version, ended up with a boot loop. Never tried k2 though, to scared to try again.
timescaming said:
I've personally try to backup and restore stock oos with the k3 version, ended up with a boot loop. Never tried k2 though, to scared to try again.
Click to expand...
Click to collapse
Understood. LoL
Pwnycorn said:
So you can confirm it works?
Does this apply to OxygenOS too or just custom ROMs?
Click to expand...
Click to collapse
Yes, it's works. But k2 apparently doesn't need the system image for data restore so your backups will be smaller and faster obviously.
Also, I'm on stock oos with stock kernel 4.5.10
---------- Post added at 11:19 AM ---------- Previous post was at 11:09 AM ----------
sjamie said:
I restore data on custom ROMs without issue when using K2 (with or without backing up the system partition). Not sure about OOS since I haven't used it in a very long time. I've been using RR-Official successfully for a few months.
Click to expand...
Click to collapse
I can't seem to find the k2 file anywhere. Do you mind posting a kind to it so I can download?
Here you go: https://www.androidfilehost.com/?fid=889764386195921506
lekiaM said:
Here you go: https://www.androidfilehost.com/?fid=889764386195921506
Click to expand...
Click to collapse
Awesome, thanks!
Eric214 said:
Also, I'm on stock oos with stock kernel 4.5.10
Click to expand...
Click to collapse
So it means k2 can perform restore on stock oos, gonna try again when I get home.
Did you decrypt your device, or remove screen lock on the device before backup? Or anything I should do before backup? Thanks.
timescaming said:
So it means k2 can perform restore on stock oos, gonna try again when I get home.
Did you decrypt your device, or remove screen lock on the device before backup? Or anything I should do before backup? Thanks.
Click to expand...
Click to collapse
I ALWAYS remove screen locks and fingerprints before a backup. I also never decrypt my phone's, not worth it in my opinion.
Im curious if anyone has tried this to flash in TWRP to remove password and pin.
https://drive.google.com/file/d/0B3gcDbDvV4MkSmNCcDdTcHpyanc/view?usp=drivesdk
Sent from my OnePlus5 using XDA Labs
Eric214 said:
I ALWAYS remove screen locks and fingerprints before a backup. I also never decrypt my phone's, not worth it in my opinion.
Click to expand...
Click to collapse
Thanks, I'll try later today.
Related
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
By default, you have to backup Boot, System and Data
Braakie said:
By default, you have to backup Boot, System and Data
Click to expand...
Click to collapse
and that will bring me back like i left off if i restore boot, system, and data?
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
kradkovich said:
Hello, i want to try a different rom out and im wondering what things do i need to back up in twrp just in case something goes wrong or i want to go back. Also if i go back i would like everything to be right as i left off before flashing a new rom. My backup options are Boot, System, System image, Vendor, Vendor Image, Data, Chache, Recovery, EFS
Click to expand...
Click to collapse
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Heisenberg said:
See section 4 of my guide.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Krunk83 said:
Don't you have to disable all security passwords like pattern lock and fingerprints before making a nandroid or it won't work when you restore? I read that in the How to thread for the 6P. Wondering if this is true or not.
Click to expand...
Click to collapse
Yes that would be true, you would have to disable any type of lockscreen security because it wont let you unlock your phone after restoring.
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Thats not even remotely a clean wipe and would cause nothing but issues.
I would highly recommend not doing that.
Sent from my Nexus 6P, Note 5, Nexus 6 or Note 4
kradkovich said:
Thank you! Im going to try flashing the BeanStalk 6.02 rom on my 6p tomorrow! Would it possible to restore data on a new rom coming from your old rom? For example: My Nexus 6p is running chroma rom right now, if i back up the data partition can i restore that partition onto my new rom ( BeanStalk 6.02)?
Click to expand...
Click to collapse
Noooooooo. When flashing a different ROM you need to clean flash (wipe system, data, cache, dalvik cache).
I have a pattern lock and fingerprints and restore my backup without any problems?
Braakie said:
I have a pattern lock and fingerprints and restore my backup without any problems?
Click to expand...
Click to collapse
Which partitions do you backup and restore?
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
TigerSoul925 said:
I don't feel the original question has been fully answered and explained.
The usual answer is: boot, system, data.
In the guide, section 4 that Heisenberg links however, vendor is added to the mix.
Remaining questions:
- Is vendor needed for usual backup together with boot, system and data. If so, why? What does it contain?
- What about the remaining partitions? Vendor image, system image. What do they contain and why do we not need them backed up?
---------- Post added at 01:40 PM ---------- Previous post was at 01:39 PM ----------
Also, yes you can still get back into a backup with fingerprint lock still active. See this post:
http://forum.xda-developers.com/showpost.php?p=64321640&postcount=91
Click to expand...
Click to collapse
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Gizmoe said:
Boot, system and data are fine just as it's always been. I've already done this and restored with no issues. Even with lock screen security. All you do is use file manager in twrp to delete "data/system/locksettings.db". If you know what you are flashing is going to actually write to a partition other than boot or system then yeah, back those up too. Suppose it wouldn't hurt to grab backups of each partition individually and store them on your pc to be on the safe side.
Click to expand...
Click to collapse
Heisenberg said:
The only issue with not backing up and restoring the vendor partition, and the reason I include that in my guide, is if you have themes applied they will survive through the wipe and be carried onto the restore/flash, potentially causing compatibility issues and a failure to boot or a wonky/unusable system after boot.
Click to expand...
Click to collapse
Oh so that's the reason! Well thanks, then I know what to do! I'll include the vendor partition then just for safety. I already have a complete backup of all partitions except recovery and cache too so I'll just keep that safe somewhere just in case.
Thanks for the replies!
Heisenberg said:
Which partitions do you backup and restore?
Click to expand...
Click to collapse
I backup/restore my boot, data and system partitions to data/media (SDCard)
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
survivor_evil said:
So what are other options such as system image?
Is it necessary to back it up? I just backed up the default ones
Click to expand...
Click to collapse
System.img is just that. An exact image copy of the system image in one chunk. So you would end up with IMG files. It's not necessary to choose the IMG options. Default options for boot, system and data is a complete backup.
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Tried clearing cache? Also, what things did you precisely backup?
DJBhardwaj said:
Tried clearing cache? Also, what things did you precisely backup?
Click to expand...
Click to collapse
almost everything including vendor ; no cache
setul34 said:
almost everything including vendor ; no cache
Click to expand...
Click to collapse
I had the same issue when I backed up system image.
DJBhardwaj said:
I had the same issue when I backed up system image.
Click to expand...
Click to collapse
okay so any solution?
Try it without the system image.
DJBhardwaj said:
Try it without the system image.
Click to expand...
Click to collapse
i did but that did not install root / apps / settings. basically i just got data and stock rom.
setul34 said:
i did but that did not install root / apps / settings. basically i just got data and stock rom.
Click to expand...
Click to collapse
No idea, I myself haven't tried further.
Lets see if someone else comes up with something
setul34 said:
Hello,
so i backup my phone before i do anything risky. so i was trying to restore my phone (from yesterday backup) using twrp. everything went perfect and when my device rebooted after restore. it stuck on Google Logo. i tried 3 times but no luck. any help? i select Boot, Data, System, System.img
EDIT: should i select vendor / vendor.img ?? while restoring it ?
UPDATE: when i tried 4th time. my phone rebooted after about 72% and stuck on google logo.
Click to expand...
Click to collapse
Let me guess you are on TWRP 3.0.0.0?
Yes
oneandroidnut said:
Let me guess you are on TWRP 3.0.0.0?
Click to expand...
Click to collapse
@oneandroidnut Yes.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
You don't backup system image, only backup system, data, and boot.
setul34 said:
@oneandroidnut Yes.
Click to expand...
Click to collapse
pm me if you are still having issues we can go to hangouts or something and i can walk you through
oneandroidnut said:
pm me if you are still having issues we can go to hangouts or something and i can walk you through
Click to expand...
Click to collapse
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Heisenberg said:
It'd be much better if you did this here, that way the solution is available for others to find, that's pretty much the entire point of the Q&A section. I'm confident it's just a case of selecting the wrong partitions to backup anyway.
Click to expand...
Click to collapse
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
oneandroidnut said:
The solution i used when i incorrectly updated vendor image and then tried to restore old system image and vendor image was to use Nexus Tool kit by wugs fresh to flash back to stock while keeping internal card intact. Then flash the rom you were on with correct vendor image in TWRP 3.0.0.0 and then restore your twrp backup without the vendor image etc and boom should be back to normal. At least that is what worked for me. What should you backup and restore? I back up everything and restore everything but vendor stuff. any suggestions?
Click to expand...
Click to collapse
this worked for me thankyou
Heisenberg said:
That seems over-complicated. You only need to backup/restore system, data, and boot. Vendor is optional if you have Layers that you want to keep. Don't backup/restore system image or vendor image. That's the reason he got into this mess, be backed up and restored system image. I posted the solution a couple of posts back.
Click to expand...
Click to collapse
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
setul34 said:
okay so i tried to recover Data System Boot, still didn't work. so i remove everything including twrp and installed stock rom. and then i installed twrp 3.0 and somehow it worked and my device is back on
this worked for me thankyou
i won't make that mistake again to backup vendor or system image.
Thanks @oneandroidnut @Heisenberg
Click to expand...
Click to collapse
No problem man glad it worked!!
I had the same problem.
I tried to restore a backup (MMB29Q - system+data+boot, done after installing the last factory image without root) and I got blocked on the Google logo. I tried twice without managing.
In the end I solved the problem installing supersu v2.68 zip before restarting.
It's as though the restore needs the root to work properly.
What do you think?
Thanks.
Hello everyone! I bring news from the TWRP developers from the #TWRP IRC channel! TWRP 3.0.2-1 has a fatal bug! If you backup and restore EFS it will brick you! Do not backup and restore EFS on 3.0.2-1! Use 3.0.2-0 instead! This has already been fixed in the newer builds!
If you have been bricked you NEED to Erase the EFS partitions and that will fix it immediately.
For the Nexus 6P go to TWRP. Then on PC Open Command Prompt with access to ADB ( Android Debug Bridge) and execute the following commands:
ADB shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst1 bs=16384
and
ADB Shell dd if=/dev/zero of=/dev/block/platform/soc.0/f9824900.sdhci/by-name/modemst2 bs=16384
This should fix it for ANY Nexus 6P users. Users on other phones with the same problem await instructions!
Hello, I'm still a noob so please pardon me, I was wondering, I'm planning to flash Ultra kernel to my MXP but I've got to have a backup plan in case of something went wrong. Yes, my MXP is still on its Original kernel.
So my question is what is MXP original kernel's name and any of you guys have the answer then may I trouble you to link me to the site that posted the Original kernel?
Thank you
HerySean said:
Hello, I'm still a noob so please pardon me, I was wondering, I'm planning to flash Ultra kernel to my MXP but I've got to have a backup plan in case of something went wrong. Yes, my MXP is still on its Original kernel.
So my question is what is MXP original kernel's name and any of you guys have the answer then may I trouble you to link me to the site that posted the Original kernel?
Thank you
Click to expand...
Click to collapse
I am expecting that you are rooted and have twrp installed. Make a backup through twrp. If you flash any other kernel, then just flashing the backup kernel won't make you phone all working as wifi would break down.
So, take a twrp backup and if something's wrong, then restore the whole backup or just system.
K.khiladi said:
I am expecting that you are rooted and have twrp installed. Make a backup through twrp. If you flash any other kernel, then just flashing the backup kernel won't make you phone all working as wifi would break down.
So, take a twrp backup and if something's wrong, then restore the whole backup or just system.
Click to expand...
Click to collapse
Yes, I'm already rooted and installed twrp, so restore my backup will eventually restore my original kernel?
in twrp while backing up you'll see a "boot" partition, that is your kernel.
bablu048 said:
in twrp while backing up you'll see a "boot" partition, that is your kernel.
Click to expand...
Click to collapse
So when I flash a new kernel, are all my data will be wiped? like it will automatically do a factory wipe?
HerySean said:
So when I flash a new kernel, are all my data will be wiped? like it will automatically do a factory wipe?
Click to expand...
Click to collapse
No data would be wiped.
Automated reply by JARVIS
K.khiladi said:
No data would be wiped.
Automated reply by JARVIS
Click to expand...
Click to collapse
Oh okay, thank you.
So I've done some testing and after a couple msmdownloadtool sessions I've come to the conclusion that the backup/restore feature in the official and unofficial TWRP for Oneplus 6t (I tested twrp-installer-fajita-3.2.3-1 and TWRP 3.2.3-28 Unofficial by mauronofrio) is borked. If you create a backup of boot,sys,vend,data and then restore it you end up only being able to boot to twrp and encrypted data? Is there currently any way to backup partitions without twrp? I tried flashfire which doesn't work on the 6t. can you backup in fastboot? Is this issue known? I can't seem to find much info on this.
Edit: Is there any alternitives to twrp atm for full backups?
fireeyeeian said:
So I've done some testing and after a couple msmdownloadtool sessions I've come to the conclusion that the backup/restore feature in the official and unofficial TWRP for Oneplus 6t (I tested twrp-installer-fajita-3.2.3-1 and TWRP 3.2.3-28 Unofficial by mauronofrio) is borked. If you create a backup of boot,sys,vend,data and then restore it you end up only being able to boot to twrp and encrypted data? Is there currently any way to backup partitions without twrp? I tried flashfire which doesn't work on the 6t. can you backup in fastboot? Is this issue known? I can't seem to find much info on this.
Click to expand...
Click to collapse
In the thread they are mentioned that not to restore vender.
Sent from my ONEPLUS A6013 using Tapatalk
..
vichao.s said:
In the thread they are mentioned that not to restore vender.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Thanks, I didn't see that. What post was that in?
If that's the only reason it breaks then that's good.
vichao.s said:
In the thread they are mentioned that not to restore vender.
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
Just tried restoring a backup excluding vendor and same issue happens. Boots to twrp and only twrp plus encrypted data
I have tried so many different ways to back up and restore all with problems I have given up. I just use TWRP to flash zips until a Dev or someone with direct knowledge chimes and in responds to a simple question with regard to a proper back up and restore thats all I will use it for.
Archangel said:
I have tried so many different ways to back up and restore all with problems I have given up. I just use TWRP to flash zips until a Dev or someone with direct knowledge chimes and in responds to a simple question with regard to a proper back up and restore thats all I will use it for.
Click to expand...
Click to collapse
Yes, after about 3-4 times having to resort to using msmdownloadtool after trying to find out what I was doing wrong. I'm going to do the same. Really wish that would have been listed as an issue on there site. I would have thought something like this would have been noticed by the twrp devs but intill it's fixed or adressed guess that's all we can use it for atm.
Thanks for the reply. It's nice to know that I'm not the only one having issues.
I don't know if it's related or not, but I've read somewhere that while backing up the boot partition it's adviced to remove the screen lock/fingerprint beforehand to avoid some issues during the restore.
Twrp restore is broken.
I don't use it anymore too
daspyki said:
I don't know if it's related or not, but I've read somewhere that while backing up the boot partition it's adviced to remove the screen lock/fingerprint beforehand to avoid some issues during the restore.
Click to expand...
Click to collapse
yeah I always do that when backing up. not sure why the data becomes encrypted still. maybe its corrupted
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
I got the same problem... I did't find the solution. Can someone help ?
k1n9n0th1n9 said:
Hi everyone, I have problems recovering data with TWRP - "extracttarfork() process ended with error=255"
How to fix it?
i worked on TWRP v3.3.1-4 Miui.gr version
Click to expand...
Click to collapse
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Pupet_Master said:
I had it too with many devices.
It really depends, some times, the TWRP can't access the partition it want to write. Other times, one file of the backup is corrupted (so it halt).
Try to change TWRP, mount the system partition and check. If it don't work.. i would say that you wont be able to fix with that backup in particular.
Try to make a new backup too, and restore from it to see if with the new backup, the problem persist.
Click to expand...
Click to collapse
hi, I had this, try doing the partitions separate, I did data afterwards following a reboot.
Try OrangeFox-R10.0_8-Stable-davinci recovery.
flamedrops said:
Try OrangeFox-R10.0_8-Stable-davinci recovery.
Click to expand...
Click to collapse
Orange fox atm is the worse and most buggy recovery for K20
Pupet_Master said:
Orange fox atm is the worse and most buggy recovery for K20
Click to expand...
Click to collapse
even the latest one?
flamedrops said:
even the latest one?
Click to expand...
Click to collapse
Yeap, it is still in it's infancy, where other TWRPs solved some issues that even the latest OF still has
I have just made a new backup after restore from Titanium Backup, but after flash new firmware and test some new roms, some of apps were crushing after restore and must be installed and configured one again.