Database Info

[Bootloader] JZO54K Bootloader

Here is the bootloader in a zip that can be flashed over anything.
I recommend flashing this because it fixes the issue where you couldn't boot into recovery from the bootloader.
Download (Mediafire)
Download (Goo.im)
MD5: a8715642fcb0400579dde21b5e4cc673

yeah,finally!!!!
it's my fisrt need in absolute in all my device the fix of the reboot-to-recovery from bootloader's bug...many times away from pc i bootlooped the n7 by my tests,and i had to wait hours to came back home to connect to pc...very good by google!:laugh:
On another side,i think is abolsutely right flash this BL and continue using a 4.1.1 rom instead of new base...right?
EDIT Wow,is very light a bootloader for nexus 7...compared tol for example a gnex one..

Odd...doesn't fix the boot into recovery bug for me. At least with TWRP.

In the german android-hilfe forum someone soft bricked his N7 by flashing this (He got a bootloop and cannot Boot into the CWM anymore).
Can someone confirm that the zips are functional or not?

I downloaded from the meadifure link in his forum on rw, installed it through clockworkmod touch and haven't had any problems. Booting to recovery from the bootloader works fine for me.
Sent from my Nexus 7 using xda premium

Thanks for this, for some reason when I updated to 4.1.2 OTA using CWM everything went fine no errors but it didn't actually update my bootloader which is odd. So I was able to update it using the CWM zip provided. Thanks!

Thanks for this! Flashed without issues.
Skickat från min Nexus 7 via Tapatalk 2

How would this affect my ability to hide breaching my warranty? Would replacing the bootloader that was shipped with the device give me away, or does an OTA update flash the new one anyway?

z1gackly said:
How would this affect my ability to hide breaching my warranty? Would replacing the bootloader that was shipped with the device give me away, or does an OTA update flash the new one anyway?
Click to expand...
Click to collapse
Update is supposed to flash new one anyway
---------- Post added at 11:13 PM ---------- Previous post was at 11:00 PM ----------
Worked fine here, thanks a lot
TWRP and PA 2.1799

how do we flash this? i have cm10 running. Thanks in advance

this,in recovery cwm...or via fastboot if you found the .img,but this case is from cwm

sert00 said:
in recovery cwm of course.(or twrp)
Click to expand...
Click to collapse
Thanks i tried that and i ended up with boot loops. I managedto flash the grouper bootloader and booted up. What am i missing or doing wrong?

Worked great for me, thanks OP.

Thanks, worked for me on JRO03S ROM.
Sent from my Nexus 7

Thanks OP worked like a charm!!!
Sent from my Nexus 7 using XDA Premium HD app

Crazy4G1 said:
Thanks i tried that and i ended up with boot loops. I managedto flash the grouper bootloader and booted up. What am i missing or doing wrong?
Click to expand...
Click to collapse
Did you double-check the MD5 hash of the download to ensure it wasn't corrupted in the downloading process?

Ahh dang i got a bootloop, I can get into fastboot mode but recovery is a no go, any suggestions?

Same im stuck at google logo, cant get into recovery. Any ideas?

Pithism said:
Same im stuck at google logo, cant get into recovery. Any ideas?
Click to expand...
Click to collapse
I'm bout to factory reset with the nexus 7 toolkit, just for reference which link did you download from?
---------- Post added at 02:18 AM ---------- Previous post was at 01:51 AM ----------
Okay i was able to factory reset and got out of the bootloop. But I lost all my data(which is my fault for not making a backup to my pc). OP should really post the md5 so we can check it.

Dl'd via goo link, but used browser to access. Flashed via teamwin, wiped, profit. PA 2.14
sent secretly from my paranoid 7

[Q] 4.3 Update + TWRP

So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....

Carousser said:
So I have TWRP installed on my rooted Galaxy S3 (I535), and the 4.3 update just came out and was available to me.
I downloaded it, and tried to install it (I know that it will remove root), and when it finished downloading, it opened the TWRP boot menu.
Does anyone else who uses TWRP know how to install the new update? I couldn't find it and it wouldn't automatically install....
Click to expand...
Click to collapse
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery

ThePagel said:
If your OK with the locked bootloder (no more twrp) that comes with 4.3 flash the Odin file. If you want to ota there are links some place on this forum to flash stock recovery
Click to expand...
Click to collapse
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?

