Database Info

Root Moto G on Lollipop 5.0.2

Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
Click to expand...
Click to collapse
can i use with stock recovery?
thanks.

vbnoob said:
can i use with stock recovery?
thanks.
Click to expand...
Click to collapse
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta

n1c00_ said:
Hi. It's a fastboot command that you run in bootloader mode. And actually the original script runs an OEM unlock command which bypasses your stock recovery.
So it probably doesn't work with stock recovery.
I'm actually on an unlocked bootloader, added that to the OP
ta
Click to expand...
Click to collapse
My phone is unlocked bootloader with stock recovery.
Thanks.

vbnoob said:
My phone is unlocked bootloader with stock recovery.
Thanks.
Click to expand...
Click to collapse
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...

n1c00_ said:
Here's what I'd do if I were you
1. I would try it as stated in the OP at first
2. ...if that doesn't work: 'mfastboot oem unlock' (as per original script) followed by 'mfastboot boot *.img'
3. If it still doesn't work I would instal philz recovery - see http://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905 - it does work, mind the ripples
...and if it still doesn't work... Oh well...
Click to expand...
Click to collapse
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.

I think I screwed phone. Being a noob I didn't realise fastboot and Bootloader screens are different. I went and use chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions link
in fastboot. After error failed now it ADB doesn't detect my phone.
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>
Any advise to help me? Tried hard method going to bootload still nothing either or at least I think its nothing since this is first attempt I ever tried root my phone. Everytime I plugin in fastboot or even in normal mode the pc does detect it. But it just won't show up in adb.
Decided to try again using leocuervo1983 method for fastboot it stated as fail as well but somehow I got root even though adb still no longer detect my phone.
Edit:
Just found out fastboot doesn't use adb commands or do they? I feel stupid. I Guess there are no issues then even if failed still got root. Fastboot commands works adb doesn't work.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
TAXXXXXXXX fastboot

The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.

pfufle said:
The easiest method would be to flash the latest version of philz recovery, boot into the recovery and then just reboot from the recovery. You will be asked to disable recovery flash and then install su binaries. Just choose yes for both the options and download and super user app you like (I personally use superSU).
PS: I have tested this method and it works.
Click to expand...
Click to collapse
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?

Xicor Yagami said:
Screen flicker issue is there if i install this on stock asia retail 5.0.2 with unlocked bootloader on stock recovery?
Click to expand...
Click to collapse
Yes since the recovery isn't entirely compatible with the new kernel.

pfufle said:
Yes since the recovery isn't entirely compatible with the new kernel.
Click to expand...
Click to collapse
Tried latest TWRP? same results?

Xicor Yagami said:
Tried latest TWRP? same results?
Click to expand...
Click to collapse
yep.

