UMIDIGI Android 9.0 ROOT - short guide not for beginners

bencebacsi

Those who have 'Waiting for device' issue after using a fastboot command, keep your phone connected to USB in fastboot mode, open the Windows Update settings page and look for updates there. The correct fastboot adb drivers will be downloaded and installed.

I don't recommend to use the twrp method, that's not reliable. Instead, follow the Magisk Installation tutorial, and you'll be successful.

Android74

bencebacsi replied at 2019-8-24 12:37
Those who have 'Waiting for device' issue after using a fastboot command, keep your phone connected  ...

bencebacsi ... also good for Umidigi F1play ... what the tutorial magisk? you could put the link ... thanks

Android74

bencebacsi replied at 2019-8-24 12:37
Those who have 'Waiting for device' issue after using a fastboot command, keep your phone connected  ...

why is it not reliable?
also Umidigi F1play

bencebacsi

Android74 replied at 2019-8-26 02:37
bencebacsi ... also good for Umidigi F1play ... what the tutorial magisk? you could put the link . ...

The link is in paragraph 2., it has always been there.

bencebacsi

Android74 replied at 2019-8-26 14:57
why is it not reliable?
also Umidigi F1play

Because while the system software gets new updates, so not always but sometimes new kernel versions as well, the recovery version will usually remain the same. Magisk always work with that system that you currently have installed if you follow the instructions in the Magisk root tutorial.

plumpkibbles

Ben, i got my A5 rooted. thank you - i over-looked one thing; but i was able to see my error when reading this quick guide. now both my A3 and A5 Pro's are rooted! i was confused by the two posts, one for 9, and one for a blanketed method for mostly all Umi devices. the A3 worked perfect, first time no issues - no data wipe. that's the part i was not expecting from the A5. i had used just the methods from getting the apk installed, patching the boot, and flashing the boot. but wasn't aware of the A5 being one of the phones in the list of the fastboot unlock options being a must. once i figured that out, all smooth. AND also had to update boot.img for Magisk 19.4 and was just as easy. just need to run patch tool, copy new boot.img to PC, flash, good to go.. now to get all my apps back lol

question about this rooting method - once a new firmware is available for the device (and others), will i have to re-do all of this; including the adb flashing unlock / wipe?
**update** i got the new software update for the A5 Pro. i did the update, lost root.. of course. now, bootloader was still unlocked, debug still enabled; i made another patch-boot.img from Magisk and went to flash the patched boot.img over to my phone.. when i loaded the scatter.txt file, i got a weird error saying that something doesn't match. i did the steps once more from beginning to end (the way that worked for me) and still no dice. i'm guessing that support for this has been stopped? or, maybe the new ROM doesn't allow?.. or is this a new encrypted partition style? either way - i don't think i'm going to be doing the root stuff anymore. most of my applications that 'required' root before, now just don't really need that option. i'm not saying the overclocking will work without root, because uh, it wont. still need root to change CPU governers. but, oh well! i can add this to the list of devices i've rooted since Android 1.5!

scyyie

Hi benci! I have a quick question regarding this A5 Pro rooting. I followed all of step 1...
1. Unlock the bootloader (will result in a factory data reset and a warning message on the boot screen)
   a) Enable Developer options
   b) Enable OEM unlock and USB debugging. (Install ADB drivers on your computer)
   c) Connect your phone to USB and in a command window type adb reboot bootloader
   d) Type fastboot flashing unlock
   e) Confirm your decision on the phone (You can re-lock the bootloader with fastboot flashing lock)
--------------

My problem is now, my phone will boot, say
"Orange State
Your devices has been unlocked and can't be trusted
Your devices will boot in 5 seconds" and it will reboot. then show that message again, and reboot over and over until i hold down the power button for maybe 10 seconds. It seems i have unlocked the bootloader but am now in a boot loop for some reason. I need help.

bencebacsi

plumpkibbles replied at 2019-8-29 13:33
Edited by plumpkibbles at 2019-9-1 03:35  

Ben, i got my A5 rooted. thank you - i over-looked one  ...

Hi,
Flashing patched boot images still works as same as before, even with the latest A5 Pro versions. What error message do you get exactly? 19.3 is the latest Magisk version at the moment. How could you update to 19.4?

bencebacsi

scyyie replied at 2019-9-3 21:42
Hi benci! I have a quick question regarding this A5 Pro rooting. I followed all of step 1...
1. Unlo ...

Hi,
Have you done anything else or only unlocked the boot loader?

plumpkibbles

bencebacsi replied at 2019-9-4 10:41
Hi,
Have you done anything else or only unlocked the boot loader?

exact steps i performed before the update: fastboot flashing unlock - confirm and reboot with wipe. initial setup finished, then enable USB Debug. get the 19.4 Magisk (updated version, same one i used before update too) installed, make a patch-boot.img from the 1.4...827 ROM from Magisk Manager - then copy over the patch-boot.img (i rename this to boot.img to avoid partition name issues), then load the scatter.txt file from the 1.4...827 ROM - then i'm issued an error stating that the ROM and the boot.img do not match. as i can't clear this error, i just flashed the 1.4...827 updated ROM directly, without root permissions of course. i'm unrooted and stock ROM at this time - i think i'm going to keep it this way, though.

i am, however, still experiencing issues with this single pixel-width green line on the left side of my display upon the transition to full brightness - i have the adaptive brightness turned on. when the photo sensor sees that the screen brightness doesn't match the ambient light, full brightness is achieved, but with this green line.

is there any reason i shouldn't be able to flash the EU ROM? i haven't seen much issues with people using that ROM and the green line issue - just wanted to check first. i'm currently using the Global ROM as that was flashed from factory. i'm more interested in seeing if the green line follows; and if so - that would give me an idea that my issue is hardware based and should be able to get this resolved through support - correct? BTW i have sent Support a message about my A5 green line issues but haven't received a response yet... if the 30 days run out for returning, who would be more at fault for communication?