[ROOT] Full Root for the Mate 9

[ante0]

Install twrp.. All was OK.. I made à wipe cache like the post 'full root Mate 9' said to try too root it again.. Bad idee.. Now i'm in Bootloop.. I tried again to flash twrp, boot. Img... Nothing..

You shouldn't bootloop from wiping cache. You mean you clicked on Format Data?
Anyway, the phone should boot even after that. If you're on stock boot image it will just encrypt internal again.
If you're on any of the other boot images (B138 or B165 linked in the OP) you can just flash back stock boot using fastboot.

Also see my previous edited post.

 

[dkionline]

Install twrp.. All was OK.. I made à wipe cache like the post 'full root Mate 9' said to try too root it again.. Bad idee.. Now i'm in Bootloop.. I tried again to flash twrp, boot. Img... Nothing..

Thats why dm-verity isnt removed.

 

[xkeyblackx]

So..it works..but! Il tried too flash twrp again to root.. And now.. Bootloop ans the phone is bricked..
Always root my phones since many years.. Huawei seems to be a big prob.. I think i need a full rom flashable.. But.. Dont know now.. Loosed

Damn thats realy bad :/ maybe u must unlock ur bootloadet agian?

How did u Flash the Update with stock recovery?

Gesendet von meinem MHA-L09 mit Tapatalk

---------- Post added at 11:37 PM ---------- Previous post was at 10:50 PM ----------

Can anyone tell me how i can Update to B138 with stock recovery?

Gesendet von meinem MHA-L09 mit Tapatalk

 

[ante0]

Damn thats realy bad :/ maybe u must unlock ur bootloadet agian?

How did u Flash the Update with stock recovery?

Gesendet von meinem MHA-L09 mit Tapatalk

---------- Post added at 11:37 PM ---------- Previous post was at 10:50 PM ----------

Can anyone tell me how i can Update to B138 with stock recovery?

Gesendet von meinem MHA-L09 mit Tapatalk

You can't unless you get it as an OTA.
Only way right now is Firmware finder or FunkyHuawei.

 

[xkeyblackx]

You can't unless you get it as an OTA.
Only way right now is Firmware finder or FunkyHuawei.

Ok thanks

Gesendet von meinem MHA-L09 mit Tapatalk

 

[ajsmsg78]

Ok, found out why it was screwing with me. If you flash HW first, it makes everything work OK.
If you flash public after, the script in public uses the command "delete_recursive("/data/hw_init"). So everything from the HW zip goes poof. Lol.
I'm gonna merge the 2 instead and see if that fixes everything

Edit: merged zip worked. just removing delete_recursive would work too

Or if youre smart, flash public first....

Can I ask how you're flashing it? In TWRP it gives errors and through dload it doesn't work either. I've been manually installing it.

 

[dkionline]

Please point it out, what you changed in boot partition. The phh su is known as the latest stable, i see.
I had your problems with developer options and security settings too a month ago, that cant be changed until data got working due to encryption. Or i specify, the keys wont be written after decrypting.
I think your changes would help, to find the culprit in encryption of data, unless your open to share.

 

[JATCHUHAN]

Can I ask how you're flashing it? In TWRP it gives errors and through dload it doesn't work either. I've been manually installing it.

I have flashed these zips in twrp, public first and then hw. Public flashes no errors, hw flashes with some errors. Upon booting up phone I get all my missing Huawei apps back and system update option in settings menu.
The only thing that seems to be missing is the magazine lock folder for the screen lock. I have a backup of the pictures in the magazine unlock folder and just manually add them afterwards.
All seems ok afterwards

Sent from my MHA-L09 using XDA-Developers Legacy app

 

[ajsmsg78]

Please point it out, what you changed in boot partition. The phh su is known as the latest stable, i see.
I had your problems with developer options and security settings too a month ago, that cant be changed until data got working due to encryption. Or i specify, the keys wont be written after decrypting.
I think your changes would help, to find the culprit in encryption of data, unless your open to share.

