Database Info

[SOLVED] Stuck on TWRP splash screen after restore

Just tried to restore a backup for the first time using official TWRP. At the end of restore it had red text saying something like couldn't mount system but said restore complete. Tried booting and it gives the unlock warning then goes to black screen and led light out up constantly and doesn't boot. I try to boot back into recovery and just stays on TWRP splash screen. What did I do wrong and how do I fix this?

try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558

Bradl79 said:
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Just did. I can successfully boot into twrp now every time but still wont boot into OOS. Still have black screen and white solid led.

Do u have the stock oxygenos full zip on ur phone?

Bradl79 said:
try to reflash TWRP to official, u will have to use fastboot method
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Click to expand...
Click to collapse
Bradl79 said:
Do u have the stock oxygenos full zip on ur phone?
Click to expand...
Click to collapse
No. Can I download it from the oneplus site and transfer it via twrp file manager?

U may be better off using this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It is going to wipe ur internal storage though

vinnievegas said:
Just did. I can successfully boot into twrp now every time but still wont boot into OOS. Still have black screen and white solid led.
Click to expand...
Click to collapse
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.

mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
What full rom zip?

vinnievegas said:
What full rom zip?
Click to expand...
Click to collapse
Whatever OOS version you want. It will make you stock after a flash with official TWRP, but since you restore data from your backup, it will keep all apps and settings. That's why you flash TWRP.zip after OTA.zip finishes. It will replace your boot IMG with stock. Then after you boot into system, you can install magisk by flashing again in TWRP. You can't flash magisk right away because of the a/b partition. Causes an error.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
You can download full ROM zip of your choice from this thread. Either will work.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232

mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
mikex8593 said:
Whatever OOS version you want. It will make you stock after a flash with official TWRP, but since you restore data from your backup, it will keep all apps and settings. That's why you flash TWRP.zip after OTA.zip finishes. It will replace your boot IMG with stock. Then after you boot into system, you can install magisk by flashing again in TWRP. You can't flash magisk right away because of the a/b partition. Causes an error.
---------- Post added at 06:17 AM ---------- Previous post was at 06:14 AM ----------
You can download full ROM zip of your choice from this thread. Either will work.
https://forum.xda-developers.com/oneplus-6/how-to/official-oxygenos-5-1-5-ota-oneplus-6-t3794232
Click to expand...
Click to collapse
How do I get the rom to my phone?

vinnievegas said:
How do I get the rom to my phone?
Click to expand...
Click to collapse
I believe OTG works in official TWRP if you have OTG cable and usb. MTP works in unofficial TWRP but I'm not sure which one I that was. May have been this one but don't flash the fix. I think the fix disables MTP
https://forum.xda-developers.com/oneplus-6/how-to/recovery-twrp-3-2-1-1-hydrogen-oxygen-t3795770
Let me know how/if it works out for you.

Bradl79 said:
U may be better off using this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
It is going to wipe ur internal storage though
Click to expand...
Click to collapse
This saved me. Thank you so much. I wish I could have got the suggestion below to work cause I had a lot set up.
mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
I never could get the older unofficial twrp to boot so I couldn't transfer the rom. Had to use above suggestion. Thanks so much for all of you guys help. I'm just so happy to have a working phone again....
I did make a cloud backup of one of my twrp backups. wondering if I can restore that data once I've got twrp installed again and rooted?

vinnievegas said:
This saved me. Thank you so much. I wish I could have got the suggestion below to work cause I had a lot set up.
I never could get the older unofficial twrp to boot so I couldn't transfer the rom. Had to use above suggestion. Thanks so much for all of you guys help. I'm just so happy to have a working phone again....
I did make a cloud backup of one of my twrp backups. wondering if I can restore that data once I've got twrp installed again and rooted?
Click to expand...
Click to collapse
That should work. Just wipe data and cache in TWRP, then restore data from your old backup. I'd recommend keeping a zip file in internal storage of the ROM in case of emergency. That way you can recover without having to wipe internal storage again.

mikex8593 said:
Boot to TWRP, restore data only, flash the full ROM.zip, reflash official TWRP, reboot (may say there is no OS installed, ignore)
If you want magisk root, reboot into recovery after phone boots into OS, flash magisk and all modules should work again.
Click to expand...
Click to collapse
Old thread but thanks! I had same problem and your method worked for Xiaomi Mi A1

Similar, but reinstalling from scratch. I don want to preserve any data on divice.
By mounting Data partition from TWRP this is what you can see among other things
Internal Storage
NitrogenOS-Updates
Nitrogen-OS-P-kenzo-20190519.zip
I don't remember what next. Any link any link is sufficient and very welcome.
Also a suggestion on where to go to ask, if this is not the right place!
Mi device "xiaomi 3", is perfect for me!

