Database Info

How to Root MOTO X PLAY XT1562 Running Android 6.0.1

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

Can i just go back to how it was?

I don't even know why I wanted to root my phone. I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img and the twrp installer .zip, I get this message saying
"Unmodified System Patition
Keep System Read only?
..."
and I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Have I bricked my phone? Is there any way for me to go back?
Thanks for the advice.

That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock

scp-507 said:
I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Click to expand...
Click to collapse
You cared enough at one point to start the process. Whether to root or not is a personal decision, based on what types of added modifications of features you want out of root, and how important those are to you. Maybe you have changed your mind to that point. And I am biased to my own opinions. But that opinion would be to go ahead and finish the job, since you got this far. Nothing wrong is going on really, you just got stuck, not knowing what to do next. It does happen from time to time, when modding these devices. And nothing to get discouraged about. You did the right thing coming onto the forum and asking before doing something you were unsure about.
scp-507 said:
Have I bricked my phone? Is there any way for me to go back?
Click to expand...
Click to collapse
This is pretty hard to brick. Unlocking the bootloader, flashing TWRP, and root likely will not result in a real brick. Even if you brick the phone, there is an unbrick tool that will mostly likely get it up and running again.
scp-507 said:
I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img
Click to expand...
Click to collapse
It's not necessary any longer to flash the patched boot.img in order to root. Follow the "Recommended" install method from the TWRP thread, which is simple and straightforward. It's pretty much what the previous response outlined above.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
The method you are following (flashing a patched boot.img) does work. But it has more steps. And you have to be careful to flash the correct boot.img for your OOS version. Otherwise, you may have some issues. So going with the easier method is better, in my opinion.

djsubterrain said:
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
Click to expand...
Click to collapse
Is that true for all phones?

If you have the Global OP7Pro and not the T-mobile variant you don't have to be afraid of bricking the phone. The MSM unbrick tool can bring your device back to stock if its bricked or even if its not. I am not sure if the MSM tool works on the T-mobile variants, but it might.
I've hard bricked this device and successfully used the tool to recover it.

djsubterrain said:
That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock
Click to expand...
Click to collapse
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?

scp-507 said:
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?
Click to expand...
Click to collapse
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?

Well if you relock your bootloader you won't be rooted or have TWRP... It will also wipe all of your data like starting over when you got the phone out of the box.... If you want to stay rooted and use twrp you will have to deal with the splash screen all of us see it on our phones also. Basically you need to have the bootloader unlocked to keep root and have TWRP

scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
You can't relock your bootloader, you currently do not have the default recovery partition, if you really want to relock your bootloader you would need to flash the stock rom back over itself so it replaces the recovery with the default one. Then you can run "fastboot oem lock" but be aware, as I said before, this will want to wipe your data so the rom will go back to default setup. Remember to disable bootloader unlocking from the developer settings if you do, then you will be back to the default stock rom state.

scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
If you want root, you need to leave the bootloader unlocked. That is normal, and just how it is. The warning screen is just something to live with.
You need to return to full stock (ROM, boot.img, recovery) in order to relock the bootloader (otherwise you will get a bootloop or no boot). Which of course defeats the purpose of rooting the phone. So again, having the bootloader unlocked is the normal and expected state, when you are rooted.

How To Guide Asus ROG phone 5: unlock bootloader and root guide

Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations

Check pm's.

m8822 said:
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
Click to expand...
Click to collapse
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.

also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help

sabnack said:
also may i suggest adding a step to your guide ?
before flashing boot.img it might be a good idea to try it first using
Code:
Fastboot boot boot.img
i've had problems in the past with some bad patched boot.img images and this may be a way to avoid problems.
sorry if this sound patronising. just wanted to help
Click to expand...
Click to collapse
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill

hilary trump said:
Do you know any module to hide that pill
Click to expand...
Click to collapse
I'm sorry i don't know but i will gladly look into that issue as soon as i can boot my phone, currently i'm stuck in a bootlop and my phone doesn't get recognised. i put all my hopes in the unbrick tool at this point, whenever it will be out.
I will let you know

hilary trump said:
Thanks, is your currently rooted now? I tried module "Fullscreen/Immersive Gesture" to hide the annoying,ugly gesture indicator (thank Apple & Google for great idea). All worked except gesture swipe up from bottom to open desktop. Do you know any module to hide that pill
Click to expand...
Click to collapse
the root guide worked on another rog 5, however mine is completely nricked and i myslef is waaiting for unbrick tools

