Database Info

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

Tried Multiple Ways to get Android 10...All Result in some sort of Bootloop

So I have a rooted Pixel 3 through Magisk that I have been updating monthly up until this point via flashing the factory image with the flash.bat edited to remove "-w" from it to ensure that my phone does not become wiped after flashing each month's update. Afterwards, I would boot up the temporary TWRP image to then install the Magisk zip to re-root it. This had worked well up until this point. However, this month with the Android 10 update, this method has failed me. For this month, I did the exact same thing...download the factory image extract the image and other parts (including the flash.bat file), edit the flash.bat file and run. The issue was after flashing, the phone would try to boot and then get stuck at the G-logo with the loading bar under. It would use up about 5-10 mins to try and boot up, then fail, and then reboot again, fail again a second time and then just go fastboot mode. I tried this with both the .019 and .020 firmware and both failed me. In order to fix my phone, I'd just install the factory image of the August update instead, which had no issue.
I next attempted to ADB sideload the OTA update. I made sure to start with an unrooted install of the August update (by doing what I said above), and then using stock recovery would use ADB sideload with the new Sept OTA update. After sideloading, when trying to boot up the phone would attempt to boot around 7-9 times and just fail as it kept trying and trying to load up. Again, needed to fix it by flashing the August update.
I've done a bit of reading and it seems people have done factory resets and wipes of the phone before finally having success updating their phone to Android 10. I'm really hoping a method to fix this WITHOUT needing to do a factory wipe of my phone....

if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.

guest12233213113 said:
if you haven't already, try downloading the latest fastboot binaries from google.
Also FYI rooting Android Q on Pixel 3 is still difficult because TWRP doesn't support Android Q yet.
Click to expand...
Click to collapse
Are you referring to the SDK Platform tools? I was using version 29.0.2 from July for the past week until I recently saw 29.0.3 popup in the last day or so (was released a few days AFTER the factory images for Android 10 were released). Have tried with 29.0.3 and still not working. I get the issue "no valid slot to boot".

You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.

ktdt00 said:
You might have already tried it but if not you could try flash without -w both slots just to make sure everything is synced up? I've had to do this once in a while to correct weird stuff. There may be better ways but when I remove -w I then add --skip-reboot. Then you can change slots with 'fastboot set_active SLOT' after the flash without rebooting and then simply run the flash again.
Click to expand...
Click to collapse
Just tried your suggestion of flashing to both slots. Unfortunately, same result.

Toronadian said:
Just tried your suggestion of flashing to both slots. Unfortunately, same result.
Click to expand...
Click to collapse
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.

jd1639 said:
What version of magisk manager are you using? You need the canary build. Then modify the boot image with it and flash that thru fastboot. You can't flash the magisk zip in twrp anymore, at this time.
Click to expand...
Click to collapse
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.

