Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558 per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5 note that this post points to another way of getting TWRP. The link I went to is how to install OFFICIAL TWRP.
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Edited to add correct link to install official TWRP.
vinnievegas said:
Ok... As you can see from this thread,
https://forum.xda-developers.com/on...en-restore-t3804734/post76832485#post76832485
I soft bricked my phone after trying to restore a backup in official TWRP.
I followed this tutorial https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-unlock-bootloader-flash-twrp-t3792643
And jumped over to this tutorial per this post in the tutorial https://forum.xda-developers.com/showpost.php?p=76564290&postcount=5
And jumped back to the original tutorial for the rest. I'm scared to death now to try and test the restore functionality in TWRP. Has anyone successfully restored a backup? If so, what steps did they take to get the backup and what steps did they take restoring backup? What partitions did the check.mark during backup and what partitions did they check mark during restore? And do you need to do anything with changing the a/b slots????
Click to expand...
Click to collapse
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
vinnievegas said:
I'll try this and if this works and is in deed the process we need to follow until TWRP can just do what it's supposed to, then shouldn't this stuff be in the tutorials or have the OPs actually pulled this off like it's supposed to be?
Click to expand...
Click to collapse
Just too lazy to make an official thread, I guess. It will work.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
mikex8593 said:
Just too lazy to make an official thread, I guess. It will work.
Click to expand...
Click to collapse
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
vinnievegas said:
So to be clear, I get the roms from here under signed flashable zips?
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Click to expand...
Click to collapse
Yep. You can use the method with any of those zips.
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
tdamocles said:
I restored boot, system and data and ended in twrp loop. Flashing magisk revived it.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
vinnievegas said:
Did you do it like he instructed above?
Flash rom
Flash TWRP
Restore boot, system, and data
Reboot?
Click to expand...
Click to collapse
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
Ok. Worked like a charm. Thank you so much. I tested all this without any lock screen security. Now I'm wondering if this procedure works with backups with lock screen security.
mikex8593 said:
Flash stock ROM in TWRP, flash TWRP again. It won't touch data partition but you can restore just your data partition from your TWRP backup. Boot into system once, then reboot recovery and flash magisk if you want root. All modules you have will be back and active after that.
---------- Post added at 01:34 AM ---------- Previous post was at 01:33 AM ----------
On the off chance TWRP says there is no OS after flashing stock ROM and TWRP, ignore messages and boot anyway. It will restore your phone without losing all data.
Click to expand...
Click to collapse
black_file said:
Yes me too twrp on oneplus 6 are buggy when I had restore all system part my Phone enter in bootloop [emoji58]
Actual Device : OnePlus 6 Past Devices : Galaxy S6, Xperia Z2, Huawei P7, Nokia 620
Click to expand...
Click to collapse
tdamocles said:
To tell you the truth I didn't even see the other post and was trying to get the renovate magisk module working in the process. It was the first time for me trying to restore a twrp backup because I borked something in the renovate magisk install. Like I said, I tried restoring boot, system and data and ended in a bootloop twrp situation. I figured what the heck, let's try flashing magisk root again and see what happens, and voila it work.
Click to expand...
Click to collapse
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
vinnievegas said:
Ok. Just tried what tdamocles did. But I've been wiping before restore. I then just restore and select system, boot, and data. I did not reflash TWRP. Rebooted and everything was good. Still had root and didn't need to reflash magisk. Was also able to reboot back into TWRP, so there was no need to reflash TWRP. But.... I think that is due to not flashing the stock room first. I'm assuming that if you reflash stock that you will indeed have to reflash TWRP. So, conclusion... If you restore system, boot, and data then no need to reflash TWRP and in my case no need to reflash magisk. Again, this is without lock screen security. My next test will be with lock screen security unless someone posts a negative result before I do.
Click to expand...
Click to collapse
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
mikex8593 said:
You will not be able to get past encrption if you decrypt in TWRP and restore. It essentially forgets encryption key.
Click to expand...
Click to collapse
Check my post above. I edited it to quote you.
I must also note that I'm using official TWRP. I edited my first post to reflect the link I used when jumping out if the tutorial and back.
vinnievegas said:
Update...
Just performed a backup with lock screen security and was able to restore the backup choosing system, boot, and data. No reflashing of TWRP or magisk. Not sure if needed but I've been performing basic wipe before all my restores. Still able to boot back into TWRP and still had root.
Click to expand...
Click to collapse
Nice.
I have restored from twrp a couple times now with no problem.. I did get the message saying can't mount system or something like that, ok I went into the mount options and mounted system after that the restore worked perfectly and I could boot back into the rom and back into twrp after.
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
primus19 said:
Restored mine yesterday too, all files checked when backup, deleted lockscreen settings before, few bootloops at the beginning, until phone changed slot, then booted into system. Cheers!
Click to expand...
Click to collapse
Not necessary to check all partitions. This only results in a huge nandroid file.
Related
Please help me!!!
I had flashed Resurrection Remix OS, I don't remember which build. It was working fine, no hiccups. But suddenly today it switched off. When I restarted the phone, it was stuck in a boot loop for almost an hour. I was able to boot into recovery. Now I have no idea what to do because I can't perform a factory reset because I don't have any backup of my data. Will dirty flashing a new build help?
Any solutions? Anything will help me right now.
aryan.arora180 said:
Please help me!!!
I had flashed Resurrection Remix OS, I don't remember which build. It was working fine, no hiccups. But suddenly today it switched off. When I restarted the phone, it was stuck in a boot loop for almost an hour. I was able to boot into recovery. Now I have no idea what to do because I can't perform a factory reset because I don't have any backup of my data. Will dirty flashing a new build help?
Any solutions? Anything will help me right now.
Click to expand...
Click to collapse
Yes,dirty flashing a new build will work fine
Don't forget to create a Nandroid backup first!
Sometimes happened to me on latest build of RR also. Sadly dirty flashing for me didn't work, clean flash needed.
UPDATE: I flashed a newer version of RemixOS, and it is still stuck in bootloop. I cannot perform a clean install because the WhatsApp conversations are important and I can't afford to lose them. Any other ideas?
Create a nandroid backup, wipe everything thing except internal storage, flash the same rom, restore data from the nandroid backup?
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
aryan.arora180 said:
UPDATE: I flashed a newer version of RemixOS, and it is still stuck in bootloop. I cannot perform a clean install because the WhatsApp conversations are important and I can't afford to lose them. Any other ideas?
Click to expand...
Click to collapse
You mean Ressurection Remix?
Akshat2100 said:
Create a nandroid backup, wipe everything thing except internal storage, flash the same rom, restore data from the nandroid backup
Click to expand...
Click to collapse
Yep, tried it. After wiping data and booting it, it booted up fine. But as soon as I restored the data from the previous backup, it didn't boot.
Akshat2100 said:
You mean Ressurection Remix?
Click to expand...
Click to collapse
Yeah... I mix both of them up
aryan.arora180 said:
Yep, tried it. After wiping data and booting it, it booted up fine. But as soon as I restored the data from the previous backup, it didn't boot.
Click to expand...
Click to collapse
You only restored the data from the backup right? Not the system or anything else?
Akshat2100 said:
You only restored the data from the backup right? Not the system or anything else?
Click to expand...
Click to collapse
Yes I'm sure
Akshat2100 said:
Create a nandroid backup, USE TWRP and backup as well, wipe everything thing except internal storage, flash the same rom,
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
1. Boot successfully, restore your messages which are important, and save them/back them up to another device.
2. Then do another full TWRP backup of your device. Now you will have the first save, with your messages but bad/corrupted other data, and a clean system save with your messages.
3. Then restore 1/2 of your TWRP data, say apps from A-M, reboot and see if it boots correctly. If so do a full TWRP save again.
4. Repeat #3, restoring 1/4 of the left over data from TWRP, say N-U, see it it reboots correctly...
It may take some time, but you will eventually identify the corrupted app data.
Another way, before the process above you could also go into your apps, and write down each app and the date and time they were last written to or updated. Chances are those last few written/ypdated to are the one/ones which corrupted your setup.
So doing steps 1 and 2, above and then restore all your TWRP Data, except for the last 3-5 apps and data with the most recent writes/updates. If that boots successively and correctly, you are closer, faster, to id'ing the culprit.
It's a pain.
Click to expand...
Click to collapse
JeffDC said:
Akshat2100 said:
Create a nandroid backup, USE TWRP and backup as well, wipe everything thing except internal storage, flash the same rom,
---------- Post added at 10:50 AM ---------- Previous post was at 10:49 AM ----------
1. Boot successfully, restore your messages which are important, and save them/back them up to another device.
2. Then do another full TWRP backup of your device. Now you will have the first save, with your messages but bad/corrupted other data, and a clean system save with your messages.
3. Then restore 1/2 of your TWRP data, say apps from A-M, reboot and see if it boots correctly. If so do a full TWRP save again.
4. Repeat #3, restoring 1/4 of the left over data from TWRP, say N-U, see it it reboots correctly...
It may take some time, but you will eventually identify the corrupted app data.
Another way, before the process above you could also go into your apps, and write down each app and the date and time they were last written to or updated. Chances are those last few written/ypdated to are the one/ones which corrupted your setup.
So doing steps 1 and 2, above and then restore all your TWRP Data, except for the last 3-5 apps and data with the most recent writes/updates. If that boots successively and correctly, you are closer, faster, to id'ing the culprit.
It's a pain.
Click to expand...
Click to collapse
Thank you so much for the help!
Before you posted this, I had clean flashed like before and WhatsApp had found a local backup and I was able to restore my messages.
If it ever happens again(which I'm pretty sure it will) I'll try your method!
Click to expand...
Click to collapse
Just figured I'd give the heads up if you factory reset with a patched boot, for root or otherwise, it bootloops the phone twice and then goes to recovery. Flashing back stock boot img fixes it.
So don't be stupid like me and reset settings while rooted lol.
thank you for providing us this info, do u just have to go through the whole process again to TWRP/Root?
would it work, if u installed the stock unmodded boot image via twrp, do the factory reset/or clean install full OS zip, then install TWRPFix & Root all in the same session?
Bradl79 said:
thank you for providing us this info, do u just have to go through the whole process again to TWRP/Root?
would it work, if u installed the stock unmodded boot image via twrp, do the factory reset/or clean install full OS zip, then install TWRPFix & Root all in the same session?
Click to expand...
Click to collapse
I would imagine so, I haven't tried that yet. TWRP broke wifi for me, so I went back to stock recovery for now, maybe I did something wrong, but I'm gonna hold out until theres an official TWRP.
Chris123NT said:
I would imagine so, I haven't tried that yet. TWRP broke wifi for me, so I went back to stock recovery for now, maybe I did something wrong, but I'm gonna hold out until theres an official TWRP.
Click to expand...
Click to collapse
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Bradl79 said:
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Click to expand...
Click to collapse
Yeah, I did, so I dunno what happened, but when I booted into the OS after all the steps WiFi was boned.
If you have TWIRP why would you factory reset?
Why not just format /data?
Or does that also cause boot loops
virtyx said:
If you have TWIRP why would you factory reset?
Why not just format /data?
Or does that also cause boot loops
Click to expand...
Click to collapse
u don't want to format data, u want to wipe data, Format will erase sdcard. That is what the factory reset does anyway is wipe the caches and data.
Bradl79 said:
u don't want to format data, u want to wipe data, Format will erase sdcard. That is what the factory reset does anyway is wipe the caches and data.
Click to expand...
Click to collapse
if youre going to factory reset might aswell format data in twrp
i just thought maybe formatting data in twrp wouldnt cause the bootloop
virtyx said:
if youre going to factory reset might aswell format data in twrp
i just thought maybe formatting data in twrp wouldnt cause the bootloop
Click to expand...
Click to collapse
I could be wrong but I believe the OP might be talking about the root files and not twrp. Prior to twrp release, factory reset was the only option. As it happen to me also, after rooting device.
Plus Oneplus did not include a rom install zip in the stock recovery.
Damn, this AB partition setup really makes things a hassle
Bumping because other people are getting tripped up by this. Something in the factory reset process is not compatible with any sort of mods.
This happened to me as well. Not sure how I recovered, as I flashed via fast boot a bunch of image files. Is the boot image in the image files the latest stock boot image for 5.1.5?
For those of us rooted and no TWRP can someone link the stock boot.img?
Nevermind I found them on the ota page by titokhan
Bradl79 said:
Did u follow post 70 step by step and used the files provided? Also when I did mine I deleted any security I had first.
Click to expand...
Click to collapse
That could be what's causing it, I did wonder about that.
Chris123NT said:
That could be what's causing it, I did wonder about that.
Click to expand...
Click to collapse
try it and let us know
So before factory reset we need to make sure to reflash stock boot.img that will unroot the phone and only then do a factory reset..
So factory reset with twrp is working or not?
Anyone know where I might be able to get the stock boot.img? My phone is now toast and the referred thread should carry a health warning
Sorry for the noob question but does factory reset delete the media partition too?
itsadme said:
Sorry for the noob question but does factory reset delete the media partition too?
Click to expand...
Click to collapse
No, it does not.
this happened to me too. I was thinking of flashing the latest OxygenOS 5.1.11 with a clean install and I am rooted with TWRP. So what I did was reboot to recovery, wiped data, flashed OOS, then TWRP, reboot recovery and then flashed magisk. Then it got stuck in a TWRP bootloop.
Good thing I had a nandroid so i restored it and tried again.
This time I did the above steps but didn't wipe data. I booted successfully to 5.1.11 and i tried Factory Reset inside OxygenOS. Phone rebooted to TWRP and no data wipe was done. I did the Wipe Data within TWRP, same thing happened... bootloop to TWRP.
Nandroid restored again.
3rd attempt to dirty flash 5.1.11 but this time i didn't flash TWRP nor magisk and just rebooted system. I was back to stock. Then I tried factory reset again within OOS, it was successful so i had to do the whole TWRP and Magisk install again, and restored my apps via Titanium.
Moral of the story is (at least for me), Factory Reset within OOS or Wipe Data in TWRP both doesn't work. If i need to do a clean install, flash OOS then factory reset after rebooting to system, and then go through the whole TWRP and Magisk install process from scratch. Pain in arse really...:crying:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
leondestiny said:
New OP6 owner, quite bugged with how this thing works when flashing stuff..
it was a breeze on my 6p, anyways.
i decided to do a "Clean" flash and wiped data/system/dalvik etc.
then tried to flash the Full zip of 5.1.8 (it is a 1.2gb file) and i flashed via TWRP then flashed twrp zip and rebooted recovery/flashed magisk.
but there is no OS installed it says, boots me back into twrp.
my question now is how do i get it back to load up OOS, do i have to use fastboot now .. ?
i dont want it to wipe my whole SD
what do i do, and how do i stop this from happening for next time?
i thought flashing was normal that way, are we not supposed to wipe system with the op phones..?
i had a MOD installed (xXx) and wanted it removed so that i could install another mod ,thus i wiped system/data etc.
please let me know how to fix this, thx !
Click to expand...
Click to collapse
You need to make sure you are booting the slot you flashed the rom on, A or B.
sting5566 said:
You need to make sure you are booting the slot you flashed the rom on, A or B.
Click to expand...
Click to collapse
how do i do this? i only flashed zip from the root of my SD , there was no option to select either A or B :C
i went into advanced or seomthing and saw SLot a and B i tapped a and reboot sytem now it is stuck on twrp logo.
f** this ab ****.
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
OnePlus 6 has two partitions like the Pixel 2. For seamless OTA updates. In TWRP go to the Reboot menu and you'll see your currently active slot. It's either A or B. Switch to the other one and reboot. That should do it if you did flash the ROM.
Bradl79 said:
When u flashed the rom and rebooted it should let u know which one u r flashing on when u flash magisk, the xXx should have been a magisk module so should have been deleted when u wiped data, I would re-download 5.1.8
Wipe all again.
Flash OS
Flash twrp installer
Reboot to twrp
Flash magisk and reboot
---------- Post added at 01:23 PM ---------- Previous post was at 01:22 PM ----------
Did u have the magisk module version of xXx, if so all u had to do was uncheck it and reboot
Click to expand...
Click to collapse
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
leondestiny said:
man screw this ab partition shet, i will be forced to do a userdata reset..
can you please advise me what not to do to get into this mess again..?
its not fun recopying my data back and forth.
all i tried to do was clean flash and flash the latest rom via twrp..
why does this thing has to be so complex, please tell me if a clean wipe does this mess ?
cant we safely clean wipe this thing or what?
i love the phone, but the flashing stuff is a huge mess imo.
Click to expand...
Click to collapse
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
mikex8593 said:
You can always just keep a backup of userdata in TWRP but you don't have to wipe data. If you wipe system and flash the full zip, you will get the no os error but you can boot to system anyway. It just thinks there is no os. The bootloop to TWRP is probably related to magisk.
Click to expand...
Click to collapse
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
leondestiny said:
hmm okay thx, someone suggested me omni rom, but i will need to erase data right?
but my issue is, if in case i wanted to go back to OOS, would i need to erase data again? :l
and also about flashing roms, must they be flashed on both slots..? a and b ?
i have no clue how i got OOS back booting to be honest.. :l
Click to expand...
Click to collapse
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
mikex8593 said:
Switching ROMs, it is best to erase data or keep separate data backups for each ROM and restore the associated ones. As far as flashing on both slots, it wouldn't hurt, but it's not necessary unless instructions dictate. The whole reason for the slots is to allow seamless updates while the os is still active. If you experience any issues with bugs that aren't stated to be in the ROM thread, a clean install is always recommended.
Click to expand...
Click to collapse
thx mate, so for next time if i were to flash some oos through twrp, i only need to wipe data/cache etc.
then flash the oos zip ? i dont think i had the option to select which Slot to flash it to, so i guess i just have to reboot to the slot that it has it flashed on..?
and also flashing procedure must be like Rom then twrp then reboot twrp then flash magisk yes?
leondestiny said:
took me an hour or so to get this thing booting up again..
without the need to wipe SD , this is so strange.
i honestly have no idea how i did it, but i am afraid to use twrp now..
this thing is messed up
Click to expand...
Click to collapse
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
mikex8593 said:
It's relatively easy. Just always remember to flash TWRP and magisk after flashing full ROM zip. It's always a safe bet to erase your lock screen before messing with TWRP as well so it can just decrypt with no password. If you use a magisk ROM, it's all systemless so the only changes that would stay are the ones that would debloat apps or remove system files. Everything would revert back to normal after you uncheck the ROM module in magisk manager.
Click to expand...
Click to collapse
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
chrcol said:
No sheet
This is what happened to me LOL and I soft bricked phone. Never ever bricked a phone before.
I tried to flash havoc os, OOS was originally on both A and B.
This process wiped slot B clean (even tho was booting on slot A), and OOS stayed on slot A.
I went to the reboot screen to reboot recovery on slot B and BAM I was bricked locked into fastboot mode.
And people say its easy.
Now I am in msmdownloadtool, I have managed to get it connected, and I can start the recovery but it fails, so I think the phone may be proper bricked.
Anyone getting a oneplus6 I would say these phones seem to have a genuine risk of brick, all I did was try to boot of a slot which TWRP says had no OS and now I have this problem.
---------- Post added at 01:59 ---------- Previous post was at 01:25 ----------
Havoc OS requires Oxygen OOS in both slots.
So I need to somehow get this to work.
I can unbrick the phone now with msmdownloadtool.
After ubricked the bootloader is locked again so I have to start from scratch.
Unlock oem loader in OS
Unlock bootloader in fastboot
Copy zips to phone.
Boot into TWRP and install TWRP, it says it installs to both slots but B bricks phone.
At this point I have oxygen OOS installed via recovery tool on slot A, twrp installed.
If I try to boot in slot B, phone bricks, fastboot loop which doesnt allow you to boot back into twrp so cannot switch back to slot A without msmdownload tool.
So the question is after I have recovered the phone how do I get oxygen OOS onto slot B as well, given I Cannot boot from slot B?
The solution is probably easy to those who know how but seems it isnt documented.
Click to expand...
Click to collapse
Fastboot boot recovery. Img
Flash oos full ROM zip
Flash recovery. Zip
Reboot recovery
Flash oos full ROM zip AGAIN
flash twrp. Zip AGAIN
Reboot recovery
Flash magisk if you want root.
Make sure your using the correct twrp aswell. I recommend bluespark v86
chrcol said:
And people say its easy.
Click to expand...
Click to collapse
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
leondestiny said:
it is not easy, i make backups of my whole phone every 2weeks because i am a flashaholic i see myself switching from aosp back to oos and vice versa (i love oos) i actually gave up on flashing roms some weeks ago tried to stick to oos only so that i wont be bothered with bricks for whatver reason (and not being forced to use msmtool) , it is frustrating.
you always have to make sure you are not flashing a rom that has an older security patch , e.g november build of oos if you flash aosp rom with october build you might brick, so the rom has to be either on november security patch or newer e.g december.
it is so confusing as you even have to use the latest twrp always or else you can mess it up again..
always make backups is my advice.
Click to expand...
Click to collapse
If you're installing havoc os, make sure you're using latest bluespark TWRP first. Reboot recovery, flash oos, flash TWRP, reboot recovery, flash havoc gapps and magisk then reboot. The only difference in a/b partition is that there's a few extra steps in the flashing process. You don't have to flash to both slots to have havoc, but you also shouldn't be manually changing the slot in TWRP to try to boot a specific slot unless you know what you're doing.
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
cvfd said:
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
Click to expand...
Click to collapse
This is exactly what happened to me! (and I thought it was related to edXposed).
Have you tried flashing only the boot img?
cvfd said:
Hi,
after installing and uninstalling some Magisk modules, my device (OP6, OOS, blu spark TWRP, Magisk) randomly froze and after restarting, it keeps booting forever. I can still get into TWRP, so I tried a few things to fix this like:
Uninstalling and reinstalling Magisk
Flashing OOS, TWRP and Magisk again
Flashing just OOS,
but nothing seems to help. Is there a proper way of fixing this without wiping my data partition?
If there is not, how do I save as much of my data (like system settings, app data etc.) as possible from TWRP so I can restore it later?
Thanks for your help
Click to expand...
Click to collapse
Boot to twrp
Flash magisk uninstaller
Flash oos full rom
Flash twrp zip
Reboot recovery
Flash oos full ROM
Flash twrp zip
Reboot recovey
Flash magisk.
yldlj said:
Boot to twrp
Flash magisk uninstaller
Flash oos full rom
Flash twrp zip
Reboot recovery
Flash oos full ROM
Flash twrp zip
Reboot recovey
Flash magisk.
Click to expand...
Click to collapse
Hmm, I just tried that and it didn't help. Is there anything else I can do?
Edit: Tried with official TWRP as well, no luck either.
davidperl99 said:
This is exactly what happened to me! (and I thought it was related to edXposed).
Have you tried flashing only the boot img?
Click to expand...
Click to collapse
Where would I find the newest boot.img? Also, isn't flashing the OOS Full ROM supposed to replace my boot.img with the stock one?
cvfd said:
Hmm, I just tried that and it didn't help. Is there anything else I can do?
Edit: Tried with official TWRP as well, no luck either.
Where would I find the newest boot.img? Also, isn't flashing the OOS Full ROM supposed to replace my boot.img with the stock one?
Click to expand...
Click to collapse
I think you might have to wipe if you can't get your phone to boot after dirty flashing ROM. I would try flashing your boot. Img first in case it's magisk related problem. What ROM are you on?
yldlj said:
I think you might have to wipe if you can't get your phone to boot after dirty flashing ROM. I would try flashing your boot. Img first in case it's magisk related problem. What ROM are you on?
Click to expand...
Click to collapse
Regular OOS 9.0.7.
cvfd said:
Regular OOS 9.0.7.
Click to expand...
Click to collapse
Stock Boot. Img can be found here
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Also try use the latest bluespark twrp
yldlj said:
Stock Boot. Img can be found here
https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853
Also try use the latest bluespark twrp
Click to expand...
Click to collapse
So flash the boot.img through fastboot and then repeat the steps above?
cvfd said:
So flash the boot.img through fastboot and then repeat the steps above?
Click to expand...
Click to collapse
Flash boot. Img and see if the phone boots. I have never flashed a boot. Img so not sure exactly how. If not it might be time to use the fastboot rom. If you flash the boot. Img you will lose twrp.
yldlj said:
Flash boot. Img and see if the phone boots. I have never flashed a boot. Img so not sure exactly how. If not it might be time to use the fastboot rom
Click to expand...
Click to collapse
No luck with that either, so I guess it's time to reset. What's the best way to backup and restore as much of my data as possible, like system settings and app data?
cvfd said:
No luck with that either, so I guess it's time to reset. What's the best way to backup and restore as much of my data as possible, like system settings and app data?
Click to expand...
Click to collapse
You can backup data in twrp but that might be the reason you can't boot. Google backup should of backed up most things. At this point you should be more concerned about getting your phone to boot.
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Encrypted?
arkansawdave74 said:
I break my system a lot (currently testing which of my favorite Xposed modules work with Pie) . I've had to set up from scratch like 6 times in the past week. Every TWRP restore results in a boot loop, both custom and stock. Has anyone made it work and, if so, how? It surprises me that our TWRP is official if it can't restore a backup.
Click to expand...
Click to collapse
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Skippy12359 said:
I'm having the same problem. This is my first a/b device and everything I thought I knew after flashing ROMs for years just doesn't seem to work on this architecture. Like you said twrp backup restore always results in a bootloop. Also any full custom ROMs I've tried appear to overwrite twrp and install its own recovery. Even gsi's don't boot and then twrp freezes and back to stock I go. This thing has me stumped.
Click to expand...
Click to collapse
I noticed when installing RR that it actually needs that Lineage recovery to factory reset after the install. A TWRP factory reset wouldn't help it, and it wouldn"t boot after the install. Funny how they try so hard to stop us tinkerers, then steal all our cool ideas for their stock ROMs. I see Linux phones in my future.
I wonder if a factory reset with that Lineage recovery would help after a TWRP restore? Next time I may try that.
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
WoKoschekk said:
Encrypted?
Click to expand...
Click to collapse
Just saw this. No. I had flashed dm-verity. Good thinking.
arkansawdave74 said:
Damn! I just got it. I'm typing this on a restored crDroid Official. The boot.img is in ramdisk, so only backup system and data. Yay!
Click to expand...
Click to collapse
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Skippy12359 said:
So your saying because recovery is in the boot image that we need only to backup system and data and then a restore of same will not go into a bootloop? That would mean the problem has been backing up and then restoring the boot image. System as root and no recovery partition is just hard to grasp at this point. For me restoring data in a backup of stock results in twrp error 255.
Click to expand...
Click to collapse
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
arkansawdave74 said:
I spoke too soon. This was the 1st time I'd flashed dm-verity on the install. That's why it worked. It won't work if /data is encrypted. I just made a backup with boot as well and it restored fine.
Click to expand...
Click to collapse
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Skippy12359 said:
Which version of dm- verify are you using and what steps did you take to get crdroid to boot?
Click to expand...
Click to collapse
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
arkansawdave74 said:
I'm not sure where I got it Or else I would link you. But this is the one I'm using this one. I flashed it after formatting /data and also after installing the ROM. One of those is proper, but I couldn't remember. I think it's supposed to be after you install, but before 1st boot.
https://www.mediafire.com/download/uxldj5okanllfza
Click to expand...
Click to collapse
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
Yup. I've restored it twice and made another with boot included and it booted as well. I hope it works with RR too, but I've got a helluva headache. I may stop messing with it for now.
Oh, I had wiped dalvic (actually ART), system, and data. I don't think boot was an option during wipe.
You know, I've only had one device before thar force encrypted, and back then, TWRP couldn't decrypt /data except by formatting. Now it can. That's why I didn't suspect it was an encryption issue.
I was still using a Galaxy S5 with crDroid 7.1.2 built by me until last week. It died, may it rest in peace.
Skippy12359 said:
That's the same one I've been using. So crdroid actually booted for you after doing a normal wipe in TWRP?. Assuming you had stock pie installed.
Click to expand...
Click to collapse
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
My goal was to have twrp backup of stock pie which is really great in my opinion and also be able to flash Q gsi's like I do on my Moto g6. So far any backup restore of stock just bootloops and any gsi just hangs at boot logo or boots back to recovery.
arkansawdave74 said:
If, when you boot TWRP, it asks you to decrypt, dm-verity didn't work, and it might not work with stock. I'm only figuring it out at the moment.
Click to expand...
Click to collapse
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Skippy12359 said:
It does appear to be an encryption issue with a stock rom TWRP backup restore not booting. Formatting data in TWRP and rebooting always results in a bootloop. Until I can format data to remove encryption and get it to boot and the security setting says it's not encrypted, I don't think a backup will ever boot. Out of ideas at this point.
Click to expand...
Click to collapse
For stock, I wonder if you could boot TWRP after all those fastboot commands and flash dm-verity before booting stock. You may be able to keep stock from encrypting. I don't know for sure though.