sabnack said:
hello and thank you very much for the detailed guide.
i was ready to do all that, i always unlock and root my devices so i'm savvy just enough to try, or so i thought.
after using asus unlock tool and rebooting, my phone ended up showing the indicated warning message but proceeded in a bootloop which is not generally a great problem, you can always flash partitions with fastboot !
But in my case the phone doesn't get recognised by "fastboot devices" command in bootloader mode nor in fastbootd (yes i have the latest adb & fastboot package installed with the latest platform tools)
so now i've got a very espensive and fancy paper holder.
if any of you encountered the same problem or maybe knows a way to get the device to be recognised by my pc I'll be very happy to donate for your trouble.
i already downloaded the latest firmware and extracted it with payload_dumper.py.
thank you very much to any of you who will take time to look into my issue.
Click to expand...
Click to collapse
Connect your phone with the side port it will work.

sorankira said:
Connect your phone with the side port it will work.
Click to expand...
Click to collapse
yes it did work, i flashed every partition and now i'm locked again, recovery doesn't work, could you please dump yours and post it ? hope i'm not asking too much.
EDIT: nevermind i finally solved it, i flashed a raw img of the system, it works now, thanks for your time

m8822 said:
Asus rog phone 5 guide
note: you follow this guide on your own responsibility. also You should note that unlocking via the official Asus app will void warranty and blacklist the device for future otas.
bootloader unlock:
! note that unlocking the bootloader will erase the phone, back up your data before starting !
- install asus unlock application from asus website (direct link)
- open the app, scroll to the bottom accept the user agreement
-scroll to the bottom, click on agree. enter your pin
- your phone should now reboot and you should see the warning message indicating that you have unlocked bootloader
! now if you don't see the warning screen and your phone was not formatted, this means this unlock method didn't work and you should seek other methods !
updating to the latest ww firmware
- download the latest firmware zip from asus website (direct link) to Version WW-18.0830.2101.86.
-move the .zip file to your main storage directory.
the phone should detect the update file, if it doesn't reboot your device and it should detect it.
after updating, set up your device, then install magisk app (download link)
extract the boot.img from the above software downloaded from asus, using payload dumper (google it).
then copy the extracted boot.img to your phone.
install magisk.
open magisk
click install.
choose patch boot.img
once the patch is completed, copy the patched boot.img to you pc
for further info, magisk patching guide
on your PC you need to install your device drivers, and ADB & fastboot. and enable usb debugging on your device
flashing patched boot image
- open adb, approve the request on your device
- enter the command
Code:
adb devices
you should see your device and authorized. if not find a guide how to access your device
-next reboot to bootloader using the command
Code:
adb reboot bootloader
- in bootloader flash the boot.img from above using the following command
Code:
fastboot flash boot boot.img
where boot image should be the address to the location of your boot image.
if you boot image is on your D:/ drive and in a folder called rootstuff.
your command should look like this.
Code:
fastboot flash boot D:\rootstuff\boot.img
once you flash the patched boot.img, reboot your phone.
open magisk app, check your root status you should be rooted.
congratulations
Click to expand...
Click to collapse
Mine causes bootloop

sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
What ? Why!
what happened? Did you get this after unlocking the bootloader or after boot.img?
My troubkeshooting will consiste of flashing raw, but i am not sure if that will lock your bootloader

sorankira said:
Mine causes bootloop
Click to expand...
Click to collapse
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.

sabnack said:
can you enter recovery and fastbootd ? if you only get access to bootloader, flashing a raw image does work !
then you can apply ota update zips from booted android and subsequently patch boot.img extracted from payload.bin from the ota update.
worked for me and i thought i bricked my device. let us know if we can do something to help.
Click to expand...
Click to collapse
I fixed the bootloop but without root access

sorankira said:
I fixed the bootloop but without root access
Click to expand...
Click to collapse
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.

sabnack said:
i believe you already have version WW-18.0830.2101.86 for WW only ( i just checked, i believe it was you who posted it here ). you can use this guide to extract boot.img from the payload.bin from the "UL-ASUS_I005_1-ASUS-18.0830.2101.81-1.1.64-user.zip" then if you continue by following the guide at the top of this thread you will be rooted in 15 minutes at most.
Click to expand...
Click to collapse
Yes i used this method, and causes bootloop sadly.

