Database Info

Prob install B029 update on 703 model

i have a big problem
i unroot my phone, install stock recovery from p8max root tools and NOW i come not in the recovery for install the update. it shows only the huawei logo.
i flashed via fastboot flash recovery recovery.img
when i flashed twrp, i come into the twrp recovery, but here i cant install the update.
anyone have a idea?
Gesendet von meinem HUAWEI P8max mit Tapatalk

Sounds linke u somehow bricked you phone, flash original recovery and force update it Form SD card.

Hirs_E_Fruit said:
Sounds linke u somehow bricked you phone, flash original recovery and force update it Form SD card.
Click to expand...
Click to collapse
thats the problem, i flash the orginal recovery and after this, i come not in the recovery. not from the update tool via local update, it restarts and stand on the huawei logo.
Gesendet von meinem HUAWEI P8max mit Tapatalk

where did u get the original recovery?

Hirs_E_Fruit said:
where did u get the original recovery?
Click to expand...
Click to collapse
from here:
http://www.mediafire.com/download/9drsdo2f6hn4j34/P8MaxRootTools.zip
Gesendet von meinem HUAWEI P8max mit Tapatalk

Huawei devices usually have 2 recovery partitions; 1 is the regular recovery & the other 1 is the eRecovery.
Here are both (from the b029 update): https://drive.google.com/file/d/0B8rpJsF4EG0YWk9xMWFJSXA3VnM
Flash the 1st one & you should be good to go.
If you want to flash the 2nd partition, you need to specify "recovery2" as target in fastboot.
In case this doesn't work but you can still access TWRP, try the following:
adb push recovery1.img /sdcard/
adb push recovery2.img /sdcard/
dd if=/sdcard/recovery1.img of=/dev/block/mmcblk0p28
& for eRecovery:
dd if=/sdcard/recovery2.img of=/dev/block/mmcblk0p21
Reboot & do your thing.

adwinp said:
Huawei devices usually have 2 recovery partitions; 1 is the regular recovery & the other 1 is the eRecovery.
Here are both (from the b029 update): https://drive.google.com/file/d/0B8rpJsF4EG0YWk9xMWFJSXA3VnM
Flash the 1st one & you should be good to go.
If you want to flash the 2nd partition, you need to specify "recovery2" as target in fastboot.
In case this doesn't work but you can still access TWRP, try the following:
adb push recovery1.img /sdcard/
adb push recovery2.img /sdcard/
dd if=/sdcard/recovery1.img of=/dev/block/mmcblk0p28
& for eRecovery:
dd if=/sdcard/recovery2.img of=/dev/block/mmcblk0p21
Reboot & do your thing.
Click to expand...
Click to collapse
ok i flashed the first one and i come into the erecovery and install the update zip.
after the update the phone reboot in the huawei boot logo and stand on this.
i wait over 10 minutes.
update is now installed, but i come not in the system.
please help.

siddartha said:
ok i flashed the first one and i come into the erecovery and install the update zip.
after the update the phone reboot in the huawei boot logo and stand on this.
i wait over 10 minutes.
update is now installed, but i come not in the system.
please help.
Click to expand...
Click to collapse
Are you sure you flashed it correctly? The full 1.4Gb update needs to be extracted & the dload folder copied into the root of the sdcard.
Not the zip itself.
I also suggest to make a full wipe from fastboot:
fastboot erase cache
fastboot erase userdata
fastboot format cache
fastboot format userdata

adwinp said:
Are you sure you flashed it correctly? The full 1.4Gb update needs to be extracted & the dload folder copied into the root of the sdcard.
Not the zip itself.
I also suggest to make a full wipe from fastboot:
fastboot erase cache
fastboot erase userdata
fastboot format cache
fastboot format userdata
Click to expand...
Click to collapse
my update.zip is only 40mb, i downloaded it with the regular update tool

siddartha said:
my update.zip is only 40mb, i downloaded it with the regular update tool
Click to expand...
Click to collapse
In this case I recommend that you download the full 1.4Gb update - the 40Mb OTA might try patching the recovery as well, & since the recovery on the device is already from that version, it will fail.
Although I don't know whether this will be an image flash or binary patching.
As mentioned - the safest & fastest way is to install the full firmware.

