Database Develop

Flashable L09C432B378

Does anyone know how to flash untouched stock L09C432B378 with TWRP ?

You do need to have an unlocked bootloader, then you can enter fastboot mode and flash TWRP.
You can flash the full OTA again in case something goes wrong and this does also restore the bootloader lock.
Or do you mean to flash the firmware in TWRP?

christopherpfister said:
You do need to have an unlocked bootloader, then you can enter fastboot mode and flash TWRP.
You can flash the full OTA again in case something goes wrong and this does also restore the bootloader lock.
Or do you mean to flash the firmware in TWRP?
Click to expand...
Click to collapse
The phone has a material problem that need to be returned for service, I want to flash a full stock ROM with all the bloatware.
Could you point me to the full OTA download ?

lapocompris said:
The phone has a material problem that need to be returned for service, I want to flash a full stock ROM with all the bloatware.
Could you point me to the full OTA download ?
Click to expand...
Click to collapse
Here you can find any firmware for the EVA-L09 to download. You need to extract the content to a "dload"-folder on your sdcard and start the install by booting with Vol+ & Vol- pressed.

christopherpfister said:
Here you can find any firmware for the EVA-L09 to download. You need to extract the content to a "dload"-folder on your sdcard and start the install by booting with Vol+ & Vol- pressed.
Click to expand...
Click to collapse
I am currently on MaHo_66's ROM with TWRP, will this fail to flash ?

lapocompris said:
I am currently on MaHo_66's ROM with TWRP, will this fail to flash ?
Click to expand...
Click to collapse
No this should work in any state your device is in regarding what's installed/flashed except​ when your battery is low.
But consider that it will also restore recovery/boot partitions and the bootloader in general.

christopherpfister said:
No this should work in any state your device is in regarding what's installed/flashed except​ when your battery is low.
But consider that it will also restore recovery/boot partitions and the bootloader in general.
Click to expand...
Click to collapse
I downloaded the EVA-L09C432B378.zip and did as you said, but the installation failed (incompatible package)

lapocompris said:
I downloaded the EVA-L09C432B378.zip and did as you said, but the installation failed (incompatible package)
Click to expand...
Click to collapse
Are you sure you have extracted the contents of the zip to a folder called dload on the root of your sdcard and your battery is not low? You can also check the guides to this method in this forum.
It also depends on what firmware you are using now but if you already are on b378 it should definitely work fine.

christopherpfister said:
Are you sure you have extracted the contents of the zip to a folder called dload on the root of your sdcard and your battery is not low? You can also check the guides to this method in this forum.
It also depends on what firmware you are using now but if you already are on b378 it should definitely work fine.
Click to expand...
Click to collapse
Since my phone is unlocked and has TWRP, maybe that the problem.
So I flash oeminfo-huawei-p9-eval09-c432.zip, then the process work but upon reboot a lot of stock app are missing, including camera, folder and backup. And there is no keyboard.

I am not entirely sure but I think these are located on the /vendor partition. But I always thought that they were part of the full OTA. Maybe you can try to find and flash the stock vendor partition?
Sent from my Huawei P9 using XDA Labs

You'll have to flash update_full_hw_eu.zip as well.
Extract it and put that update.app in the dload folder. Where did you download firmware from?
Seems you must flash hw in twrp. no other way.
EVA-L09C432B378 FullOTA-MF: http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v75049/f1/full/update.zip
EVA-L09C432B378 update_full_hw_eu: http://update.hicloud.com:8180/TDS/...04/v75049/f1/full/hw/eu/update_full_hw_eu.zip
I don't think Public is needed, it contains no update.app anyway and would need to be flashed in TWRP.
christopherpfister said:
I am not entirely sure but I think these are located on the /vendor partition. But I always thought that they were part of the full OTA. Maybe you can try to find and flash the stock vendor partition?
Sent from my Huawei P9 using XDA Labs
Click to expand...
Click to collapse
It's downloaded separately when you update, but not with dload.

