Question ROMs or roote methods? - Moto G Power (2021)

I just got one of these bad boys and i about rooted it and flashed an older models ROM before i realized i had the 2021 model

I imagine we will have to wait for stock firmware to show up before we can root

[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it

If you loaded Magisk and are having problems with banking app look at this post and he has another setting in Magisk that you can change to fix this. It is under the heading "a note about mobile banking apps".
Rooting with Magisk
Just a heads up to anyone who is wondering about root for this phone - I successfully rooted it with Magisk. It was pretty easy. Basically I just followed the same steps as outlined in this thread, which was for rooting last year's Moto G Stylus...
forum.xda-developers.com

kbwojo said:
I imagine we will have to wait for stock firmware to show up before we can root
Click to expand...
Click to collapse
Stock firmware maybe available with LMSA' s Flash rescue option
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

Fun... I made my first brick using that panda build box link.

kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
Is there a way to root the xt2117-1 version without a pc?

Knox-jack said:
Is there a way to root the xt2117-1 version without a pc?
Click to expand...
Click to collapse
No

Rooting these phones is dead simple. If you boot into bootloader mode, you can find your device's codename. Look for your codename on the lolinet site, select your varient, and download your firmware. Be sure to share the codename here so links can be updated.
Then you unlock your bootloader, patch boot.img you got from the firmware archive with Magisk, and flash the patched image through fastboot.

Seen any Roms for this floating around?

pontifier said:
Fun... I made my first brick using that panda build box link.
Click to expand...
Click to collapse
Did you FLASH recovery.img, instead of BOOT recovery.img?
It's pretty hard to perma brick phones these days. You can probably reflash device with LMSA -
Rescue and Smart Assistant (LMSA)(Motorola/Lenovo Only)
Rescue and Smart Assistant LMSA: Lenovo's Motorola Smart Assistant (PC) For Lenovo and Motorola Devices Only Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone...
forum.xda-developers.com

kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
I have tried this method on a linux system and a windows version and yhe twrp program always goes to straight to a lockscreen and doesnt stay

kbwojo said:
[Edited to clean up instructions]
I have the xt2117-4 version of the moto g power 2021 and the following worked for me to get root Using Magisk.
There is only one issue I had and this was because of Magisk. Some apps have issue's using fingerprint if Magisk is not set correctly. I will add the setting to fix fingerprint on apps at end. As always try at your own risk.
if you have a pin or security code remove it as touch screen for me did not work so had to manually type in twrp adb commands to backup boot and not knowing how to add security codes to twrp adb backup fails.
You need to have unlocked your bootloader and usb drivers from Motorola and phone in usb debug mode in developer options.
Now plug in usb cable to computer and phone
On the PC
Install adb (plenty of info on this and other sites how to do this). Then get moto g play twrp recovery image #1 from
BuildBox
mirror.theogpanda.workers.dev
Put it into adb folder on PC and rename it recovery.img
Start phone in bootloader mode by using power and volume down button
Once phone is in bootloader mode on pc at command prompt in adb directory run
fastboot boot recovery.img
this side loads it and does not replace your recovery.
Once twrp is fully loaded on your phone on the pc at command prompt in adb directory run
adb shell twrp backup B
this will back up boot.emmc.win to twrp directory on your phone and can be seen using a file explorer. The twrp folder is at the same levels as photos, alarms, etc
After backup is completed, hold down power button until phone reboots. I cannot remember if it boots to the phone or bootloader, at this point we want to boot to phone and allow usb file transfer.
Now use windows file explorer and copy boot.emmc.win to the pc and rename it boot.img and then put it in the adb directory. Reboot phone to bootloader again and in command prompt in adb directory run.
fastboot boot boot.img
this sideloads it and makes sure it boots right.
Put the phone to usb transfer mode again then copy boot.img to the download folder of the phone and install Magisk following method 2 from this guide
How to Install Magisk and Root Android Devices with it [2 Methods]
In this comprehensive guide, we will show you how to install Magisk Universal Systemless Interface to root Android devices. There are two different methods to install it – First…
www.thecustomdroid.com
Once rooted and finding a app that finger prints do not work on you can hide Magisk from the app. In Magisk manager click on shield at bottom. Click on magisk hide grey bar and select only apps not working as I heard putting in to many can cause issues (cannot verify but why try) Now programs should work with fingerprint.
Don't forget to keep original boot.img incase you have to restore it
Click to expand...
Click to collapse
Hello. I just got one of these on accident. Meant to get a G9 Power. Oh well. I will still love it. Having rooted countless phones and a great many Motos, I went to root mine without looking for instructions. I fastboot flashed the entire RETUS from lolinet, magisk patched and flashed the new kernel, and then booted to a phone without a working digitizer. Not only that, but when I flashed the original back on it, it didn't fix it. Still no digitizer. I then flashed the entire RETUS again, including the same kernel, and it fixed, but of course I had to set everything up again. I made a fastboot command list though, for flashing firmware from lolinet, if anyone could use it. It's on my computer though. I'll have to share it later. I just made this post to warn others of possible problems with a magisk-patched boot.img.
And also to thank @kbwojo . I've many times wished we could use twrp from a command line. Where did you learn that? Is there a manual?
Oh, BTW, the codename for xt2117-4 is borneo.

arkansawdave74 said:
Hello. I just got one of these on accident. Meant to get a G9 Power. Oh well. I will still love it. Having rooted countless phones and a great many Motos, I went to root mine without looking for instructions. I fastboot flashed the entire RETUS from lolinet, magisk patched and flashed the new kernel, and then booted to a phone without a working digitizer. Not only that, but when I flashed the original back on it, it didn't fix it. Still no digitizer. I then flashed the entire RETUS again, including the same kernel, and it fixed, but of course I had to set everything up again. I made a fastboot command list though, for flashing firmware from lolinet, if anyone could use it. It's on my computer though. I'll have to share it later. I just made this post to warn others of possible problems with a magisk-patched boot.img.
And also to thank @kbwojo . I've many times wished we could use twrp from a command line. Where did you learn that? Is there a manual?
Oh, BTW, the codename for xt2117-4 is borneo.
Click to expand...
Click to collapse
I did try a few things that didn't work. What I ended up doing was just flash boot the original boot.img and that basically reset magisk

Just giving an update and a thanks again to @kbwojo . I finally booted a patched kernel by patching a kernel extracted with twrp in the command line. All the kernels from lolinet caused me to lose touch support after patching, even if I was running the same version the kernel was from. But when I patched it after pulling the kernel with twrp, all is good. Whew. That was different.

Well i have done it. I have rooted my phone .
moto g power (2021)
model XT117-4
Android version 10
basebrand version : HA10_18.534.0273R BORNEO_NA_CUST
Kernel version 4.19.95-perf + #1 Wed Mar 31 12:08:54 CDT 2021
After extensive reading multiple threads i found one and followed the attemt using magisk and no twrp installed.
1st Magisk installed on phone
2nd Install magisk and then patch using the boot.img from a mirror site for Borneo
3rd (not sure yet) Install magisk and then patch file recovery.img (originaly TWRP 3.4 renamed)
renamed the 2 magisk files accordingly to boot and recovery
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
restarted phone directly back into fastboot mode
selected recovery option and started the phone
Sucessful Root!!!!

slickmojo said:
Well i have done it. I have rooted my phone .
moto g power (2021)
model XT117-4
Android version 10
basebrand version : HA10_18.534.0273R BORNEO_NA_CUST
Kernel version 4.19.95-perf + #1 Wed Mar 31 12:08:54 CDT 2021
After extensive reading multiple threads i found one and followed the attemt using magisk and no twrp installed.
1st Magisk installed on phone
2nd Install magisk and then patch using the boot.img from a mirror site for Borneo
3rd (not sure yet) Install magisk and then patch file recovery.img (originaly TWRP 3.4 renamed)
renamed the 2 magisk files accordingly to boot and recovery
Fastboot flash boot boot.img
fastboot flash recovery recovery.img
restarted phone directly back into fastboot mode
selected recovery option and started the phone
Sucessful Root!!!!
Click to expand...
Click to collapse
Can anyone confirm this works?
Just bought a G Power 2021 after thinking it was supported for custom roms already. It should just be arriving today and if i can't unlock the bootloader and root it I'm going to be returning it and getting the 2020, which I'm already considering even if i can be rooted.
Thank you

MyNameIsEarlB said:
Can anyone confirm this works?
Just bought a G Power 2021 after thinking it was supported for custom roms already. It should just be arriving today and if i can't unlock the bootloader and root it I'm going to be returning it and getting the 2020, which I'm already considering even if i can be rooted.
Thank you
Click to expand...
Click to collapse
the 2021 can be rooted, that is what I use with root, and heavily modified UI. You can even change things so system is writable (but will need a computer with linux, or a VM to complete the process), after bootloader unlocked and rooted. But does not presently have any custom ROMs for the device, however some in this branch of the forums have cited they are working on one. If I had the time to, I'd tinker and try my hand at porting LineageOS, or similar fairly easy to port, since TWRP is mostly done or doable for 99% of these devices, there are some that still have touch issues, and that seems to be all digitizer and screen related like mentioned in this thread. As long as you restore yours from the Motorola software and grab your stock files, when they are restored, it has touch, you know you can always fix it back even if a test flash of TWRP has no touch. But then it is not that hard to build from those files the TWRP, even in Android Image Kitchen. I made mine have touch support the hackish way before the compiled way.
So it can absolutely be done, just play things smart with it is all keeping backups of vital files and so on so you have stock even with data loss as the worst that would happen from messing about.
Edit: You will need to keep the device online, wifi and cell data for at least a day if not two before bootloader unlock option in settings will usually permit being toggled on. I know in my experience I got mine on a Friday, and it was not till Sunday about mid-day that it popped, and I'd check it every few hours that I was awake otherwise in that time.

Onoitsu2 said:
the 2021 can be rooted, that is what I use with root, and heavily modified UI. You can even change things so system is writable (but will need a computer with linux, or a VM to complete the process), after bootloader unlocked and rooted. But does not presently have any custom ROMs for the device, however some in this branch of the forums have cited they are working on one. If I had the time to, I'd tinker and try my hand at porting LineageOS, or similar fairly easy to port, since TWRP is mostly done or doable for 99% of these devices, there are some that still have touch issues, and that seems to be all digitizer and screen related like mentioned in this thread. As long as you restore yours from the Motorola software and grab your stock files, when they are restored, it has touch, you know you can always fix it back even if a test flash of TWRP has no touch. But then it is not that hard to build from those files the TWRP, even in Android Image Kitchen. I made mine have touch support the hackish way before the compiled way.
So it can absolutely be done, just play things smart with it is all keeping backups of vital files and so on so you have stock even with data loss as the worst that would happen from messing about.
Edit: You will need to keep the device online, wifi and cell data for at least a day if not two before bootloader unlock option in settings will usually permit being toggled on. I know in my experience I got mine on a Friday, and it was not till Sunday about mid-day that it popped, and I'd check it every few hours that I was awake otherwise in that time.
Click to expand...
Click to collapse
Thank you very much!
I'm perfectly happy with needing to make my own custom ROM. I've never done it, but I've been wanting to for quite some time. At least a few years.
The last 2 android phones I've been using couldn't even be rooted. Long story short, i bought a redmi 5, got it all setup great, then moved and the only service around my new area is Verizon so i sold that, bought a note 5, couldn't root it, bought a pinephone which i do love, but the battery life is really bad. So I've been using my note 5 that's close to a decade old so I'm just looking for a phone with root and a good battery life.
Look forward to getting mine rooted!

Quick question, hopefully doesn't derail too much. Wondering if there is any work being done on the XT2165-5 model? Can't seem to find anything on it?

Related

Unlock/TWRP/Root/Flash ROM - Nearly Noob-proof instructions

UPDATED to include instructions for flashing other ROMS
I've successfully unlocked, flashed TWRP, rooted, and flashed Lineage on both an XT1602 and an XT1607. I'd done this before on other devices, but had forgotten just how it all came together, so when I was done I went back and made this step-by-step guide. It's a bit shorthand.
Many thanks to squid2 for his TWRP port, to the folks who make superuser, to parrotgeek1 for superSUFixer.zip, and to spiked_mistborn for reminding me about it. And, of course, huge thanks to squid2 and Alberto97 for the killer Lineage ROM. It is far better than stock or the last Nougat CM. If I forgot anyone, or made any mistakes here, somebody please point them out. Have fun!
1. Preparation (if the links don't work, search on xdaDevelopers or with Google)
a. Backup entire phone to the extent you are able, either with a dedicated tool and/or to Google via the Android backup feature
b. Download and install Motorola Device Manager on your computer from https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481 so as to make sure you have the proper drivers
c. Download adb and fastboot tools onto your computer from
http://forum.xda-developers.com/showthread.php?t=2588979 or
http://forum.xda-developers.com/showthread.php?t=2317790​d. Download TWRP for Moto G4 Play to same folder as adb and fastboot tools from http://forum.xda-developers.com/devdb/project/?id=16870#downloads
e. Depending upon whether you want to flash Lineage or stay with the stock ROM, download to the same directory on your computer either:
i. Lineage and the Lineage SU addon (if you want root) from https://forum.xda-developers.com/g4-play/development/rom-lineageos-14-1-moto-g4-play-t3544646 and Google apps (arm 7.1 micro) from http://opengapps.org/; or,
ii. superSUFixer.zip from http://forum.xda-developers.com/g4-play/development/automatic-flashable-zip-fix-supersu-t3464396 and superusersu.zip from http://www.supersu.com/download
Note: I did not find superSUFixer.zip necessary when I intially rooted, but after later installing squid's kernel it was indispensable to reinstallation of superusersu.zip.​g. Attach phone to computer with USB cable, enable file transfer on phone and either copy the Lineage zip and Lineage SU addon zip and gapps.zip to your phone, OR copy superSUFixer.zip and superusersu.zip to the phone (you don't need to copy twrp)​
2. Unlock bootloader
a. Enable developer options (Settings/About Phone/tap Build Number 7x)
b. Enable USB debugging on phone (Settings/Developer Options)
c. Enable OEM unlock on phone (same)
d. Open command window and change to the directory where you put adb, fastboot, and twrp
e. > adb devices (to check that you are connected - you should get a response with a device id)
f. > adb reboot bootloader
g. >fastboot oem get_unlock_data
h. On computer, go to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a (you need to proceed through the login and to the second page)
i. Copy data returned by phone in the command window (make sure you copy all of it!)
ii. Paste that data into the Data Scrub Tool on the web page
iii. Copy scrubbed data, paste it into the box on the web page at step 6, and click the button; if it says you can't unlock your device, either you didn't copy and paste all the data, or your phone can't be unlocked and you're done; otherwise,​i. Copy unlock key from email
j. > fastboot oem unlock <unique unlock key>​
3. Flash TWRP
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery​
4. Flash Lineage and root, or just root -- when the phone has rebooted into recovery (you'll be in TWRP now)
a. follow prompts to make TWRP permanent or not
b. DO A FULL BACKUP OF EVERYTHING with TWRP
c. make sure you performed step b (or you may wish you had later, if something goes wrong!)
d. To flash another ROM, in TWRP
i. Wipe Data, Cache, and Dalvik. (Yes, you have to do this.)
ii. For Lineage - Install the Lineage zip file, the Lineage SU addon zip file, and the gapps zip file, one after the other, in that order, WITHOUT REBOOTING in between. TWRP will let you add all three to its queue to flash in order;
iii. For other ROMs - see instructions for those ROMs, but in general, install the ROM zip file, and then the gapps zip file, one after the other without rebooting in between. For root access, depending on the ROM, you may need superSUFixer, supersu.zip, or both; again, see the instructions for the ROM you are flashing.​OR
e. To stick with the stock ROM but get root access, DO NOT WIPE, just flash superSUFixer and then supersu.zip​
5. If TWRP does not automatically reboot your phone (if you unchecked the "reboot when done" box), then reboot to the System; if you left the box checked, then your device will reboot by itself once the zip files have been flashed.
6. Follow the prompts to set up your new ROM or stock Android.
7. Reboot into recovery (TWRP) and make another backup!
8. Want to get rid of the "Unlocked Bootloader!" warning screen? Flashing this file from TWRP worked for me (all the others I tried did not work):
https://forum.xda-developers.com/attachment.php?attachmentid=4065906&d=1488923356​
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
fireball0093 said:
For me, and it seems like I'm not the only person facing this issue either, I cannot unlock my boot loader on their website as it says it's not eligible. I do have the unlocked XT1607, bought it at Walmart for $150. I contacted their customer support and they said it can be unlocked and that they'd forward the boot loader string to the dev team and then follow up and email the unlock code, yet it's been almost 24hrs and no response which is saddening.
-Edit-
I did some research quickly, and it does fully quality according to their forums, as my CID value is 0x0032 and they state that devices with that CID are eligible for being unlocked. So they must be updating things in the background in their system
Click to expand...
Click to collapse
Any word yet on that unlock code?
loociddreemr said:
Any word yet on that unlock code?
Click to expand...
Click to collapse
After talking to their customer support, I never got an email. The next day however I decided to go online to their boot loader page and put my code in, then it worked! The data scrub tool or whatever it may be called that they have I recommend using it too.
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Thanks a ton for the guide
haher2 said:
where the twrp backups are stored? how do I transfer them to pc? (coz phone's capacity is not enough).
Click to expand...
Click to collapse
They are in a subdirectory of the TWRP directory. With the proper drivers installed on your PC you can transfer them via File Explorer. Or, 20 pounds/euros/dollars will get you a 64gb SD card.
3. Flash twrp
a. > fastboot flash recovery twrp.img
b. > fastboot reboot recovery
Click to expand...
Click to collapse
I tried to fastboot boot recovery from the bootoader but it didn't work. I rebooted the phone first and did it with: "adb reboot recovery" in windows.
Overall nice guide, works like a charm, i also flashed the unlocked bootloader warning with a custom logo.bin, no issues here and works like a charm (I flashed it with the stock logo you see when you first bought the phone with a locked bootloader)
Thank you!
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
loonix said:
Yah fastboot reboot recovery doesn't work. But very nice guide.
While in the main bootloader menu, the Power & Vol+/- buttons are active and you can go straight to recovery (and other modes) using the toggles. Perhaps this should be mentioned in the OP.
It should also be noted that after flashing recovery, one needs to go to recovery straight before rebooting to normal (system) for the TWRP/Custom Recovery to stick.
Also worth noting, Power + Volume Down will boot to bootloader/fastboot and then hardware buttons to navigate to all other modes as needed.
.
Click to expand...
Click to collapse
Yes and, adding to what you said, you need to re-enable the "Allow bootloader unlocking" and "USB Debugging" in Developer Settings if you failed to flash your recovery as the device expects to be flashed. Else, you'll get a "unable to load kernel" error in the bootloader log and being rebooted again to the bootloader menu.
Great tutorial indeed, thanks a lot. Nandroid backup doesn't worked for me but i'm going on.
Edit - worked after disable sd as internal memory
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
hamelg said:
I found the stock firmware for my phone here :
https://mirrors.lolinet.com/firmware/moto/harpia/official/
Is it possible to relock and revert the phone to stock after flashing twrp/Lineage/Root ?
https://forum.xda-developers.com/moto-g4-plus/help/moto-g4-plus-relock-bootloader-t3410399
does it work with g4 play ?
Click to expand...
Click to collapse
In concept, I don't see any reason why you couldn't use TWRP to flash the stock ROM and then fastboot to flash the stock recovery ... or fastboot to flash both (be easier and quicker). The Moto website may have instructions for re-locking.
mkollersms said:
I want to throw something out there, because it happened to me. In newer builds of Windows 10, you are no longer able to open a command window in a folder (the only available option is Powershell). I even tried that Path thing some Android tutorials talked about, and it failed. When I went to flash TWRP, I had to put twrp.img in my User folder directly (I only figured this out because when I did t-tab it fetched the .thumbnails folder). Make sure you know what CMD is referencing BEFORE you start the process, because doing so will save you a lot of headache down the road.
Click to expand...
Click to collapse
In a command window use the cd command to change directories. For example:
C:> CD \mytopdirectory\mysubdirectory
Another link to consider about OTA update if you stick with the stock ROM :
https://forum.xda-developers.com/moto-g4-plus/how-to/guide-sucsessfull-ota-update-rooting-t3472658
Thanks again.
If your phone is from Verizon Prepaid, Moto will say the device is not eligible to be unlocked. Knowing Verizon, it's not likely to be unlocked later along down the line either. Hopefully someone comes up with a good way to bypass this restriction and install some ROMs.
Does this method work on the Verizon prepaid model, or does it have to be from moto/amazon?
Moto g play twrp IMG file not IMG it's **** IMG file please develop it
Does this works with LATAM version? XT1601?
Thanks :good:

How to Root Nuu R1 (R5001LA) ?

I just bought a Nuu R1 Rugged Phone. It has Oreo 8.1.0 on it.
It is an "unlocked" phone. But I don't know if unlocked refers to the phone carrier or to the boot loader. (I'm thinking phone carrier.)
The last I rooted my tablets was Android 5, which required using a custom script that a dev here wrote that temporarily ran CW via fast boot.
I would like to root my R1. I hear now that Magisk is the way to go. (Instead of SU.)
Most every Guide says that I have to have TWRP installed before installing Magisk. But there's no TWRP for the R1. And I am incapable of compiling my own.
I learned, from Nuu Tech Support, that I can get into the phone's Recovery mode with some hidden button pushes. Here's a screen shot:
My first question is, could I simply install Magisk by selecting "Update from SD card"?
If it's not that easy, then, second: I can also get to a fastboot screen. (Not shown here.) Could I install Magisk from ADB on my computer?
I suppose a third question: Is there a version of TWRP that's compatible with this phone? And if so, how do I find it? It would be nice to have a Nandroid backup.
I am willing to show various screens that come up from various button pushes if that would help a dev here.
More data for TWRP'ing
So, I see that one needs an image of the OEM ROM to compile TWRP. I found two sites on the web that claim to have the ROM. (Before the R1 was officially released.) Sounds sketchy. Will try to get an image from Tech Support.
In the meantime, I found that the bootloader can be unlocked (or allowed to be unlocked) via a setting under Developer Options.
I contacted Nuu Mobile Support and they were kind to send me the MediaTek USB drivers for the R1.
It was a two step process to get the driver installed for ADB. But now I have access to the R1 via ADB.
I read here on the forums that I can boot TWRP via fastboot, and not risk ruining/corrupting the R1's Recovery Partition.
Anyone know of a TWRP model version that's close enough to work on the R1? (I presume a TWRP for another MediaTek device might work?)
I would hate to try KingRoot to get root.
I found a website called unofficialtwrp.com. It has a TWRP for the MediaTek 6739, running Oreo 8.1, with 16/2 GB. That's exactly what the Nuu Mobile R1 has.
So, hopeful that this would allow me to root my R1, I tried it. (Short version: Didn't work.)
I already had ADB installed and could talk to my R1 via ADB.
But once the R1 had booted into fastboot mode via ADB, I got a message from fastbood devices that it was "waiting."
I learned that that message means that I didn't have drivers for fastboot.
I ended up installing a fresh version of Win8.1 and using the Windows' updater to find the needed drivers. I had to have the R1 plugged in to the USB in fastboot mode for this to work. After that, I could talk to the device via the fastboot command.
So I unlocked the boot loader (which wiped my data - not every Guide warns you about that) and I did "fastboot boot recovery.img."
I got the message that the recovery file had transferred. After abotu 15 seconds, the phone rebooted. But no TWRP.
Rats.
I didn't want to try the fastboot flash command in case this unoffiical twrp from an unofficial site bricked my phone. If I understand things correctly, booting in fastboot to the recovery.img should give me a temporary instance of TWRP.
Presumably, after copying Magisk into memory, I would be able to get root that way.
PMikeP said:
I found a website called unofficialtwrp.com. It has a TWRP
Click to expand...
Click to collapse
Whoa you have been busy you must've heard XDA helps those who help themselves.. :highfive:
I just dropped by to say, 1st rule of modding is taking a pristine stock backup..
For MTK devices, there is a tool called SP Flash Tools, a quick search will help you take a full backup using this tool.
Afterward, you can even try using SP Flash Tools to flash a Magisk patched boot image to your device for ROOT!
Hope this helps!
Thanks. I did see SP Flash Tools mentioned and I did take a look at it. While I've rooted before, I'm trying to get my head around a Scatter File.
Everything I've read so far - well, almost everything - says that I need TWRP to get Magisk installed. But if you think it can be done via SP Flash Tools, I'll start playing with it.
Root nuu r1
Did u ever manage to figure out how to do this & get TWRP to install? :fingers-crossed:
No, I haven't had time to play with rooting lately. I still would like to root it tho.
Anyone know how to root the nuu phones?
someone has the boot.img i need the image
I will port TWRP for you in case you have stock recovery.img
jjgvv said:
I will port TWRP for you in case you have stock recovery.img
Click to expand...
Click to collapse
plis
do you have stock rom?

How to root with Magisk Lenovo M7 (TB-7305F) / Android 9

Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
hw-schrauber said:
Hi,
I'm trying to root the tablet. Unfortunately so far without success. I have tried several rooting tools (Desktop and Tablet App).
What promised most success is Magisk. It is also known that it works with Android 9. I copied the bootimage on the tablet from the stock-ROM, patched the image with the latest Magisk-APP (7.5.1) (Magisk 20.3 (20300)). Then back to the PC, and with fastboot written to the boot partition. After unlock the partition, this was possible. After a restart, however, the tablet will remain on the boot logo. Original stock-ROM on it again, tablet runs again (no boot loop).
Then I looked at the image sizes. The original is 16,385 kB. However, the patched Magisk file is only 7,148 kB. That can't really be, can it?
Does anyone have an idea of what this can be, or what I'm wrong about?
Thank you for your help.
Click to expand...
Click to collapse
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Augustoandro said:
Seems like Magisk Manager is not able to patch the boot.img properly.
The size of patched image is never lesser than the original boot image.
Try patching your boot image using an older version of Magisk Manager.
HIT THANKS IF FOUND USEFUL
Click to expand...
Click to collapse
Thank you Augustoandro, but unfortunately I can't use an older version. Since I want to run my device with magic, I only have to install the apk. If I take an older one here, I will only get to the patch buttons when the app is updated.
So this proposal does not help.
Perhaps it is also because the 7305F does not seem to have the partitions set up as usual. If I want to make a BackUp using the tool "MTKdroidTools 2.5.3" (screenshot), it means that the partition structure does not fit and no backup is possible. A root with the tool is also not possible.
Is there another idea?
For more information:
CPU MT8321 (32bit), Memory 1/16GB, kernel 4.9.117+ (#25.10.2019)
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
macgajos said:
I was able to patch the file with magisk and flash the
boot, but no root. Were you able to find a solution to your problem?
Click to expand...
Click to collapse
You have to root by means of Magisk: Magisk itself doesn't root the Android.
jwoegerbauer said:
You have to root by means of Magisk: Magisk itself doesn't root the Android.
Click to expand...
Click to collapse
Thank you for your reply. Sorry for not being clear here: I get "Magisk is not installed" info in magisk manager after flashing the magisk patched boot img in fastboot mode.
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
hw-schrauber said:
I have found the way to install MAGISK. You have to install MAGISK to the recovery.img. Then start in Recovery-mode and the system will boot to the normal System with installed MAGISK. Works perfect to me.
Some more information. There is an update named TB-7305F_100049_200508_ROW. After you have update to this release, you haven't MAGISK installed and you are not able to reinstall MAGISK. Also, when you get the original recovery from the version it is not possible. As well, I have tested to use the working recovery from the prerelease with the newest release, this also don't possible. For me the only working release is the TB-7305F_100043_200223.
If someone flash a later version that woks, please let know here!
Click to expand...
Click to collapse
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
macgajos said:
Yes, recovery is the way to go. I have figured it after reading this:
topjohnwu - install.html#boot-image-patching
As I have X model, TB-7305X_S100043_200224_ROW and TB_7305X_S100062_200610_ROW was the ROM that worked. Cool thing is that you can get roms from lenovo with "Rescue and smart assistant" app.
The trick that makes magisk rooted all the time is to choose 'reset phone' after rooting. This would cause the tablet to start with root each time.
Click to expand...
Click to collapse
What do you mean with reset? When MAGISK is in recovery, the only way to start is in the recovery-mode. Then you have ever MAGISK working when it is installed!?!
Today I have seen, that there is a new version for the "F" model. TB_7305F_S100055_200703_ROW. I will test and report!
How do I pull the Recovery.img from this tablet in the first place? Please help. Thanks.
Hi. I am trying to manage root without twrp for a couple of days. I picked up the solution with recovery.
I've tried to flash root to recovery with magisk patched recovery.img via fastboot. But the .img size is to large (is texted in fastboot). By the way i was curious after magisk patching cause the patched .img file has the same size as the original .img file. I downloaded twrp port tool and ported recovery.img and got a recovery.img with a smaller size so i was able to flash it via fastboot. Fastboot flash recovery recovery.img
Fastboot reboot.
Device is booting to Lenovo splash screen with the warning that the device is unlocked and boot in 5s. Could wait forever. After 2min pushed vol+, Lenovo Banner starts to flip and it booted to system.
But no root.
Reboot.
Boot with key combo
Hold Vol+ and power, released as lenovo splash with the warning appears. Nothing happend.
Pushed vol+. Nothing happened. It stuck at splash.
After that i could not boot the device with power key anymore. It stays at splash every time i rebooted.I had to reboot to recovery and do rebooting to system from recovery.
From bootloader i was able to boot to system also.
I like to flash magisk patched boot.img via fastboot but magisk doesn't make the .img file smaller.
I tried with sp flash tool but after patching the img is not signed anymore soflash tool doesn't flash it.
So that is my state for now.
_
_
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
PART HO said:
Hi all,
I want to remove all of the google apps from my tablet 7305F in a bid to save ram, adb does most of the trick. can even uninstall play store, but the google play services com.google.android.gms is very hard to disable, keeps popping a "play services has stopped" message frequently.
till now I was able to free upto 50 % ram using this trick only its annoying that the play services message keeps popping.
Click to expand...
Click to collapse
.....Install twrp and root rights, it's not difficult. You can then do whatever is needed
I rooted my Lenovo M7 (TB-7305X) the folling way
On a PC Get and Install LMSA "Lenovo Rescue and Smart Assistan"
* Using LMSA do a recovery, this way you are sure you have al the drivers working and that you have a correct rom
On the Tabled enabled developer mode
* enable remote debugging
* enable oem unlocking
Unlock the bootloader using fastboot
(you will find adb and fastboot in the location where LMSA was installed)
P.S. this will erase of data on your tablet
* adb reboot-bootloader
* fastboot flashing unlock
* fastboot reboot
PS tablet well be in orange state (because the bootloader is unlocked)
* android boots
On the tablet create a rooted boot.img using magisk
* download and install the latest magisk.apk
* look for boot.img (boot.img_verified) the ROW downloaded by LMSA (some where in c:\programdata)
* uplad the boot.img to the tablet
* start magisk and patch the boot.img file
* download the patched boot.img
On the PC start MTK_Flash tool
P.S. this will erase of data on your tablet
* open the download tab
* the download agent should be set by default (MTK_AllInOne_DA.bin)
* select the scater file (from the LMSA rom directory)
* deselct all files except BOOTIMG
* change the location of the BOOTIMG and select the pached boot.img
Flash boot.img by clicking download
Rooting instructions for TB_7305X (Should be the same for TB_7305F using TB-7305X_S100043_200223_ROW)
Install Rescue and Smart Assistant from Lenovo
Start Rescue and download latest ROM
Replace the latest ROM files from C:\ProgramData\RSA\Download\RomFiles\TB_7305X_S1000xx_xxxxxx_ROW with the ones from TB-7305X_S100043_200224_ROW
Can be downloaded from:
https://mirrors.lolinet.com/firmware/lenovo/Tab_M7/TB-7305X/
Rescue the device as per the RSA instructions
Install latest Magisk
Upload recovery-verified.img from the TB-7305X_S100043_200224_ROW ROM to the Internal Shared Storage of the device in Download directory
Run Magisk Manager
Patch the recovery-verified.img with magisk
Copy the newly created magisk_patched-xxxxxxxx.img file in Downloads to C:\Program Files (x86)\Rescue and Smart Assistant and rename to magisk_patched.img
It will later be used to flash the device after unlocking
Enable developer mode on the device
From developer options enable:
OEM Unlocking (needs Internet connection)
USB Debugging
Start cmd and navigate to C:\Program Files (x86)\Rescue and Smart Assistant directory
adb reboot bootloader
Wait for reboot. You will see “=> FASTBOOT mode …” message when ready
fastboot.exe flashing unlock
Press volume up key to confirm
fastboot flash recovery magisk_patched.img
disconnect USB cable
press volume-up+volume-down+power buttons to switch off the tablet
press volume-up+volume-down+power buttons to switch on the tablet in Recovery mode
When Lenovo logo appears release the buttons.
Wait several minutes. Do not give up, do not restart. It takes time.
Reconfigure device
Enable USB Debugging
Disable System updates
Reinstall Magisk
Your device is rooted.
Whenever you want to use it in rooted mode you have to switch to recovery mode
The normal mode calls boot.img where magisk is not installed and the device will not be rooted.
You may proceed with removing Orange mode 5 sec wait message. Instructions available on the Internet.
If at some point the device writs back the original Recovery mode just reflash with magisk patch recovery-verified.
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Skylon5000 said:
Hi,
I would like to root my Lenovo TB-7305F as well. The file I have leased from Magisk generates "size is too large" in fastboot. This problem has been written by others. I have compared the original filesize and the patched filesize. They are identical. Exactly to the byte. I did it exactly as greenbul describes. However, he uses the 7305X and I use the 7305F.
Also the SP tool cannot upload this patched file.
I have the 1GB 7305F model.
Do you have any idea?
Many thanks
Andreas
Click to expand...
Click to collapse
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to
Lenovo 7 tb-7305f
Root and TWRP
Lenovo Tab M7 - Обсуждение - 4PDA
Lenovo Tab M7 - Обсуждение, Планшет, 7"
4pda.to

Question Moto G Power (2021) RETCA

Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
jwreidmoto said:
Hello, I am from Canada and I just got a Moto G Power (2021) XT2117-4 with the firmware QZBS30.Q4-43-129-2. I unlocked the bootloader thru Motorola with no problems. I installed Rescue and Smart Assistant and downloaded my firmware. I patched the boot.img thru Magisk and flashed it to my phone using ADB. I was not able to achieve root. I also tried to boot thru recovery mode but got the no command sign. I then rescued my phone and tried it again flashing to both boot_a and boot_b still to no avail. If anyone has any info on why this is and has a solution to my problem it would be greatly appreciated.
Click to expand...
Click to collapse
Does the phone boot with the patched boot.img ?
sd_shadow said:
Does the phone boot with the patched boot.img ?
Click to expand...
Click to collapse
Yes.
jwreidmoto said:
Yes.
Click to expand...
Click to collapse
What does the magisk app say?
Can you share a screenshot?
[Guide] Using Fastboot.exe with Motorola devices
Guide: Using Fastboot.exe with Motorola Devices If your device has its own section please post in that section. You can ping me with @sd_shadow MediaTek or Qualcomm Chip? Do I have a MediaTek Device? see post #26 Info: If you have a MediaTek...
forum.xda-developers.com
sd_shadow said:
What does the magisk app say?
Can you share a screenshot?
Click to expand...
Click to collapse
That is just how the patched boot.img is created.
Now you have to flash it with fastboot.exe
Been thru that already no root.
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
I am going to start from scratch again. I don't think I made a mistake because I rooted my G7 Play this way too. I also get feedback from terminal confirming flashing.
jwreidmoto said:
Do I have to rename it to boot.img when I flash it or can I leave with with the patched name?
Click to expand...
Click to collapse
[Guide] Root Motorola with Magisk (UnLocked Bootloader)(Non-TWRP method)
Root Motorola Devices with Magisk Note: This method has been working with most Moto Devices that the Bootloader can be UnLocked. If the Bootloader cannot be Unlocked this method will not work. Please only use this as a reference. If you require...
forum.xda-developers.com
and
How to root your Android smartphone: Google, OnePlus, Samsung, Xiaomi, and more
Rooting your phone is still possible — and fun — these days. Here's how to do it on your Android device.
www.xda-developers.com
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
jwreidmoto said:
Followed link instructions exactly and still no root. Maybe I have to go with a TWRP recovery method. I will keep checking forums for others having same issue.
Click to expand...
Click to collapse
Ok, if you want help you have to give details.
No root means nothing.
I downloaded firmware from Rescue assistant copied boot.img to phone selected it thru magical and patched it. Copied patched boot.img to PC. Put it in ADB folder renamed it back to boot.img. Opened up ADB terminal and flashed - fastboot flash boot boot.img. Terminal said writing boot_a......okay.....finished. reboot no root. Tried again with flashing to boot_a and to boot_b. Reboot still no root. That's about all I can tell you everything checked out including ramdisk - yes in Magisk, boot.img from same firmware that is currently on phone. Not sure why it's not working.
Actually, sorry phone is now rooted. Once I added root checker to superuser in magisk it showed phone was successfully rooted Thanks for all your help!
Just to confirm, as I've yet to root my device and may encounter this same issue. Did you solve it having done anything different with the rooting procedure or was it a simple matter of adding the root app to Magisk SU? If the latter, Did magisk display the SU prompt at all?
Yes, the root instructions are good. I think why Magisk did not prompt me, initially was because my phone was setting up for the first time and it was bogged down by Google restoring apps etc. Now Magisk prompts me every time for root apps.
So I'm Down to Help this is what I did. So
Download Rescue and blah blah assistant
Found My Phone Checked and Double Checked all information then when I did so I extract led the Folder to My desktop, looked inside it's little bundle of goodness to find boot.img pulled it out and connect my Moto G.
At This Point I Just Opened up My Phone storage (from My P.C) pulled it out and stuck it in my main storage.
At that point Went and Got Magisk v.23 renamed the download as Magisk v.23.apk
Then Riped her Open Like A wild animal installed the .apk (If the File Manager or whatever you are using won't let you install go to settings for the particular File Manager you are using on your phone and allow download a from unknown sources)
Pulled out the boot.img I put in my main storage and went to My sexy New Magisk App and selected "select and Patch a file"
At the Point stepped out for a quick smoke and had a tug.
Then your final product will be Magisk_patchedv23.img (or something like that)
Then after you get all that mumbo move that back to your P.C
I assume you have adb fastboot
So then I pull it up (not sure if it affects anything but I did adb Root)
Anywho first I did
adb devices -l
As soon as I see my phone se then I know I got it.
#also side not make sure the wording next to the device says device
Ok so at the point type
adb reboot fastboot
Then repeat same command as the adb one
Fastboot devices
#seeyour device? Dope
Then wherever you put that patched image sometimes you need to put the FULL path
Example for me it was
Fastboot flash magisk_patched.img boot
Which didn't work so tried the _a still nothing soo hence the FULL PATH I put it on my desktop if you don't know the full path right click the file and hit properties
final Command for me
fastboot flash boot C:\Users\insan\Desktop\magisk_patched.img
Boom Done and Done!!!! And as always take Back Ups Before and After and Save that Patch .img
I've needed it like 10 times !
Hope That Helps Ya
And the last pic Is Proof
God Bless, and Good Luck!

How To Guide [GUIDE][ROOT][MAGISK] How to Root ACE 2/11R with Magisk without TWRP

Hello everyone hope you are all keeping well.
Since I believe that many of you don't know about this, I've decided to share the steps I've done in order to root the OP 11R ( ACE 2 )
I cannot be responsible if you brick your device. Your phone, your choices, your responsibility!
1 - Unlock the bootloader (if you haven't done it already...beware that this will erase all of your user data). To do so, you must:
Enable developer options
Enable the "OEM unlocking" option
Enable USB debugging
Have both adb and fastboot, from SDK Platform Tools available on your PC
Connect your phone to your PC using the USB cable and run the following commands:
adb devices
adb reboot bootloader
(so your phone will reboot into fastboot mode)
fastboot flashing unlock
(device should now unlock)
fastboot reboot
(device reboots with an unlocked bootloader and data partition wiped so set up the device from scratch again)
2 - Download OP 11R stock boot.img that you may find later on this post, that matches your current build.
Copy the boot.img to your devices internal memory
Leave a copy of it on your PC (on the same folder you have adb and fastboot...you never know if you will need to use it again in the future...to restore the stock boot.img, aka revert to stock...)
Indian Boot.img A_0.8 - download
3 - Download latest Magisk Manager from HERE and install it on your phone
4 - Open Magisk Manager App and press:
Install
Select and Patch a File
Browse to the path where you saved stock boot.img and select it
Magisk Manager will now patch the boot image and store it in [Internal Storage]/Download/magisk_patched.img
5 - Copy the patched boot image from your device to your PC (Store it on the same folder where you have adb and fastboot)
6 - Flash the patched boot image to your phone by running these commands (remember, you must have patched boot image on the same folder you have adb and fastboot and, of course, your device must be connected to your PC...)
adb reboot bootloader
fastboot flash boot magisk_patched.img
fastboot reboot
7 - After the phone boots up, hopefully with a normal boot (almost feels like nothing happened....), install/open Magisk Manager App again and watch Magisk doing it's magic!
8 - Enjoy!
All credits goes to topjohnwu and his incredible work with Magisk.
Why title says NORD 2T?
firoz3321 said:
Why title says NORD 2T?
Click to expand...
Click to collapse
MB ... typo
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
firoz3321 said:
Thank you for detailed steps.
Is there any benefit with KernelSU over this method ?
I always used Magisk on OP8, but recently saw an article for OP11 with Kernel SU.
Also is there MSM tool support to recover softbriked device ?
Click to expand...
Click to collapse
Sorry but there is no msm tool available for new OnePlus devices. + You can use Fastboot enhance tool from github to recover softbrick , magisk is always recommended for rooting because of ease of steps and simple to use
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
saifsohel said:
Hello, thanks for the detailed instructions. Today I updated to A. 10, and unfortunately lost my root access. Without the root cannot extract the boot image. If you're already updated and have a backup of A. 10 boot, can you please share?
Click to expand...
Click to collapse
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
shiki_senpai said:
i didn't got the update yet ... + oxygen updater also showing A.08. i will update this post soon as I got update
Click to expand...
Click to collapse
Then remember to take a backup of the boot before rebooting. I messed up big time.
Thanks for the detailed information man. Can I know if bootloader unlock decreases widevine L1 to L3? As this was case with my OP6

Categories

Resources