[ROOT][Android 7.0][EMUI 5.0]SuperSU 2.82 for EMUI 5

[zgfg]

I have L09 c432 b393 robtained by OTA, ooted by SuperSU-v2.82-EMUI5-SELPermissive.zip

I've received OTA b394 System Update notificatoon, how to proceed:
- unroot from SuperSU
- flash stock b393 Boot IMG from TWRP
- flash stock b393 recovery IMG from Fastboot
- let it do OTA System Update?

 

[Tecalote]

I have L09 c432 b393 robtained by OTA, ooted by SuperSU-v2.82-EMUI5-SELPermissive.zip

I've received OTA b394 System Update notificatoon, how to proceed:
- unroot from SuperSU
- flash stock b393 Boot IMG from TWRP
- flash stock b393 recovery IMG from Fastboot
- let it do OTA System Update?

Backup your Apps and stuff before you do so.
After you have flashed Stock Recovery you should do wipe cache and Factoryreset from Stock Recovery.
If you go then into system update in settings, open the menu inside above and choose Full Package OTA, perhaps 2,4 GB.
If you let install only 600 MB or less OTA, it may cannot be installed successfully.

If you are then on b394 it's fine and you can try my new Rom which is based on b394.

It will be ready end of this week and will be tested during next week and officially come out after next week perhaps on Sunday next week.

 

[zgfg]

Backup your Apps and stuff before you do so.
After you have flashed Stock Recovery you should do wipe cache and Factoryreset from Stock Recovery.
If you go then into system update in settings, open the menu inside above and choose Full Package OTA, perhaps 2,4 GB.
If you let install only 600 MB or less OTA, it may cannot be installed successfully.

If you are then on b394 it's fine and you can try my new Rom which is based on b394.

It will be ready end of this week and will be tested during next week and officially come out after next week perhaps on Sunday next week.

HiSuite backup (even TWRP, just in case, plus VCard contacts backup) is supposed, as well as additionally forcing Google and WhatsApp syncing.

I also always disable lock-screen PIN and firgerprint, and re-enable system apps like SwiftKey and Swipe for Huawei before upgrading.

And yes, I also planned to force Full Backup.

Edit: Done everything as described, successfully updated to OTA b394

I did Hard Reset (just in case) as you suggested, although I believe it would work without.