adwinp said:
In this case I recommend that you download the full 1.4Gb update - the 40Mb OTA might try patching the recovery as well, & since the recovery on the device is already from that version, it will fail.
Although I don't know whether this will be an image flash or binary patching.
As mentioned - the safest & fastest way is to install the full firmware.
Click to expand...
Click to collapse
ok thx, i will try this.
is there a faster download for the full b029 firmware?

now it works!
i flashed stock recovery and then twrp many times and halleluja, i come in twrp.
now ich restore a backup und come in the system. i look into the settings and here is the b029. i wonder why...
**** happens, now it works!
thanx for your help!!!
Gesendet von meinem HUAWEI P8max mit Tapatalk

siddartha said:
now it works!
i flashed stock recovery and then twrp many times and halleluja, i come in twrp.
now ich restore a backup und come in the system. i look into the settings and here is the b029. i wonder why...
**** happens, now it works!
thanx for your help!!!
Gesendet von meinem HUAWEI P8max mit Tapatalk
Click to expand...
Click to collapse
Glad you could solve the problem ;]
the b029 is simple: nandroid only makes a backup of the boot, data & system partitions, but Huawei flashes customization to other partitions (/dev/block/mmcblk0p8, /dev/block/mmcblk0p39), where the firmware level is stored.
If you want to apply OTAs in the future, I really recommend doing a full flash to get all firmware levels consistent.

[REQUEST] bckup img from TL10

Hi all,
My mate can't boot , can't enter to dload for install firmware and can't enter recovery mode, fastboot mode only I can.
I need bacup .img MM for TL10
system.img,cache.img,recovery.img ,boot.img,cust.img,userdata.img to fastboot please help me

I can fixed
Many thanks for kindly help @blue_Ember and @chudy85
Sent from my HUAWEI NXT-L29 using Tapatalk

No problem cheers and try back to lp
Send from ?

[PROJECT][QUESTION] About Nokia 8 Custom Recovery and Unlock Bootloader?

I finally rooted my Nokia 8 PROTO with a custom TWRP recovery kindly provided by Chinese 7to forum.
Here's the procedure I did on my Nokia 8 PROTO:
1. I managed to extract boot.img manually by using WinHex manually. But I found the Recovery is combined into boot.img when analyzing ramdisk included in boot.img. This made Nokia 8 Custom Recovery difficult.
2. After maintenance purposed bootloader activated by OST LA, you could flash custom recovery by this command:
Code:
fastboot-android flash boot NB1-boot.img
Yes, that's boot partition instead of recovery partition. (Mine is TA-1012)
Sorry I've put the recovery for Nokia 5 by mistake, now replaced with correct one.
Click to expand...
Click to collapse
To activate maintenance purposed bootloader, you need to load original stock firmware with OST LA, then click "Edit phone data". When OST LA prompts "Boot FTM mode fail", the maintenance purposed bootloader is loaded.
3. Type this command but do not execute right now:
Code:
fastboot-android reboot
4. Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
5. The custom recovery doesn't include SuperSU ROOT package. I sideloaded "SR4-SuperSU-v2.82-SR4-20170918204844.zip" to the phone. The sideload option is in "高级" (Advanced in Chinese) catagory. I've never tested magisk on it.
6. You may want to remove verification feature in recovery. Reboot your phone.
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Here's the result if you're interested: https://twitter.com/Hikari_Calyx/status/917348942165155841
----------SEPARATOR----------
Here's how to enter Emergency Download mode:
1. Enter Download Mode by using OST LA.
2. After maintenance purposed bootloader activated by OST LA, type this command:
Code:
fastboot-android oem reboot-edl
In order to enter Emergency Download Mode. It may complex, currently it's the only way to enter Emergency Download Mode without disassembling.
3. Do something with your phone with QFIL.
----------SEPARATOR----------
I finally untrapped my Nokia 8 prototype, which has an unlocked bootloader.
Although Nokia 8 cannot enter EDL mode (Or 9008) with EDL Cable directly while Nokia 5 and 6 are able to enter EDL mode with EDL cable, I still figured out how to enter the EDL mode on Nokia 8 without any specific peripherals.
With @heineken78‘s nb0tools2016v2, I was able to unpack few of files from Nokia 5/6/8's nb0 firmware from @blackpanther0582, but that's only about bootloaders and rawprogram*.xml and patch*.xml, and I was not able to unpack any further, the program got overflow and terminated.
These files should be enough for unbrick your phone from full brick.
Anyway, that's off topic.
After I entered the EDL mode of my Nokia 8 prototype (with provided retail firmware installed), I used Partition Manager from QFIL included in QPST 2.7.460. I attached the screenshots of the partitions.
However, I noticed there's no recovery partition, which makes the TWRP port to Nokia 8 confusing.
(Although our Chinese Team ported TWRP to Nokia 6 and 5 recently)
And which partitions are important for bootloader unlocking?
Since we could enter EDL mode easily, it should be easy to unlock bootloader for Nokia 5/6/8 currently.