n1c00_ said:
Hello lads!
Surprised to see there are no threads about rooting moto g on lollipop (or maybe I just didn't search the threads enough :silly
A simple search on the internet brings you to http://www.theandroidsoul.com/chainfire-releases-android-5-0-root-moto-g-moto-x-2013-2014-editions/
Unfortunately - for me at least - just following the guide it just didn't work
But... what did work was to just take the *.img from the downloaded folder, paste it into the folder where the fastboot command is (I personally use mfastboot in my android-sdk/platform tools folder) and run the command mfastboot boot *.img (while in bootloader mode obviously)
The blue M logo appeared, rebooted after a few seconds and voilà - I'm rooted!
Not sure if it installs supersu by itself cause I already had it installed from my previous tries but you can download it from the play store.
Thought I'd share, hope this helps, sorry no dev here
Props to Chainfire!!!
cheers
LE: I should probably mention my bootloader is unlocked
Click to expand...
Click to collapse
Thanks a lot! Worked like a charm using mfastboot command.

Works fine
My bootloader was however unlocked...I tried this on CM12....extract the img file from the CF-Auto root File and then flash on the bootloader mode...with mfastboot boot filename.img

The method same as that of kitkat works for lollipop too...you could made some mistake unknowingly somewhere in the middle while following the original procedure
Sent from my Moto G using XDA Free mobile app

is there any method to root moto g?
Any side effects of chainfire method?

leocuervo1983 said:
I am attaching the files that served to me with this I got root in Moto G 2013 5.0.2 Retail Beazil.
I have the stock recovery.
I climb into three parts that weighs 11 megs, Just extract it and put the phone mode fastboot and execute the bat file root-windows.
enjoy it
Then tell me as if I served them.
Click to expand...
Click to collapse
It did'n work for me .... I ran the bat file , and when I pressed a key, it was waiting for the phone and nothing happened.
Edited:
Sorry... I forgot to unlock bootloader first.... worked fine!!! Thanks a lot!!!

[XT1572][EU] STOCK MM 6.0.1 SEPTEMBER patch + TWRP + root + xposed

Wrote down guide how to get STOCK version of Android for XT1572 - Moto X STYLE, and also install TWRP recovery and get root with xposed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Last UPDATE: 25/02/2017
1. GUIDE TO STOCK
@Prazaar 's provided link with STOCK files.
@lAndroXl guide here (Files also for other versions of device).
@dbolivar guide here for RETLA-DS (Brazil).
Stock 6.0.1 EU here, my mirror here (6.0.1 with security patch from September).
Flash scripts - here, or my script here. (for Windows - flashes STOCK files without re-locking bootloader, but also wipes data)
you need adb/fastboot drivers installed (Good ADB installer for PC can be found here);
you need to backup all your data on your phone, guide will erase everything;
reboot your phone into bootloader mode and plug in your usb cable which is connected to your PC. (power off your device then press the POWER and VOLUME DOWN button for 3-4 seconds);
Open a command prompt in the folder where you unpacked the zip file you downloaded before (press SHIFT + RIGHT CLICK on a empty space then "open command prompt here");
Check the functionality of the adb drivers, simply type "fastboot devices" and you will see a list with your connected devices in bootloader mode.
Type every single command in the command prompt window from the list below. (You can ignore OEM LOCK commands if you not wish to lock down bootloader, but just update device to latest version of Android!);
Code:
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
[INDENT](for [B]5.1.1 [/B]there are one more file)
fastboot flash system system.img_sparsechunk.9[/INDENT]
[INDENT](for [B]6.0.1[/B] there are more files)
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11[/INDENT]
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot erase customize (optional: will erase any customizations if ordered through motomaker)
fastboot erase clogo (optional: will erase the custom boot logo if ordered through motomaker)
fastboot oem lock
fastboot reboot
2. UNLOCK BOORLOADER.
Remember, that after unlocking bootloader, all device will be WIPED.
Code:
fastboot oem unlock UNIQUE_KEY
3. FLASH TWRP RECOVERY.
twrp-3.0.2-0-clark.img from here.
Code:
fastboot flash recovery twrp-3.0.2-0-clark.img
Note: After flashing TWRP, boot into custom recovery and make restart to recovery again!
4. INSTALL SUPERSU.
Flash 2.62-3 from TWRP from here. (Later from Play Store upgrade to latest version);
OR
Flash latest SuperSU root ZIP from here.
(before flashing this, TWRP-Advanced-Terminal and enter "echo SYSTEMLESS=true>>/data/.supersu" and then flash ZIP file.)
5. INSTALL XPOSED.
Latest v86 from here. (xposed-v86-sdk23-arm64.zip)
OR
Latest unofficial SYSTEMLESS Xposed from here. (You need 2.76+ SYSTEMLESS root, latest MAGISK Iterface from here and Material Design Xposed Installer to work)
6. To make OTA update.
Remove XPOSED (can be turned off from XPOSED app) + UNROOT (can be done from SUPERSU app) + remove MAGISK (use latest unintaller from thread);
Flash STOCK recovery file from FASTBOOT (fastboot flash recovery recovery.img);
Now you can perform OTA update;
Follow all steps from guide (I do - > TWRP, SYSTEMLESS ROOT, MAGISK, XPOSED).

I have a Brazilian xt1572 with marshmallow via OTA. Do you think this method will work for me? I mean, without flashing the 6.0 firmware first?
Enviado de meu XT1572 usando Tapatalk

But if you make TWRP read only, how can you flash SuperSu and Xposed Framework?
Inviato dal mio XT1572 utilizzando Tapatalk

bbb77 said:
But if you make TWRP read only, how can you flash SuperSu and Xposed Framework?
Inviato dal mio XT1572 utilizzando Tapatalk
Click to expand...
Click to collapse
yea, you right, I forgot. will edit.
After checking if my device boot up, I restarted to twrp recovery, and unchecked read only. Thanks!

danielgava said:
I have a Brazilian xt1572 with marshmallow via OTA. Do you think this method will work for me? I mean, without flashing the 6.0 firmware first?
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Its hard to tell that. After upgrading mine stock 5.1.1 to 6.0 via OTA, I unlocked bootloader, but didnt do device restart and did flash TWRP, after that mine device got bootloop. If you are ready to experiment, you can try, but remember that you will wipe all your data on internal storage. Its strange why now I can boot up my device, I think that restart of device after unlocking bootloader and restart after booting into twrp (read only), could change something.

I'll give it a try later, but for insurance, do you have the link for the Brazilian 6.0 firmware?
Never mind, I've found it: https://mega.nz/#!9ItwmIKb!-73GF5Sk00BpkDeFWIJzcUAp2hOFIZS7ksJ5al0CgiA
Enviado de meu XT1572 usando Tapatalk

danielgava said:
I'll give it a try later, but for insurance, do you have the link for the Brazilian 6.0 firmware?
Never mind, I've found it: https://mega.nz/#!9ItwmIKb!-73GF5Sk00BpkDeFWIJzcUAp2hOFIZS7ksJ5al0CgiA
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Ok, good luck!

What about Indian XT1572?
Can anyone confirm this for India? Or should I risk being the first one to try it on an Indian XT1572 Dual Sim? Although I'll have to wait for a week. My phone is at the service center currently. It apparently had a manufacturing defect in the audio jack.

Any XT1575 owners doing this with success?

radpp16 said:
Any XT1575 owners doing this with success?
Click to expand...
Click to collapse
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.

jason2678 said:
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
Click to expand...
Click to collapse
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Enviado de meu XT1572 usando Tapatalk

danielgava said:
You are absolutely right! When I first tried this method I almost lost my device, since when uncheking "system read only" it some how wiped my baseband, and through rsd I was not been able to flash it back... Had to dig a lot in Google to recover it...
So the good way is: unlock bootloader, install systemless SuperSU via fastboot, boot up, go to bootloader, install TWRP by fastboot, boot in it twice, never uncheking read-only, than you can even install Xposed (I'm using it, it's OK)
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
I will appreciate if you could explain how did you install SuperSu via fastboot?
Thanks!
For "TWRP - read only" I can refer to SuperSu thread:
"If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"

sayV said:
Can anyone confirm this for India? Or should I risk being the first one to try it on an Indian XT1572 Dual Sim? Although I'll have to wait for a week. My phone is at the service center currently. It apparently had a manufacturing defect in the audio jack.
Click to expand...
Click to collapse
all is good.. @freakzapster has already done this aanndd it works fine

BooBzi said:
I will appreciate if you could explain how did you install SuperSu via fastboot?
Thanks!
For "TWRP - read only" I can refer to SuperSu thread:
"If TWRP offers you to keep /system read-only, indeed keep it read-only.
If TWRP tells you SuperSU is not installed, and asks you to install it, do not do it, you will break things!"
Click to expand...
Click to collapse
Sorry I meant via ADB. Here is the link:
http://forum.xda-developers.com/showthread.php?p=64055153
Enviado de meu XT1572 usando Tapatalk

danielgava said:
Sorry I meant via ADB. Here is the link:
http://forum.xda-developers.com/showthread.php?p=64055153
Enviado de meu XT1572 usando Tapatalk
Click to expand...
Click to collapse
Ok, thanks! That make sense now.

I have an Australian xt1752 Moto X style and i tried the trupure MM rom.
my steps were:
unlock
install TWRP
backup the entire phone , all of it to external card and then save the backup to pc just in case
wipe all partitions except for internal and ext card
flash the trupure mm rom already rooted and ready for exposed.
clear cache
boot
problem is i dont have wifi working and if i flash the modem either from the eu 5.1.1 or the us or the indian version my wifi works but then the sim card stops being detected and no calling or sms working.
what i didnt try is flashing one of these modems and then restoring my efs partition from the backup of twrp.
Other then this the phone is much much faster especially for gaming.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
jason2678 said:
XT1575 US here. This worked for me on the second try. I followed the procedure in the OP with the following exceptions. Never unchecked system read only in step 3, and never installed xposed. I used the systemless supersu version referenced in the OP and I'm rooted. Confirmed with a few apps that require root like LMT Pie.
The first time I tried this I fastboot flashed, booted straight into recovery, kept system read only, rebooted to recovery, then rebooted into the ROM before I made any changes. I just wanted to be extra sure everything was ok. When I tried to reboot to recovery I got the "no command" error with the android laying on his back. Rooting, even if it is systemless seems to be necessary before you reboot into the system to make TWRP stick.
Click to expand...
Click to collapse
i had the android laying on his back with no command screen in recovery once aswell, what i did was while at that screen i press power + up for 3 second and release up and then its taken to the default recovery menu

Alanbarnes said:
I have an Australian xt1752 Moto X style and i tried the trupure MM rom.
my steps were:
unlock
install TWRP
backup the entire phone , all of it to external card and then save the backup to pc just in case
wipe all partitions except for internal and ext card
flash the trupure mm rom already rooted and ready for exposed.
clear cache
boot
problem is i dont have wifi working and if i flash the modem either from the eu 5.1.1 or the us or the indian version my wifi works but then the sim card stops being detected and no calling or sms working.
what i didnt try is flashing one of these modems and then restoring my efs partition from the backup of twrp.
Other then this the phone is much much faster especially for gaming.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
i had the android laying on his back with no command screen in recovery once aswell, what i did was while at that screen i press power + up for 3 second and release up and then its taken to the default recovery menu
Click to expand...
Click to collapse
For wifi you can flash TruPureXMM modem!

BooBzi said:
For wifi you can flash TruPureXMM modem!
Click to expand...
Click to collapse
I just tried that and WiFi now works but now I have no network signal. I tried redoing it same thing. I also restored my efs but nope now no phone network

Alanbarnes said:
I just tried that and WiFi now works but now I have no network signal. I tried redoing it same thing. I also restored my efs but nope now no phone network
Click to expand...
Click to collapse
Clean wipe, flash ROM, flash modem?

I did almost the same but I skip " changed to read only, and reboot to recovery again, so it sticks on. Reboot device normally, see that it boots normal. After that, I boot to TWRP again, uncheck read only on mount menu."
After instalation SU and xspoed in twrp reboot system i got loop x2 or x3 but after that system loaded
android starts up
optimalization apps xx/175 :_)