Use Android Image Kitchen to extract the boot.img and edit the ramdisk/fstab.hi3660 file and change the fileencryptioninline to encryptable. (you'll see it in the userdata line) Then edit the split_img/boot.emmc.win-ramdisk.cpio.gz in linux (Linux can open that file like a zip) and change the same line in the fstab.hi6630 file. Then save the file and overwrite the existing file in Android Image Kitchen with the one you just edited in Linux, then repack the boot.img. Now the boot image will no longer force encryption so if you're decrypted your data will stay that way.

 

[ante0]

Can I ask how you're flashing it? In TWRP it gives errors and through dload it doesn't work either. I've been manually installing it.

Like a regular flashable zip. Public installs fine, HW installs fine too but errors out because it tries to run Update.app with some weird command. It still flashes what it's supposed too though. If you flash HW before Public, public will remove what HW installed.
And they're supposed to install to /data/hw_init/.
When you're installing manually, do you chmod to 755 after, and chown "selabel" (I think that was the owner the script gave all files from HW and public) ?

 

[ajsmsg78]

Like a regular flashable zip. Public installs fine, HW installs fine too but errors out because it tries to run Update.app with some weird command. It still flashes what it's supposed too though. If you flash HW before Public, public will remove what HW installed.
And they're supposed to install to /data/hw_init/.
When you're installing manually, do you chmod to 755 after, and chown "selabel" (I think that was the owner the script gave all files from HW and public) ?

Yeah I do.

 

[ante0]

Yeah I do.

What errors do you get other than "mountencrypt" and error status 7?

 

[druun]

Ok..

You shouldn't bootloop from wiping cache. You mean you clicked on Format Data?
Anyway, the phone should boot even after that. If you're on stock boot image it will just encrypt internal again.
If you're on any of the other boot images (B138 or B165 linked in the OP) you can just flash back stock boot using fastboot.

Also see my previous edited post.

Thank's.. I spend a moment to find what was wrong... Pffff I made a "reset factory"..
I just read your message and a found the solution this night after flashing MATE_9_DECRYPTED_BOOT_B138.img my phone came back to life..
install twrp 3.0.2.2 again and root .
All work fine now.. I make my BACKUP now...
Thank's every body for help...

 

[ajsmsg78]

What errors do you get other than "mountencrypt" and error status 7?

I'm fixing the script now so it doesn't give any errors.

 

[ante0]

I'm fixing the script now so it doesn't give any errors.

Might be an idea to check if /data is actually mounted. Mine seems to be automatically and the script should toss errors if it wasn't.

 

[ajsmsg78]

Might be an idea to check if /data is actually mounted. Mine seems to be automatically and the script should toss errors if it wasn't.

The mountencrypt command is useless so I removed it as is the second to last line which is what throws the error.

All of my files (with thanks to the original creators of course) will be stored here. New files, mods, etc will be updated accordingly.

https://www.androidfilehost.com/?w=files&flid=151828

 

[Blue.Ember]

Twrp format data and wipe doesn't erase the data totally, my phone is working but I have FRP lock, and cannot enable it from developer option, I tried to flash official recovery from twrp as an advice from a friend but this deleted the twrp and didn't install official.
So now I can't flash anything from bootloader, don't have an official recovery so I can flash full rom, also don't have twrp so I can gain root again.

Anything else should I do to solve this

Sent from my MHA-L29 using Tapatalk

 

[eddmecha]

Twrp format data and wipe doesn't erase the data totally, my phone is working but I have FRP lock, and cannot enable it from developer option, I tried to flash official recovery from twrp as an advice from a friend but this deleted the twrp and didn't install official.
So now I can't flash anything from bootloader, don't have an official recovery so I can flash full rom, also don't have twrp so I can gain root again.

Anything else should I do to solve this

first of all u r on which build n region?L29Cxxx?if u r on C636 mayb u can try to dload using the offline b110 fw file from this thread https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656

edit - to unbrick you just need the dload file and also the hw data zip ,let me know if u need assistance

 

[Blue.Ember]

first of all u r on which build n region?L29Cxxx?if u r on C636 mayb u can try to dload using the offline b110 fw file from this thread https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656

Dload method will not wotk specially for my situation cause it need an official recovery to install the update and I don't have, when I try to enter to recovery it's direct me to eRecovery, my build is L29C185

Sent from my MHA-L29 using Tapatalk

 

[gm007]

Dload method will not wotk specially for my situation cause it need an official recovery to install the update and I don't have, when I try to enter to recovery it's direct me to eRecovery, my build is L29C185

Dload doesn't need recovery.img maybe it use recovery2.img cause it work even with twrp installed. But the problem with oeminfo.
You can try both c636 and AL.