There not being a recovery partition would explain this. There is a obviously a recovery though, but it's accessed through the download mode. So my guess is the recovery is either hidden/baked in with another partition or it's inside the kernel like in the old days (more likely the former though). Unfortunately I know far too little about this stuff so I'm not of much help.

CazeW said:
There not being a recovery partition would explain this. There is a obviously a recovery though, but it's accessed through the download mode. So my guess is the recovery is either hidden/baked in with another partition or it's inside the kernel like in the old days (more likely the former though). Unfortunately I know far too little about this stuff so I'm not of much help.
Click to expand...
Click to collapse
Well, I got this information from Nokibar.
To enter Recovery for factory reset if you want to try it out, here's the method provided by HMD:
1. Power off your phone.
2. Press and hold Volume Up key and connect your phone to PC.
3. Waiting for Android robot on the ground displays along with NO COMMAND, release the Volume Up.
4. Press Volume Up while pressing power key to get Recovery menu.
Click to expand...
Click to collapse
It does have recovery, but I still can't figure out which partition includes it.

hikari_calyx said:
Well, I got this information from Nokibar.
It does have recovery, but I still can't figure out which partition includes it.
Click to expand...
Click to collapse
Thank you for the reminder that I found it

hikari_calyx said:
I finally rooted my Nokia 8 PROTO with a custom TWRP recovery kindly provided by Chinese 7to forum.
Here's the procedure I did on my Nokia 8 PROTO:
1. I managed to extract boot.img manually by using WinHex manually. But I found the Recovery is combined into boot.img when analyzing ramdisk included in boot.img. This made Nokia 8 Custom Recovery difficult.
2. After maintenance purposed bootloader activated by OST LA, you could flash custom recovery by this command:
Code:
fastboot-android flash boot nokia-ta-1004-twrp3.1.1-7to-recovery.img
Yes, that's boot partition instead of recovery partition. (Mine is TA-1012)
3. Type this command but do not execute right now:
Code:
fastboot-android reboot
4. Press and hold Volume Up, then execute the command above. Keep holding Volume Up until you see the 7to logo.
5. The custom recovery doesn't include SuperSU ROOT package. I sideloaded "SR4-SuperSU-v2.82-SR4-20170918204844.zip" to the phone. The sideload option is in "高级" (Advanced in Chinese) catagory. I've never tested magisk on it.
6. You may want to remove verification feature in recovery. Reboot your phone.
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Here's the result if you're interested: https://twitter.com/Hikari_Calyx/status/917348942165155841
Click to expand...
Click to collapse
So they did put the recovery inside the boot image like I first guessed. That's.... surprising to say the least as that's very old school. Like Galaxy S old school. Wonder why they did it that way, as it just feels stupid. Glad you figured it out though, now we just need a way to unlock the bootloader and we can get rooting.

CazeW said:
now we just need a way to unlock the bootloader and we can get rooting
Click to expand...
Click to collapse
HMD promised they'd unlock all Nokia phones one by one. It's just a matter of time till they reach Nokia 8.
But if someone can figure out how to do it before that happens, that'd be amazing