Flashed 5.1.11 via TWRP now reboots to TWRP?

I went to reload 5.1.11 ..I think it might be because I forgot to remove my security features now keeps rebooting to TWPR
do I have to do a compete wipe now....or is there a simple method ?? Thanks for the help!

Did you have magisk installed? Did you install it again after flashing full ota and twrp?

ImSpiderman said:
Did you have magisk installed? Did you install it again after flashing full ota and twrp?
Click to expand...
Click to collapse
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP

double post

skyeking69 said:
Yes I followed the guide here.. full rom, TWRP installer, reboot to recovery, Magisk 16.4 reboot system..........boots back to TWRP
Click to expand...
Click to collapse
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update

ImSpiderman said:
Strange, that happened to me because i didn't Remember to reflash magisk...wait for someone else to answer but if it isn't a big deal for you i'll just factory reset, it's always good to do after a new update
Click to expand...
Click to collapse
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??

skyeking69 said:
Yeah I tried that too everything except internal storage...just wondering if I have to wipe that as well ??
Click to expand...
Click to collapse
No you don't have to

ImSpiderman said:
No you don't have to
Click to expand...
Click to collapse
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...

skyeking69 said:
Well I guess I'll wait for more ideas..... Or might just wipe internal and see what happens...
Click to expand...
Click to collapse
That didn't work? Really strange tho

See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter

Gradusr said:
See this. This article only applies to users running TWRP recovery on a rooted device. Don't have TWRP or don't know what this means? You're probably fine.
If you've recently installed or updated TWRP recovery, you might have faced that you can't install anything with it, and that the start screen is immediately shown when updating your device via Oxygen Updater.
Why is this happening to me?
From what it seems, this issue is caused by TWRP versions 3.2.2-0 and 3.2.3-0 being incompatible with the storage encryption technology present on OnePlus devices.
Normally, you're asked to enter your PIN or unlock pattern before installing an update / flashing something yourself. However, these new TWRP versions don't prompt for it anymore. Therefore, accessing the storage space of your device is no longer possible.
This is really frustrating, as almost all of your updates / .zip files are stored there. But luckily, there is a solution:
How do I fix this issue?
First of all, if you don't have encryption turned on or are not facing this issue, do not proceed with the steps below since flashing a new version of TWRP can be risky.
Now for the the solution: it involves downgrading TWRP to an earlier version, in which installing updates still worked correctly.
The downgrade can be done either by using a computer with the fastboot command, or by using flashing apps such as the Official TWRP app or Flashify on your device itself.
These are the steps you'll need to do:
- Make sure to download TWRP version 3.2.1-1 for your specific device. This is the version which worked fine, and is still fairly recent.
- Flash the version of TWRP using your method of choice. For fastboot users, connect your device to your computer in Fastboot mode and type fastboot flash recovery twrp-3.2.1-1-<yourdevice>.img. When using any of the flashing apps, browse to the correct TWRP.img file and flash it.
- Reboot your device. You'll now be able to access the working version of TWRP
- Do not update your TWRP version until it has been confirmed that this issue has been resolved.
Thanks to Peter Aarnoutse for reporting this issue.
Icon credit: Twitter
Click to expand...
Click to collapse
Thanks but I really don't understand this....first I don't know if encryption is on ? Don't think I have turned it off...2nd 3.2.2.0 worked fine for me before..I installed 5.1.9 and 5.1.11 with no problems.....it was when I tried to reinstall 5.1.11 and forgot to remove security features this happened now?
How old is this thread about TWRP 3.2.2.0 ?

It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)

WOS17 said:
It happened to me since the first time. what i do is wipe everything except internal, flash rom, flash twrp, reboot twrp, boot system, and then after set up, reboot recovery and flash magisk.
I dont know what is the problem ive never used a security feature.(maybe thats my problem)
Click to expand...
Click to collapse
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??

If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.

Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.

skyeking69 said:
I'll give that a try...... you have no pin or fingerprint or face unlock setup ??
Click to expand...
Click to collapse
No, any security just double tap to wake.
Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer

Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Thanks..I'll try that first....the TWRP I have is 3.2.2.0 from official page ( I think ?) I'll try 16.7 and see what happens..

WOS17 said:
No, any security just double tap to wake.
which TWRP version are you using? what Ive read is Magisk 16.7 has some problems like the pop up that say you have to contact your manufacturer
Click to expand...
Click to collapse
I'm using 3.2.2.0 which was working fine.....the guy below tells me to use 16.7 Magisk???? Geez not sure now ?

