Database Info

Official OTA Update Links and OTA updating modified systems

Don't forget to thank me and Radii it means a lot to us!
Click to expand...
Click to collapse
Upon discovering the reason people being given an error trying to flash OTAs in my TWRP recovery image I decided I would come up with a work around while I work out a way to fix it.
The following solution is group work between me and Radii.
If you came here just for OTA links then click HERE
Click below spoiler if you haven't installed TWRP on your device and you want to OTA update and then install TWRP.
First you need to download the version you would like, in theory you could backdate although this hasn't been tested and it may misbehave. For example the latest version as of 16/10/2015, build number cm-12.1-YOG4PAS38J.
On the spread sheet you will need two files, the fastboot and the signed. In the fastboot ZIP there is a file called recovery.img. Copy this to your android SDK platform tools folder. Now with the signed ZIP you either copy that to the same folder (platform-tools). Put your phone into fastboot mode and type.
Code:
fastboot -i 0x2b4c boot recovery.img
Or the name of the recovery if you renamed it.
Your phone will boot into Cyanogen OS Recovery. From there click Apply Update (Top option) and click ADB Sideload. Then type,
Code:
adb sideload cm-12.1-YOG4PAS38J-ham-signed.zip
Or whatever you renamed it to.
Reboot and you're done! Now you'll need to install TWRP to flash things like SuperSU and Xposed.
To install TWRP you need to download the latest TWRP image from HERE move that to platform-tools and type (with your phone in fastboot mode/bootloader mode of course)
Code:
fastboot -i 0x2b4c flash recovery "recovery.img"
Changing the name in the quotations to the name of the recovery and removing the quotes.
Click below spoiler if you have installed TWRP on your device and you want to OTA update and restore/preserve TWRP
Do the same as above, I have discovered it's impossible to preserve because Cyanogen will auto-write it's own recovery to the recovery parition.
Nerdy stuff
If you're wondering why you can't OTA without going through all this then it's because Cyanogen OS will do checks to see if the System has been r/w mounted. If so then it will stop all OTAs from installing. Simple when you think about it.
FAQ
Q: Why isn't TWRP still installed after installing the OTA? A: Because Cyanogen OS will write over the recovery partition with Cyanogen Recovery
Q: Will I lose all my data? A: Don't wipe and no, you can dirty flash to preserve data.

Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...

othe01 said:
Thanks for your work, really appreciated.
However, it sucks a bit that we have tons of work just for the OTA updates if we want root, i guess we should annoy Cyanogen to add a Superuser option to CyanogenOS...
Click to expand...
Click to collapse
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk

Breadcrust said:
It's designed to be shipped with devices like Samsung or LG's ROMs they'll never add that option.
Sent from my Z1 using Tapatalk
Click to expand...
Click to collapse
Why not? root is a normal option in CyanogenMod, why wouldn´t the "commercial" edition not support it? I see no reason they can´t add it to PrivacyGuard.
Here one of the forum admins said hes telling the team to add it -> http://community.cyngn.com/t/reques...-thethering-and-inbuilt-superuser-access/97/2

Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.

othe01 said:
Breadcrust,
did you try this method used for oneplus one phones with CyanogenOS?
https://forums.oneplus.net/threads/flashable-zip-cm12-enable-integrated-superuser.297089/
https://github.com/julian-klode/bacon-superuser/
From what i´ve read OTA updates are working with it and all we need to do is update the recovery after installing a new ota, the script on github creates the patched boot files automatically, we just have to change the config to use the ZUK files.
All theory tho...as i don´t have my phone yet.
Click to expand...
Click to collapse
I'll look into it at sunrise it currently 3:23AM here so can't do it now
P.s thanks for waking me :3
Sent from my Z1 using Tapatalk

@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:

Titokhan said:
@othe01
No COS device allows you to flash incremental OTA if your /system partition is modified. Your quoted package puts compatible su binary in /system & flashes boot-debuggable kernel so that root can be achieved from both app & ADB. It has nothing to do with OTA. Your only choice is to get the signed zip & flash it manually.
@Breadcrust
It would be nice to put incremental OTA zip links too. My posts regarding OTA links also contain them.
:highfive:
Click to expand...
Click to collapse
sounded different here: [FLASHABLE ZIP] [CM12] Enable integrated superuser
But is prolly just a misunderstanding from my side.
How exactly does CyanogenOS check if System is modified and can´t we patch the check with an xposed module?

