I've switched from my Lumia 928 to LG V20 (US996 unlocked) for 6 motnhs, and i loved it untill some **** happened. After the previous OTA update, my phone encounted radio off or no service issue. I find out this happened after reflashed the stock rom or OTA update, if you have this issue please follow these steps:
What you need:
US996 stock rom: http://lg-firmwares.com/category/lg-series/lg-v20/ (US99610f for unlocked ver.)
Patched LGUP for V20: https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
The lastest Super SU or Magisk (in case you need to pass the Safety Net for using Banking app, Android pay, etc.)
Modem file.
ADB, LG lastest driver.
I uploaded the nesscesary in here: https://drive.google.com/drive/folders/1pKKp78EqFwoCs5PuXi_2P-4_hsEx6u5_?usp=sharing
This tutorial will have 3 section: first you need to downgrade your phone to US99610f or this won't work. Next unlock your boot loader via dirtysanta n flasing TWRP. Then you flash the modem file and root your deviece with superSU or Magisk (optional).
I recommend you read this though out and pateintly following these step. You should backup your data before starting this. Do this at your own risk.
Downgrade to US99610f
If you are on the US99610n then you need to downgrade to US99610f cause you can't use dirtysanta on the US99610f (you can start from step 4 in case your phone is not soft bricked)
1. Completely Power off the v20 ( or to remove and put the battery back )
2. Plug the USB end of sync cable to your PC
3. Press and hold "Volume Up"
4. Plug in the USB-C end of sync cable to the v20. The phone will enter download mode (or Firmware Update). Now you can release the "Volume Up".
5. Run LGUP. The program will regconise the v20.
8. At the file path, click "..." and chose the .kdz file
9.Choose "UPGRADE"
10.Click "Start" and wait until the process is complete wait untill your phone boot up and there you are US99610f and still no service :silly:
Unlock Bootloader n' flashing TWRP
Turn on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times or spamming it until it's enabled):laugh:
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in Files transfer mode.
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
"This may void your warranty"
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
After your phone boot up:
1. copy twrp.img to your internal storage or SD card.
2. Start ADB and following these steps (just copy and paste):
https://github.com/jcadduono/android_external_dirtycow#running
3. Wait for it to complete and type:
Code:
reboot recovery
If you don't want to void your warranty please use the dirty santa by following this threat:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
In this threat you will unlock you boot loader n flashing recovery. Right after you've done step 3 and your phone boot up you can wait (I dont recommend you to wait for you phone boot up, mine have screen static after that so just following these step to enter TWRP we will fix it later):
1. unplug the cable right after the logo boot up
2. remove the battery.
3. boot your phone up while holding BOTH vol down and power key.
4. Briefly release the power key right after you saw the LG logo and press it back again.
5. untill your phone boot up use vol key and power key to select yes on both screen.
6. wait for you phone reboot and now you in TWRP.
7. Select cancel if the phone ask you for password and swipe to right to allow modifications.
Flashing modem, fix screen static and other.
Now put these files in your SD card or your internal storage with mount option in TWRP (Mount=> enable MTP): Modem.img, SuperSU or Magisk, kernel and boot2.img (in adb folder).
In TWRP:
1. Tap on "wipe" => format data => type "yes"
2. Go back to home menu then select “Reboot” then “Recovery”.
3. Once rebooted, swipe to right again.
4. Tap on “Install”.
5. Choose your microSD card or internal storage depend on where you copy those files.
6. Tap on "Install Image" and select "modem.img"
7. Select "modem" and Swipe to flash.
If you use dirtysanta method you need to flash "boot2.img" to fix the screen static. Similar to flashing "modem.img" but you select "boot" before swipe to flash.
8. Go back to home menu then select “Reboot” then “System”.
Wait for your phone boot up and the issue should be fixed.
Additional things
For more advance you can flash SuperSU or Magisk if you want to root you phone for more benefit.
Flashing kernel to fix your screen retention, screen static and more ( this won't cause SafetyNet failure that mean you can use android pay and banking app).
mk2000 kernel features:
Linux 3.18.85
KCAL - Screen panel control.
ElementalX and Zzmoove CPU governors.
Modules signed and secure, as in stock rom.
Disable software CRC checking of SD Card - More performance.
Fix by emdroidle for eng-bootloader (US996Santa, H990 & H910).
CRC32 and CHACHA20 HW ACC, CRNG based on CHACHA20.
Static screen fixed (US996Santa, H990 & H910).
Many patches that improves or fixes things.
Maple I/O scheduler.
LZ4 compression.
RCTD removed.
You need to flash kernel right after SuperSU/Magisk or before you reboot to system.
Update:
in case you want to upgrade to the lastest OTA you can follow this threat:
https://forum.xda-developers.com/v20/development/rom-us99610k-stock-rom-twrp-flashable-t3691784
And you need to reflash the "modem.img".
My thanks to:
@askermk2000 for his kernel.
@jcadduono, @me2151 for rooting guide.
hi ttnduy, thank you for creating this thread.
my lg v20 now is no service after i update from lg bridge. before i update via lg bridge i have to upgrade via OTA but fail. then i read a message to upgrade via lg bridge.
i have some questions:
1. i missed this step : "To unlock your bootloader, follow the unlock instructions on LG's site."
so my next step is :
"github.com/jcadduono/android...rtycow#running is that right?"
then after follwing "https://github.com/jcadduono/android...rtycow#running"
my next step is :
"If you don't want to void your warranty please use the dirty santa by following this threat:"
is that right?
2. can you please explain which one i must do(copy and paste) on this step :
github.com/jcadduono/android...rtycow#running
where i run this step? is on adb to copy and paste?
thank you very much
harry.wong said:
hi ttnduy, thank you for creating this thread.
my lg v20 now is no service after i update from lg bridge. before i update via lg bridge i have to upgrade via OTA but fail. then i read a message to upgrade via lg bridge.
i have some questions:
1. i missed this step : "To unlock your bootloader, follow the unlock instructions on LG's site."
so my next step is :
"github.com/jcadduono/android...rtycow#running is that right?"
then after follwing "https://github.com/jcadduono/android...rtycow#running"
my next step is :
"If you don't want to void your warranty please use the dirty santa by following this threat:"
is that right?
2. can you please explain which one i must do(copy and paste) on this step :
github.com/jcadduono/android...rtycow#running
where i run this step? is on adb to copy and paste?
thank you very much
Click to expand...
Click to collapse
1. If you already unlock your boot loader with LG unlocked file then after you do step 3 (type reboot recovery) then you can go straight to "Flashing modem, fix screen static and other" step.
2. Here what you need to copy n paste (Running part in the link):
Code:
adb push dirtycow /data/local/tmp
adb push recowvery-applypatch /data/local/tmp
adb push recowvery-app_process64 /data/local/tmp
adb push recowvery-run-as /data/local/tmp
adb shell
$ cd /data/local/tmp
$ chmod 0777 *
$ ./dirtycow /system/bin/applypatch recowvery-applypatch
"<wait for completion>"
$ ./dirtycow /system/bin/app_process64 recowvery-app_process64
"<wait for completion, your phone will look like it's crashing>"
$ exit
adb logcat -s recowvery
"<wait for it to tell you it was successful>"
"[CTRL+C]"
adb shell reboot recovery
"<wait for phone to boot up again, your recovery will be reflashed to stock>"
adb shell
$ getenforce
"<it should say Permissive, adjust source and build for your device!>"
$ cd /data/local/tmp
$ ./dirtycow /system/bin/run-as recowvery-run-as
$ run-as exec ./recowvery-applypatch boot
"<wait for it to flash your boot image this time>"
$ run-as su
#
From your root shell, it's possible to use commands such as:
Code:
dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery
ttnduy said:
I've switched from my Lumia 928 to LG V20 (US996 unlocked) for 6 motnhs, and i loved it untill some **** happened. After the previous OTA update, my phone encounted radio off or no service issue. I find out this happened after reflashed the stock rom or OTA update, if you have this issue please follow these steps:
What you need:
US996 stock rom: http://lg-firmwares.com/category/lg-series/lg-v20/ (US99610f for unlocked ver.)
Patched LGUP for V20: https://forum.xda-developers.com/v20/how-to/guide-patch-lgup-to-unlock-features-t3652222
The lastest Super SU or Magisk (in case you need to pass the Safety Net for using Banking app, Android pay, etc.)
Modem file.
ADB, LG lastest driver.
I uploaded the nesscesary in here: https://drive.google.com/drive/folders/1pKKp78EqFwoCs5PuXi_2P-4_hsEx6u5_?usp=sharing
This tutorial will have 3 section: first you need to downgrade your phone to US99610f or this won't work. Next unlock your boot loader via dirtysanta n flasing TWRP. Then you flash the modem file and root your deviece with superSU or Magisk (optional).
I recommend you read this though out and pateintly following these step. You should backup your data before starting this. Do this at your own risk.
Downgrade to US99610f
If you are on the US99610n then you need to downgrade to US99610f cause you can't use dirtysanta on the US99610f (you can start from step 4 in case your phone is not soft bricked)
1. Completely Power off the v20 ( or to remove and put the battery back )
2. Plug the USB end of sync cable to your PC
3. Press and hold "Volume Up"
4. Plug in the USB-C end of sync cable to the v20. The phone will enter download mode (or Firmware Update). Now you can release the "Volume Up".
5. Run LGUP. The program will regconise the v20.
8. At the file path, click "..." and chose the .kdz file
9.Choose "UPGRADE"
10.Click "Start" and wait until the process is complete wait untill your phone boot up and there you are US99610f and still no service :silly:
Unlock Bootloader n' flashing TWRP
Turn on developer options in Settings -> About device -> Software info -> Build number. (tap 7 times or spamming it until it's enabled):laugh:
Now navigate to Settings -> Developer options -> OEM unlock. (turn it on)
Don't ever turn OEM unlock or Developer options off when using a custom ROM or recovery. This could lose to loss of all your data.
For your computer to see ADB, you will need to put the phone in Files transfer mode.
To unlock your bootloader, follow the unlock instructions on LG's site (I can't really help you there):
"This may void your warranty"
https://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS
After your phone boot up:
1. copy twrp.img to your internal storage or SD card.
2. Start ADB and following these steps (just copy and paste):
https://github.com/jcadduono/android_external_dirtycow#running
3. Wait for it to complete and type:
Code:
reboot recovery
If you don't want to void your warranty please use the dirty santa by following this threat:
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
In this threat you will unlock you boot loader n flashing recovery. Right after you've done step 3 and your phone boot up you can wait (I dont recommend you to wait for you phone boot up, mine have screen static after that so just following these step to enter TWRP we will fix it later):
1. unplug the cable right after the logo boot up
2. remove the battery.
3. boot your phone up while holding BOTH vol down and power key.
4. Briefly release the power key right after you saw the LG logo and press it back again.
5. untill your phone boot up use vol key and power key to select yes on both screen.
6. wait for you phone reboot and now you in TWRP.
7. Select cancel if the phone ask you for password and swipe to right to allow modifications.
Flashing modem, fix screen static and other.
Now put these files in your SD card or your internal storage with mount option in TWRP (Mount=> enable MTP): Modem.img, SuperSU or Magisk, kernel and boot2.img (in adb folder).
In TWRP:
1. Tap on "wipe" => format data => type "yes"
2. Go back to home menu then select “Reboot” then “Recovery”.
3. Once rebooted, swipe to right again.
4. Tap on “Install”.
5. Choose your microSD card or internal storage depend on where you copy those files.
6. Tap on "Install Image" and select "modem.img"
7. Select "modem" and Swipe to flash.
If you use dirtysanta method you need to flash "boot2.img" to fix the screen static. Similar to flashing "modem.img" but you select "boot" before swipe to flash.
8. Go back to home menu then select “Reboot” then “System”.
Wait for your phone boot up and the issue should be fixed.
Additional things
For more advance you can flash SuperSU or Magisk if you want to root you phone for more benefit.
Flashing kernel to fix your screen retention, screen static and more ( this won't cause SafetyNet failure that mean you can use android pay and banking app).
mk2000 kernel features:
Linux 3.18.85
KCAL - Screen panel control.
ElementalX and Zzmoove CPU governors.
Modules signed and secure, as in stock rom.
Disable software CRC checking of SD Card - More performance.
Fix by emdroidle for eng-bootloader (US996Santa, H990 & H910).
CRC32 and CHACHA20 HW ACC, CRNG based on CHACHA20.
Static screen fixed (US996Santa, H990 & H910).
Many patches that improves or fixes things.
Maple I/O scheduler.
LZ4 compression.
RCTD removed.
You need to flash kernel right after SuperSU/Magisk or before you reboot to system.
Update:
in case you want to upgrade to the lastest OTA you can follow this threat:
https://forum.xda-developers.com/v20/development/rom-us99610k-stock-rom-twrp-flashable-t3691784
And you need to reflash the "modem.img".
My thanks to:
@askermk2000 for his kernel.
@jcadduono, @me2151 for rooting guide.
Click to expand...
Click to collapse
sir is this only applicable for US996? i have my v20 H91010I same issue after updates no signal and radio. i was waiting for threads like this but hopefully this will work for other variant
AceGed said:
sir is this only applicable for US996? i have my v20 H91010I same issue after updates no signal and radio. i was waiting for threads like this but hopefully this will work for other variant
Click to expand...
Click to collapse
Idk if this gonna work with H910 but you can try. If you still in warranty than you better turn it in. Btw you may need the modem file from other working H910.
You saved my ass and my US996, with your guide. Thanks!
I have this same issue on my LS997, but as you may know there is no stock kdz for LS997(LG V20 SPRINT). If i were to flash the US996 Kdz to my LS997 via LGUP(yes it would boot fine) and then follow your steps ie flash US996 modem to my LS997 after hitting it with US996 kdz, would that get my radio working?
einsteino said:
I have this same issue on my LS997, but as you may know there is no stock kdz for LS997(LG V20 SPRINT). If i were to flash the US996 Kdz to my LS997 via LGUP(yes it would boot fine) and then follow your steps ie flash US996 modem to my LS997 after hitting it with US996 kdz, would that get my radio working?
Click to expand...
Click to collapse
Maybe, since i only have us996 so i couldn't tell you if that gonna work or not. But i think, it worth to try. Btw be carefully with the ARB.
ttnduy said:
Maybe, since i only have us996 so i couldn't tell you if that gonna work or not. But i think, it worth to try. Btw be carefully with the ARB.
Click to expand...
Click to collapse
Thanks for your reply. I was able to fix it by flashing the ls997 ZV6 firmware zip that someone posted on one of the threads
First of all, thank you for this guide.. You were savior of my LG V20 US996 to turn back with signal . But even my signal is exist, I cannot connect to internet. I stay in Indonesia. I already changed every modem (around 5 times I suppose..) but stilL can't connect to internet. Do you have any suggestion?
Thank you
US99610f not in Google Drive Link
Hello ttnduy,
I am following your guide. I was just wondering if you have US99610f for (Unlocked) version. The download at lg-firmwares[dot]com/lg-us996-firmwares/firmwares/ is pain fully slow.
Thanks mate
MW
zee789 said:
First of all, thank you for this guide.. You were savior of my LG V20 US996 to turn back with signal . But even my signal is exist, I cannot connect to internet. I stay in Indonesia. I already changed every modem (around 5 times I suppose..) but stilL can't connect to internet. Do you have any suggestion?
Thank you
Click to expand...
Click to collapse
Maybe the different in mobile broadband or something, do you try reflash the modem file or ROM ?
-MW- said:
Hello ttnduy,
I am following your guide. I was just wondering if you have US99610f for (Unlocked) version. The download at lg-firmwares[dot]com/lg-us996-firmwares/firmwares/ is pain fully slow.
Thanks mate
MW
Click to expand...
Click to collapse
I have updated the US99610f kdz file for the unlocked version. Hope this gonna help.
Hi all,
on my LG-US996
when I tried to run the bootloader from the LG page
I get the following error
"Unfortunately, your device(United States, (US CELLULAR_TULSA(USA)) )does not support unlocking the bootloader."
What are my options now? How else can I get the on board radio/modem working again?
My phone stopped working after the update from the LG Bridge. (I would have been better off not doing any update)
You have to be careful what kdz you flash on us996 I have found if you flash the wrong kdz it will not work properly and can be a hassle to get it back.....
You have saved my ass! I thanked you, and rated your post as excellent, but i feel the need to also post a thank you! Merry Christmas, Happy Holidays and may you have a Happy New Year!
Help request..
Recently i bought v20 us996 unlocked us cellular.
And it's automatically updated to us99610n.
The signal was lost after that.
What I've done after following this thread instruction:
1. Downgrade to us99610f via patched LGUP. Success.
2. Unlock bootloader via LG developer web. Failed.
I inputted imei & device ID 64 digits. But it's unmatch.
What's wrong with my step?
I'm using adb & got device ID.
My v20 condition now is most basic apps force closed.
I would like to unlock via dirtysanta, but I'm kind of confused. This is my first time using adb.
I hope to get some help in here ???
FYI I'm in Indonesia.
Thanks.
kmn5 said:
Hi all,
on my LG-US996
when I tried to run the bootloader from the LG page
I get the following error
"Unfortunately, your device(United States, (US CELLULAR_TULSA(USA)) )does not support unlocking the bootloader."
What are my options now? How else can I get the on board radio/modem working again?
My phone stopped working after the update from the LG Bridge. (I would have been better off not doing any update)
Click to expand...
Click to collapse
Areechen said:
Recently i bought v20 us996 unlocked us cellular.
And it's automatically updated to us99610n.
The signal was lost after that.
What I've done after following this thread instruction:
1. Downgrade to us99610f via patched LGUP. Success.
2. Unlock bootloader via LG developer web. Failed.
I inputted imei & device ID 64 digits. But it's unmatch.
What's wrong with my step?
I'm using adb & got device ID.
My v20 condition now is most basic apps force closed.
I would like to unlock via dirtysanta, but I'm kind of confused. This is my first time using adb.
I hope to get some help in here
FYI I'm in Indonesia.
Thanks.
Click to expand...
Click to collapse
unlock bootloader via LG web can be use with US996 UNLOCKED Version only, in your case US CELLULAR, you should follow the DirtySanta method to unlock your bootloader and the rest still be the same with the unlocked version.
Hope this help.
crs77 said:
You have saved my ass! I thanked you, and rated your post as excellent, but i feel the need to also post a thank you! Merry Christmas, Happy Holidays and may you have a Happy New Year!
Click to expand...
Click to collapse
Thank you. I'm glad this help and Happy New Year.
ttnduy said:
unlock bootloader via LG web can be use with US996 UNLOCKED Version only, in your case US CELLULAR, you should follow the DirtySanta method to unlock your bootloader and the rest still be the same with the unlocked version.
Hope this help.
Click to expand...
Click to collapse
Hi ttnduy,
OK I'll try it. I'll post if i found some problem.
Thanks for your response.
Related
Hello Moto X Play owners
This guide is for those who still don't figure out how to root moto x play running android 6.0.1(stock Rom)
Old Thread for rooting moto x play is outdated, so decide to write this one with updated steps and links.
As usual I'm not responsible for your bricked device, as Motorola says Unlocking your boot loader is not for the faint of heart. you can't blame anybody but yourself. You will loose your warranty by unlocking your boot loader. and you will loose every data on your phone.
Still want to root your phone, okay fine follow these three steps to root your phone.
They are 3 Steps involved in this process.
1, Unlocking the Bootloader
2, install custom recovery
3, Install Super SU
Before you begin
A. Back up all your data. yes you gonna loose entire stuffs on your phone.
B. Download all the required files from the below links
1.Download and install Motorola USB Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
2.Download Fast boot and extract it to your hard drive (file attached on this thread)
3.Download TWRP latest version (do not extract)
http://forum.xda-developers.com/devdb/project/dl/?id=17934
4. Download Super SU V. 2.62-3 (do not extract)
https://download.chainfire.eu/751/SuperSU/
Now you are ready to begin
Step 1 : Unlock Bootloader
1. Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
2. Plug in your device to your PC using a USB cable.
3. Head over to the Motorola website to get your unlocking key and follow the steps provided there or follow the same steps provided below.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
3. Go to the extracted fastboot folder and open a command prompt (ctrl+shift+right click and open command prompt)
4. At the prompt, type
Code:
fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be
fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
copy this from the command prompt and paste in a notepad and remove all (bootloader) and make it string like belwo
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
5. Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page and agree the terms and condition and check your mail box for unlock key
6. copy your unlock code from mail and type the following command to unlock bootloader
Code:
fastboot oem unlock KEY
replace unlock key with your copied code from mail. Now you will see a unlocked message on your device and your device will reboot. you will see a unlocked bootloader warning with vibration on your phone and you are successfully unlocked your bootloader.
Step 02 Installing custom recovery TWRP
7.Put your device in fastboot mode again (power off, then press the power and volume down buttons simultaneously).
8.Type in the following command into the Command Prompt Window and Enter.
Code:
fastboot flash recovery twrp-lux-3.0.2-r3.img
note that fastboot flash recovery is command and twrp... is our file name so if you are using different version change the name accordingly
9. Now restart your device using keys in your phone to recovery (make sure your are rebooting in to recovery)
10.When prompted allow twrp to make changes. And make a back up of your system from the twrp menu
(do not choose read only, if you choose read only android will erase your recovery next time you reboot and you can not root your phone.)
Step 03 Rooting your phone using Super SU V. 2.62-3
warning : make sure you have a back up of your current system copied to your hard disk or else you can't restore your device if something went wrong.
11. Copy your downloaded super su file to your phone
12. Unplug your device from computer and restart to recovery
13. Go to terminal in TWRP - Advanced-Terminal type command in your phone
Code:
echo SYSTEMLESS=true>>/data/.supersu
14. flash super su and restart your phone.
Congrats you've rooted your phone successfully .
Now you can install custom rom, xposed modules .... etc
visit my YouTube channel for more stuffs related to moto x play rooted phones :good:
https://www.youtube.com/channel/UCOcePwMSubyeW0eBWr5SW6Q
Android 7.0 most stable Custom Rom for Moto x play so far
https://www.youtube.com/watch?v=4DFrOVmCqdk&t=7s
reserved
Should it work on XT1563?
CheyTac-12 said:
Should it work on XT1563?
Click to expand...
Click to collapse
It supposed to work but I got xt1562 so I haven't personally checked this on xt1563 so I can't guarantee that. But in the previous thread people rooted their xt1563 using this method.
Before you can enter the unlock code in Fastboot, you have to enable it in the developer options first.
Thanks...I tried many methods like one click...but none worked...gonna try .. thanks for info????
Abisheik01 said:
Thanks...I tried many methods like one click...but none worked...gonna try .. thanks for info
Click to expand...
Click to collapse
so what happened ? let us know the result :good::laugh:
Check my youtube channel for custom rom tutorials and other stuffs for your moto x play
https://www.youtube.com/channel/UCOcePwMSubyeW0eBWr5SW6Q
Yo!!!again thanks
hey!hey!hey! i got it thankyou very much...unlocking the bootloader was a very big task for me but with your steps i did it im on my way to flash twrp ..........again thanks
How easy is it to revert to stock once the Nougat update rolls out? I like the stock rom but don't want to miss the update just for adaway and Xposed
purplegreendave said:
How easy is it to revert to stock once the Nougat update rolls out? I like the stock rom but don't want to miss the update just for adaway and Xposed
Click to expand...
Click to collapse
Better you keep your bootloader locked. There's no point to loose your warranty if you love stock rom.
jerry0476 said:
Better you keep your bootloader locked. There's no point to loose your warranty if you love stock rom.
Click to expand...
Click to collapse
Bought it in January so I'm almost out of warranty anyway. All I want is Adaway, XposedGEL and system wide icon packs. Extra freedom with tasker would be nice too. I wish Moto/Lenovo would just give us a better idea of when they're rolling N out but I'm sick of waiting. If it's easy enough to lock the bootloader again and get the OTA (I'm happy to wipe the device in the meantime) then I'm going to root this week
purplegreendave said:
Bought it in January so I'm almost out of warranty anyway. All I want is Adaway, XposedGEL and system wide icon packs. Extra freedom with tasker would be nice too. I wish Moto/Lenovo would just give us a better idea of when they're rolling N out but I'm sick of waiting. If it's easy enough to lock the bootloader again and get the OTA (I'm happy to wipe the device in the meantime) then I'm going to root this week
Click to expand...
Click to collapse
We can expect OTA by the end of Dec or Jan. You can restore stock rom for sure but never tried so I can't recommend it.
How do you lock the bootloader
(I'm sorry, I'm a noob)
FIREBREATH1001 said:
How do you lock the bootloader
Click to expand...
Click to collapse
You don't. Is not possible. Unlock is not reversible. It is possible to achieve a relocked state which usually isn't helpful.
I have a strange issue where it's as if SuperSU stops and my root permissions are lost until I reboot. If I open any app that usually requests root through SuperSU it just hangs.
I'm using v2.62 so should I try a later version? Do I need to flash this in twrp or just install within Android or is this a known different problem?
farquea said:
I have a strange issue where it's as if SuperSU stops and my root permissions are lost until I reboot. If I open any app that usually requests root through SuperSU it just hangs.
I'm using v2.62 so should I try a later version? Do I need to flash this in twrp or just install within Android or is this a known different problem?
Click to expand...
Click to collapse
if you are in stock use this:
go to terminal in TWRP - Advanced-Terminal type command in your phone:
Code:
echo SYSTEMLESS=true>>/data/.supersu
flash super su and restart your phone.
there is new version 2.79:
Code:
https://my.pcloud.com/publink/show?code=XZIvxlZ2TCrbpMdwQkSiAJhQwHuv0J8lRsy
So, this is the updated guide for rooting the Moto X Play, right?
Completely working as of today still?
working but you need updated version twrp 3.0.2-r5 and supersu 2.79. here twrp:
Code:
https://my.pcloud.com/publink/show?code=XZPF6lZmr0aJ56hbe8rm51jfaaXU5L6O5EV
without systemless command you should use version 2.62-3
Code:
https://my.pcloud.com/publink/show?code=XZ5t3lZvON7CblxVEYaWhGGr9rMpY02EEpX
jerry0476 said:
Hello Moto X Play owners
This guide is for those who still don't figure out how to root moto x play running android 6.0.1(stock Rom)
Old Thread for rooting moto x play is outdated, so decide to write this one with updated steps and links.
As usual I'm not responsible for your bricked device, as Motorola says Unlocking your boot loader is not for the faint of heart. you can't blame anybody but yourself. You will loose your warranty by unlocking your boot loader. and you will loose every data on your phone.
Still want to root your phone, okay fine follow these three steps to root your phone.
They are 3 Steps involved in this process.
1, Unlocking the Bootloader
2, install custom recovery
3, Install Super SU
Before you begin
A. Back up all your data. yes you gonna loose entire stuffs on your phone.
B. Download all the required files from the below links
1.Download and install Motorola USB Drivers
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
2.Download Fast boot and extract it to your hard drive (file attached on this thread)
3.Download TWRP latest version (do not extract)
http://forum.xda-developers.com/devdb/project/dl/?id=17934
4. Download Super SU V. 2.62-3 (do not extract)
https://download.chainfire.eu/751/SuperSU/
Now you are ready to begin
Step 1 : Unlock Bootloader
1. Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
2. Plug in your device to your PC using a USB cable.
3. Head over to the Motorola website to get your unlocking key and follow the steps provided there or follow the same steps provided below.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
3. Go to the extracted fastboot folder and open a command prompt (ctrl+shift+right click and open command prompt)
4. At the prompt, type
Code:
fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be
fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
copy this from the command prompt and paste in a notepad and remove all (bootloader) and make it string like belwo
0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
5. Check if your device can be unlocked by pasting this string in the field below, and clicking “Can my device be unlocked?”
If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of this page and agree the terms and condition and check your mail box for unlock key
6. copy your unlock code from mail and type the following command to unlock bootloader
Code:
fastboot oem unlock KEY
replace unlock key with your copied code from mail. Now you will see a unlocked message on your device and your device will reboot. you will see a unlocked bootloader warning with vibration on your phone and you are successfully unlocked your bootloader.
Step 02 Installing custom recovery TWRP
7.Put your device in fastboot mode again (power off, then press the power and volume down buttons simultaneously).
8.Type in the following command into the Command Prompt Window and Enter.
Code:
fastboot flash recovery twrp-lux-3.0.2-r3.img
note that fastboot flash recovery is command and twrp... is our file name so if you are using different version change the name accordingly
9. Now restart your device using keys in your phone to recovery (make sure your are rebooting in to recovery)
10.When prompted allow twrp to make changes. And make a back up of your system from the twrp menu
(do not choose read only, if you choose read only android will erase your recovery next time you reboot and you can not root your phone.)
Step 03 Rooting your phone using Super SU V. 2.62-3
warning : make sure you have a back up of your current system copied to your hard disk or else you can't restore your device if something went wrong.
11. Copy your downloaded super su file to your phone
12. Unplug your device from computer and restart to recovery
13. Go to terminal in TWRP - Advanced-Terminal type command in your phone
Code:
echo SYSTEMLESS=true>>/data/.supersu
14. flash super su and restart your phone.
Congrats you've rooted your phone successfully .
Now you can install custom rom, xposed modules .... etc
visit my YouTube channel for more stuffs related to moto x play rooted phones :good:
https://www.youtube.com/channel/UCOcePwMSubyeW0eBWr5SW6Q
Android 7.0 most stable Custom Rom for Moto x play so far
https://www.youtube.com/watch?v=4DFrOVmCqdk&t=7s
Click to expand...
Click to collapse
i can't ub my phone, plz help me
ub by fastboot
http://sv1.upsieutoc.com/2017/02/12/Untitled.jpg
ub by windroid v3.0, v3.1
http://sv1.upsieutoc.com/2017/02/12/Untitled15eff6.jpg
ub by windroid v2.4, v2.5, v2.6
http://sv1.upsieutoc.com/2017/02/12/Untitled2.jpg
Root Guide
** Root will void the warranty and disable OTA updates **
boot.img patch method
I don't recommend updating the firmware OTA before rooting. There is a chance you will update your phone to a firmware that hasn't been released yet on the ASUS website. New updates are released OTA first and then about a week or two later they are posted on the ASUS website. If by chance you updated the firmware OTA and the firmware isn't on the ASUS website, you'll have to wait for the firmware to be posted before you can root.
If already rooted and updating firmware skip to 5b
1. Make a folder called ROG Phone to store all files needed
2. Download the following to the ROG Phone folder
-- Unlock Tool, aka Unlock Device App
---- https://dlcdnets.asus.com/pub/ASUS/..._SIGNED_UnlockTool_9.1.0.7_180912_fulldpi.apk
-- Latest Firmware - Under Firmware click on See All Downloads | Look at version number, not dates
---- Match SKU/Region - Example: WW->WW, CN->CN, JP->JP
------ Settings > System > About phone > Software information
-------- https://www.asus.com/us/Phone/ROG-Phone/HelpDesk_BIOS/
-- Minimal ADB and Fastboot - Portable
---- https://devsjournal.com/download-minimal-adb-fastboot-tool.html
-- Payload Dumper
---- Attatched image_extrator.zip script
-- Python
---- https://www.python.org/downloads/
-- Magisk Manager
---- https://github.com/topjohnwu/Magisk/releases
3. Unlock bootloader
-- Connect the phone to the PC via the side port on your phone
-- Select USB File Transfer on the phone; If problems connecting, update drivers on the PC
-- Copy the Unlock Tool to your phone's Downloads folder
-- This voids the warranty and disables OTA updates
-- This will force a factory reset, so backup your data
-- Use File Manager (in ASUS folder) on your phone to run the Unlock Tool from the Downloads folder
-- If asked for Pin select "Use your Google account" in white text (can't see) below the Pin request
---- Pin request YouTube: https://www.youtube.com/watch?v=aPKAEGptfas
4. Enable Developer on the phone
-- Settings > System > About phone > Software information
---- Tap "Build number" 7 times
5. Update phone to latest downloadable firmware
-- 5a
-- Open the ROG Phone folder and enable view file extensions
---- File > Change folder and search options > Click View tab > Uncheck Hide extensions for known file types > Click OK
-- Unzip Minimal ADB and Fastboot - Portable file
-- 5b
-- Copy the firmware to the Minimal ADB and Fastboot folder and rename firmware.zip
-- Turn on USB debugging
---- Settings > System > Developer options
------ Enable "USB debugging"
-- Connect the phone to the PC via the side port on your phone
-- Select USB debugging on your phone.
-- From the Minimal ADB and Fastboot folder run cmd-here.exe
-- From the command prompt (black window) type the following:
adb devices
-- To check the connection
adb reboot recovery
-- Select ADB on phone
adb sideload firmware.zip
-- Check that your phone was updated to the latest firmware
---- Settings > System > About phone > Software information
If by chance adb sideload doesn't work, try copying the firmware to the root directory (folder) on the phone and then reboot to install. Don't change the name of the firmware while using this method and you can't skip updates. So if there are two updates out from your current version, you'll have to install both.
6. Extract the boot.img file from the firmware using Payload Dumper
-- Use the attached image extractor script
---- Requires Python; Look at readme.txt
7. Patch boot.img using Magisk Manager
** Make sure that boot.img is from the same firmware version that is on the phone **
-- Turn off USB debugging
---- Settings > System > Developer options
------ Disable "USB debugging"
-- Connect the phone to the PC via the side port on your phone
-- Select USB File Transfer on the phone
-- Copy Magisk Manager and boot.img to your phone's Downloads folder
-- Use File Manager (in ASUS folder) on your phone to run Magisk Manager from the Downloads folder
---- Magisk Manager requires access to the Internet via wifi or mobile network
-- More Information
---- https://www.google.com/search?q=How...Methods)&ie=utf-8&oe=utf-8&client=firefox-b-1
------ Look at Method 2
-- Copy patched_boot.img from the phone's Downloads folder to the Minimal ADB and Fastboot folder
8. Flash patched_boot.img
** Make sure that patched_boot.img is from the same firmware version that is on the phone **
-- Put phone into fastboot mode
---- While the phone is off, hold down volume up and power buttons
-- Connect the phone to the PC via the side port on your phone
-- From the Minimal ADB and Fastboot folder run cmd-here.exe
-- From the command prompt (black window) type the following:
fastboot devices
-- To check the connection
fastboot flash boot patched_boot.img
fastboot reboot
--------------------------------------------------------------------------------
Some users couldn't get a connection to a PC via a PC's Type-C USB port and had to use a Type-C to Type-A USB cable.
https://www.amazon.com/gp/product/B...00__o00_s00?tag=detailedview-20&ie=UTF8&psc=1
If by chance something went wrong and your phone locks up on boot, this raw WW firmware install will get you back up and going (so far it has worked for everyone). This can also be used to relock the bootloader, but it will not restore OTA updates.
https://drive.google.com/file/d/155ZDnBjHeknppthFtNpGadicSNvBGokP/view?usp=sharing
Download and unzip
Reboot phone into fastboot mode
Run flashall_AFT.cmd
..
Tesla74 said:
Quick Root Guide
1. Unlock bootloader
https://dlcdnets.asus.com/pub/ASUS/..._SIGNED_UnlockTool_9.1.0.7_180912_fulldpi.apk
2. Download unofficial TWRP by shakalaca (Doesn't fully work, but can flash files from USB drive)
Download the TWRP that matches your firmware version and rename twrp.img
https://mega.nz/#F!pst3URCQ!l_N503AsNmytaErhmuiwqg
3. Put phone into fastboot mode (volume down + power button)
Connect to the computer using the side USB port
4. Download Minimal ADB and Fastboot and flash twrp.img
https://devsjournal.com/download-minimal-adb-fastboot-tool.html
fastboot flash boot twrp.img
5. Download Magisk Manager, Magisk, and Magisk Unistaller onto a USB drive
https://github.com/topjohnwu/Magisk/releases
6. Flash Magisk with TWRP and install Magisk Manager to root
I don't have the phone yet, but if anyone wants to add to this guide to make it more accurate, I'll update this post.
Click to expand...
Click to collapse
Before running the fastboot command run: "fastboot devices" without quotations. To make sure the device is recognized and connected.
Nice write up!. By the way there is an update to the system a small one maybe 70+ MB. Minor stability update.
Rashad83 said:
Before running the fastboot command run: "fastboot devices" without quotations. To make sure the device is recognized and connected.
Nice write up!. By the way there is an update to the system a small one maybe 70+ MB. Minor stability update.
Click to expand...
Click to collapse
Thanks, I updated post. I was wondering after the system update, does TWRP still work because of encryption? Or does TWRP need to be updated for every system update?
Does the unlock bootloader tool REALLY erases all everything, or it's just ASUS warning so they cover their end if user data is lost?
Tesla74 said:
Thanks, I updated post. I was wondering after the system update, does TWRP still work because of encryption? Or does TWRP need to be updated for every system update?
Click to expand...
Click to collapse
Once you flash TWRP you will not be able to update through OTA. You will have to download the update manually and then flash it, once you do that i believe it flashes the stock boot.img which removes TWRP. When that happens you will have to flash a compatible TWRP for the new update.
That's how i understand it, personally i haven't rooted yet so i can't be 100% certain.
Also it's recommended by TWRP team to return to stock before updating the system and then flashing TWRP.
---------- Post added at 08:04 AM ---------- Previous post was at 07:49 AM ----------
mbze430 said:
Does the unlock bootloader tool REALLY erases all everything, or it's just ASUS warning so they cover their end if user data is lost?
Click to expand...
Click to collapse
It's not just ASUS, Any Android device once you unlock the bootloader the user data is erased. So better backup!. By the way ASUS has a backup tool for all your apps and data i haven't tried it yet, give it a try.
That is correct. When I had my Pixel 2 XL (or any phone for that matter). When you flash TWRP on to the recovery the OTA update will always fail. You will have to either find the original recovery or the whole rom and reflash it.
---------- Post added at 04:07 PM ---------- Previous post was at 04:05 PM ----------
---------- Post added at 08:04 AM ---------- Previous post was at 07:49 AM ----------
[/COLOR]
It's not just ASUS, Any Android device once you unlock the bootloader the user data is erased. So better backup!. By the way ASUS has a backup tool for all your apps and data i haven't tried it yet. so check it out.[/QUOTE]
Dang it! I just setup the phone exactly the way I wanted it too.
Rashad83 said:
Once you flash TWRP you will not be able to update through OTA. You will have to download the update manually and then flash it, once you do that i believe it flashes the stock boot.img which removes TWRP. When that happens you will have to flash a compatible TWRP for the new update.
That's how i understand it, personally i haven't rooted yet so i can't be 100% certain.
Also it's recommended by TWRP team to return to stock before updating the system and then flashing TWRP.
Click to expand...
Click to collapse
Thanks! I hope shakalaca keeps updating TWRP with the new firmwares. Sounds like recovery.img will have to be extracted from the firmware and flashed before updating.
You will not find any file under the name of recovery.img. I tried looking for it in the stock firmware before no such file exists. The only way I think to do it is by flashing all of the boot.img where it resides I think.
Fastboot flash boot boot.img
Rashad83 said:
You will not find any file under the name of recovery.img. I tried looking for it in the stock firmware before no such file exists. The only way I think to do it is by flashing all of the boot.img where it resides I think.
Fastboot flash boot boot.img
Click to expand...
Click to collapse
I wasn't able to find either recovery.img or boot.img in the firmware.
boot.img vs recovery.img always confuses me. I wonder if updating with the update.zip method really needs stock recovery?
Tesla74 said:
I wasn't able to find either recovery.img or boot.img in the firmware.
boot.img vs recovery.img always confuses me. I wonder if updating with the update.zip method really needs stock recovery?
Click to expand...
Click to collapse
You need the payload dumber app on windows to extract the payload file which contains all the .img files which boot.img is one of them.
The boot.img contains the kernel and other important files needed to boot the device, while the recovery contains all the recovery settings responsible for reseting the device and updating, wiping actions.
From the comments i saw about recovering the phone after a bootloop it seems stock recovery isn't needed but i could be wrong. We will need input from others who have done it.
On my previous phone i could go back to stock rom without stock recovery as long it's the same rom build. So you will need to flash the same stock rom you are currently on and then flash the update.
I ran into some trouble. after running bootloader unlocker apk. it is now asking for a PIN. I tried the PIN I used when setting up the fingerprint reader and it doesn't work. It won't let me setup the phone again now.
Also got into the stock Recovery and did a user/data factory reset
Anyone suggestions?
Tesla74 said:
4. Put phone into fastboot mode (volume down + power button)
Connect to the computer using the side USB port
Click to expand...
Click to collapse
By pressing volume down + Power button, the phone goes into recovery mode not fastboot.
It's easiest doing it by adb:
Adb devices
If the phone Is found:
Adb reboot bootloader
That's what I did when I root my Rog
mbze430 said:
I ran into some trouble. after running bootloader unlocker apk. it is now asking for a PIN. I tried the PIN I used when setting up the fingerprint reader and it doesn't work. It won't let me setup the phone again now.
Also got into the stock Recovery and did a user/data factory reset
Anyone suggestions?
Click to expand...
Click to collapse
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
Click to expand...
Click to collapse
OMG! You are right! after staring at the screen I can finally see it! THEY NEED TO FIX THAT! I spend the past 2 hours erasing all the partitions! I wanna kill ASUS!
Marco589 said:
By pressing volume down + Power button, the phone goes into recovery mode not fastboot.
It's easiest doing it by adb:
Adb devices
If the phone Is found:
Adb reboot bootloader
That's what I did when I root my Rog
I was in the same situation, but if you check carefully you will see "use your account Google" it's just below of the pin request.
(It's written in White )
Click to expand...
Click to collapse
Thanks! I"ve updated the guide for both issues.
Tesla74 said:
Thanks! I"ve updated the guide for both issues.
Click to expand...
Click to collapse
To go to fastboot mode the hardware method will be by:
1. Holding (Power+Volume Up) until you see "Republic of Gamers" logo then release.
2. If the phone is turned off; hold the volume up only and connect the usb c to the phone(make sure the usb wire is connected to the PC already "It's basically the same as holding the power button except you'r getting the power from the usb"). You will go directly to "fastboot mode/ bootloader mode" i used to do this before on my phones, will also work on the ROG phone.
Rashad83 said:
To go to fastboot mode the hardware method will be by:
1. Holding (Power+Volume Up) until you see "Republic of Gamers" logo then release.
2. If the phone is turned off; hold the volume up only and connect the usb c to the phone(make sure the usb wire is connected to the PC already "It's basically the same as holding the power button except you'r getting the power from the usb"). You will go directly to "fastboot mode/ bootloader mode" i used to do this before on my phones, will also work on the ROG phone.
Click to expand...
Click to collapse
Thanks! I updated the guide and added link to your post.
I loaded TWRP but I can't flash Magisk on it. Can't read the /system partition.
Worse off, I am stuck at the ROG logo even after reboot.
what can I do to get the phone to at least boot back to the OS?
-----Update------
Nevermind I extracted the payload.bin and fastboot flash boot boot.img from there and it booted up again.
mbze430 said:
I loaded TWRP but I can't flash Magisk on it. Can't read the /system partition.
Worse off, I am stuck at the ROG logo even after reboot.
what can I do to get the phone to at least boot back to the OS?
-----Update------
Nevermind I extracted the payload.bin and fastboot flash boot boot.img from there and it booted up again.
Click to expand...
Click to collapse
In order to flash Magisk v17.3, you need to load Magisk and magisk unistaller on a USB drive, then boot into recovery , select USB storage then flash magisk.
Thanks to mbze430 posting the boot.img patch method of rooting, I've updated the guide. This works without the need for TWRP.
Need info on flashing twrp. Are all attempts done on firmware version 23 (where latest shakalaca version of TWRP is supported)? Is there no way to get TWRP working on firmware version 43?
Found this while trolling through the Chinese forums, none of this is my work, I have translated the instructions as best I can.
Disclaimers; I have not tried this, it may brick the global rom, the custom recovery is likely only in Chinese language.
You need:
Boot Loader unlock code (currently probably not possible to get)
Huawei USB drivers
Recovery image (attached)
Magisk package (attached)
files: https://mega.nz/#!PM0EmYLA!384hZjmJ9ExNc7Q8rSqssHunWSO7AxQ3GA4qet6RX4E
Extract files to a folder, open command prompt and change into this folder.
Unlock bootloader (BL unlock will clear the phone data, please do a backup)
- Obtain an official unlock code
- double-click to open the "Huawei Toolbox.exe"
- click "unlock bootloader "
- enter the unlock code in the pop up window , click OK, and wait for the phone to unlock complete restart.
Flash the third-party recovery
- Turn off the phone and connect the computer. Press and hold the “Volume Down” button and “Power button” until the phone displays the android page and release your finger.
- open command prompt and run:
fastboot flash recovery_ramdisk twrp.img
- after seeing the two OKAY feedback from the command line, the flash is successful.
Enter recovery to flash root image (this step will clear all data of the mobile phone including memory card, please make a backup in advance)
- long press “Volume Up” and “Power” ", until you see the a twrp logo, release the keys and wait to enter recovery mode
- After entering recovery, click the second item “Clear”, click “Format Data Partition” in the lower left corner, slide the slider to enter the clear, wait for the progress bar to complete
- Return to the recovery homepage, click on the last item "Advanced", select the last item "Remove data forced encryption", slide the slider to release, wait for completion
Copy the root package to the phone
- In Command Prompt type or copy the following commands
adb push magisk-installer.zip /sdcard
adb push magisk.apk /sdcard
Install Image
- Whilst still in recovery mode, click the first item to install the magisk-installer.zip package from the sdcard , slide the slider to install, wait for the flash to complete, and restart the phone
- After reboot is complete, click “File Manager”, select the apk file “magisk.apk” just copied from the memory card when install is finished, open the magisk app and click “No, thank you” in the pop-up window
- Return to the command line tool, type the code to execute, and wait for the phone to automatically restart
Fastboot reboot recovery
- after the restart, open "magisk", it should show that the installation is complete, that is, ROOT is achieved.
Anything in that forum on how to manually update phone?
technotika said:
Anything in that forum on how to manually update phone?
Click to expand...
Click to collapse
That is actually what I was looking for
But none, problem is the v20 (china version) seems to get OTA way before us, they all got v143 2 weeks ago.
I did find the menu to do it, but it only supports if the image is stored on an sdcard, and when I click it it says no sdcard found. so its impossible.
Tried same with similar results. One day eh? ?
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
greenblueye said:
İ have V20 chinese version. İ want to root but could not find a way. Can you share the chinese forum maybe i can find how to unlock bootloader
Click to expand...
Click to collapse
If you read what I wrote in the first post you would see you cannot root without a bootloader unlock code.
Tested! Work bootloader code on Russia services (Cost 20USD)
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Nice! Did unlocking bootloader factory reset your device?
Yes of course. All new Huawei and Honor do a reset after unlocking
i get bootloader unlock code from funkiehuwai for 20$
any one tried this instructions and have success?
I just wonder comments below will work?
*adb push magisk-installer.zip /sdcard
*adb push magisk.apk /sdcard
because there is no sd card support for view20?
when i opened huawei-toolbox.exe its in chinese and im afraid to continue other instructions
Did anyone use TWRP and which version?
Did the View 20 Boot correctly?
I read in a Forum, that with the view 20 doesn´t boot correctyl with TWRP. The reason should bei the Storage...
Best regards
Unlocked Bootloader
belam00r said:
Tested! Work bootloader code on Russia services (Cost 20USD)
Click to expand...
Click to collapse
Does that mean you rooted you device (with the files from above) or you just unlocked the bootloader?
I was able to unlock my bootloader with a code from funkyhuawei (about 18 €, site seems to be down currently). I did not use the unlock tool above, mainly because its chinese
- Enabled "USB debugging" and "OEM unlock" in developer settings
- Connected phone to PC, opened adb and used "adb reboot bootloader"
- Unlocked via "fastboot oem unlock *16digit code*"
This worked out fine. However, as far as i understand it magisk is installed over twrp (recovery_ramdisk), removing twrp but granting you root. This makes me kind of nervous since twrp has been a nice safety net on several occasions. This is why I stopped after unlocking the bootloader. Maybe someone has more experience on this? Why is there so little interest in rooting this phone?
Regards
root achieved
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
garris_bibop said:
I don't know if nobody's interested or nobody wants to try rooting this phone. However, I just went ahead and tried it. I used this guide: https://topjohnwu.github.io/Magisk/install.html#emui-9 (posted in https://forum.xda-developers.com/honor-view-20/help/root-t3900266). https://androidhost.ru/search.html is were I got the firmware from (posted in https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). I downloaded the 9.0.1.137 firmware, since this corresponds to the one currently installed on my phone.
In summary:
I extracted recovery_ramdis.img from the update.app with the huawei extractor. In order to see this image file, I had to uncheck "verify header checksum" under settings->extract.
I then transferred this file to my phone (download folder), downloaded newest magisk manager and installed it. I then pushed INSTALL next to magisk (which was not installed of course), Install again and then Patch boot image file. Choose your transferred recovery_ramdis.img and go ahead. Transfer patched file (now called patched_boot.img) back to PC.
For the next step, bootloader has to be unlocked already! Turn on "Enable OEM unlock" and "USB debugging" in the developer options and reboot to fastboot. Open ADB as usual and connect cable to phone. Type "fastboot flash recovery_ramdisk *path to patched_boot.img*" and wait for success.
A few things to keep in mind:
-Had a bootloop with the newest version of the viper4android module!
-The root was done without custom recovery, therefore a magisk module leading to a bootloop requires you to factory reset and do everything again if you want root to work (at least i couldn't get it to work again by reflashing orginial recovery_ramdis.img followed by patched_boot.img).
-For rooting to work you have to boot phone to recovery (in this case resulting in a "normal boot"). This means pressing volume up and holding it when booting the phone. For restart you could use an app which lets you boot to recovery automatically.
-While the above my sound annoying, permanently gives you the chance to boot you phone unrooted. This is nice, especially when you have a bootloop due to a magisk module (which I had).
-According to the first link, you could install a custom recovery into the second recovery partition of Huawei/Honor devices (erecovery_ramdis). there is no official twrp available for Honor View 20 at the moment.
-After unlocking my bootloader (see post above) I had "device not verified" in google play store. After rooting, my device is verified again
Regards
Click to expand...
Click to collapse
Well done good job:good:
İ have chinese version PCT-AL10 9.0.1.144 right now. Do you think i can use the same way? İ wonder from which version to extract recovery_ramdis.img
I have my view20 rooted
Thanks for the instructions.
greenblueye said:
I have my view20 rooted
Thanks for the instructions.
Click to expand...
Click to collapse
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
garris_bibop said:
You're welcome Be careful with sound improvement modules in Magisk! Had another bootloop with the Zirene module...
Which firmware did you get the recovery_ramdisk from in the end?
Click to expand...
Click to collapse
I get recovery-ramdisk from firmware PCT-AL10 9.0.1.129 . my phone is on version 9.0.1.144 but it worked:good:
After root i can not auto update software. 9.0.1.166 version is seen on ota but after download it says update is unsuccessful. Do you have any suggestion?
I think thats to be expected when rooted. Go for manual update I guess (https://forum.xda-developers.com/honor-view-20/how-to/honor-view-20-ota-march-patch-t3909075/page12). Personally I wouldn't bother with every update unless theres interesting new features and/or security updates. just to be on the safe side I would reflash the original recovery_ramdisk before updating! And backup your data!
NM Card
Hello !
Unless I'm mistaken, the View20 must be able to use nano sd cards (NM Card)
There's a ton of information out there, but finding it can sometimes be a challenge, especially for a newbie. And then there's posts to read through, in case a process has changed and it's only talked about in a single place, buried any number of pages back. So this is my attempt to put all Pixel 3 how-to's into a single thread. Everything below is what worked for me, from start to finish, with a fresh phone directly from Google that was bootloader-locked, unrooted, and running stock Android. Comments are welcome and encouraged: if something doesn't work for you, or you have a better/quicker/more reliable way of doing something, or maybe I made a mistake...let me know!
A few things:
Everything in this guide was tested on a "regular" Pixel 3 (blueline). It should all work exactly the same on a Pixel 3 XL (crosshatch), as long as you download the appropriate files (specifically the factory/OTA images and TWRP). I'm posting this in both blueline and crosshatch forums.
This first post will have links to files and the tools you need, as well as general things (like how to enable debugging and boot into recovery). The second post has how-to's for the big stuff (flashing images, TWRP, unlocking, etc).
I'm not responsible for anything you do. Follow these guides at your own risk. Doing so may also void your warranty.
Files and URLs
Official Android files
Factory (wipes device and requires unlocked bootloader): https://developers.google.com/android/images
Full OTA (leaves data intact, can be done via ADB sideload): https://developers.google.com/android/ota
Preview/beta OTA: https://developer.android.com/preview/download-ota.html
TWRP
XDA thread: https://forum.xda-developers.com/pixel-3-xl/development/twrp-3-2-3-0-pixel-3-xl-t3861623
Download: https://dl.twrp.me/crosshatch/
Magisk
XDA thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ADB and Fastboot
Google USB drivers: https://developer.android.com/studio/run/win-usb
SDK platform tools: https://developer.android.com/studio/releases/platform-tools
Download the ZIP and open (no need to extract the whole thing)
Copy the files below to their own directory (you will use this directory for all ADB/Fastboot commands):
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
General
Enable USB debugging
Download Google USB drivers (see above)
Download SDK platform tools and copy required files to their own directory (see above)
Enable USB debugging (Settings > About > tap Build 7 times > back > Developer options)
Plug phone into computer and when "Allow USB debugging" box comes up, check the box and allow (may need to have adb daemon running on the computer already, see below)
Fastboot mode (using hardware keys) aka bootloader
Power off
Hold VOL- and press/hold PWR until bootloader (fastboot) comes up
Recovery mode (using hardware keys)
Get into Fastboot mode (see above)
Use VOL buttons to find Recovery in the list, use PWR to select (should boot to broken android image)
Hold PWR and press VOL+ once to get into recovery
Useful ADB and Fastboot commands
Enable USB debugging (see above)
ADB (used while phone is "on" and booted up):
Use "adb devices" to ensure the computer is authorized
Use "adb reboot bootloader" to get into Fastboot
Fastboot mode
Use "fastboot devices" to verify computer can see your phone
Update #1: Items below marked through were removed since they don't really apply to Android 10.
Update #2: Edited to reflect changes in root with Android 11.
A quick note: everything below is assuming you're using Windows 10. When it says "Type...", this assumes you've opened a command window in the location of adb/fastboot and that all files referenced are in the same directory and (in some cases) renamed as I reference them (short names without spaces simplifies things). If you're using Powershell, you will probably need to change "adb" and "fastboot" to read ".\adb" and ".\fastboot" so Powershell will use the local files.
Unlocking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
In Developer Options, enable OEM unlocking and confirm (it may ask you to input fingerprint or PIN/pattern/password)
Boot into Fastboot mode (see above)
Type to unlock:
Code:
fastboot flashing unlock
Use VOL+ key to get the options on the screen to read "Unlock the bootloader" and use PWR button to select
Type to reboot:
Code:
fastboot reboot
Locking the bootloader
THIS WILL WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Boot into Fastboot mode (see above)
IMPORTANT: restore stock recovery if you replaced it with TWRP (this should prevent the "Can't find valid operating system" issue)
Type to lock:
Code:
fastboot flashing lock
Use VOL buttons to find "Lock the bootloader" and use PWR to select
Type to reboot:
Code:
fastboot reboot
Factory reset via fastboot (can also do this without wiping data)
THIS COULD WIPE YOUR PHONE, SO MAKE SURE EVERYTHING IS BACKED UP!
Download factory image ZIP and unzip all files into their own folder
Unlock bootloader (see above)
Reboot into Fastboot mode
You have 2 options:
Register the location of fastboot.exe with the PATH system variable and run "flash-all.bat"
Wipe data: just run "flash-all.bat" and call it a day
Do not wipe data: open "flash-all.bat" in a text editor (careful not to double-click and run it!), remove the "-w" from the last line to disable the wiping of data, then save, close, and run
Move the 3 files (bootloader IMG, radio IMG, image ZIP) into the ADB folder, rename for simplicity if you want, launch cmd or Powershell, and run the commands below (which come from "flash-all.bat")
Wipe data: type out commands below, but at last line, add "-w" flag: fastboot -w update image.zip
Do not wipe data: type out commands below as written (no "-w" flag)
The commands:
Code:
fastboot flash bootloader bootloader-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot flash radio radio-blueline-XXXX.img
fastboot reboot bootloader
[wait for reboot]
fastboot update image-blueline-XXXX.zip
Note: The last command (update image) will launch the red "fastbootd" screen, so don't worry and be patient while the command line tells you what's happening. The phone will reboot on its own into the Android system (not fastboot) afterward.
Root Android 10+ using Magisk (Canary channel)
This must be done after every update, and you cannot use the patched file from a different phone!
Unlock bootloader (see above)
Download factory image (not OTA, see link above)
Download and install Magisk Manager Canary (see link above)
In Magisk Manager settings, set Update Channel to "Canary"
Extract boot.img from image-blueline-XXXX.zip found in the factory image you downloaded
Place boot.img on your phone's internal storage
Open Magisk Manager and do:
tap "Install" button (next to "Magisk" in first block on the main screen)
"Select and Patch a File" option
Find boot.img file you just placed on your phone
tap "Let's Go"
When finished, move the newly-created magisk_patched.img file over to your computer's ADB directory
Reboot into bootloader
Type:
Code:
fastboot flash boot magisk_patched.img
fastboot reboot
Open up Magisk Manager and make sure everything's good!
Note : if you get stuck in fastboot mode or in a boot loop, flash the stock boot.img to both slots and try again
Code:
fastboot flash boot boot.img --slot all
Optional:
for adblocking, tap "Systemless hosts" in Magisk Manager, then install AdAway using F-Droid
install a performance kernel like Kirisakura for Bluecross (R)
Updating Android 10+ while rooted
You can't take an OTA while rooted, so updating Android 10+ (as in monthly updates) can be one of two ways.
Method #1 (faster, but more chance for issues)
Download OTA ZIP and move it to ADB folder (don't unzip it)
This does not require an unlocked bootloader, but does require USB debugging (see above)
Get boot.img from the factory image (see first post on where to download this) and place your ADB directory
Reboot into bootloader / fastboot and type to restore stock boot to both slots:
Code:
fastboot flash boot --slot all boot.img
fastboot reboot bootloader
[wait for reboot]
Use VOL buttons to select "Apply update from ADB"
Type (where filename is the name of the file you want to sideload):
Code:
adb sideload filename.zip
Wait for it to finish, will take you back to Recovery when it's done
Reboot using menu
Method #2 (takes longer, but best bet for minimal issues)
Follow "Factory reset via fastboot" instructions (see above, make sure you don't wipe your data!)
Take the OTA in the official way (through Android)
Follow "Root Android 10+ using Magisk Canary" instructions (see above)
Boot into TWRP (3.3.0-0 or higher)
Download TWRP IMG and place in ADB folder (rename the file to twrp.img)
If not already done, unlock the bootloader (see above)
Reboot into bootloader
Type to boot TWRP (it will restart and should boot into TWRP):
Code:
fastboot boot twrp.img
OPTIONAL: Replace recovery by installing TWRP
Your phone should automatically mount, so move twrp.img from PC to Download folder on phone's internal storage
Advanced > Install Recovery Ramdisk > choose TWRP IMG > Swipe to install
Back > Fix Recovery Bootloop > Reboot System > Do Not Install when asked if TWRP should install app
Root using Magisk (18.1 or higher)
Download Magisk ZIP and move to device
Boot into TWRP (see above)
Enter your PIN/pattern/password to decrypt (unnecessary if you are not using security on your phone)
Swipe to Allow Modifications (to system)
Install > find and select the Magisk ZIP > Slide to install
Wipe cache > Reboot system > Do Not Install when asked if TWRP should install app
Open Magisk Manager to verify latest and to install modules
"Can't find valid operating system" booting issue
Unlock your bootloader again (see above)
Follow steps for "Factory reset via fastboot" (see above) and keep the wipe flag
After it reboots, power off (press PWR and select "Power off" from menu)
Follow steps for "Locking the bootloader" (see above)
After it reboots into Fastboot mode, have it start using the PWR button
Android Recovery / "Cannot load Android system" booting issue
This can happen for a number of reasons, but the fix is the same: "Factory reset via fastboot" (see above). You probably do not need to wipe user data, so you can omit the "-w" flag.
If you still get the error message, select the "Try again" option. If it still doesn't work, try "Factory reset via fastboot" again, as well as "Try again". If it doesn't work this time, you probably have no choice but to do a factory reset (in which you will definitely lose your data).
If it happens after flashing Magisk in TWRP, though, you've got a slightly different issue and the problem will persist no matter how many times you flash the factory images and re-install Magisk. This is probably due to something leftover in the previous Magisk installation that conflicts with the new installation. There are two ways to handle this.
First and easiest: uninstall Magisk Manager app before rebooting into the bootloader and running fastboot commands. Then proceed as usual (sideload OTA or flash factory images via fastboot, boot TWRP, and flash Magisk). All guides for this are above. This method preserves any modules you have installed.
Second and more complete (if the above method still gives you trouble):
download to your phone the Magisk ZIP, Magisk Uninstaller ZIP, and Magisk APK from this XDA thread
uninstall the Magisk Manager app
reboot to bootloader
using fastboot, boot into TWRP using IMG (you don't need to replace boot with TWRP)
flash Magisk Uninstaller ZIP
wipe Dalvik
flash Magisk ZIP
wipe Dalvik
reboot system (do not install TWRP)
install Magisk Manager APK and re-install any modules
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
farfegnugen said:
I just have a couple questions pls-
1) Do the above instructions work on the Verizon Pixel 3 XL
2) I'm currently runned the official Android Q Beta (April 5). Do I need to leave the beta, then restore back to stock Android P (and do I do all those updates before starting root instructions)?
Click to expand...
Click to collapse
1.) If you somehow have an unlocked bootloader, yes, it would work for the Verizon Pixel 3 XL. However, I was under the impression that Google will not unlock the BL for the Verizon variant and there is currently no way to "hack" it.
2.) It should work the same whether you're on P or Q, though if you want to remain with Q, make sure you download the beta files directly from Google (rather than the P images) and use Magisk 19.0 instead of 18.1.
mcwups1 said:
Should I be concerned if my phone hasn't informed me of an April update?
I don't remember if I unlocked the bootloader before or after the updates to the March security update. Does it matter?
Click to expand...
Click to collapse
You can force it to check for updates; when you unlocked the BL shouldn't matter if you're using a patched boot image.
HACK3DANDR0ID said:
Is your bootoader Locked or Unlocked?
---------- Post added at 08:08 AM ---------- Previous post was at 08:07 AM ----------
No it does NOT matter which build you unlocked your BL
*edit*
Try to go into settings and force the update or you can always flash the entire factory img for april
Click to expand...
Click to collapse
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
farfegnugen said:
I haven't done anything to the phone since I got it 3 weeks ago but hoping to. Can the VZ version be unlocked? If so please point me in the right direction.
Click to expand...
Click to collapse
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Homeboy76 said:
No, but they working on finding a way to unlock it: [Bounty] Unlock Bootloader VZW Pixel 3 XL by coolhandz
Click to expand...
Click to collapse
Thanks so much for the info! Its difficult trying to find the current status of all the diff devices' root statuses.
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
CadTechBGMC said:
Thanks for this guide, when using the flash-all.bat and wiping the device will this method flash to both slots?
Click to expand...
Click to collapse
yes, if you are flashing with wipe all option (without removing -w) it does flash to both slots.
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
EMJI79 said:
Regarding getting to fastboot:
Since I have flashed April security update and after lightly bricking my Pixel 3Xl, (I have not lost data but I was unable to boot till solving the brick), the phone doesn't stay in fastboot when I use the adb command to get into it and all I can do to get to stay in fastboot is the power and volume down combo for more than 40 seconds.
I have my pixel working perfectly with root and kirisakura kernel but it is a bit of a pain getting to boot TWRP from fastboot for flashing stuff.
Click to expand...
Click to collapse
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
what i do normally is to power off the device first wait for few seconds then then use key combination to get it to fastboot from power-off state. Booting from fastboot to twrp never had any issues unless i had messed up the twrp installation due to some mess i did.
SacredDeviL666 said:
yeah if i try to get into fastboot directly from a power on state it doesn't stick on fastboot blinks for a second and then starts with reboot process, probably we are pressing it too long.
Click to expand...
Click to collapse
I have to press the keys 40 seconds even from power off.
EMJI79 said:
I have to press the keys 40 seconds even from power off.
Click to expand...
Click to collapse
definitely not 40seconds from power off state for me. not sure whats happening there
Maybe a short video would be a help to some of us newbies
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Drashnar said:
Dumb question. Probably gonna upgrade from an original Pixel XL soon. As long as I buy it from store.google.com, I should be able to unlock the bootloader without worrying about a crack/hack, correct? Thanks!
Click to expand...
Click to collapse
That is correct. I made the same switch from an OG Pixel and Pixel XL to P3 and P3XL right after release. Unlock the bootloader before you mess around a lot since it will do a factory reset.
How about backups? Does anyone backup and restore, or not?
If so, how do you do it with this 2 partition system?
installed and I like it. I cant get the clock off the lock screen. all settings says it is off.
wished it had MicroG installed instead of gapps
EDIT: I attached a zip with AIDA64's reports for this phone. One report has Magisk hidden from AIDA64, the other doesn't.
This mostly a copy of _cab13_'s Rooting the UMI F2 post as the same instructions for rooting that phone are how I rooted the S5 Pro. So please give _cab13_ thanks here if this helped you root your phone. I'll take a thanks for removing the orange state warning if I helped you with that
Please be patient when posting questions, I will get back to you as quickly as I can. I just have many responsibilities which take up a great deal of my time.
Rooting the S5 Pro
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEI['s]s and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
Once bootloader is unlocked, warranty is considered void. By following this guide, you consent to that happening. Safety net CTS will not pass anymore unless you flash Magisk which hides the unlocked bootloader.
Never re-lock your bootloader while running anything unofficial as the phone will not boot until you unlock again.
And, once again, a lot of bad things can happen like boot loops, if that happens to you, don't freak out! Simply re-flash the stock ROM, redoing the rooting process from the start. It might be time consuming, but that's your safest bet!
More important even, have fun rooting, it's before all a hobby!
Various Resources
>>> Latest official stock ROM <<<
[Non European] UMIDIGI_S5Pro_20210107.V3.04
[European] UMIDIGI_S5Pro.E_20201130.V3.04
Minimal ADB and Fastboot by shimp208
> Magisk (and Manager) by topjohnwu <
Mediatek SP Flash Tool
UMIDIGI Community Forum S5 Pro Thread
Unlocking Bootloader
ATTENTION!! After unlocking the bootloader, all user data in the phone's memory will be lost, so do not forget to throw all the most important things on your computer or flash drive!
1) Activate "Developer options" through Settings > About Phone > Tap Build Number multiple times.
2) Open "Developer options" in Settings > System > Tap Advanced.
Enable "OEM Unlocking" and enter your password to confirm. Enable "USB Debugging" as well.
3) On Windows, download and install Minimal ADB and Fastboot by shimp208
On Linux, use your package manager to install android-tools-adb and android-tools-fastboot
4) Open command prompt (Win + R > type cmd) or a terminal on linux.
5) Plug your phone, accept the prompt about adb and the PC signature.
6) Type adb reboot bootloader to reboot in fastboot mode. Unplug your cable from your phone
and replug it after fastboot is printed at the bottom of the screen.
THESE NEXT TWO STEPS WILL COMPLETELY WIPE YOUR DATA
7) Unlock the bootloader using fastboot flashing unlock and pressing Vol+
8) Unlock the secure partitions using fastboot flashing unlock_critical and pressing Vol+
9) Restart using fastboot reboot
You will now always see "Orange State" at boot; this is completely fine and will only delay your boot by 5 seconds.
Rooting using Magisk patched boot.img
This is "experimental" and is probably overkill, but everyone managed to install Magisk with it.
1) Clean install UMIDIGI_S5Pro_20200702.V3.02 (or the European one) with SPFT by selecting the scatter file, pressing download an rebooting the phone
(Make sure it is in "Download Mode" and not "Format + Download")
2) Patch boot.img by copying it to your device, using Magisk Manager to patch it, and get back the magisk_patched.img in the Download folder back to your PC.
3) Start ADB while booted; run adb reboot bootloader. Alternative is to reboot to recovery and selecting "reboot to bootloader"
4) unlock if not already done with fastboot flashing unlock followed by fastboot flashing unlock_critical
5) In the following code, the vbmeta.img and the recovery.img are the stock files from the ROM you downloaded and extracted.
Code:
fastboot erase boot
fastboot --disable-verity --disable-verification flash boot magisk_patched.img
fastboot --disable-verity --disable-verification flash recovery recovery.img
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot reboot
When rebooting, install Magisk Manager. It will prompt to finalize the installation, you can do so.
Congratulations ! You are now a proud Magisk user ! All credits goes to @topjohnwu he's the real MVP here.
Returning to stock / Resolving issues
The best way to resolve any issue is to return to stock. Here is the method.
1) Download latest stock ROM on UMIDIGI's forums
2) Download SP Flash Tool if you don't have it yet (Windows only)
3) Extract stock ROM in SP Flash Tool directory. Refer to Flash Tool guide if needed.
4) Open SP Flash Tool, Download Tab, "Choose" in Scatter-loading file, select the scatter file in the stock ROM directory.
5) If you want to keep your data, untick "userdata" partition. MAKE SURE FORMAT IS NOT SELECTED!
6) Press Download and connect your device via USB. Reboot the phone or turn it off and everything will be flashed.
7) If you want a full stock experience, I recommend relocking the bootloader so that SafetyNet will pass. Get into fastboot mode by using adb reboot bootloader and use fastboot flashing lock_critical followed by fastboot flashing lock. This will wipe your data once more.
You should be good to go.
ONE LAST THING
Get rid of your orange state warning.
Download the attached zip file and extract.
Put your phone into fastboot and:
Code:
fastboot erase lk
fastboot erase lk2
fastboot flash lk lk_patched.img
fastboot flash lk2 lk_patched.img
fastboot reboot
No more orange state warning! Reflash the stock lk before unrooting, though.
ATTACHED LK FILE IS FOR UMIDIGI S5 Pro ONLY.
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Hey guys it's me again !
Got some good news : I bought a S5 Pro as well
And I ABSOLUTELY LOVE IT !
I might get into rooting it soon, idk.
Thanks for the shout-out @zerosava
hermeez said:
Thank you for re-posting this as an option to root the S5. I did get stuck on flashing the recovery. I have tried a few times and every time it just flashes orange , restarts and loads normally. I have verified root.
i have used the recovery found here
https://forum.xda-developers.com/android/general/guide-rooting-umidigi-s5-pro-magisk-t4151183
I have no success installing TWRP. Do you know if twrp has a recovery that will work?
Click to expand...
Click to collapse
No luck for me finding a custom recovery (twrp or anything else.)
If you have any exp with them, see if you can make the F2's (found in the F2 root thread) work. It SHOULD only need a minumum of tweaking, just to account for the (afaik) slight soc differences. i'm not gonna hold my breath. there seems to be a void when it comes to enthusiasm for this phone. by my serial no, i have the 4832nd phone manufactured. compared to serials ranging from 22000- 189000 for my other umis (f1play, s3pro, f2, power3)
I think I'll try making TWRP soon for it.
The F2 TWRP would not be usable this easily, it's easier to start fresh.
If anyone wants to try, download the sources for the F2 TWRP on my GitHub, then you need to extract the stock kernel and replace the F2's with the S5pro's
root working thanx
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
Sorry, but I made this clear in the original post:
Disclaimers
This is important, please read thoughtfully.
whatever you do, NEVER EVER use SP Flash Tool in "Format All+Download" mode. This will wipe your IMEIs and some other bad stuff will happen like loss of fingerprint sensor. This cannot be reversed by us.
I do not know how to help you. My only suggestion is to post your problem in UMIDIGI's forum here: UMIDIGI Forum
If anyone can help you, that's where to find them.
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
I am sorry, but you will have to contact UMIDIGI support. Only they can help you as far as I know. I feel for you, I really do. I did this when I was a newbie with my F1 Play.
QUICKLARA said:
Hi guys ,i lost the imei on my phone and have the" Googlekeystate:fail", how can i fix them, thanks for you help.
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1
Ruiz702 said:
Please I need your help I reset it wrong with SP Flash Tool and now I get Googlekeystate: fail and it doesn't grab my fingerprint I'm desperate I need a solution please
Click to expand...
Click to collapse
hello, good and bad news.. fix but fingerprints are lost for good
https://community.umidigi.com/forum.php?mod=viewthread&tid=19722&extra=&page=1
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
stick2020 said:
hello folks,
This message is not about rooting s5 but rather about downgrading. I posted on the umidigi forum but have not received an answer. So the problem is the new OTA update that they pushed out yesterday. After update I lost 4G connectivity and i am unable to restore it. I want to roll back to the previous update. They have the roms available on the forum and I downloaded one but what I am not sure is can I use SP flash tool to just download the older ROM version on top of the new one?
I see lots of manuals on how to update but how do I safely downgrade?
Any help is greatly appreciated.
Sticks
Click to expand...
Click to collapse
Do a "download only" flash of the "super", " vbmeta_system", and "vbmeta_vendor" partitions only (uncheck all other partitions) from the previous ROM. That should do it.
ZeNNoP said:
i followed the instructions but i got stuck after step 4 it would be nice if this had a video walkthrough thanks for the guide though =w= 10/10 would try to root again lol
Click to expand...
Click to collapse
What precisely stuck you?
There is a new update firmware please make a rooting tutorial on youtube.,
Somebody made a custom TWRP and posted it on here. So if that'll help anyone out and get them to make a tutorial video, that be great. 'Cause I'm reading this over and over again, and I think I can do it, but I'm being very hesitant about it. And it's getting me all frustrated. I had it on "Flash Mode". And when I continued typing it out, it didn't go through and that had me on a raging panic attack. Luckily, it didn't mess up. But now I'm more hesitant. Please make a quick tutorial, doesn't even have to be perfect...
TWRP is at the bottom of this page:
[MT6785]How To Root Umidigi S5 Pro And Install TWRP 3.4.0 Recovery ~ Techswizz
To Root Umidigi S5 Pro, we will be using the Adb Tool Mode with TWRP recovery for Umidigi S5 Pro. It will be wise to read the post very well before flashing the recovery to avoid any Device errors or brick.
www.techswizz.com
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
bmaz121 said:
Thanks for this guide. I am completely lost with step 7 and 8. What does the Unlock the bootloader using fastboot flashing unlock and pressing Vol+ mean?????? Where do you enter the unlock code and what is it?
Click to expand...
Click to collapse
I am able to get FastBoot Mode on my screen (through step 6). I plug the phone back in per directions & I hear the Windows device connected chime.
I type: fastboot flashing unlock in the same cmd window
and I get "<waiting for any device>" in the cmd window and it hangs.
Every few seconds I hear the Windows device disconnected noise, but no device connect chime. This lasts indefinitely.
I repeated step 7 several times with variations with the Vol+ button: pressing first, holding down while pressing enter in cmd window, pushing afterward, holding down afterward, etc. Same results as described above.
Any help available? Should I not unplug my phone from the PC? The F2 directions did not require that.
thanks!