Database Info

Tell me I've not bricked my Xoom!!!

I've just tried to root my wifi only Xoom using the 1 click method, but didn't see there was a tab for wifi only & a 3G tab. I went through the options using the 3G options.
Now my Xoom's stuck at the red Motorola screen & won't go any further.
Are there any threads to reverse my balls up?? I've had a look but can't see anything
Please tell me I've not bricked it?!?

tell me why you posted this in the wrong section

I could tell you that it's not bricked...but then I might be lying.

Moved to Q&A. This is not development.

You will need to adb and flash recovery then flash the rom again.
Sent from my PC36100 using Tapatalk

PaulG1488 said:
tell me why you posted this in the wrong section
Click to expand...
Click to collapse
Sorry, I didn't realise I'd put it in the wrong place.
Do you know if I've stuffed my Xoom?
thanks

alex2792 said:
You will need to adb and flash recovery then flash the rom again.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Do you know how I do this. I can't get adb working??

So the Xoom isn't recognizes when you type adb devices?
Sent from my PC36100 using Tapatalk

alex2792 said:
So the Xoom isn't recognizes when you type adb devices?
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
It's ok alex, I've managed to get the stock boot & system images on it again. Just updating to 3.1 again now.

clemo71 said:
It's ok alex, I've managed to get the stock boot & system images on it again. Just updating to 3.1 again now.
Click to expand...
Click to collapse
how do you solved ? ive the same problem on my xoom...

davidebeatrice said:
how do you solved ? ive the same problem on my xoom...
Click to expand...
Click to collapse
clemo71 said:
It's ok alex, I've managed to get the stock boot & system images on it again. Just updating to 3.1 again now.
Click to expand...
Click to collapse
Please let us poor souls know how you did it!!! I am stuck with the same problem - the screen freezes with the Motorola logo and the tablet wouldn't boot up!

For those still having issues, try going into fastboot and flashing the stock images.
You can access fastboot by restarting your xoom (power and vol up) and then once the red M comes up, tap the volume down key around a second later. You have a decent window of opportunity to press the key. This should take you to the bootloader. Once in there, use the volume down key to enter fastboot.
From fastboot you can either flash a custom recovery then from the recover install the BRD 3.1 rooted update, or you can just use the fastboot flash command to flash each partition back to stock.
Good luck.

willverduzco said:
For those still having issues, try going into fastboot and flashing the stock images.
You can access fastboot by restarting your xoom (power and vol up) and then once the red M comes up, tap the volume down key around a second later. You have a decent window of opportunity to press the key. This should take you to the bootloader. Once in there, use the volume down key to enter fastboot.
From fastboot you can either flash a custom recovery then from the recover install the BRD 3.1 rooted update, or you can just use the fastboot flash command to flash each partition back to stock.
Good luck.
Click to expand...
Click to collapse
Thanks . I have now installed custom recovery (ClockworkMod 3.0.2.8) but where do I get the rooted or stock ROM from? I suppose it has to be in a *.zip format.

Need help. I think its dead.

I have an AL-10 64GB mate 8. I wanted to turn it to the iternational ROM to have google apps. I followed this guide: http://forum.xda-developers.com/mate-8/general/howto-load-international-mate-8-t3293619
Afte flashing with fastboot commands the files my phone doesn't boot up. It shows the warning screen because it is Unlocked but I doesn't boot in menu.

u forgot to flash boot.img, try that through fastboot as well and then try and boot again

jbmc83 said:
u forgot to flash boot.img, try that through fastboot as well and then try and boot again
Click to expand...
Click to collapse
There isn't a boot.img in the thread there. Where do I find it?

So I thought to try myself something... I flashed the oldest boot.img from this thread: http://forum.xda-developers.com/mate-8/orig-development/kernel-insecure-boot-img-t3311306 (B156 FLASHABLE IMG). The only difference now is that it remains stuck at the warning scrren. Previously that screen would dissapear and the phone would be total black.

Also I downloaded the update.app from here: http://forum.xda-developers.com/mate-8/general/nxt-l09-nxt-l29-stock-rom-b133-download-t3311839 of L29. Extracted boot,cache,cust,system,recovery,userdata from that package and flashed all files with fastboot. Everything successful but still stucked at warning screen.

