Database Info

Downgrade from lollipop b312 to kitkat b143

As the title, anyone know how? I tried the transitional b300 but failed. Tq in advanced

I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?

muzammil84 said:
I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?
Click to expand...
Click to collapse
Where can I find b300?
Sent from my HUAWEI MT7-TL10 using Tapatalk

muzammil84 said:
I just did mine couple of days ago. Rollback to b300 worked without any issues. Then trying to install b141 I couldn't get it working( 3 button method wasn't getting to installation screen, it was rebooting device after huawei logo). So I tried few times with SD card taken out, worked after 3rd time(you have to push the card in just when the huawei logo is going off).
Not sure why you cannot install transition pack, what phone have you got? Is your recovery stock? Phone rooted and unlocked?
Click to expand...
Click to collapse
R u malaysia? Btw.. Can i hv the b300 link

It always stuck at 19%

Dekdek1 said:
R u malaysia? Btw.. Can i hv the b300 link
Click to expand...
Click to collapse
No man UK.
http://www.carbontesla.com/2015/07/how-to-downgrade-ascend-mate-7-to-kitkat-firmware/

why u all downgrading .. u love so much lolipop all sudden dont like it ?

because it's a performance step back, phone is almost non usable on lollipop.

if you have L09, from B300 you can flash B137Sp03, then you can flash any kitkat you want

I just want to go back to kitkat lollipop is boring , i stuck on 19% on rolling back of MT7-tl10

muzammil84 said:
because it's a performance step back, phone is almost non usable on lollipop.
Click to expand...
Click to collapse
Update to 317 it is really cool..

XDADEVX said:
Update to 317 it is really cool..
Click to expand...
Click to collapse
yeah, done it few days ago, big improvement over b308 and b312.

Anybody else here stuck on B300 transition? I can't seem to flash back to B137 or B145...keep getting stuck at 19% and menu says failed. I was at B327 5.1.1, flashed B300 and now I'm stuck.
Any ideas? Please help.

jfer671 said:
Anybody else here stuck on B300 transition? I can't seem to flash back to B137 or B145...keep getting stuck at 19% and menu says failed. I was at B327 5.1.1, flashed B300 and now I'm stuck.
Any ideas? Please help.
Click to expand...
Click to collapse
Have you tried flashing KitKat B119?
For the model TL10, here is the link: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Let me know if it works or not.

kingrk said:
Have you tried flashing KitKat B119?
For the model TL10, here is the link: http://consumer.huawei.com/en/support/downloads/detail/index.htm?id=32364
Let me know if it works or not.
Click to expand...
Click to collapse
I'm MT7-L09...tried the lowest firmware 127 up to 148, no luck.

jfer671 said:
I'm MT7-L09...tried the lowest firmware 127 up to 148, no luck.
Click to expand...
Click to collapse
Can you try this?
Upgrade to firmware B308 by downloading from here for L09 -> http://www.carbontesla.com/2015/06/download-ascend-mate-7-b308-lollipop-ota-zip-emui-3-1/
Then follow this guide:
http://www.carbontesla.com/2015/07/how-to-downgrade-ascend-mate-7-to-kitkat-firmware/
Best

Ok, problem solved. Before being stuck, I was on 145, then >148...wanted 145 back, and flashed 300. Somehow was able to then upgrade to 324 and >327. Camera is really slow on 5.1.1 and somehow doesn't take full pics (leaves gallery with multiple "no image") files.
Flashed 300 again and became stuck for the past two weeks. Re-flashing and factory resetting failed as well. Read somewhere on the forum to not factory reset on 5.1.1, after the fact, and thought I'd been soft-bricked.
**Update: finally was able to unlock boot-loader; and via adb/fastboot, re-flashed 300>324>327.
Thinking of going back 145 if I can't find solution for LP root.
Thanks for all the input tho, helped in organizing my thoughts on what went wrong.

How did you flash using fastboot. Can you write the procedure please. Did you use a custom recovery or directly flash using fastboot?
Sent from my HUAWEI MT7-TL10 using Tapatalk

