Develop Bugs

January security update?

I received the download on my 5x that's rooted. Will this break root for me?

Yes but you can easily re-root after re-installing TWRP

bg1906 said:
Yes but you can easily re-root after re-installing TWRP
Click to expand...
Click to collapse
I don't get this answer. I'm not able to install the security update on my rooted 5X, it reboots into TWRP and after I manually boot to system nothing happened. Tried it 3 times and still have root access.
Is the only way to get the security update by flashing an entire Android image? Or more specifically, can I update without wiping the phone?

Yeah OTA isn't going to work. You need to manually do it. You will need USB Drivers and ADB/Fastboot files. Create a folder on your desktop called Android and put the ADB files there. Now download the image. The image is an archive file. Extract the contents of archive files (there is one archive inside the original archive file you download), and after you have all the files extracted, modify the flash-all file (.bat if you are on Windows) with a text editor (Notepad) to remove the -w and save. This will prevent a wipe of your device. Connect your phone via USB and reboot to the bootloader. Open the folder you are in and if on Windows hold shift and right click and select Open Command Prompt. This will open a Command Prompt Window at the folder's location. Next type the command fastboot devices and press Enter. If everything is right, a device id will be returned. If that works, then go back to the folder and double click the flash-all.bat (Windows) and this will install the update. Root will be lost as will TWRP recovery. After the install, the phone will attempt to reboot. I always stop the reboot and go back to bootloader. Choose Recovery and go to the default recovery. You will see an Android figure with a red X. Simultaneously press the power and volume up & down buttons together repeatedly until you get the recovery menu (this may take a few times). Wipe Cache. Then reboot and you will have the update. You can then reinstall the latest version of TWRP by going to the TWRP website and downloading the latest version of TWRP. I usually put it in the same folder as the Android files and when it downloads rename it to twrp.img. Make sure you are in the bootloader and then at the command prompt all you need type is fastboot flash recovery twrp.img and this will install TWRP. You can then go to TWRP and flash SuperSU. I use the latest beta 2.66. But read here (http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3) for the details on the various versions of SuperSU Beta. *I take no responsibility for what may/may not happen to your phone as that depends on your level of comfort flashing/rooting etc*
Hope this helps. IF the flash-all gives you an error, you will need to flash the various parts of the update individually. If that happens, follow the instructions here for the update: https://www.androidpit.com/how-to-get-android-m-preview

This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
Yes please let me know how this goes

Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd

bosbeest said:
This is exactly what I was looking for, thanks! Couldn't find it anywhere with Google which btw somehow returns mostly Nexus 5 results even when using "nexus 5x"...
I'll try this later on and reply with the results.
Click to expand...
Click to collapse
It's the same process with both phones.

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Tried it, worked. Thanks a bunch!
Yaz75 said:
It's the same process with both phones.
Click to expand...
Click to collapse
Still doesn't make sense that you can't search for "5X"

Tomyk89 said:
Download the factory image and extract boot.img, system.img, and vendor.img. Nothing changed in the bootloader or radio with this update, so you do not need those.
Then, run the following:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot into TWRP and flash SuperSu again.
Then wipe cache/dalvik and reboot into system.
Info taken from This thread with the help of dmudd
Click to expand...
Click to collapse
Does this wipe data?

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
No
Sent from my Nexus 5X using Tapatalk

ch.ch1 said:
Does this wipe data?
Click to expand...
Click to collapse
Nope!

SlimSnoopOS said:
Nope. The fastboot command has to have "userdata" included to do that.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.

gee one said:
Not true- the -w flag will wipe userdata when flashing other partitions.
fastboot -w flash system system.img will wipe data
fastboot flash system system.img will not wipe data.
Click to expand...
Click to collapse
Oh, I learned something new
Sent from my Nexus 5X using Tapatalk

jhester1967 said:
I received the download on my 5x that's rooted. Will this break root for me?
Click to expand...
Click to collapse
I doubt it will install. The install will simply fail.

Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"