Carousser said:
Well I don't plan on using a custom ROM, I was using just the stock ROM + root. How do I do this?
Click to expand...
Click to collapse
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might

ThePagel said:
What way do you want to go Odin firmware will wipe internal sd card but it will be a nice clean install. Or ota after the stock recovery has been flashed through Odin but you might have weird bugs with ota... Might
Click to expand...
Click to collapse
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root

Carousser said:
I'd rather not wipe the internal SD card.. Isn't there just a way to install the update without all the hassle? I don't remember doing all this for rooting it... I'm fine with losing the root upon installing the new update as I can just root it again with safe root
Click to expand...
Click to collapse
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.

ThePagel said:
Find the. Stock recovery download it and flash through Odin. there are ways to do it through terminal but odin is the fastest to explain. After that you should beable to ota and keep your setup as is. It is odd that you cant ota I had twrp when i took the ota.
Click to expand...
Click to collapse
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.

Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Carousser said:
Well it just directs me to TWRP, and I have no idea where to go from there. I don't care about ever having TWRP again and I don't care about having a locked bootstrap, as I only need stock with root.
Click to expand...
Click to collapse
Oh your stuck on twrp can't boot up to usable state?

ThePagel said:
Never mind I was on stock recovery I forgot I was recovering from a soft brick when I decided to give it a shot.
---------- Post added at 03:26 PM ---------- Previous post was at 03:24 PM ----------
Oh your stuck on twrp can't boot up to usable state?
Click to expand...
Click to collapse
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it

Carousser said:
It goes to a screen with options such as Install, Wipe, Backup, Restore, etc....
I don't know where the ota is downloaded and thus cannot install it
Click to expand...
Click to collapse
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.

ThePagel said:
You kind of only have 2 options now. Attempt a "dirty" flash of a ROM so you can save your internal SD files then odin or do the full Odin wipe and forget about keeping the files. Either way unless anyone else has a idea you lose your current setup.
---------- Post added at 03:37 PM ---------- Previous post was at 03:33 PM ----------
I forgot the obvious. If you made a backup in twrp you can just recover with that.
Click to expand...
Click to collapse
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Edit-----
I found the zip file while browsing TWRP. Can I just install it?

Carousser said:
So let me get this straight.
There's no way for me to install the update unless I flash to another ROM? I don't see why I can;t just update and lose odin and TWRP or whatever
Click to expand...
Click to collapse
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of the 3 options I gave you are your only options.

ThePagel said:
OK I'll explain what I think went bad.when you downloaded the update it was expecting factory stock recovery to finish the install. Since you had twrp it failed. FYI Odin is a program on the PC to communicate with the phone in download mode (Odin mode). try to do a factory reset before you go crazy with my other suggestions. I have a feeling one of thoughs 3 options are your only options.
Click to expand...
Click to collapse
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible

Carousser said:
I found the zip file while browsing TWRP. Can I just install it? It said it was a flash and that it may be incompatible
Click to expand...
Click to collapse
Sure you can try tell me if it works

ThePagel said:
Sure you can try tell me if it works
Click to expand...
Click to collapse
Is there a chance of me bricking my phone?

Carousser said:
Is there a chance of me bricking my phone?
Click to expand...
Click to collapse
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.

ThePagel said:
Yeah but you already soft bricked it. Any brick you do you should be able to fix. just so you know you backed yourself into a corner. No matter what you do you have a chance of bricking. Its all part of being a power user. If your uncomfortable with that after you are on 4.3 you might not want to root.
Click to expand...
Click to collapse
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?

Carousser said:
Yeah I know there's always the chance of bricking, just wanted to know if that specific thing would do it. I've been into rooting since my Droid 1, Droid 2, and Droid X. But I'm always cautious.
If I do a factory reset and back up all my data, will it get rid of odin and TWRP and everything? Then just install the 4.3 update and root using safe root? Would that work?
Click to expand...
Click to collapse
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
---------- Post added at 05:37 PM ---------- Previous post was at 05:34 PM ----------
If you have backups of stuff on your internal sd it would be much faster to just Odin to 4.3 right now.

