Database Users

[Q] nexus 7 wont update, fastboot fails, recovery no go

When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?

ive tried fastboot oem unlock using nexus toolkit and direct through the command line with same results

is this guide any good?
http://forums.androidcentral.com/ne...1477-guide-nexus-7-factory-image-restore.html

Otherwise you have this GUIDE
Phone:I9100P
Kernel:Dorimanx
ROM:4.2.1 Vanilla RootBox
Tablet:Nexus 7
Kernel:M-Kernel
ROM:4.2.1 AOKP PUB
MOD:JusTunBean

welly_59 said:
When i had my nexus 7 i updated to 4.2.1 and then did a factory reset. Upon booting my nexus was back on android 4.1.2(i thought this shouldnt have happened?)
Now the OTA update wont install - i get the dead android with an exclamation mark.
I have downloaded the nexus 7 toolkit to try and unlock the bootloader and flash stock 4.2.1 but i get an error when trying to unlock - FAILED (command write failled (unknown error))
anyone able offer some help please?
Click to expand...
Click to collapse
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one

liamwli said:
It is possible (albeit very slightly) that the file didn't flash correctly, but did corrupt the bootloader just enough to stop it being unlocked/booting into recovery.
If you can't issue the 'fastboot oem unlock' command then it could be for 2 reasons:
1. It is already unlocked (try typing 'fastboot oem lock' and see if it re-locks')
2. The bootloader is slightly corrupt.
Hopefully it is the first one
Click to expand...
Click to collapse
i managed to get it working after erasing everything as in the guide above. I had to keep unplugging the device and trying again though and after a few attempts it worked

when encountering this error i simply cycled through the options (using volume) and said boot into bootloader, familiar windows device dis/connect and then tried the fastboot flash boot boot.img cmd again, worked a treat, currently flashing the system part.
hope this helps!

[Tutorial] How to root Motorola XT925 with 4.4.2 update

hi all motorola users
1st you must have Unlocked your motorola XT925
see this thread : http://forum.xda-developers.com/showthread.php?t=2797116
2nd you need custom recovery for example CWM for kitkat bootloader
you can download the stable kitkat cwm for XT925
from there : http://www.mediafire.com/download/uxyrv1b17ctu5rv/CWM6049-RAZR-HD_M-KITKAT.img
3rd you need root package
download from there : http://www.mediafire.com/download/v8sptt6oy9m1xd6/UPDATE-SuperSU-v2.16.zip
let's start :laugh:
put everything in adb folder and connected you XT925
adb wait-for-device
adb reboot bootloader
fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
----------
disconnected you phone power off and go to bootloader again and then go CWM recovery and install the UPDATE-SuperSU-v2.16.zip
you can use the sideload options
good luck

Has anyone tried/verified this yet or should I be the first?

matt121188 said:
Has anyone tried/verified this yet or should I be the first?
Click to expand...
Click to collapse
back when i flashed kk, it worked to get root. no other root exploits have been found unfortunately.. this is the normal and easiest way to get root just need an unlocked bootloader and flash chainfire's super su through a custom recovery.

A little help please
s27moto said:
hi all motorola users
1st you must have Unlocked your motorola XT925
see this thread : http://forum.xda-developers.com/showthread.php?t=2797116
2nd you need custom recovery for example CWM for kitkat bootloader
you can download the stable kitkat cwm for XT925
from there : http://www.mediafire.com/download/uxyrv1b17ctu5rv/CWM6049-RAZR-HD_M-KITKAT.img
3rd you need root package
download from there : http://www.mediafire.com/download/v8sptt6oy9m1xd6/UPDATE-SuperSU-v2.16.zip
let's start :laugh:
put everything in adb folder and connected you XT925
adb wait-for-device
adb reboot bootloader
fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
----------
disconnected you phone power off and go to bootloader again and then go CWM recovery and install the UPDATE-SuperSU-v2.16.zip
you can use the sideload options
good luck
Click to expand...
Click to collapse
I apologize for my stupidity.
But, is there any chance for more advance step by step tutorial on this topic.
I have a filing that i'm going to miss something. My bootloader is unlocked now im trying to root my phone and install custom recovery on it. Currently on 4.4.2 kitkat motorola tx925.

hassoman_64 said:
I apologize for my stupidity.
But, is there any chance for more advance step by step tutorial on this topic.
I have a filing that i'm going to miss something. My bootloader is unlocked now im trying to root my phone and install custom recovery on it. Currently on 4.4.2 kitkat motorola tx925.
Click to expand...
Click to collapse
it's so simple
1- unlocked bootloade
2- root you device
3-install recovery
4-install custom roms
5-install google apps

Confusing with first step...
s27moto said:
it's so simple
1- unlocked bootloade
2- root you device
3-install recovery
4-install custom roms
5-install google apps
Click to expand...
Click to collapse
Hi s27moto,
Thanks for your very clear guide. Btw, In 1 step (unlock bootloader) could you tell me more about this step:
0. My phone is RAZR HD Kitkat offical update, no root, bootloader locked.
1. Can I unlock it by using fastboot command with motopolycase that provided in following link in step 1 (4.4.2 kitkat) ?
2. I tried to unlock my phone using Motorolar website but It's say that my phone is not qualify. What can I do ?
Thanks you.

Quang Hung said:
Hi s27moto,
Thanks for your very clear guide. Btw, In 1 step (unlock bootloader) could you tell me more about this step:
0. My phone is RAZR HD Kitkat offical update, no root, bootloader locked.
1. Can I unlock it by using fastboot command with motopolycase that provided in following link in step 1 (4.4.2 kitkat) ?
2. I tried to unlock my phone using Motorolar website but It's say that my phone is not qualify. What can I do ?
Thanks you.
Click to expand...
Click to collapse
If you have a 926 and are on the latest FW, you can't unlock. If you have a 925, you should be able to unlock via Moto.
Sent from my HTC6525LVW using Tapatalk

xt926 4.4.2 unlocked........
how do I get my root back after 4.4.2 update. all instruction lead to needing custom rom and or rooted. I have stock kk and my device is unlocked what would be the next step for installing a custom rom. hope I asked the question right

kadesxys said:
how do I get my root back after 4.4.2 update. all instruction lead to needing custom rom and or rooted. I have stock kk and my device is unlocked what would be the next step for installing a custom rom. hope I asked the question right
Click to expand...
Click to collapse
no need for custom rom just install a recovery like twrp then flash root and then you are rooted

Fastboot Success??
billycar11 said:
no need for custom rom just install a recovery like twrp then flash root and then you are rooted
Click to expand...
Click to collapse
Has anyone actually flashed a custom recovery on an xt925 4.4.2 OTA? I have had no luck trying any kind of fastboot, mfastboot, Olympian-fastboot... Nothing. If anyone has, perhaps point us to the resource you used. Thanks.

gtan2589 said:
Has anyone actually flashed a custom recovery on an xt925 4.4.2 OTA? I have had no luck trying any kind of fastboot, mfastboot, Olympian-fastboot... Nothing. If anyone has, perhaps point us to the resource you used. Thanks.
Click to expand...
Click to collapse
i use fastboot from the android sdk also make sure you have moto drivers installed

billycar11 said:
i use fastboot from the android sdk also make sure you have moto drivers installed
Click to expand...
Click to collapse
And you did this after the OTA update to 4.4.2? I'll double check the drivers, since I use multiple phone types on my PC. Thanks.

gtan2589 said:
And you did this after the OTA update to 4.4.2? I'll double check the drivers, since I use multiple phone types on my PC. Thanks.
Click to expand...
Click to collapse
yes i did this on 4.4.2
---------- Post added at 03:35 PM ---------- Previous post was at 03:28 PM ----------
gtan2589 said:
And you did this after the OTA update to 4.4.2? I'll double check the drivers, since I use multiple phone types on my PC. Thanks.
Click to expand...
Click to collapse
also here is updated recovery https://twitter.com/dhacker29/status/557054829357707264
edit: i hate the sites he uploads to but you can figure out the right button

Ok. I tried what you said (checked the drivers) and I'm getting this...
(bootloader) Variable bot supported!
Then it looks like it worked, but no joy. Ideas?
--Update--
Just tried with 'mfastboot' and it gave me no error this time and didn't freeze after 'writing recovery', i.e. actually finished the process. Still no TWRP recovery on the phone though.

gtan2589 said:
Ok. I tried what you said (checked the drivers) and I'm getting this...
(bootloader) Variable bot supported!
Then it looks like it worked, but no joy. Ideas?
--Update--
Just tried with 'mfastboot' and it gave me no error this time and didn't freeze after 'writing recovery', i.e. actually finished the process. Still no TWRP recovery on the phone though.
Click to expand...
Click to collapse
Are you booting directly back into recovery after flashing? If you don't, stock recovery will override it. After flashing, immediately power off the phone and boot straight into recovery.
Sent from my HTC6525LVW using Tapatalk

RikRong said:
Are you booting directly back into recovery after flashing? If you don't, stock recovery will override it. After flashing, immediately power off the phone and boot straight into recovery.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I can't get that far. Whenever I try to flash the recovery, I get...
(bootloader) Variable not supported!
target reported max download size of 31457280
C:\Users\Gaetano\AppData\Local\Android\android-sdk\platform-tools>fastboot getvar all
(bootloader) version-bootloader: 109B(*)
(bootloader) product: vanquish_u
(bootloader) secure: yes
(bootloader) mid: 0056
(bootloader) version: 0.5
(bootloader) serialno: TA24001ST4
(bootloader) qe: qe 0/1
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 16GB
(bootloader) reason: Reboot to bootloader
(bootloader) revision-hardware: 0x8300
(bootloader) cpu: MSM8960 CS
(bootloader) uid: 93ABD20802000100000000000000
(bootloader) cid: 0x0e
all:
finished. total time: 0.031s
--UPDATE--
Got it!! I had to...
mfastboot erase cache
Then everything work perfectly!! Thanks, all.

Hello! I'm trying to root it, but it seems like I can't! Is it beacause my version is unable to do so? I have already unlocked the bootloader, flashed the CWM even tryed the TWRP, but I'm unable to do it from the PC and even by the ROM Manager App.
As I enter the recovery mode, there is always a opened up android robot with the !triangle
sistem vers: 180.46.117.XT925.Brasil.en.BR
running 4.4.2
where am I missing?
Thanks!

euricko said:
Hello! I'm trying to root it, but it seems like I can't! Is it beacause my version is unable to do so? I have already unlocked the bootloader, flashed the CWM even tryed the TWRP, but I'm unable to do it from the PC and even by the ROM Manager App.
As I enter the recovery mode, there is always a opened up android robot with the !triangle
sistem vers: 180.46.117.XT925.Brasil.en.BR
running 4.4.2
where am I missing?
Thanks!
Click to expand...
Click to collapse
Looks the same issue I had. When you are in bootloader (fastboot) did you try erasing the cache, then flash recovery?

gtan2589 said:
Looks the same issue I had. When you are in bootloader (fastboot) did you try erasing the cache, then flash recovery?
Click to expand...
Click to collapse
sorry it took too long to answer you. now it won't be online on the adb. i think i've tried everything, new drivers, sdk update, debuggin on/off, delete certifieds pcs, reboot. I'm about to give up hahahah
I couldn't try to do "mfastboot erase cache"

euricko said:
sorry it took too long to answer you. now it won't be online on the adb. i think i've tried everything, new drivers, sdk update, debuggin on/off, delete certifieds pcs, reboot. I'm about to give up hahahah
I couldn't try to do "mfastboot erase cache"
Click to expand...
Click to collapse
Try it without the "m" (fastboot). "mfastboot" command only works if it's in the directory. If that doesn't do it, do a search for "mfastboot" (Motorola version of "fastboot"), put it in the same folder as "fastboot", and try again.
It took me almost 3 weeks of research and experimentation to find something that worked. Don't know how some people got it done so easily.

Amazon Moto G4 bootloaders can't be unlocked?

I've followed a couple tutorials of that explain how to unlock Motorola's Moto G4 bootloader. This seems to be the "official" one from Motorola:
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
I copied part of it up to where I get stuck. Here it is:
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure fastboot is in your $PATH)
At the prompt, type $ fastboot oem get_unlock_data
The returned string will be used to retrieve your unlock key.
Example: On a Windows Desktop, the returned string format would be $ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
****************************************
OK, so I just bought a Moto G4 for $125 on Amazon's prime day. This means that it has ads on the lock screen. I'm OK with that. But I think they also made the locked bootloader unlocakble as 3 times I've gotten this from a Windows machine in ADB mode:
(bootloader) Unlock data:
(bootloader) 3A45210407248602#
(bootloader) 5A59323233433246534C004D6F746F2047200000#
(bootloader) 1095EFAB6000EDC14660539C503A04F7900B9A01#
(bootloader) 9F93C800000000000000000000000000
There should be numbers in that first Bootloader line and then Motorola says:
You're device does not qualify for bootloader unlocking.
Has anybody else had this happen? This is my second time doing this to a Motorola phone and the Moto g2 was a snap! I was hoping to install a custom recovery like TWRP so I could get a nandroid backup while everything is new
Marty