eltarod said:
Also I downloaded the update.app from here: http://forum.xda-developers.com/mate-8/general/nxt-l09-nxt-l29-stock-rom-b133-download-t3311839 of L29. Extracted boot,cache,cust,system,recovery,userdata from that package and flashed all files with fastboot. Everything successful but still stucked at warning screen.
Click to expand...
Click to collapse
try this first
1- go to recovery then factory reset then reboot if not booting so try this method below (use same update.app file)
rowihel2012 said:
Download the update file
Extract
Folder "dload" at the root level of the memory Share (internal or external).
Update.app in the folder "dload" Copy
As Huawei has removed the item "Local Update" from the update program, you must do the following:
Option 1: update via ForceUpdate
Switch off
Simultaneously Power + Volume Down + volume Louder press until the update starts
Click to expand...
Click to collapse

dload doesn't work. I did manage to install TWRP though... Will try to flash a custom ROM

So I managed to make it boot using DarkSilentSC instruction: http://forum.xda-developers.com/mat...ng-to-b321-t3375934/post66776218#post66776218
Only 2 problems left. First the memory shows 4GB rather than 64GB and there is no theme support. Any idaes?

hmmm....try and go to recovery and format the data partition, maybe that helps.... just make sure u dont have any important data on the phone before u do that

Data partition is:
TWRP - wipe - advanced wipe - tick data and slide to start?
Sent from my HUAWEI NXT-L29 using Tapatalk

Nevermind I did it thanks to jbmc83. The solution for anyone that has the same problem is to format data partition. It's in twrp-wipe the right button. Thanks to jbmc83 and to all that helped me!!
Sent from my HUAWEI NXT-L29 using Tapatalk

yep thats correct although i think ull have to type "yes" in order to start it. in any case, just follow the screen instructions! also, be aware that this takes a lot of time, so wait at least half an hour before giving up ^^ let it run its course!
edit: ah ok, i just saw that it worked! glad it did

Huawei mate 8, hard bricked while it's updating. Pho
Huawei mate 8, hard bricked while it's updating custom rom. Phone is not responding at all. No power, black screen, it i put on charging, doesn't feeling like battery charging. Can someone help me out this problem.

Yes, if you can go into bootloader mode, kindly run these commands and report back what are the results.
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem get-build-number

dear phone doesn't respond at all. not connecting to pc. no sign of power.

Syd2Ldh said:
dear phone doesn't respond at all. not connecting to pc. no sign of power.
Click to expand...
Click to collapse
Which rom were you try to flashing which caused this issue?

Very hard brick