Root Huawei P10, P10+

Everything you do with the device, you do at your own peril and risk.
An unlocked bootloader is required, and the factory unlock is enabled.
1. Install TWRP
2. Install SuperRoot_noverity_nocrypt.zip through TWRP
3. Boot the system.
4. You need to install the APK from PlayStore afterwards https://play.google.com/store/apps/details?id=me.phh.superuser
Now you have root access and full access to the system partitions.
Enjoy Root
If an error "Error 1" is output with the firmware in TWRP. It is necessary to replace BOOT.img, on BOOT.img, from the firmware that you installed before obtaining root access.
Code:
fastboot flash boot boot.img
Acknowledgments:
https://forum.xda-developers.com/p10/development/testers-twrp-t3585256
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Additional materials that can help with troubleshooting. (Here you will find firmware from Huawei.)
The firmware for VTR
The firmware for VKY
SuperRoot_noverity_nocrypt.zip

Entering recovery?
yury_z said:
An unlocked bootloader is required, and the factory unlock is enabled.
1. Install TWRP
2. Install SuperRoot_noverity_nocrypt.zip
3. Download the device.
4. You need to install the APK from PlayStore afterwards https://play.google.com/store/apps/details?id=me.phh.superuser
5. All of you got Root + disabling the protection of system partitions for writing.
Enjoy Root
If an error "Error 1" is output with the firmware in TWRP. It is required to override BOOT.img on BOOT.img from the firmware.
Code:
fastboot flash boot boot.img
Acknowledgments:
https://forum.xda-developers.com/p10/development/testers-twrp-t3585256
https://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Boot_VTR-L29C10B120
Recovery_VTR-L29C10B120
SuperRoot_noverity_nocrypt.zip
Click to expand...
Click to collapse
How do you enter recovery on P10? It throws out that warning when you press "-" together with power on button. and then boots as normal.

Jaunpetrovics said:
How do you enter recovery on P10? It throws out that warning when you press "-" together with power on button. and then boots as normal.
Click to expand...
Click to collapse
power on button and "+"

Where to copy root .zip?
yury_z said:
power on button and "+"
Click to expand...
Click to collapse
And where to copy root .zip file? When I press Install, I can't seem to see the file, because it's not there and all the normal files except folders seem to be encrypted.. I pasted it in the main view. Where can I find it?

Jaunpetrovics said:
And where to copy root .zip file? When I press Install, I can't seem to see the file, because it's not there and all the normal files except folders seem to be encrypted.. I pasted it in the main view. Where can I find it?
Click to expand...
Click to collapse
Put on the microSD card, below the button select the media.

@yury_z i get an error while installing the zip in twrp. I think is the same error that you said.
I have installed VTR-L09C432B123
What can i do?
Will Boot_VTR-L29C10B120 working in my device?
Thanks

TheBigCatTheory said:
@yury_z i get an error while installing the zip in twrp. I think is the same error that you said.
I have installed VTR-L09C432B123
Thanks
Click to expand...
Click to collapse
BOOT_VTR-L29C432B123

SuperSU
Is possible flash classic SuperSU?

matata86 said:
Is possible flash classic SuperSU?
Click to expand...
Click to collapse
No SuperSU can not get root access on the Huawei P10.
I've tried many ways. Got only a recovery device.
If you disable SELinux, for example, through SELinuxModeChanger. We have full access without SuperSU.

Sorry I'm an old iOS user.
What do you mine by this step : "Download the device."
I checked with "Root checker" I'm now rooted, but I did'nt use these file : "Boot_VTR-L29C10B120 and
Recovery_VTR-L29C10B120" Is it normal ?
Thanks

larecrue said:
I checked with "Root checker" I'm now rooted, but I did'nt use these file : "Boot_VTR-L29C10B120 and
Recovery_VTR-L29C10B120" Is it normal ?
Thanks
Click to expand...
Click to collapse
They are needed to correct mistakes. If you get root access, then you do not need them.