kingrk said:
How did you flash using fastboot. Can you write the procedure please. Did you use a custom recovery or directly flash using fastboot?
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
You need to be on correct firmware version (KK or LP) to flash correctly.
-Extract correct firmware using Huawei Update Extractor (127-137SP03), and highlight boot, recovery img
-Power down device and do Volume - and Power with usb plugged (to enter rescue mode)
-Shift + right click inside adb/fastboot folder (to open command prompt)
-Type: adb devices (to make sure it recognizes, you should see your device number)
-Type: fastboot flash boot boot.img (wait a few seconds, success)
-Type: fastboot flash recovery recovery.img (wait few seconds again, success)
-Type: fastboot reboot (your device should reboot and flashed to the firmware you chose.
---------- Post added at 03:38 PM ---------- Previous post was at 03:35 PM ----------
jfer671 said:
You need to be on correct firmware version (KK or LP) to flash correctly.
-Extract correct firmware using Huawei Update Extractor (127-137SP03), and highlight boot, recovery img
-Power down device and do Volume - and Power with usb plugged (to enter rescue mode)
-Shift + right click inside adb/fastboot folder (to open command prompt)
-Type: adb devices (to make sure it recognizes, you should see your device number)
-Type: fastboot flash boot boot.img (wait a few seconds, success)
-Type: fastboot flash recovery recovery.img (wait few seconds again, success)
-Type: fastboot reboot (your device should reboot and flashed to the firmware you chose.
Click to expand...
Click to collapse
Sorry, make sure to put extracted boot/recovery img files into adb/fastboot folder, and then proceed with Shift + right click

[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

[Guide] Mate 20 X root is here

Thanks to @topjohnwu, magisk canary builds officially support emui 9, albeit with some caveats.
Note:
This root requires replacing stock recovery with patched magisk init, which will then boot system with magisk support. This means that currently, TWRP or stock recovery and magisk can't exist simultaneously. Also, in order to boot with root, you will NEED to hold down VOLUME UP as the phone is rebooting or booting until the "device is booting" text is displayed. This tells the phone to boot into recovery, which is taken over by magisk init and booted into system with root. Failure to do this will result in the phone booting WITHOUT root or magisk.
I've gone ahead and patched the recovery_ramdisk for EVR-AL00 and EVR-L29.
What is needed:
ADB/fastboot
A computer
A bit of know-how
Step 1: You MUST be bootloader unlocked
-Start by downloading the relevant recovery ramdisk for your variant the AND magisk manager below
Step 2:
-Install the magisk manager
Step 3:
-Copy the recovery ramdisk to a folder with fastboot. Those with environment set up for adb/fastboot can ignore this step.
Step 4:
-Reboot your device to the bootloader. This is accomplished easiest with the adb reboot bootloader command. If you would like to gracefully put the device in bootloader mode, simply power off the device, remove all USB cables from it, but make sure one is plugged into your PC. Once the device is fully powered off, hold down the volume-DOWN key and then press and hold the power button and IMMEDIATELY plug the USB-C cable into the phone.
Step 5:
-Once the device is in bootloader and connected to the PC, run the command "fastboot flash recovery_ramdisk recovery_ramdiskMagiskVARIANT" with VARIANT being whatever ramdisk you downloaded. For example with AL00 you would input "fastboot flash recovery_ramdisk recovery_ramdiskMagiskAL00.img"
Step 6:
-Run the command "fastboot reboot" and immediately disconnect the USB-C cable from the phone. At this point you will want to hold down VOLUME-UP until the "device is booting" message is displayed.
Step 7:
-Once the system is booted, open magisk manager and profit.
Download:
Patched Recovery Ramdisk for EVR-AL00
Patched Recovery Ramdisk for EVR-L29
Stock Recovery Ramdisk for EVR-AL00
Stock Recovery Ramdisk for EVR-L29

All Mate 20 X users can now rejoice with root! Working perfectly here on AL00 20 X. Thank you @freeza :good:

Thank you freeza!
I saw you didn't have a link to the patched L29 so I patched mine and everything is perfect.
If anybody wants to use it or if you want to link it on the OT, it's fine.
Patched Recovery Ramdisk EVR-L29

Thanks bro @freeza
Sent from my iPhone using Tapatalk Pro

@freeza is the man!

Those who have rooted their phones. Can you guys still use Mobile Banking apps with no problem as well as finger print scanner?

Thank you freeza!
all this img version 166 ?

I just smashed the hell out of your thanks meter! Thanks!
Do module's install correctly from the magisk manager app?

lawtq said:
I just smashed the hell out of your thanks meter! Thanks!
Do module's install correctly from the magisk manager app?
Click to expand...
Click to collapse
Yes they do.

antiochasylum said:
Yes they do.
Click to expand...
Click to collapse
Omg. Thanks, that'll do!
So all we're missing is twrp. Bravo

Thanks man... Working good here! I did notice that EMUI update wants to fix some files. It says unauthorized files to some apps have been changed. Is it ok to let system EMUI update again?

lightning413 said:
Thank you freeza!
I saw you didn't have a link to the patched L29 so I patched mine and everything is perfect.
If anybody wants to use it or if you want to link it on the OT, it's fine.
Patched Recovery Ramdisk EVR-L29
Click to expand...
Click to collapse
How did you unlock the bootloader for L29?. I am using L29 but on mine the oem unlock is grayed under developer options.

lawtq said:
I just smashed the hell out of your thanks meter! Thanks!
Click to expand...
Click to collapse
Exactly what I just did.
Thanks a lot - this was one of the few things keeping me from pulling the trigger :victory:

msy198 said:
How did you unlock the bootloader for L29?. I am using L29 but on mine the oem unlock is grayed under developer options.
Click to expand...
Click to collapse
Use the guide below
How to unlock Mate 20 X bootloader EVR-L29

This is great news! My only concern is does having root break anything?

Steamer2499 said:
Thanks man... Working good here! I did notice that EMUI update wants to fix some files. It says unauthorized files to some apps have been changed. Is it ok to let system EMUI update again?
Click to expand...
Click to collapse
It says that cause it detected root. Even if you choose to let it update, it will fail since the patched ramdisk replaces the recovery.

Doesn't work for me. I got this after holding volume up. AL00

abbas said:
Doesn't work for me. I got this after holding volume up. AL00
Click to expand...
Click to collapse
That means you didn't flash it correctly as your stock recovery was not replaced. You might have missed a step

VeNuMuS said:
It says that cause it detected root. Even if you choose to let it update, it will fail since the patched ramdisk replaces the recovery.
Click to expand...
Click to collapse
Thx... It must wants to do a complete restore because download size is 4.3gb
---------- Post added at 12:45 PM ---------- Previous post was at 12:40 PM ----------
abbas said:
Doesn't work for me. I got this after holding volume up. AL00
Click to expand...
Click to collapse
That's what happened to me the first time. I think I didn't let go of the volume up button sooner the first time...

Thanks. It worked now. I think the Huawei Find my phone needed to be disabled.

EMUI 9.1.0.332 (C432) download

Hi, I had to recover my tablet and it updated to 9.1.0.332. My Magisk patched recovery_ramdisk from a previous version (9.0.x) is no longer working so I'm trying to find a download for a 9.1.0 EMUI ROM. The Firmware Finder doesn't find it and I can't find it through their website either. 9.0.x seem to be the latest I can find.
Not sure how else I can get root back, can I pull an image from the partition itself to patch it with Magisk and flash it with fastboot? I'm reluctant to flash anything (like TWRP for example) as long as I don't have the original firmware to extract and restore the original partitions.
Thanks for the help!

Which tablet version do you have? I have SHT-W09 and I can you provide with a download link for the firmware.
Unfortunately I do have 9.1.0.331 as latest version received on my tablet otherwise I could also provide a patched recovery_ramdisk.img if you have the same model.

My model is 10" wifi only CMR-W09 C432.
I found the full firmware and I have a Magisk patched recovery_ramdisk if anyone wants it.
Link to shared folder with all 3 files.
Direct link to full firmware CMR-W09 EMUI 9.1.0.332 (C432E5R1P3T8).
Direct link to patched recovery_ramdisk.
Direct link to original recovery_ramdisk.

I just have a weird issue getting to boot with Magisk activated. I used to just hold volume up during reboot up until the Huawei boot logo and release. I'd see the three options in yellow and it would continue to boot. Magisk would be active.
Now, I seem to only get Magisk activated with a USB cable hooked up and I am never sure how exactly I did it. When I think I got it, next time it will fail and Im struggling again with pushing volume buttons and powering off/on rebooting. I seem to have the most luck with both volume up and down when the tablet is powered off but that fails most of the time too.
Most of the time I just end up in EMUI recovery (which fails) and need to reboot again.
What exactly is the procedure? Did it change with EMUI 9.1 updates?
Thanks for the help.
Edit: recording this for my own sanity: just now got Magisk activated by powering off with USB disconnected, hold volume up & down simultaneously and connect USB. Release both volume buttons at the Huawei boot logo.

droidvark said:
I just have a weird issue getting to boot with Magisk activated. I used to just hold volume up during reboot up until the Huawei boot logo and release. I'd see the three options in yellow and it would continue to boot. Magisk would be active.
Now, I seem to only get Magisk activated with a USB cable hooked up and I am never sure how exactly I did it. When I think I got it, next time it will fail and Im struggling again with pushing volume buttons and powering off/on rebooting. I seem to have the most luck with both volume up and down when the tablet is powered off but that fails most of the time too.
Most of the time I just end up in EMUI recovery (which fails) and need to reboot again.
What exactly is the procedure? Did it change with EMUI 9.1 updates?
Thanks for the help.
Edit: recording this for my own sanity: just now got Magisk activated by powering off with USB disconnected, hold volume up & down simultaneously and connect USB. Release both volume buttons at the Huawei boot logo.
Click to expand...
Click to collapse
Hello Droidvark, thanks for the file links above, which have been very helpful. However, like you, I struggle to get my M5 pad to boot into (magisk) recovery, not erecovery, and I just don't seem to manage to do it anymore. Either I end up in unrooted mode or erecovery or some huawei usb update screen.
Can anybody help and let me know how I can boot my M5 mediapad into magisk/root/recovery mode? It used to work in the past by pressing the power and volume up buttons until the huawei/android logo appears, but over the last few days it hasn't worked anymore. I did upgrade to magisk 20.4 during that time, and emui 9.1 from 9.0, with the latter being the more likely culprit.
Anyway, I'm very grateful for any advice and help. Cheers, David
---------- Post added at 04:04 AM ---------- Previous post was at 03:11 AM ----------
spoo333 said:
Hello Droidvark, thanks for the file links above, which have been very helpful. However, like you, I struggle to get my M5 pad to boot into (magisk) recovery, not erecovery, and I just don't seem to manage to do it anymore. Either I end up in unrooted mode or erecovery or some huawei usb update screen.
Can anybody help and let me know how I can boot my M5 mediapad into magisk/root/recovery mode? It used to work in the past by pressing the power and volume up buttons until the huawei/android logo appears, but over the last few days it hasn't worked anymore. I did upgrade to magisk 20.4 during that time, and emui 9.1 from 9.0, with the latter being the more likely culprit.
Anyway, I'm very grateful for any advice and help. Cheers, David
Click to expand...
Click to collapse
'adb reboot recovery' did the trick and all is well now. It's possible the first magisk ramdisk patching wasn't successful on top of that.

spoo333 said:
Hello Droidvark, thanks for the file links above, which have been very helpful. However, like you, I struggle to get my M5 pad to boot into (magisk) recovery, not erecovery, and I just don't seem to manage to do it anymore. Either I end up in unrooted mode or erecovery or some huawei usb update screen.
Can anybody help and let me know how I can boot my M5 mediapad into magisk/root/recovery mode? It used to work in the past by pressing the power and volume up buttons until the huawei/android logo appears, but over the last few days it hasn't worked anymore. I did upgrade to magisk 20.4 during that time, and emui 9.1 from 9.0, with the latter being the more likely culprit.
Anyway, I'm very grateful for any advice and help. Cheers, David
---------- Post added at 04:04 AM ---------- Previous post was at 03:11 AM ----------
'adb reboot recovery' did the trick and all is well now. It's possible the first magisk ramdisk patching wasn't successful on top of that.
Click to expand...
Click to collapse
'adb reboot recovery' doesn't always work either. Once again stuck ... anybody have an idea how to enter magisk patched recovery? thx

spoo333 said:
'adb reboot recovery' doesn't always work either. Once again stuck ... anybody have an idea how to enter magisk patched recovery? thx
Click to expand...
Click to collapse
Hey,
You can install apk name Rashr and then there is option to go to recovery try that once and let me know what does it do.
Sent from my P5 mini using premium XDA app

PrashannaGP said:
Hey,
You can install apk name Rashr and then there is option to go to recovery try that once and let me know what does it do.
Sent from my P5 mini using premium XDA app
Click to expand...
Click to collapse
llello PrashannaGP,
thanks for trying to help. As expected, the app doesn't start up as it it needs root access. If I could boot into the magisk enabled recovery, then Magisk itself would also provide the option to boot into recovery. Without root access, neither of those two apps can offer that function
The problem is getting the pad to boot the magisk patched recovery partition once, then I'd be in business.

spoo333 said:
llello PrashannaGP,
thanks for trying to help. As expected, the app doesn't start up as it it needs root access. If I could boot into the magisk enabled recovery, then Magisk itself would also provide the option to boot into recovery. Without root access, neither of those two apps can offer that function
The problem is getting the pad to boot the magisk patched recovery partition once, then I'd be in business.
Click to expand...
Click to collapse
Please refer to this page.
https://huaweiflash.com/how-to-install-twrp-recovery-on-huawei-mediapad-m5/
Unfortunately I forgot that you have no root access.
Does your USB cable work well and
Works this code??
adb kill-server
adb devices
adb reboot
adb reboot bootloader
fastboot devices
fastboot flash recovery [downloaded twrp file]
fastboot reboot
adb reboot recovery
Try that post and if something went wrong I am responsible and will be happy to help you.
Sent from my P5 mini using XDA-Developers Legacy app

PrashannaGP said:
Please refer to this page.
https://huaweiflash.com/how-to-install-twrp-recovery-on-huawei-mediapad-m5/
Unfortunately I forgot that you have no root access.
Does your USB cable work well and
Works this code??
adb kill-server
adb devices
adb reboot
adb reboot bootloader
fastboot devices
fastboot flash recovery [downloaded twrp file]
fastboot reboot
adb reboot recovery
Try that post and if something went wrong I am responsible and will be happy to help you.
Sent from my P5 mini using XDA-Developers Legacy app
Click to expand...
Click to collapse
thank you for your help and offer to help me out (further) in case things went belly up. Don't know if it was your detailed description or downgrading Magisk to 20.3 (apparently there is some issue with bootloops or similar on my device and a few others), but it's working again )) I got my rooted pad back and I'm happy and grateful!!
For other users with a Mediapad M5 running Emui 9: remember to use fastboot flash recovery_ramdisk [magisk_patched.img] as per Magisk installation guide for Emui 9+ instead.

spoo333 said:
thank you for your help and offer to help me out (further) in case things went belly up. Don't know if it was your detailed description or downgrading Magisk to 20.3 (apparently there is some issue with bootloops or similar on my device and a few others), but it's working again )) I got my rooted pad back and I'm happy and grateful!!
For other users with a Mediapad M5 running Emui 9: remember to use fastboot flash recovery_ramdisk [magisk_patched.img] as per Magisk installation guide for Emui 9+ instead.
Click to expand...
Click to collapse
its my pleasure mate no worries now!