ThePagel said:
You would need to flash stock recovery completely replacing twrp. so if factory reset works and you can boot you should beable to flash stock recovery then redo the ota.
Click to expand...
Click to collapse
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x

Carousser said:
Is there a chance that doing a factory reset wouldn't flash it back? What else would I have to do? Sorry I haven't dealt with flashing since i had my droid x
Click to expand...
Click to collapse
Factory reset deals with the rom. So no it will stay twrp.
---------- Post added at 05:45 PM ---------- Previous post was at 05:40 PM ----------
Using Odin is a lot like SBF'ing on the droid x (that was my last phone also). So if you can remember installing cyanogen mod 6 or 7 you probably always did a factory reset before first boot. Custom recovery stays intact the only way to get rid of it was to flash stock recovery with terminal emulator or sbf back to pure stock. Luckily Odin let's us flash the recover by its self so we have more options with Samsung.

Nexus 5 with "TeamWin" failed update - and won't start again

Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!

Fablus said:
Hello everyone.
Two hours ago I received the notification about the Android 5.0 update. I downloaded it and hit "Install". Then, "TeamWin" started, but not the update. I rebooted into System and tried to update again - but it tells me that 4.4.4 is the latest version I can get now. I'm on Build KTU84P now.
1) Do I need to remove TeamWin? If yes, with what?
2) How can I start the update again? I'm on a super slow connection and it would hurt to download the 500 MB again…
Thank you!
Click to expand...
Click to collapse
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.

Mysticodex said:
You need to remove TeamWin, and load up your stock recovery. I don't have the exact instructions for this unfortunately.
The OTA update will come back to your phone soon, usually. Did for me within the hour.
The issue I am having now, back with stock recovery, is during the install I am getting a dead Android error icon, and can't continue. Looking for any help I can, and hopefully it will help you too.
Click to expand...
Click to collapse
Maybe we need http://forum.xda-developers.com/google-nexus-5/general/stock-checker-zip-prepare-ota-t2927865?
Gosh, this used to be so easy all the time.

if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.

simms22 said:
if you are using twrp, why the heck are you trying to install the ota? why not download(from xda) and flash a recovery flashable stock or aosp build, and make life much easier for yourself? heck, i dirty flashed from 444 to 5.0 via an aosp flashable zip without any issues, and kept all my data.
Click to expand...
Click to collapse
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
-Do a factory reset (maybe you can keep data coming from STOCK 4.4.4 - maybe)
Click to expand...
Click to collapse
And I didn't want to count on a maybe.

I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.

Fablus said:
I've read http://forum.xda-developers.com/goo...-android-4-4-3-ktu84m-rooted-busybox-t2557523 and it clearly states
Click to expand...
Click to collapse
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
Mysticodex said:
I'm using stock recovery, rooted as per normal, and a custom kernal. OTA is giving an Android dead error, with no text. Trying to figure out how to diagnose this.
Click to expand...
Click to collapse
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.

simms22 said:
it clearly states what? to use recovery version 2.8+? i used an older version, twrp version 2.6.2.4. what else?
---------- Post added at 05:51 PM ---------- Previous post was at 05:48 PM ----------
it wont flash over a rooted rom anymore as of lollipop. you can flash the factory img via fastboot though, in your bootloader.
Click to expand...
Click to collapse
Trying to remove the root right now via SuperSU. I am hopeful it will work better afterwards.
Edit: SuperSU unrooted it, rebooted, did OTA again, error again. Is there no way to find out what this error is?

[OTA] Official Marshmallow build MCG24.251-5