Ok thanks for reply, now I'm rooted, no need custom ROM ? Sombody know the best way to transfert data from iOS to android (sms...)

I already rooted my VTR-L09C432B113 but want to decrypt and unlock the file system. Any solutions? Don't want to flash your boot.img for other device brand.

Did i lose some feature if i root P10? For example if i root my Sony Xperia i'll lose some camera and display technology if i don't backup some files. Thanks in advance.

SebastianAlejandro said:
Did i lose some feature if i root P10? For example if i root my Sony Xperia i'll lose some camera and display technology if i don't backup some files. Thanks in advance.
Click to expand...
Click to collapse
I'm on phh Supersu and didn't lose anything or got malfunction.
EDIT:
Unlocked filesystem is working for me now. I tested it with AdAway - the Hosts file stays after reboot.
If you need the boot.img of VTR-L09C432B113, klick here (extracted from original update.app).

Jannomag said:
I already rooted my VTR-L09C432B113 but want to decrypt and unlock the file system. Any solutions? Don't want to flash your boot.img for other device brand.
Click to expand...
Click to collapse
Install your VTR-L09C432B113 boot.img, then again get the final access using SuperRoot_noverity_nocrypt.zip.
P.S. VTR-L09C432B123 = VTR-L09C432B113 - Bootloaders are the same.

It worked! Thank you. I'm a newby, and managed to do this. If there is any questions - feel free to ask!

Does this work for VTR-AL00?
I just recently got mine from China

xZhongCheng said:
Does this work for VTR-AL00?
I just recently got mine from China
Click to expand...
Click to collapse
TWRP is needed for the Chinese location VTR-AL00. The rest (item 2) is suitable.

yury_z said:
Install your VTR-L09C432B113 boot.img, then again get the final access using SuperRoot_noverity_nocrypt.zip.
P.S. VTR-L09C432B123 = VTR-L09C432B113 - Bootloaders are the same.
Click to expand...
Click to collapse
What about VTR-L09C109B100? Is it safe to follow this method? Thank you!

How to install MAGISC without TWRP and locked bootloader?

Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk

Not to hijack your thread, so consider this a free bump, but I am also curious. Galaxy S7 G920T here and looking for the same options.

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Sent from my Redmi 2 using Tapatalk

fake2die said:
1 answer,,u can't..
Systemless mean that's it's doesn't messed with system partition so u can get the OTA update..
Or some app that detec change from system partition then refuse too work..
And to do that u need to flash TWRP and unlocked bootloader..
Click to expand...
Click to collapse
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.

veez21 said:
Not completely accurate. Magisk modifies boot.img (boot partition) and to modify it, you need to have an unlocked bootloader.
Click to expand...
Click to collapse
Right! So you can accomplish a Magisk install without a custom recovery for example using the Magisk Manager or Flashfire but as stated above, in order to boot a modified boot.img the bootloader needs to be unlocked or otherwise it will refuse to boot it.

There should be an option to install magisc like a systeme update with the stock recovery.
Gesendet von meinem XT1650 mit Tapatalk

JRapsky said:
There should be an option to install magisc like a systeme update with the stock recovery.
Click to expand...
Click to collapse
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.

Sytis said:
I don't think you understand how Android works, there are several stages to the system in which the actual /system rests. Basically everything is signed and validated to guarantee the installation of the official software and to protect the phone. Even if you can install Magisk via the stock recovery (which would require a phone specific Magisk which is the opposite of the universal interface that topjohnwu is targeting) you won't be able to boot the phone because the /boot partition is altered and the verity function won't allow an altered image to load in order to protect the phone. So in order to load the changes Magisk makes, the bootloader which checks and loads the boot.img (that's why it's called boot-loader) needs to be unlocked so it boots everything (the new boot.img needs to be compatible of course, you cannot boot the S8 img on the G6 for example). If I missed anything or something is wrong please correct me.
Click to expand...
Click to collapse
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?

