Help rooting Huawei Watch - 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!!!!!

Related

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.

Rooted and TWRP Recovery, how do I update OTA? Please help! Google Pixel XL

I've searched the forums but nobody has answered the questions yet, I'm not familiar with entering the commands, please tell me what I'm suppose to do step by step. I know ADB but when people say flash the firmware, I'm not quite sure what I type or mean.
I was able to sideload the OTA with TWRP RC1. My understanding is this doesn't work on the alpha versions.
1. go here and download the OTA (the file ending in 26O is the Verizon version)
2. Boot into TWRP
3. Select "Advanced" then "ADB Sideload"
4. Run the command adb sideload <file you downloaded>
5. If you have a custom kernel, you will need to re-flash it
6 Reboot your device(first boot will take a while)
7. ???????
8. PROFIT
brewcrewwheels said:
I was able to sideload the OTA with TWRP RC1. My understanding is this doesn't work on the alpha versions.
1. go here and download the OTA (the file ending in 26O is the Verizon version)
2. Boot into TWRP
3. Select "Advanced" then "ADB Sideload"
4. Run the command adb sideload <file you downloaded>
5. If you have a custom kernel, you will need to re-flash it
6 Reboot your device(first boot will take a while)
7. ???????
8. PROFIT
Click to expand...
Click to collapse
when i click advanced and adbsideload it gives me two options one is to wipe dalvik the other is to wipe cache then at the bottom it says swipe to start sideload ( i havent selected any files or ran a command for it to sideload anything)
those steps are optional, just swipe to start then you can run the adb side load command.
an important thing I forgot to add is that in addition to having to re-flash a custom kernel is you'll also need to re-flash TWRP and likely re-root (I am not rooted so I can't be sure). I'd recommend waiting until after the first boot to do that just to make sure everything comes up OK.
Not sure this saves as much time as it could. I had not updated from the x build yet, so after installing RC1 and SU 2.79 I figured why not try the TWRP sideload. It worked (though I originally tried the Q build which showed a file validation failure I used O), but sideload changes your slot. In my case, it cleared the slot of the recovery and got rid of root access. I had to temp fastboot the TWRP .img and then install the TWRP zip. I then reinstalled SuperSU as well. All's back to normal now.

Applying OTA while running Magisk and a custom kernel

Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
ilatimer1 said:
Hello everyone,
So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)?
If someone has an idea on the process to do this please let me know.
Thanks!
Click to expand...
Click to collapse
Kernel, TWRP and Magisk get overwritten by the OTA. You need to reinstall.
Also I'd recommend to disable all Substratum themes before flashing - for me this led to a Bootpool...
ilatimer1 said:
Hello everyone, So today is the day (at least for me) that I want to try applying the Jan OTA to my Pixel 2 XL. I am currently using Magisk and ElementalX kernel and was wondering if anyone has tried this yet (I know, the OTA just came out)? If someone has an idea on the process to do this please let me know. Thanks!
Click to expand...
Click to collapse
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
peoplesindian said:
What's the difference between this step and sideloading the OTA?
Edit: nevermind. Realized you'd flash-all without the -w if you have TWRP.
Click to expand...
Click to collapse
Yes, OTA's fail to execute if you have modified the boot or system partition. An OTA is an incremental only update that selectively writes certain files and is (usually) much, much smaller. This is appropriate for a stock, unmodified device. Lots of people get tired of waiting for the OTA to come, and so they just update manually by sideloading the OTA through the stock recovery (over adb). Nothing wrong with that, and it this will sometimes bring a phone back from bootlooping or other serious problems like FC's and crashing.
A full image contains the full partition images and they are written to the device fully and unconditionally via fastboot. You can only flash a full image if your bootloader is unlocked. It essentially erases the partitions by overwriting the entire contents from beginning to end. Some would argue this more "complete" method is less likely to result in errors, or corrupt files. Removing the -w switch from the batch file script prevents the script from overwriting the userdata partition where all your media, user apps and settings are. Some call this "dirty" flashing.
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
did exactly this, and all is fine.
otonieru said:
did exactly this, and all is fine.
Click to expand...
Click to collapse
Same
trim81 said:
Same
Click to expand...
Click to collapse
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
xclub_101 said:
Interesting that Google seems to claim that updating with the OTA should create less problems with this January update:
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
Click to expand...
Click to collapse
That article is quite dubious with no source about google confirming the issue :silly:
v12xke said:
Then just execute that file from a fastboot prompt.
Click to expand...
Click to collapse
REALLY dumb question, but how do you execute a .bat from fastboot? Or do you mean with the phone in bootloader/fastboot mode, run the modified .bat?
EDIT: Never mind... put the phone in Bootloader/fastboot mode. Ran the modified .BAT from command prompt within the Platform-tools folder.
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
v12xke said:
I recommend using the full image (not OTA) downloaded from Google. Extract the files from the zip into your ADB folder, open up flash-all.bat with a text editor and remove the -w (wipe) switch from the script. Save. Then just execute that file from a fastboot prompt. You will not lose data or settings, but you will lose TWRP, kernel & Magisk. When the script finishes running, boot back into fastboot mode (bootloader) and from your PC, fastboot boot twrp. When it loads queue up (add zips) TWRP.zip, Kernel.zip, Magisk.zip and let her rip. Reboot to system and everything will be normal. Just make sure you have those three files (latest versions) on your phone AND the twrp.img on your PC so you can boot to it. Takes about 3 minutes if you have all the files in place before starting.
Click to expand...
Click to collapse
I followed this and everything is installed perfectly with root.
Thank you ??
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
Slow internet here, you mind uploading the boot and dtbo.img?
sn0warmy said:
I did it last night with no issues. The process is pretty simple.
1) adb reboot bootloader
2) fastboot flash boot /location/of/december/boot.img
3) fastboot flash dtbo /location/of/december/dtbo.img
4) reboot
5) allow the OTA to install
6) adb reboot bootloader
7) fastboot boot twrp
8) install TWRP then custom kernel then Magisk
7) reboot
Click to expand...
Click to collapse
I like this idea better than the flash all, but forgive me as I haven't flashed any Android 8.1 devices yet.
Is dtbo the new name for what used to be called system?