ch.ch1 said:
Im not so good at this...
So I just copy the 3 img files to the same folder adb is installed and I run the 4 commands? Do I have to install TWRP again? Do I have to root again?
I did the command "adb reboot bootloader" which rebooted my phone in the bootloader home page, but when I did the next command "fastboot flash boot boot.img" I got the msg "<waiting for any devices>"
Click to expand...
Click to collapse
Keep this guide by Heisenberg for reference, it is very helpful when updating firmware or returning to stock. You want to refer to section 10 to update via fastboot.
If going from MMB29P to MMB29Q OTA, flash in fastboot: boot, system, and vendor. Radio and bootloader are unchanged if you are using MMB29P. Recovery does not need to be flashed since you want to keep TWRP.
Yes, you will need to root again in TWRP.

Pixel xl in twrp with no OS installed?

Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..

Which guide did you use to do all of this? I will help us understand where you started

Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery

There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!

I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device

Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?

mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot

Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root

Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...

I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.

Help rooting Huawei Watch

Hi,
I'm a noob trying to root my Huawei Watch (to be able to read BTLE messages). I used egalite_kernel_HW_dffc4c0-2.0 which should be rooted (and indeed I see su.sh and busybox.sh script in the /setup folder)
I did the following:
sudo adb reboot bootloader
sudo fastboot reboot-bootloader
# Unzip TWRP_3.1.1.-0_Unofficial-Sturgeon.zip => recovery.img
sudo fastboot boot recovery.img
#In the phone, using TWRP, set to ADB sidleoad (wipe data and wipe cache)
sudo adb sideload negalite_kernel_HW_dffc4c0-2.0.zip
TWRP loaded fine and the rom installed fine to, but when opening the "Advanced Settings" it says that the phone is not rooted.
Any hint of what I did wrong?
Thanks

ruscull said:
Hi,
I'm a noob trying to root my Huawei Watch (to be able to read BTLE messages). I used egalite_kernel_HW_dffc4c0-2.0 which should be rooted (and indeed I see su.sh and busybox.sh script in the /setup folder)
I did the following:
sudo adb reboot bootloader
sudo fastboot reboot-bootloader
# Unzip TWRP_3.1.1.-0_Unofficial-Sturgeon.zip => recovery.img
sudo fastboot boot recovery.img
#In the phone, using TWRP, set to ADB sidleoad (wipe data and wipe cache)
sudo adb sideload negalite_kernel_HW_dffc4c0-2.0.zip
TWRP loaded fine and the rom installed fine to, but when opening the "Advanced Settings" it says that the phone is not rooted.
Any hint of what I did wrong?
Thanks
Click to expand...
Click to collapse
You keep saying your phone. Are you trying to root a phone or a watch? I'll assume you're talking about your watch.
adb sideload is for applying OTA updates. What you want to do is flash that zip.
While in TWRP, do the following:
sudo adb push [path to kernel zip] /sdcard
In the TWRP menu, select install. Navigate to /sdcard and select the zip. Install it.
If you can't get that working, just flash the supersuwear.zip I've attached to this post using TWRP: https://forum.xda-developers.com/hu...aw-1-5-build-m9e42c-to-downgrade-2-0-t3607859
Also, use the advanced wear settings from the play store. I've had issues with the one that negaman includes in his thread.

TheSt33v said:
You keep saying your phone. Are you trying to root a phone or a watch? I'll assume you're talking about your watch.
Click to expand...
Click to collapse
Yes! I just want to root the watch.
Thanks, for the reply. I'll try it and report back

I installed TWRP_3.1.1.-0_Unofficial-Sturgeon and then I tried to install negalite_kernel_HW_dffc4c0-2.0.zip
sudo adb push negalite_kernel_HW_dffc4c0-2.0.zip /sdcard
and Installed using TWRP.
Unfortunately I got the error below:
--
set_perm: some changes failed
Updaterrocess ended with ERROR:
Error installing zip failed
--
Trying to fix the problem I started wiping parts and I screw-up and delete the system. Wonderful.
I then tried to find ROMs and finally I found Huawei-Rom-NX-v2.7.zip and successfully installed (with Root)
https://forum.xda-developers.com/hu...-negalite-huawei-rom-nx-root-bb-v1-6-t3406813
Unfortunately I find out I need a specific build NWD1.171016.002 (Stock ROM from December 2017).
Any idea were to find it?
Or shall I open a new thread?