COOLPLAY6FAN said:
but can we could not flash magisk file useing pc instead of custom recovery??(with unlock bootloder) if no then Y?
Click to expand...
Click to collapse
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Actually you can boot into twrp rather than install/flash twrp which means u must use cmd to boot twrp everytime for flashing something~ As for locked bootloader, just like others said, you must unlock it.

Didgeridoohan said:
Of course you can (with some possible limitations set by the OEM). With fastboot, for example. But you won't be using the recovery at all (stock or custom).
Click to expand...
Click to collapse
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance

COOLPLAY6FAN said:
so can u gave proper guide to root useing magisc useing pc instead of custom recovery
(with unlock OEM)
Thanks in advance
Click to expand...
Click to collapse
There are installation instructions on how to create the patched boot image with the Magisk Manager in the release thread.
When you have the patched_boot.img file, you'll need to flash it to your device. On most normal devices you can do this with fastboot. Check out your device's forums/DuckDuckGo/Google/Whatever-search-engine-you-use for instructions on that.

I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
* Unlocked bootloader is needed. Period.
* A custom recovery is needed to flash Magisk. TWRP for instance.
* That custom recovery prevent the built-in OTA update to work
* But TWRP can flash OTA updates that can be downloader from XDA for example
Am I correct?
Also,
* Magisk needs a patched boot image
* This image has no impact on the OTA process at all
* There are encryption matters to take care of (I don't understand them yet though).
Is everything correct?
Thanks.

Krystanos said:
I'm also interested to install Magisk with as less impact as possible, so to summarize for newbies like myself:
Click to expand...
Click to collapse
Let's see about answering those statements/questions.
* Unlocked bootloader is needed. Period.
Click to expand...
Click to collapse
Yes.
* A custom recovery is needed to flash Magisk. TWRP for instance.
Click to expand...
Click to collapse
Not necessarily. You can let the Magisk Manager patch your device's stock boot image and then flash it to your device with fastboot. See the installation instructions in the release thread.
* That custom recovery prevent the built-in OTA update to work
Click to expand...
Click to collapse
Yes.
* But TWRP can flash OTA updates that can be downloader from XDA for example
Click to expand...
Click to collapse
No. And yes. Official OTA files can (most of the time) not be flashed in TWRP. ROM zips and flashable firmware packages can.
* Magisk needs a patched boot image
Click to expand...
Click to collapse
Yes, that's all Magisk is about.
* This image has no impact on the OTA process at all
Click to expand...
Click to collapse
It definitely does. See the official docs
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips for more info on how to keep OTA capabilities for your device.
* There are encryption matters to take care of (I don't understand them yet though).
Click to expand...
Click to collapse
Possibly. Depends on what you're talking about.

Great answers. It's more clear for me now. Many thanks sir!

JRapsky said:
Hi,
I used Magisc with several chinese brand phones and never had problems so far.
Now I got a new Moto Z, and I don't want to unlock the bootloader and install a custom recovery.
Is there another way to get Magisc working on my new device?
I understand the concept of systemless root and modification in general. The bootloader unlock and custom recovery installation do not fit in this concept, don't you think so?
Kind regards
Gesendet von meinem XT1650 mit Tapatalk
Click to expand...
Click to collapse
Hi!
There are good news for you, rooting with magisk is very easy that way . No bootloader unlocking, custom recovery,
adb and fastboot command, no sdk no mtk tool . NOTHING but Sp flashtool - our best friend. This method really works with mtk phones android 5.0+ .
What U only need is
Sp flashtool and its drivers /scatter file with the ROM/ -I think not mtk devices with their own flashtool will work too
the ROM of your device
Magisc manager app on the phone
First of all you need clear up the device / after backup somewhere if needed/with sp flashtool - flash the whole ROM in format+download mode.
Install Magisc manager app , it will load for U a zip file in the map of the app
Put the boot img file of your rom in that map too
Run install option - it will create a patched boot img file within the app s map
Run again sp flashtool with download mode , mark only the boot section , and flash that patched boot img in phone
After reboot phone it is rooted
best regards

Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it? 
 @Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)

lefteriskmail said:
Forgive me and explain me something:
I read that "no custom recovery needed" and through the application it will create a patched boot img file.
I installed Magisk Manager 5.4.3, οpens and displays "not installed". I followed the steps that are described in the guide without anything being done.
One of the users they created patched recovery from the application menu in what order did they do it?
@Galaxtracker: you write "it will load for U a zip file in the map of the app" Where is the map of application ; I do not see any folder created ιn Android/Data or or somewhere else.
I have the Ulefone S8Pro with unlock bootloader (Android 7)
Click to expand...
Click to collapse
Install Magisk Manager.
Press install.
Select "Patch Boot Image File".
Select the stock boot image you've previously saved on your device.
Wait.
Flash the patched boot image to your device.
Done.
All of this is covered in the installation instructions...
The folder being mentioned above is MagiskManager on your internal storage (where the patched boot image is also stored).

Magisc
Hi!
Magisc works fine for me from the first time. Excuse me I won't do installation again to see how it goes. Really it causes some hesitation but in the end it's clear.
I use Total commander, and magisc folder is on the external SD card after installing magisc manager app. Factory reset later will not clear the root. After installing manager it says "not installed" till the end of the rooting process. Opening the app it begins to look after the downloadable zip file, you have to wait and download it. This zip and the stock boot img must be in the same place in a folder, and the app itself makes the patched boot img but I don't remember what was the name of the option. This is the flashable img file. In the end after flashing with flashtool and rebooting, magisc manager says "installed". Good luck

Hi, I am trying to centralise this sort of information and am compiling it in another topic for Magisk and android-based media centres too.
Trying to properly document things (full sentences with references, links, and examples) rather than just writing some brief summarised steps that most people will not understand - not just for myself but to share should it assist others learn and understand the preparation and steps involved, plus consequences and ramifications of their actions (which never seem to be stressed enough).
Here is what I have compiled. Hopefully it will help and prevent you going loopy!? :silly:
- - - - - - - - - - - - - - - - - - - -
*** EXTREMELY CLEAR MAGISK ROOT INSTRUCTIONS ***
(Work In Progress! To Be Verified & Critiqued By Others)​
Connect your WiFi so that all auxillary files can be downloaded during the rooting process.
Ensure you have a minimum of 2GB of free disk space. Allow for 1-2 hours to perform these steps. Do not rush!
Bootloaders come with every Android device, and give it all the instructions on how to boot and what to execute. If your Bootloader is locked, then you have not flashed anything like TWRP previously, or, you have re-flashed a stock Bootloader and Recovery, etc. The process is much easier when you have previously rooted the device using another method, and the Bootloader already unlocked.
To preserve your System partition, Magisk only modifies the unlocked Bootloader boot partition, which can easily* be restored and 'locked' later.
0. Before starting anything, always perform a FULL Backup (ADB) of your device, using a good quality USB cable and ADB FastBoot toolkit. Or on some devices you can use a Micro SD card with a TWRP recovery.img to boot into TWRP to perform a backup of partitions. Do both if you want! Make sure you search for the appropriate commands and usage of ADB FastBoot backup so that all data is backed up and included.
> ADB FastBoot: https://developer.android.com/studio/releases/platform-tools.html
> TWRP: https://dl.twrp.me/twrpapp/ \\ https://twrp.me/FAQ/
> Plus various other solutions...
1. Identify your device's firmware, build number, Bootloader, full unique model number, etc. Download any two of these apps:
a) AIDA64 ("System", "CPU" & "Android" tabs.)
b) Device Info HW ("General" & "System" tabs.)
c) DevCheck ("Hardware" & "System" tabs.)
2. Download the stock Bootloader, Recovery and Firmware (___.tar.md5) for your device model, variant and OS. (e.g. match your firmware, build number, bootloader, full unique module number, etc). Some sites will force you to pay to download - search around and you can get free download links, or sometimes from the manufacturer's site. From this firmware, we need to either extract or download the stock Bootloader.img image separately.
3. Install Magisk Manager v5.3-v5.6 as of 2017.02.22 ("Magisc" is typo by guy above).
4. Open Magisk and go to settings, adjust theme, change the language, enable notify for updates, change prompt timeout, etc.
5. On the home screen of the Magisk Manager app, click "Install" then in the pop-up select "Install" again.
a) If you have root access already, choose "Direct Method" - Select, wait, reboot and done (very easy!);
b) If you have stock recovery & locked bootloader, choose "Patch Boot Image File" - in the pop-up explorer, browse for the downloaded Bootloader Image.
c) ... I don't know about "Download ZIP Only" - I assume for flashing with Odin or ADB FastBoot from PC or existing root/unlocked user....?
NOTE: If you are being asked to browse and select a file, be aware that there is no confirmation! As soon as you click, that JPG or RAR archive will be used for patching (and result in an error if cannot be extracted!!!)
6. A file will likely be downloaded in the background (flashable ZIP), a black screen will pop-up processing etc. Wait.....
The processed Boot image will be processed and output to the /MagiskManager/ directory.
If you do NOT have root, or custom recovery, you will need to:
a) grab a PC, install the USB drivers for your device and confirm your device is fully recognised
b) then flash the "patched" Boot image from the Magisk Manager directory with ODIN for Windows or FastBoot on Windows via a good-quality USB cable.
7. ...
8. ...
I think that is it... I may have forgotten something. Please advise if something needs to be fixed or corrected. My Media Centre was already unlocked, so I did not have to unlock and flash the Bootloader.
9. Install free TWRP on your device, and choose to backup any partitions, should you wish to restore them later. Set an alarm to backup your device every few months! What are you prepared to lose if your device was lost/squashed/washed/crunched et al.???
Say thank you and donate to the amazing and all powerful Magisk developer 'TopJohnWu' and team!
Sweet! :fingers-crossed:

Root p20 pro emiu 9

hi friends ..
how can i root my p20 pro android p emiu 9
Without loss of data ??
Sent from my CLT-L29 using Tapatalk

Please don't post questions in the development section.
There is no root afaik

Shmally said:
hi friends ..
how can i root my p20 pro android p emiu 9
Without loss of data ??
Sent from my CLT-L29 using Tapatalk
Click to expand...
Click to collapse
at the moment, there is no 9.0 root. If you want to keep your root - stay on 8.1
CLT-L29 C432

dladz said:
Please don't post questions in the development section.
There is no root afaik
Click to expand...
Click to collapse
ok im sorry

Zarapho said:
at the moment, there is no 9.0 root. If you want to keep your root - stay on 8.1
CLT-L29 C432
Click to expand...
Click to collapse
thank you but im on 9.0

Shmally said:
thank you but im on 9.0
Click to expand...
Click to collapse
he's saying that you can stay on 9.0 without root, or find the steps to go back to 8.1 and get root.

bravo261 said:
he's saying that you can stay on 9.0 without root, or find the steps to go back to 8.1 and get root.
Click to expand...
Click to collapse
i wan stay on 9.0 and wait any new root
Sent from my CLT-L29 using Tapatalk

At this point in time Oreo vs Pie, Pie has been shown as a venomous conundrum, especially for EMUI, Tom Wu has had a hard time trying to exploit Android, it's almost impossible, not sure if @Chainfire has even bothered with his exploit, but i think anything at this point would do.
In all fairness PIE VS OREO, they're so similar, battery is similar, problems are similar, it's a waste of time to flap about and try to root PIE when Oreo is so functional.
Either way, until it's official, i'd avoid PIE.

