Hi,
Since there is no available TWRP Recovery version for UMIDIGI A3S, so I have to root it by Magisk.
the following was what I did:
1, OEM(bootloader) unlocked. command C:\Users\user\Downloads\fastboot>fastboot flashing unlock
2, USB debugging actived.
3, down load factory ROM.
4, transferred MagiskManager-v7.5.1 and boot.img(from factory ROM) to A3S
5, open MagiskManager Patch a File, and selected boot.image file
6, flash the magisk_patched.img command C:\Users\user\Downloads\fastboot> fastboot flash boot magisk_patched.img
Then I fell in bootloop.
Help needed! thanks in advance.
// Johan
Looks like you've visited getdroidtips.. The tutorial was written by someone who never heard of signature verification. I had the same issue and had to restore the stock rom.
Follow the instructions on the Umidigi forum: https://community.umidigi.com/forum.php?mod=viewthread&tid=19502&extra=page=1
Related
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Spocki990 said:
Hi,
i have a problem rooting my Pixel 3.
it already worked, then i installed another rom which i did not like, so i re-installed the stock image from google (9.0.0 PQ1A.181205.006, Dec 2018).
But, here comes the problem, i can not install Magisk. When i do, my Pixel does not boot to system, but boots back to recovery or says can´t load android system.
this is how i do it:
1. flash factory image
2. boot to system
3. boot twrp
4. flash Magisk v18.0
also tried:
1. flash factory image
2. boot twrp directly
3. flash Magisk v18.0
this does not work. what i also tried is patch the stock boot.img with magisk and flash it to boot_a and boot_b. also did not work.
what am i doing wrong?
thnaks in advance for your help!
Click to expand...
Click to collapse
You've got the kernel and recovery messed up on your device from the failed flash of twrp and magisk. I would start over by flashing the factory image using the flash all batch file with the -w edited out of it. Then try again booting twrp, not flashing it. Once you try to flash the twrp image file you pretty much have to start over with the stock boot image. When you boot into twrp you'll want to allow modifications. You also need to setup a pin or pattern security for your system so twrp will decrypt your device.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Spocki990 said:
Thanks for the hint. It works now. But had to use the patched boot image from this link.
https://www.google.de/amp/s/forum.x...o-root-pixel-3-xl-magisk-t3856712/amp/?espv=1
Click to expand...
Click to collapse
you are my hero. My phone was stuck in the situation you describe after installing active edge. I was thinking about wipe my pixel 3 until I saw your post. Thank you !:good:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Use Sharp by the old process! Dont have to use twrp made for Android 9
Is a problem with a new security patch, i have one only and functional..
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Return at the v10.xxx rom stock, and can i flash twrp or orange fox recovery, but not all the version can i flash new's rom android 10 i have the same problem about 1 month & this is my solution :crying:
vjrx88 said:
Hi I recently updated my Mi A3 to May Android 10 update i.e. v11.0.15 . Before this it was rooted with TWRP and Magisk as now both of these softwares are gone due to update. Now i want to flash TWRP first but unable to install it as I changed the active slot to A (current B) as per old method but nothing happened and phone stucked at Fastboot screen. This thing really concerns me as if I flash twrp.img at slot B, does it boot properly? Other way around to root Mi A3 using Magisk manager by patching boot.img of V11.0.15. Where can i get this and is it a reliable method without flashing custom recovery like TWRP? Can i flash any other good custom recovery?
Click to expand...
Click to collapse
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
SidRose01 said:
Starting July im also facing the same issue. I restarted my phone but received a message that phone has been updated. Now TRWP and root is gone. I can't flast TWRP again on slot boot_a, also cannot flast twrp on boot_b. Stuck on Flashboot.
I was lucky to have the Stock boot img, i then flashed the Stock boot img on both slots a & b. But cannot flast TWRP anymore using ABD/fastboot
Solution: I flashed the new TWRP 3.4 for Android 10 from this link and now the problem is fixed!! https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
Click to expand...
Click to collapse
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
ovi2901 said:
in that post they said
"Note: enable "use rm -rf instead of formatting" in TWRP settings, before you wipe data, else userdata partition will be damaged"
what does it mean???
Click to expand...
Click to collapse
I only used the files from that link. I did not read it anything. But Thanks, you pointed this out.
This means that the next time I wipe data in TWRP, then I should first enable "use rm -rf instead of formatting" in TWRP settings
I have never tried 'wipe data' on this phone. But I'll remember this the next time I 'wipe data'. Thanks, you just saved me.
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?
Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE
All,
I'm looking for suggestions on how to restore root to my Huawei MediaPad M5. I recently updated Magisk to stable Manager 8.0.7 and Magisk build 21.4. However this caused me to lose root on the tablet. The tablet is on Android 8.0.
To restore root, I tried the following steps:
1) Downloaded Huawei tablet image 8.0.0, build 200, for the SHT-W09 (C567) USA model
2) Extracted Ramdisk image and copied over to the tablet
3) Opened Magisk and selected Download and Patch File
4) Magisk patched the file and saved it in my downloads folder
5) I then transferred the patch file back to my pc
6) Opened my Fastboot folder that had the patched image
7) Booted the tablet into fastboot mode and tested with command "fastboot devices"
8) After verifying I had a connection, I typed "Fastboot flash ramdisk patched_boot.img"
9) The file was flashed to the tablet
10) I rebooted the tablet, but I still don't have root
Any ideas, do I need to use the command "fastboot flash boot magisk_patched.img"?
Thanks,
Rick
Rick,
I managed to root my CMR W09 C567 EMUI 8.0.0.200 by flashing this older version of Magisk directly within TWRP:
Release Magisk v20.4 · topjohnwu/Magisk
Miscellaneous This release is mainly focused on stability and bug squashing. Please be aware that MagiskHide is no longer enabled by default. Since Google has enabled hardware-based key attestation...
github.com
It does all the work of patching the boot file withing TWRP, and when you reboot into system, there will even be a Magisk apk already installed. Do not upgrade afterwards.
The TWRP that works for me is:
[RECOVERY][UNOFFICIAL] TWRP 3.2.2-1
This is for the Mediapad M5. NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files. Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use...
forum.xda-developers.com
The command to flash:
./fastboot.exe flash recovery_ramdisk TWRP-3.2.2-1-MediapadM5.img
PS. You evidently need to have an unlocked bootloader. Mine was locked, but I managed to use the test point method and PotatoNV program. This requires removing the screen (I busted mine--had to replace from AlixExpress).
zentico said:
Rick,
I managed to root my CMR W09 C567 EMUI 8.0.0.200 by flashing this older version of Magisk directly within TWRP:
Release Magisk v20.4 · topjohnwu/Magisk
Miscellaneous This release is mainly focused on stability and bug squashing. Please be aware that MagiskHide is no longer enabled by default. Since Google has enabled hardware-based key attestation...
github.com
It does all the work of patching the boot file withing TWRP, and when you reboot into system, there will even be a Magisk apk already installed. Do not upgrade afterwards.
The TWRP that works for me is:
[RECOVERY][UNOFFICIAL] TWRP 3.2.2-1
This is for the Mediapad M5. NOTE: Decrypting data is not currently supported. MTP also does not work, but you can use adb to push and pull files. Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use...
forum.xda-developers.com
The command to flash:
./fastboot.exe flash recovery_ramdisk TWRP-3.2.2-1-MediapadM5.img
PS. You evidently need to have an unlocked bootloader. Mine was locked, but I managed to use the test point method and PotatoNV program. This requires removing the screen (I busted mine--had to replace from AlixExpress).
Click to expand...
Click to collapse
Hello zentico, is your M5 model SHT-W09?
I have a similar issue: after upgrading my SHT-W09 to latest 9.1.0.360 firmware I patched the recovery_ramdisk-image with Magisk v23.0 and it didn't boot :-(
I was able to pach the same image for recovery mode but in that case I had only limited root access. The only solution I found up to now: using the "old" patched recovery_ramdisk.image which was patched with Magisk v20.4
Edit: looks as if there are existing several C432-360 images. I got the LGRP4-OVS as this was the only version available on firmwarefinder but my device identifies as "P2" most likely that's the reason why it's not booting.
Gamblor2 said:
Hello zentico, is your M5 model SHT-W09
Click to expand...
Click to collapse
Mine is a CMR-W09.
C5Longhorn said:
All,
I'm looking for suggestions on how to restore root to my Huawei MediaPad M5. I recently updated Magisk to stable Manager 8.0.7 and Magisk build 21.4. However this caused me to lose root on the tablet. The tablet is on Android 8.0.
To restore root, I tried the following steps:
1) Downloaded Huawei tablet image 8.0.0, build 200, for the SHT-W09 (C567) USA model
2) Extracted Ramdisk image and copied over to the tablet
3) Opened Magisk and selected Download and Patch File
4) Magisk patched the file and saved it in my downloads folder
5) I then transferred the patch file back to my pc
6) Opened my Fastboot folder that had the patched image
7) Booted the tablet into fastboot mode and tested with command "fastboot devices"
8) After verifying I had a connection, I typed "Fastboot flash ramdisk patched_boot.img"
9) The file was flashed to the tablet
10) I rebooted the tablet, but I still don't have root
Any ideas, do I need to use the command "fastboot flash boot magisk_patched.img"?
Thanks,
Rick
Click to expand...
Click to collapse
Hi!
I have the exact same tablet, but I'm unable to find the full update to patch magisk and root it fully, where/how were you able to obtain the full ota and extract the image?
Mine is SHT-W09 8.0.0.200(C567)
Thanks!
How to root realme 7 a.89....i have a.87 vbmeta img file.but my device is a.89.is this vbmeta file work on my a.89. please help
I think you can flash a.87 vbmeta in a.89 because if any version of vbmeta is in a10 or you are in a10 then you can flash it there no problem because i tested it tell me if you have problems with
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
qeb said:
How to root realme 7 a.89....i have a.87 vbmeta img file.but my device is a.89.is this vbmeta file work on my a.89. please help
Click to expand...
Click to collapse
That vbmeta ( if it's patched ) can be used for all A10 builds. Which means u can use it with not only A87, A89. but all others RUI 1 available builds ( A83, A75....etc)
nabarun12 said:
hello guys, i'm having a problem here, I just installed a pixel plus ui and then installed the magisk app, then I renamed it to a zip file as mentioned in the website and went to flash it on my phone (Realme 7) after flashing successfully completed I pressed the reboot to system option, now it's stuck on the realme logo and doesn't budge anymore... I'm really worried please help me.
Click to expand...
Click to collapse
You can only do that with Permissive ROM builds, for Enforcing, you will need to patch boot.img manually with Magisk, then flash it into boot partition using fastboot command or custom recovery.