Toronadian said:
Since attempting to switch to Android 10, I've been using the latest Canary build of Magisk Manager, currently 7.3.3-f383d11d (234).
The thing though is that it's bootlooping before I even attempt to root. Like after attempting to update the firmware on it's first attempt the device is bootlooping. It's happening when it's stock (no patched boot image. I've tried it with both the stock firmware, and also flashing the patched boot image before it's first boot up after the update and both cases there's a bootloop.
Click to expand...
Click to collapse
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.

jd1639 said:
You possibly need to completely uninstall magisk. But of course twrp is not working on 10 so that's a non- starter. See the last 3 or 4 pages of the twrp thread for the 3xl. @Tulsadiver has a boot image file that i think will work for you.
Click to expand...
Click to collapse
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?

Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.

jd1639 said:
No, i think you need to do it now. You have some half installed magisk and it's not letting you boot. You need a work around that to get it to boot. If i read correctly, you've already tried to flash the stock firmware with the - w in the flash all batch file. But check out that thread in the 3xl forum and see if others have been successful with it.
Click to expand...
Click to collapse
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?

Toronadian said:
Are you referring to uninstalling Magisk on Android Pie before trying to flash Android 10?
Click to expand...
Click to collapse
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Toronadian said:
If you're talking about right now, I'm back on August update, so still Android 9, with my phone rooted via Magisk and everything is currently functional. So use TWRP, flash the latest Magisk Uninstaller?
Afterwards what should I do after? I'm looking in the TWRP thread for the 3XL, is THIS the boot image you would like me to try? Should I be flashing that boot image AFTER updating to Android 10 (if it works)?
Click to expand...
Click to collapse
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.

Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?

Toronadian said:
Alright I'll try running the magisk uninstaller zip in twrp later tonight.
I haven't installed any modules but I did use the systemless hosts setting (for Adaway) and I do see it in my "modules" tab. Wonder if that's the culprit.
The boot image you have posted, is that to be flashed after/if Android 10 boots up successfully after flashing the factory image?
Click to expand...
Click to collapse
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.

Tulsadiver said:
Try fastboot boot image-new.img, this image. It should boot core-only mode and you can then see if you have some modules installed that need to be removed (/data/ADB/modules). It is not zipped. Just rename it as image-new.img
https://www.androidfilehost.com/?fid=1899786940962585361
---------- Post added at 05:06 PM ---------- Previous post was at 05:03 PM ----------
Yes, flash uninstaller if you can or maybe in magisk manager click uninstall. Modules survive updates and you might have pie modules that obviously aren't meant for Android 10.
Click to expand...
Click to collapse
Tulsadiver said:
Curious, how do you run the uninstaller in TWRP without a working TWRP?
The image I posted is to recover from bootloop caused by bad modules. Phone should boot up with modules disabled.
Click to expand...
Click to collapse
I boot the temporary TWRP image for Android 9 as it works on that. I'd assume I would use the install option with the uninstaller zip? Keep in mind currently I'm on Android 9 right now (every time I bootloop due to the Android 10 flashing not working, I run the flash.bat script to reinstall the August firmware).
And speaking of nonworking TWRP on Android 10...if for some reason magisk causes bootloop, in order to uninstall magisk, would I need to adb sideload it then?

OK seriously....really have no idea what the issue is. In TWRP on Android 9, I flashed the Magisk Uninstaller zip then attempted to run the flash.bat file to try and flash Android 10. Exact same issue before with the bootloop. Before that, I also tried flashing Android 10 after I had removed the Systemless Hosts "module" that was there (yes, I did restart the phone first after removing it), same thing with the bootloop. I have no clue.

Update Sept. 24:
Whelp, seems like people are just as out of ideas as I am. I tried today the NEW firmware Google just released (.20.C3, differs from the one released earlier in the month) as well as the newest SDK Platform Tools (29.0.4, a second update that was released in September), still not working. I installed the factory image using the edited flash-all.bat file (removing "-w") and again, device tries to boot up twice and then restart back in fastboot mode, with the issue being "no valid slot to boot".
EDIT: Re-flashed August firmware back onto the phone, and then tried to sideload the new .20.C3 firmware as a OTA (yes, I made sure to use the OTA zip and not the factory image), now just continuously bootlooping. I think I'm on bootloop #5 or 6 right now.

FINALLY have a positive update. I have Cerberus, an anti-theft app on my phone that I tried to uninstall just for the sake of trying to see if some apps were causing compatibility issues. I was trying this after reading one of the really long threads on the Google support threads that someone managed to get the Android 10 update to work AFTER removing some apps. After taking some time to finally remove Cerberus for the time being, I once again tried to flash the factory image for Android 10 (the newest one, .20.C3) and it ACTUALLY managed to work. I'm now finally on Android 10.
With my own device finally figured out, I think I may give my wife and dad's devices a try to update to Android 10 (they're on Pixel 2 and 2XL respectively). I installed Cerberus on their devices as well and I think I'm gonna try removing that first and seeing if that manages to allow me to update the Pixel 2 and the 2XL to Android 10.

Messed up upgrading to 10.0.1

So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?

Reflash 10.0.1 with the system Updater in settings using local upgrade option. Use Oxygen Updater to re-download if you removed the file. Then through fastboot, boot up twrp (fastboot boot twrp.img) and flash magisk. Unofficial TWRP for Android Q is available in the development forum.

Thank you!
Did exactly what you said and now I have WiFi and sounds again!