Gradusr said:
If you have face unlock and or pin than you have issues with the new twrp reed this article , I have posted than you understand it.
Click to expand...
Click to collapse
The thing is TWRP 3.2.2.0 does ask me to enter my pin code then goes to the options page...install, wipe, backup,restore...etc...

Nameless said:
Go to twrp and wipe dalvik/art cache, system, data *do not wipe internal* then flash 5.1.11 followed by twrp from xda, reboot to recovery again and flash *latest* Magisk 16.7 not 16.4, reboot system. 100% steps to use if doesn't work God knows whats haqppening to yours mate.
Click to expand...
Click to collapse
Geez ...now when I go to reboot to recovery it gives me a warning " No OS installed, are you sure you want to reboot?? " what do I do now ??

Can't install Magisk 17.1 on OxygenOS Pie Open Beta 2

Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
UPDATE (09/12) : Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx to exelinguy.

Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.

Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.

Azhar_Fahry said:
Just updated my phone to Open beta 2, dirty flashed it and it booted up. works perfectly fine. but after i tried to flash magisk 17.1 , it won't boot. stuck at the boot animation.
im using blu spark twrp to flash the magisk.
btw i had magisk installed on 5.1.11 and it works fine too.
any suggestions ? thxx.
Click to expand...
Click to collapse
Will upgrading reset the phone or will just upgrade with the same data?

sanu26661 said:
Will upgrading reset the phone or will just upgrade with the same data?
Click to expand...
Click to collapse
it depends on the situation. If you're on the Open beta updating to a newer build, the data will still be there, but if you're on the open beta downgrading a build or downgrading to oreo, your data will be lost.

whizeguy said:
Try to do the whole flash procedure again.
Boot into recovery
Flash beta2
Flash twrp
Reboot to twrp
Flash magisk
Boot to system
That way it will be installed on both partitions, could/should do the trick.
Click to expand...
Click to collapse
I already tried, still nothing

try to change slot A / B

dum143 said:
try to change slot A / B
Click to expand...
Click to collapse
When you install rom, install twrp and reboot to twrp it changes slot. If he has done it 2 times both slots are tested.

exelinguy said:
Flash the Magisk uninstaller first to remove any old files, and then flash 17.1 zip again.
Click to expand...
Click to collapse
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop

Azhar_Fahry said:
I tried to wipe the system and flash the rom, thought that will remove all the Magisk files that already installed before. but then I flash magisk again, it still nothing. just bootloop
Click to expand...
Click to collapse
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post

exelinguy said:
Nonetheless, just try flashing the magisk uninstaller from here and reflashing magisk 17.1 zip
Refer to section Hotfix v17.1 in topjohnwu's update post
Click to expand...
Click to collapse
Issues fixed by installing the uninstaller first then install the magisk 17.1 zip. thx for helping me bro. appreciate it.

I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.

whymista said:
I'm having the same issue but now twrp won't even show my files although I haven't wiped it. Its only showing like 9gb of storage.
Click to expand...
Click to collapse
have u tried to flash the open beta rom zip? I got that problem too, it's shows random folder and it contains nothing. but after I flashed the open beta rom and re flash the twrp from fastboot, it's fixed.

No OS installed in TWRP

Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?

raptax said:
Hi guys
I was trying some of custom rom on my OP6 and I wanted to go back to Oxygen OS. So i did a clean installation with system wipe and i flashed the last full OTA update. But since i can't boot to system anymore, TWRP always displays that there is no OS installed despite the fact that I've tried several rom . Is this the first time it's done this to me how can I fix it?
Click to expand...
Click to collapse
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data

Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again

raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
Exactly! I'm glad to had help you sometimes if something is done wrong TWRP is dangerous

raptax said:
I tried your solution ..... and it worked thx man
I don't know why there was a problem with TWRP but the important thing is that my phone is alive again
Click to expand...
Click to collapse
If you wipe system, then flash oos ROM, TWRP will think there is no os. You can just ignore and boot.

Wiping system then flashing any time will make twrp display "no os installed" it does this because it hasn't created files for twrp to check if you have a ton installed. Flashing twrp then rebooting to twrp fixes it.

Reboot to stock recovery?
Hitman478™ said:
The best suggestion I can give you is to flash stock oos with TWRP, reboot to stock recovery, without flashing anything else, wipe data from stock recovery and startup system.. if it is working you can flash back TWRP and magisk if you need it
Just be careful because at your point is easy to lose all of your stored data
Click to expand...
Click to collapse
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?

