Database Info

[ROOT] Moto X Style - XT1572 BR - Marshmallow

Hello guys!
I make my own ROOT (systemless, thanks for Chainfire) images for Moto X Style with Marshmallow (build MPH24.49-18). Its use "experimental" systemless SuperSU version 2.56 - more info on http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2. No need replace bootloader or recovery. Still need unlocked booloader.
Because TWRP didn't work in this version of bootloader (0xA048), I cooked "su.img" in a Linux box and used "/data/local/tmp" as bridge (accessible by ADB).
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it!
For use, you need
1) unlocked bootloader.
2) if your bootloader not unlocked, make sure you have copy of your data, because this process will erase your device.
3) install ADB and FASTBOOT on your pc using minimal ADB or Android SDK.
4) install ADB drivers from Motorola or Universal ADB.
5) download provided files.
6) download SuperSU ver. 2.56 from http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344.
Steps:
1) extract files in a folder of your choice (su.img, boot.img).
2) extract Superuser.apk from SuperSU-v2.56-20151030013730.zip from common folder.
3) enable USB debugging on Android.
4) connect your device on pc.
5) open a command prompt in a new folder.
6) type "adb push su.img /data/local/tmp" without quotes.
7) type "adb install Superuser.apk" without quotes.
8) now reboot your device into fastboot mode by typing "adb reboot bootloader".
9) type "fastboot flash boot boot.img" without quotes.
10) type "fastboot reboot" without quotes.
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
Ivan

Do I still need to unlock the bootloader in order to root this device

ivcarlos said:
2) write "boot.img" with fastboot.
Click to expand...
Click to collapse
What do you mean? Como assim?

Oh I see thanx partner

How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.

Marccelllorzn said:
How can I copy "su.img"?
If no Root I can not copy into data/local/tmp.
Click to expand...
Click to collapse
Restart in bootloader
1) adb push su.img /data/local/tmp
2) fastboot flash boot boot.img
3) Install SuperSu ver 2.56 apk

would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?

zittorb said:
would this work on xt1575 us? if not why?..... i mean .. why the indian MM would work 4 any variation and this one would not?
Click to expand...
Click to collapse
Yes, work with XT1575.

I dont test on another device, only on XT1572.
After 24h, no errors, work like a charm.
With this approuch you dont need to downgrade bootloader.

assuming that we need a "CLEAN", unrooted system for this as advised by @Chainfire in his instructional post regarding this experimental root method!
Instructions
You must absolutely re-flash your stock /system partition, or the separate root instances will interfere with each other. The installer for this experiment will not clean up old root files.
- Flash stock /system
- Flash the attached boot image
- Flash the attached SuperSU ZIP in TWRP
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
Also you should probably make a point of mentioning that this method is an experiment.
Aside from this, let me take my "high-visibility" jacket off, along with my "safety helmet" and say thank you very much for taking the time to do this for us all @ivcarlos! You are a gentleman!

Is Android pay confirmed working with this root method?
Sent from my XT1575 using Tapatalk

@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.

ivcarlos said:
@bb12489
I dnt know because I dnt use this feature.
@Doktaphex
I dnt mentioned this - clean and unrooted system - because after apply OTA on XT1572, custom recovery (TWRP) didn't work anymore. By the way, I assume no root and clean system.
I know this method is "experimental", but it's best at this time, without downgrade bootloader (not safe).
Thanks for comments! I make this work because I need root and I dnt like to make heavy changes on smart...
In this way, I share for everyone.
Click to expand...
Click to collapse
Could you please give me the link that how you created modified boot.img ? I want to make it work on Indian XT1572

@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.

ivcarlos said:
@gulshanstrider
I make boot image based on post of Chainfire (http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344), with applying steps:
1) unpack stock "boot.img";
2) patch sepolicy;
3) edit "init.rc" and "init.environ.rc";
4) edit "file_contexts";
5) repack "boot.img".
Use Chainfire generated images with model.
Without TWRP, I cooked "su.img" in a Linux box, and use "/data/local/tmp" with bridge.
Click to expand...
Click to collapse
wifi not working now please tell me how to revert everything back pleaseeee help !!!!

Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
Your model is XT1575 or XT1572?

Shishir Singhal said:
wifi not working now please tell me how to revert everything back pleaseeee help !!!!
Click to expand...
Click to collapse
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.

Not working on my XT1572
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.

ivcarlos said:
@Shishir Singhal
Whats your model and version?
I make this image for my XT1572 (BR, dual) and wifi working.
To revert back you must write back stock boot.img version. On first post I provided stock of XT1572 RETLA 6.0 (my base).
On my device no issues at all.
Click to expand...
Click to collapse
Thank u for quick reply got it working by flashing NON-HLOS.bin now everything is working fine thank u soo much