I have a rooted P20 Pro, running EMUI 9.

This is how i got root on EMUI 9
1 - I Flashed THIS
Command: fastboot flash recovery_ramdisk patched_boot.img
2-Reboot phone, install Magisk manager, go into settings, and change the update channel to custom: https://t2m.io/wuAFCrwO, go back to the Magisk home screen and hit install, download the odd Magisk file.zip file.
3-Reboot phone, press and hold the volume up key and your phone should boot just fine.
4-Open Magisk, install, then patch, and install the downloaded Magisk.zip file.
5-Reboot phone, press and hold the volume up key and your phone should boot just fine.
6-Open Magisk, install, select direct install option. and reboot.
Note:
1 - Now your phone will reboot into the recovery every time on its own, which is a good thing, you no longer need to hold the volume up key every time you reboot, it does it for you. This means no TWRP.
2 - In order to apps root access for the first time you need to have Magisk open, or you wont get prompted for approval. Then the app will have permanent root access.
As always, if you do this it's at your own risk.

So no need for the bootloader unlock code from Huawei ?
Martin

iatros1830 said:
So no need for the bootlocker unlock code from Huawei ?
Martin
Click to expand...
Click to collapse
No you definitely still need to unlock your bootloader, otherwise your can't control certain things which are required

So can you still get an unlock code for the bootloader on the 8.1?