CazeW said:
So they did put the recovery inside the boot image like I first guessed. That's.... surprising to say the least as that's very old school. Like Galaxy S old school. Wonder why they did it that way, as it just feels stupid. Glad you figured it out though, now we just need a way to unlock the bootloader and we can get rooting.
Click to expand...
Click to collapse
And here's another problem: When I rooted the phone, it will destroy the recovery included in boot.img, so doing factory reset is tough for it.

hikari_calyx said:
And here's another problem: When I rooted the phone, it will destroy the recovery included in boot.img, so doing factory reset is tough for it.
Click to expand...
Click to collapse
Makes sense as SuperSU modifies the boot.img. Unless we (or HMD) somehow can put the recovery on a recovery partition, a custom/updated version of SuperSU is going to be needed. Not sure if Magisk root modifies the boot.img but I would suspect that it does.

hikari_calyx said:
I tested it on a Nokia 8 Retail Phone, it says "verification failed" after I reboot. So I wonder if anything wrong.
Click to expand...
Click to collapse
Prototype units are for development use, so most likely have secure boot disabled.
In retail unit or production unit with secure boot enabled, if you modified the bootloader (or its partition), the secure boot verification will fail.

CazeW said:
Makes sense as SuperSU modifies the boot.img. Unless we (or HMD) somehow can put the recovery on a recovery partition, a custom/updated version of SuperSU is going to be needed. Not sure if Magisk root modifies the boot.img but I would suspect that it does.
Click to expand...
Click to collapse
I updated the procedure of entering Emergency Download mode on topic. You can give it a try if interested.

How to enter recovery mode?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka

Araa01 said:
How to enter recovery mode?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
Use adb : adb reboot recovery, then hold the power + volume up buttons.

gee2012 said:
Use adb : adb reboot recovery, then hold the power + volume up buttons.
Click to expand...
Click to collapse
When i off device combination power + up not work? I must use adb?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka

Araa01 said:
When i off device combination power + up not work? I must use adb?
Wysłane z mojego Nokia 8 przy użyciu Tapatalka
Click to expand...
Click to collapse
No, don`t think so but for me thats the easiest method to get into recovery

gee2012 said:
No, don`t think so but for me thats the easiest method to get into recovery
Click to expand...
Click to collapse
Thank u! When we get oreo i must shoot full wipe so.. :d
Wysłane z mojego Nokia 8 przy użyciu Tapatalka

Interesting to see 'OEM Unlocking' in the Developer Settings.

Steve Geemaggio said:
Interesting to see 'OEM Unlocking' in the Developer Settings.
Click to expand...
Click to collapse
I tried to unlock the bootloader with Fastboot but I only get an error saying that it is not possible. That is with the setting turned on. So I guess the setting is still not active.

alexcannasV said:
I tried to unlock the bootloader with Fastboot but I only get an error saying that it is not possible. That is with the setting turned on. So I guess the setting is still not active.
Click to expand...
Click to collapse
I see! Well then I guess we got to wait for Nokia to step up and do it then.
Great to be running pure AOSP out of the box though. I'm grateful for that, but would love to be able to get rid of the mountain of Google apps pre-installed.
Glad Nokia changed their mind about unlocking the bootloader!

Steve Geemaggio said:
Glad Nokia changed their mind about unlocking the bootloader!
Click to expand...
Click to collapse
Hold your horses! Haven't seen any unlocked bootloaders yet...

I was reading today this http://neopodapsi.com/how-to-unlock-bootloader-on-nokia-8/
Is this for real or not? I was very interested in the Nokia 8 if they were unlocking the BL and releasing the kernel sources

Bricked my Mi Mix 2S

