Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Hello Guys and Girls,
the title is obvious: Here is a twrp build for the HTC U12+. I spent quite a bit of time together with the dear @Captain_Throwback to get everything working.
At this place a huge thanks to @Captain_Throwback for helping me, even though not having the device at his hands!
Instructions:
With A/B devices the command
Code:
fastboot flash recovery recovery.img
is not possible, because these devices generally don´t have a recovery partition any longer. The recovery sits now in the ramdisk of the boot.img.
So how do we get TWRP on it?
The first option is to just boot TWRP temporarily with the command
Code:
fastboot boot twrp.img
. This will just boot up TWRP, not actually flash it onto your device. After rebooting the phone, TWRP will be gone. This is a great option for those, who just like to flash their phone one time, don´t want to modify the boot.img and don´t need a permanently installed TWRP.
The second option is to use the twrp flashable installer zip to install TWRP permanently to your ramdisk from the booted TWRP or magisk manager! Installing from Magisk Manager was made possible by @osm0sis!
So you see there are generally 2 steps needed on A/B devices now.
First booting TWRP. Second flashing the installer zip.
But and now comes HTC into play. When permanently flashing TWRP zip touchscreen gets disabled, because HTC added a nasty little check into the touchscreen driver. If it detects that the phone is in recovery mode it disables the touchscreen.
Luckily we found 2 ways around that!
First way is to have a custom kernel, that has this check patched out!
Second option is to use a zip we provide here, that also patches your kernel, to avoid tripping this check. The downside of flashing this zip is that all commands like
HTML:
adb reboot recovery
, hitting reboot to recovery in magisk manager and finally reboot to recovery in TWRP are not working and only boot to the OS!
How to temporary boot TWRP:
1. You need a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img provided in this thread and copy it to your fastboot folder (pay attention that firmware version matches)
3. Open a command prompt in your fastboot folder!
3.a While your phone is booted to the OS and USB debugging is enabled, type:
Code:
adb reboot bootloader
4. You need to fastboot boot twrp currently
Code:
fastboot boot <filename of the twrp.img>
example:
Code:
fastboot boot twrp-3.2.3-2-ime.img
5. Wait for twrp to be booted
6. You´re now in TWRP
7. Please note that you need to fastboot boot the TWRP every single time you need it. After a reboot it will be gone!
8. Important:
Please note that
Code:
fastboot boot twrp.img
(like done in step 4) will also break OTA functionality. More about this in the FAQ.
How to permanently flash TWRP via the .zip installer
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the flashable TWRP installer zip provided in this thread!
2a. If you´re on a stock kernel that has no touchscreen fix for recovery included please also download the touchscreen_hexpatcher.zip
3. Flash the TWRP-Installer.Zip from the booted TWRP or Magisk Manager on your phone (hit the + while in modules section)
3a. Important: Directly afterwards flash the magisk zip from TWRP or Magisk Manager
If you don´t flash it you will only be able to reboot to TWRP, regardless of the option you choose
4.Only needed when on stock kernel without touchscreen fix:
also flash the touchscreen_hexpatcher.zip from TWRP or Magisk Manager
Be aware that flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes
Code:
adb reboot recovery
, reboot to recovery from magisk manager and reboot to recovery from inside TWRP.
To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
5. Reboot
6. Congratulations: you can now reboot into your permanently flashed TWRP
How to permanently flash TWRP via the TWRP.img file inside TWRP
1. Make sure you have a working fastboot and adb environment! Your device´s bootloader must be unlocked!
2. Download the twrp.img file from the offical twrp site
2a. If you´re on a stock kernel that has no touchscreen fix for recovery included please also download the touchscreen_hexpatcher.zip
3. Boot to TWRP. Navigate to Advanced -> Install Recovery Ramdisk -> Choose the twrp.img downloaded earlier. Wait for the flash to be completed successfully and do either 3a or 3b.
3a. If you want to be rooted flash the magisk.zip
3b. If you don´t want to be rooted navigate to Advanced -> Fix Recovery Bootloop to be able to boot into system
4.Only needed when on stock kernel without touchscreen fix:
also flash the touchscreen_hexpatcher.zip from TWRP or Magisk Manager
Be aware that flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes
Code:
adb reboot recovery
, reboot to recovery from magisk manager and reboot to recovery from inside TWRP.
To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
5. Reboot
6. Congratulations: you can now reboot into your permanently flashed TWRP
Few tips and tricks:
1. You need to mount ext_sd card before you can access it in the file manager
2. Go to mount and click on mount usb storage to access the ext sdcard when connected via USB
3. Don´t forget you can connect an usb device via usb-otg to backup/flash stuff from/to an usb storage device
Official Changelog: twrp.me
22.06.2020 3.4.0-0
HTC Firmware on Android Pie can´t be decrypted.
Add support to be able to decrypt Viper GSI - Huge Thanks to @Captain_Throwback
20.05.2019 3.3.1-0
Decryption on devices running firmware 1.68.xxx.y with security patch state of 1st April 2019 when fastboot booting the twrp.img
NOTE: The official TWRP image 3.3.1-0 will only decrypt devices on the 1st April 2019 security patch state when fastboot booted. The official TWRP image 3.3.0-0 will only decrypt devices on the 1st February 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-5 will only decrypt devices on the 1st January 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
17.04.2019 3.3.0-0
Decryption on devices running firmware 1.62.xxx.y with security patch state of 1st February 2019 when fastboot booting the twrp.img
Future TWRP.img files can be flashed via the "Install Recovery Ramdisk" option inside TWRP´s advanced settings (for now the twrp.zip is also still available)
If you don´t flash magisk there is also option to "Fix Recovery Bootloop" inside TWRP´s advanced settings to be able to boot to system
you are able to take screenshots via power + home button
busybox is included instead of toybox
NOTE: The official TWRP image 3.3.0-0 will only decrypt devices on the 1st February 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-5 will only decrypt devices on the 1st January 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
01.01.2019 3.2.3-5
Add support for successfully decryption devices on firmware 1.57.xxx.y with security patch state of 1st December 2018
NOTE: The official TWRP image 3.2.3-5 will only decrypt devices on the 1st January 2019 security patch state when fastboot booted. The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
01.01.2019 3.2.3-4
System is no longer being mounted R/W when booting TWRP
NOTE: The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
01.01.2019 3.2.3-3
Add support for successfully decryption devices on firmware 1.53.xxx.y with security patch state of 1st December 2018
NOTE: The official TWRP image 3.2.3-3 will only decrypt devices on the 1st December 2018 security patch state when fastboot booted! The TWRP 3.2.3-2 image will only decrypt devices on the 1st Sepember 2018 security patch if fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-3 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Older versions:
05.10.2018 3.2.3-2
[Fix] TWRP Image 3.2.3-2 successfully decrypts devices on 1st September Security patch state! Also see the information below.
[Tweak] resetprop included statically, remove dependencies for it thanks @Captain_Throwback, @topjohnwu and @nkk71
NOTE: The official TWRP image 3.2.3-2 will only decrypt devices on the 1st Sepember 2018 security patch state when fastboot booted! The TWRP 3.2.3-1 image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer (also from the 3.2.3-2 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
07.09.2018 3.2.3-1
[Fix] MTP now enabled/working! (@Captain_Throwback)
[Fix] Vibration feedback now enabled/working (@notsyncing)
[Fix] Maximum brightness fixed - you need to manually adjust brightness in Settings using the slider to update (@Captain_Throwback)
[Tweak] Zip now automatically unroots the device when flashing to allow device to reboot to system normally if root isn't immediately flashed afterwards (@osm0sis)
[Tweak] /data/cache contents now mounted to /cache on flashed version (@Captain_Throwback)
NOTE: The official TWRP image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer, however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
07.08.2018 3.2.3-0
Official TWRP release
NOTE: The official TWRP image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer, however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Unofficial Changelog:
21.07.2018 3.2.2-0
Initial Release
28.07.2018 3.2.2-1
Decryption is now working
02.08.2018 3.2.3-0
fix system not getting mounted by magisk installer!
fix no OS message upon reboot
flashable installer for permanently installing TWRP!
05.08.2018 3.2.3-1
fix system not being mountable as R/W in twrp
display a message asking you to reflash magisk after flashing twrp installer zip
Download:
Official
twrp.me
NOTE: The official TWRP image will only decrypt devices on the 1 June 2018 security patch if fastboot booted. If you are on the 1 March 2018 security patch, you will need to fastboot boot one of the unofficial 1.15 TWRP images. The zip installer, however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Unofficial
XDA | AFH
Additional Downloads
Touchscreen hexpatcher | Mirror (AFH) - SEE IMPORTANT NOTES BELOW:
Only needed when on stock kernel without touchscreen fix
Flashing touchscreen_hexpatcher.zip will make touch work when using stock kernel but render all recovery related commands unusable.
This includes "adb reboot recovery", reboot to recovery from Magisk Manager and reboot to recovery from inside TWRP. To get into TWRP you first have to reboot to bootloader and from there on to TWRP/Recovery!
Known Issues:
MTP is disabled in official TWRP. This is currently an issue on several A/B devices. - Enabled since 3.2.3-1
Official TWRP can´t decrypt HTC Firmware on Android Pie!
NOTE: The unofficial TWRP image has MTP enabled for fastboot booting ONLY.
fastboot booting TWRP mounts the system RW and breaks ability to take an OTA.
Please take a look at FAQ, found in the 2nd post here. It contains more information
Bug Reporting:
If you have an issue, the first step is to post a recovery log so we can determine the cause of the issue. This is done in recovery using Advanced -> Copy Log, or adb pull /tmp/recovery.log. Once a log is uploaded we can determine how best to proceed. NOTE: Posts that are reporting bugs or issues without an accompanying recovery log will be ignored! Additionally, providing details about your device setup, including variant, firmware version, and exact steps to reproduce your issue will also be helpful in diagnosing the problem.
We need your help!
Join the TWRP Testing group on Slack to help us test TWRP prior to official releases!
Tips on how to build TWRP for the U12+ yourself:
To build TWRP you need to use this branch as your device tree:
https://github.com/freak07/android_device_htc_ime
Additionally you these commits from gerrit to your twrp tree!
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/31760/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/31207/
https://gerrit.omnirom.org/#/c/android_bootable_recovery/+/31021/
Depending on the base you're building for, you may need to comment/uncomment the PLATFORM_SECURITY_PATCH flag for your respective build if you want to fastboot boot the twrp.img. If the patch level of the image doesn't match the patch level of the current system, decryption will not function when fastboot booting the image. If installed via zip, the patch level doesn't matter, as it is automatically updated from system using @topjohnwu & @nkk71's resetprop.
XDA:DevDB Information
TWRP for HTC U12+ aka Imagine, Tool/Utility for the HTC U12+
Contributors
Freak07, Captain_Throwback, nkk71, topjohnwu, Dees_Troy, bigbiff, _that
Source Code: https://github.com/TeamWin/android_device_htc_ime
Version Information
Status: Stable
Current Stable Version: 3.4.0-0
Stable Release Date: 2020-06-22
Created 2018-07-21
Last Updated 2020-06-25
F.A.Q.:
Q: Which TWRP.img to choose for my current Security Patch State
A: For the old base 1.15 use on of the unoffical 1.15 release found in the OP.
TWRP Image 3.2.3-1.img decrypts devices, which run firmware on the 1st June Security patch State.
TWRP Image 3.2.3-2.img decrypts devices, which run firmware on the 1st September Security patch State.
The zip installer (also from the 3.2.3-2 release), however, will work on any patch level, but if you're on stock kernel, you will still need to flash the hex patcher or a custom kernel to have working touch when rebooting into recovery mode.
Q: I´m not able to fastboot boot the recovery, because the command won´t execute properly.
A: Update your adb and fastboot binaries to the latest one found here:
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Make sure you´re using the original cable.
Make sure you are in bootloader mode.
Try different USB ports on your machine.
On windows make sure you have the latest usb/mtp driver installed properly when the phone is connected in bootloader mode.
Q: I flashed the permanent twrp installer zip and now my touchscreen is not working.
A: This happens when you´re on stock kernel and did not flash the hexpatch-touchscreen zip found in the OP.
Q: I flashed the permanent twrp installer zip and the hexpatch-touchscreen zip found in the OP. Now commands/actions like
Code:
adb reboot recovery
reboot to recovery button in magisk manager
reboot to recovery button in TWRP
are only booting me straight to the OS.
A: As mentioned in the OP flashing the hexpatch-touchscreen zip will break the reboot to recovery command and associated actions.
To get to twrp reboot to bootloader and from there choose reboot to recovery with volume buttons and confirm with the power button.
Q: I flashed the permanent twrp installer zip, booted to the OS and lost root
A: Directly after flashing the twrp installer zip flash the magisk zip to keep root!
Q: I only fastboot booted TWRP but now my OTA functionality is broken.
A: Fastboot booting the twrp image trips a check, this check isn´t able to determine if system has been modified (because it receives no output) and subsequently assumes it has been modified.
this breaks verity on system and probably vendor. Resulting in non existing OTA functionality.
If you are interested in a more detailed explanation please follow this link:
https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1301
to check if system has been modified check the following path:
"/sys/fs/" + Current_File_System + "/" + block + "/lifetime_write_kbytes"
Current_File_System is ext4 on the U12+
block is related to your boot_slot. so check the partition table here:
https://forum.xda-developers.com/u12-plus/how-to/guide-how-to-root-u12-magisk-tips-tricks-t3802583
if you´re on slot A: system_a is sda18
if you´re on slot B: system_b is sda19
Example:
I was on slot B so the file I needed to check was: `/sys/fs/ext4/sda19/lifetime_write_kbytes`
if this file shows 0 system was not modified. Any other value means it was modified and you will not be able to take an OTA!
Same check applied for vendor! you just have to adjust the path.
Slot A vendor: sde19
Slot B vendor: sde40
Example to check if vendor_b has been modified: /sys/fs/ext4/sde40/lifetime_write_kbytes
To restore OTA functionality follow this post:
https://forum.xda-developers.com/showpost.php?p=76606113&postcount=3
or alternatively:
1. after updating your device via RUU or OTA, patch the boot.img with magisk (look at my guide thread)
2. run the following command on either a terminal shell on the phone or via adb shell on your pc(don´t forget to grant su permissions) to obtain an untouched system.img:
dd if=/dev/block/bootdevice/by-name/system$(getprop ro.boot.slot_suffix) of=/sdcard/system.img
3. store this system.img somewhere safe
Additional info:
you can also backup vendor this way!
dd if=/dev/block/bootdevice/by-name/vendor$(getprop ro.boot.slot_suffix) of=/sdcard/vendor.img
Information: Please note that only perm s-off devices are able to flash the vendor.img in fastboot!
Q: Is there a way to restore OTA functionality and keep using TWRP?
A: Yes there is. Please read below! thanks to @osm0sis who came up with the idea!
Temporary Workaround for TWRP mounting /system as RW
the issue linked here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/1301, which is causing TWRP not being able to mount system as read-only, results in a non pristine system partition after booting TWRP once.
The following file will allow TWRP to mount system as read-only (and therefore keeping OTA functionality)
That means after the following procedure, you can restore an untouched system.img, keep TWRP flashed on your device and simultaneously be able to take OTAs!
Instructions:
1. Download the following file https://www.androidfilehost.com/?fid=1322778262904004337 and extract it! (also as attachement to this post)
2. Copy/Replace the .twrps files to
/persist (make sure to grant the correct permissions afterwards! 0664 | rw-rw-r-- )
/storage/emulated/0/TWRP
with the one you just downloaded
3. When now booting/flashing TWRP system will get mounted as read only.
4. You can now restore a pristine system.img to your device! TWRP shouldn´t mount it as RW now!
5. Check if everything worked by following the guide above (check file lifetime_kbyte_writes for your active system partition)
A huge thanks to @MassStash for testing all this!
also mine
nice.:good:
noob question: can I format data partition and install magisk without force encryption flag like HTC 10? or is that impossible without decrypt the partition?
wiQbold said:
nice.:good:
noob question: can I format data partition and install magisk without force encryption flag like HTC 10?
Click to expand...
Click to collapse
I didn’t try it.
If you could try it and report back to confirm that would be great :highfive:
Nice work guys. Thanks @Freak07, @Captain_Throwback and all others who are still with as, as well as those who had to leave to soon - you'll be remembered.
Sent from my HTC U12+ using XDA Labs
@Freak07
Followed your instructions, but hangs at downloading 'boot.img' after second step: "fastboot boot TWRP_3.2.2.0_Imagine.img"
I'm Unlocked and Rooted with Magisk.
same here
fastboot boot TWRP.img
downloading...
FAILED: unknown command
schmeggy929 said:
same here
fastboot boot TWRP.img
downloading...
FAILED: unknown command
Click to expand...
Click to collapse
Might be a stupid question but did you try booting in fastboot? AFAIK it only works in fastboot
umaranjum said:
Might be a stupid question but did you try booting in fastboot? AFAIK it only works in fastboot
Click to expand...
Click to collapse
Yes that too, just hangs at booting... It is the same procedure at the U11. You boot TWRP in Bootloader and flash from Download Mode. Fastboot is the command for both.
umaranjum said:
Might be a stupid question but did you try booting in fastboot? AFAIK it only works in fastboot
Click to expand...
Click to collapse
Not the person you replied to, but since I have the same problem, I followed the steps in OP, and since it's only 2 steps, I'm sure the other person performed the "adb reboot bootloader" step.
Ah, Ok. Interesting, it worked the first time for me, have you tried redownloading the TWRP img and trying it again? If so, then it may be a problem specific to your device, in which case @Freak07 should be able to help you out better
---------- Post added at 02:27 AM ---------- Previous post was at 02:25 AM ----------
k_l_o said:
Not the person you replied to, but since I have the same problem, I followed the steps in OP, and since it's only 2 steps, I'm sure the other person performed the "adb reboot bootloader" step.
Click to expand...
Click to collapse
Ah, yes, I forgot about that lol. I do apologise, I'm quite tired. If it still doesn't work after redownloading then you'll need to wait for @Freak07 to help you out, as I mentioned above. Apologies that I couldn't be of more help and I hope you two manage to get it working
k_l_o said:
@Freak07
Followed your instructions, but hangs at downloading 'boot.img' after second step: "fastboot boot TWRP_3.2.2.0_Imagine.img"
I'm Unlocked and Rooted with Magisk.
Click to expand...
Click to collapse
Do you also get the same
FAILED: unknown command
as @schmeggy929?
schmeggy929 said:
same here
fastboot boot TWRP.img
downloading...
FAILED: unknown command
Click to expand...
Click to collapse
To both of you.
Try both bootloader and download mode for booting. Although only bootloader should work for booting.
Make sure you have the latest fastboot and adb drivers!
Try different usb ports.
What happens if you try to fastboot boot a stock boot.img?
Thanks @Freak07, @Captain_Throwback. TWRP_3.2.2.0_Imagine.img is worked.
product: htc_imedugl
current-slot: a
version-main: 1.15.709.6
Great news! Thanks everyone for your hard efforts! Get my U12 at the end of the month so looking forward to flashing. Hopefully Lee will have a nice ROM for us by then too
Freak07 said:
Do you also get the same
FAILED: unknown command
as @schmeggy929?
To both of you.
Try both bootloader and download mode for booting. Although only bootloader should work for booting.
Make sure you have the latest fastboot and adb drivers!
Try different usb ports.
What happens if you try to fastboot boot a stock boot.img?
Click to expand...
Click to collapse
I get a "FAILED (status read failed (Too many links))
Does it matter that I've Magisk already installed which required a patched_boot.img?
Freak07 said:
Do you also get the same
FAILED: unknown command
as @schmeggy929?
To both of you.
Try both bootloader and download mode for booting. Although only bootloader should work for booting.
Make sure you have the latest fastboot and adb drivers!
Try different usb ports.
What happens if you try to fastboot boot a stock boot.img?
Click to expand...
Click to collapse
Tried all available USB ports, two different cables. Where do I get a stock boot img for US Unlocked? Also while in bootloader, the only command that works is "fastboot reboot bootloader". "Fastboot reboot" and "fastboot reboot download" does nothing.
k_l_o said:
I get a "FAILED (status read failed (Too many links))
Does it matter that I've Magisk already installed which required a patched_boot.img?
Click to expand...
Click to collapse
Could you please post everything from your terminal?
And update the fastboot and adb binaries with the one from the following link for your current OS beforehand
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
No it doesn’t matter I did the same.
schmeggy929 said:
Tried all available USB ports, two different cables. Where do I get a stock boot img for US Unlocked? Also while in bootloader, the only command that works is "fastboot reboot bootloader". "Fastboot reboot" and "fastboot reboot download" does nothing.
Click to expand...
Click to collapse
You can extract it from the US firmware zip linked in the firmware thread.
Is fastboot devices showing your device?
Did you update your fastboot and adb binaries to the ones found here for your OS?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Freak07 said:
You can extract it from the US firmware zip linked in the firmware thread.
Is fastboot devices showing your device?
Did you update your fastboot and adb binaries to the ones found here for your OS?
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
Click to expand...
Click to collapse
Low and behold after updating the binaries twice and redownloading TWRP.img for the third time, it finally booted to TWRP. Cancelled decrypt and kept "Read Only". Flashed your Kernel successfully except for preload error due to not mounted. Rebooted and everything seems good, shows Kirisakura_1.0.
Thanks for the help!
Related
This is my version of TWRP built for the 2017 Moto G5S. It should work fine, but using it is a try at your own risk procedure. Your bootloader must be unlocked to use this recovery. Fastboot mode is used to flash or boot this recovery. To enter fastboot mode, turn off your device, hold PWR and VolDn for 3 seconds, then let go.
Differences between upstream TWRP and my fork:
My original green theme
No SuperSU
No TWRP app
No HTC Dumlock cruft
Updated pigz compressor (slightly faster and more tolerant of corruption)
To temporarily boot this recovery:
Code:
fastboot boot twrp.img
To permanently flash it:
Code:
fastboot flash recovery twrp.img
The download is available on the downloads tab.
XDA:DevDB Information
TWRP for Moto G5S, Tool/Utility for the Moto G5S
Contributors
squid2
Source Code: https://github.com/moto8937-twrp
Version Information
Status: Stable
Current Stable Version: 3.2.3-r1
Stable Release Date: 2018-08-17
Created 2017-11-05
Last Updated 2018-08-17
Squid TWRP 3.1.1-r3
Initial build for montana is up. I expect it to be fully functional, including encryption support. Special thanks to @lohanbarth for testing.
thank you for your work :good:
Hi,
i just flashed your TWRP. The flash was successful, after booting to recovery twrp came up just fine. I wiped /data to decrypt, then rebooted the phone... Now it seems either bootlooping or bricked.
(Of course i unlocked the bootloader before flashing)
The phone just shows the bootloader-screen (blue background, red M-Logo, white letters "powered by android") with a small text in the middle "bad key).
Nothing happens. I cant even shut it down. Holding the power button for 10 seconds seems to start a reboot (screen goes black) but the bootloader-screen immediately shows back up and stays. Theres nothing i can do, no adb/fastboot access either...
Any suggestions?
Edit1:
AH! Pressing VolDown + Power gets me to fastboot/recovery... Phew. Guess i flash the stock rom first before proceeding any further.
Edit2:
Succeeded, nice!
Hi,
I flashed this TWRP. After flashing I went to recovery mode. Format Data failed as /data unknown. Flashed stock ROM. Again flashed TWRP. This time it just bootloops into TWRP recovery. When I power off and ON again, it bootloops and goes into TWRP recovery again and again. Any idea what could be wrong? My guess is I screwed up partition table. But not sure.
Thanks
KS
I went through flashing stock ROM, TWRP once again. After flashing TWRP, I went to recovery repeatedly and did 'Format Data' every time. I flashed Magisk. System booted fine. I verified by power off/on several times. Seems to be working fine.
Thanks
KS
Thanks for your hard work at bringing TWRP to the MOTO G5s.
It took me a while to install it on my XT1797, as there was some strange message during boot which said
ID: Bad key
But after many many times bricking and unbricking, I am now finally rooted using Magisk.
Hope that we can see some custom Roms for this great device soon.
I tried it with XT1797, but I can not boot and flash twrp.
Is this twrp compatible with XT1797?
hello, your bootloader and unlock it?
did you enable USB debugging?
that you put the fastboot cmd?
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
FAFAŁ said:
Hi . Thx for You job . My phone stil a live But I have a question .
how about this one ? At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda
Click to expand...
Click to collapse
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Root and TWRP. And a great phone.
Just need some Roms, pray that they will come!
Thank you!
janhieber said:
What is the question? For me it worked without such vertiy disable stuff. Simply unlock the bootloader, boot and/or flash TWRP, root your phone or do anything else. When TWRP asks to change /system, answer yes.
Click to expand...
Click to collapse
Ok .that's all super go to recovery end fire .Thanks
Hello, I compiled the twrp3.2 with the sources of squid2.
thank @squid2 for sources
twrp-montana-3.2.0-r1 > http://www.mediafire.com/file/4443oy6kwiyvm5g/twrp-montana-3.2.0-r1.img
Squid TWRP 3.2.0-r1
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
squid2 said:
I've posted a new build of my TWRP with the latest changes from upstream. It brings better support for Oreo zips while still supporting older ones. It also has improvements to the reliability of backups.
Click to expand...
Click to collapse
Dear @squid2 please give some ROMs also
... please i know you are busy with work but it is just a request
Unable to Flash twrp recovery
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
dau999 said:
After flashing oficial firmware, i am no longer able to flash twrp recovery, after each system reboot, i am back on stock recovery.
Does anyone know how to fix?
Flashed using: fastboot flash recovery twrp.img
Get a notification: bootloader file not signed or corrupt
Click to expand...
Click to collapse
after the flash of the twrp you select good recovery in the bootloader?
lohanbarth said:
after the flash of the twrp you select good recovery in the bootloader?
Click to expand...
Click to collapse
Select good recovery in the bootloader??!!
Bootloader gives me a notification that the img is not signed or corrupt (squids one)
you tried to download it again and then try again
lohanbarth said:
you tried to download it again and then try again
Click to expand...
Click to collapse
I did, same error.
I want to root my poco f1 ....
But i have some questions regarding it
1. Will my data be format while rooting and installing twrp
2. How i will get ota update
3. Will installing ota update also format my data?
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
roxor101 said:
1. Your whole internal data needs to be wiped... To flash the force decryption enabler at first...
Even while installing twrp via fastboot.. Your data will be formated
2. You will get updates... But not via ota.... Yes you will get to download the updateds in some roms... But you need to dirty flash them.
3. While dirty flashing.... Formatting data is not required.
Click to expand...
Click to collapse
Does the twrp with working decryption also need to format my data?
You can root your device in two ways.
First, with twrp (OTA won't work afterwards)
Second, without twrp (OTA will work)
First method, unlock the bootloader (device will be wiped)>Grab the twrp with working decryption>Boot your device into fastboot and type fastboot flash recovery twrp.img (or whatever the recovery image name is)>Now type fastboot boot twrp.img (or whatever the recovery image name is)>Once booted into twrp, swipe to allow modification>Now download Magisk installer and copy into the device>Flash it?Reboot to system>Profit.
N.B. After flashing twrp, make sure to first boot into twrp before booting into system or else device will restore stock recovery. If you need to update in future, just grab the twrp flashable update package and flash it. That's it. No need for OTA.
Second method, this will also require an unlocked bootloader. Once the bootloader is unlocked, get the stock boot image of your current software (e.g. if you are on miui 10 with October security patch, make sure to grab the stock boot image for miui 10 october). Now install Magisk manager apk in your device. Now open magisk manager and go to install. You will find an option for patching stock boot image. Click on it and select the stock boot image. Magisk will patch the boot image and will place it in your internal memory. Now boot into fastboot mode and type fastboot boot patched_boot.img (or whatever the name is). Once device is booted into system, go to Magisk and click on Install>Direct install (recommended).Magisk will get flashed by itself and reboot. Once rebooted, go to Magisk manager and check. If you do everything correctly, you are rooted.
N.B. When you get an OTA update, open Magisk and go to Unsinatll and click on "Complete uninstall". It will uninstall magisk and revert your stock boot image back. Note that, if you play witgh system partition like modifying build.prop or change host file or bootanimantion or any such thing, you won't be able to get any further OTA update. In that case, you need to flash the complete fastboot rom through MiFlash tool.
For more information, please go to Magisk thread or search online.
I have flashed latest android 10 to my A3 and mistakenly uninstalled TWRP. Now i want to install twrp recovery. But everytime I flash it in partition b, it get stuck on fastboot screen.
If twrp doesn't support Android 10 then how come it supports other Android 10 based custom rom like Pixel Experience?
Because those custom ROMs use android 9 vendor, boot etc
Thanks for your helpful response
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Thank you for your helpful response. If i want to flash twrp permanently, which zip file i need to flash after booting it temporarily with your attached twrp.img?
Sapper Morton said:
You must always use TWRP Installer (there's no need in specific custom ROMs, since they provide built-in custom recovery), the image I attached can only be used to install temporarily in Android 10 firmware (other than 11.0.8.0 QFQMIXM). And remember, all of this could be avoided if Xiaomi had implemented the boot command into Mi A3 bootloader:
Code:
fastboot boot image_example.img
Click to expand...
Click to collapse
so i am guessing there is no way to add the boot command to fastboot
build v11.0.11.0
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Hi!
Thanks a lot, where I can find the file for the v11.0.11.0, or at least can you specify how I do this using stock boot?
Thanks! Hope to hear you back.
I booted with patched boot and finally was able to enter into TWRP recovery, but then I erased system/data/dalvik and tried to flash Pixel Experience but I am always getting error 1 when doing it. What can I do? It is something about the Android Q base? I'm now on build 11.0.11
Sapper Morton said:
You must always use TWRP Installer (there's no need in specific custom ROMs, since they provide built-in custom recovery), the image I attached can only be used to install temporarily in Android 10 firmware (other than 11.0.8.0 QFQMIXM). And remember, all of this could be avoided if Xiaomi had implemented the boot command into Mi A3 bootloader:
Code:
fastboot boot image_example.img
Click to expand...
Click to collapse
means that with this twrp it is used only to open the twrp periodically, once the custom rom is installed I install the twrp normally
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
What do you mean "patch the q boot image". What is that?
Sapper Morton said:
TWRP itself is compatible with Android 10, but not the pre-built image; the non-bootable state could be explained by the Pie Kernel inside twrp.img from official TeamWin website. Nonetheless, you can use Magisk to patch the Q boot image, or just download and flash the attached file, it's a v11.0.8.0 QFQMIXM boot image patched with the latest TWRP:
•https://app.blackhole.run/#5ae9e6c2301FpEtcnUSvhBisE7AD1JV98DHmKGDtK3WP
Click to expand...
Click to collapse
Thanks you saved me. I could boot into recovery with your boot.img but the encryption failed. Nevertheless I could sideload the recovery.zip to the device and install on both slots.
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?
Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE
All,
I'm looking for suggestions on how to restore root to my Huawei MediaPad M5. I recently updated Magisk to stable Manager 8.0.7 and Magisk build 21.4. However this caused me to lose root on the tablet. The tablet is on Android 8.0.
To restore root, I tried the following steps:
1) Downloaded Huawei tablet image 8.0.0, build 200, for the SHT-W09 (C567) USA model
2) Extracted Ramdisk image and copied over to the tablet
3) Opened Magisk and selected Download and Patch File
4) Magisk patched the file and saved it in my downloads folder
5) I then transferred the patch file back to my pc
6) Opened my Fastboot folder that had the patched image
7) Booted the tablet into fastboot mode and tested with command "fastboot devices"
8) After verifying I had a connection, I typed "Fastboot flash ramdisk patched_boot.img"
9) The file was flashed to the tablet
10) I rebooted the tablet, but I still don't have root
Any ideas, do I need to use the command "fastboot flash boot magisk_patched.img"?
Thanks,
Rick
Rick,
I managed to root my CMR W09 C567 EMUI 8.0.0.200 by flashing this older version of Magisk directly within TWRP:
Release Magisk v20.4 · topjohnwu/Magisk
Miscellaneous This release is mainly focused on stability and bug squashing. Please be aware that MagiskHide is no longer enabled by default. Since Google has enabled hardware-based key attestation...
github.com
It does all the work of patching the boot file withing TWRP, and when you reboot into system, there will even be a Magisk apk already installed. Do not upgrade afterwards.
The TWRP that works for me is:
[RECOVERY][UNOFFICIAL] TWRP 3.2.2-1
This is for the Mediapad M5. NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files. Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use...
forum.xda-developers.com
The command to flash:
./fastboot.exe flash recovery_ramdisk TWRP-3.2.2-1-MediapadM5.img
PS. You evidently need to have an unlocked bootloader. Mine was locked, but I managed to use the test point method and PotatoNV program. This requires removing the screen (I busted mine--had to replace from AlixExpress).
zentico said:
Rick,
I managed to root my CMR W09 C567 EMUI 8.0.0.200 by flashing this older version of Magisk directly within TWRP:
Release Magisk v20.4 · topjohnwu/Magisk
Miscellaneous This release is mainly focused on stability and bug squashing. Please be aware that MagiskHide is no longer enabled by default. Since Google has enabled hardware-based key attestation...
github.com
It does all the work of patching the boot file withing TWRP, and when you reboot into system, there will even be a Magisk apk already installed. Do not upgrade afterwards.
The TWRP that works for me is:
[RECOVERY][UNOFFICIAL] TWRP 3.2.2-1
This is for the Mediapad M5. NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files. Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use...
forum.xda-developers.com
The command to flash:
./fastboot.exe flash recovery_ramdisk TWRP-3.2.2-1-MediapadM5.img
PS. You evidently need to have an unlocked bootloader. Mine was locked, but I managed to use the test point method and PotatoNV program. This requires removing the screen (I busted mine--had to replace from AlixExpress).
Click to expand...
Click to collapse
Hello zentico, is your M5 model SHT-W09?
I have a similar issue: after upgrading my SHT-W09 to latest 9.1.0.360 firmware I patched the recovery_ramdisk-image with Magisk v23.0 and it didn't boot :-(
I was able to pach the same image for recovery mode but in that case I had only limited root access. The only solution I found up to now: using the "old" patched recovery_ramdisk.image which was patched with Magisk v20.4
Edit: looks as if there are existing several C432-360 images. I got the LGRP4-OVS as this was the only version available on firmwarefinder but my device identifies as "P2" most likely that's the reason why it's not booting.
Gamblor2 said:
Hello zentico, is your M5 model SHT-W09
Click to expand...
Click to collapse
Mine is a CMR-W09.
C5Longhorn said:
All,
I'm looking for suggestions on how to restore root to my Huawei MediaPad M5. I recently updated Magisk to stable Manager 8.0.7 and Magisk build 21.4. However this caused me to lose root on the tablet. The tablet is on Android 8.0.
To restore root, I tried the following steps:
1) Downloaded Huawei tablet image 8.0.0, build 200, for the SHT-W09 (C567) USA model
2) Extracted Ramdisk image and copied over to the tablet
3) Opened Magisk and selected Download and Patch File
4) Magisk patched the file and saved it in my downloads folder
5) I then transferred the patch file back to my pc
6) Opened my Fastboot folder that had the patched image
7) Booted the tablet into fastboot mode and tested with command "fastboot devices"
8) After verifying I had a connection, I typed "Fastboot flash ramdisk patched_boot.img"
9) The file was flashed to the tablet
10) I rebooted the tablet, but I still don't have root
Any ideas, do I need to use the command "fastboot flash boot magisk_patched.img"?
Thanks,
Rick
Click to expand...
Click to collapse
Hi!
I have the exact same tablet, but I'm unable to find the full update to patch magisk and root it fully, where/how were you able to obtain the full ota and extract the image?
Mine is SHT-W09 8.0.0.200(C567)
Thanks!