requesting help to ROOT Moto Z Play - Moto Z Play Questions & Answers

Good morning (or afternoon, depending on your time zones).
I just bought the MOTO Z PLAY, and I thought rooting it would be easy. So far it's bee quite challenging.
I have the bootloader unlocked, I get this message every time I start my phone, the bootloader can't be trusted so it's going to restart in 5 seconds.
I've been using the command prompts to launch the flash.img. but every single time, no matter where I get the IMG From it always says this;
C:\Users\Laptop\Desktop\moto\flashing>fastboot devices
ZY223M64KT fastboot
C:\Users\Laptop\Desktop\moto\flashing>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (16198 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.312s]
finished. total time: 0.665s
You guys here are the best at what you do and you make things pretty simple. I'm requesting your help to make my phone as fun as it can be. Thanks in advance for your help!

It looks like you did everything right. Just choose recovery on the fastboot menu and you should boot to TWRP.

thanks turkobr
when I do that, it goes to the NO COMMAND screen
{
"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"
}
then after about 30 seconds, the phone boots normally.
I don't see any TWRP screens

nina.gardener said:
thanks turkobr
when I do that, it goes to the NO COMMAND screen
then after about 30 seconds, the phone boots normally.
I don't see any TWRP screens
Click to expand...
Click to collapse
Looks like you've flashed the wrong TWRP
Sent from my XT1635-02 using XDA-Developers Legacy app

nina.gardener said:
thanks turkobr
when I do that, it goes to the NO COMMAND screen
then after about 30 seconds, the phone boots normally.
I don't see any TWRP screens
Click to expand...
Click to collapse
You could try to use this command.
fastboot boot recovery.img
This way it dont has to be written, maybe then it can get through the verification.
Try out this recovery:
https://forum.xda-developers.com/mo...recovery-unofficial-twrp-moto-z-play-t3495629

alright guys...THIS is what I'm talking about. This is why I recommend this website to people.
twrp-3.0.2-0-addison.img worked with fastboot boot recovery.img
I'm doing the backup (as everyone recommends).
G4liant thanks for the command, and for the link.
thank you guys so much!!

Please excuse the double post/bump.
I got that TEAM WIN menu to show up
I installed a SUperuser from a ZIP file
"UPDATE-SuperSU-v2.46.zip"
it had these files on it;
arm
arm64
armv7
common
MEDA-INF
mips
mips64
x64
x84
it seemed to install within minutes, and I thought my phone was fully rooted.
I went into ROOT EXPLORER and tried to go into (phone storage);DATA/DATA to transfer some content from my previous phone to this new phone. But, get a message the phone isn't rooted.
I feel like an idiot asking this, but what's the next step in rooting the phone after getting TEAMWIN's recovery up and running.
Thanks for your time.

nina.gardener said:
Please excuse the double post/bump.
I got that TEAM WIN menu to show up
I installed a SUperuser from a ZIP file
"UPDATE-SuperSU-v2.46.zip"
it had these files on it;
arm
arm64
armv7
common
MEDA-INF
mips
mips64
x64
x84
it seemed to install within minutes, and I thought my phone was fully rooted.
I went into ROOT EXPLORER and tried to go into (phone storage);DATA/DATA to transfer some content from my previous phone to this new phone. But, get a message the phone isn't rooted.
I feel like an idiot asking this, but what's the next step in rooting the phone after getting TEAMWIN's recovery up and running.
Thanks for your time.
Click to expand...
Click to collapse
I don't know where you've downloaded the version of TWRP from but it seems it's an older version.
Here's the link to the thread where you'll find the Chinese version of TWRP that has built in SuperSU.
Just read the section on how to install recovery.
I would also highly recommend you download your specific firmware package for your phone, things can go wrong which could leave you with a soft bricked device.
https://forum.xda-developers.com/showthread.php?p=70337221
Sent from my XT1635-02 using XDA-Developers Legacy app

flashallthetime
the link you provided did exactly what I was hoping. the IMG loaded just fine ( had to change the language), but I found the SU installer, and it installed without issue. I've gained access to the ROOT\Data\Data folder, so now I can transfer my game data over from my other phone (Xperia Z1).
Thanks a bunch. I'd be frustrating myself with links and tutorials without your kindness.
Issue resolved. Thread may close.

Related

[Q] Is my Gnex motherboard faulty?

