Database Info

Constant softbrick while trying to root stock

Hi
I have flashed stock and no problem but I can't root it. I have flashed the latest SuperSU and many others zips and wiped cache and dalvik cache, but when I reboot it stucks in bootlogo. I have the latest TWRP recovery and I use stock MM 6.0.1 ROM.
What can I do?
Thanks

EvilHowl said:
Hi
I have flashed stock and no problem but I can't root it. I have flashed the latest SuperSU and many others zips and wiped cache and dalvik cache, but when I reboot it stucks in bootlogo. I have the latest TWRP recovery and I use stock MM 6.0.1 ROM.
What can I do?
Thanks
Click to expand...
Click to collapse
Read some posts on rooting... You can't root a Marshmallow device like you used too, systemless root is required...
Open TWRP, go to Advanced - Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
And flash SuperSU again, you should see a message about systemless install, then clear caches (takes forever) and rebooted and give it a while.
Sent from my Motorola XT1575 using XDA Labs

EvilHowl said:
Hi
I have flashed stock and no problem but I can't root it. I have flashed the latest SuperSU and many others zips and wiped cache and dalvik cache, but when I reboot it stucks in bootlogo. I have the latest TWRP recovery and I use stock MM 6.0.1 ROM.
What can I do?
Thanks
Click to expand...
Click to collapse
Flash supersu zip v2.62.3 ( http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip )
If you flash other version you will get bootloop.

Nikos dima said:
Flash supersu zip v2.62.3 ( http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip )
If you flash other version you will get bootloop.
Click to expand...
Click to collapse
Not true... You can flash this beta version without doing anything special, but any SuperSU v2.63 or above, including the current version, works perfectly if you create the /data/.supersu file containing "SYSTEMLESS=true" flag as noted in my previous post. It is not difficult and any newer version cleans up a "bad" regular system flash as well.
Sent from my Motorola XT1575 using XDA Labs

A SuperSU v2.62.3 installation will be updated to 2.76 via playstore.

acejavelin said:
Read some posts on rooting... You can't root a Marshmallow device like you used too, systemless root is required...
Open TWRP, go to Advanced - Terminal and enter:
echo SYSTEMLESS=true>>/data/.supersu
And flash SuperSU again, you should see a message about systemless install, then clear caches (takes forever) and rebooted and give it a while.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Registered for this forum specifically to thank you for this.
Lots of instructions found when googling for rooting the Moto G 3rd gen, some good, some not so good. Every one of them resulted in getting stuck at the Motorola bootloader unlocked warning page. Re-flashed back to stock firmware and had almost given up until I saw this post. Solved the problem.
Thanks!

[ROM][Nougat 7.0] LG G Pad X 8.0 V521 20G Stock and Debloated Rooted ROMs 2/22/2017

Heres the latest update from LG.
Must be at least 20f with TWRP to flash this.
To get TWRP go here: (Kdz to 20f if on 20g)
https://forum.xda-developers.com/showthread.php?t=3533338
Do NOT wipe system or you might get stuck in twrp bootloop.
**********************
FLASHING INSTRUCTIONS
**********************
1. MUST BE IN 20F.
2. DO NOT FORMAT SYSTEM.
2. TWRP BACKUP FIRST
3. Flash from TWRP.
DOWNLOAD
LG-V521-20G-Stock-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705254
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
***********************************
LG-V521-TWRP.ZIP (Thanks to shabbypenguin)
***Also adds flashing TWRP to recoverybak so if an error comes up your stock recovery doesn't get reflashed.
https://www.androidfilehost.com/?fid=673368273298934005
***********************************************
COMING FROM ANOTHER ROM FLASHING INSTRUCTIONS
***********************************************
1. TWRP BACKUP FIRST
2. PLACE ROM IN INTERNAL STORAGE
3. WIPE DATA, CACHE, DALVIK/ART CACHE, SYSTEM
4. FLASH ROM FROM INTERNAL STORAGE.
*****IF IT REBOOTS BEFORE FINISHING FLASH, PRESS AND HOLD VOLUME DOWN AND POWER TILL OFF.
*****THEN ON REBOOT WITH VOLUME DOWN AND POWER PRESS, LET GO OF POWER ONLY FOR A SLIT SECOND AND *****REPRESS TO GO INTO FACTORY RESET MODE. THEN SAY YET, AND IT WILL GET YOU BACK TO TWRP.
*****IN TWRP, GO TO REBOOT AND SELECT POWER OFF. THEN GO TO STEP 4.
**************
ERROR???
**************
If you wipe system then flash a rom you might get stuck in twrp bootloop.
Here's a fix by ralphwiggum1:
https://forum.xda-developers.com/showpost.php?p=70851933&postcount=39
If that fix fails, then flashing stock recovery is another option. Then you'll have to reroot and get twrp again. If your on 20g, you'll have to kdz 20f and start over.
LG-V521-STOCK-RECOVERY.zip
https://www.androidfilehost.com/?fid=745425885120710531
Sent from my LG-H811 using Tapatalk

Thank you!, working 100%

LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk

MicroMod777 said:
LG-V521-20G-Stock-Debloated-Rooted.zip
https://www.androidfilehost.com/?fid=529152257862705822
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
what was debloated?

SiNJiN76 said:
what was debloated?
Click to expand...
Click to collapse
Most gapps and tmo bloat.
Sent from my LG-V521 using Tapatalk

SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?

rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk

MicroMod777 said:
Odd. Flash just SuperSU then:
https://forum.xda-developers.com/showthread.php?t=3452703
Sent from my LG-H872 using Tapatalk
Click to expand...
Click to collapse
It went back to stock recovery after flashing the zip. adb reboot recovery takes me to stock recovery.
Vol Down + Power to boot, and letting go of Power holding down Vol Down, then pressing Power & Vol Up takes me to the "hard reset" prompt, and it actually wipes device when selecting yes. I'm thinking the recovery has changed in 20G and it wipes the device instead of taking you to recovery.
Joey's Root Checker shows "Sorry! Root access is not properly installed on this device". SuperSU shows "There's no SU binary installed and SuperSU cannot install it. This is a problem."
I have a feeling I'll have to downgrade to 20F using KDZ.
EDIT: Weird...FlashFire shows "Root was found, but access could not be acquired! Supported roots: SuperSU, Magisk, CM SU (SELinux/Permissive)) Found root: (null)".
Installed SuperSU app, no luck. Tried Superuser app, no luck.

rbadh91 said:
SuperSU is not detecting root in LG-V521-20G-Stock-Debloated-Rooted.zip
LG-V521-20G-Stock-Debloated-Rooted.zip doesn't seem to have TWRP either.
Am I missing something?
Click to expand...
Click to collapse
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.

NoMoreBackdoors said:
I had the same issue. Lost root and twrp. Had to downgrade and start from scratch.
Click to expand...
Click to collapse
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk

MicroMod777 said:
Yea I've had this happen multiple times now. Twrp is somewhat buggy where if theres a crash during flashing, or if you format the system partition, somehow theres a failsafe feature that restores the stock recovery.
I thought I had it figured out and made a flashable zip for twrp that also flashes it to the recoverybak partition. But it happened aga7n.
Sent from my LG-V521 using Tapatalk
Click to expand...
Click to collapse
There's another update on my tablet...(after flashing your zip from 2-22). Will you be doing another zip with this new update?

New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?

LvDisturbed1 said:
New update is 95.22MB. I'm guessing security update. I would be wary, as the 20g update patches dirty cow, but still allows downgrade to 20f. This could block downgrade. Any brave souls out there want to confirm?
Click to expand...
Click to collapse
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/fota
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Then reboot and all will be well.

sgrant said:
I know I'm late, but I just picked one of these tablets up this week. I didn't think much about what I was doing, and did all OTA updates that where available. This was on 10/25/2017 or so. I was able to then use Uppercut and LGUP to flash backwards to V52120i_00_0619.kdz and successfully root, and install TWRP.
I didn't keep stock long, I jumped over to Lineage OS 14.1.
Be warned though, on Lineage OS the weekly on 10/27/2017 will cause a bootloop in TWRP. At least it did for me. After install, and while stuck in bootloop it is pretty easy to fix:
1. Open ADB Shell and run the following 2 commands:
Then reboot and all will be well.
Click to expand...
Click to collapse
QUOTE

I've been running stock for a while and had this in a drawer for a year. I decided I'd start using it in my kitchen to pull up recipes on chrome. I decided to do a "factory reset" to start "clean" forgetting the warning not to do it. Now I'm stuck in a TWRP bootloop.
How can I get out of this?
Or should I switch to lineage?

Why there is no LG-V521-20N version?

[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 ??

Unable to root properly

So I have this TWRP backup that i restored through.
I install SUPERSU zip from TWRP, all the scripts run fine, no issues or interruptions.
However, once I boot up normally, go through the setup process of Android's first boot and install the Super User app, it does not detect root X(
I have tried flashing the latest BETA & stable SuperSU zips (2.82)
I have tried older SuperSU zips (2.79)
None of the above have worked for me,
I have a European HTC U11+
S-ON, Unlocked Bootloader, Build 1.24.400.3
Any help would be great

Found the FIX
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well

usmantahir said:
So every guide i've tried for my u11+ has been leading me to a debacle.
However, after days of restoring and resetting and reflashing and backing up, I have finally got my phone to root properly
Turns out none of the latest or typical Supersu zips worked for me.
So I went to this thread : https://www.teamandroid.com/2017/08/23/root-google-pixel-xl-android-80-oreo-software-update/2/
Downloaded this supersu zip : https://devfiles.co/download/wJDOxFEm/SR3-SuperSU-v2.82-SR3-20170813133244.zip
DO NOT BOOT THE RECOVERY IN THE GIVEN LINK, just flash the supersu
I hope this helps out other people as well
Click to expand...
Click to collapse
Why you didn't just use magisk? It is so simple...

Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)

usmantahir said:
Because I'm facing another issue, whenever I go to recovery after i setup my phone through normal boot, the password works at twrp but when I try to boot up, the device decryption password turns up invalid and I lose access to everything. It's a vicious cycle ?
Maybe it's cz I flashed a different build onto my phone
(Originally: 1.24.401.12, flashed: 1.24.400.3)
Click to expand...
Click to collapse
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread

skodann said:
Try to flash 1.24.401.7 ruu via sdcard method and after that flash corresponding recovery. You can find it in recovery thread
Click to expand...
Click to collapse
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up

usmantahir said:
It won't flash.. shows some sort of incompatibility
Also, i tried flashing the system.img of 1.24.401.12, it still reads 1.24.401.3 when i boot up
Click to expand...
Click to collapse
It wouldnt flash but it did successfully install the full RUU zip of 1.24.401.7 using the SDCard method
And later, I was able to take the OTA to the latest build 1.24.401.12