[Mido] Modem for RN4 SD Mido

If you ever flashed a ROM and found that you've not been able to send and receive any kind of wireless activities, chances are your modem file is either corrupted or some problem with it.
It happened to me when i tried to install RR Nougat and found that my modem files are missing and any methods of restoring backup from TWRP ended up unsuccessful. Thank god! i got Fastboot ROM of MIUI 8 Nougat Beta and flashed the modem file which i found inside it.
Download the Modem file from this link.
Instructions:
1. Boot your phone into fastboot mode and connect your phone to PC.
2. Flash the Modem by entering the command
Code:
fastboot flash modem NON-HLOS.bin
3. After flashing, reboot your device.
NOTE: Make sure the modem file is in the same folder as the fastboot binary. If you added the fastboot to your path directory, having modem and fastboot
binary in same folder is optional.
NOTE: Fastboot and ADB codes are case-sensitive, i.e. make sure you type exactly, including the capital letters.
Thankyou!

I have an RN4X(international)
Can I
1) download the latest greatest fastboot ROM from here
http://en.miui.com/a-234.html
2) extract the NON-HLOS.bin (which is >80MB, whereas the bin you linked is just 36MB)
and
3) flash it (as explained by you)

Do i need to unlock bootloader first?

fx3000se said:
I have an RN4X(international)
Can I
1) download the latest greatest fastboot ROM from here
http://en.miui.com/a-234.html
2) extract the NON-HLOS.bin (which is >80MB, whereas the bin you linked is just 36MB)
and
3) flash it (as explained by you)
Click to expand...
Click to collapse
If your board's name is mido then you can. To know the name of your board download AIDA64 from play store and check.

