Develop Bugs

Stuck rooting

Hi all, so I have Verizon's Pixel XL. I have unlocked it successfully and had rooted. I asked on the forums about upgrading the OTA update and was told it was fine. After doing so, I noticed my SuperSU was gone (although I might have lost it earlier and not noticed). So after trying to get it back and keeping getting stuck, I bit the bullet and ADB sideloaded the factory image from google (NDE63X) and got it able to boot up. Yay.
So then I ran the 'adb reboot bootloader' command, then verified my device was connected with 'fastboot devices' and finally I ran 'fastboot boot boot-to-root.img'. And here I am, stuck on the splash screen again.
So I looked around and saw some mentions of people that had used older versions of Chainfire's SuperSU. I tried the newer one (2.78 SR3) and the same thing happened. I do see that there is a SR5, but I also see Chainfire's comment "Do not use the SuperSU ZIP on work-in-progress TWRP releases for Pixel, it will not work - use the model specific links above instead.
I can get it to run just fine without using chainfire's supersu...but then I don't have the supersu app or any real gains from having rooted.
So, I feel like I must be doing something wrong. Any suggestions?

@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.

cam30era said:
@smokeydriver,
You probably should update your Android SDK package. This problem can also be caused by an obsolete fastboot.
Click to expand...
Click to collapse
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!

smokeydriver said:
I can give it a shot, but I only installed minimal adb yesterday on my new laptop. Thanks!
Click to expand...
Click to collapse
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.

cam30era said:
I understand. Here's the thing: I don't know if minimal has up to date ADB and fastboot for Android 7.1.1.
Click to expand...
Click to collapse
The OTA update I took only got me to a new version of 7.1, not 7.1.1 (from NDE63P to NDE63X). It still shows an available update to 7.1.1 which I have *not* done.

Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.

Nitemare3219 said:
Try using the Unified Toolkit. It saved me from having a bootloop disaster when I tried upgrading from 7.1.1 due to poor instruction availability around the web. It should fix whatever problem you are having, even if that means flashing the factory image first again.
Click to expand...
Click to collapse
I've tried, but keep getting an error 21 code that it can't install...I tried this with SR5 and SR2.

How I Rooted
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.

FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb boot.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
Ok, I must be doing something wrong on a very basic level. It gave me error 21 (signature verification error) when trying to use the unified android tookit to install 7.1. Anyways, I'll just move on and skip that step and see what happens.

Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Dees_Troy said:
How to install SuperSU SR5 on TWRP RC1: In TWRP tap on Advanced -> File Manager and scroll to and select the fstab.marlin or fstab.sailfish file and then delete it.
Click to expand...
Click to collapse