ruscull said:
I installed TWRP_3.1.1.-0_Unofficial-Sturgeon and then I tried to install negalite_kernel_HW_dffc4c0-2.0.zip...
Click to expand...
Click to collapse
Why do you need that? You're running a rooted rom, right? Wasn't that the goal?
If your goal is actually to be on a rooted rom AND be on the latest system software, I think it would probably be best to start from scratch since you've done so much flashing and I'm really not sure what state your watch is in at this point. This is how you do that:
1. Download this factory image: https://www.androidfilehost.com/?fid=745425885120748838
2. Extract output.tar from that package. If you need software to do this, I recommend 7zip.
3. Extract the contents of output.tar.
4. Copy flash-all.sh, image-sturgeon-m6e69f.zip, flash-all.bat and bootloader-sturgeon-m6e69f.img to the same folder where you have installed fastboot.exe.
5. Boot your watch in bootloader mode (aka fastboot mode), connect it to the computer and double click on flash-all.bat. This will bring your watch to a 100% stock state.
6. Setup the watch and keep taking OTAs until you are on NWD1.171016.002 (there should only be 1 or 2 that you have to take).
7. Boot into bootloader mode and do one of the following steps:
If you want to keep the stock recovery menu and only use TWRP temporarily, perform the command fastboot boot [path to TWRP image].
If you want to have TWRP permanently installed on your watch, replacing the stock recovery menu, perform the command fastboot flash recovery [path to TWRP image]. Then select reboot to recovery in the bootloader menu.
8. Download the supersuwear.zip package that I linked to in my previous post.
9. While in TWRP, adb push [path to supersuwear.zip] /sdcard
10. Install supersuwear.zip using TWRP menu.
And there you go. Latest firmware version, rooted. Download advanced wear settings from the play store if you want it.

Youre the man.
TheSt33v said:
Why do you need that? You're running a rooted rom, right? Wasn't that the goal?
If your goal is actually to be on a rooted rom AND be on the latest system software, I think it would probably be best to start from scratch since you've done so much flashing and I'm really not sure what state your watch is in at this point. This is how you do that:
1. Download this factory image: https://www.androidfilehost.com/?fid=745425885120748838
2. Extract output.tar from that package. If you need software to do this, I recommend 7zip.
3. Extract the contents of output.tar.
4. Copy flash-all.sh, image-sturgeon-m6e69f.zip, flash-all.bat and bootloader-sturgeon-m6e69f.img to the same folder where you have installed fastboot.exe.
5. Boot your watch in bootloader mode (aka fastboot mode), connect it to the computer and double click on flash-all.bat. This will bring your watch to a 100% stock state.
6. Setup the watch and keep taking OTAs until you are on NWD1.171016.002 (there should only be 1 or 2 that you have to take).
7. Boot into bootloader mode and do one of the following steps:
If you want to keep the stock recovery menu and only use TWRP temporarily, perform the command fastboot boot [path to TWRP image].
If you want to have TWRP permanently installed on your watch, replacing the stock recovery menu, perform the command fastboot flash recovery [path to TWRP image]. Then select reboot to recovery in the bootloader menu.
8. Download the supersuwear.zip package that I linked to in my previous post.
9. While in TWRP, adb push [path to supersuwear.zip] /sdcard
10. Install supersuwear.zip using TWRP menu.
And there you go. Latest firmware version, rooted. Download advanced wear settings from the play store if you want it.
Click to expand...
Click to collapse
Bro Thanks!!!!!

Unlocked, stuck boot, where is Download folder?

Followed the instructions here for Rooting and fastbooting to TWRP. Could not locate the Download folder where I put Magisk, so rebooted and put it in a few other folders. Rebooted back to TWRP image and still cannot the Magisk zip or extracted files anywhere. Switched to the B partition and looked around there with no luck. Then went to reboot in TWRP. Now I have a spinning white screen with the "scrolling G" ...15 minutes and counting.
How do I get it out of this stuck boot.
Why can I not find the Download or Android folders in TWRP File Manager where I put Magisk?
Thanks

Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.