thanks a lot, u saved my phone

Hello,
I'm did everything in this stage but loader is stuck at NON-HLOS.bin and doesnt load it.
I can access fastboot, in fastboot, loading last 2 second. Its says succesfull but it doesnt load. Since loading cant last 2 secon.
Any tips?
Model: 2016102
Windows 10, latest flash loader

crymed said:
Hello,
I'm did everything in this stage but loader is stuck at NON-HLOS.bin and doesnt load it.
I can access fastboot, in fastboot, loading last 2 second. Its says succesfull but it doesnt load. Since loading cant last 2 secon.
Any tips?
Model: 2016102
Windows 10, latest flash loader
Click to expand...
Click to collapse
Bad Cable？

Can i flash this modem with my previous version on my phone is miui 8 8.5.8.0?

Btw, is this file flashable using TWRP? And, what is/are the different between this modem and global? I mean, the one in the global rom?

Shaikat007 said:
Do i need to unlock bootloader first?
Click to expand...
Click to collapse
Obviously. Otherwise your PC's fastboot screen will keep saying that the OEM is locked.

[GUIDE] How to flash a custom recovery and root a Nokia 6 Retail Phone

WARNING: This method currently doesn't work on Nokia 6 TA-1000 with latest Android O Update! Finding workaround.
Workaround found on leaked Android 8.1 Update, with Magisk Systemless Root Method.
ROOT YOUR PHONE MAY VOID YOUR WARRANTY, DO IT AT YOUR OWN RISK
You can download new recovery from this post: https://forum.xda-developers.com/nokia-6/how-to/nokia-6-ta-1000-homebrew-stock-android-t3752006
Changes in new TWRP Recovery 3.2.1-0:
1. Add English Interface.
2. Use Magisk ROOT instead of SuperSU ROOT.
3. You can backup EFS. However you can't backup modem or the procedure will break.
Thanks to @xinkid 's effort, we can finally root Nokia 6 on Android Oreo again.
Procedure for non TA-1000 users:
0. Backup your phone and remove your lock screen password before proceed! If your phone get stuck at "Powered by Android" splash after the procedure, you may need to format userdata.
1. Sideload the PLE-372B ota package in recovery, which you can download from here:
https://forum.xda-developers.com/nokia-6/help/nokia-6-ota-update-ddls-t3721424
Refer this guide's part 2 to downgrade.
https://forum.xda-developers.com/nokia-6/how-to/guide-upgrade-downgrade-nougat-oreo-t3752393
2. Flash the service bootloader and grant service permission
Reboot to bootloader, then flash the service bootloader with following commands. Service bootloader file (D1C-emmc_appsboot.mbn attached in this topic)
Code:
fastboot oem dm-verity [md5_of_your_device_serial_number]
fastboot flash aboot D1C-emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem dm-verity [md5_of_your_device_serial_number]
For example, if your serial number is PLEABCD123456789, and the md5 checksum of your serial number is 5f47b9a8dc1da1873c12945cf806691e, then type this command:
Code:
fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e
fastboot flash aboot D1C-emmc_appsboot.mbn
fastboot reboot-bootloader
fastboot oem dm-verity 5f47b9a8dc1da1873c12945cf806691e
You can google a website to calculate md5 checksum of a string.
3. Reflash newer firmware basis to your phone except aboot
After you grant service permission, Extract the newer one OTA package on your PC, in this case, PLE-558B.
Everything you need are placed at firmware-update folder that you extracted.
Take PLE-558B for example, type these commands (commands need to be changed if newer firmware released):
Code:
fastboot flash sbl1 D1C-0-558B-sbl1.mbn
fastboot flash keymaster D1C-0-558B-keymaster.mbn
fastboot flash devcfg D1C-0-558B-devcfg.mbn
fastboot flash cmnlib64 D1C-0-558B-cmnlib64.mbn
fastboot flash rpm D1C-0-558B-rpm.mbn
fastboot flash tz D1C-0-558B-tz.mbn
fastboot flash cmnlib D1C-0-558B-cmnlib.mbn
fastboot flash modem D1C-0-558B-NON-HLOS.bin
fastboot flash dsp D1C-0-558B-adspso.bin
fastboot flash default_nv D1C-0-558B-NV-default.mbn
fastboot flash persist D1C-0-558B-00WW-persist.img
fastboot flash hwcfg D1C-0-558B-hwcfg.img
fastboot flash mdtp D1C-0-558B-00WW-mdtp.img
fastboot flash systeminfo fver
fastboot flash sec D1C-0-558B-sec.dat
fastboot flash cda PLE-00WW-013-cda.img
You'll also need the boot img in the extracted ota package:
fastboot flash boot boot.img
Then flash the custom recovery:
fastboot flash recovery nokia-6-ta-1000-8_0-twrp3.2.1-7to-recovery-magisk-root-2018.3.15.img
Power off your phone (case sensitive). Disconnect your phone after execute this command:
fastboot oem HALT
4. Connect your phone to a charger. When charging animation appears, press and hold Volume Up and Power until you see "7to.com" logo. Tap the white cog to choose English language, tap Advanced - Magisk Root, and wait for the procedure complete.
========================SEPARATOR====================
This new guide is only based and tested on Nokia 6 TA-1000. Non TA-1000 (e.g. TA-1021) users need to find their own old OTA package to downgrade.
1. Downgrade the bootloader according to this guide: https://forum.xda-developers.com/nokia-6/how-to/guide-upgrade-downgrade-nougat-oreo-t3752393
If you've flashed my homebrew Android O firmware, skip this step.
2. Use old method below to flash the new recovery again. You must use this recovery, otherwise you can't mount and root.
If you've flashed my homebrew Android O firmware, type this command will allow you to flash recovery:
Code:
fastboot-android oem dm-verity (your_serial_number's_md5_checksum)
3. Use old method below to enter recovery. To load English interface, tap the white cog on the top-right corner, then tap "English" and OK button, just wait few seconds.
4. Tap "Advanced" - "Magisk ROOT" and swipe.
5. If you meet recovery loop after rooted, flash the package misc_initial.zip attached below to escape from recovery loop.
That's it. It's not recommended to receive any newer OTA update since it will overwrite bootloader to patched state.
If you're using TA-1000, you can also try to flash Android 8.1 Homebrew Firmware before rooting.
I'm sorry if you found the guide looks confusing.
Following method for Nougat is archived, only for reference.
Yesterday, I got my own Nokia 6 Retail Phone. Since I’ve already rooted Nokia 5, 6 and 8 Prototype, now it’s time to find out how to root retail Nokia 6 without involving risky Qualcomm EDL Mode.
It works on any variant of Nokia 6 in theory, but I only tested it on D1C/TA-1000.
If there’s a custom recovery for Nokia 2/3/5 released, the guide also works on them. But I’ve tested it on a Nokia 8 retail phone, it doesn’t work on it.
To Nokia 7 and 8 Users, You may want to read this topic: https://forum.xda-developers.com/showthread.php?t=3729396
Click to expand...
Click to collapse
First, you need to download OFW of Nokia 6, install OST LA and patch it.
You can download them from here: https://forum.xda-developers.com/no...ia-8-official-firmware-links-updated-t3678487
(Although the link is for Nokia 8, firmware for Nokia 6 is still available)
如果你是中国用户，诺6固件的下载和使用方法请看本文：
https://www.ithome.com/html/android/328333.htm
Click to expand...
Click to collapse
If you own an unlocked prototype device, just skip to step 6.
Click to expand...
Click to collapse
1. Open OST LA from INSTALLATION DIRECTORY DIRECTLY instead of Start Menu.
2. Load your OFW you downloaded with extension name nb0.
3. Power off your phone, then connect it to your PC. This will boot your phone to “Download mode” directly, in fact it’s fastboot mode.
4. Click “Edit Phone Info” on OST LA. This will load a service purposed bootloader. When your phone reboots and re-enters the Download mode, the service purposed bootloader is now loaded.
5. You can close OST LA when it prompts “Boot FTM mode fail”, or just kill it in task manager if it’s not responding.
6. Open a command prompt or PowerShell in OST LA Installation Directory, then execute this command to flash a custom recovery:
Code:
.\fastboot-android flash recovery E:\recovery.img
I assume that you put the custom recovery in drive E and named as recovery.img.
You can also use your own fastboot if you want, but I’ll prefer the one provided along with OST LA.
I used the recovery from here: https://forum.xda-developers.com/no...veryteamwim-recovery-project-nokia-6-t3650499
7. Type this command but do not execute right now:
Code:
.\fastboot-android reboot
8. Now this step is a little tricky. Press and hold [Volume Up] and [Power] on your phone, then execute the command above at the same time. DO NOT RELEASE both keys on your phone until your phone entered the custom recovery.
9. Now your phone has entered a custom recovery. In this example, we’re using TWRP from Chinese 7to forum, only Chinese is available. I believe most of members on XDA can’t read Chinese, so I’ll attach screenshots. Simply tap “Advanced” – “SuperSU ROOT” will root your phone. If you prefer your own root zip update package, tap “Install Zip” then flash your own zip package in your storage, or tap “Advanced” – “ADB Sideload” then use ADB to sideload a zip package.
You can install the Materialized Theme for TWRP to get English interface from https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584 by @z31s1g
Click to expand...
Click to collapse
Currently, DO NOT FLASH Magisk, or your phone will brick as Qualcomm 900E.
You can only use Magisk Root method in latest Android O Update, which I'll cover later.
Click to expand...
Click to collapse
10. After your phone rooted, you can reboot your phone. DO NOT INSTALL ANY OTA UPDATES OR YOUR PHONE WILL GET STUCK AT STOCK RECOVERY, but I’ll recommend you to disable automatic update in settings.
That’s wraps up the whole guide. Please do feedback if there’s something wrong.
Here' the video of how to root a Nokia 6: https://youtu.be/24b-49qTheg
Special thanks:
@blackpanther0582 for Nokia 3/5/6/8 Official Firmware.
@xinkid from Chinese 7to forum for his TWRP.
@hawwin88 for providing info about adding English Interface to recovery.
UPDATE: Uploaded the SuperSU ZIP (verify-xinkid.zip) used in this recovery.

Thank you it worked on nokia6 ta-1000 chinese. I rooted the phone successfully

Finally!
Boy O Boy!
Finally, after a long, long wait, Got my Nokia 6 Rooted! (TA-1000)
Thanks a LOT, Man! :good:

Anyone tried it on any other variant yet?

Hi .i am 1st root my ta1021 with Android 7.1.2 .f**k me
but your method have some problems ...
1. I can't find powershell or anything else in ost la folder.
2.fastboot-android not working....
Now I want complete your method from 6.
6. Before you must install adb and fastboot tools and drivers and use command prompt ,
copy recovery.img to drive c
After ost la changeing phone to edit mod wait 10 second and type this command
Fastboot flash recovery c:\recovery.img
And after flashing completed hold both volume+ and power button and type this command
Fastboot reboot
Don't release buttons and after few seconds you enter Chinese recovery swipe it to right and use screen shots to root your device, after that reboot to system you can find it from screenshot, it go to download mod and then type
Fastboot continue
And enter congratulations, your phone go to normal boot.
Bla bla super su installed....
Thanks, hikari_calyx. For this thread..
Some errors happend when I use rill but after reboot again it is not happening....

same6630 said:
Hi .i am 1st root my ta1021 with Android 7.1.2 .f**k me
but your method have some problems ...
1. I can't find powershell or anything else in ost la folder.
2.fastboot-android not working....
Now I want complete your method from 6.
6. Before you must install adb and fastboot tools and drivers and use command prompt ,
copy recovery.img to drive c
After ost la changeing phone to edit mod wait 10 second and type this command
Fastboot flash recovery c:\recovery.img
And after flashing completed hold both volume+ and power button and type this command
Fastboot reboot
Don't release buttons and after few seconds you enter Chinese recovery swipe it to right and use screen shots to root your device, after that reboot to system you can find it from screenshot, it go to download mod and then type
Fastboot continue
And enter congratulations, your phone go to normal boot.
Bla bla super su installed....
Thanks, hikari_calyx. For this thread..
Some errors happend when I use rill but after reboot again it is not happening....
Click to expand...
Click to collapse
If you're running Windows Vista or Windows 7, you can open a command prompt from installation directory by click right button on the mouse while holding Shift key on the keyboard.
If you're running Windows 8/8.1 or Windows 10, you can open a command prompt or PowerShell from the left corner "File" button. Administrators privilege is optional.
Also, as I mentioned:
You can also use your own fastboot if you want.
Click to expand...
Click to collapse

IDK but you should have change/put the title of this topic as Nokia 6 - TA 1000 (Chinese variant) rather than Retail Phone.
Well, getting root is definitely a temptation but since I'm just a noob and the HMD hasn't release any official firmware/tool yet to recover the phone if thing goes wrong, I guess I'll wait a little bit longer then.

lips_1234 said:
IDK but you should have change/put the title of this topic as Nokia 6 - TA 1000 (Chinese variant) rather than Retail Phone.
Click to expand...
Click to collapse
As I mentioned on the topic, it works on any variant, not only China Variant TA-1000 and Hong Kong Variant TA-1003.
 @same6630 tested on a TA-1021 which is a global variant.
lips_1234 said:
Well, getting root is definitely a temptation but since I'm just a noob and the HMD hasn't release any official firmware/tool yet to recover the phone if thing goes wrong, I guess I'll wait a little bit longer then.
Click to expand...
Click to collapse
HMD released official firmware of Nokia 6 of course, and it's needed to flash a recovery.

Mine
I got some screenshots....

Did someone successfully rooted his Nokia 6 TA-1033?

So just to be clear before I do this to my TA-1000; how do I go about to update it later if I want to update it? For example, my TA-1000 still don't have the 7.1.2 update, and the 8.0 update coming later would be something I want as well.
Do I just update through zip files, or will I simply not be able to update?

Make.Sense said:
So just to be clear before I do this to my TA-1000; how do I go about to update it later if I want to update it? For example, my TA-1000 still don't have the 7.1.2 update, and the 8.0 update coming later would be something I want as well.
Do I just update through zip files, or will I simply not be able to update?
Click to expand...
Click to collapse
After you rooted your phone, you're not able to install any update until you reinstall stock rom.

[THEME][TWRP] TWRP Materialised
U can also install theme for your chinese twrp and you will show english language ...
download theme from this thread
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584

hawwin88 said:
U can also install theme for your chinese twrp and you will show english language ...
download theme from this thread
https://forum.xda-developers.com/android/themes/theme-twrp-materialised-dark-light-play-t2915584
Click to expand...
Click to collapse
Thanks for providing info!

When I try to flash the recovery.img through command I have this:
...etc
FAILED (remote. Partition flashing is not allowed)~
finished. ´
etc...
Im using a TA-1033, unlocked UK version.
Can anyone help me, please.

wolfpower95 said:
When I try to flash the recovery.img through command I have this:
...etc
FAILED (remote. Partition flashing is not allowed)~
finished. ´
etc...
Im using a TA-1033, unlocked UK version.
Can anyone help me, please.
Click to expand...
Click to collapse
maybe u are not in bootloader mode .. try to reconnect ur phone again and tap "edit phone" on OST LA software
or try to type this in command :
"fastboot reboot-bootloader"

hawwin88 said:
maybe u are not in bootloader mode .. try to reconnect ur phone again and tap "edit phone" on OST LA software
or try to type this in command :
"fastboot reboot-bootloader"
Click to expand...
Click to collapse
When I connect my TA-0033 it enters in Download mode, when I press "Edit phone", the device continues in download mode and the OST LA software goes unresponsive.
Im using a TA-0033 with 7.1.2 N

done!!!! thank you my good friend!!!! i've just installed the recovery AND ROOT MY TA-1021 with english theme. only a question. without pc what is the best way to reboot in recovery mode nokia 6? when i'ts time to update to oreo, i've only just click to restore in: setting=>backup and restore?? thanksssssss

canapo92 said:
done!!!! thank you my good friend!!!! i've just installed the recovery AND ROOT MY TA-1021 with english theme. only a question. without pc what is the best way to reboot in recovery mode nokia 6? when i'ts time to update to oreo, i've only just click to restore in: setting=>backup and restore?? thanksssssss
Click to expand...
Click to collapse
I recommend you to install Xposed and GravityBox for Nougat to enable Reboot to Recovery option.

hikari_calyx said:
I recommend you to install Xposed and GravityBox for Nougat to enable Reboot to Recovery option.
Click to expand...
Click to collapse
I just got Nokia 6 TA 1021 android 7.1.1, Build is 00WW_3_320. Can your method also work for it?

Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)