sorankira said:
Yes i used this method, and causes bootloop sadly.
Click to expand...
Click to collapse
oh ! dammit it's weird... you could try to patch the boot image with another phone.
or maybe the update file isn't right for your phone. i don't get it

Somebody successfully succeeded with the bootloader & Rooting this Asus ROG 5 phone?

my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)

miguel.jackass said:
my experience rooting was as follows:
I bought the rog phone 5 I005DA in china, in which the store changed the rom CN to WW version WW-18.0830.2101.86 and blocked the bootloader.
When my hands arrived I updated the firmware to WW-18.0840.2103.26 (the last one available).
I followed all the steps in this post and I was successful with root.
(Attention, extract the boot.img from the firmware that you currently have installed on the phone)
Click to expand...
Click to collapse
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money

m8822 said:
how did you open the bootloader? using asus app?
because it did not work before i rooted i was on 2101.86 at the time. i tried goind down to 2100.95 also did not work.
i had to rent a guy to do it via edl. which he is not sharing the method because he wants to make money
Click to expand...
Click to collapse
I updated the firmware to the latest official version, extract the boot.img from the last official firmware, and installed the official unlock tool from the ASUS website, I just had to follow the tutorial.

How To Guide Root Edge 2021 with Magisk

I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted.
Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled.
You should have Lenovo RSA installed which also has needed driver installed. Get the latest ROM from RSA and let it run rescue (phone will be wiped, but bootloader unlock wiped the phone anyway). Doing this in order to grab boot.img from C:\Program Data\RSA\Download\Romfiles\.
You will lose Widevine L1 after bootloader unlocked. Stop if it matters to you.
Are you ready? Let's do it
1. Unlock the bootloader if you didn't do it. The way to get "oem get_unlock_data" is to use mark on command window and copy 5 lines of code and paste on notepad, and make it into one line. Submit to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You should get the code in few minutes over email. Then use this below:
Code:
fastboot oem unlock (code received from email)
(your phone will be wiped]
To enter bootloader. Turn the phone off (make sure you make a backup and copied files to host computer) then press and hold volume down and power buttons.
2. Patch boot.img. After bootloader unlocked, you can stay on bootloader screen and run RSA rescue. Doing this to make your phone up to date as well as getting boot.img. Your phone will be wiped again during the process.
Now you have to do initial setup and install Magisk. Copy the boot.img to the phone and patch it, and copy the patched_boot.img back to host computer.
You can get USNF, fox Magisk Module Manager, Adaway, and other modules if you want.
3. Post root process. You should re-enable USB debug and allow the host computer.
Enter fastbootd
Code:
adb reboot fastboot
or
Code:
fastboot reboot fastboot
Flash patched_boot
Code:
fastboot flash boot
Press space once to make a space, drag and drop patched_boot into command window, and press enter.
Since 24.1, Magisk has different approach to hide/deny.
Enable Zygisk, enforce deny list, install USNF as module (don't worry about GMS because USNF takes care of it).
Put any app can detect root on deny list and reboot everytime you updated the list
Happy rooting

This is my first time rooting an android phone, so thank you. Perhaps I might suggest you add some more details to the "patch boot.img" section, as it took me some extra looking about before I figured out what I was doing.
Thankfully it's pretty simple, I just had to download the Magisk apk from its official github repo onto the phone (post step 1), transfer over the downloaded "boot.img" that the lenovo RSA app downloads during its rescue process (it tells you were it downloads it in the app), over to the phone (usb file transfer), patch "boot.img" on the phone using the Magisk app (install > pick file > done!), transfer back over the newly patched image (stored in downloads) to pc, and then use the above instructions to `fastboot flash boot /path/to/your_patched_boot.img` when the phone is once again put into fastboot mode.
Okay maybe that isn't super simply explained, but I wanted to write it down so others might benefit.
Thank you again, I now have my phone rooted, and will be looking into various things I can do with it, such as degoogling, TWRP (if it's even available for this phone), etc.
---
As far as I know, there is no TWRP yet pre-made for this phone. Unless I'm mistaken, I'd have to manually compile TWRP for my phone? (Not exactly sure how to go about that.)
Also, any tips for a newbie like me?

Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao

ninjakira said:
Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao
Click to expand...
Click to collapse
Yes, this is how I did mine

How To Guide Rooting the Google Pixel 6a

Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted

To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!

To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.

Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?

jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.

these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)

ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.

Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.

Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)

KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.

KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.

stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen

binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.

You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.

Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed

Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?

Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.

You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io

Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.

Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?