roberto.marcal said:
Didn't work on my XT1572 with Android 6.0.
Enable root option is disabled in SuperSU with a message saying that system-less root is currently not supported.
Click to expand...
Click to collapse
What version of SuperSU you was installed?
You put "su.img" into "/data/local/tmp"?
If you enter in shell with ADB, ls command show "su" directory in root? Image was monted successfully?

[ROOT] and TWRP with squashfs 3.1.1 for Lg urbane 2nd

Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]

zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele

mminfor said:
Hi, Congratulations for the help and thanks
After doing all the procedure I did the verification of the root and
Tells me it's not root.
It's possible?
Michele
Click to expand...
Click to collapse
you can check root trough adb
connect the watch and type this:
"adb shell"
"su"
you must have installed busybox on rails on the watch, you can try only booting the recovery with this command "fastboot boot twrp-3.1.1.0.img"

zbask said:
Steps
Unlock bootloader
Enable adb debugging via developer settings
Push the SuperSU zip onto your watch:
"adb push SuperSU.zip /sdcard/"
"adb reboot bootloader"
Flash or just boot custom recovery:
fastboot boot twrp-3.1.1.0.img
fastboot flash recovery twrp-3.1.1.0.img
Install SuperSU:
In the bootloader menu, select "RECOVERY MODE"
Press "Install", "Install Zip", SuperSU.zip, next, "Reboot after installation is complete", start.
Now you should have root in android wear 2.0 final build number NXH20E
All the files are not mine, i have just build the TWRP for our Smartwatch.
here is the link for download:
https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k?usp=sharing
If you would like to buy me a bear this is my paypal account [email protected]
Click to expand...
Click to collapse
I can confirm that you are correct that the TWRP does flash correctly and that the normal reboot to recovery works properly and I thank you for that, but the SU does not flash properly I get error 2 which indicates it does not work for the device (through searching) google, I forgot what that error was, I tested through the only app I see on wear that allows root and works, Advanced Settings and anytime I change the processor settings and exit the app, the same standard non-root settings appear again. Indicating that root was un-successful. I will see what I can do for the SU zip, becuase it appears to be related to the updater binary, the updater scirpt is usually more straigt forward, but sometimes harder to figure out. I will try to do what I can in this regard, but power might go out (Harvey) and circumstances might becom unfavorable throught this weekend.

try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M

zbask said:
try this supersu
https://drive.google.com/open?id=0Bzk4DPXefDhrUjRLTXpPSkxVT2M
Click to expand...
Click to collapse
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor

Working.
mminfor said:
I also tried this but nothing to do still gives me "no root"
I will wait for better times.
thank you
MMinfor
Click to expand...
Click to collapse
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.

physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
This solution seems to work.
Here's the check
thanks

zbask said:
Steps
Unlock bootloader
...
Click to expand...
Click to collapse
How exactly do you unlock the bootloader?

madsc13n41s4 said:
How exactly do you unlock the bootloader?
Click to expand...
Click to collapse
1.Unlock the bootloader if not already unlocked
(Make sure to set up device with phone after unlocking bootloader otherwise no boot!)
Code:
- adb reboot bootloader
- fastboot oem unlock
enjoy!

Is there any way we can pass SafetyNet for Android Pay using SuperSU?

???
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?

Grumps said:
Will this work with watch sport as well?
Can we then maybe fix APN settings after its rooted?
Click to expand...
Click to collapse
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.

Drakosha said:
APN settings cannot be changed on AW2.0 because SquashFS is read-only. Howerver, if you edit APN settings manually in AW1.5 (using xml file edit from adb root shell, see this forum for tutorial), they remain & work after OTA update to AW2.0. They will be lost, however, if you disconnect your watch from the phone "the official way" (with hard reset). In order to always use APN settings, use this tutorial on how to pair AW watch to new phone without factory reset.
Click to expand...
Click to collapse
Isnt APN settings configured after you install a sim card from the provider? Surely it must then be stored somewhere else?

Did anyone succeed ?

what is about squashfs? is there anyway, to make /system/ writeable?

sebj84 said:
what is about squashfs? is there anyway, to make /system/ writeable?
Click to expand...
Click to collapse
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later