Links to Firmware & OTA & TWRP & Magisk & Bootloader - Z3 PLAY BECKHAM (All Variants)
Firmwares
the latest firmware as of time of writing is February's 2020 OTA (BECKHAM_RETAIL_9.0_PPWS29.131-27-1-18_subsidy-DEFAULT_regulatory-DEFAULT_CFC) = https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
previous OTAs RETAIL variant can be found here = https://mirrors.lolinet.com/firmware/moto/beckham/official/RETAIL/
future OTAs possibly here = https://androidfilehost.com/?w=search&s=beckham
other variants = https://mirrors.lolinet.com/firmware/moto/beckham/official/
Unlock Bootloader
first you need to install Motorola Drivers = https://support.motorola.com/us/en/solution/MS88481
- ATTENTION - use the most up-to-date ADB Drivers otherwise will brick if older version is used; instead of downloading ADB elsewhere which is often old version, get it directly from GOOGLE, here = https://dl.google.com/android/repository/platform-tools-latest-windows.zip
now you can proceed to unlock bootloader = https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
TWRP
get the official TWRP here = https://dl.twrp.me/beckham/
- ATTENTION - if you just want root access, then there's no need to install TWRP, just boot from the .img once using the latest version
use TWRP to make a backup of EFS partition before installing anything, store the backup files outside of the device
if you want custom ROMs or GSI, then you will need to install TWRP installer .zip into the recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the latest .zip version in the recovery partition. Unfortunately the only official installable version of TWRP that exists is bugged, and the TWRP developers haven't fixed it yet, go talk to them ask for some love, be respectful = https://github.com/TeamWin/android_device_motorola_beckham/issues
Magisk
install Magisk using the new&correct method AKA "Boot Image Patching Method" to be able to install OTA later = https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
when OTA arrives, you may manually install it whilst retaining Magisk by carefully following these instructions = https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
- ATTENTION - you won't be able to install stock OTAs if you use older method or if system partition is modified, be really careful to not alter the hash of the partitions

Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45