Hello guys!
Yesterday I made a huge mistake and installed a treble ROM as a normal one. I loaded (not installed) TWRP on my phone, deleted system, data and cache, installed the ROM, deleted cache and dalvik and officially bricked it.
This is where I stand now:
The phone OEM is unlocked.
USB debugging is not activated and I can't activate it because I don't have access to the OS.
There is no recovery whastoever. Booting into recovery starts a bootloop.
Regular booting starts a bootloop.
The only thing that work is fastboot mode and it has its limitations.
- Can't use MiFlash to install a new ROM (I left it working for 8 hours with no results).
- It auto shuts down with the error message press any key to shutdown, which is the error it shows when USB debug is not activated.
Is there a way I can unbrick it? At this point I don't mind opening my phone and manipulating its insides becuase the warranty is already void by some company legal gibber-gabber.
I also have access to Windows, Ubuntu (Debian) and Antergos (Arch) on my computers, if anyone knows how to solve this from these operating systems. I don't mind installing other OS if it's necessary.
OK GUYS. IT'S FIXED. HERE IS THE PROCESS:
Boot the phone into fastboot mode and open adb on terminal
Type adb flash recovery whateverrecovery.img
The phone disconnects but the terminal says < waiting for device >
Keep the phone plugged and reboot into fastboot, wait a bit and it will flash
The rest you know, reboot into recovery, flash your rom and move on to breaking other devices.
Thanks to averyone that helped. You are the best!

Groctel said:
Hello guys!
Yesterday I made a huge mistake and installed a treble ROM as a normal one. I loaded (not installed) TWRP on my phone, deleted system, data and cache, installed the ROM, deleted cache and dalvik and officially bricked it.
This is where I stand now:
The phone OEM is unlocked.
USB debugging is not activated and I can't activate it because I don't have access to the OS.
There is no recovery whastoever. Booting into recovery starts a bootloop.
Regular booting starts a bootloop.
The only thing that work is fastboot mode and it has its limitations.
- Can't use MiFlash to install a new ROM (I left it working for 8 hours with no results).
- It auto shuts down with the error message press any key to shutdown, which is the error it shows when USB debug is not activated.
Is there a way I can unbrick it? At this point I don't mind opening my phone and manipulating its insides becuase the warranty is already void by some company legal gibber-gabber.
I also have access to Windows, Ubuntu (Debian) and Antergos (Arch) on my computers, if anyone knows how to solve this from these operating systems. I don't mind installing other OS if it's necessary.
Click to expand...
Click to collapse
Simply flash recovery from fastboot and wipe everything and flash stock global/cn
Wysłane z mojego MIX 2S przy użyciu Tapatalka

Wooby said:
Simply flash recovery from fastboot and wipe everything and flash stock global/cn
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
I can't do that. Flashing recovery gives me an error that reads FAILED (command write failed (No error)). It happens with anything I try to flash.

Groctel said:
I can't do that. Flashing recovery gives me an error that reads FAILED (command write failed (No error)). It happens with anything I try to flash.
Click to expand...
Click to collapse
If You have access to fastboot, you should be able to flash everything without limitations, maybe some issues with drivers or start fastboot command line with admin rights
Wysłane z mojego MIX 2S przy użyciu Tapatalka

Have you tried running flash_all.sh / flash_all.bat? It should be part of official fastboot rom package. You have to have fastboot + drivers installed.

Wooby said:
If You have access to fastboot, you should be able to flash everything without limitations, maybe some issues with drivers or start fastboot command line with admin rights
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
What operating system do you suggest I use?
Can you guide me with the commands I should try?

Cubiss said:
Have you tried running flash_all.sh / flash_all.bat? It should be part of official fastboot rom package. You have to have fastboot + drivers installed.
Click to expand...
Click to collapse
I'm going to try, I'll update you on that.

Groctel said:
What operating system do you suggest I use?
Can you guide me with the commands I should try?
Click to expand...
Click to collapse
fastboot flash recovery "recovery.img"
And then boot with power + volume up
Wysłane z mojego MIX 2S przy użyciu Tapatalka

Wooby said:
fastboot flash recovery "recovery.img"
And then boot with power + volume up
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
It returns the error I told you before. Can't do that :/

Send me that error please, another method would be like that guy said above download latest fastboot MIUI
Groctel said:
It returns the error I told you before. Can't do that :/
Click to expand...
Click to collapse
Wysłane z mojego MIX 2S przy użyciu Tapatalka

Cubiss said:
Have you tried running flash_all.sh / flash_all.bat? It should be part of official fastboot rom package. You have to have fastboot + drivers installed.
Click to expand...
Click to collapse
Checked that I had the drivers installed. Run fastboot devices and the phone went into press any key to shutdown mode.