Hi!
Okay, this case is really weird and of course is thanks to my negligence. I'm gonna post it hoping someone can help me, or at least keep other people aware about trying stupid things lol
I tried to update to Nougat with an unofficial method (I don't consider necessary to tell what method...) and I just messed it up, badly. I'll try to give a detailed explanation:
The phone has the bootloader unlocked. After trying to update to Nougat, it got stuck when rebooting. After the unlocked bootloader warning message, the phone won't go further than that, it just stays there. If I hold and press the power button for more than 10 seconds the phone won't shut down, it will restart to get stuck again after the unlocked BL warning, making impossible to turn it off completely.
I try to enter to stock recovery by pressing vol + and power button at the same time (tried other combinations, vol - and power button & vol -, vol + and power button) but I have no luck, it just gets stuck at the same point.
I already tried extracting BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img from an official update.app and flash them in that order via fastboot (yeah, I can enter to fastboot mode). The process is successful in terminal (I use Linux) but when I reboot the phone, it gets stuck again after the warning.
The only recovery that is actually working is TWRP, the one ported for the Honor 8 (flashed via fastboot), but it won't let me install any custom ROM, it just stays in "patching image unconditionally" forever, making me press and hold the power button but this won't shutdown the phone, it reboots, gets stuck and... so on *infinite loop*
Btw, when I wipe cache, dalvik and data in TWMP, the message "failed to mount /cust" with red letters appears, so it's probably a very corrupted system partition. also, It's impossible to repair the custom partition. This appears:
Repairing Custom using e2fdck...
/sbin/e2fsck -fp /devblock/mmcblk0p44 process ended with ERROR: 8
Unable to repair Custom.
Click to expand...
Click to collapse
Tried HiSuite from Huawei (in Windows) and it doesn't even recognize the phone.
Hope somebody could possibly give a solution, if there's any. If not, I'm afraid I have a beautiful paperweight now...
Oh yeah, one very important part: my Honor 8 is the US version (FRD-L04), and yes, I'm making sure I'm getting the current update.app for this model.
Any help would be greatly appreciated. Thanks in advance.

Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this

chongns said:
Hi There
you try this method.
Get a SD CARD
make a directory at the card root name dload
put your best update.app in the directory (the most older version the best)
insert into your phone 2nd sim slot
try everyway to make the 3 button combo.
hope this help
edit: you need stock recovery to do this
Click to expand...
Click to collapse
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons... But I'll try it.
Edit: Trying your method right now, hope it goes well...

El Brillantinas said:
Hey, thanks!
unfortunately, as far as I know is that for this method I have to enter to stock recovery, but then again, I can't get in. The phone gets stuck trying any combination of pressed buttons...
Click to expand...
Click to collapse
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Edit: Fastboot erase {partition} before flash back the image maybe help

chongns said:
Yes, but since you r able to go into TWRP, can your use adb command like adb reboot bootloader than flash stock recovery image?
after that since it is keep rebooting, you can hold your volume up and down all the way to force update.
IDK if this work. but no harm to try it, since it is "very hard brick"
Click to expand...
Click to collapse
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Software install failed!
Get help from: http//www.emui.com/emotionetcetc.
Click to expand...
Click to collapse

El Brillantinas said:
Yep, I'm trying it now and right now is installing the update (the EMUI logo with the circular progress bar). Hope it works *crossed fingers*
Edit: No luck. After the process finished, it says:
Click to expand...
Click to collapse
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access

chongns said:
I assume you having the update.app from a L04 full firmware, not the OTA.
for the not able to repair partition like custom maybe you can erase it using fastboot erase command and fastboot flash it back
or you can fastboot erase all the known partition like system, cache, data, custom etc.... and fastboot flash back the image.
i assume your fastboot still able to access
Click to expand...
Click to collapse
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!

El Brillantinas said:
I did it!!
I could bring it back following some of your methods. Here's how I achieved it:
-Formatted the Custom partition in fastboot.
-Flashed BOOT.img, RECOVERY.img, CUST.img and SYSTEM.img again.
-Forced the update by putting the entire firmware in the dload folder located in the sdcard, it failed at the end, but I rebooted by pressing and holding the power button.
-The phone passed beyond the point where it was getting stuck (finally!), but now it got stuck in the Honor 8 blue screen. Rebooted it again doing coldboot.
-Entered to stock recovery, wiped everything.
Then I just rebooted it and Voalá! It started all new!
Guess it was not that hard brick haha. I'll have to change the name of the topic.
A million thanks @chongns, you rock!
Click to expand...
Click to collapse
Good to know you succeed.
please tag a moderator to move your thread to Guide, News and Discussion section..
most of the time ppl search solution at there.

Guide in another Huawei phone XDA forum.
http://forum.xda-developers.com/mate-8/general/fuss-debrick-restore-mate-8-t3457969

Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.

Glad you fixed it bro. That was very critical.

El Brillantinas said:
Moderatos, can you please move this topic to the Guides and discussion section? Thanks in advance.
Click to expand...
Click to collapse
good to hear u go phone back , and there is another guides already exist to restore a framware throw the same method , thank you for sharing ur experience .

Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated

bho01 said:
Here's the issure I'm having. My Honor 8 FRD-L04 is stuck at a hard brick. It won't reach the recovery. I tried to flash images using fastboot. But I end up with the error: FAILED (remote: Command not allowed)
Any help would be appreciated
Click to expand...
Click to collapse
Is your frp status lock in fastboot?

faizalotai said:
Is your frp status lock in fastboot?
Click to expand...
Click to collapse
No it's unlocked

bho01 said:
No it's unlocked
Click to expand...
Click to collapse
Your phone status?

faizalotai said:
Your phone status?
Click to expand...
Click to collapse
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images

bho01 said:
Still can't get into recovery and I'm still getting the "FAILED(Command not allowed)" error whenever I try to flash stock images
Click to expand...
Click to collapse
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.

Try using the dload method of flashing

faizalotai said:
I mean your phone status in fastboot.
Its comes with frp and phone status..both have to be unlocked in order to flash images.
Click to expand...
Click to collapse
Also unlocked

peter twrp replaced by stock after first boot

I unlocked bl and flashed Peter twrp using command fastboot flash recovery recovery. img it shows success. Now if I go to twrp from fastboot directly via vol. Up + power it will boot to twrp as normal but after first boot it automatically replaced by stock mi recovery 3.0? What should I do now?

hackermssharma said:
I unlocked bl and flashed Peter twrp using command fastboot flash recovery recovery. img it shows success. Now if I go to twrp from fastboot directly via vol. Up + power it will boot to twrp as normal but after first boot it automatically replaced by stock mi recovery 3.0? What should I do now?
Click to expand...
Click to collapse
Try flashing it once more and this time try switching off the phone and then reboot to recovery..

Naveenthemi said:
Try flashing it once more and this time try switching off the phone and then reboot to recovery..
Click to expand...
Click to collapse
Can u please elaborate? After flashing i used fastboot reboot command and after just that by vol + button i entered in twrp but it will still replaced by stock after first boot.
I also did after flashing reboot to system from fastboot screen and then try to boot via vol.+ and power button but it will get replaced.

hackermssharma said:
Can u please elaborate? After flashing i used fastboot reboot command and after just that by vol + button i entered in twrp but it will still replaced by stock after first boot.
I also did after flashing reboot to system from fastboot screen and then try to boot via vol.+ and power button but it will get replaced.
Click to expand...
Click to collapse
What I meant was, flash the TWRP again( this time try 3.3.1-5), once flashed power off the device, now try booting into TWRP, now boot to system and check if it still gets replaced...

Naveenthemi said:
What I meant was, flash the TWRP again( this time try 3.3.1-5), once flashed power off the device, now try booting into TWRP, now boot to system and check if it still gets replaced...
Click to expand...
Click to collapse
How to power off from fastboot after flashing twrp?

hackermssharma said:
How to power off from fastboot after flashing twrp?
Click to expand...
Click to collapse
Hold the power button for long enough and I personally think flashing 3.3.1-5 would fix this as some people have reported issues like this only after flashing to 3.3.1-6

Naveenthemi said:
Hold the power button for long enough and I personally think flashing 3.3.1-5 would fix this as some people have reported issues like this only after flashing to 3.3.1-6
Click to expand...
Click to collapse
Fixied after formating the data before first boot.
Sent from my Redmi Note 7 Pro using XDA Labs

hackermssharma said:
Fixied after formating the data before first boot.
Click to expand...
Click to collapse
Format!? Never had to do that on Peter's..

Naveenthemi said:
Format!? Never had to do that on Peter's..
Click to expand...
Click to collapse
Without formating it will always replaced by mi recovery i tried both 6 and 5 versions everything. Finally formating fixed the problem.
Sent from my Redmi Note 7 Pro using XDA Labs

hackermssharma said:
Without formating it will always replaced by mi recovery i tried both 6 and 5 versions everything. Finally formating fixed the problem.
Click to expand...
Click to collapse
Damn ok...

hackermssharma said:
Without formating it will always replaced by mi recovery i tried both 6 and 5 versions everything. Finally formating fixed the problem.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
How to format data
with fastboot command

gsunil said:
How to format data
with fastboot command
Click to expand...
Click to collapse
No install the twrp from fastboot then boot to twrp (by holding power + vol down) then in twrp formate the data ( dont wipe anything just formate).
Sent from my Redmi Note 7 Pro using XDA Labs

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!