@heynando, what is the difference between "retail" and "retus"? Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?

ritchea said:
@heynando, what is the difference between "retail" and "retus"?
Click to expand...
Click to collapse
RETUS is short for Retail + US.
The difference between RETUS and RETAIL is, I imagine, cannot confirm, the same RETAIL firmware with some US regional modifications such as bloatware or CSC thing
you can check which model is yours in SETTINGS > SYSTEM > ABOUT PHONE > SOFTWARE CHANNEL. Or in the bootloader by running the command
Code:
fastboot getvar product
you can find the entire list of product codes here = https://mirrors.lolinet.com/firmware/moto/readme-en.html#listone
XT1929-4(Canada, SS, 4+32GB) XT1929-3(NA/Sprint, SS, 4+32GB)
XT1929-4(NA/AMZ/BWACA/RETCA/RETUS/USC, SS, 4+64GB)
XT1929-5(BRAZIL/RETBR/TIMBR/TEFBR, DS, 4+64GB / 6+128GB)
XT1929-6(LATAM/AMXLA/NIIPE/ATTMX//TEFCL/TEFPE/RETLA/RETAR/RETMX/RETCL/AMXMX, DS, 4+64GB)
XT1929-6(LATAM/RETLA/TEFCO/TIGCO, DS, 6+128GB)
XT1929-8(EMEA_APAC/RETEU/DTEU, DS, 4+32GB / 4+64GB)
ritchea said:
Also, does anyone know the numbering system? All the uploads on lolinet.com for Pie have 131 as the first three numbers, but the few posted about here have 183. Maybe 183 is an ota number?
Click to expand...
Click to collapse
I believe that's the internal version of the software. If the number changes that emphasizes there has been software changes and/or tweaks in the system and/or firmware. If the number doesn't change, then it's just a regular security patch with no further modifications in system and/or firmware.

Thanks for that info. Yeah, I know mine has the retus software channel. I just couldn't find or figure out if Retail was actually one word or if it was a combo of ret+ail. That version has a LOT of software posted.

I flashed retail on an EU model. And after it the software channel say Reteu just like the original. Also the model number is as it should be. In my opinion you can flash retail firmware on us and EU models.

confirmed that this firmware is working on XT1929-4
these are the steps I took:
downloads and setup
install moto drivers (in windows, not needed for linux)
install android tools (adb and fastboot)
downloaded official TWRP
downlaoded and extracted the firmware
backup of partitions (including efs)
Code:
adb reboot bootloader
fastboot boot twrp_recovery.img
backed up lots of partitions
rebooted system
copied the TWRP backup files to my pc for safe keeping
set the fastboot slot (i did this because many of teh fastboot commands below were failing)
Code:
adb reboot bootloader
fastboot --set-active=a
rebooted back into bootloader
installed the firmware
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot reboot
installed magisk the new good way
did the initial device setup
installed magisk manager
copied the boot.img from the extracted firmware above to the phone.
followed these steps for boot img patching and install of magisk https://topjohnwu.github.io/Magisk/install.html#boot-image-patching

sirkuttin,
Thanks for the detail how to. That worked perfectly for me, and my moto z3 play, same model as yours. I could not get the ota or even lenovo smart assistant to work on my phone. It basically had it locked up, stuck on the boot logo. I'm assuming its the old way of install magisk that caused that. This got me on the latest firmware release, and then installed magisk the new way. Lenovo smart assistant was useful in downloading the firmware.
Thanks.

Hi I tried the new magisk install way. I'm on XT1929-4_BECKHAM_RETUS_9.0_PPW29.183-29-1, copy boot.img and patched it to magisk_patched.img. Then after fastboot flash boot /path/to/magisk_patched.img and a reboot, i'm not stuck on the motorola powered by android screen. Verity mode is set to disabled.
I tried holding down the power button to simulate a battery pull but no luck, the screen just stays on. Can anybody give me any advise? I think now I have to just wait till the device is out of juice. Never experience this before.
---------- Post added at 02:16 PM ---------- Previous post was at 01:31 PM ----------
So the battery pull is "Power + Vol Down". I was able to flash the PPW29.183-29-1 firmware and get it going again. I noticed it tried to upgrade me to PPW29.183-29-1-2 so I must have been on newer firmware. I flashed the magisk_patched and am rooted now.

It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).