E30Nova said:
Thank you!
Did exactly what you said and now I have WiFi and sounds again!
Click to expand...
Click to collapse
No problem. This was due to boot.img mismatch with system. I'd recommend staying away from downloading and flashing patched images.
There's a thread here that explains how to update without losing root, always follow those steps.
https://forum.xda-developers.com/oneplus-7-pro/how-to/successfully-upgraded-to-9-5-7-t3937414
To summarise:
- Download the zip through Oxygen Updater.
- Settings > System > System Update > Cog icon > Local upgrade.
- Select zip. Don't reboot after flashing.
- Open magisk & click install.
- Select after OTA option and then reboot.
If you want to keep TWRP, I would suggest re-downloading the installer and flashing it from magisk instead of using the retention script. After reinstalling magisk (after OTA) and rebooting, you should flash the twrp installer through magisk and then reinstall magisk with the direct install option.

Yeah, I knew it was going to screw stuff up, but I did it anyway.
It's not the first time I knew I shouldn't do something but did it anyway, lol.
At least it was a simple fix, and I didn't lose any data. Maybe my stupidity will hopefully be a lesson to others. If it seems like a bad idea or common sense says not to do it, don't do it, lol.
Thanks again.

E30Nova said:
So I messed up while flashing 10.0.1 just now.
I mean, it worked, technically. But I'm on the AA rom, and flashed a patched boot image from 10.0 to get magisk and TWRP.
But now I can't turn on WiFi and I have no audio.
Volume is maxed out, slider switch is in the ring position, but I have no audio at all.
I'm guessing it's due to the incorrect boot image being used, but I couldn't find a patched 10.0.1 image to use.
I know, I goofed.
Any way to fix things without having to wipe and start over?
Click to expand...
Click to collapse
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------
disbeyad999989 said:
I just tried to post the rooted boot img for 10.1 for your but it says the file is too large, if you send me your email address i can send it to you.
Click to expand...
Click to collapse
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.

disbeyad999989 said:
Just remember that you should only flash this if you are trying to root without twrp otherwise follow the instructions in the thread the other guy a few posts up showed you.
Click to expand...
Click to collapse
You can always simply boot twrp.img without flashing. (Just make sure you use the right image matching the currently installed android version) I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
EDIT: This user has solved his problem though. Only commenting for posterity.

kgs1992 said:
You can always simply boot twrp.img without flashing. I would consider it much safer to flash magisk with twrp and let it patch the boot image rather than downloading a boot image that someone else patched since it might not match with your system.
Click to expand...
Click to collapse
That's very true i didn't think about that also, go that route better

Unresponsive touch screen in TWRP - how can install a ROM?

So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots? I wish I could check but since my touch screen doesn't work in TWRP..
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?

kerelberel said:
So I am not an entire noob when it comes to these things, I've flashed ROMs on phones for 8 years now, but this Moto G7 Power screwed me up good.
I tried installing CrDroid from this post. I didn't even notice the A/B part at first, I went through all the usual steps, I booted TWRP, then flashed it, rebooted into the installed TWRP, flashed CrDroid, GApps and Magisk and rebooted, hoping to start Android up. At that part it all screwed up. The phone didn't boot AT ALL, and after a while I found that blankflash zip file and managed to get into the bootloader again. The only thing I can do now is boot into TWRP, not flash, and when I boot, the touchscreen does not work.
So, where do I go from here? I now only have an unlocked bootloader to play with. What are the exact steps to flash the firmware? Why do I need to flash firmware to slot A anyway? Isn't or wasn't there firmware out of the box on the device? The guides for this phone are vague and people write really short and rambling sentences in the steps and mention certain files out of the blue without explanation or download link.
1 - Which firmware file do I need? I have an XT1955-4 bought in a Dutch shop called Belsimpel with no sim. I assume it's an international variant. Here is a download list of all the firmware variants, but how do I know which one to pick? Will it wipe things like IMEI data? The box says the type is M3C94, and it seems to be this international variant.
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
4 - The 'guide' in the CrDroid thread suddenly mentions copypartitions.zip. What is that file, where do I download it, and why do I need to flash it? It says I have to flash it in Slot A. Does TWRP give options to switch slots?
5 - During the actual ROM install part, the guide says Flash ROM.zip + TWRP_installer/boot.img ramdisk method Why do I need to install TWRP again? And what is the ramdisk method? How do you do that?
Can someone please explain in detail step by step what I need to do?
Click to expand...
Click to collapse
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip

vinoxflame said:
1. go to settings - system - about phone check build number, this is the firmware you'll need
2. there's a thread here regarding that matter check again
3. I'm not aware of this issue
4. you'll only need to flash that file once coming from stock rom - https://androidfilehost.com/?fid=4349826312261636295
5. because it be overwritten by lineage recovery.
ramdisk method is just another way of installing twrp back when we still dont have the installer zip
Click to expand...
Click to collapse
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
then try another version of twrp or the unofficial orangefox recovery for our device

vinoxflame said:
then try another version of twrp or the unofficial orangefox recovery for our device
Click to expand...
Click to collapse
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.

kerelberel said:
I tried an older version of TWRP which didn't work either. I am not aware of Orangefox, but I don't see any mention, official or unofficial for the G7 Power. There's no mention in the G7 Power forum either.
Click to expand...
Click to collapse
it's on the telegram group

vinoxflame said:
it's on the telegram group
Click to expand...
Click to collapse
No it is not. There's no mention of G7 Power in the search results. Only E5.

kerelberel said:
No it is not. There's no mention of G7 Power in the search results. Only E5.
Click to expand...
Click to collapse
deleted

vinoxflame said:
https://t.me/mG7Power
tell me if it is not!!!!
Click to expand...
Click to collapse
From the desktop search in this one I couldn't find it: https://t.me/OrangeFoxRecovery I didn't know there was a separate chat for each device. But thanks.

FWIW when this happened to me I did the blankflash thing to get it back to bootloader. Then I used the LMSA tool from Motorola to do a rescue/restore.
I also used LMSA to force the update to the most recent security update. In general, it seems a very useful utility.
https://www.motorola.com/us/lenovo-motorola-smart-assistant

I had this issue after blankflashing this temperamental device out of a brick. While in twrp you can do "adb shell" then "twrp install /path/to/zip" I think this has to do with new twrp versions on older firmwares

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done.
---------- Post added at 06:06 PM ---------- Previous post was at 05:58 PM ----------
kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
When i had this issue go reboot fastboot
then fastboot boot recovery.img or twrp as your boot img do what you need to do just dont flash it to boot only boot from it so you preserve your real boot should fix the touch screen part only time i had prob like this is when i flashed twrp to recovery without disabling dm verity etc. But I cant even get a stock OTA since I flashed twrp as recovery nor can I find a RETUS stock recovery.img so far if i had that I can update and keep magisk etc, then reflash twrp when im done. The latest stock RETUS build i can find is here https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip but if i do that i will lose all my apps AGAIN etc I am trying to just get the stock recovery img from previous version so I can install the ota in magisk you just tap uninstall tap restore images to get stock boot as well then ota should work once its done go back into magisk and install to inactive slot but you will or could need TWRP A/B retention script so that you keep it even after ota...which you will first go in magisk tap uninstall restore images, but must have stock recovery not twrp installed at this time either from what i can tell, once ota is successful install the TWRP A/B Retention script but do this before you install magisk to inactive slot from magisk manager after that it should work. But I cannot locate a stock recovery.img thus far.... and I dont wanna redownload my apps right now, so I may just wait til I see a rom i really think ill like and say screw it.

kerelberel said:
I only have the boot loader, no stock ROM. I wiped that when I tried installing CrDroid, as I have written in my post. So I can't check my firmware if I don't have ROM installed. And I know which thread you mean because I linked the list of firmware from that thread in my post.
The big issue here is the touch screen not working. I can't do anything inside TWRP.
Click to expand...
Click to collapse
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.

s33b said:
I also installed crDroid and after that twrp-3.3.1-2-ocean.img was not responding to touch, but twrp-3.3.1-0-ocean.img works. (btw I was doing a fastboot -w in between.)
Edit:
Ah nevermind, I have it constantly when installed, with both versions.
Click to expand...
Click to collapse
I've flashed another stock rom (https://forum.xda-developers.com/g7-power/how-to/guide-moto-g7-power-supra-flash-to-t3927138) and it worked with twrp-3.3.1-0-ocean.img not with the newest.