LinuxHippy said:
You're device does not qualify for bootloader unlocking.
Has anybody else had this happen? This is my second time doing this to a Motorola phone and the Moto g2 was a snap! I was hoping to install a custom recovery like TWRP so I could get a nandroid backup while everything is new
Marty
Click to expand...
Click to collapse
A Lot of us have already unlocked our bootloader

Rempala said:
A Lot of us have already unlocked our bootloader
Click to expand...
Click to collapse
Do u have the Amazon moto g4?

I do and I unlocked my bootloader and rooted the phone already.

Yes I have the Amazon G4

Well, these posts gave me hope that I was repeating the same mistake and I was. Forth time worked to unlock the BL. I was deleting the # signs at the end of each line. That was the mistake. It should be this from 4 lines:
3A45210407248602#5A59323233433246534C004D6F746F2047200000#1095EFAB6000EDC14660539C503A04F7900B9A01#9F93C800000000000000000000000000
Now I'm trying to boot into the TWRP image I flashed with fastboot and fastboot gave me errors about it not being signed so I'm not sure it worked. Where are people here getting the Moto g4 TWRP images? I went here:
https://www.androidfilehost.com/?w=...23bf15e9165ccc3b437c48af2047195d3fae863dca817

This is what I get when I try to flash TWRP now and then reboot into it with adb:
C:\Users\Huntz\Downloads>fastboot devices
ZY223C2FSL fastboot
C:\Users\Huntz\Downloads>fastboot flash recovery twrp_athene_20160526.img
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (12498 KB)...
OKAY [ 0.398s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.344s]
finished. total time: 0.746s
C:\Users\Huntz\Downloads>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: no devices/emulators found

