Has anyone been able to boot a TWRP restore on this phone? - Moto G7 Power Questions & Answers

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.

Related

Why is my TWRP backup of stock EMUI unable to boot? (And what can I do to fix it?)

Whenever I try to return to stock EMUI 5.0.1 from Lineage OS 14.1 with my TWRP backup, it just stays at the boot screen that says "Honor" and doesn't continue past that point. I was wondering why this happens and what I can do to fix this since I want to return back to stock without doing the painful dload method. I currently have TWRP 3.1.1-0 OpenKirin Edition, the same version I used to make the backup too.
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
RedSkull23 said:
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
Click to expand...
Click to collapse
I have the one by HassanMirza01
SenyorMauricio said:
I have the one by HassanMirza01
Click to expand...
Click to collapse
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
RedSkull23 said:
Which LineageOS ROM do you have, OpenKirin's or HassanMirza01's..?
Click to expand...
Click to collapse
RedSkull23 said:
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
Click to expand...
Click to collapse
Should I do that before restoring the backup? I've done it after restoring the backup, and it doesn't do anything but mess up TWRP's permissions.
RedSkull23 said:
Did you already formatted data partition back to ext4 before trying to restore the backup? Hassan's roms are f2fs based, so you won't be able to restore an ext4 based rom over f2fs
Click to expand...
Click to collapse
It booted up whenever I changed it back to ext4, but it comes up with a screen saying "Unencryption Unsuccessful" whenever I boot up. I click on reset phone, and it brings back to TWRP. This even happens if I reset the phone via TWRP. I'm not sure if this process would work if I restored the stock recovery, but I'm not sure if I want to find out.
SenyorMauricio said:
It booted up whenever I changed it back to ext4, but it comes up with a screen saying "Unencryption Unsuccessful" whenever I boot up. I click on reset phone, and it brings back to TWRP. This even happens if I reset the phone via TWRP. I'm not sure if this process would work if I restored the stock recovery, but I'm not sure if I want to find out.
Click to expand...
Click to collapse
Whenever I formatted data through the stock e-Recovery (the stock portion of the recovery that stays even with TWRP), it booted up perfectly fine! Thanks for all your help!
SenyorMauricio said:
Whenever I formatted data through the stock e-Recovery (the stock portion of the recovery that stays even with TWRP), it booted up perfectly fine! Thanks for all your help!
Click to expand...
Click to collapse
Nice one dude

Soft brick after restoring backup with TWRP

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.

disabled encryption

I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
jacksummers said:
I have successfully decrypted my essential phone using the dm verity disabler by zackptg. Need to test it some more, but twrp boots after flashing it, instantly.it doesn't have that lag
Click to expand...
Click to collapse
were u rooted before or not? did u have to format everything in twrp?
edit it actually works!!!!!! I'm unencrypted...i can go into twrp while a pin is set....i can flash magisk with first boot of a rom and it boots...!!!!!
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Here's the thread folks
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
Thanks to Zackptg
jacksummers said:
This is a huge advancement. I didn't think it worked until I booted into twrp. And it was instantaneous.so before I flashed the dm verity decryption zip, I did indeed wipe everything on both slots, then mounted system in twrp and flashed the zip, then I flashed the ROM.i will be switching back to stock to test if it stays decrypted later today. I'm running a gsi,(benzo ROM+ all my own customizations)rooted,with all the trimmings) the same mentality will have to follow, but it will be interesting to see how it goes with flashing stock fresh. I imagine restoring my nandroid will be fine and stay decrypted, but probably will have to flash stock, then after setup, back to twrp, wipe factory reset and flash the dm verity decryption zip..I think, I gotta just do it to be sure. Anyone who does this should share notes and that will help the community.
Here is a good question, wtf can I do to have lte again. ever since pie official, I lost lte.phone drops to 3g during calls only. I discovered this while searching for a fix for my volte. Hence,, switching to gsi's because they don't have volte and neither does my stock, even with fresh installs.i have t mobile.all the betas it worked fine.
Click to expand...
Click to collapse
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Tech_Savvy said:
How did u get wifi to work on gsi..for me i can seem to get it working..and im using the last 8.1 vendor....for the lte go into dialer and *#*#4636#*#* and change the lte/utms/cdma setting around until u get it
Click to expand...
Click to collapse
I have found that after booting up a gsi, factory reset it. Then be sure not to root with magisk. Every time I tried it killed my data and wifi. Use phhhsuperuser ab zip. I think I may have had to flash my modem.img a time as well after the initial install.
And yeah I got it kinda, still no lte. I'm gonna try a modem img from the pie firmware..I think it is the problem
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
jacksummers said:
Has anyone had success in decrypting on stock? I cant get it and then i lose touch with the phone booted up. So in other words do not try to decrypt stock. U will wreck your phone and the only way to fix it is to flash stock via fastboot AND adb sideload. One or the other doesnt fix it for some reason. Has to be both.
Click to expand...
Click to collapse
Were you trying on stock oreo or pie?
governmentissuejoe said:
Were you trying on stock oreo or pie?
Click to expand...
Click to collapse
Both
jacksummers said:
Both
Click to expand...
Click to collapse
I tried it on stock Oreo and it works.
governmentissuejoe said:
I tried it on stock Oreo and it works.
Click to expand...
Click to collapse
Ok cool, I was worried I did this as a fluke. What was the steps u did?
jacksummers said:
Ok cool, I was worried I did this as a fluke. What was the steps u did?
Click to expand...
Click to collapse
So these are all the steps I took to get it to work. All of these steps may or may not be necessary. I used aer0zer0's stock dump for the lastest release of oreo and flashed the wipe all bat. It did its thing and wiped and flashed on both slots. I booted into the rom and finished initial setup and enabled adb in developer settings. I rebooted to bootloader and flashed twrp to inactive slot. I booted into recovery and selected the format data option and typed yes. I rebooted to bootloader and reflashed twrp. When I booted into recovery I transferred the stockboot.img, magisk 17.1 zip, and disable encryption zip to the phone. I flashed the stockboot.img to the boot partition. I then flashed the disable encryption zip. I then mounted the system partition and flashed the magisk zip. Finally, I rebooted into the rom and set pin and fingerprint. I installed EX Kernel Manager and created a backup of the decrypted magisked boot.img just in case. I flashed twrp through ex kernel manager and rebooted to recovery. Everything stayed decrypted. I flashed my newly created boot.img backup and booted back to my rom. Thats it. I hope I remembered everything. I hope this helps. Again, I do not know if all the steps I took are required but it worked for me.

Fix infinite boot without resetting data?

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.

Cannot boot phone after updating

The problem is kinda complicated. Previously, I flashed a custom ROM on my phone (a modified version of Oxygen OS). Just now, I updated my phone using the official ROM downloaded from Oneplus's official site (no idea what I was thinking), and I was only able to boot into the stock recovery. So, I tried reinstalling the TWRP recovery. I was able to boot the phone, but upon boot, it would say something like "Settings stopped working" and it would shut down immediately. I tried flashing a couple of different ROMs using the Install option in TWRP, but I still get the same error when booting my phone. Is there anyway to solve this problem? If not, would there be any way for me to recover my files at least?
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
CosmicInsight said:
Go back to factory stock using the MSM tool. If you can get to TWRP you can backup your stuff.
Click to expand...
Click to collapse
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
leniumC said:
I am able to get to TWRP right now. However, I did noticed that the Data partition in the TWRP Backup option is only 76MB. Does this mean that my data's gone already somehow?
Click to expand...
Click to collapse
Yeah, probably.

Categories

Resources