kerelberel said:
2 - In the bootloader, what commands do I need to put into adb when I want to flash the firmware to partition A?
Click to expand...
Click to collapse
You use fastboot commands in the bootloader.
The firmware contains a flash file with all fastboot commands you'll need.
kerelberel said:
3 - When I boot into TWRP, my touchscreen does not work, so how can I even use it?
Click to expand...
Click to collapse
TWRP has adb enabled by default. So instead of TWRP you can use
Code:
abd shell twrp --help
So you can use the basic functions like backup, install, and so on.

I had the same issue...
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.

TheGuysGuysGuy said:
I'm not sure everyone is experiencing the same issue here, but I've been dealing with that exact problem the entire time I've had this phone. While this work around won't work every time, it will eventually work (for me within 3 tries). It doesn't matter if your "fastboot boot twrp.img" or running an installed version, all are the same. Even the latest 3.4.0.0.
As soon as you start recovery, start tapping the area of the screen where the "Advanced button" is in recovery. I mean tap as fast as you can, use two fingers if you need to. If it doesn't work right away, "adb reboot bootloader" and try again. I can get this to work within 3 tries. Its sucks and its stupid, but it works.
Click to expand...
Click to collapse
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)

roadkill42 said:
I getba link to one that works for u. https://t.me/CustoKernal_JavaShin_Mods/565. Fastboot boot (name of recovery)
Click to expand...
Click to collapse
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.

TheGuysGuysGuy said:
Again not everyone is experiencing this same issue. A custom kernel isn't going to help when its incompatible with my ROM. My stupid workaround works for "No Touch Screen Response" in TWRP as well as OrangeFox. Its happened to me in both. Happily cruising along on Paranoid Android Quartz.
Click to expand...
Click to collapse
The problem with the touch is the right driver needs to b installed that kernel I shared makes it work and stick I'm on it now go to tellagram group Moto g7 power support group both twrp and ofox there that works not the one from twrp it's self and the twrp there has some other features that one from official one has that don't work

This boot image gave me a touchscreen and allowed me to flash a regular twrp: hxxps://f.emvn.me/android-roms-and-stuff/twrp.3.4-kakarot.boot.img
Thanks to whoever made it.

Best/most efficient root method OP7P

I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.

Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!

You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Sent from my GM1913 using Tapatalk

Bagpuss said:
You only need a patched image if you don't want to install TWRP. If you install TWRP, I'd simply ADB sideload Magisk to get root.
That's what I've done and it works just fine.
This assumes that you're using a OnePlus 7 Pro, and not a 7T Pro. Not got a 7T, so can't comment on that.
Click to expand...
Click to collapse
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!

Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
Are you positive? I see TWRP install guides everywhere. From what I've read TWRP with magdisk (not SuperSU, us it's not open source) is the best way to root with the most flexibility. What if I'm running 10.03.0GM21AA, and there is no patched image? Do I need to roll back?

Lossyx said:
There is only one way to root, and that is by using a patched image. Check the guides section, there's probably a patched image of your device, if not, you'll have to make your own.
And what's your version? AA or BA?
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
What's the best phone with SD card feature that can run TWRP magdisk without issues like using banking apps and Netflix?
Forgive my ignorance, I am still in the learning process.