FreeSoftwareServers said:
Personally, I'd flash to latest OTA via Unified Android Toolkit before starting this process.
Then use Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)
AT this point you should already have 2 zips on your phone, TWRP-RC1 and SuperSU v5.
Flash TWRP, then SuperSU.
Reboot into OS, confirm root, give it 5 minutes.
Reboot back to Recovery and flash Kernel if desired.
Do not flash root with RC-1 (thats why we flashed root while using Alpha2 adb twrp.img), do not restore backups made with Alpha2 using RC1 or vic versa. AKA Backup and Restore with same version of TWRP.
Click to expand...
Click to collapse
I transferred those 2 files to my download folder on my phone, ran the twrp.img script, and then when I go in...the file names are not normal. Everything is random letters and numbers. Again, I feel like I'm making some stupid basic mistake that I don't understand (and I've rooted plenty of phones).

spotmark said:
Flashing SuperSU SR5 works just fine with TWRP RC1. All you have to do is delete the file you're told to before flashing.
Click to expand...
Click to collapse
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?

smokeydriver said:
So I go in TWRP to advanced, file manager, and I don't see the names of those files. Are they buried in a folder?
Click to expand...
Click to collapse
You have TWRP RC1 installed?

spotmark said:
You have TWRP RC1 installed?
Click to expand...
Click to collapse
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.

smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Ah, I see. I misunderstood. I thought you were just under the impression that you couldn't flash SU with RC1. My apologies.

Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?

smokeydriver said:
Nope...stuck before that. I'm using Minimal ADB to flashboot boot twrp.img (The Alpha2 Version)...but then I go to the sd card and it's all random letters and numbers...so I can't install twrp rc1.
Click to expand...
Click to collapse
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.

toknitup420 said:
Twrp is not decrypting you're data. Try rebooting twrp from fastboot a second time.
Click to expand...
Click to collapse
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??

smokeydriver said:
Son-of-a B#[email protected]#$. It asks me to 'decrypt data' by entering a password. I had hit cancel. What's the password??
Click to expand...
Click to collapse
Never mind...it's my 4 digit password that's used when my finger unlock doesn't work. Ugh- I knew it was something simple and dumb I was doing!

smokeydriver said:
Ok, so can someone tell me why I am getting stuck with 1 thing. I go to my stock recovery and into ADB sideload. When I tell it the file, it keeps failing to verify whole-file signature. What is wrong with this one step?
Or alternatively...when I'm in TWRP Alpha 2- why are all the files within the sdcard random letters and numbers?
Click to expand...
Click to collapse
Can I ask you how you fixed this? I'm having the same issue and this post popped up on Google.

trying to flash twrp; it just hangs!

Hi all,
*I've unlocked bootloader
* Have tried fastboot boot TWRP.img, as well as tried flashing TWRP RC1 via the Skipsoft toolkit.
Every way I've tried the phone just sits at the TWRP boot screen and doesn't allow me to go any further..
Any help here would be truly appreciated!
Cheers,

I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
You're braver than me. I haven't had my Pixel XL long but this is the first phone I've ever owned where I am afraid to try and install a custom recovery and ROM. With the dual partitions and what I hear about TWRP still being buggy it just seems like Google didn't want people to run anything but pure Android on the Pixels.

dutchy716 said:
I've been having the same issue tonight. Re-flash the stock image, go through the whole setup process and make sure you add a lockscreen pin, then flash TWRP. That is what worked for me. I still can't flash a Rom though for some reason. It's driving me insane.
Click to expand...
Click to collapse
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....

mikefnz said:
Same issue here, but no solution. Adding a lockscreen pin didn't change anything for me. I just get a teamwin image but it just sits there & doesn't actually open TWRP. My bootlocker is unlocked but thats as far as I can get 7.1.2 with May security. I have tried reloading everything and followed commonly recommended steps.
Any suggestions greatly appreciated. I would love to get this thing rooted and get some ROM flexibility - even to just get rid of the Nav Bar ....
Click to expand...
Click to collapse
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.

mac796 said:
I have never had a problem. Make sure your using the rc1 fast boot TWRP. Should be fastboot boot twrp.img. I change file name to this or copy and paste. Then you install rc1 or rc2 zip.
I know you will have problems if you try to install the wrong file.
Click to expand...
Click to collapse
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?

XtraArrow said:
Hmm are you on may bootloader because i think modifying the boot partition causes bootloop without the boot signature?
Click to expand...
Click to collapse
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!

mazubo said:
Yes I am.. should I downgrade to 7.1.1? Tjere was no mention of that issue in the skipsoft toolkit thread... Weird!
Click to expand...
Click to collapse
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.

XtraArrow said:
Sure, i guess.. or you could just manually flash the April bootloader. a lot easier.
Click to expand...
Click to collapse
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..

mazubo said:
I am doing exactly as you mentioned.. flash rc1.img, however the phone does not go beyond the boot screen, it just sits there.... Can I ask what steps you are taking prior to flashing twrp? Thanks!
Click to expand...
Click to collapse
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1 zip
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again

mazubo said:
Ok, would flashing just the bootloader wipe the phone? Also how would I find just the bootloader? Thanks for the suggestion, I haven't flashed just a bootloader before..
Click to expand...
Click to collapse
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??

mac796 said:
That strange. I just flash a factory image from Google
Set up a security pattern
Enable adb debugging
Fastboot boot twrp 3.0.2-0 rc1 IMG
Make sure it asks for your security pattern if it doesn't reboot to bootloader and fastboot twrp again, and keep repeating until it does
Install twrp 3.1.0.0 rc2 or rc1
If your using may bootloader's fish VBS 6 zip
And it should stick, if you flash. Anything else that messes with boot flash that VBS zip at the end again
Click to expand...
Click to collapse
Hmm, maybe this is where I've gone wrong.. I thought the need to create a security pin/pattern was only if coming from a previously rooted state, or from a custom ROM. I will try this as well and report back.. thanks!

XtraArrow said:
If you download the offiial april firmware, you can manually extract it from the .zip then you would do this command in fastboot :--------- fastboot flash bootloader PUTFILEHERE.img
EDIT: Are you able to get into TWRP by any chance??
Click to expand...
Click to collapse
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..

mazubo said:
Unable to get into twrp as previously mentioned. I flash the IMG file, then it just hangs on the TWRP boot screen..
Click to expand...
Click to collapse
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.

XtraArrow said:
Alright, try doing what I mentioned. Download April firmware, extract the bootloader.img from it and flash using command above.
Click to expand...
Click to collapse
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!

mazubo said:
This seems likely to work. Thanks for the suggestions, and I'll report back! Cheers!
Click to expand...
Click to collapse
I'm no expert but it's seems like a decent suggestion. Let us know how it goes.

@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!

Just wait. It will take little longer
Sent from my Pixel XL using Tapatalk

freddy0872 said:
@mazubo
You keep stating that you just flash the image. Are you flashing it from the bootloader then trying to boot to recovery?
You have to boot TWRP from your PC first. Then from TWRP you can then "flash" TWRP.
Just wanted to make sure that was a step you were taking!
Click to expand...
Click to collapse
Yes, I have tried fastboot to flash the TWRP img, as well as skipsofts toolkit. I guess I've been using the term "flash" for fastboot, as I haven't been able to use twrp yet.. I understand that you need to flash the TWRP img via pc and then flash the TWRP zip, then SuperSU or magisk, whatever your poison may be !

Issues on top of issues rooting Pixel 2 XL! Help? :(

First, I followed a tutorial precisely and ended up with a bootloop. It was just stuck at the white screen with a G. This was only after flashing the patched_boot.img file that Magisk gave me. I searched for hours online for an answer for that, and my device isn't listed when I type "adb devices." It's just blank. I uninstalled and reinstalled the drivers, I used different usb ports, different cables, I'm using the latest Google usb drivers, as well as the latest adb/fastboot files.
I wanted to push twrp to my phone via ADB, so I can flash magisk that way and fix this issue. I've read that it fixed my problem for other people, but sadly I'm unable to so far. When I try using the command "adb push twrp.zip /sdcard/" I get the following error:
"adb: error: failed to get feature set: no devices/emulators found"
In case anyone was wondering this is the tutorial I initially followed: https://youtu.be/M-0NIUUvYI4
I really don't know where to go from here. I've been looking around for 6 hours straight. All help is most appreciated.

Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.

rickysidhu_ said:
Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.
Click to expand...
Click to collapse
Thanks for the response, Ricky. I tried using the ADB sideload feature in TWRP but it just stuck at "Starting ADB sideload feature..." and eventually fails. Then I used a flash drive and connected it to the phone via the adapter, and that worked. Unfortunately, after flashing those files it was still stuck at the same bootloop screen. I went back to TWRP and now the usb flash drive isn't being recognized. What should I do?
Edit: I was able to FINALLY get it out of the bootloop! I tried this script earlier and it didn't work, but it was because I didn't have the critical partitions unlocked (https://forum.xda-developers.com/pixel-2/development/tool-deuces-bootloop-recovery-flashing-t3725778). Unlocked them, ran the script, works perfectly now. However, now I'm going to root it via TWRP and use the files you mentioned. Will do that tomorrow after sleep!

rickysidhu_ said:
Fastboot boot the twrp img file, then once you're in twrp, adb push the twrp zip file, and the stock boot image (extract it from whatever security update you're on). Then, adb push the magisk zip file (instead of a patched boot image) and download and adb push a custom kernel as well.
Flash the stock boot img, then twrp zip, then a custom kernel to retain touch functionality within twrp (I recommend flash kernel) and finally flash the magisk zip file and once you reboot, you should be good to go.
Click to expand...
Click to collapse
Hey I just wanted to inform you that I did get it working after continuing where I left off last. Thanks for your help, Ricky. It's much appreciated. Now I'm just gonna investigate on how to update OTA with magisk.

Mr December said:
Hey I just wanted to inform you that I did get it working after continuing where I left off last. Thanks for your help, Ricky. It's much appreciated. Now I'm just gonna investigate on how to update OTA with magisk.
Click to expand...
Click to collapse
If your going the OTA route, which, personally, I wouldn't if your bootloader is "fully" unlocked, you'll need to completely unroot, and return back to stock recovery. Not trying to deter you, I just think that fastbooting the monthly factory images is much easier, with fewer chances for errors. Not to mention, if you know the proper technique, you won't lose any data :good:

Badger50 said:
If your going the OTA route, which, personally, I wouldn't if your bootloader is "fully" unlocked, you'll need to completely unroot, and return back to stock recovery. Not trying to deter you, I just think that fastbooting the monthly factory images is much easier, with fewer chances for errors. Not to mention, if you know the proper technique, you won't lose any data :good:
Click to expand...
Click to collapse
That sounds sick to me. :laugh: Would you mind pointing me in the right direction to a tutorial that has the proper technique to get it done without losing any data?

Mr December said:
That sounds sick to me. :laugh: Would you mind pointing me in the right direction to a tutorial that has the proper technique to get it done without losing any data?
Click to expand...
Click to collapse
This is how I do my monthly updates

Badger50 said:
This is how I do my monthly updates
Click to expand...
Click to collapse
Thanks bro I'll give it a shot today :laugh:

Badger50 said:
This is how I do my monthly updates
Click to expand...
Click to collapse
Hey I'm not exactly sure which factory image I should choose. When I was rooting the phone the tutorial said to use the image with the same build number. My current build number is "OPM1.171019.018, Feb 2018", and I'm assuming what I should do is use this one "OPM2.171019.029, Apr 2018"?
https://developers.google.com/android/images#taimen

Mr December said:
Hey I'm not exactly sure which factory image I should choose. When I was rooting the phone the tutorial said to use the image with the same build number. My current build number is "OPM1.171019.018, Feb 2018", and I'm assuming what I should do is use this one "OPM2.171019.029, Apr 2018"?
https://developers.google.com/android/images#taimen
Click to expand...
Click to collapse
You are correct :good:

Unable to flash OTA update

Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?

I have not heard of anyone successfully loading an OTA through TWRP. Either restore stock recovery (install boot.img to both slots) and sideload with the Google instructions or run the flash-all (remove the -w) to use the factory image. Either way, you ere going to be reverting to stock recovery.
P.S. Your message doesn't make sense since you say you have TWRP on your device but then are showing that you used fastboot boot to run the TWRP .img file. If TWRP was on your device, you wouldn't have to use that command. You would just have entered TWRP with the adb reboot recovery command. I am guessing you are rebooting into the bootloader screen where either you run the TWRP .img or run the flash-all.

I also thought I saw a previous post somewhere that said you cannot skip an update, so going from December to February may not work.....not sure...
But definitely you need to load the OTA via regular Recovery using adb not TWRP....

Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.

parakleet said:
Can you install a OTA?
I thought you had to perform an ADB sideload of an OTA.
Even then I am not aware that ADB sideload works for Pixel 3xl yet.
I have been flashing the factory image with -w removed.
Click to expand...
Click to collapse
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.

spotmark said:
ADB sideload works fine for the OTAs in stock recovery. That's how I've been doing mine.
On a side note, the Essential phone is the only phone I've come across so far that TWRP will flash the factory OTAs.
Click to expand...
Click to collapse
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:

Badger50 said:
The P2XL and Nexis 6p can flash OTA's via twrp as well. Hopefully Team Win will get it sorted out for you guys as well :good:
Click to expand...
Click to collapse
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the factory zips. That doesn't mean my memory isn't shot either.

spotmark said:
Flash them or sideload them? I never had a P2XL, but I had a Nexus 6p and I don't remember being able to flash that with the Factory zips. That doesn't mean my memory isn't shot either.
Click to expand...
Click to collapse
Yeah, it was possible, just not many people knew about it, but it definitely works :good:
Flashing them that is.

I went from dec to feb update no problem

hilla_killa said:
I went from dec to feb update no problem
Click to expand...
Click to collapse
Sideloading or factory image method?

I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.

Badbrad17 said:
I am trying to do an OTA update on my Pixel 3xl. I have TWRP installed and need to get back to stock recovery. I have the stock boot.img file and have attempted to flash with adb fastboot but I keep getting this error
writing 'recovery'...
FAILED (remote: Not allowed to flash (recovery))
Bootloader is unlocked
USB debugging is on
Any help would be appreciated.
Click to expand...
Click to collapse
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??

Badger50 said:
Did you first extract the secondary zip file inside the factory image, and then placed the boot.img in your platform-tools folder, and the used the command..fastboot flash boot boot.img....??
Click to expand...
Click to collapse
Yes that is what I did.

Badbrad17 said:
Yes that is what I did.
Click to expand...
Click to collapse
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.

Badger50 said:
Okay, and you are in fastboot mode and not adb from the OS as well I take it? Have you tried a different USB cable and port? If all else fails, you can flash the boot.img in twrp as well.
Click to expand...
Click to collapse
OH I di not know I could do it in TWRP. Will try that first. thanks

Badbrad17 said:
OH I di not know I could do it in TWRP. Will try that first. thanks
Click to expand...
Click to collapse
Just make sure you flash it to the boot partition :good:

raphytaffy said:
Hi all, I have TWRP + Magisk on my device and I am attempting to update from PQ1A.181205.006 to PQ2A.190205.001.
Steps taken
1. Downloaded the OTA from here: https://developers.google.com/android/ota#crosshatch
2. Moved the OTA to phone storage.
3. Checked SHA256 checksum matches.
4.
Code:
adb reboot recovery
5.
Code:
fastboot boot twrp-3.2.3-3-crosshatch.img
6. From TWRP > Install > OTA zip file
Fails with the attached error. I have also tried sideloading through TWRP with the same result. Has anyone hit this error or successfully flashed the OTA update through TWRP?
Click to expand...
Click to collapse
I've installed 3 latest updates from twrp ...
Download the latest OTA, you have to be in stock Rom and Kernel stock ... and have last twrp on your phone... Flash OTA and twrp installer to keep twrp ... restart in twrp for magisk or restart system ... benefits
sorry for my bad english.

Badger50 said:
Just make sure you flash it to the boot partition :good:
Click to expand...
Click to collapse
How do I make sure of this? Sorry I'm a bit of a noob.

Badbrad17 said:
How do I make sure of this? Sorry I'm a bit of a noob.
Click to expand...
Click to collapse
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:

Badger50 said:
Tap install on the twrp home screen. Then go to where you have the boot.img on your internal storage and tap image on the bottom right. Then select the "boot" partition, and swipe to install. This will return you back to stock recovery and kernel :good:
Click to expand...
Click to collapse
Well I managed to do that, but now when my phone rebooted the touch screen no longer responds. Very strange. It all loads fine and I can see my screen but nothing works. I tried to go back into recovery and I get the little dead Android guy laying on his back with a red exclamation point and "No Command" below it.
Any ideas?

Question Rooting a T-Mobile 9 Pro on A12?

I recently got my hands on a T-Mobile 9 Pro. Fresh out of the box a couple weeks ago.
It updated to A12 a few days ago (Software Version says LE2127_11_C.16).
What are my options to root this thing? I'm relatively aware of the steps, but I don't see any temp boot images for the T-Mobile variant.
As I've seen other people mention, OEM unlocking is no longer grayed out, so that appears to be one hurdle out of the way. Right now, after reading about users having data connection issues, I'm not interested in flashing the global/EU images and I'm more than happy sticking with the T-Mobile image.

i have been trying this all day so far and all i get is either bootloop to fastboot or black screen of nothing...
i have also been trying to find the tmo a12 update on my phone where they place it before it installs. but can seem to find it even with a rooted 11.2.9.9. does ne1 know where this file is located. i want to pull it and try and get the boot.img out and try it that way..
ok we are making progress on this, i was apparently doing it the wrong way.

galaxyuser88 said:
i have been trying this all day so far and all i get is either bootloop to fastboot or black screen of nothing...
i have also been trying to find the tmo a12 update on my phone where they place it before it installs. but can seem to find it even with a rooted 11.2.9.9. does ne1 know where this file is located. i want to pull it and try and get the boot.img out and try it that way..
ok we are making progress on this, i was apparently doing it the wrong way.
Click to expand...
Click to collapse
How did you manage to get the root? I have been looking into it for a long time now and haven't been able to obtain it or should I say I'm more afraid to obtain the wrong method and ruin the phone.

NotSoSweet6626 said:
How did you manage to get the root? I have been looking into it for a long time now and haven't been able to obtain it or should I say I'm more afraid to obtain the wrong method and ruin the phone.
Click to expand...
Click to collapse
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy root.
Sorry I do not have the n10 so I can not help you there.

galaxyuser88 said:
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy roo
Click to expand...
Click to collapse

NishiMoon said:
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
Click to expand...
Click to collapse

galaxyuser88 said:
Well when I fastbooted I would flash boot instead of just boot boot.img.
Also make sure you use the correct boot.img with the same security patch version other wise you might or will have issues..
I am hoping that you have all the adb, fastboot, device drivers all set on your computer. If you do not you can search the internet to see how to setup your computer for this. You will need this to properly root your phone.
Make sure you download and have msm just in case you need it..
1. Download magisk and the magisk app to your phone and install it.
2. You have two choices here you can either pull your own stock boot.img and use magisk app on your phone to patch the img or download the correct version magisk patched boot.img from these forums.
3. Put your phone into fastboot mode
4. Open cmd prompt and Use fastboot " fastboot boot (magisk_patched_boot.img) < this is your patched boot.img".
5. Hit enter. Your computer should send the patched boot img to your phone and then your phone should reboot.
6. Once your phone boots ups, open the magisk app and then click on install. On this part you have to click direct install and then click let's go. Magisk will then root your stock boot img and will reboot.
7. After your phone reboots and you have done everything correctly you should have a rooted phone.
8. Enjoy root.
Sorry I do not have the n10 so I can not help you there.
Click to expand...
Click to collapse
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated

NishiMoon said:
Would you happen to have a copy of the Oneplus 9 (not pro) TMobile LE2117_11_C.18 Stock Boot.img?? It would be greatly and I mean greatly appreciated
Click to expand...
Click to collapse
I will check when I get home. If I do it will prolly be the 9pro 5g one I have..

I would imagine the boot.img would be the same if not very close. I can't seem to get oppo_decrypt to extract the firmware ops file for the boot.img. I just wanna root my phone already

Rooted Stock TMO LE2127_11_C.18
After the last update that screwed up my oneplus 9 pro, I decided it was time to look at unlocking the bootloader and rooting my phone so that I could get control over these damn updates. I just want to be able to root my stock OOS so that I can...
forum.xda-developers.com
Take a look here for the c18 boot img for tmo..

galaxyuser88 said:
Rooted Stock TMO LE2127_11_C.18
After the last update that screwed up my oneplus 9 pro, I decided it was time to look at unlocking the bootloader and rooting my phone so that I could get control over these damn updates. I just want to be able to root my stock OOS so that I can...
forum.xda-developers.com
Take a look here for the c18 boot img for tmo..
Click to expand...
Click to collapse
Thank you but I ended up pulling my own boot.img for the OnePlus 9 instead of trying the OP9 Pro. I was able to pull my own boot.img then patch it, boot it, flash it. Now I'm happily rooted

LE2117.11.c18