WARNING: THIS HAS BRICKED PHONES! It is suspected that having an encrypted phone causes these bricks, but that has not been confirmed. If your data partition is encrypted, it is extra important that you perform a factory reset before taking this OTA. Doing this will remove the encryption.
WARNING: INSTALLING THIS ON A LOCKED BOOTLOADER WILL ELIMINATE ALL CHANCE OF YOU EVER UNLOCKING YOUR BOOTLOADER.
If your bootloader is unlocked, it will not be re-locked after this update.
Do NOT flash this using TWRP. If you want to do that, use this version: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949
So if you're a bad enough dude to flash this anyway, follow these instructions:
1. Backup all data on your phone. It will be lost.
2. If your bootloader is locked, make sure you are on SU4TL-49. If you aren't, take all available OTAs until you are.
3. If your bootloader is unlocked and you have TWRP installed, flash SU4TL-49 using this package: https://mega.nz/#!3xRhiaSR!KxH2Ya_BYK4zBjrxmej7dqaaDJVT1coTFJVJ5Fvb2WM
4. If you have TWRP installed on your phone, download the stock SU4TL-49 recovery here: https://mega.nz/#!L1AkQD4T!qoZIlLa-wuUBLMEi_gE574meiHd6Pehb34a-x3Gb-V8 and install it using the install image option in the install menu in TWRP. Reboot to recovery.
3. Perform a factory reset using the stock recovery menu. This will wipe all data and ensure that everything is formatted exactly as it should be.
4. Boot the phone normally and place the marshmallow update on the root of the directory that pops up when you plug in your phone.
5. Boot to recovery and at the stock recovery menu, select "apply update from sdcard."
6. Select the update and cross your fingers.
Get the update here: https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8

TheSt33v said:
WARNING: THIS HAS BRICKED PHONES! Do not use this unless you know what you're doing.
I will do my best to provide more detailed instructions later today. Good luck.
https://mega.nz/#!v0pRwThS!Pz9xuOSPjiOMtjlORkFrZ_ok0GTKqCfGzi5KmbDpHQ8
Click to expand...
Click to collapse
Are you sure that that file is the right one? It has the same version number as su4tl-49.

zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
I'm positive. I seem to remember they did the same thing with SU4TL-49. The OTA was named after SU4TL-44 for some reason.

This is the stock recovery version, correct?

koftheworld said:
This is the stock recovery version, correct?
Click to expand...
Click to collapse
Correct. You install this using the sideload option in the stock recovery.

TheSt33v said:
Correct. You install this using the sideload option in the stock recovery.
Click to expand...
Click to collapse
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.

Thank you, now we can see what can be done with the new modem, kernel, etc...
Looking forward to a plethora of improvements to our phones

koftheworld said:
Thanks for the info and the download! You finally brought the wall down. I'm waiting for the twrp version myself
.
Click to expand...
Click to collapse
I'm testing the TWRP version now. It should be up shortly.
EDIT: I flashed it and it seems to work fine. Uploading now. Should be up in a few hours. I'll check on it after I go run some errands real quick.

Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
zys52712 said:
Are you sure that that file is the right one? It has the same version number as su4tl-49.
Click to expand...
Click to collapse
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.

Sweet. I am going to wait till it is more stable. I do have a bad esn Turbo but I will need to unlock to bootloader to test.

Mirror for people having "quota exceeded" error at Mega
https://yadi.sk/d/AhmhE-yX32E84p
Rename to Blur_Version.24.81.5.quark_verizon.verizon.en.US.zip before use, throw in internal storage, and check for updates.
PS: I have 64Gb Employee Edition, and still had not receive update by air. What a shame, VZ! )

kitcostantino said:
Despite having software status report official, not modified, I too got a status 7 error. Downloading again.
---------- Post added at 09:52 PM ---------- Previous post was at 09:51 PM ----------
This used to always be Motorola's naming scheme. New updates were named after the firmware version they replaced.
Click to expand...
Click to collapse
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.

TheSt33v said:
Error 7? Are you trying to flash this in TWRP? Because you can't do that with this package. You need the stock recovery. I'm uploading a TWRP-friendly version now, but the internet is being slow today.
Click to expand...
Click to collapse
Negative. Stock recovery on a system that reports "Official". I'm at a loss.

kitcostantino said:
Negative. Stock recovery on a system that reports "Official". I'm at a loss.
Click to expand...
Click to collapse
Strange. Try reflashing SU4TL-49. If my TWRP package doesn't do it for you, use the full firmware package and do it manually with fastboot.

Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"

s5610 said:
Installed successfully on two devices.
...
kitcostantino, did you refresh system, kernel, modem and recovery by SU4TL-49? Are you sure you didn't mess with Turbo Maxx ROMs in the past? Foreign bootloader can cause even brick, not just error. See bootloader status at fastboot mode should be " locked, status 0"
Click to expand...
Click to collapse
lol. lawd, No. Ive been rocking status 3 for over a year.
As a tip, if anyone else with an unlocked bootloader runs into this,
what i had to do was restore my su-44 unmodified backup, OTA to SU-49, and then, after confirming my
q/e status was 0/1 i was able to update via the file in my Mega download folder. all is well now. they even added the newer version of command center. sweet. thank you all!!