Want to use Sultan kernel, having flashing issues

Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Bverns88 said:
Hey guys. Just upgraded to the android 10 October image via the adb flash-all command. Magisk rooted via adb and everything is going great. Want to install Sultan's ported kernel for Android 10. Used adb to flash twrp image and flashed the kernel zip via twrp but it keeps saying it can't mount /system and /vendor upon finishing. Upon rebooting I get stuck at the google G load screen. Have to redo flash-all and instal magisk via adb all over to get back to normal. Anyone have this problem or could offer some help? Would be great.
Click to expand...
Click to collapse
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Ericarthurc said:
As long as the kernel finishes the install it's fine. The mounting errors don't matter if it finishes. The mounting errors are just a bug with Android 10. Everything I flash has those errors after it, but I am good. I am on Oct. with Magisk 20 and Sultan kernel.
Click to expand...
Click to collapse
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Bverns88 said:
So the way I'm seeing it is flash the twrp image file, flash the kernel, reboot. Then adb fastboot to bootloader and reflash patched magisk boot.img?
Click to expand...
Click to collapse
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Ericarthurc said:
Do this:
Setup:
1. Download latest platform tools for your OS
2. Download latest factory image for Pixel 2 XL
3. Download twrp.img and twrp.zip
4. Download the kernel.zip you want
5. Download magisk.zip version 20
(Keep in mind those aren't the actual filenames, I am just shortening them; plus you will want to rename them for easier flashing)
Install:
1. Boot phone to bootloader.
2. Extract factory image into the platform tools folder
3. Run flash-all script
4. After done reboot back to bootloader (dont do the phone setup)
5. Now remove the factory image from platform tools (or just extract a clean platform tools folder)
6. Place twrp.img, twrp.zip, kernel.zip and magisk.zip into the platform tools folder (rename the files to make it easier to type them out when flashing with computer adb)
7. Run: fastboot boot twrp.img (or whatever you named it)
8. When in twrp, go to settings and turn off "screen timeout" there is a bug
9. Go to advanced then "adb sideload"
10. In your computer terminal type: adb sideload twrp.zip
11. Then run: adb sideload kernel.zip
12. Then run: adb sideload magisk.zip
13. Reboot to system
Should be good! Using sideload allows you to pass files from your computer to your phone, it makes it easy. If adb sideload is "hanging" or "freezing" (you should see a kinda progress bar with it's working) then reboot twrp.img and try a different USB port. There is a glitch when it hangs, where when you remove the USB cable the phone goes black; just hold power + volume down for about 10 seconds and it will boot back to bootloader.
Click to expand...
Click to collapse
Thanks so much. I went and used AZ bikers method and it worked fine. Easy and hassle free. https://forum.xda-developers.com/pixel-2-xl/how-to/quick-2xl-upgrade-reference-8x-oreo-to-t3826330

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.

Categories

Resources