SQUASHFS is read only by default.
sebj84 said:
Ok,
sorry wasn't on aw before. so sorry for my last question.
Anyhow. Did somebody managed to get XPosed running?
I've tried, but got an error of not enough place on /system. When i try to delete system apps, i get the same error.
Now using supersu.
before with magisk, got xposed and a few other packsages installed, but they never show up in magisk later
Click to expand...
Click to collapse
You won't be able to do anything within the /system/ partition while it is mounted. I can't answer the question as to why specifically, because I am not as knowledgeable of it, but here is the wiki SQUASHFS info. and another one that gives more information as to the uses SQUASHFS HOWTO.. If I am correct in order to make any changes to the system one would have to have a backup or original system image unsquash the image make any changes from that then re-squash the image and flash it in custom recovery. I have already unsquashed the image of the original image from the newest update myself and have it on my laptop, but I have not been able to go much further (busy). There are workarounds to the system not being able to write, but those are mostly for other versions of the filesystem and on different devices along with it not being totally writable.

Ok. I see now.
Thanks for the link. I will check those infos first.

physicistman said:
I worked on it over the weekend and figured out what was my problem. After going through the updater binary for the SuperSU I noticed that if you made the kernel insecure within the default.prop the updater thinks you are already root and attempts to go for the regular install instead of the systemless root method required by wear, so I luckily made a backup of the original unmodified kernel, re-flashed that and attempted to flash the SuperSU zip again, I did not use the zip in this thread instead I made a flashable zip of the newest SuperSU 2.82 version that works for wear. I have uploaded both the SuperSU zip I created along with the original kerenel that is unmodified. One thing to note if you flash the original kernel you will have to flash TWRP recovery again as I had to. I am still new to how Android Wear works, but will try to help with what I can.
SuperSU Zip.
Original Kerel.
Click to expand...
Click to collapse
I changed my phone and I have on LG Urban 2 started the Wear Recovery procedure.
after restart, it will start only on TWRP. what can I do??
Thanks in advance
mminfor

Stock recovery and boot collection

In case, you want the stock boot/recovery to install Magisk like me, you can get it out of the firmware.zip inside the OTA zip, which you can download from HTC server using the link:
Taiwan model 1.10.709.23:
http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip
Taiwan model 1.23.709.3:
http://fotadl-az.htc.com/secure/OTA....10.709.23_release_518569sr63mm3mtji85ret.zip
Hong Kong model 1.10.400.23
http://fotadl-az.htc.com/secure/OTA....05.400.13_release_517158ov5r8lbbi6tc9m38.zip
I have extracted the recovery.img and boot.img for Taiwan version. If someone doesn't want to extract it themselves, let me know through PM. I can send it to you.

devsk said:
In case, you want the stock boot/recovery to install Magisk like me, you can get it out of the firmware.zip inside the OTA zip, which you can download from HTC server using the link:
http://fotadl-az.htc.com/secure/OTA....05.709.12_release_517077z7dxrjhjj6rk2y9h.zip
I have extracted the recovery.img and boot.img. If someone doesn't want to extract it themselves, let me know through PM. I can send it to you.
Click to expand...
Click to collapse
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.

Would you know how to enable volte and wifi calling?

cameljockey1 said:
Would you know how to enable volte and wifi calling?
Click to expand...
Click to collapse
Not yet.

Perfectionalism said:
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.
Click to expand...
Click to collapse
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!

Prot02018 said:
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!
Click to expand...
Click to collapse
screenshot of your software information page in settings showing "Software number" (e.g. 1.10.709.23 for me, it would be 1.xx.1405.xx for you).

devsk said:
screenshot of your software information page in settings showing "Software number" (e.g. 1.10.709.23 for me, it would be 1.xx.1405.xx for you).
Click to expand...
Click to collapse
Here's the screenshots! Many thanks devsk.

Perfectionalism said:
Desk
Thank you your work .Is this version recovery work for HTC U 11 PLUS China. Mainland version 2Q4D200.THANK YOU again.
Click to expand...
Click to collapse
Prot02018 said:
I would like to know this too. I have the Chinese U11+ and I'm desperately looking for the boot.img and recovery.img for this variant (2Q4D200)
Thanks in advance!
Click to expand...
Click to collapse
OCEAN_M_DTWL
modelid: 2Q4D20000
cidnum: HTCCN701
OTA zip link (1.05.1405.16 - 1.03.1405.1)
https://drive.google.com/file/d/1Q3Kz88fJm1NA6ccPcb1jbQstZYWASnFO/view?usp=sharing

nenebear said:
OCEAN_M_DTWL
modelid: 2Q4D20000
cidnum: HTCCN701
OTA zip link (1.05.1405.16 - 1.03.1405.1)
https://drive.google.com/file/d/1Q3Kz88fJm1NA6ccPcb1jbQstZYWASnFO/view?usp=sharing
Click to expand...
Click to collapse
Thanks nenebear. Is this is the OTA file to go from stock 1.03.1405.1 to latest 1.05.1405.16 ?
I found the RUU's for the version of my phone also. Can anybody here confirm that the stock recovery zip file found at the following link will allow me to go back to stock recovery if I decide to flash TWRP?
https://androidfilehost.com/?w=search&s=OCEAN_M_DTWL
Thanks guys

Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David