boostedduece said:
Downloads from your phone should be in /sdcard/downloads.
If you are stuck with a non-booting system, you need to flash the factory image, you can try to flash it and remove the '-w' from flash-all.bat to keep your data.
Edit: btw to root stock, simply boot twrp image and flash magisk.zip, then reboot system. You can then boot twrp and flash twrp.zip if desired.
Click to expand...
Click to collapse
From what I recall, in the /sdcard/ I had 2 folders /0/ and /00b/? Both had "scrambled" folder names within, nothing that was Download or the like.
So, it's been at least an hour and I still have the scrolling boot screen. In hindsight I recall I went to B before restarting. Can't see device from ADB. Tried the previous Nexus methods of holding power and up/down keys...still white screen G with scroll. Edit: I tried again holding Power and it will now shut off. Holding volume down and power I can get to the boot menu and see Fast Mode. It won't boot on it's own, but I can get to the boot menu. So I'll try connecting again in the morning. Edit #2: after trying recovery and power button a few times the phone booted.
So it looks like I am back to finding Magisk in the Download folder-which I copied from my computer to the Download folder on the 3xl. I installed ES File Explorer and see the zips are in storage/emulated/0/Download but I do not see Download after I reboot with the TWRP image.

There is one /sdcard folder, the other 2 in /storage/emulated/.. have different attributes, but I recommend dealing with /sdcard.
Sounds like it did not decrypt the partition in twrp, that's why the names were garbled.
Holding both volume buttons and power for a while should hard shutdown the device.
You should be able to get to bootloader from power + volume down, flash-all.bat should work from here, you are definitely not bricked though.

Still unable to locate Download Folder
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?

vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel

vette8t7 said:
So, I can get the phone to boot and reboot.
From a command prompt:
adb devices (device is available)
adb reboot bootloader
fastboot boot twrp-3.2.2-3-crosshatch.img
Boots to TWRP asking for password, I hit cancel.
It then asks if I want write protection. Initially, I went this route, but tried again allowing full access.
I can see /sdcard/ and 2 folders /0/ and /0bb/, /0bb/ is empty.
when I go into /0/ the folder names are scrambled. Some have sub-folders that are also scrambled.
Why are the names scrambled? Where is my Download folder with my .zip and unzip files?
Click to expand...
Click to collapse
TWRP is failing to decrypt your phone. This used to be a big issue, but has been solved for some time. What version of TWRP are you using?

@vette8t7 if you haven't figured this out yet, as others have said, twrp is not decrypting your device. If you haven't you'll need to boot into your system and enable a pin security. Without that twrp doesn't have any info to decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app

hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:

hatdrc said:
You have to enter your password that unlocks your phone when you first boot into TWRP so that it can decrypt your phone. Don't hit cancel
Click to expand...
Click to collapse
vette8t7 said:
Oh man, THAT makes sense. I thought it was wanting me to create one and I didn't want to have to track ANOTHER password.
Okay, I'm in, see Downloads and .zip files!!:good:
Click to expand...
Click to collapse
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.​
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
I was able to run fastboot from the cmd and run twrp-3.2.3-3-crosshatch.img again.
In /sdcard/ I have an empty /obb/ and an empty /TWRP/ folder.
Performed an adb push of magisk.zip and twrp.zip to /0bb/directory and this time performed magisk followed by twrp install and now I get the Google setup window..I don't see Magisk installed.

vette8t7 said:
Geez, back in the day I unlocked and rooted my Galaxy Nexus without issue and did most of the same on a Note 4. Didn't really have a need to do either on my Nexus 6p-which I have gone back to using while I straighten out the 3XL. I'd leave the 3XL alone except I need to unlock and root to run the commands to prevent the service check for hotspot on my Verizon GUDP. The 6p has gotten sluggish as of late, thus the 3XL upgrade.
So...I found my Magisk-v18.0.zip (the non-beta) in TWRP after entering the passcode. Hit install. It went through to restart adn white screen scrolling G and now I keep landing on an Android Recovery page:
google/crosshatch/crosshatch
9/PQ1A.181205.006/5108886
user/release-keys
Use volume up/down and power.
Can't load Android System. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device.
Try again
Factory data reset.​
So after trying the "Try again" and it try to load and then reboots and tries to load and I come to the same screen above.
I finally tried selecting "Factory data reset" only to come to the same menu.
Any ideas what I did now and how I get out of it?
Click to expand...
Click to collapse
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I'd start fresh by flashing the factory image by running the flash-all batch file. BUT, edit it first to remove the -w you'll see a number of times down. If you don't your device will be wiped. Then boot twrp with fastboot boot, don't flash it. Then install magisk within twrp. If you want to keep twrp permanently then install the twrp zip file. I generally install twrp, then boot back into recovery and then install magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
so I'll try what you suggest.