5xonlineage said:
Hi, need a little bit of support, since I'm new to this as well. I was in a working OOS open beta 25/28, but then I think I flashed the wrong zip (OOS 9.0.9?), and I was not able to boot to system. It kept going to "bootloader unlocked" screen and custom recovery. Currently in TWRP blu_spark 3.3.1-x v. 9.109, and it's showing me no OS installed when I attempt to reboot. I haven't rebooted to system yet.
All the folders in my /sdcard is gibberish... if I try to push a file to it, it says "Required key not available." I did remove all security/passwords from my phone before doing any updates/backups.
I completed a wipe cache/dalvik/system via TWRP, and flashed the OOS OTA stable Android 10 zip downloaded directly from OnePlus Support. Considering this situation, do you still think it's safe for me to reboot to system? Then how do I get to stock recovery from there--is that by holding down the buttons?
Click to expand...
Click to collapse
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.

Fastboot method?
°Washy said:
No, your internal storage Is like trash cause the last rom you flashed has older security patch than oos10. Your device Is now encrypted and wont boot to system. I Guess you have to erase all via MSN tool or fastboot signed rom. Even if you wiped what mentioned above, your problem still be the data.
Click to expand...
Click to collapse
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.

5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.

5xonlineage said:
Thank you for replying. I'm relieved that you know of a couple methods to try.
Is using "Format Data" in TWRP an option for dealing with the encryption??
For the MSN tool, can I use this one? Tried looking around, but it's unclear. "[TOOL] MsmDownloadTool V4.0 International (Oxygen OS 5.1.5)" https://forum.xda-developers.com/on...wnloadtool-v4-0-international-t3798892/page10
I would be more comfortable with using fastboot, but am I at any risk of having lost fastboot, or can I just turn off my device from TWRP right now and hold down the buttons to get there? Afraid to move out of TWRP right now, in case I can't get back. I do have twrp-3.3.1-18-enchilada-Q-mauronofrio.img that I can run from fastboot if needed.
By "signed rom," do you mean I can simply flash one of the zips here from fastboot? "[OnePlus 6][ROM][OTA][Oxygen OS] Mirrors for official Oxygen OS ROMs and OTA updates" https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244
Thanks again.
Click to expand...
Click to collapse
Do you solve, man?

Fastboot ROM
°Washy said:
I hardbricked my device about 10 times and i was able to recovery It even from a blank screen. Btw format data Will erase all your data but also the internal storage. About fastboot dont be afraid, go under twrp reboot section and reboot to bootloader. Then go under xda op6 guide section and search for mirrors for fastboot rom guide by Mauronofrio. He pushed my ass out the **** a lot of time.
P.s. Sorry but I dunno how to paste a link via xda app. Yes, ik! It's a vert newbie thing.
Click to expand...
Click to collapse
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?

5xonlineage said:
That's awesome, I'm starting to grasp how much of a genius Mauronofrio is, after so many people referencing his work.
In his guide, he says, "These ROMs can't be used to update or downgrade your phone but just to restore your phone, so don't use them to come back to oreo or to update from oreo to pie." This may be a dumb question, but how do I know which zip/OOS version to flash, when I don't have a functioning OS on my phone?
Click to expand...
Click to collapse
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.

Magisk, boot img?
°Washy said:
I talked with Mauronofrio in pm and he said me that you could solve your issue simply flash the ROM you want and format data after flash that one. Remember that your internal will be wiped but it would happen in any scenario we talked.
Click to expand...
Click to collapse
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?

5xonlineage said:
That worked! And starstruck that you were able to check that with him. I flashed Mauronofrio's fastboot ROM for 10.3.2 and it rebooted (WOW). I clicked through the Google setup pages and checked that my data and wifi worked.
I then went back into fastboot, booted M's twrp img, fomatted data, and then installed twrp-3.3.1-x_blu_spark_v9.109_op6.zip, rebooted into recovery.
Then I think I made a mistake, because I installed Magisk-v20.4.zip. It succeeded, but now I can't boot into system anymore. Is it too late to flash the 10.3.2 boot.img?
Click to expand...
Click to collapse
No. Just flash stock boot image if magisk broke something.

Rooted
°Washy said:
No. Just flash stock boot image if magisk broke something.
Click to expand...
Click to collapse
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!

