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=2317790d. 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:
Related
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
Hi guys
I've tried everything, i bought this watch today and i was so hyped about it.
I tried to update it to 6.0.1 using adb on my mac.
The problem is when i do this command "adb reboot recovery" and then "adb devices" it shows no devices! (before entering recovery it actually shows the device in the list!
This is so wierd and there is absolutely no solution that worksfor me... anyone has any ideas?
Edit: The problem more clearly:
Ok guys so the problem was that my LG G Watch (square) for some unknown reason wasn't available in recovery mode through adb, that means when i would use the command "adb devices" in recovery mode, i would see the empty list without any devices, while anywhere outside the recovery (system, fastboot etc) i was able to communicate with the device. (Since i was so frustrated i didn't make it clear enough in the original post ) And my watch was on 4.4! ( :| )
The solution:
Ok, so the problem was the watch, because i tried a OS X (and a windows on the same mac) and 2 windows laptops, all with drivers installed (and done the "update driver..." stuff on all) and the problem still persisted.
This solution is for people whose device is not displayed while in the recovery mode in cmd/terminal.
This is what i did: (i didn't do this in the order because i literally tried every solution on the internet! but this is the order that i was finally able to solve the problem with.)
1. I downloaded this tool from this topic (go to the link, click on LG G Watch > G watch script tool > LG G Watch Restore Tools V9.8.zip)
2. Run this bat (i used a windows but it works on the mac too) 1 LG G Watch Tools for Windows.bat
3. Let it recognize the device
4. When the blue list comes up choose 4 ( you should be in bootloader)[cmd > adb reboot bootloader] when it's done, your device should be on 5.1.1.
5. Download this tool from this topic
6. In cmd/terminal type "adb reboot bootloader" then type "fastboot flash recovery [draggedfile] and drag the downloaded .img to the cmd and press enter.
7. Now you have installed a custom recovery called CWM
8. In cmd type "fastboot reboot" then after reboot "adb reboot recovery"
9. Now inside this tool swip down to "install ..." and swip (to right i guess) and stay here on the watch.
10. Now in cmd type "adb push -p [draggedfile] /sdcard/0/Download" and drag the 6.0.1 OTA update and press enter
11. Now the update is in your device as a zip file in this path : /sdcard/0/Download (it didn't work when i wanted to push it to "/sdcard" folder so i had to go deeper)
12. Now swip on install from sdcard and navigate to the path and choose the zip file.
13. Done! you have successfully updated your device without going into recovery mode!
Thank you very much @lfom for sticking to this topic and helping out in the process!
I just tried it with windows as well and ain't working... im so frustrated...
There's a guide in General section that you may want to read:
http://forum.xda-developers.com/g-watch/general/guide-how-to-fix-6-0-1-adb-bug-t3347122
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
miladkalbasi said:
Thank you very much for your response, but my watch is on 4.4w and i just want to update it because im not able to update it via the sysyem update function... So i guess that guide is no help to me
Click to expand...
Click to collapse
So you are on 4.4 and want to update? What else? Rooted and custom recovery?
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
lfom said:
So you are on 4.4 and want to update?
Click to expand...
Click to collapse
Yes, i bought this watch yesterday and it's on 4.4 and i want to update to 6.0.1 (or any newer update)
lfom said:
What else?
Click to expand...
Click to collapse
I have never had developer experience with any android device before so i learned everything in like 6-7 hours, therefore there is a high probability that i might have made mistakes in the way but here's what i have done so far:
1. i tried to update the watch from "About" on the watch itself but kept getting "Something went wrong" error and couldn't fix it.
2. so i moved on to use my mac to do the update which took me 4-5 hours to figure out what SDK platform tools, ADB, OTA updates, bootloader, fastboot etc means.
3. i figured out all this and went on until i reached here: i have to use this commend in the terminal (it's like windows cmd): adb devices
so that i know my device is there and authorized on the companion android device (i see the device in the command shell), i then proceed to this command : adb reboot recovery , as soon as i type this command and press enter, the device reboots and enters recovery mode but it is also vanished from the system, by typing adb devices i no longer see it, i just see an empty list.
4. i also did unlock, wipe, restore back to stock ROMs (5.1.1 ROMS), tried TWRP (i then realized i can't do OTA updates with this tool)
5. i did all of these steps several times and always got the same results!
6. i also tried the windows on my mac and got the exact same results.
7. i tried 3 different windows laptops in the household (2 of which run win 8 and one runs win 7) but was not able to make it through installing the drivers (i couldn't see the android device when i clicked on update drivers...)
lfom said:
Rooted and custom recovery?
Click to expand...
Click to collapse
no i haven't rooted the device
lfom said:
I think there's a tool to flash stock LG ROM, you may want to search for it. This tool may help too:
http://forum.xda-developers.com/g-watch/development/script-lg-g-watch-tool-t2820863
Click to expand...
Click to collapse
Thank you very much for your suggestion, i have already tried that and it doesn't actually give me any more options that i already have.
I've come to the believe that it's either my laptop (which only has 2 USB 3.0 ports and some people say it causes issues) or my watch. I have to try to use a different computer but i don't think i can access more computers or solve the driver problem on the 3 existing ones.
I really wish i could solve this by myself, i live in a country that i can't access warranty and stuff so i either have to fix it myself or get a professional's help.
i found this topic as well, that's exactly my problem.
I can communicate with the watch in bootloader and TWRP but not in the recovery mode (stock)
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
lfom said:
Well, that thread has a tip about how to access watch in Recovery, it says it will be listed in Windows as an unlisted device, you have to install drivers for that...
It seems that 4.4w is too old so it won't get updated. But I remember reading another thread where the user was able to update it, probably using a full image of system or using TWRP.
If you can get to stock 5.1.1 I remember reading that if you install TWRP you can flash 6.0.1 zip, so maybe it's the best way to go. Also, probably you can force OTA on 5.1.1 (maybe any 5.x) if you do a watch reset while it's in cradle.
Click to expand...
Click to collapse
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
miladkalbasi said:
Thanks for your response.
Do you mean i use boot, recovery, and system images to get to 5.1.1? i have already done this (through bootloader) and (i guess it's called the ROM?) it's on 5.1.1.
I used TWRP but when i try to use adb sideload and use the 6.0.1 zip file it gives me error saying it failed. (gives me this error on the mac : Total xfer: 0.00x , and "failed" on the watch)
I used CWM right now and it gives me the same results as the stock recovery (not being able to communicate when i enter recovery but when i go back to menu i can communicate with the device again!)
Is flashing the update more complicated that i think it is? i can't find a tutorial for TWRP and flashing an update...
O and about the last part that u added, i don't know how to force anything in that matter...
Click to expand...
Click to collapse
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
lfom said:
ROM is basically kernel+system, what the device needs to run an operational system, but may include other files like boot and recovery.
As "to force an update", you don't need do to anything else but reset the watch while it's on cradle charging. It's a way to force the system to update to latest firmware, as checking in the About page does not work always if there is an actual update available. It's more like a trick. But I am not sure if it only works if watch is stock (all files from manufacturer's ROM). If I remember correctly, as it's possible to flash 6.0.1 update directly from TWRP then maybe OTA also works with TWRP (I can't verify as my LG G Watch W100 is all stock).
As for adb, probably only custom recovery (TWRP is the most common) supports adb, stock recovery probably not. Anyway, this thread is about rooting with a working TWRP (it says the official one has a bug with 6.0.1) maybe it's what you need:
http://forum.xda-developers.com/g-watch/development/guide-how-to-root-lg-g-watch-6-0-1-t3320512
Oh, and by the way, you can push files to /sdcard before booting to TWRP, it won't be erased unless you factory reset the watch or use recovery to wipe data partition, the same way it works on phone.
Click to expand...
Click to collapse
I solved the problem!
Funny thing is i didn’t see your answer and fixed it by myself but you actually proposed exactly what i had to do! Thank you very much for your effort and spending your time on this topic!
For others who might run into the same problem in the future I'm gonna update the first post and say what i did.
Cheers!
This guide is outdated now. Please refer to the thread OPs of the respective projects.
Hi all, I am starting this thread with the very reason to educate and help newbies as well serve as a resource guide that could be used by all. I will try my best to update this thread often. You can ask any question regarding Moto Z2 Play aka albus here. Our XDA Community will try to help you. Make sure you always read before posting the same queries. If you're stuck in a problem, make sure you provide us with as much as information of what you were exactly doing and what happened along with your device details ofcourse.
Also remember that unlocking the bootloader will void your warranty. Relocking it won't give you back your warranty. If you are visiting a service center for repairs of any kind, they will come to know that you have unlocked your bootloader (you put a code on their site lol). But yea you can try your luck by visiting them after you lock your bootloader using the fastboot firmware.
No one, but you are responsible for whatever you do to your device. If something happens due to your ignorance or lack of backups or knowledge, only you are responsible, not the developer, not the XDA Community. Just read the respective posts, search (at XDA and at Google) before posting and you might probably find answers. Cheers.
Setting up adb/fastboot on your system:
These drivers are quite essential for every android user.
How to use?
Windows:
Minimal Fastboot/ADB: https://www.androidfilehost.com/?fid=745425885120698566
Just install the setup. Reboot your phone in bootloader mode (Power off and then press and hold power + vol down simultaneously) and connect via USB cable. On your computer, navigate to the directory where you installed them. Press shift+right click and choose Open Command Window / Powershell here. Type:
Code:
fastboot devices
If you get a serial number, fastboot is working.
For adb to work enable Developer Options and turn on USB Debugging on your device. Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Now authorize USB Debugging by allowing it (Choose something like Always trust)
Type this on your command window / powershell window:
Code:
adb devices
Again it should return a serial number.
If both these fail, you might consider rebooting your computer or even installing (MDM) motorola device manager. Make sure you don't have any crappy or outdated drivers. (Always keep your system upto date ) Anything else, you'll have to google up things.
Motorola Device Manager:
For more info regarding adb/fastboot open this: https://developer.android.com/studio/command-line/adb.html
Linux users might need to install it from their respective package manager repos, Ubuntu for example:
Code:
sudo apt install android-tools-adb && sudo apt install android-tools-fastboot
Arch Linux on the other hand:
Code:
yaourt -S android-tools --noconfirm
Similarly for the other distros.
Commands are the same. fastboot needs to be used with sudo.
Unlocking the bootloader:
Unlocking Bootloader
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
Unlocking Bootloader:
1- Register
Head to Motorola website https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b and register your E-Mail ID.
Open Settings app on your device and go to About Phone section. Next, tap 7 times on Build Number and get the Developer Options enabled.
Head back to Main Settings Menu and go to Developer Options and switch the 'Allow OEM Unlock' option.
2- Getting Unique ID for each device
Reboot to Bootloader/fastboot mode (power off the device, then press the power and volume down buttons simultaneously).
On your computer, go to the directory where you installed the adb/fastboot drivers (or make sure this folder is in your $PATH to acess fastboot and adb system wide).
Open CMD/Powershell/bash in here. (Windows users might need to Shift+Right Click and choose "Open Command/Powershell Window here" , Linux users can open terminal as per their respective distro. Now , type
Code:
Code:
fastboot oem get_unlock_data
You will get something like this:
On a Windows Desktop, the returned string format would be:
Code:
(bootloader) 0240540162024205#4C4D3556313230
(bootloader) 30373as313630330df332323239#BD00
(bootloader) 8A672BA4746C2CE0a328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0240540162024205#4C4D355631323030373as313630330df332323239#BD008A672BA4746C2CE0a328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlocking the device:
Check if your device can be unlocked by pasting this string in the specific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page. Click on it and wait for the unique code to be sent to your mail.
After you got the code type the following :
Code:
fastboot oem unlock your_code
and wait your device to reboot !
Flashing TWRP Recovery:
IMPORTANT NOTE :
At first boot twrp will ask for "Swipe to allow modifications for /system" and if you choose to allow it system partition will get modified. So if you choose to reboot back to OS without performing anything in twrp, the OS won't boot (as verity check is enabled in stock OS/kernel) . To avoid this you have to flash either SuperSU or flash any of the verity disabler zips there in xda.
Force encryption is enabled by default in stock OS and twrp will successfully decrypt /data at first boot if all goes well
If in case decryption doesn't go fine, twrp will popup a dialog box asking for password and that means decryption went wrong and you would need to format data once via twrp wipe options and reboot back to twrp for functioning of /data
Downloads : http://www.androiddevs.net/downloads/
Keep the twrp recovery file (.img extension) in the adb/fastboot folder
Reboot to bootloader, open cmd/bash and type:
Code:
fastboot flash recovery filename.img
(if you want permanent flash) or
Code:
fastboot boot filename.img
(if you want temporary
boot)
Now you must flash the verity disabler zip.
HIGHLY RECOMMENDED:
After the twrp is done and you have successfully rebooted to system, it is a good time to reboot to TWRP again and backup your phone. (System and Boot most necessary)
Flashing Stock ROM:
Will be updated as soon as the fastboot version of the stock ROM is available.
Unbricking your hard bricked/dead device:
Connect your device via the usb cable, extract this zip file to the adb/fastboot folder and then run:
blankflash.bat file if on windows; the .sh file if on linux.
Once this is completed, you must flash the full stock firmware via fastboot. This is MANDATORY.
Blankflash zip: http://cloud.vache-android.com/Moto/albus/blankflash/blankflash.zip
Reserved
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
OneArm said:
please forgive the ignorance, but is this device fully unlockable in the same fashion that Nexus devices are, similar method if i'm reading this correctly? Im very used to unlockable bootloaders on VZW
Click to expand...
Click to collapse
Yeah, I am not sure what is going on this time around with the VZW variant. Since the Droid Z was bootloader locked and the unlocked Z wasn't (but not VZW compatible) I am almost expecting the same here, but I keep being told that the unlocked version of the Z2 will work on Verizon so maybe they just don't care anymore. I mean, the unlocked Nexus 6 and VZW Nexus 6 were pretty much the same phone too, and both were bootloader unlockable.
The only thing that gives me pause from going out now and getting the VZW version vs the unlocked model (whenever its slated to come out) is that Motorola's Bootloader Unlock page doesn't have it listed (yet). Either it can be and they are behind on updating the list, or it can't... at which point the unlocked one will be listed with a (Except VZW Model) like the other phones have. But... if either version works on VZW... what's the point of making one unlockable and the other not? Seems like a waste of time.... of course VZW's past decisions on phones don't make sense in some aspects.
All I know is... I want one of these if they are unlocked. Once the keyboard mod is released I will be back to the nerdy bliss that is a sliding keyboard and making this phone the spiritual successor to the Droid 4.
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
---------- Post added at 06:05 PM ---------- Previous post was at 05:46 PM ----------
After installing TWRP it asked for the encryption password so I put it and it opened normal I went to restart> system, then appeared option to install the application twrp, I slipped it to be installed, then went on reboot> system and stopped on the screen Of bootloader unlocked .. help me: |
m.lucas said:
After flash twrp when rebooting the mobile system, stopped in screen of bootloader unlocked .... how to proceed help me: /
Click to expand...
Click to collapse
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
how should I proceed? My device has no ROM only TWRP installed. :s
m.lucas said:
how should I proceed? My device has no ROM only TWRP installed. :s
Click to expand...
Click to collapse
Start TWRP, and you can transfer zip file from PC by using "adb push"
"adb sideload" may work too.
yunzo said:
I have same issue yesterday and recovered by flashing Dm-verity and Forced Encryption Disabler via TWRP.
I think this issue is caused because SuperSU is NOT flashed correctly. Thus TWRP modifies system-area without disabling dm-verity, and results bootloop.
I have solved bootloop with disabler, but failure of installing SuperSU has not solved yet. Disabler seems no effect for FE...
SuperSU shows error message as below while flashing.
Code:
- Extracting ramdisk
--- Failure, aborting
As far as googleing this message, moto Z users have met same issue.
Ultimate solution is to extract, modify and rewrite boot.img:.
Click to expand...
Click to collapse
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Junior Passos said:
Don't use SuperSU.
Use Magisk-v13.0(54e6a79)
https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Click to expand...
Click to collapse
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
yunzo said:
Thank you for information.
I have just tried Magisk, but failed with error message as below.
Code:
mounting /data/magisk.img to /magisk
! Magisk image mount failed...
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Magisk-v13.0(54e6a79).zip'
It is same for latest version (c4377ed).
Click to expand...
Click to collapse
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
tywinlannister7 said:
Reserved
Click to expand...
Click to collapse
Z2 Play stock ROM needed.
Anyone help to search complete stock Noughat Rom, for the Z2 Play (Indian retail unit model no XT 1710-10), I did not find yet. Please help will be highly appreciated.
@niteshpant kindly edit your post and remove the reserved post from the quote.
Moreover, the links will be added here as soon as the firmware is available.
Junior Passos said:
Latest version don't work.
I use Magisk-v13.0(54e6a79) on my Moto Z2 Play.
Click to expand...
Click to collapse
As I wrote before, I have failed both of 54e6a79 and latest.
Error message on TWRP is same.
Have you met this message but rooted successfully after boot?
Today I tried system-mode SuperSU, and met boot failure which continues to show Motorola/lenovo logo.
It is different from dm-Verity failure (which shows unlock warning).
Stuck in TWRP, Help
I have successfully flashed the TWRP but now it is looping at TWRP and when try to do factory reset, in just seconds it is boot again and shows TWRP main screen again, moreover storage shows about 50000 mb in internal memory, secondly my memory card is not accessible, selection is not working only shows internal memory. As I think at this stage my bootloader(stock) is fine, original stock recovery is replaced by the TWRP 3110 . My factory Android rom is still there in my phone because twrp inernal memory option shows about 50000 mb space captured in internal storage. I have clear delvik and cache but all fails, how I can get the OS by the TWRP. I assume if my old OS has been erased then twrp should have give the "no OS install" massage but this is not happening in my case. Any help...... I am not doing something more due to complete device failure in this stage mainthing is this no factory rom image is available yet, very annoying issue.... regards
WARNING:
You should only proceed if you are familiar with unlocking and rooting android cellphones in general or... if you dare. Instructions assume you have a working computer with adb installed.
1. Getting the cellphone ready
Enable Developer mode
Enable USB Debugging
Enable OEM Unlock
2. Download magisk apk
Downloading Magisk App... | Magisk Manager
The download will automatically start in 5 seconds, please click here to access the download URL directly. If you are confused and want to know how to install the Magisk Manager on your phone you can click here.
magiskmanager.com
3 Install the apk using adb
adb install MagiskManager-v8.0.5.apk
4. Download original firmware (check precise version at About phone > Compilation number)
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
.... YOU MUST BE ABSOLUTELY SURE THIS IS THE SAME VERSION !!!!!
5. Unzip and copy boot.img to /sdcard/Download
adb push boot.img /sdcard/Download
6. Patch the boot.img
Open magisk on the cellphone and click Install (upper right corner)
"Select and patch file"
7. Copy the patched file to your computer
adb pull /sdcard/Download/magisk_patched_XXXXX.img
(replace XXXXX with appropriate characters)
8. Unlock the bootloader
Standard process for all motorola phones. Go to the bootloader:
adb reboot bootloader
Get the unlock data
fastboot oem get_unlock_data
With this information complete the process at:
Unlocking the Bootloader | Motorola Support US
Visit the customer support page to view user guides, FAQs, bluetooth pairing, software downloads, drivers, tutorials and to get repair and contact us information.
motorola-global-portal.custhelp.com
When you have the KEY, unlock with:
fastboot oem unlock <KEY>
9. Flash the unlocked boot.img
fastboot flash boot magisk_patched_XXXXX.img
10. Reboot and you're done
fastboot reboot
Don't forget to disable and uninstall lots of the built-in rubbish
Happy hacking!
Does it work with Moto One fusion + ?
I know i'm a little bit late, but... Is there a way to disable the bootloader unlocked screen?
Skycr0nos said:
I know i'm a little bit late, but... Is there a way to disable the bootloader unlocked screen?
Click to expand...
Click to collapse
You mean disable the message saying "your bootloader is unlocked, don't store data on the phone" ?
I'm not sure, but i don't think it's easy...
Can I root my device motorola one power fusions plus.?
Root work on this device .?
If root is work why YouTube not making videos about this device.?
I want to root my device. Than I need custom recovery.IMG file and magisk stable version.
Can you help me guys
Thanks, it worked for me, XT2073-2 128GB
BruceWawe said:
Does it work with Moto One fusion + ?
Click to expand...
Click to collapse
It does but make sure to download different stock firmware (its called liber go back a few folders in the link OP gave)
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?