vette8t7 said:
I've gotten to the point where TWRP is installed. If I install TWRP.zip I can get the phone to boot to an image that doesn't appear to have Magisk installed. So I installed the Magisk Manager. It indicates Magisk isn't installed. So I reboot into TWRP select Magisk v18 and install, then reboot system. The phone will go to the Google white screen spin for a bit and then reboot to TWRP. If I install the twrp.zip I can get back into the phone and see Magisk still isn't installed. Ihave tried combinations of installing TWRP.zip then Magisk.zip and vice versa, but I never seem to get Magisk installed.
I've seen mention of the flash-all batch, but I don't seem to have it in anything I have downloaded from these two guides:
https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I see it in #4 here, so I'll try what you suggest.
Click to expand...
Click to collapse
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
I assume you've found the factory image and extracted the zip file. In there is the flash-all.bat. Edit that, notepad++ is a good editor. Save the file after you've edit it and run that. Make sure you save it or you'll run the unedited version. Then start the process of booting twrp and installing magisk.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).

vette8t7 said:
Yes, found the factory image and extracted the zip. Is started to take the -w out and yes, Notepad++), but decided to leave it in to start fresh. I put the phone in Fastboot. Ran the flash-all, it worked for a while and then indicated there waasn't a recovery.img and a few other things and then "ended" with any key to exit. So I restarted to find everything was still there. So I rebooted to TWRP and installed the Magisk.zip, only to result in the same boot and restart into TWRP. So, convinced the factory image didn't wipe I performed that step again. Boot phone to Fastboot. Opened a command prompt in the image directory. flash-all. It ran for a while complained about the few .img files, but seemed to do more than it did the first time. This time I reloaded the boot loader and fastboot boot twrp.img only to go in and find I still had file in the Download folder (I was expecting to push them from a wipe). So of course when I install magisk.zip and restart it goes to the white google spinning rescreen and eventually restarts back into TWRP.
Your instructions lineup with #4 and 7 or 8 here: https://forum.xda-developers.com/pixel-3-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3857195
For some reason I can't seem to wipe for 1 and ever get Magisk to install 2. Of course my phone has the December OTA update if that has added any new variables here?
I reran this flash-all again to a log file (attached).
Click to expand...
Click to collapse
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.

Homeboy76 said:
- first, make sure you have the latest SDK Platform-tools r28.0.1 (see guide 'Prerequisites c.' for link).
- extract the December factory image in the Platform-tools folder.
- Open a command prompt in the Platform-tools folder.
- type flash-all at the prompt.
- when it finishes, do #8 for root.
Click to expand...
Click to collapse
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.

vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Click to expand...
Click to collapse
If you have r28.0.1 where is the Platform-tools folder?
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
vette8t7 said:
I have the r28.0.1
I was researching the Image and I had downloaded and used the A1.docomo, which, as jd1639 pointed out in another thread is for japanese phones. I've just finished downloading the non-docomo for December and see where I get.
Oh, now I see what I am doing wrong. The image .zip needs to be extracted into the platform folder. I noticed you said run the command from "platform-tools" folder.
Click to expand...
Click to collapse
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.

Homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
C:\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
---------- Post added at 05:54 AM ---------- Previous post was at 05:50 AM ----------
Yes, the Factory image zip needs to be extracted to the Platform-tools folder.
Click to expand...
Click to collapse
So once the factory image is done, I go through setup (skipping through most for later) to get the usb debugging enabled and copy Magisk.zip and twrp.zip.
adb reboot bootloader
fastboot boot twrp.img
put in passcode
Swiped to allow for modifications
First time I just installed the magisk.zip only to have it reboot twice into the loop of my #10 post again.
The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!
Holy Moly what a PITA!! On a positive note, I kind of refreshed some of this stuff I hadn't done in years :good:
I got stuck a couple of months back when my wife's nexus 6p died (not battery-which I later swapped into mine), something with the processor board. I got a Verizon 3XL with the locked bootloaderL...so if anything ever develops there, I can root that phone for the GUDP hotspot as well.

I followed the steps here: https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
So far, so good. Great Success! Thanks for your help!