Flintblade said:
So can you still get an unlock code for the bootloader on the 8.1?
Click to expand...
Click to collapse
Couldn't tell you, I unlocked mine back in may from Huawei for free.
Funky Huawei may be the last ones who offer it, but I'd say to research it before committing.
Ministry of solutions did offer keys but I've read that they don't anymore.

Unsupported/Unknown Image format
Hello,
After I push the patched_boot.img and reboot I tried to install the zip file I got the Unsupported/Unknown Image format.
Have you seen this before ?
Cheers from Calgary
Vedrick said:
This is how i got root on EMUI 9
1 - I Flashed THIS
Command: fastboot flash recovery_ramdisk patched_boot.img
2-Reboot phone, install Magisk manager, go into settings, and change the update channel to custom: https://t2m.io/wuAFCrwO, go back to the Magisk home screen and hit install, download the odd Magisk file.zip file.
3-Reboot phone, press and hold the volume up key and your phone should boot just fine.
4-Open Magisk, install, then patch, and install the downloaded Magisk.zip file.
5-Reboot phone, press and hold the volume up key and your phone should boot just fine.
6-Open Magisk, install, select direct install option. and reboot.
Note:
1 - Now your phone will reboot into the recovery every time on its own, which is a good thing, you no longer need to hold the volume up key every time you reboot, it does it for you. This means no TWRP.
2 - In order to apps root access for the first time you need to have Magisk open, or you wont get prompted for approval. Then the app will have permanent root access.
As always, if you do this it's at your own risk.
Click to expand...
Click to collapse

Personally I just flash magisk to recovery_ramdisk then boot and install manager.
Then on each reboot, just try to boot to recovery and it'll load the magisk IMG which will make your ROM rooted.
Better ways to do it but that always works

Question Rooting Zenfone 8

I understand there is no TWRP recovery for Zenfone 8 yet, but according to other posts, their are other ways to root the phone, e.g. using Magisk boot image patch method.
I tried, but I'm not able to flash the boot image in fastboot. I'm able to boot to fastboot mode, but it's showing no device when I use "fastboot devices" with USB connection. If I enter recovery mode, "adb devices" is showing unauthorized.
I don't know how to proceed. Appreciate your help!

It's solved by plugging the USB cable to USB 2.0 port on the PC

Good to hear it worked out. I was going to suggest installing a driver when in fastboot mode.
How did you get the boot image btw? I've never tried for anything other than a Lineage OS device, for which all the files are easily accesible.

To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.

After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?

DerSteppo said:
After opening the bootloader and rooting the phone, are there any disadvantages you discovered? Warning screen on boot, (banking) apps not working, etc.?
Click to expand...
Click to collapse
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.

dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
OK thanks for the information!

dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.