And I used Backup/Restore app - seems, it preserves more Settings than HiSuite.
Still, I have to manually re-apply many settings lost in Hard Reset ;(

Nevertheless, I'm having now clean b394 and looking forward for Magic Rainbow v3

 

[netaccs]

Which version should work on 394?
I try severals super su. Root checker says:
Sorry, root access is not properly installed.

 

[Tecalote]

Which version should work on 394?
I try severals super su. Root checker says:
Sorry, root access is not properly installed.

P9 b394 you can root with official SuperSU SR5
http://download.chainfire.eu/1220/SuperSU/SR5-SuperSU-v2.82-SR5-20171001224502.zip
Download from this website

 

[netaccs]

I try it - same result. Root checker says -> Sorry, root access is not properly installed on this device.
Try second time - same result. TWRP is 3.1.1 open kirin.
Any idea ?

After every super su installed from recovery there was one loop, then boots normally.

One more thing. After I made the upgrade to 394 install twrp 3.1.1.1 and I am not sure,but may be supersu 2.79 and it was working.
Unfortunately I delete the .zip and don't remember which version was.

I think that something else is wrong, cause I already try several version of supersu.
Should I use another recovery or may be flash again ?

 

[zgfg]

I try it - same result. Root checker says -> Sorry, root access is not properly installed on this device.
Try second time - same result. TWRP is 3.1.1 open kirin.
Any idea ?

After every super su installed from recovery there was one loop, then boots normally.

One more thing. After I made the upgrade to 394 install twrp 3.1.1.1 and I am not sure,but may be supersu 2.79 and it was working.
Unfortunately I delete the .zip and don't remember which version was.

I think that something else is wrong, cause I already try several version of supersu.
Should I use another recovery or may be flash again ?

Recovery must be
https://forum.xda-developers.com/p9/development/twrp-t3565703

but if you spoiled system, you should restore from the clean b394 nandroid backup (before you tried rooting, hopefully you made TWRP backup then?)

Or at least, flash from TWRP clean/stock boot partition (again, you hopefully backed it up before tried to root)

---------- Post added at 05:45 PM ---------- Previous post was at 05:24 PM ----------

I try it - same result. Root checker says -> Sorry, root access is not properly installed on this device.
Try second time - same result. TWRP is 3.1.1 open kirin.
Any idea ?

After every super su installed from recovery there was one loop, then boots normally.

One more thing. After I made the upgrade to 394 install twrp 3.1.1.1 and I am not sure,but may be supersu 2.79 and it was working.
Unfortunately I delete the .zip and don't remember which version was.

I think that something else is wrong, cause I already try several version of supersu.
Should I use another recovery or may be flash again ?

Recovery must be
https://forum.xda-developers.com/p9/development/twrp-t3565703

but if you spoiled system, you should restore from the clean b394 nandroid backup (before you tried rooting, hopefully you made TWRP backup then?)

Or at least, flash from TWRP clean/stock boot partition (again, you hopefully backed it up before tried to root)

 

[netaccs]

No, I don't have any backups of partition.
Yes, this is the recovery. Can I reflash it again or should flash with nonstop recovery and than with twrp ?

 

[zgfg]

No, I don't have any backups of partition.
Yes, this is the recovery. Can I reflash it again or should flash with nonstop recovery and than with twrp ?

Since b394 is Approved, no difference if you use no-check or stock b394 recovery

But how do you mean to reinstall b394 - you would need stock or no-check recovery and stock boot partition

Besides, it is not PV version to be installedl by DLOAD, you can only go for DNS or Proxy trick in FirmwareFinder or via rollback to MM, then back through OTA upgrades

You can try the following
- flash from TWRP the stock b394 boot partition
- try rooting again (2.82 Permissive from this thread, OP post #1, worked for me on b393 and IMO must also for b394)

You can find stock recovery b394 (for flashing from fastboot) and b394 boot stock partition (for restoring from TWRP), as well as complete b394 FullOTA download, 2.82 Permissive SuperSU zip, etc, on my Mega (you can open in browser and browse/download)
https://mega.nz/#F!w41RmZKB!IG53JadhjUKgFK8anbctIw

 

[netaccs]

No, I don't want to flash 394 again. Want to have root and recovery on my p9 nougat b394, what I should do?
If flash with stock boot 394, how to enter in recovery and flash with supersu?

 

[Tecalote]

No, I don't want to flash 394 again. Want to have root and recovery on my p9 nougat b394, what I should do?
If flash with stock boot 394, how to enter in recovery and flash with supersu?

I write you after work in later evening (Germany), I am busy at the moment

 

[Tecalote]

No, I don't want to flash 394 again. Want to have root and recovery on my p9 nougat b394, what I should do?
If flash with stock boot 394, how to enter in recovery and flash with supersu?

First at all:
Flash unsu.zip with TWRP: https://forum.xda-developers.com/showpost.php?p=63615067
After restore original boot.img from b394 - if you dont have, take it from here: https://www.androidfilehost.com/?fid=889964283620771919
Flash boot.img by choosing img (right down) and flash it to: boot
Then go to Wipe in TWRP but Advanced Wipe and Wipe Dalvik/Cache and Cache only. Reboot your phone.
Now start again to TWRP and flash this version of SuperSU, which is attached.
Its SuperSU 2.82 SR5 - but with some goodies.
And after flashing SuperSU - DONT wipe Dalvik/cache - just reboot your phone (it will boot up twice) - wait until it is rebooted.
Check your Homescreen - you should find anywhere SuperSU (apk) to manage your Root. Open it and if theres no error, you have already Root. You dont need any root checker to know that.

 

[netaccs]

I made this
1. twrp -> flash -> UPDATE-unSU-signed.zip
2. restore original boot.img b394
fastboot flash boot L09-b394-BOOT.img
fastbook reboot
3. twrp -> advanced Wipe -> Wipe Dalvik/Cache and Cache only - reboot
4. twrp -> flash > SuperSU-v2.82-SR5-permissive.zip (no cleaning caches or else, never did before anyway)

Still su not working. Adaway is stucking at home screee, ES File manager has no root explorer, terminal cannot make "su"

:/ :/

 

[Tecalote]

I made this
1. twrp -> flash -> UPDATE-unSU-signed.zip
2. restore original boot.img b394
fastboot flash boot L09-b394-BOOT.img
fastbook reboot
3. twrp -> advanced Wipe -> Wipe Dalvik/Cache and Cache only - reboot
4. twrp -> flash > SuperSU-v2.82-SR5-permissive.zip (no cleaning caches or else, never did before anyway)

Still su not working. Adaway is stucking at home screee, ES File manager has no root explorer, terminal cannot make "su"

:/ :/

Have you opened SuperSU apk - what does it show?
For working Root properly you need also Busybox.
Search for Busybox by osm0sis on xda.
I have rooted b394 with this SuperSU without any problem

 

[netaccs]

https://www.dropbox.com/sh/hx1r1dazmb8xq89/AADu4DfmK_6-JbcYcHnUVvtba?dl=0
There some photos. Last time when I has root and busybox I make some mount -ro /system or something similar.

I will try busybox flashable by osm0sis.

Edit.
Flash it via twrp, flashing was successful, but after reboot, no busybox app on the phone, root still failing.

May be have other issues - kernel, twrp or else.
I had twr+root, than unroot and flash recovery with nocheck.... img.
Somehow bootloader was locked.
Unlocked again, twrp and supersu, but.... have no luck.

Can I try with another root solution, is there any working?

 

[Tecalote]

https://www.dropbox.com/sh/hx1r1dazmb8xq89/AADu4DfmK_6-JbcYcHnUVvtba?dl=0
There some photos. Last time when I has root and busybox I make some mount -ro /system or something similar.

I will try busybox flashable by osm0sis.

Edit.
Flash it via twrp, flashing was successful, but after reboot, no busybox app on the phone, root still failing.

May be have other issues - kernel, twrp or else.
I had twr+root, than unroot and flash recovery with nocheck.... img.
Somehow bootloader was locked.
Unlocked again, twrp and supersu, but.... have no luck.

Can I try with another root solution, is there any working?

Yes, you can try Magisk 14.5 Beta. I recommend this, its working very well (but not stable v14)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

And here are some additional tips:
https://forum.xda-developers.com/showpost.php?p=74265463&postcount=768

 

[netaccs]

Magisk got error in the beginning of flashing.
Will try to make supersu. Any idea what else to try?
Some other version, another recovery, some clean wipe, logs, I can record steps of flashing.

 

[Tecalote]

Magisk got error in the beginning of flashing.
Will try to make supersu. Any idea what else to try?
Some other version, another recovery, some clean wipe, logs, I can record steps of flashing.

It seems to me like your Firmware has some kind of softbrick.
This can be happen if you made faults and then try several time different things.
Normally, if you choose from beginning the right version of SuperSU or Magisk, both would work.

What I would do in your case is to flash Stock Recovery for b394 and then do a complete Factoryreset with and Wipe Cache Partition with Stock Recovery.
I would watch if the Firmware works as it should for one or two days.
If yes you can flash TWRP 3.1.1-1 from OldDroid again and flash SuperSU 2.82 SR5 from my attachment.
There's no reason why it should not work - if your Firmware is clean.
But if the Firmware has some bugs, I would make a Downgrade to Android 6 with Stock Recovery and b300 Transition Pack.
After you must flash b182 with dload method. Your Bootloader become closed.
You will get OTA to Android 7 (b383, b386, b391, b393, b394)
Maybe there's another Factoryreset required then to receive the latest OTA.
Then you can open Bootloader again. You have clean Firmware after and with this SuperSU and Magisk both will work.

 

[XcyiouS]

Got it

 

[zgfg]

Hi, I'm new to rooting Huawei P9 and I can't seem to find the adb toolkit or something with the fastboot file to unlock my boot loader. Can someone send me a link to it or the file? Thanks!

For ADB toolkit, use Minimal ADB (smallest, fastest to download and install):
https://forum.xda-developers.com/showthread.php?t=2317790

For unlocking the bootloader, search on XDA and you will find many threads about (doesn't matter if they refer to P9, P9 Lite, etc, it's the same procedure).

In short, you must obtain unlocking code for your IMEI and S/N. You must enable Developer Options on the phone, and inside enable USB Debugging and OEM Unlocking. By ADB and Fastboot you will unlock the bootloader - it will make Factory Reset hence backup your apps and contacts by HiSuite before (and restore afterwards).

For the unlocking code, see e.g.
https://forum.xda-developers.com/wiki/Huawei_Unlocking_Bootloader
https://forum.xda-developers.com/hu.../guide-unlock-bootloader-root-huawei-t3632260 - Part 1

You can use the following batch file to unlock bootloader:
adb devices
PAUSE
adb reboot-bootloader
PAUSE
fastboot devices
PAUSE
fastboot oem unlock <your_unlocking_code>

The above procedure is completely free, but some
prefer to pay few bucks and unlock by DC Unlocker.
However, you will need ADB/Fastboot later for flashing TWRP anyway, hence I don't see an advantage in using the 'easier' DC Unlocker tool.