Just FYI, Motorola's bootloader unlock website has a webtool that you can use to clean the output of get_unlock_data, so you'll only get the relevant info. Copy-paste the raw code into the tool, hit clean, copy paste the output into the unlock code line on the website, submit.
Regarding TWRP, yes I think everyone gets that "Image not signed or corrupt" message. Also, you can't "adb reboot recovery" from fastboot. Just flash it via fastboot, reboot into fastboot, then go into recovery.

Maybe it did install twrp OK since it still boots into the original stock ROM OK. How do u get into twrp with the buttons on the phone?

LinuxHippy said:
Maybe it did install twrp OK since it still boots into the original stock ROM OK. How do u get into twrp with the buttons on the phone?
Click to expand...
Click to collapse
Boot into fastboot (press and hold power + volume down, let go when the bootloader screen shows up), press down on the volume rocker twice, and it'll say "recovery mode" on the screen. Press power once and it'll boot into TWRP.

Something's wrong then. I get to the fastboot screen OK but when I go into recovery it says your device has been unlocked and can't be trusted. It will reboot in 5 sec and then I see a dead robot.
EDIT
it does boot OK into the stock ROM from there if u do nothing for a minute or two or if u just hold in power button for 15 secs to get a black screen and then release the button and hold it 4 secs to get a normal boot