It works in LOCKED BOOTLOADER??? .-.

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Um, I couldn't tell you.i be been unlocked since the day Sunshine could unlocked our bootloader's. What I can tell you is you should absolutely unlock that via Sunshine before you even dream of applying this update. There will never be another opportunity.
Just my
.02. This is likely the last update for this phone, and your only chance of seeing N is via custom Roms.

TWRP version up now: http://forum.xda-developers.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949

square1230 said:
It works in LOCKED BOOTLOADER??? .-.
Click to expand...
Click to collapse
Yes it should. See instructions in OP.

Full Access ROOT

Hi there,
I tried to flash the patched boot.img and it bricked my phone, I managed to fix it by flashing the official boot.img. Now, I REALLY want full access root, so does someone know what needs to be altered in the boot.img for this to work? I want to alter my boot.img from my firmware.

Tigas001 said:
Hi there,
I tried to flash the patched boot.img and it bricked my phone, I managed to fix it by flashing the official boot.img. Now, I REALLY want full access root, so does someone know what needs to be altered in the boot.img for this to work? I want to alter my boot.img from my firmware.
Click to expand...
Click to collapse
Hey Tigas,
some users are able to get full root with this patched boot.img from this post:
raimondomartire said:
For kindly request in MAte 9 thread
https://www.androidfilehost.com/?fid=529152257862700042 ---> Patched Mate 9 image. Use only supersu.apk to see root (Don't flash any zip with supersu before)
https://www.androidfilehost.com/?fid=529152257862700052 ---> Clean mate 9 image to patch with my zip in first thread
Click to expand...
Click to collapse
Unfortunately, this method using SuperSU will break your fingerprint/PIN protection.
If you want to try, simply flash the patched img over the stock img (in TWRP) and install SuperSU from the Play store.

Tigas001 said:
Hi there,
[skipped]
Now, I REALLY want full access root...
Click to expand...
Click to collapse
Do you have option to restore your device in case of hardbrick? Obtaining full root on Mate 9 must be done with knowledge what are you doing and what tools are doing...

There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.

ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
Just to discuss.
Steps 2 and 3 can be merged, if using modified script changes.sh inside of superuser.zip.
Sure, flashing decrypted boot does not require clean stock boot, so we have right boot before installing superuser
But on other side there will be unexpected problems if we will use prepared boot.
I noticed that boot images are different by version. One has additional code to thermal sensors, other doesn't.

Hi also wanted to clarify that this boot image can be flashed on any regular mate 9 and any firmware. Or is it only for a specific version of mate 9 with the same firmware as the boot.img. Thanks for any advice
Sent from my MHA-L09 using XDA-Developers Legacy app

Hi just to update I followed the instructions by ajsmsp78 and gained full root and was able to install meefik busybox and also uninstall system apps which I couldn't do before. When I flashed the boot.img and superuser and booted up some of my apps were missing. I then flashed the public and hw zips for my region and most of them were back. I now have decrypted data and full root. Thanks a lot
Sent from my MHA-L09 using XDA-Developers Legacy app

ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse
so is that means we can backup n restore thru twrp??
---------- Post added at 03:11 PM ---------- Previous post was at 03:11 PM ----------
JATCHUHAN said:
Hi just to update I followed the instructions by ajsmsp78 and gained full root and was able to install meefik busybox and also uninstall system apps which I couldn't do before. When I flashed the boot.img and superuser and booted up some of my apps were missing. I then flashed the public and hw zips for my region and most of them were back. I now have decrypted data and full root. Thanks a lot
Click to expand...
Click to collapse
did you tried to back up n restore in twrp?

If I flash that boot.img it will brick my phone, I've tried it and had to flash the original boot.img as of now I have the phh superuser root. The flash method I used was fastboot and yes, I have my bootloader unlocked. Been rooting android phones for 5 - 6 years
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?