ch3mn3y said:
It seems there is TWRP 3.3.1-1 with an Installer. Does it mean it can be flashed to recovery partition? Tried booting it, but got stuck on TWRP logo (3.3.1-0 boots fine).
Click to expand...
Click to collapse
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.

heynando said:
I haven't tested it myself, though you're correct, the installer .zip can be installed on recovery partition. To install the .zip, boot using a .img for example the 3.3.1-0, then use it to install the .zip in the recovery partition.
PS only do it if you have a reason to, I'm not sure if the firmware OTA checks the hashing of the recovery partition so altering it could potentially prevent you from installing OTAs of the official ROM.
Click to expand...
Click to collapse
It, unfortunately, does... However I csnnot update (continous update unsuccesful) :f Have to check if Xposed module is not a reason.
And You probably could use Installer to flash stock recovery? If not TWTP itself however I've never checked if one for Play has access to recovery partiotion to flash images. It should gave if it can be done using the installer...
Sent from my Moto Z3 Play using Tapatalk

ch3mn3y said:
However I csnnot update (continous update unsuccesful)
Click to expand...
Click to collapse
Me too and it drove me nuts, I did patch the /boot partition with the original file, but the OTA app still failed to install, even after reboot. And there's no useful data in the logcat to debug the app. So I gave up and had to use Titanium to freeze the OTA app otherwise it would keep trying to download and install infinitely.
ch3mn3y said:
:f Have to check if Xposed module is not a reason.
Click to expand...
Click to collapse
It's probably not because I don't use it and the OTA method didn't work me either
ch3mn3y said:
And You probably could use Installer to flash stock recovery?
Click to expand...
Click to collapse
Yes you're right, I agree there..