Sounds like TWRP didn't flash correctly, or maybe was a bad download (can download directly from TWRP's website here: https://dl.twrp.me/athene/). Reboot back into fastboot and try flashing TWRP again (you might also want to try renaming it to recovery.img, so the flashing command would be "fastboot flash recovery recovery.img").

I'll try again later today-hopefully it works and thanks for the link
I'm gonna try doing adb in Linux too.

xtermmin said:
Sounds like TWRP didn't flash correctly, or maybe was a bad download (can download directly from TWRP's website here: https://dl.twrp.me/athene/). Reboot back into fastboot and try flashing TWRP again (you might also want to try renaming it to recovery.img, so the flashing command would be "fastboot flash recovery recovery.img").
Click to expand...
Click to collapse
When u reboot now, do u get a 5 second delay screen that says your device has been unlocked and can't be trusted?
Marty

LinuxHippy said:
When u reboot now, do u get a 5 second delay screen that says your device has been unlocked and can't be trusted?
Marty
Click to expand...
Click to collapse
Yes, that is normal for devices with unlocked bootloaders. You can get rid of it by rebooting into fastboot and following this guide: http://forum.xda-developers.com/showpost.php?p=67031810&postcount=5
(if you don't have mfastboot, you can use plain-old fastboot as well)

I'm puzzled-the md5 on twrp was right and I unlocked the BL OK. I'll try it in Linux later and see if it takes.

Might be worth trying another USB port or even another cable. Some people have issues when trying to flash things on a USB 2.0 phone plugged into a USB 3.0 port.

About how much time should it take to flash twrp? I don't think it even flashed anything yesterday because it was too quick.

LinuxHippy said:
About how much time should it take to flash twrp? I don't think it even flashed anything yesterday because it was too quick.
Click to expand...
Click to collapse
It is almost instantaneous. As for the booting into recovery and seeing the dead robot, that is probably due to the fact that the phone tries to re-write the recovery when you reboot automatically. Just flash the twrp.img, and then go to recovery from the bootloader without rebooting and you will be fine; just make sure you have whatever you want to flash (e.g. supersu) on your device storage when you get there.

Sounds like a plan! What's the md5 on the supersu file?

Bootloader loop - unable to unlock bootloader

Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.

pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad
HTML:
fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.

minimale_ldz said:
You can still flash the firmware that is meant for your model/carrier without unlocking bootloader. run getvar all command in fastboot to determine what firmware exatly do you need if unsure.
Click to expand...
Click to collapse
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response

pldeep said:
Can you please guide me trough the steps in a very vauge way(I'll be able to folllow) thanks a ton for the response
Click to expand...
Click to collapse
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.

minimale_ldz said:
Connect your phone in fastboot mode and type this command:
Code:
fastboot getvar all
in output look for this:
Code:
(bootloader) ro.build.fingerprint:
It's the firmware version that you currently have on your phone. Download exactly the same one and you'll be able to flash it with bootloader locked.
Click to expand...
Click to collapse
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again

pldeep said:
Hey Sorry minimale_ldz,
I got it till this step. I wanted to know what command should I use to flash the os into the phone.
I know how to do Recovery though
HTML:
Fastboot flash recovery recovery.img
I want to know how to do the same with OS.
Thanks again
Click to expand...
Click to collapse
You've got instructions in this thread:
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Mind that you'll likely have more system.img_sparsechunk files, so make sure you flash all of them (just change commands accordingly).

Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please

pldeep said:
Guys I had no luck in doing that.
When ever I try to flash the contents of the stock os, I get a error message which says Pre Flash validation failed.
Can any one help me please
Click to expand...
Click to collapse
Your emmc ship is corrupt. That means your whole storage is broken and not fixable.

But i am able to flash some of the contents of the stock ROM. I get this "Pre flash validation failed" error only when I try to flash some of the files like (system.img_sparsechunk.0-9,recovery.img and gpt.bin). I even tried to reset the emmc_chip, I says that the command was succesfully executed.
Is there any other option left??
I am fighting this battle since a week now.

pldeep said:
Dear All,
I have a Problem with my Moto X play XT 1562. I have brought it a year back.
For some strange reason, My phone stopped working all of a sudden.
when I connect it to a PC via USB I'll get a boot-loader menu which says "StartUp failed Please connect the phone to a software repair assistant on the PC". Though I have figured out the problem I am unable to do anything about it.The problem is simple yet complex at the same time,
Problem: Though I have rooted many android phones previously, I never rooted this one. So My boot-loader is locked. I have got the Unique unlock key from Motorola site But when I get to this commad fastboot oem unkock [MY_UNLOCK_KEY]
I get an error message saying "Check 'Allow unlock OEM' in developer options". But my phone is not booting so far so that I can check that.
The basic problem is, My phone's OS is corrupted and I am unable to boot a new OS to it, As the boot loader is locked, I am unable to unlock the boot loader because I have not checked on 'Allow OEM unlock'. I am unable to check 'Allow OEM Unlock' because I The os is corrupted. - (This looks like a riddle )
1.Is there any way I can either bypass this?
2.Is there any way I can check 'Allow unlock OEM' using fastboot or any other tool?
I have tried the following already,
1.tried to clear user data and cache with fastboot - Still remains the same
2.tried to flash a recovery image even though the boot-loader is locked - No Use.
3.contacted service centre just to realise that I have to change the PCB which will cost me a new phone!
Can anyone of you please help me out with this.
Thanks a Ton in Advance.
Click to expand...
Click to collapse
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC

kpamkar said:
Bull**** about the PCB. Use RsdLite, had the same issue. Flash the latest package and use the USB at the back of the PC
Click to expand...
Click to collapse
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with
HTML:
fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!

pldeep said:
Hey Kpamkar,
I have tried it with RSD Lite, But no luck. on the RSD interface it says that flash failed,
On the mobile it says
version downgraded for primary_gpt
Can you please help me out with the latest stock rom for Moto x play, I am unable to get the exact stock rom any where, I have looked at this link: https://github.com/motoxplay/stock
My phone finger prints details are as follows(I got it with fastboot getvar all
command):
ro.build.fingerprint[0]: motorola/lux_retasia_ds/lux_uds:6.
ro.build.fingerprint[1]: 0.1/MPDS24.107-70-1-5/5:user/relea
ro.build.fingerprint[2]: se-keys
ON the phone these are the details that are shown:
baseband version:M8936_2020632.44,03.21.57R LUX_EMEA_DSDS_CUST
Product/Variant: LUX XT1562 32GB P2C
It wold be great if you could please share with me any kind of links that you have used which can guide me through this whole process.
Thanks a lot again!
Click to expand...
Click to collapse
In my case I had. 52 version of the ROM. I had a locked bootloader boot loop. But I was able to fix it using rsdLite. Are you using the latest version of the firmware and connecting the ports at the back of the pc? Also install proper drivers
You need to use RETASIA DS, the most recent version

@pldeep
firmware is here.

minimale_ldz said:
@pldeep
firmware is here.
Click to expand...
Click to collapse
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"

pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
try flashing it without gpt.bin and bootloader

Try booting into twrp without flashing it. Use fastboot boot command
---------- Post added at 08:44 PM ---------- Previous post was at 08:29 PM ----------
pldeep said:
Tried this. But no luck.
It still shows the same error "version downgrade for gpt_bin"
Click to expand...
Click to collapse
What are you trying to flash?

Same problem over here... Did you solve it?
Downloading right now the latest rom image for Moto X Play from this site.... //firmware.center/firmware/Motorola/Moto%20X%20Play/Stock/XT1563/

Hey install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Then run :- Fastboot reboot recovery.img
It will boot to twrp.

Any update for this? I'm in a similar situation now :-/
Tried RSD, it doesn't see my device (fastboot and adb works fine)
install Fastboot files and download twrp image for Lux and place it in the Fastboot folder.
Click to expand...
Click to collapse
How can I do that?
Also, someone mentioned emmc_chip reset - how to do that?
Thanks

PSA: 'fastboot boot'ing a bad image can confuse the A/B bootloader (fix inside)

Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!

So useful, thanx man!

Thank you, this is good to know.

Can anyone share system dump pls?

No need for system dump, the factory images are up: https://developers.google.com/android/images

joshua_ said:
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
Click to expand...
Click to collapse
With that said you should still probably reflash partition_b because it might interfere with future updates which I assume you know how they work. Images like @hazzamon said are finally available.
Sent from my marlin using XDA Labs

Doesn't pixel 1 have a TWRP version which can see both slots and boot to either? Did you try to install or just fastboot to .img file? Did you unlock the bootloader? If you bought it from Google, I would think the bootloader should be pretty easy to unlock, there is the option to allow it in the dev settings.

I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Any Help would be greatly appreciated!
Thanks!

I was looking through the bootloader screen and apparently there is a download mode, perhaps you could sideload an OTA

RagedElimanator said:
With that said you should still probably reflash partition_b because it might interfere with future updates which I assume you know how they work. Images like @hazzamon said are finally available.
Click to expand...
Click to collapse
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
pvillegeek said:
I flashed the 8.1 beta using an old fastboot (that didn't know about slots) and now I'm stuck in the bootloader. I can't get android to boot, and I can't even get into the stock recovery or download options.
I've tried flashing the stock image several times, but that didn't do any good.
Click to expand...
Click to collapse
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
pixel-painter said:
I was looking through the bootloader screen and apparently there is a download mode, perhaps you could sideload an OTA
Click to expand...
Click to collapse
The download mode is a no-op on production Walleye, I think
pixel-painter said:
Doesn't pixel 1 have a TWRP version which can see both slots and boot to either? Did you try to install or just fastboot to .img file? Did you unlock the bootloader? If you bought it from Google, I would think the bootloader should be pretty easy to unlock, there is the option to allow it in the dev settings.
Click to expand...
Click to collapse
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.

joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
The download mode is a no-op on production Walleye, I think
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
Click to expand...
Click to collapse
Which is why I asked if the bootloader was unlocked

joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Click to expand...
Click to collapse
I wonder if that means that flashing the factory image replaces the opposite slot with those prebuilt odex files then. On the original Pixel and Pixel XL it just flashed the opposite slot with an empty image.

joshua_ said:
Reflashing slot B is kind of funny on these devices. When they come from the factory, slot B doesn't come with an Android image, but instead the extra space is used to host prebuilt .odex images, to speed up first boot. (They comment on this in the A/B appnote: https://source.android.com/devices/...size-of-the-system-partition-without-squashfs ). So you actually don't really want to reflash slot B if you can avoid it.
Have you tried with a modern fastboot?
What does 'fastboot getvar all' tell you?
You need to set_active, like I mentioned.
The download mode is a no-op on production Walleye, I think
I took the steps I mentioned in the OP You can't fastboot boot, fastboot set_active, or fastboot flash something without unlocking the bootloader.
Click to expand...
Click to collapse
Well if you want to use slot_b then you might as well flash the image over that the slot_a pretty much takes place of what slot_b was in the beginning, but yeah you are right though about having slot_b at preconfigured state yet that's if you are on slot_a.

I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
PS C:\Users\hanna\Desktop\platform-tools> fastboot boot twrp-3.1.1-beta1-walleye.img
downloading 'boot.img'...
OKAY [ 0.715s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.734s
Click to expand...
Click to collapse
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?

mtpease said:
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
Click to expand...
Click to collapse
Use cmd instead of powershell. I've had issues relating to fastboot/adb with PS in the past
Sent from my Pixel 2 using Tapatalk

mtpease said:
I think I might be in real trouble. I can't boot anything at all, just like others in this thread. I can't even boot TWRP, and I get this error:
I've tried setting the active slot to a, and back to b. I've tried multiple times to flash the stock image files from Google. They appear to flash normally, but I still can't boot.
All of this started after I accidentally tried to boot the recovery image from the pixel 2 xl. Something got seriously messed up, and I can't figure out how to repair it.
Does anyone know what else I can try?
Click to expand...
Click to collapse
I was in the same boat. Would only boot to bootloader after typical manual flash-all of the system image (no recovery, no nothing, just bootloader).
Here's what I did (Windows 10):
1) Update fastboot/adb
2) Download and extract latest 8.0 image (ends in 25)
3) Open CMD (not powershell)
4) fastboot set_active other
5) Manually flash bootloader (failed for me), radio (went ok), update .zip (some errors), reboot bootloader between each:
fastboot flash bootloader <location>
fastboot flash radio <location>
fastboot update <location of image-walleye-opd1.170816.025.zip>
6) fastboot set_active other then repeat bootloader, radio, update.zip manual flashes
Though I read this about the og Pixels... Basically just manually flash images to both slots when all else fails.