eddmecha said:
so is that means we can backup n restore thru twrp??
Click to expand...
Click to collapse
Yeah, you can. When you are formatting data, encryption is going off. Then need use modified boot to prevent encryption back.
---------- Post added at 06:00 PM ---------- Previous post was at 05:57 PM ----------
Tigas001 said:
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
Click to expand...
Click to collapse
Not really need. If you are interesting only root and writeable system, then don't format data.
Can't say anything about fingerprint sensor - I never used it.

I haven't tried backing up in twrp yet. Will do so later today. When I flashed the public and hw zips all my huawei apps came back but not the extra bloat like Facebook or todoist etc. Not to bothered as I don't need them. The only thing missing was the magazine lock wallpapers but I downloaded replacements from the theme app. All good now. Thanks
Sent from my MHA-L09 using XDA-Developers Legacy app
---------- Post added at 03:27 PM ---------- Previous post was at 03:17 PM ----------
Tigas001 said:
If I flash that boot.img it will brick my phone, I've tried it and had to flash the original boot.img as of now I have the phh superuser root. The flash method I used was fastboot and yes, I have my bootloader unlocked. Been rooting android phones for 5 - 6 years
Do I really need to wipe the data partition? Will the fingerprint sensor remain working?
Click to expand...
Click to collapse
I also flashed that boot.img previously and bricked my phone. However this time it worked, the only thing I did different was to wipe data in twrp. Don't know if this made any difference but it worked
Sent from my MHA-L09 using XDA-Developers Legacy app
---------- Post added at 03:35 PM ---------- Previous post was at 03:27 PM ----------
Sent from my MHA-L09 using XDA-Developers Legacy app

If you don't wipe data first to decrypt and then flssh the decrypted boot you'll probably end up in a bootloop. I'll have to make a decrypted boot thread with a few different boot images for those still on older systems (B112, B029 etc)

Thanks that would be great and very helpful to others
Sent from my MHA-L09 using XDA-Developers Legacy app

Someone state that one of the root methods broke the finger print scanner, does this method from @ajsmsg78 correct that issue? And is there any other side effects or "broke" items after the process?

phillymade said:
Someone state that one of the root methods broke the finger print scanner, does this method from @ajsmsg78 correct that issue? And is there any other side effects or "broke" items after the process?
Click to expand...
Click to collapse
Fingerprint works fine for me after rooting.

Have you tried android pay? TiBU works without issues? Any chance OTA updates could still work? Thanks.

For all models...?
Just to be clear; which model do you have? Would the boot.img work for all models? I have the AL00.
ajsmsg78 said:
There is full root. Here are the steps for the regular Mate 9
1) Download TWRP 3.0.2-2 from here and fastboot flash it:
https://www.androidfilehost.com/?fid=745425885120697579
2) Boot into TWRP (volume up+power) Go to Wipe, Format Data, then type in yes. Then reboot recovery.
3) Flash my decrypted boot.img from here:
https://www.androidfilehost.com/?w=files&flid=152685
4) Flash Superuser from here:
https://www.androidfilehost.com/?fid=817550096634746024
5) Boot up fully. Go into the Play Store and download PHH Superuser. Or you can download the newer beta here. Install it like any other apk:
https://www.androidfilehost.com/?fid=673368273298931027
6) Congratulations, you no longer are encrypted, twrp will see your internal storage and data properly and you have full root. Now do a backup of your current rom in TWRP.
Click to expand...
Click to collapse

xfive420 said:
Have you tried android pay? TiBU works without issues? Any chance OTA updates could still work? Thanks.
Click to expand...
Click to collapse
I don't use Android pay but the fingerprint scanner works fine so far for me after rooting. OTA should work fine but I need confirmation of it working by someone.
rbt001 said:
Just to be clear; which model do you have? Would the boot.img work for all models? I have the AL00.
Click to expand...
Click to collapse
I have the MHA-L29C567 US version. I made a boot image thread you can go to for a link to the different boot images.

5[Strogino] said:
Yeah, you can. When you are formatting data, encryption is going off. Then need use modified boot to prevent encryption back..
Click to expand...
Click to collapse
Are you saying that if you just flash superuser to gain root but do not decrypt, you can't do backups and restores with TiBU? And remove system apps? I was under the impression from another thread that decrypting was only necessary for TWRP data access, and would not prevent TiBU features from working.

deleted sorry wrong thread