Davil_79 said:
Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David
Click to expand...
Click to collapse
I think yours is the Europe model. If so, download the following ZIP:
https://androidfilehost.com/?fid=889964283620770441
Extract firmware.zip from it, and you will then extract boot.img from the firmware.zip, and then, patch that in magisk manager. Hope that helps!

devsk said:
I think yours is the Europe model. If so, download the following ZIP:
https://androidfilehost.com/?fid=889964283620770441
Extract firmware.zip from it, and you will then extract boot.img from the firmware.zip, and then, patch that in magisk manager. Hope that helps!
Click to expand...
Click to collapse
Many thanks!
I should have a European model. If I'm looking in the Download mode:
"htc_ocmdugl PVT S-ON
LK-1.0.0.0000
RADIO 8998-002772-1711021849
OpenDSP-UNKNOWN
OS 1.10.401.23
Nov 25 2017.01: 13: 33 (991677)"
If something goes wrong, or if it would be the wrong boot.img, can I flash a complete RUU via adb fastboat so I dont brick my phone?

Davil_79 said:
Many thanks!
I should have a European model. If I'm looking in the Download mode:
"htc_ocmdugl PVT S-ON
LK-1.0.0.0000
RADIO 8998-002772-1711021849
OpenDSP-UNKNOWN
OS 1.10.401.23
Nov 25 2017.01: 13: 33 (991677)"
If something goes wrong, or if it would be the wrong boot.img, can I flash a complete RUU via adb fastboat so I dont brick my phone?
Click to expand...
Click to collapse
That link matches your version exactly. You should be good with boot.img from that ZIP. Make backup of your stuff and be very careful with commands you fire...

devsk said:
That link matches your version exactly. You should be good with boot.img from that ZIP. Make backup of your stuff and be very careful with commands you fire...
Click to expand...
Click to collapse
Hmm.. It is 25 pcs. compressed zip-files in this download.
In one of the zip there is "boot_signed.img"
It must be it. But when I try to unzip it doesn't work. It says the file is corrupt [emoji852]️.
I will try to download the file again, mayby the download failed.
Edit: The file is corrupt. I cant unzip it
Skickat från min HTC U11 plus via Tapatalk

Davil_79 said:
Hmm.. It is 25 pcs. compressed zip-files in this download.
In one of the zip there is "boot_signed.img"
It must be it. But when I try to unzip it doesn't work. It says the file is corrupt [emoji852]️.
I will try to download the file again, mayby the download failed.
Edit: The file is corrupt. I cant unzip it
Skickat från min HTC U11 plus via Tapatalk
Click to expand...
Click to collapse
You need RUU decrypt tool to retrieve the boot and recovery image

Root HTC U11+ European model software number 1.10.401.23
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Davil_79 said:
Please help me!
I have unlocked my bootloader, installed twrp. Unfortunately, twrp is worthless since it can not be used as it seems...
Now I wonder if I can use this guide to root my phone:
"1. Download http://fotadl-az.htc.com/secure/OTA_...bbi6tc9m38.zip
Edit / Important: Read next post down below before Step 2/
2. Extract firmware.zip.
3. Extract boot.img from firmware.zip from step 2 and transfer to the /sdcard.
4. Install Magisk Manager and select Beta channel
5. Click install and choose to use "patch the stock boot image" method. It will browse you to /sdcard. Choose the boot.img from step 3. After its done, it will give you path of patched boot image.
6. Transfer the patched boot image from step 5 to PC using 'adb pull'
7. Boot the phone into download mode and flash the patched boot image.
8. Reboot and enjoy!!"
Where/how can I get the correct boot.img för my device?
My version is "1.10.401.23 9.0_g CL991677 release-keys" and none of the download links match my version? Or can I use some of them anyway?
I would be very happy and thanksful if I got help so I can get root access!
Best regards/ David
Click to expand...
Click to collapse

bnwg said:
You need RUU decrypt tool to retrieve the boot and recovery image
Click to expand...
Click to collapse
Aha! Hm ok So it wasnt that easy. I am such a Noob .
I have never used that RUU decrypt tool and it seems a bit complicated but I have to try.
Thanks for your answer!
---------- Post added at 04:22 PM ---------- Previous post was at 04:12 PM ----------
freebsd124 said:
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
Thank you! I will try this!
I'm considering starting a new thread. I know there are more people who have similar problems and considerations within this.