joetheshmo said:
Use cmd instead of powershell. I've had issues relating to fastboot/adb with PS in the past
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
I'm trying this now, but I can't get my phone to boot. It just goes back to the bootloader (which is unlocked). I'm getting the same "FAILED (remote: Failed to load/authenticate boot image: Load Error)" error. My adb/fastboot is at the latest version. Trying to flash the 8.1 factory image.

joshua_ said:
Yesterday, I was messing about trying to fastboot boot other MSM8998 TWRP boot.imgs, with the hopes that the device-trees on some of them would be close enough to get far enough in boot to bring up the USB port (even if they didn't mount anything or bring up the screen). As it turns out, none of them did (and, in fact, they all blanked the screen and went back to having the USB interface enumerate as fastboot -- how could that be? does anyone understand what could cause fastboot to reject a kernel before even trying to boot it?), but when I was done for the day, I had another disturbing event: when I tried to boot the device normally, it would simply sit there at the fastboot screen, and in fact, when I tried to boot into recovery, it would still just kick me back to fastboot.
This was very scary -- without factory images to reflash it with, I thought I had bricked my device! I did a fastboot getvar all, and saw:
Code:
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:0
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:3
(bootloader) slot-unbootable:a:yes
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
So apparently just fastboot booting something that fails to boot can cause fastboot to declare that the live system image is no good.
If this happens to you, the answer to this is to make sure that you have the latest platform-tools (I had a properly oldschool version of fastboot that I've been kicking along on my Mac from the unrevoked era...) -- get them from Google -- and you can un-confuse the bootloader even without flashing a new image by doing a fastboot set_active a.
Then your phone will boot again. Phew!
Click to expand...
Click to collapse
What if both partitions show as not successful?
Code:
(bootloader) current-slot:b
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:no
(bootloader) slot-successful:b:no
(bootloader) slot-retry-count:a:5
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:no

Sorry to resurect this from the dead, but I was in the same boat and there doesn't seem to be an answer here, So I'll tell you what I did.
1. I booted into linux
2. Made sure my android platform tools were up to date
3. from the bootload I went to recovery(which would not open, ended up with phone with black screen)
4. from that black screen I could use Duece's tool and that fix the phone to where it will at least boot properly.
In hope this helps