@othe01
He must used the signed zip to update. Regarding OTA faliure, I've discussed the issue here: http://forums.yuplaygod.com/index.php?threads/15124/
You need to registered in the forum to read, so I've uploaded a PDF of the same: https://drive.google.com/file/d/0B9zZIJPXbMsubkFBYmZ4eGtMQjQ/view?usp=sharing
I personally own OnePlus One & YU Yureka so already have a good experience with these things.
The whole procedure is clearly explained - no 'Xposed' module can bypass it. You can, in theory, deploy a file based OTA (I've already requested it through YU developers) instead of block based OTA or patch the update-binary to return always true (unmodified) value while checking the state of partitions.
:good:

@Titokhan I will post them later
Sent from my Z1 using Tapatalk

@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .

aaswar said:
@Breadcrust can you please help me if you can, I have problem flashing any ota (increments or full), it return error " this package is for device:Z1 this device is k9", all ota was installed directly till unlocked bootloader and root .
Click to expand...
Click to collapse
Issue is noted method is in post
Sent from my Z1 using Tapatalk

@Breadcrust
cm-12.1-20150805-EXPERIMENTAL-YOG4PAP1CG-ham: http://forum.xda-developers.com/showpost.php?p=63390843&postcount=223

@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?

aaswar said:
@Breadcrust
for clarification:
-isn't "cm-12.1-YOG4PAS38J-ham-signed-fastboot.zip" is the same as "cm-12.1-YOG4PAS38J-ham-signed.zip", but with the recovery image include, can sideload this file using the same process you mentioned?
-if the phone is rooted, boot with the COS recovery and sideload the "cm-12.1-YOG4PAS38J-ham-signed.zip" will not work as the system partition is already been modified by the root process, am I right?
Click to expand...
Click to collapse
re: above
if using cos recovery and sideload via abd or from file the full signed version , and your have root, it will work, root will be lost though.
fastboot zip has recovery signed doesn't. you need to flash recovery extracted from the fastboot zip and then flash the signed full zip using cos either using abd or sideload file onto system

I flash the rom, but when I insert CDMA SIM into slot one, there is no signal
and there is no option to choose band from the menu.
would you please instruct on how to get CMDA works?

@taitai
As you can see here, it is not an CDMA device.

As regards technical faults as well we're unable to help in most cases as ROMs are from Cyanogen and unedited.
Sent from my Z1 using Tapatalk

I have a chinese version of Z1 and it has CDMA capability

None of them do. They're the exactly the same under the hood.
Sent from my Z1 using Tapatalk

[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] [OFFICIAL EU UNTOUCHED] [MULTI] LeEco Le2 X527 5.9.21s

Hello
i make dump and convert it to recovery rom
it can be flashed by TWRP
this is last official EU version of Le2 x52x rom
this rom have complete translation (without english or chinese untranslated parts) of all EU languages
best way how to flash it if you havent got twrp
0. download rom https://webshare.cz/file/363v61oM3d/x527-5-9-21s-rar
1. extract downloaded package
2. go to bootloader by pressing and hold volume down and power button
3. open command promt and run:
3.1 fastboot oem unlock-go
3.2 fastboot boot twrp.img
4. now you are rebooted to twrp
5. copy rom (X527-5_9_21S.zip) to the phone
6. flash rom
7. wipe data factory reset
8. reboot phone
9. you are in official EU rom with stock recovery

veisen said:
Hello
i make dump and convert it to recovery rom
it can be flashed by TWRP
this is last official EU version of Le2 x52x rom
this rom have complete translation (without english or chinese untranslated parts) of all EU languages
best way how to flash it if you havent got twrp
0. download rom https://webshare.cz/file/363v61oM3d/x527-5-9-21s-rar
1. extract downloaded package
2. go to bootloader by pressing and hold volume down and power button
3. open command promt and run:
3.1 fastboot oem unlock-go
3.2 fastboot boot twrp.img
4. now you are rebooted to twrp
5. copy rom (X527-5_9_21S.zip) to the phone
6. flash rom
7. wipe data factory reset
8. reboot phone
9. you are in official EU rom with stock recovery
Click to expand...
Click to collapse
Can you make the same with the x522? I want to get stock again

nabelar82 said:
Can you make the same with the x522? I want to get stock again
Click to expand...
Click to collapse
yes you can

Thanks! Thats exactly what im looking for! Pefect stock ROM! Easy to install with twrp, working perfect in my x520.

veisen said:
yes you can
Click to expand...
Click to collapse
I mean if you can I don't have the stock backup I deleted by mistake

nabelar82 said:
I mean if you can I don't have the stock backup I deleted by mistake
Click to expand...
Click to collapse
you can flash this rom it is compatible

veisen said:
you can flash this rom it is compatible
Click to expand...
Click to collapse
The ROM is really good but i Tried everything to pass through safetynet but i cant do it.

Can I install regularly via stock update, w/o twrp? What's is date of security patch? Can you put homescreen there?
I'm on 5.9.021s for x526. I have x527.

google Drive
Can you upload it on google Drive and share the link please , cause google drive is faster and easier way to download
Owing all gratitude towards you

svsavic said:
Can I install regularly via stock update, w/o twrp? What's is date of security patch? Can you put homescreen there?
I'm on 5.9.021s for x526. I have x527.
Click to expand...
Click to collapse
You can not update it via stock recovery bcs leeco never release this rom it is installed on europe (Czech branded phones) i cannot post screen bcs im change phone i have Essential ph-1 for now

Can i flash it as a secondary rom (multirom)?

Does anyone have the stock modem for x527? because my signal keeps coming on and off constantly in every eui rom so I can't go back to stock, strangely I can use it on Nougat and Oreo. I've flashed this stock rom but no solution.

Hi @veisen !
Thanks for the ROM.
However - how can it be an official ROM if it shows a 'Le X527' but with a 'Snapdragon 820' (when it should be a Snapdragon 652)?
Cheers, raimerik

raimerik said:
Hi @veisen !
Thanks for the ROM.
However - how can it be an official ROM if it shows a 'Le X527' but with a 'Snapdragon 820' (when it should be a Snapdragon 652)?
Cheers, raimerik
Click to expand...
Click to collapse
Thats a bug with official rom itself. This rom is official, so chill

veisen said:
5. copy rom (X527-5_9_21S.zip) to the phone
Click to expand...
Click to collapse
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?

xe7um said:
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
Click to expand...
Click to collapse
Try pushing it through adb
Rename the file to update.zip
Open terminal
cd "directory of the zip folder"
adb push update.zip /sdcard/
Wait for few minutes, it should be done.

bonsai.14 said:
Try pushing it through adb
Rename the file to update.zip
Open terminal
cd "directory of the zip folder"
adb push update.zip /sdcard/
Wait for few minutes, it should be done.
Click to expand...
Click to collapse
I've tried it already:
Code:
[email protected]:~/LeeecoLe2X527$ adb push -p X527-5_9_21S.zip /sdcard/Varis
Transferring: 15335424/2096207546 (0%)
Hanged up

xe7um said:
can't copy X527-5_9_21S.zip (2,1GB) to /sdcard. Copy always stops after copying 140MB or so. I copy mounting USB storage from TWRP, and then through the file administrator with copy-paste (Ubuntu 16.04, linux). Filesystem is ok. I've done a factory reset before. What can I do?
Click to expand...
Click to collapse
You can Sideload it enable sideload on twrp and use command
adb sideload "/your_dir/your_file.zip"

veisen said:
You can Sideload it enable sideload on twrp and use command
adb sideload "/your_dir/your_file.zip"
Click to expand...
Click to collapse
Ok, @veisen I'll try it. But do you have any reasonable explanation of why adb push stops copying?

Any one using this rom? How's battery life n camera ?
If possible post some screenshots

[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