homeboy76 said:
If you have r28.0.1 where is the Platform-tools folder?
Click to expand...
Click to collapse
vette8t7 said:
C\adb\platform-tools_r28.0.1-windows\platform-tools
Within that is adb, fastboot, twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img), december factory image (extracted) as well as the Magisk-v18.0.zip and twrp.zip (for copying or pushing)
Click to expand...
Click to collapse
"twrp-pixel-installer-crosshatch-3.2.3-3.img (renamed twrp.img)"
I think you mean 'twrp-3.2.3-3-crosshatch.img (renamed twrp.img)
vette8t7 said:
...The second time I repeated the whole factory image process up to fastbooting twrp.img and this time installed twrp.zip, reboot recovery, install Magisk-v18.0.zip. Reboot system. It boots and No Magisk in the app tray! Err...well now it is there and it shows Magisk installed!...
Click to expand...
Click to collapse
@vette8t7
Yes

Rooting 7T without TWRP / Pre-patched Magisk boot.img for 10.0.13.HD65AA (Global)

For those who can't root via TWRP or somehow lost root while updating (like I did), I have a patched boot image to aid others in this endeavor. This is a boot.img from a T-Mobile 7T which I had converted to the Global ROM, extracted and patched by Magisk after applying the latest update (10.0.13.HD65AA). Fully tested and working!
Instructions:
Unzip and place it in a convenient folder (ie, C:/adb/ or whatever's easy to remember.
Open a cmd prompt and navigate to your fastboot/adb folder.
Then run the command
Code:
fastboot boot boot.img
Your phone will be "temp-rooted" once it boots. If you haven't already, install Magisk Manager, then flash Magisk itself (ALWAYS do direct install!).
Don't install any modules yet. Just reboot when prompted after the Magisk flashing process is done.
Profit!
Download from Google Drive
[I dunno where else to upload this that XDA would consider "safe," so GDrive it is, I suppose.]
Spoiler: Process for manually patching the boot.img without TWRP:
Requirements: Stock device with unlocked bootloader only (no other mods), most recent OTA update applied and system rebooted. Fastboot and ADB Windows executables.
1) Enable advanced reboot and usb debugging in developer options.
2) Reboot to bootloader.
Code:
adb reboot bootloader
3) Boot to twrp
Code:
fastboot boot twrp.img
(or whatever you named it).
4) Once booted, enter:
Code:
adb shell
dd if=/dev/block/bootdevice/by-name/boot of=/tmp/boot.img
exit
5.5) Copy file to the PC:
Code:
adb pull /tmp/boot.img stock_boot.img
6) Reboot phone back to Android.
6.5) Copy boot.img back to phone:
Code:
adb push stock_boot.img /sdcard/boot.img
7) Make sure you have a data connection.
8) Install Magisk Manager.
9) Select option to install Magisk (not the Magisk App). Choose "Select and Patch a File."
10) Point to the boot.img.
11) It will do its thing then come back with a done message. File /sdcard/download/magisk_patched.img will be created.
12) Copy this file to your PC, either using MTP or ADB.
Code:
adb pull /sdcard/download/magisk_patched.img
13) Reboot the phone into bootloader mode again.
Code:
adb reboot bootloader
14) Boot the patched boot from step 12:
Code:
fastboot boot magisk_patched.img
15) Launch Magisk Manager again. You should see the current version available and the installed version below that now. If all is good, choose to install/update Magisk, then "Direct install" and reboot when finished.

I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?

>Akshay< said:
I guess you posted it in wrong section as mentioned the file is for Oneplus 7t ?
Click to expand...
Click to collapse
OH! You're right. I goofed. I'll ask a mod to move it.

This will delete all the data from the phone + bootloader needs to be unlocked?

Brontok said:
This will delete all the data from the phone + bootloader needs to be unlocked?
Click to expand...
Click to collapse
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).

GuyInDogSuit said:
Flashing this doesn't erase your data, unlocking the bootloader does, though (and is necessary to flash this).
Click to expand...
Click to collapse
never mind!
someone already did!
https://forum.xda-developers.com/showpost.php?p=83780229&postcount=12
thanks anyway!

Will this work for 10.0.13 tmobile ? Thanks

gershee said:
Will this work for 10.0.13 tmobile ? Thanks
Click to expand...
Click to collapse
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.

GuyInDogSuit said:
You might be better off pulling the boot.img yourself and patching it. I can't guarantee that this will even work on the T-Mobile version. But if you want to test it, just boot the img and root from Magisk once it loads. If it bootloops, well, then we know.
EDIT: Updated OP with instructions on how to patch the boot.img.
Click to expand...
Click to collapse
Thanks!
Worked like a charm.