HTC-RUU-Decrypt_Tool
You'll find the htc-ruu_decrypt-tool here
Davil_79 said:
Aha! Hm ok So it wasnt that easy. I am such a Noob .
I have never used that RUU decrypt tool and it seems a bit complicated but I have to try.
Thanks for your answer!
---------- Post added at 04:22 PM ---------- Previous post was at 04:12 PM ----------
Thank you! I will try this!
I'm considering starting a new thread. I know there are more people who have similar problems and considerations within this.
Click to expand...
Click to collapse

freebsd124 said:
To root your HTC U11+ thru twrp use version 3.2.0.0
1. make sure you got Magisk-15.2 on you sd-card
2. boot into TWRP and leave system read only
3.goto install and install Magisk (in my case 15.2)
4. you will get error, like "can't mount data" (not to worry)
5. after install GO BACK!! DO NOT REBOOT!!
6. format data AND THEN reboot!!
7 You'll have to setup your phone as a new one; finish that and install Magisk_Manager
8 your now rooted!!! check with root checker
Hope this will help you;
Click to expand...
Click to collapse
YES! Root access :good: Finaly a success! :victory:
Now my phone is like I want it to be!! Thank you so much!!'

If it's useful for somebody wanting to try twrp and/or custom kernel...you can find inside stock boot and recovery for India/HK version, 1.10.400.23 and the new 1.24.400.2
https://drive.google.com/file/d/18FgmqIb_4UNpmRsXyxKj2bbCf6TnTXSd/view?usp=sharing

[ROOT]Root Guide for Huawei MediaPad M5

DISCLAIMER: I'm not responsible for anything that happens to your device. Use the steps below at your own risk . Be mindful of the facts unlocking bootloader voids your warranty and also hard resets your device - ALL YOUR DATA, SETTINGS, FILES AND APPS WILL BE DELETED. Rooting your device voids warranty as well. I own the Chinese SHT-AL09 8.4" LTE device and tested this root procedure ONLY WITH THIS MODEL. However, I believe there is a good chance the steps below will work for all other models of MediaPad M5, including WiFi only variants and 10" models. You MUST unlock your bootloader first. Do NOT use ramdisk image I provide in the steps below for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. Ramdisk I provided is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Credits:
@Wirmpolter - this root method largely based on his Magisk guide for Mate 9
@topjohnwu for creating the awesome Magisk Manager, which was used to patch ramdisk image with superuser binary
People, who created HuaweiUpdateExtractor
@magnumlove who pointed me in the right for developing root method in this post
This site, for hosting stock firmware for Huawei MediaPad M5
1. First, you will need to unlock the bootloader of your M5. Follow this guide
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
3. Once bootloader is unlocked, install latest Magisk Manager from the official Magisk thread
4. Once Magisk Manager gives you a pop-up prompt to either download Magisk zip or patch the boot image file - chose to patch the boot image, but instead of boot.img select ramdisk.img from step 2. Magisk Manager should give you a message the image was successfully patched. It will be saved as patched_boot.img in MagiskManager folder on your sdcard. If it does not say success - do NOT proceed
5. Transfer the newly created patched_boot.img back to your PC
6. If you already have ADB and Fastboot tools installed on your PC you can just use what you've got. If not - get them from here
7. Connect your M5 to PC via USB cable
8. Run command prompt. If your ADB and Fastboot are installed as system app - you can do this from any path in CMD. If not - you need to switch in CMD to your ADB and Fastboot folder. Either way, the patched ramdisk patched_boot.img file must be in the same path, from which you will be running commands below in CMD window
9. Type "adb " in CMD window to start android debug bridge
10. Type "adb reboot-bootloader" and wait until your device restarts in Download mode
11. Once in Download mode, type "fastboot flash ramdisk patched_boot.img" - you should see some output from flash procedure, indicating successful flash
12. Once patched ramdisk is flashed, type "fastboot reboot"
That is it - you're done. Once your device reboots it will be rooted.
Note 1: Magisk Manager has it's own built-in superuser app and uses Systemless root, which works completely differently - you will not see external, standalone app like SuperSU or SU you might be familiar with in your App Drawer. The way to control the superuser app is from Magisk Manager itself: Settings->Superuser section
Note 2: I don't do tech support via PM, so don't PM me for help or with questions. Use the thread instead, and some other XDA members or myself will probably help you. Good luck!
Note 3: You may find some links to Huawei stock firmware in the 2nd post
UPDATE - August 6, 2018
Huawei officially approved 8.0.0.171 firmware with GPU Turbo for installation on SHT-AL09 devices. If you're doing first time root - just follow the original steps above. If you are already rooted and want to upgrade to 8.0.0.171 - follow the steps below:
1. Boot into download mode:
Code:
adb reboot-bootloader
from CMD window
2. Flash stock recovery from 8.0.0.171 to your device in fastboot:
Code:
fastboot flash recovery_ramdisk recovery_ramdis.img
3. Download and install the official OTA through Settings (full or just the update)
4. Boot into download mode again and flash patched ramdisk from 8.0.0.171
Code:
fastboot flash ramdisk patched_boot.img
5. OPTIONAL: If you were using TWRP or any custom recovery - you will need to reflash it back
Code:
fastboot flash recovery_ramdisk twrp.img
or whatever you named your custom recovery image
REMINDER: Do NOT use ramdisk image I provided for any other model besides SHT-AL09 - doing so is guaranteed to render your device unusable. This patched ramdisk is ONLY for SHT-AL09. You will need to extract your own ramdisk from stock firmware, specific to your device model
Needless to say, all the images you are going to flash must reside in the same directory, from which you are going to be running the CMD commands. If your ADB/Fastboot folder is not in your WIndows' PATH environmental variable - the images must be placed in the same folder where ADB/Fastboot binaries are, and CMD commands must be run from that folder.