5xonlineage said:
I ended up following the guide to Magisk Root without TWRP for OnePlus 6 Oxygen OS https://forum.xda-developers.com/oneplus-6/how-to/patched-boot-image-magisk-16-7-beta-t3818853 since it was referenced by Mauronofrio's post for having issues getting his TWRP to work with latest Magisk.
Someone posted a patched boot.img for 10.3.2, so now I'm rooted without TWRP. Priorities. Now all I need is for special characters and emojis to work Will keep an eye on other threads.
I'm learning a lot, thanks so much for all your help. You pointed me in the right direction when I was not sure what the hell to do!
Click to expand...
Click to collapse
I followed that thread for the first A10 release cause there wasn't a worked twrp yet. You are welcome man, when I feel myself usefull I always try to help.

Rooting of Poco x2 MIUI 12

Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......

KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.

KartikBapna said:
Does any one know how to root POCO X2 running on MIUI 12 ?
I tried each and every method which worked on MIUI 11 but always ended up in bootloop
Plz help......
Click to expand...
Click to collapse
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.

tuskan_supa said:
I successfully rooted the EU miui 12 rom earlier and there wasn't any bootloop.
Click to expand...
Click to collapse
superminnu said:
Be careful brother, there are no fastboot images of MIUI 12. If you end up bricking it, you'll have to wait 1 whole month for "miui 12 fastboot imgs" to arrive.
Click to expand...
Click to collapse
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?

KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Are you on the Indian build or EU build?

tuskan_supa said:
Are you on the Indian build or EU build?
Click to expand...
Click to collapse
Indian

KartikBapna said:
Indian
Click to expand...
Click to collapse
I did successfully on the EU build not on Indian. I guess you should wait few days maybe someone will try and figure it out.

KartikBapna said:
How did you did it ?
You did it on POCO X2 ?
And also do you know how to disable Dm-Verity to write in system partition ?
Click to expand...
Click to collapse
Isn't flash Magisk will always disable dm-verity?

Never_Sm1le said:
Isn't flash Magisk will always disable dm-verity?
Click to expand...
Click to collapse
It didn't disable it in my POCO....

KartikBapna said:
It didn't disable it in my POCO....
Click to expand...
Click to collapse
And now I realize the problem in you answer. Why did you need to write into the system partition?

Never_Sm1le said:
And now I realize the problem in you answer. Why did you need to write into the system partition?
Click to expand...
Click to collapse
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.

KartikBapna said:
What is the advantage of root access if you can only read partitions not write them
And also, I want to install and uninstall apps in system partition.
Click to expand...
Click to collapse
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.

Never_Sm1le said:
You can't, because since Android 10 Google made the /system partition read-only. You can use adb to disable those app, uninstall apps in /system does not help you gain any free space anyway.
Click to expand...
Click to collapse
I don't want any free space just want to remove bloatware and install some apps in system like appninja's app

KartikBapna said:
I don't want any free space just want to remove bloatware and install some apps in system so like appninja's app
Click to expand...
Click to collapse
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school

Never_Sm1le said:
you can remove bloat with adb command, and install app in system using app systemizer. Install things in /system is old-school
Click to expand...
Click to collapse
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk

KartikBapna said:
Can't install apps with systemizer because app always crashes after moving to system.
Root is used for many things like running modules so my problem is still there how to root Poco X2 running on MIUI 12
Also systemizer is a module which requires root as well as magisk
Click to expand...
Click to collapse
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.

Never_Sm1le said:
Do as usual? Or there's a different thing involved? On my redmi K30 MIUI 12, things is as simple as unlock bootloader, boot the recovery, do not swipe modify system then flash the recovery, reboot to recovery then flash magisk. I have never encounter dm-verity before when follow these steps.
Click to expand...
Click to collapse
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop

KartikBapna said:
Things I have tried after unlocking bootloader and then flashing the recovery
1) flash magisk zip result bootloop
2) flash patched boot.img result bootloop
3) flash patched recovery.img result bootloop
In MIUI 11 method 2 worked
Method 1 always gave bootloop
Click to expand...
Click to collapse
Did you use fastboot flash twrp.img or fastboot boot twrp.img?

Never_Sm1le said:
Did you use fastboot flash twrp.img or fastboot boot twrp.img?
Click to expand...
Click to collapse
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.

KartikBapna said:
I flashed twrp that means I used
fastboot flash recovery twrp.img
And then to boot
fastboot boot twrp.img
I flashed patched boot.img from twrp.
My phone boots up with twrp flashed.
Click to expand...
Click to collapse
Try my way: boot TWRP then flash TWRP.img from TWRP. Reboot to recovery again then flash Magisk zip. Flash patched boot.img is unnecessary, like Topjohnwu said it's only for devices without TWRP. Beside if you want to use the patched method, you must patch the stock recovery image not TWRP.