Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
UPDATED:
After some testing the problem only occurs when i take back up for all partitions which isn't mandatory, but when i take back for (system, boot, data) which is enough for working backup and the restoring process is flawless
I did not disable security (PIN code) and restoring was successful
Short answer:
Only take backup for data, system, boot
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
R1skNt said:
Greetings,
after restoring back up from official TWRP the device soft-bricked like our friend here
https://forum.xda-developers.com/oneplus-6/help/soft-brick-restoring-backup-twrp-t3805112
the device won't even boot to fastboot from hardware button but from adb on recovery mode which hang on twrp logo screen.
what I saw on log is that /system partition structure need cleaning (and can not be mounted)
my backup contains all partition.
so my steps to restore the backup
boot to recovery
from PC into CMD "adb reboot bootloader"
wait until boot to bootloader (fastboot)
boot temporary into twrp "fastboot boot twrp.img" make sure you have twrp img
restore all partition except /system
then restore /system alone
reboot to system
everything's works like charm
I know it seems hideous but this is how I fix it ( and I can confirm I've done it twice)
:good:
Click to expand...
Click to collapse
What about security? Did you have to disable all security before the backup?
I did not disable security (PIN code) and restoring was successful.
R1skNt said:
I did not disable security (PIN code) and restoring was successful.
Click to expand...
Click to collapse
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
lollyjay said:
These are the backup settings that I am using. Can you please tell me if you use the same, or if not please share the ones you are using.
Click to expand...
Click to collapse
Please see the 1st post (update)
PeterGuru said:
Sounds great, but it doesn't work for me. I posted the following comment in another thread:
----------------------------------
I'm having the same problem. I simply cannot restore a TWRP backup. It always produces an error 255.
No, I do not have any "999" folder/files, nor do I have any lockscreen security. I also do not have parallel apps or anything involving multi-user.
I'm extremely experienced at flashing ROMs, as well as performing Nandroids and restoring them.
Nothing I've done is working. As I said, I simply cannot restore the data partition. That's when I get the 255 error. System restores fine, but that's it.
Any ideas?
----------------------------------
Thank you,
Peter
Click to expand...
Click to collapse
For what it's worth, I think I found a solution to why I couldn't restore the data partition. I can't explain why, but now it's working.
Previously, and historically, whenever I did a restore, I always wiped my device: system, data, boot.
This time; however, I did not wipe the device. I simply did the restore and everything worked. Therefore, the problem is somehow associated with the wipe.
Peter
I did a nanroid backup (boot, system, data only as per the instructions) of 5.1.8, rooted with magisk 16.6, ROM, installed lineage OS, than restored my backed up OOS ROM the restore process completed successfully but got stuck on boot logo, flashed magisk again along with the custom kernel but all to no joy, keeps bootlooping, however lineage restored fine and booted, any help be much appreciated, cheers.
joemossjr said:
You guys are crazy and I feel I need to answer your questions. So here we go. So just becuase there's multiple partitions doesn't mean you can dual boot or set up other things. So the way it works is the userdata partition is one partition. There are 2 system partitions for seamless updates two boot partitions for seamless and two firmware slots. In theory yes you can have two roms on both slots. Will they work? No. They will both use the same userdata partitions. So it will be incompatible.now you could in theory have lineage on one slot and oos on the other and if you ever want to go back just format userdata and fastboot --set-active=other to get to the other slot. But that doesn't really seem like a good idea. If you guys have other questions feel free to ask me!
Click to expand...
Click to collapse
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Bonito77 said:
This is from another thread here, my understanding is you have to format userdata partition, but please read it by self.
Click to expand...
Click to collapse
totally irrelevant to this thread, cheers.
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
bannannn said:
"fastboot boot twrp.img
cannot load 'twrp.img': No such file or directory"
What is wrong?
Click to expand...
Click to collapse
I assume you're in the directory twrp.img is in and are using the img file instead of the zip file? Also you renamed the img file to twrp.img?
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
kingwicked said:
after 6 hours of head banging . i stumbled across this thread. and i got my renovate backup. Since new to oneplus 6 have shifted from samsung S9+. The first post correctly resolved my headache. I have learned.
1. Only Backup sytem , data, boot other partitions of twrp restore needed. not need to restore others
2. Had to format the internal storage as it become fully corrupted with lot of folders with strange names
3. Had to re install full OOS rom zip then boot into sytem
4. reflash twrp via fastboot, install twrp offical .img from twrp.
5 NO WIPES( I think wiping system and then restoring vendor and other partitions was creating issues)
6 Only Restoring Boot , System, Data. and then straight away booting back phone to system worked perfect. didnt require to flash magisk
thanks a lot for this thread OP. :good:
i am an experienced flasher. but i guess to comeback to oxygen OS from other roms you have to install stock full OOS Rom again.
Click to expand...
Click to collapse
I followed your guide. But I'm stuck at the boot animation...
RheinPirat said:
I followed your guide. But I'm stuck at the boot animation...
Click to expand...
Click to collapse
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
I was on 9.0.2
I restored the phone with the MSM tool and updated the ROM to 9.0.2 via manual system update like before.
Question:
Is it not possible to restore the whole system? Or only Data like you said under point 8?
Do I need verity? Because I think my phone is encrypted (flashed never a verity file)
Could I restore the whole system from a full TWRP (all partitions included) - only select data, system?
restoring system and other never worked for me. always failed. but only restoring data partition always worked
when you restore only data. your all apps. settings messages everything will restore even magisk modules.
im not sure about encrypted because. encrypted phone when restoring twrp messed up my whole internal memory. and i had no choice but to wipe it.
so there is no issue with no verity. as it helps not to scramble the internal memory of your device and you wull not loose any data or get stuck on qualcomm dump mode
but remember the steps to verity when installed on already used rom with data. you have to format data to remove encryption
only restoring data is the best option. you can try without no verity to restore i think may work but follow all options i mentioned
but i dont recommend to use with no verity.since using no verity i have never got to wipe my internal memory
I've bricked my device twice after trying to restore and always resorted to just a clean flash of stock using the MSMDownloadTool... wish I'd found this thread sooner as you just solved my third backup restore soft-brick!
I'll also remember to just backup system/data/boot going forward...
Thanks!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Thanks buddy, It worked like a charm.
About the pin removal, as you siad there is a good tutorial in below link which can be used.
https://www.howtogeek.com/240657/how-to-fix-pin-errors-after-restoring-from-twrp-android-backups/
Thank you!!!
You saved my phone (and life).
I can confirm your procedure is working with my back up made on 10.3.2 using a usb c key.
I just restored the DATA. Nothing else!
Thank you so much!
kingwicked said:
well i have found new method which works every time
if stuck in boot animation
1. install the version stock OOS e.g 6.0.2 of which u have backup as well. again oem unlock process
2. install twrp
3 . reboot twrp
4.instal verity for phone being always decrypted
5. install magisk
6. reboot into system once
if you still have twrp
6 reboot to twrp
8. restore ONLY Data from twrp backup of SAME rom.
9. install twrp
10 reboot twrp install verity zip and magisk
remember
both rom installed and backup have to be of same OS. for e.g OOS 6.0.2 stable. only same backup can be restored as they have same security patch date
if you have a backup of for example OOS 5.1.11 then only rest ore data on a 5.1.11 rom
and flash magisk after backup restoee if ur backup had magisk. otherwise you will be stuck in boot animation
if you made backup with pin see the main OOS guide it has instructions how to remove pin after twrp restore
from twrp
Dont do any wipes before or after restoring data from twrp only magisk with verity zip is required if you had root
i always use the twrp bluespark as i had issues with stock twrp
thia methodology has worked always for me
best of luck
Click to expand...
Click to collapse
Edit: Since I am the impatient guy of course I still meddled with the backup after posting this thread. By chance I found a solution that finally worked for me. Latest Oxygen Os 9.0.2 stable without root.
Note that I will list every step even it may be that it hasn't contributed anything to the solution:
1. From fastboot I booted into latest blu_sparc TWRP.
2. I plugged the phone into USB and copied all files from my backup into the usual TWRP folder.
3. I flashed only DATA, nothing else.
4. From TWRP I rebooted directly into bootloader/fastboot.
5. Then I ram the flash-all-partitions.bat from Mauronofrio provided by this thread https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 .
6. Crucial step: At the beginning, it asks "Wipe all data?". SELECT NO. It will start "restoring" all other partitions.
7. Reboot the phone and it should work as you left it before creating the backup.
Note that this method worked the restoration of backup data from the same OS and same version. Feel free to try it out on other system images. It's ugly and inconvenient, but it seems to work.
Hey guys,
is there a fail safe way to restore data from a clean twrp backup without soft bricks or PIN error?
I tried to restore a very recent TWRP backup but had serious trouble. At first, it rebooted just fine but upon trying to unlock the device with 4-digit pin it suddenly told me that my usual pin isn't working.
Then I tried deleting the lockscreen.db and other related files. Rebooted and got into the OS, but it got stuck at "starting up device".
The I did a complete wipe without internal storage and tried it again. Then it wouldn't even boot and I had to use the flash-all.bat to flash all partitions "manually" to get it working again.
Now I am afraid of using Oneplus 6 if it's impossible to make a seamless backup/recovery. Is there a guide on how to do this?
Thank you in advance!
This is a known issue though. If you want to make a usable backup in TWRP: Remove the PIN (screen lock), do the backup, and then activate the screen lock again.
efex said:
This is a known issue though. If you want to make a usable backup in TWRP: Remove the PIN (screen lock), do the backup, and then activate the screen lock again.
Click to expand...
Click to collapse
I remember having read a thread with this hint too and disabled my security pin in a temporary working OS. Then I did the flashing stuff and I just noticed that my now working restored phone doesn't have a pin anymore. So basically removing this pin on a data backup will make things go smooth? I will keep this in mind, thank you
Any time I've tried to restore a backup it has completely bricked my phone. I tried just backing up the default options and restoring bricked, so when I had my phone rooted and setup perfectly with XXX no limits on Android 10 and all my apps installed, I made a FULL backup in case I bricked it with smurf kernel or something. Long story short, I ended up bricking it via other methods and tried to restore my full backup only to be completely bricked again. Not even recovery works after installing a backup. I've found that no matter what I backup, if I restore it it completely bricks my phone to the point where it only automatically boots into fastboot and I have to install a system image and start over every time. Am I doing something wrong or does TWRP 3.3.1-70 not support restoring yet?
jld2k6 said:
Any time I've tried to restore a backup it has completely bricked my phone. I tried just backing up the default options and restoring bricked, so when I had my phone rooted and setup perfectly with XXX no limits on Android 10 and all my apps installed, I made a FULL backup in case I bricked it with smurf kernel or something. Long story short, I ended up bricking it via other methods and tried to restore my full backup only to be completely bricked again. Not even recovery works after installing a backup. I've found that no matter what I backup, if I restore it it completely bricks my phone to the point where it only automatically boots into fastboot and I have to install a system image and start over every time. Am I doing something wrong or does TWRP 3.3.1-70 not support restoring yet?
Click to expand...
Click to collapse
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
tech_head said:
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
Click to expand...
Click to collapse
It's just a hassle because installing Android 10 factory image via fastboot fails every time. If I fiddle around and brick, I have to fastboot install Android pie, root it and install twrp, download Android 10, install it via local updater then flash magic to the other slot then reboot and install my xxx no limits module before I can restore my data. Compared to just getting TWRP up and running and restoring my backup I'm looking at a time consuming process to get to that point. I wish I knew why flashing Android 10 via fastboot bricks every time because that's a major cause of this headache while figuring out what does and doesn't work on Android 10. I already have titanium backup backing up nightly to Google drive so by the time I get to the point I can flash my data I might as well just restore my apps + data in TB. If I could get TWRP to successfully restore my backups I'd be given a lot of freedom to tinker around freely without worry of this time consuming restoration. I think next time I'm gonna try backing up into a flashable zip and seeing if I can successfully restore my image via fastboot when I inevitably brick again while messing around
tech_head said:
Stop trying to restore the complete backup.
Flash the ROM and restore data only.
I don't see a point in backing up the ROM, when you can just as easily flash it then restore data.
Click to expand...
Click to collapse
I haven't actually tried this. Are you talking about flashing the rom, and (within the same instance of TWRP), then restoring? Or are you talking about flashing the ROM, booting it, then going back into TWRP and restoring data?
just a quick question?? why are you always downgrading to a9?? when you can simply
1. flash a10 ( i save one on my PC in case a problem arises)
2. set up the phone
3. in pc, open a10 rom, locate for its boot.img amd store in phone
4. install magisk.apk and patch boot img , then copy to pc
5. install patched boot.img via fastboot
congrats,, back on track.. it only took me about 10-15 min to restore a bricked device up to being rooted and twrp installation
New to the A/B slot root scene, apologies. I also searched but couldn't find an answer for something matching this exact specificity . I know its fixable but I cant figure out what would be best to do.
I am (or was) running TWRP/Magisk on 10.3.4 Stock OOS. broke the OS boot and it will only goes right into fastboot, no TWRP anymore, doesn't even show the warning from OP when booting a rooted OP device.
Weighing my restore options, I changed the active slot with the fastboot command and that slot was able to boot into TWRP just fine, however, the mounting folder that's usually emulated/o (SDcard) was just a bunch of folders with random text and capitalization.
I have a TWRP backup (around 8GB) . Can i just change the active slot back to the non active one and restore to the other? I am concerned i will break it worse or restore it to the wrong slot somehow. If i restored it to both slots, would that be ok?
edit: I connected my TWRP backup and wasn't able to force the restore to another slot. The backup includes Boot, System, Data (excluding storage) and EFS. I could "swipe to restore" at any moment but unsure how that would effect everything seeing as the backup was done on Slot A and now I am on slot B.
I read you should flash the 10.3.4 full while staying on the same slot but was having issues getting it to upload to the phone (no drive mounts on my computer OS on the default slot, only can do so when i change slots) I have a very recent titanium backup i can restore once i am back in, either way.
I am just not 100% exactly how to get myself back up and running.
Lastly, i only started rooted again after a 10-15 year break because I got real sick of the background data the official OOS build was sending. I was interested in converting to LineageOS with gapps form Micro (if it can pass safetynet) but Open to any ROM that could assist in stopping the official background activity. I would love a ROM that can pass safetynet, help with the battery life on my aging OP6 and hopefully keep rocking on Android 10.
Thank you to everyone or anyone that reads this and assists. I know it must be annoying to read what may just be the same question over and over but this exact issue was hard to find another experiencing with the latest OOS.
Take care.
I ended up trying to restore the TWRP backup to the different slot, this put both slots in a fastbootloop. i then flashed all partitions with a fastboot image of 10.3.4 and this fix my phone and got it back up in running. i rooted again, flashed twrp and then tried to restore the TWRP backup again and it completed successfully, however, both slots were back to bootlooping.
i will just wipe all again, root/magisk and then install titanium to restore my full backup of that. Im sure ill be coming to a new issue trying that too, but who knows.
I fixed it the way i wanted (off the backup i made with TWRP) by restoring my backup (without EFS this time, per the tips on the devs website, rebooted into fastboot, flashed the OOS 10.3.4 fastboot image (WITHOUT -w to keep my user files), let it run. when it rebooted i had everything back from the TWRP backup!.
all i did then was boot the TWRP image, flash its zip, then flashed magisk again and rebooted.
All is well! (until Slot B issues rear their ugly head) I really hope to flash both and move to a custom ROM but saying encrypted is more important to me than I thought it was.
I hope anyone who finds themselves in the same stupid situation is helped by this come day.
PS. titanium backup is really not a system restore feature like I thought it would be when you are encrypted. TWRP was my only viable solution and so happy this worked. Ill be running that weekly, for sure.
Hi,
So it seems when i restore data via TWRP it triggers the protection which encrypts the whole sdcard, can this be avoided?
Here are the steps i did:
Full wipe
fastboot boot twrp (Nebrassy)
sideload stock 11.1.1
sideload magdisk
Finished setting up the device
Then booted twrp again
Did full backup
And then it never boot again to system... no idea why could be the twrp.
Now i'm stuck with this backup, every time i restore it, the entire sdcard gets encrypted.
I've tried flashing both stock boot and patched boot but it didn't help
Any ideas or should i do it all again and lose twrp, seems to be very buggy at v11.1.1
I managed to solve this issue myself.
Encryption is forced by default since android v10 i think so that means when you try to flash any data it has to be either the same type or it would encrypt the whole internal storage, i.e. you can backup just fine but if you restore and reboot the phone will tamper with all the data making it unreadable.
You need to disable encryption first then flash the data and then it works fine, unless you disabled it to begin with of course.
Another key point here is that when the phone encrypts the entire storage you won't be able to flash anything else until you completely erase everything.
Wasted hours on this on OP6 and OOS 11.1.1 + Unofficial Twrp,
Here is a short summary of the main points:
Full backup from TWRP works fine but copy it elsewhere or you might lose it when restoring
If you booted into encryption i used to flash lineageos recovery then boot into it and do a full wipe, then flash twrp back. i don't think it works from that twrp version
If you want to disable encryption or restore backups use this one (only one that worked) https://forum.xda-developers.com/t/...ncrypt-disk-quota-disabler-11-2-2020.3817389/
If you want OOS v11.1.1 + TWRP + Root + Backups do it in the following order: Unlock Bootloader, Boot TWRP, Install TWRP permanently, Flash Magdisk, Flash DFE
Not sure it's important but lineageos has a script for A\B slot phones like OP6 to sync slots, should be used at least once after flashing V11 just in case to avoid possible problems https://wiki.lineageos.org/devices/enchilada/install
I'm also adding stock and patched boot images in case someone needs them.