Lossyx said:
TWRP doesn't work on devices launched with Android 10, which has been discussed many times.
My reply above stands true, a patched boot image is the only way as for right now.
(And we're on a 7T Pro forum)
Sent from my OnePlus7TPro using XDA Labs
Click to expand...
Click to collapse
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
sixisixsix said:
I am running 10.05, I can't decide whether to install twrp, dd root, or magdisk. Given that I have the most current version of oxygen os, what would be the best way to root my phone?
Don't misinterpret my ignorance for lazyness, a majority of guides I've seen aren't recent and don't go over pros & cons of the method.
Thank you, I'm willing to donate for help.
Click to expand...
Click to collapse
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.

QUBiCA said:
No we're on a 7 Pro forum. And TWRP works fine on the 7 Pro, but you need a patched version of some sort last time I checked.
Click to expand...
Click to collapse
Oh damn, I'm actually stupid... How did I miss were on 7 Pro?!
@sixisixsix please ignore everything I've said! I will edit my posts.
Sorry once again
Sent from my OnePlus7TPro using XDA Labs

sixisixsix said:
AA. So do I need to roll back? I bought the OP7P because I stupidly assumed it would be as easy/flexible to root as my past OP devices. It's ironic I switched from a Samsung devices to a OP for the ability for a stress-free rooting experience and I got the same problem lol. I might just return the phone for another, I'd prefer something with an SD card slot anyway.
Click to expand...
Click to collapse
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
QUBiCA said:
To root my phone, I didn't even use TWRP. I downloaded the lastest OOS version from OnePlus, extracted the boot image, copied that to my phone, Magisk patched that boot image file (you don't need root for that, you can use the Magisk manager). Then unlocked the phone, and installed the bootloader I just patched while the phone was in bootloader mode (fastboot flash boot boot.img or whatever).
Might not be the easiest, but I think it's clean, however back then I did not know about the option to properly use TWRP. Maybe I can find it, but I know it's possible to just unlock the 7 Pro, and then from the bootloader boot to TWRP once without flashing it, and install Magisk.
Click to expand...
Click to collapse
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.

Lossyx said:
Edit: I'm stupid, I was in wrong forum. Please ignore this post and what I've said!
Click to expand...
Click to collapse
redpoint73 said:
I've found OP devices (having owned two now) to be easy to root, and very friendly to the mod/root community such as XDA. Samsung is the opposite, in my experience (although each Sammy device is different, some better than others in this regard).
The main complexity with the 7 Pro is not that it is an OP device per se; but that it has something called A/B partitions, which are used for "seamless" OTA updates (Pixel devices use this scheme also - as well as a number of other phones).
The thing with A/B partition devices, is that they do NOT have a discrete recovery partition that you can just flash TWRP to. Therefore, you need to patch the boot.img partition (which on A/B devices contains both kernel and recovery, along with ramdisk). It is a little trickier, and somewhat more of a learning curve. But once you've learned that basic difference, it is not too bad.
It seems that the list A/B partitions devices is growing. So while I'm not an expert in the industry or anything, it appears that this is where Android is going (A/B is certainly not going away anytime soon, in any case).
So while the SD card feature is a legitimate difference (and a discriminator for some), I would say you should not make the A/B partition difference scare you away from OP devices. Maybe "too much information", but you can read more about the A/B partition scheme here: https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
---------- Post added at 10:13 AM ---------- Previous post was at 10:05 AM ----------
Certainly a valid approach (fastboot flash a patched boot image). The "other" (TWRP) method works as well, and probably a little easier for most folks:
1) Unlock bootloader
2) fastboot boot twrp.img
Note that this is just remote booting a TWRP image, not installing it. It simply allows the next steps. You can't flash a TWRP image directly, for the reason I've noted above.
3) Once booted to TWRP, flash TWRP installer zip (OPTIONAL). This patched the boot.img so that TWRP is installed. You only need to do this if you want TWRP installed on the phone.
4) Also in "booted" TWRP, flash the Magisk zip.
The main fundamental difference, is that Magisk is patching the boot.img for you, instead of doing it yourself. Have the files (TWRP.zip and Magisk) on the phone before starting the process, and it is really pretty simple and fast.
The nice thing about the patched boot.img method, is that is worked even when TWRP method did not. This applied to when the phone was first released, and the command "fastboot boot" was broken (therefore not possible to fastboot boot TWRP). This happened again when the device was updated to Android 10. Although the developer got fastboot boot working fairly quickly in both circumstances.
Click to expand...
Click to collapse
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?

sixisixsix said:
Thank you for taking the time to respond to my post in such detail! Wouldn't installing TWRP give me more flexibility for future updates? If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
I don't think TWRP would give you more flexibility when it comes to updates, unless you are planning on switching ROMs often, but if this phone is your daily driver I would recommend against that.
If you unlock the phone your data will be wiped, but only once. After that it is completely up to you, if you switch ROMs and pick something that is completely different from stock, it is indeed recommended to wipe data to prevent weird issues. But for a regular system update (if you simply stick with the stock ROM and use Magisk for root, you can still receive normal updates from OnePlus), or an update of the same custom ROM, you do not need to wipe data. I wiped data only once, when I unlocked it, because I had to.
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct). What @redpoint73 explained is that instead of installing (AKA flashing) TWRP, it is possible to just start it up (boot it) once without installing it. From there you can install Magisk on your stock OnePlus ROM and use the benefits of a rooted system.