C5Longhorn said:
Yes, they still work. I have the same model and build as you and I'm rooted.
Sent from my Pixel 3 XL using Tapatalk
Click to expand...
Click to collapse
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.

samiller said:
I'm considering buying an SHT-W09 with firmware version 8.0.0.200 (C567), but I'd like to know if I can root it first. I do not know if the bootloader has been unlocked. Since you have the same version, can you confirm that it's possible to unlock and root, and if so, sketch out how it's done? I'm confused about whether it's possible with this firmware.
Click to expand...
Click to collapse
Unlocking is possible *only* if you've gotten already your unlock code. As this service was suspended about 2 years ago there is no easy way to get it unlocked.

Small request to developers, or people with access to reliable file hosting: I don't have a developer account, so all the files I linked or referenced in the OP are hosted on free hosting sites. That file hosting has expiration date and max downloads limit, so the files will become inaccessible sooner rather than later. Please upload these files to reliable hosting and create a post with the links. I will link your post in the OP as a mirror.
In the meantime, mirror for SHT-W09 firmware: https://mega.nz/#!asVjmZrR!bW2OmXgTjnyVN4pqb9fA7OzAJ4bzil7YZxNW14qoCmk

I can confirm that this works on the 10.8" wifi model using the devices relevant ramdisk.img.

Hello, can somebody test sixaxis controller tool with root and magisk? There is a Trial in Google Play Store, that is called sixaxis compatibility checker without purchise the App. Maybe i want to buy the Tablet, but only with Dualshock 4 Support...

Just a heads up, been following threads on this forum for flashing a GSI. Now that you guys can root, you can also make backups of your own stock system image if you can't find one from Firmware Finder. Then you can safely try flashing the GSI.

@MishaalRahman well it's bit like chicken egg dilemma. As we do not have a stock system image for e.g. SHT-W09 we cannot patch the ramdisk.img and so we cannot get the stock system image ...

Thanks Apo11on, great to have root so soon for the M5! Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.

Question is, for those of us with the Non Pro version, can this still be done.

@OHP Yes. The OP did it with the 8.4" version which has no pro option.
I'm looking to buy the Chinese 10" wifi version myself but need Google Play Store + Services on it which I'm guessing the Chinese version doesn't have. Is one of the firmwares at the website you link to a global version of the firmware that will work on this model?

OHP said:
Question is, for those of us with the Non Pro version, can this still be done.
Click to expand...
Click to collapse
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.

magnumlove said:
Doesn't matter what version you have as long as you have access to your device firmware and the ramdisk.img. You really need to reread the guide.
Click to expand...
Click to collapse
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:

OHP said:
Problem I have is :
CMR-W09C432B123 (8.0.0.123) from download headlines.
notice the Bold letter.
my Firmware on device:
CMR-W09C432123 (8.0.0.123)
obliviously it could be nothing but I wouldn't want to brick my tablet :fingers-crossed:
Click to expand...
Click to collapse
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).

magnumlove said:
I have exactly the same tablet/firmware as you and it was fine. The additional letter also threw me a little. But if you are unsure, download Huawei Firmware Finder from Google play and it will automatically detect your tablets firmware (which you can download if you wish).
Click to expand...
Click to collapse
I took the plunge, and I am sucessfully rooted now :silly:

struggling with this part
2. Transfer this patched ramdisk image to your device
Note for users with version of M5 other than SHT-AL09: Do NOT use the above ramdisk image. Download the full stock rom (update.zip) from the site I linked in the credits. Extract UPDATE.APP file from the zip. Then use HuaweiUpdateExtractor to extract ramdisk.img specific to your device. If you get errors in HuaweiUpdateExtractor - uncheck first 2 checkboxes for checksum verification on Settings tab and try again
I have a CMR-W09 :s i can got the files downloaded and the huwai software not sure how i make a img