How to root OPPO Find X2 Lite

Hello I want to root my phone because I use AAmirror (android auto mirror) in my car
I unlock boot loader tried KingRoot, KingoRoot, TowelRoot, I tried to install under ColorOs Recovery Magisk or SuperSu nothing work
Maybe solution could be to modify an existing original rom (I have last one) and flash it ?
It's a very good 5G phone for price but seems alone
thank you

Anyone successful with magisk? I wanted to unlock bootloader, but got stuck with the oppo chinese website not doing what I expected... I read somewhere it's not possible to replace recovery ROM with TWRP, but it's possible to boot it using ADB or Fastboot once. Has anyone been successful, can you share how-to?

nznatty said:
...using ADB or Fastboot once...
Click to expand...
Click to collapse
Perhaps something similar to:
(ROOT) Android 11 / Latest stock and patched img's / payload dumper / magisk_patched guides
Hi all, Have seen a lot of requests for patched boot images on these threads so thought i'd share a guide on how to get it yourself as well as all the files required, plus the patched boot.img if you just want to go ahead and boot/flash it...
forum.xda-developers.com

nznatty said:
Anyone successful with magisk? I wanted to unlock bootloader, but got stuck with the oppo chinese website not doing what I expected... I read somewhere it's not possible to replace recovery ROM with TWRP, but it's possible to boot it using ADB or Fastboot once. Has anyone been successful, can you share how-to?
Click to expand...
Click to collapse
hey..
this device is enter to fastboot mode.? when i use the command ; "adb reboot bootloader" device is try to enter fb mode but screen appears then gone..and rebooting to normal mode..i think e need patched aboot or boot or sth like that..

t-mobile_mda said:
hey..
this device is enter to fastboot mode.? when i use the command ; "adb reboot bootloader" device is try to enter fb mode but screen appears then gone..and rebooting to normal mode..i think e need patched aboot or boot or sth like that..
Click to expand...
Click to collapse
That's my experience so far too. I can't get the phone rooted, I think i'll put it back on ebay.

Looking to get that device for testing, I found this which may help: https://forum.xda-developers.com/t/magisk-root-install-with-unlocked-bootloader.4157327/