QUBiCA said:
Flashing/installing TWRP generally is not necessary and like @redpoint73 explained, with the "new" A/B system, it is not advised to flash TWRP as it is combined with the boot image (which your phone needs to start up, and is updated after every update, so after every update you will lose TWRP again if I am correct).
Click to expand...
Click to collapse
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
sixisixsix said:
Wouldn't installing TWRP give me more flexibility for future updates?
Click to expand...
Click to collapse
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
sixisixsix said:
If I go the flashed image route won't I need erase my data on my phone every time I update?
Click to expand...
Click to collapse
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.

redpoint73 said:
It is correct that you lose the TWRP install when you update (as well as losing root). But it is just a simple matter of flashing the TWRP installer zip after the update (I do this the same time as re-flashing Magisk after OTA update), which takes about 10 seconds to accomplish. I wouldn't personally take that as a reason to "not" flash TWRP. But it is a personal preference whether to install TWRP or not. The reasons to have TWRP installed on the phone are much reduced from previous devices. In the past I would have said that being rooted without a custom recovery is asking for trouble. But now, with A/B partitions, along with the fastboot stock ROMs, the choice becomes much less clear. To the point that installing TWRP is purely optional.
I still personally believe that having TWRP installed gives you more recovery options. But again, it is a personal choice, and certainly not mandatory by any means.
---------- Post added at 09:11 AM ---------- Previous post was at 09:01 AM ----------
Actually, no (as QUBiCA touched on above).
Reason being, OTA updates will still come through on this device (even rooted). And you can still flash (or put OTA files on the phone to flash) using the built-in update engine in the phone's settings menu. Which gives you the option to update to either A/B partition slot. Plus, you can just re-flash TWRP (if desired) and Magisk after the update, straight from the Magisk Manager.
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
No (again, just backing up the answer already provided). There is not a big difference between the two methods. In either case, you are patching the boot.img partition to be rooted (whether you flash a patched boot.img, or you have Magisk patch it for you). And in both cases, you don't need to wipe your data.
Click to expand...
Click to collapse
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk

sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Sent from my Redmi Note 8 Pro using Tapatalk
Click to expand...
Click to collapse
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.

tech_head said:
NO.
You need to go through the process and flash Magisk from inside Magisk Manager.
Click to expand...
Click to collapse
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?

sixisixsix said:
So if I used the patched version of 10.3.0 and another new version comes out I can just download it through settings and I will remained rooted?
Click to expand...
Click to collapse
You should get the OTA update and be able to download it through settings. BUT, after you install the update, you still need to do as I already said in order to remain rooted:
redpoint73 said:
The trick is to make sure you do NOT reboot immediately after an OTA update (when rooted). Then simply open Magisk Manager, flash TWRP as if it were a Magisk module (optional, if you want TWRP installed again). Then install Magisk again through the Magisk Manager as well.. Now you can reboot, and you will be updated with root.
Click to expand...
Click to collapse
---------- Post added at 09:28 AM ---------- Previous post was at 09:00 AM ----------
sixisixsix said:
Okay so I downloaded magdisk manager, I flashed the patched version of 10.03, then when I rebooted I hit install update on magdisk and when the phone rebooted it was no longer rooted.
Even the guides for flashing aren't in depth enough for me. Can you help me out real quick?
Click to expand...
Click to collapse
You seem to be mixing the two processes: Install update in Magisk is for when you update in the future. You shouldn't have to do this rooting the existing ROM with the patched boot.img method.
For the patched boot.img method, you should just be able to flash the patched boot.img, flash the Magisk apk, and open Magisk, and it should say rooted.
My recommendation is follow this guide: https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-bootloader-unlock-twrp-install-t3940368
I can't possibly see how it can be any more in depth.