The good news is I followed these instructions yesterday and they worked perfectly (SHT-AL09).
The bad news is, I seem to have lost root overnight.
---------- Post added at 06:41 AM ---------- Previous post was at 06:22 AM ----------
And I figured out why I lost root; I was playing around with Developer options and switched the default GPU renderer from 'default' to 'Skia.' Apparently, this disables root access until you switch back. I regained root access on a reboot, lost it again after switching back to Skia, and then regained it after switching back to default.

I got the right image file from the site and huwai extract. I have googled how to use this app but what files do I extract as there appears to be. Alot ? I extracted all of them ? I don't have a ramdisk.img
Also thanks for writting this up. Without it I would be lost

Thanks for the efforts making this thread. Unfortunately my device is SHT-W09 and I'm still waiting for the right firmware. Is there anything I can help, considering I have the device?

@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...

This works perfectly no issues. i had some how maanged to download the wrong rom first. AND thankfully it did not have a ramdisk in. it is important that your firmware matches the firmware present on the site as explained. This was easy guide to follow now to flash it with somthing other then andriod

AndDiSa said:
@dkk6 I am in the same boat as you. Unfortunately I installed the update to 8.0.0 123 without having the Firmware Finder installed on the device. Do you have installed already the update to 8.0.0 123?
If not, you could install Firmware Finder and provide us with the ota url ...
Click to expand...
Click to collapse
I'm on 8.0.0.101

[2022 Root For S7/S7Edge Oreo Rev4_To_Rev10/A_Odin Flashable Or ADB Method] Plus [Limited Root Method Rev11/B _Using Combo_Firmware]

Oreo Root For The S7/S7E (Will work on Rev4-Rev10/A Bootloader) Adb Install
A big thanks goes out to @klabit87 he is 99 percent the reason we have root! Also @stang5litre and stang5litre test group.​Prefered Root Method Oreo Only Using Odin Only For Rev-4 Too Rev10/A
Odin Install Root Method For S7 Flat Can Be Found Here
Odin Install Root Method For S7 Edge Can Be Found Here
Root Method Using Odin Only For Rev-11/B -- Please Read Limitations On The Thread
Rev11/B Root Method For S7 Flat Can Be Found Here
Rev11/B Root Method For S7 Edge Can Be Found Here
ADB Method Oreo Or Nougat For Rev-4 Too Rev10/A -- Must Use Adb Method For Nougat Root
2023_S7_Flat_Edge _ADB_Root_Plus_Safestrap_V1.7z​
Directions:
This works for Oreo Rev4-Rev10/A Bootloader Roms or Nougat Rev4
As always there is a chance of bricking your phone
1. Download and extract 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z
2. Reboot your phone to download mode
3. Inside the 2022_S7_Edge_ADB_Root_Plus_Safestrap.7z folder you will find an Odin_Firmware folder. Use Odin and flash the Eng Boot Image for your phone
4. Once phone is rebooted and connected to computer click on the cmd-here.exe and type Install_One_Click.cmd in the command window and hit enter
5. Once root is done and root bat closes your phone will reboot too stock recovery where you must wipe data
6. Once booted click on SuperSu app and update su binary if app ask then reboot
7. Don't flash any superuser zips in recovery that are not made by me or use any other SuperSu apk
Rebooting Too Safestrap Recovery
1. Reboot phone as you would too boot stock recovery Pwr + VolUp + Home. It takes up too 40 seconds too boot recovery. Ignore the mount system errors on info screen
2. Enter recovery.
3. Too leave just reboot system ignore no system installed message if you get it
4. There is screen lag issues on scrolling in recovery. There is aroma file manager that takes care of this issue while in recovery but selecting zips too install may present a problem for this you can use the kernel manager recovery flash option while phone is booted too system. Simply select zip too flash and phone will reboot too recovery and flash it and reboot back too system. Most other function in recovery should work the issue is just scrolling too select files.
5. Flashfire is installed as an alternative as well
Features:
1. SuperSu Root- Do not use any other SuperSu app. Its ok to update su binary if app ask.
2. Safetrap recovery-Still working out scrolling issue
3. Flashfire
4. Kernel tweaks CPU governor set too Conservative
5. Entropy/Swapiness set to High
6. Build Prop tweaks to combat lag
7. Bloat removed from rom
8. Knox removed from rom
Bugs:
Eng Boot Image causes lag
Safestrap Recovery has scrolling issues
Random Reboots will most likely happen
Safetynet will not pass
Battery life may not be optimal
SuperSu cannot be updated
Flashfire may need date changed too 2016 to function if it just keeps closing on you
Volte And Hotspot Fix
View attachment OREO_VOLTE_ICON_HOTSPOT_FIX.zip
Old Downloads
S7_Oreo_Nougat_Adb_Advanced_Root_V12.zip Recommended Root Zip
This zip gives you the option to install some cpu tweaks and will also. Install the entropy tweak that the SEFix app does. The tweak sets entropy to high by default I also include the SEFix app if you want to change the settings. I also set the swappiness settings to very high. If you want to change these settings you can download the speedup swap app from playstore. The above zip also removes knox and changes the fstab.qcom file to disable dm-verity on system files and remove all file encryption which makes it seem to work better and make it compatible with my no root roms that has to have this done to allow safestrap to work. Installing the above zip requires a data wipe unless you have already installed it or you are coming from my non rooted roms
S7_Oreo_Su_Binary_Only_ADB_Root.zip Alternative Root Zip
This root zip is only for oreo an only installs the su binary to the system/xbin folder giving you root privelages it has no tweaks and does not change the fstab.qcomn file to remove dm-verity and system file encryption. There is no SuperSU app installed either but you will have root privelages.
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap
- @me2151 for help and finding alternative flash methods
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for help
- @partcyborg for help and guides other devices root methods
- @elliwigy for being great help when I need it
- @stang5litre
- @jds3118
- @Krog18
If I missed you please pm me
Donations
If you would like to donate please send all donations to @klabit87 PayPal Link Here and give a thanks!