heynando said:
Yes you're right, I agree there..
Click to expand...
Click to collapse
Just checked the inside of the installer zip file and it won't work. Still once every 3 months it wouldn't be a problem to connect device to PC and flash recovery.img with fastboot.
Is there a list with a commands and order how to flash Z3 Play images of official firmware? I want July patches and have some problems, so clean reflash is what I need.
Additional question is if I have to use "-u" when flashing second and other system images? Remember I had to do it with my X Play coz of unlocked bootloader and here I have one in the same state as well. If yes than could someone tell me where to put it, coz I'm not sure...

tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?

tb110188 said:
Another mirror for the latest ROM with May 1st patches, uploaded by me you can find here:
https://forum.xda-developers.com/showpost.php?p=79122632&postcount=45
Click to expand...
Click to collapse
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?

Ramble2k said:
Hi. How are you doing. My software channel says: US Retail. and my build number is 183-19-1-2. What would be the firmware?
Click to expand...
Click to collapse
This one, make sure to get the latest. https://mirrors.lolinet.com/firmware/moto/beckham/official/RETUS/

Hi, I'm trying to unlock my Moto Z3 Play bootloader, but I don't get the code on CMD, but only a few numbers ... The version of my device is PPW29.131-27-1-11, channel RETBR software.
Someone went through this, can you tell how to reverse this situation?

I couldn't get the bootloader unlocked for xt1929-4. I tried different computers, Linux and win. Have latest adb and fastboot. When fastboot OEM get_unlock_data is given, I says counttas slot not found etc., can someone help?

It may seem obvious, but you
checked OEM unlocking and USB Debugging?