Wooby said:
Send me that error please, another method would be like that guy said above download latest fastboot MIUI
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is from yesterday. I'm now on Antergos (Arch Linux) and can't even see that my device is attached using fastboot devices.

I recommend you to download minimal adb and fastboot, run fastboot devices and tell me if you see your device
Groctel said:
This is from yesterday. I'm now on Antergos (Arch Linux) and can't even see that my device is attached using fastboot devices.
Click to expand...
Click to collapse
Wysłane z mojego MIX 2S przy użyciu Tapatalka

What MIUI base is installed before it bricks? What kind of custom did you flashed?

Wooby said:
I recommend you to download minimal adb and fastboot, run fastboot devices and tell me if you see your device
Wysłane z mojego MIX 2S przy użyciu Tapatalka
Click to expand...
Click to collapse
The first time I run it I see it. The second time I run it the phone enters into press any key to shutdown mode and turns fastboot off.

Muhdxzhafir said:
What MIUI base is installed before it bricks? What kind of custom did you flashed?
Click to expand...
Click to collapse
Latest MIUI 10 version and tried to install the unofficial treble LOS rom in this forum section.

Groctel said:
Latest MIUI 10 version and tried to install the unofficial treble LOS rom in this forum section.
Click to expand...
Click to collapse
Latest beta or stable?
"adb devices" works? try this if it could help, but.. just take a look http://en.miui.com/thread-528989-1-1.html

Muhdxzhafir said:
Latest beta or stable?
"adb devices" works? try this if it could help, but.. just take a look http://en.miui.com/thread-528989-1-1.html
Click to expand...
Click to collapse
I can't boot into twrp, that's my main problem. Every time I try to do it my phone disconnects and shows the press any key to shutdown screen.

Groctel said:
I can't boot into twrp, that's my main problem. Every time I try to do it my phone disconnects and shows the press any key to shutdown screen.
Click to expand...
Click to collapse
Uninstall all adb drivers you have on your computer, restart and install these adb/fastboot drivers:
https://forum.xda-developers.com/showthread.php?t=2588979
Try it on a different usb port on your computer (use the ports on the back!)
Use a windows computer.
If it does not work, try a different computer, use windows.
It's an issue on your computer, and not related to usb debugging

malimukk said:
Uninstall all adb drivers you have on your computer, restart and install these adb/fastboot drivers:
https://forum.xda-developers.com/showthread.php?t=2588979
Try it on a different usb port on your computer (use the ports on the back!)
Use a windows computer.
If it does not work, try a different computer, use windows.
It's an issue on your computer, and not related to usb debugging
Click to expand...
Click to collapse
I get the error : device not found after this command
adb reboot bootloader.
How to solve it ??? Thanks !
https://drive.google.com/file/d/1Re6YZkL8KXSK35Pea5K6Iw41AQ9nVT7u/view?usp=sharing
Please see the link above.

[GUIDE] Root AL00 EMUI 9.1

To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator

File link is broken (file not found), please fix.

Repaired, sometimes a few times you need to refresh

I have rooted emui 9.1 mate 20x chinese but contact and dialer dont open ..any idea how to fix it?

Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka

facet_ said:
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
Click to expand...
Click to collapse
You saying to me?
---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
facet_ said:
Try flash https://androidfilehost.com/?fid=1395089523397950492
Wysłane z mojego EVR-AL00 przy użyciu Tapatalka
Click to expand...
Click to collapse
I don't have twrp

walkwitmeinhel said:
You saying to me?
---------- Post added at 11:06 PM ---------- Previous post was at 11:06 PM ----------
I don't have twrp
Click to expand...
Click to collapse
Maybe you flash busybox in magisk and unzip the downloaded file then replace the file in system with root explorer. Try and let me know also. Ps. I never try before.

I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers

dladz said:
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
Click to expand...
Click to collapse
If you unlocked bl you can flash patched img and root