dohanin said:
To get the boot image:
1. Get the full firmware form Asus official site: (must get the same version as your current phone)
https://www.asus.com/UK/supportonly/ZenFone 8 (ZS590KS)/HelpDesk_BIOS/
2. Extract payload.bin from the zip file
3. Use Payload Dumper to extract the img files, and you'll find boot.img
note. their are some versions requiring to install Python on your PC. I found this one with executable:
https://ava4.androidfilehost.com/dl...18474/2188818919693785372/Payload_Dumper.zip?
4. Use Magisk to patch boot.img.
Hope this helps.
Please note after flashing the patched boot.img, your phone will be rooted but it fails safetynet. Have to install the module "safetynet-fix-v1.1.0.zip", then everything is fine.
Click to expand...
Click to collapse
Ah, thanks that did help. I didn't know the full firmware was available from the site.

yunyou said:
After rooting, it seems that the official ota update cannot be detected, and it cannot be seamlessly achieved by using the Magisk to install to the unused slot. Is there any other way to achieve the update? For example, OnePlus can choose to install the full ota downloaded from the official website locally.
Click to expand...
Click to collapse
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.

dohanin said:
Do you mean you already tried this with Zenfone 8 OTA update after rooting? I did it with firmware "WW-30.11.51.67" and it's still the current one, so I don't know whether it would work or not.
Click to expand...
Click to collapse
I found ota's solution. Download the "WW-30.11.51.67" firmware from the official website and move it to the main storage directory of the phone. Then the phone should detect the update file, but if the phone does not prompt, then try to restart the device. When the phone restarts and enters the system again, the system will detect the update, and there will be an update launcher notification in the notification bar!
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.

dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.

grootzy said:
If you use DRM Info app do you still have Widevine L1 security level? (needed for netflix hd playback) thanks.
Click to expand...
Click to collapse
yes, it's showing L1 in Widevine CDM

dohanin said:
yes, it's showing L1 in Widevine CDM
Click to expand...
Click to collapse
Thanks, great news that ASUS are not being dicks with the bootloader unlocking.
For anyone else who isn't too clear on the steps (like me!) - After patching the boot image with magisk you then can use adb to pull that image to a PC and then use adb reboot bootloader and then fastboot boot patched-image.img to check the rooting works without flashing anything and then use adb reboot bootloader again and then fastboot flash boot patched-image.img to write it to the flash memory if everything went smoothly. This worked for me and everything seems great. Obviously you need adb and fastboot set up on your PC for this to work. I'm not sure if this was the intended method but it is what I did.

dohanin said:
Yes, there is a warning screen on boot. And yes, some banking apps I use can't be cheated by Magisk Hide, but I use Work profile (via Island) to work around it. So far so good.
Click to expand...
Click to collapse
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know

fatjoez said:
did you try hiding magisk manager by changing the magisk manager package name? (it's an option in magisk manager).
some apps detect the magisk manager app to guess rooting.
If you hide magisk app + use magiskhide on the bank app it should be working.
please check let me know
Click to expand...
Click to collapse
hi, yes i tried but while most apps are working fine, some banking apps can still detect root. however, for those apps, if i disable the magisk app beforehand, then it can be passed. i could not figure why since the magisk app is already with a random package name. i posted my query in the magisk forum too.
anyway, with this method, i don't need to use work profile now.

Hi everbody.
I hope someone can help me out.
I unlocked my Zenfone 8 with the official unlock tool and i want to relock the bootloader back.
I was using commands like fastboot oem asus-lock, fastboot flashing lock, but nothing works.
Did Asus changed something in Android 11?
In Android 10 the first command was working without problems.
Thanks

You can't lock it back.
Only to change motherboard.

dron39 said:
You can't lock it back.
Only to change motherboard.
Click to expand...
Click to collapse
Oh that's bad news. Thank you very much for your fast answer.

yunyou said:
When the system update interface is over, when prompted to restart, install to an unused slot through the Magisk option. Select the installation to keep ROOT to achieve seamless ota.
Click to expand...
Click to collapse
Can you explain further on this? Are you saying to install the firmware to an unused slot? What exactly is an unused slot? I haven't seen anything like this in magisk.