It's awesome to see yet ANOTHER post by you! You're doing great. Looking forward to future development

Nice, hopefully I will update to Oreo on e @stang5litre does a new rom for us. Once again thanks @klabit87 and you also
Sent from my SM-G935V using Tapatalk

I've selected "1 - Yes SafeStrap is Install" in :MENU5 phone reboted to SafeStrap how to exit? It is always rebooting to safestrap back.
Note: After I selected that menu console fast closed and I noticed some error.

abyss7 said:
I've selected "1 - Yes SafeStrap is Install" in :MENU5 phone reboted to SafeStrap how to exit? It is always rebooting to safestrap back.
Note: After I selected that menu console fast closed and I noticed some error.
Click to expand...
Click to collapse
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Edit:
redownload zip from OP its fixed. As far as you not being able to boot flash the BL enter_safetrap file then enter safestrap then mount system use file manage and delete e2fsck from system/bin folder then rename e2fsck.bin to e2fsck then reboot to download and Flash BL file in BL slot And the Eng boot loader in the AP slot

jrkruse said:
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Click to expand...
Click to collapse
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.

Nice!! Is this the binary you wrote and how did you get the script to fire off??

abyss7 said:
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Click to expand...
Click to collapse
follow my above directions

Craz Basics said:
Nice!! Is this the binary you wrote and how did you get the script to fire off??
Click to expand...
Click to collapse
@klabit87 found a way to hook in a script at boot so normal root works

jrkruse;77136767 [user=4168602 said:
@klabit87[/user] found a way to hook in a script at boot so normal root works
Click to expand...
Click to collapse
Normal root as in SuperSU?? And hats off to you @klabit87

abyss7 said:
On the contrary, I cannot exit from safestrap, it enters always after reboot. Sometimes screen contain small image of original loockscreen, it looks like split view.
Click to expand...
Click to collapse
jrkruse said:
Wow sorry about that I had script wrong. You cant really enter safestrap can you?
Edit:
redownload zip from OP its fixed. As far as you not being able to boot flash the BL enter_safetrap file then enter safestrap then mount system use file manage and delete e2fsck from system/bin folder then rename e2fsck.bin to e2fsck then reboot to download and Flash BL file in BL slot And the Eng boot loader in the AP slot
Click to expand...
Click to collapse
Follow these instructions

V2 zip is posted in OP that fixed the safestrap issue

Craz Basics said:
Normal root as in SuperSU?? And hats off to you @klabit87
Click to expand...
Click to collapse
Yes normal supersu

jrkruse said:
Yes normal supersu
Click to expand...
Click to collapse
I didn't think SuperSU supported Oreo?

@jrkruse, will it work with your CRF1 hybrid?

TheDevelopper said:
@jrkruse, will it work with your CRF1 hybrid?
Click to expand...
Click to collapse
Yes make sure you download V2 zip file from the OP

Craz Basics said:
I didn't think SuperSU supported Oreo?
Click to expand...
Click to collapse
It does 8.0 not 8.1

@jrkruse, there are two different Eng.boot for G935, which one should I choose? The 21.92MB or the 22.07MB?

Added a Volte Icon and Hotspot fix zip to OP

TheDevelopper said:
@jrkruse, there are two different Eng.boot for G935, which one should I choose? The 21.92MB or the 22.07MB?
Click to expand...
Click to collapse
Read what they say it tells you one is for OREO and one is for NOUGAT