walkwitmeinhel said:
If you unlocked bl you can flash patched img and root
Click to expand...
Click to collapse
Thats what i thought dude
boot to bootloader
put magisk patched img in adb folder
fastboot flash recovery_ramdisk magisk.patched.img
Remove cable, boot and hold up
device boots to the first screen for eRecovery
same problem with TWRP
I've even factory wiped and booted straight to bootloader before flashing magisk or twrp, had to install the stock recovery_ramdisk to perform the wipes required
at this point i've no idea what to do so i'm looking for a non service firmware to flash, only the ones i've found are all 311 not above, can't find 320
sucks
EDIT: Downloading this now
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=145556

dladz said:
Thats what i thought dude
boot to bootloader
put magisk patched img in adb folder
fastboot flash recovery_ramdisk magisk.patched.img
Remove cable, boot and hold up
device boots to the first screen for eRecovery
same problem with TWRP
I've even factory wiped and booted straight to bootloader before flashing magisk or twrp, had to install the stock recovery_ramdisk to perform the wipes required
at this point i've no idea what to do so i'm looking for a non service firmware to flash, only the ones i've found are all 311 not above, can't find 320
sucks
EDIT: Downloading this now
https://support.halabtech.com/index.php?a=downloads&b=file&c=download&id=145556
Click to expand...
Click to collapse
Fastboot flash recovery_ramdisk magisk_patched.img

walkwitmeinhel said:
Fastboot flash recovery_ramdisk magisk_patched.img
Click to expand...
Click to collapse
Yep I know pal..doesn't work.
Have done this hundreds of times.
Don't worry about it, I'm getting rid of this turd of a phone.
1+7pro here I come.

dladz said:
I'm on a P20 Pro with EMUI 9.1 - 9.1.0.311
I cannot flash TWRP or Magisk boot img's, bootloader is still unlocked, FRP is fine, it's just not letting me play.
I pathced TWRP, Recovery_ramdisk, nothing is playing lol.
Perhaps it's the rom i'm on.
Thanks for the guide, but no good for the pro on 311 unfortunately.
Cheers
Click to expand...
Click to collapse
I have highlighted your problem above. This is a mate 20 x thread. You have a p20 pro.

facet_ said:
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
Does this also work on my Huawei Mate 9?
And did you just patch the EMUI 9.1 recovery_ramdis via magisk or something else?

Doesn't work for me I have AL00 135

i had the same prob: the trick ist to keep Vol up and (!) Power at the same time until the blue bootschreen from the honor appears. Do it NOT as in earlier times: Do NOT realese power after the first vibration as before. After flashing the modyfied patched recovery (modyfied by magisk), keep both buttons until the blue honor bootscreen apears, then release the buttons & you will see only one text line (not the three), which indicates that the v10 is booting with root!

Anybody want to sell their rooted mate 20 x? United States only
Thanks

Does this work for Mate 20 non-X?!

facet_ said:
To have root on EMUI 9.1 we need https://androidfilehost.com/?fid=11410963190603907556
and ADB on the computer.
1. connect the phone to the computer, turn on the USB debugging mode
2. In ADB: "adb reboot bootloader"
The phone will go off in fastboot mode.
The downloaded file is loaded with a command: "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00-b7f69238.img
5. We're rebooting with a command: "fastboot reboot, quickly disconnect the phone and hold the VOL+ at the same time (all the time from the restart)
The phone will enter the eRecovery mode and we normally click "Factory/WIPE" as if we were restoring the factory settings.
This will cause root (magisk) to save permanently.
Of course we need to unlock the bootloader, but now (10.06.2019) it is not a problem because they sell for $41 (I bought it on imei.by - paid PayPal)
I wrote this post because I've been working hard to get root for half a day and there were incomplete answers everywhere.
Translated with www.DeepL.com/Translator
Click to expand...
Click to collapse
I've been looking for a way to install Magisk on a Huawei Mate 20 Lite (running EMUI 9.1 before) for weeks, and you gave me the solution (= reboot to eRecovery then wipe before the first boot) ! THANK YOU !!!

What I need to do is to downgrade the OS to Android 9 so I can unlock the bootloader.
How can I do the downgrade? I already have the special Harmony cable for the downgrade.