Hi guys,
I can't flash any ROM/Kernel/whatever file via Bootloader/ODIN & Recovery. Worst still I can't access Recovery now.
My Nexus can goto Bootloader or ODIN mode but once i started to push files to it, it will just freeze. Please refer below for photos:
{
"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"
}
BEFORE
AFTER
My Gnex was on the latest Paranoid ROM and Franco kernel.
Timeline:
1. It just went into bootloop when I am just browsing the internet.
2. Went to Recovery to clear cache. (that's my mistake, should have waited longer for my device to boot :crying
3. Still bootloop.
4. Went to recovery to flash stock kernel as I suspect it's kernel fault.
5. Kernel flash failed as it the operation was aborted and restarted. Bootloop again.
6. Done battery pull and went to Recovery to Restore my backup Nandroid.
7. Flashing halfway and it frooze.
8. Can't access Recovery anymore.
9. Tried to restore stock rom using ODIN. Failed at NandWrite as the screen froze as the above image.
10. Tried WugfFresh to restore back to stock rom and failed again as the screen froze.
So guys, can i conclude that my motherboard is the culprit here?
Thanks in advance.
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
ual4720 said:
Are you able to get into the bootloader? Have you tried manual fastboot flash of factory images?
Click to expand...
Click to collapse
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
d3vils said:
Hi,
Yes, I am able to get to bootloader.. the problem is when i start to do fastboot flash the factory images (using WugFresh).. the screen will start to freeze with double image as per my 1st post...
:crying:
Click to expand...
Click to collapse
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
cmaag said:
Sound like there is a possibility of corrupt nand partition .... though that is usually unlikely unless you are an extreme flashaholic ... but still possible
but the guy above is suggesting use the fastboot commands manually rather than using the toolkit as it sometimes makes a difference
As in manually flash the recovery in the bootloader then see if you can get into recovery, but there are many avenues that you can take to see where you can get with this. There are many places that explain how to do this step by step on the web.
Also you should always try switching usb ports and usb cables as sometimes it will cause issues
I know i used the same usb port with the same usb cable to flash my n7 and gnex multiple time then one day it just stopped working switched the port and cable then it started working again.
But other than that I don't know much about is a possible JTAG but I really doubt that will help at all since the device does does get into bootloader and odin just freezes....
Click to expand...
Click to collapse
corrupt nand partition... that's an interesting theory... will explore on the solutions on the manual fastboot commands...
thanks!!

[FIXED] adb sideload "timed out waiting for package"

Hi guys, i'm new in this forum, so please pardon me if i did something wrong.
i really need a help now, my asus zenfone 2 (ZE551ML) got bricked Yesterday.
this is the timeline why my zenfone 2 got bircked:
1. I rooted my phone without cwm or anything else on around 2 weeks ago
2. Yesterday, i recieved the firmware update message (auto download) and i accidentaly clicked on update now without unrooting first.
3. My phone stuck on the logo screen, loading forever (softbrick?)
4. i've tried to factory reset and wipe all the system cache via recovery mode, but it didn't wok.
5. i looked at some forum and youtube said that i can flash rom my device to unbrick my device with 2 ways : via adb and microsd.
6. using adb sound promising, so i learnt how to flash rom via adb and i downloaded the latest firmware on the official website.
7. i tried to flash rom via adb: i've put the firmware zip on adb folder and open windows command in that folder, i connected my zenfone 2 with usb and start to "apply update from adb" and type "adb sideload xxxx.zip".
8. several times later i got message: "timed out waiting for package, installation aborted".
9. i repeated step 7 and 8 for almost 5 times and the results are same
Can someone help me? I'm really frustated now cause i can't using my phone or maybe share the reference about flash rom with microsd, because i've tried it but i don't really understand how to do it
Thx. in advance for all of you
nb: i've tried to search in this forum, but i didn't find correct answer for me
{
"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"
}
FIXED!!!
FINALLY I FOUND HOW TO FIX IT IN THIS SITE http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=39487 THE PROBLEM IS PERSIST WITH MINE AND FINALLY I DIDN'T NEED TO STPCK RECOVERY! THX FOR THE REPLIES GUYS
since you know how to go into recovery mode so i'll skip that part,
use this adb tool instead https://www.androidfilehost.com/?fid=95784891001607611
If you have an external sdcard take it out and copy the firmware you want to side load and copy it to the external sdcard. Now name it "MOFD_SDUPDATE.zip" and reboot to fastboot and choose recovery. It should automatically flash the firmware. Move it to a folder when you are done or it will install automatically every time you reboot to recovery.
bar4 said:
since you know how to go into recovery mode so i'll skip that part,
use this adb tool instead https://www.androidfilehost.com/?fid=95784891001607611
Click to expand...
Click to collapse
Thx for your reply! My device has been fixed already
mremghz said:
If you have an external sdcard take it out and copy the firmware you want to side load and copy it to the external sdcard. Now name it "MOFD_SDUPDATE.zip" and reboot to fastboot and choose recovery. It should automatically flash the firmware. Move it to a folder when you are done or it will install automatically every time you reboot to recovery.
Click to expand...
Click to collapse
Thx for your reply! My device has been fixed already
great thanks

htc m8 wont flash CRW!

Hello guys , i am trying to flash cwm recovery in my htc m8 international device.I don't know why but it wont flash.i have tried many versions of trwp and cwm but still nothing.i have tried changing cables, usb ports and also tried flashing from internal storage and sd card but it says "failed to map".I don't know what to do. Also ,My bootloader is unlocked an i am not rooted.Can you guys please help me?I am also attaching a photo of the moment it stucks when i try to flash the recovery image
{
"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"
}
192latform-tools GB$ ./adb reboot bootloader
192latform-tools GB$ ./fastboot flash recovery crw.img
target reported max download size of 1826414592 bytes
sending 'recovery' (12846 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 405.903s
First of all, I would avoid CWM. Reason being, CWM never official supported this device. There are some unofficial CWM versions compiled for the M8, but they are all very old, and by definition will not be compatible with a great many firmware versions that came after.
Also, we need more info about your device. Do fastboot getvar all, and post the results (delete IMEI and serial number).
What versions of TWRP exactly did you try? Give us actual version numbers, as saying something like "many versions" doesn't give us the required specific information.
Hi,thank you for the reply.I flashed from a window pc and it flashed perfectly so phone is ok now.i was trying to flash it from my mac yesterday and it didnt work.I executed excatly the same steps in my pc as i did in my mac and the procedure went on.In mac whenever i typed " ./fastboot flash recovery crwp.img " it got stuck at " sending<> " .
In window i tryed flashing both cwm and trwp and it worked with both ,so i think its my mac fault.
Anyways thank you for the help and the reply.
giulianoballshi said:
Hi,thank you for the reply.I flashed from a window pc and it flashed perfectly so phone is ok now.i was trying to flash it from my mac yesterday and it didnt work.I executed excatly the same steps in my pc as i did in my mac and the procedure went on.In mac whenever i typed " ./fastboot flash recovery crwp.img " it got stuck at " sending<> " .
In window i tryed flashing both cwm and trwp and it worked with both ,so i think its my mac fault.
Anyways thank you for the help and the reply.
Click to expand...
Click to collapse
Interesting, although I personally am only experienced with using a PC for phone mods; fastboot and adb should be agnostic (not matter) as to PC, Mac, or Linux. As long as you have the proper Google adb/fastboot package/drivers installed.
What version TWRP to use is still pretty dependent on the phone's firmware version, so if you need help identifying that, post your fastboot getvar all results, as indicated in my last reply. Flashing TWRP is one thing, but if you have a mismatched TWRP version, you may have trouble flashing ROMs, root, etc.

Friend's Pixel stuck in bootloop, flash unsuccessful

My friend's unlocked Pixel got stuck in a bootloop about a week ago, and we're unable to get into Recovery Mode so we've been trying to flash it instead. I've used minimal adb and fastboot v1.4.3 and v1.3, and the latest and next to latest Marlin image files.. Currently on 1.3 and the latest image file, and the process gets stuck while trying to erase 'cache.'
screenshot of flash-all.bat:
{
"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"
}
Any help would be very appreciated. (I'm a total noob with these terms and tools btw. My realm is computers, not phones. :/ )
i think the problem is that you're using minimal adb and fastboot. v1.4.3 was updated in february 2018. the official platform tools from google have gone through several updates since then, the most recent being last month. i suggest trying again with the latest android platform tools and the latest marlin image.
the latest android platform tools can be downloaded from here.
altwu said:
i think the problem is that you're using minimal adb and fastboot. v1.4.3 was updated in february 2018. the official platform tools from google have gone through several updates since then, the most recent being last month. i suggest trying again with the latest android platform tools and the latest marlin image.
Click to expand...
Click to collapse
I already had the official tools but I never thought to use that.. So I tried that and we got somewhere. It looks like it was successful on this end, but the phone is still in a bootloop. Does that mean that this thing is a paperweight?
i wouldn't give up yet. it does look like the flash was successful and user data got wiped. did you see any error messages to indicate that something went wrong with the flash? you probably got a bunch of warnings about certain images not being available. those are normal.
if the flash went through with no errors, then the only other thing i can think of to try is to flash both slots. here's how:
get the latest platform tools from here.
flash the factory image like normal, with flash-all.bat.
wait for the phone to reboot and finish the install.
reboot to the bootloader.
look for the line that says "Boot-slot". it will be either a or b.
change to the other slot with this command.
Code:
fastboot --set-active=a or fastboot --set-active=b
reboot the bootloader
Code:
fastboot reboot-bootloader
run flash-all.bat to flash the factory image.
same exact thing as last time.. So I run flash-all.bat and it finishes in 134 seconds, then immediately after, the phone reboots. But it gets to the google splash image and then it'll power off again, and reboot again. It only stays on the google image for a few seconds. Nothing else ever happens.
So both slots are now flashed and the problem still exists.
Dallas Roberts said:
same exact thing as last time.. So I run flash-all.bat and it finishes in 134 seconds, then immediately after, the phone reboots. But it gets to the google splash image and then it'll power off again, and reboot again. It only stays on the google image for a few seconds. Nothing else ever happens.
So both slots are now flashed and the problem still exists.
Click to expand...
Click to collapse
Try factory reset in recovery if you haven't already..........ya never know.
crackerjack1957 said:
Try factory reset in recovery if you haven't already..........ya never know.
Click to expand...
Click to collapse
I thought I put this in the original post but we can't access recovery mode, it just reboots like normal.
Dallas Roberts said:
I thought I put this in the original post but we can't access recovery mode, it just reboots like normal.
Click to expand...
Click to collapse
I seen that but if flash was successful I thought maybe you would have recovery..
crackerjack1957 said:
I seen that but if flash was successful I thought maybe you would have recovery..
Click to expand...
Click to collapse
I tried it again after your message just in case it might be working again, and I got nothing. So maybe the problem is hardware-related?
Dallas Roberts said:
I tried it again after your message just in case it might be working again, and I got nothing. So maybe the problem is hardware-related?
Click to expand...
Click to collapse
Probably hardware
Just to make sure you know how to get to recovery & navigate after no command image
https://www.youtube.com/watch?v=P1RGEle3qN0

I have no bootloader that I'm aware of..

My phone: Asus Zenfone 3 Deluxe NON PRO with the snapdragon 820 2.15ghz CPU..
When I try to enter fastboot mode my phone just goes nowhere and sits there. If I hard reset the phone it turns on again.. Calls and works but take one picture with camera and it shuts off.. gets the picture oddly.
Ive installed ADB on my PC and I'm about to start seeing if I can talk to the phone in fastboot even though the phone itself shows nothing at all. This happened during a failed upgrade and has NOT been able to upgrade since. I'm on 6.0 still.. failed 7.0
My question: Is there a certain way I should attempt to flash the files using ADB? I do have the RAW files from Asus support..
I'm going to post a couple pictures and a short video if needed to make this easier to understand for anyone reading this, I'm just going to try some simple commands first in ADB and see if the phone responds first. I have a feeling this could make everything much much easier if it does.
Try to enter fastboot or flash from here?
I have no recovery that I know of my phone goes totally dead when its in recovery mode and doesn't seem to respond to anything at all BUT.. When I plug in a cable it makes the connecting sound over the PC.. I'm about to try a few different scenarios of trying to enter fastboot other than manually with the side buttons but if that doesn't work what are my odds of repairing my file system from this state? I can get into MOST of the files in the LS.. but not all I do not have root access but I can get into pretty much everything else just FYI. If anyone has any questions or advice feel free to chime in at anytime.
I got into fastboot using command.
I assume its pretty straight forward from here I'll just post the steps I'm about to take or links to what guide or guides I follow just in case anyone else suffers from this in the future.
I used the commands in the following order :
adb devices (to start the server)
adb shell (to get connected to the phone)
reboot bootloader (to reboot into fastboot)
When the phone rebooted it looked stuck on the Asus logo but once it settled I tried the command :
fastboot devices (BAM it showed up instantly)
Now I have downloaded some RAW STOCK and TWRP files I'm I'm planning to restore my factory 6.0 ROM.
If this is successful then I plan to make a backup... and then sleep before I play more lol
{
"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"
}
BWPHonda said:
I assume its pretty straight forward from here I'll just post the steps I'm about to take or links to what guide or guides I follow just in case anyone else suffers from this in the future.
I used the commands in the following order :
adb devices (to start the server)
adb shell (to get connected to the phone)
reboot bootloader (to reboot into fastboot)
When the phone rebooted it looked stuck on the Asus logo but once it settled I tried the command :
fastboot devices (BAM it showed up instantly)
Now I have downloaded some RAW STOCK and TWRP files I'm I'm planning to restore my factory 6.0 ROM.
If this is successful then I plan to make a backup... and then sleep before I play more lol
Click to expand...
Click to collapse
Were you able to repair your CP? im still looking for ways to back up my data before proceeding

Categories

Resources