Database Info

SAFE rooting to HUAWEI MATE 9

hi guys ,
I`ve read this thread https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986
my ask : Does this rooting goes well with MHA-L29C185B172 ?
if not , then how can i root my device SAFELY ?
thanks all

one, post, no experience with rooting android phones, do NOT root this phone unless there is some important reason to.
do ALOT more reading before you even think about rooting

Thx to reply. Like the others i wanna root to have root apps in my phone ,

Thx . Wanna have apps requires root in my phone . That simple

You don't even need to decrypt if you don't want to.
Unlock Developer Options (Settings - About: tap build number until it says it's enabled)
Go to the Developer Options and enable OEM Unlocking
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+

super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action

nawraz said:
super!!! , I did unlock the device and flashed twrp ,then tried install SU but failed , that made me afraid of bricking if i did further action
Click to expand...
Click to collapse
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.

ante0 said:
Original SuperSU 2.79 won't install. We have no loop support in kernel pre-B182. And even with support it doesn't install. The one I linked is a phh supersu hybrid. It uses phh su's method of installing, but installs SuperSU.
Click to expand...
Click to collapse
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!

I failed install su however still waiting for any updates

nawraz said:
I failed install su however still waiting for any updates
Click to expand...
Click to collapse
You flashed the one I linked? And which twrp do you use?

ante0 said:
You don't even need to decrypt if you don't want to.
Unlock bootloader
Flash twrp 3.1.0
Flash SuperSU no-decrypt (https://mega.nz/#!lkV0jbYJ!b1h-5uVksvpt7rw0tRHV7Qxjwk2xkKox0w-iRsCLlbU)
Have fun.
For decryption follow the decrypt guide.
To undo root and relock (Bootloader Locked) flash a stock firmware using the Force flash guide under Guides or use firmware finder).
For Magiskv12 root you need firmware B182+
Click to expand...
Click to collapse
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!

FootSlave said:
Just would like to say that it's not fair to say him that in case that the second entry said: One post on xda and he wants to root!
I think the problem is the order you gave him @ante0 (MAYBE!)
Unlock bootloader
flash TWRP
And I think he now has a BIG problem bc you DIDN'T said or forced him to go into developer settings and turn on OEM-unlock!
@nawraz did you turned on OEM-unlock in developer settings?
if you boot into fastboot mode are BOTH (bootloader and FRP = unlocked (in red letters), or and I really hoper NOT is FRP lock (in green letters)???
Maybe that is now the problem for him, not being able to flash SuperSU?
If you have luck @nawraz then try to flash TWRP 3.0.2-2 and with that SuperSU2.79
If you have root then you can install latest TWRP (3.1.0-1)
If you can't flash anything... oh oh!
Click to expand...
Click to collapse
He already unlocked and flashed twrp.
3.1.0 installs SuperSU fine. 3.0.3 does not.
And if oem was locked he wouldn't even be in twrp as you can't flash anything with fastboot if it is locked.
But I'll update my post in case anyone does miss to unlock oem.

Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk

FootSlave said:
Hope you don't get me wrong!
Just said that bc I had that problem 5 days ago and the only thing that helped was funky!
I had a softbrick and a reboot always kicked me into eRecovery
I just had eRecovery and fastboot!
Bootloader relocked and frp locked!
Stupid me relocked the bootloader bc I read that you then can unlock oem, then unlock bootloader again!
Well, that was a mistake!
Send from Huawei Mate 9 with Tapatalk
Click to expand...
Click to collapse
Yeah. Only way then would be to rebrand to C636 using the DLOAD method, then rebrand back to your stock version using the Update thread under Guides. The latter requires twrp though so you'd need to rebrand first to get a working system.
To be honest I just figured he had already unlocked and flashed twrp as he was in the decrypt thread
Missing oem was an error on my side. It was long since I had to unlock oem xD

ante0 said:
You flashed the one I linked? And which twrp do you use?
Click to expand...
Click to collapse
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310

nawraz said:
hi , i used twrp-3.0.2-2 successfully and failed with superuser-r310
Click to expand...
Click to collapse
Weird. I tested with 3.1.0 a few days ago. But I guess it could have to do with builds. 3.1.0 is using kernel for B182. Maybe it's fixed if you use 3.1.0 with B182.
Oh well, good you managed to install it anyway.
Edit: I tested with the SuperSU I linked.

mscion said:
Hi. I just happen to come across your post and noticed you said that there is no loop support pre-B182. I have the Chinese version with B213. Some apps, like Linux on Android need, unless something has changed, loop support as well as root. Do you have a reference or a link about the loop support on this phone? Thanks!
Click to expand...
Click to collapse
All I know is that it wasn't present in builds before B182.
 @st_voss is the one who found out it was added in B182 (Kernel build April. 11th probably as that's what I have on B182.).
It might be present in B181 on C636 as well, that was released 8th of May.

mr. ante0 ..... u r the man , thank you so much

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

thank you guys i finally rooted my mate 9 safely ,,,,, thanks n credits to ante0

Vernee Mars Pro blocked in TWRP

20 days ago i rooted my phone using this thread : https://forum.xda-developers.com/general/security/vernee-mars-pro-t3632162
Today i deceided to check if there was system update : 1 found . I started it but during the reboot , TWRP show up and i can't exit it , i tried to reboot multiple times but i am still blocked with twrp during the boot .
Anyone got a solution ? Any help be much appreciated .

Elixar05 said:
20 days ago i rooted my phone using this thread : https://forum.xda-developers.com/general/security/vernee-mars-pro-t3632162
Today i deceided to check if there was system update : 1 found . I started it but during the reboot , TWRP show up and i can't exit it , i tried to reboot multiple times but i am still blocked with twrp during the boot .
Anyone got a solution ? Any help be much appreciated .
Click to expand...
Click to collapse
You can't apply stock OTA updates on a device that is rooted or has TWRP installed. That's why it started fine but went stupid when it went it tried to boot to recovery, it didn't find stock recovery, it found TWRP, the update isn't compatible with TWRP so it couldn't flash it, now you're stuck because it doesn't know what to do.
OTA updates require the device to be unrooted and must have stock recovery.
You will have to flash your stock firmware via PC using your devices flashtool.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE

Droidriven said:
You can't apply stock OTA updates on a device that is rooted or has TWRP installed. That's why it started fine but went stupid when it went it tried to boot to recovery, it didn't find stock recovery, it found TWRP, the update isn't compatible with TWRP so it couldn't flash it, now you're stuck because it doesn't know what to do.
OTA updates require the device to be unrooted and must have stock recovery.
You will have to flash your stock firmware via PC using your devices flashtool.
DO NOT CONTACT ME VIA PM TO RECEIVE HELP, YOU WILL BE IGNORED. KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
I already finded the solution but thank you anyway .

Can't Update renovate firmware

Hey guys,
Hopefully someone can help me with my problem. So i did the following:
To get rid of the 7 day Block of oem-unlocking on my s8+ i downgraded back to Nougat. From here on I flashed TWRP + rooted my device with magisk. After That i flashed the RENOVATE_ICE_G95X-7.5 rom + the Flashable_G95xF_FD_Firmware_TWRP_AQL5_r8 Firmware. I've let my Phone start up and went back to TWRP To Update the rom to RENOVATE_ICE_G95X-10.1. To this point everything Worked fine, the Phone Boots completely fine. Now to my problem: im Sitting on the actual stable rom but with the Baseband-version of Nougat which is AQL5. When i try to Flash the actual Firmware (CRC7 or CRD7) via TWRP my Phone gets stuck on the first Samsung Logo and Shows the following red Message: "Only official released binaries are allowed to be flashed". I would be glad for any help.

If you can find a standalone modem file from the ROM you mentioned you should be able to flash it in TWRP recovery. Last time I did this was on a Note 3. I think that the process should be the same with S8.

Can't seem to find one, but i found out that the same error occurs when installing other custom-roms like the King Oreo Rom which installs the newest Bootloader and Modem via Aroma installer. Only solution after that is to Flash Nougat again via Odin.

[Solved]"only official released binaries are allowed to be flashed" (CRi9)

Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
1. Changed the date of the date of the phone and went to "update firmware" and then reset to get OEM unlocked
2. Went to download mode and flashed succesfully TWRP.
3. In TWRP I formated data (yes) and rebooted into recovery
4. Flashed the following files: a) Magisk, b) No verify 6.0, c) RMM state bypass Mesa, d)samsung anti-root removal 4.1
5. Rebooted into system
Click to expand...
Click to collapse
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?

josegon30 said:
Hi all, thanks in advance for reading me.
I have this model:
S8+ (SM-G955FD) with the last firmware from sammobile G955FXXU4CRJ5
When I flashed that firmware with ODIN I wanted to root, so this is what I did:
After doing that, everything seems to be OK... I can re-config my phone and Magisk Manager is installed. But when I went to Developer options I can't see "OEM unlock" activated. So, when I rebooted I got the "only official released binaries are allowed to be flashed" error.
I made the procedure several times. Is that related to the "October security patch update"? I think the error is due to a failure in RMM state bypass flashing, although the flashing procedure says "OK. Done".
Anyone have the same issue? do you guys know how to fix it?
Click to expand...
Click to collapse
More than likely RMM state zip didn't work are you using the version 2 zip and did you allow modifications in twrp before flashing zip files.

@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.

josegon30 said:
@spawnlives; thanks for your repply, I guess that was part of the solution. What I did was to flash a custom kernel plus RMM state bypass v2. I read a custom kernel could fix my problem.
Now I have my phone rooted and with OEM unlock enlabed.
Click to expand...
Click to collapse
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....

Johnny™ said:
what kernel did you use? i have the same issue. i cant reboot on unlocking as i get the dreaded only official binary....
Click to expand...
Click to collapse
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).

thanks im really struggling, im on the 11th try, every time is just gives me only official bineries.... , ive tried several methods, all root nicely but wont reboot.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
i cant find the v2 its coming up as 4k where v1 is 100k?

josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!

Johnny™ said:
let me buy you a beer! got it working thanks, the V2 did the trick. I used your kernel as well just in case. no more nasty red message!
Click to expand...
Click to collapse
:good: I´m glad it worked.

josegon30 said:
I used Velocity Kernel.
Just follow the steps: 1. flash twrp; 2. factory reset and reboot recovery; 3. flask kernel; 4. flash magisk; 5. flash no verify; 6. flash rmm bypass (v2, not v1).
Click to expand...
Click to collapse
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...

nasko7 said:
Okay, that's great and all but I can't even do the first step because every time I'm in Download mode and try to flash TWRP with Odin, it says "Only official released binaries are allowed to be flashed (RECOVERY). I have triggered Knox security but I can't undo it now, so I can fix the RMM state with the bypasser because I can't even flash TWRP. It was suggested to change the date to another one, prior to the security patches, but that didn't work. Sad times...
Click to expand...
Click to collapse
Depending on .android version, you will need to have the following coditions to be able to flash non signed samsung firmware eg: twrp,root, custom roms etc.
In system - OEM unlocked
Download mode -
RMM status - normal ( or disappeared )
KG status - checking
Otherwise you will get errors

Can only install official binaries message when flashing TWRP with Odin3 on A750FN U4

Hi, I'm having a lot of trouble trying to install a custom recovery. I had it working a couple months back but wanted to go with official again for dumb reasons and now i want to go back but it won't let me flash TWRP, i can't find a TWRP specifically for this version either. It's Android 10 with March security patch.
I hope someone can help me.
Thanks.

Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.

Didgeridoohan said:
Please only create one thread per topic. I've removed the duplicate thread you started on this topic.
As far as your issue goes, I don't actually know much about Samsung specifics, but I believe that particular message means you haven't unlocked your bootloader. You'll need to do that before you can flash custom stuff.
Click to expand...
Click to collapse
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.

Parthiv Shaji said:
actually Im also having the same problem even though i have unlocked my bootloader.. I had previously installed twrp and was trying custom os until one os (evolution x) for some bricked my phone and i had to flash the stock firmware and after that when i try to re-flash twrp through odin it is saying officail binary can be flashed.
Click to expand...
Click to collapse
Like I said, I'm not 100% on Samsung shenannigans, but have you checked to verify that you didn't lock the bootloader as a part of flashing the stock firmware?

OEM unlock toggle in Developer's Options

Hi ¡...
1. You have to reinstall via odin the latest version 9 (AP, BL...etc)
2. On reboot do the entire TWPR flashing process for android 9
The current problem is that there is no TWPR for android 10.
Cheers