Database Users

Xoom memory/flash LOCKED ???

Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks

y2k-inc said:
Ok i will explain ...
Got my Xoom ROOTED but decided to put it back to stock, so I UNROOTED by flashing my Canadian 3.0 version, boot it up update to the 3.1 OTA and then setup my market, the XOOM FC out alot so i want to try "hacked firmware".
Boot to fastboot to flash CWM recovery, all the flash show completed OK, reboot into recovery to only found out that it's not there ... ok, try factory reset from the Recovery, all good and then the Xoom reboot ... all my data is still there, then try Setting > Private > factory reset ... all OK, but can boot into the Recovery to fully reset ... no problem, i will reflash a different version via Fastboot.
Try the US-Wifi version, all the flash/erase when OK but still at Canadian 3.1 ... then try installing ROM manager, install fine and working (of cause no Root access). Reboot and the ROM manager is gone ...
Look like the Memory of the Xoom somehow is LOCKED?
Anyone have a idea? i'm taking out the battery for 1h now and hope to have some reaction ... but still nada!!!
Help!!! Thanks
Click to expand...
Click to collapse
When you flashed the stock Canadian images did you relock your bootloader?
If you followed Moto's instructions completely it ends with relocking.
It sounds like you need to unlock again and go from there. You will still get the OTA updates if you are unlocked as long as you are completely stock, if that's what you're worried about.

okantomi said:
When you flashed the stock Canadian images did you relock your bootloader?
If you followed Moto's instructions completely it ends with relocking.
It sounds like you need to unlock again and go from there. You will still get the OTA updates if you are unlocked as long as you are completely stock, if that's what you're worried about.
Click to expand...
Click to collapse
Yup! Locked up so i can get OTA, since instruction are differences from person to person ... now, no mater if i unlocked it, it's look like the memory locked out ... like i have copy some files over it, and upon shutdown and restart, the file are gone on the Xoom ... it's like your CMOS on your computer only save data when it on power but lost when you shut it down (is there a backup battery on XOOM?)
Thanks

please .... any one?

Start over from scratch. If you want stock U.S. then use the U.S. stock imgs. Make sure that you use no Canadian imgs. If you want Canadian use the Canadian stock imgs. It looks like you flashed the wrong files together. I see people flashing U.S. stock then trying to root with their country imgs and it messes up. Use adb and fastboot flash moto stock imgs again, boot img, recovery img, system, erase cache, etc. Just remember if you use canadian, the you have to root with a Canadian file as well.
Sent from my Xoom using xda premium

hammer4203 said:
Start over from scratch. If you want stock U.S. then use the U.S. stock imgs. Make sure that you use no Canadian imgs. If you want Canadian use the Canadian stock imgs. It looks like you flashed the wrong files together. I see people flashing U.S. stock then trying to root with their country imgs and it messes up. Use adb and fastboot flash moto stock imgs again, boot img, recovery img, system, erase cache, etc. Just remember if you use canadian, the you have to root with a Canadian file as well.
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Been there, done that the fastboot flash toke all the flash steps but after it's just "like reversed back" to the original one ... i can even ERASE everything with fastboot and the Xoom still boot up with the "old image" is there a "Short or reset button" on the Motherboard? i have toke out the battery for 10h now
Thx

Sounds like you have not changed the files in your tools folder. I use a seperate folder for stock and root. Keeps me from flashing a file wrong. Make sure that is not happening. Did you try and oem unlock and reboot, then go back to fastboot and flash?
Sent from my ADR6400L using xda premium

done that but not work
C:\SDK_tools>fastboot oem unlock
... INFO To continue, follow instructions on the device's display...
OKAY [ 52.261s]
finished. total time: 52.261s
C:\SDK_tools>fastboot erase boot
erasing 'boot'... OKAY [ 0.289s]
finished. total time: 0.289s
C:\SDK_tools>fastboot erase system
erasing 'system'... OKAY [ 0.366s]
finished. total time: 0.366s
C:\SDK_tools>fastboot erase recovery
erasing 'recovery'... OKAY [ 0.294s]
finished. total time: 0.294s
C:\SDK_tools>fastboot -w
erasing 'userdata'... OKAY [ 13.663s]
erasing 'cache'... OKAY [ 0.529s]
finished. total time: 14.192s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.637s]
writing 'boot'... OKAY [ 0.586s]
finished. total time: 1.224s
C:\SDK_tools>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 16.741s]
writing 'system'... OKAY [ 7.270s]
finished. total time: 24.011s
C:\SDK_tools>fastboot flash recovery recovery.img
sending 'recovery' (12288 KB)... OKAY [ 0.894s]
writing 'recovery'... OKAY [ 3.590s]
finished. total time: 4.485s
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 8.946s]
writing 'userdata'... OKAY [ 8.166s]
finished. total time: 17.113s
C:\SDK_tools>fastboot erase cache
erasing 'cache'... OKAY [ 3.215s]
finished. total time: 3.215s
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...

Looks like this line:
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
might be the cause of your problem. I think if you lock you can't write.

cadiken said:
Looks like this line:
C:\SDK_tools>fastboot oem lock
... INFO To continue, follow instructions on the device's display...
might be the cause of your problem. I think if you lock you can't write.
Click to expand...
Click to collapse
Yes, why lock?

Yep if you lock you can't flash. Go in and fastboot OEM unlock. Then you can update.
Sent from my Xoom using xda premium

problem is not if the Xoom is locked or not, i have tried all possibilities so far, but some place they tell to lock it for OTA.

If it is locked you can't load any cwm or custom firmware.
Sent from my ADR6400L using xda premium

Do you means the bootloader is locked? event "fastboot oem unlock" show successful unlock?
Please elaborate?
I wish there is nvflash that you can use like the Gtablet

Yeah bootloader locked. But if it says unlocked then try a different rom.
Sent from my ADR6400L using xda premium

I have done all the Fastboot things without luck, bootloader version 1045 if anyone know how this is can be fix?
like i said, all fastboot command response with success ... so only way now is to see how can i short the memory to wipe out and restart ... any idea?
Thx

I will clear something up for you. You absolutely do NOT need to lock the bootloader for a ota.
In fact there really is NO reason to re lock the bootloader unless you are sending it for repairs.
Where over or who ever said to re lock it you should ignore them from now on.

albundy2010 said:
I will clear something up for you. You absolutely do NOT need to lock the bootloader for a ota.
In fact there really is NO reason to re lock the bootloader unless you are sending it for repairs.
Where over or who ever said to re lock it you should ignore them from now on.
Click to expand...
Click to collapse
thanks for the heads up ... i think it's needed a jtag now

anyone know how to get the SFU file out from a working Xoom so it can be used be RSD Lite for restoring?

[FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1

First of all:Remember:im just making a thread, all of this wasn´t possible if not for @ccfries(He works at motorola, and sent the files to shamu´s device tree repo)
and @Casper34
See: http://forum.xda-developers.com/showpost.php?p=59562745&postcount=9 and https://android-review.googlesource.com/#/c/143010/
Requirements:
Motorola Drivers:
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Qualcomm Drivers:
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
Optional: If having issues use:
http://forum.xda-developers.com/showthread.php?t=2263822
Unbrick Stuff:
https://www.dropbox.com/s/8783ohne2mufiwc/Nexus6Unbrick.rar?dl=0
or
https://drive.google.com/file/d/0BwduAK2l37Oaa1BQZncwaEpNb1E/view?usp=sharing
Factory Images for Nexus 6(needs to be 5.1)
https://dl.google.com/dl/android/aosp/shamu-lmy47d-factory-6c44d402.tgz
or via RSD Lite
http://motofirmware.center/files/file/1069-shamu-lmy47e-release-keys-subsidy-default-cfcxmlzip/
FASTBOOT AND ADB NEEDS TO BE ALREADY SETTED UP
Pre Requirements:
- Disable driver signature checking
Windows 7:
https://www.youtube.com/watch?v=k4RwaI4mn6Y
Windows 8:
https://learn.sparkfun.com/tutorial...abling-signed-driver-enforcement-on-windows-8
Windows 8.1:
http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
- Install the drivers:
Go to device manager, Unknown devices, double click qhusb_bulk, install driver, select location and select where you extracted the drivers.
{
"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"
}
- Next you should extract both zip files (Unbrick and factory images)
- Then Connect your nexus 6 on your computer (now should appear as Qualcomm HS-USB QD-Loader 9008 under "COM PORTS"):
- Open the Unbrick folder and run blank-flash.bat:
- Flash Stock factory images: (Problems see #2)
Your phone should show up on the computer as fastboot.Just flash stock factory images. (Motorola via "RSD Lite" or Google one should do the trick).
Thanks:
@ccfries(HUGE Thanks to him, turns out he is the one who made the commit with the necessary files, props to him!)
@Casper34 (Huge help with his working nexus 6)
@bitdomo (helped me a lot, and i got some images from another thread of his)

Problems that may occur during or after:
Stuck at waiting for device
Check if drivers are installed correctly and restart pc
Check if you have an updated fastboot
THESE TWO ARE THE MAIN REASON OF PROBLEMS (mostly outdated fastboot)
-Drivers
http://forum.xda-developers.com/showthread.php?t=2263822
http://storage.googleapis.com/tetheredupgrades/MotorolaDeviceManager_2.5.4.exe
Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
Problems while flashing factory images:
ccfries said:
First, fastboot flash partition gpt.bin
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Click to expand...
Click to collapse
PS:
ccfries said:
If you lock, it clears the setting by design, so you can't lock and unlock without booting up and checking the box.
Click to expand...
Click to collapse
Wifi / Bluetooh dosen´t work:
See http://forum.xda-developers.com/showpost.php?p=59561966&postcount=3
No IMEI / No Signal
Restore EFS Backup

If wifi/bt/camera dosen´t work Then probably your /persist got somehow corrupted. (Post Under construction)
For a fix:
Flash a custom recovery, and open a terminal with the phone booted to it
run
umount /persist
mkdir /persist
mount /dev/block/platform/msm_sdcc.1/by-name/persist /persist
#e2fsck /dev/block/platform/msm_sdcc.1/by-name/persist
you will be propmpted to check / repair errors, keep pressing enter for each that it appears
then run
umount /perist
and reboot phone

Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:

wow indeed!

jayharper08 said:
Wow! Very nice. I bet you just saved some poor guys from getting yelled at from wifey. Good job and thanks for helping the community. :highfive:
Click to expand...
Click to collapse
simms22 said:
wow indeed!
Click to expand...
Click to collapse
Thanks to both, thankfully cm already merged a check for the bootloader, but i hope this can fix phones that are already bricked for people who cant use warranty (outside area, on a trip, etc).
Oh yeah, or in the case of my friend, his mom

This needs stickied
Sent from my Nexus 6 using XDA Free mobile app

@opssemnik
No worries, glad to help out!
Sent from my Nexus 6

opssemnik said:
@ccfries(Huge thanks for him, for finding an un merged commit that had the partition layout)!.
Click to expand...
Click to collapse
I authored the commit this afternoon so finding it was pretty easy. :good:

ccfries said:
I authored the commit this afternoon so finding it was pretty easy. :good:
Click to expand...
Click to collapse
Oh no wait, I DIDN´T SEE THE AUTHOR LOL.
may i ask was it hard for you to get the permission to post? afaik these files are proprietary (aside from the paritition table) or aren´t they?.
also can i ask you something a bit more offtopic?
i noticied the nexus 6 works directly with QPST (at least it can communicate with it)
but some other devices (like the nexus 5) can´t, its something that qualcomm or the manufacturer decide / make?
Once again ,props to you and motorola!
Never thought of an oem doing that, even more that the bricks can only be achieved when messing with things you shouldnt be :good::good::good:

Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?

So I thought I would rid myself of no Xposed or CM12 on 5.1 (LMY47D) by going back to 5.0.1 and flashing CM12 again from an older nightly I had downloaded already....I think we all know what happened.
I managed to get through it all and have the blank-flash boot loader screen up but I get hung up on <waiting for device> when trying to flash factory image (LMY45D). The boot loader shows as locked and as a result I am unable to flash a factory image. Hopefully I am not breaking any rules or anything by posting this here but this is the error I am getting when running the flash-all.sh:
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.131s]
writing 'bootloader'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.181s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.769s]
writing 'radio'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 2.772s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(665,0xa03911d4) malloc: *** mach_vm_map(size=1779851264) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1778070480 bytes
error: update package missing system.img​
and when I try to run em unlock:
fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.002s​

Looks good. Does this only help the CM12 people or does it override the "enable OEM Unlock" people too?

serdaj said:
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
Click to expand...
Click to collapse
First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris

Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.

Delboyd12 said:
Damn, wish this was on here last week. Had to send my N6 off to repair centre for this as I thought it was a gonner. Fault diagnosed as 'Electrical issue - Replacement required'. Replacement is coming tomorrow hopefully. Will bookmark this, thanks.
Click to expand...
Click to collapse
That was when he started this.... After many bricks. I know a lot of people RMAed their phones, but this can still help others!

ccfries said:
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1.
Click to expand...
Click to collapse
It would be helpful if the OP would add this to his first post.

@opssemnik Great Job can you please help me to do so with my HTC One M8 ?
i had the same problem " qualcomm hs-usb qdloader 9008 "
Thanks

bradputt said:
Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?
Click to expand...
Click to collapse
Restore he wrote
Shamu/Hammerhead/Flounder Dkwhq www.jsand.dk

Please can someone help me?
I am stuck in the bootloader, which is locked. I can't boot the phone up. I am trying to flash stock images but nothing is happening. Just booting to the bootloader every time.
I can detect my device using fastboot devices, but every time I try and write an img it fails, because the bootloader's locked! Argh!
Thanks in advance,
Tom

Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"

Nexus 7 (grouper) doesn't boot - Bootloader says "FAILED (remote: (FileWriteFailed))"
Hi,
My Nexus 7 (grouper) won't boot Android anymore. It automatically boots into the bootloader and when I select 'Start' or 'Recovery Mode' it just says "Booting failed".
When I try to flash a new recovery Image over fastboot I get the following Output:
[[email protected] Downloads]$ sudo fastboot flash recovery twrp-2.8.7.0-grouper.img
sending 'recovery' (11850 KB)...
OKAY [ 1.409s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 1.441s
Click to expand...
Click to collapse
It's the same, when I try to flash anything else. So I have no chance to flash a Stock-Image. I also get the same error when I try to format a partition. I'm pretty much out of ideas now. Can anybdoy help me?

yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.

productofusa said:
yeah this same thing kept happening to me (I have no idea why) Once you get into the bootloader make sure your device shows up IE fastboot devices, then flash bootloader, then fastboot reboot-bootloader then between each succeding flash use the volume buttons to select reboot bootloader on the device. I had to flash individual partitions it would'nt do a -w update, so flash system, then reboot bootloader on device, then flash, then reboot bootloader, ect
Also booting into Android takes a bit so be patient, like 10/15 min. Maybe there's an easier way but after screwng around with it for an hour this is the only way I could get 5.1.1 on it.
Click to expand...
Click to collapse
When I try to flash the bootloader I get:
[[email protected] Downloads]$ sudo fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.263s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.403s
Click to expand...
Click to collapse
And when flashing other partitions it says "FAILED (remote: (FileWriteFailed))".
Something seems to be really screwed up with my storage. Is there a way to repartition the device from fastboot? Maybe that would be help.
I'm willing to try out everything, by now.

Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!

productofusa said:
Is it possible the files your trying to flash are somehow corrupt? try downloading again. My problem was fastboot kept crashing, not really sure what you got going on.
I will say that i've just finished flashing nexus 6,7,7, and 9 and for some reason the nexus 7 (2012) was a real pain in the butt, didn't have issues with any of the others.
Maybe someone else with another idea will chime in, good luck!
Click to expand...
Click to collapse
I already downloaded them multiple times. And even if they are corrupt, formatting the partitions should still work. I'm guessing on corrupt storage now, as I can't find any other explanation. Maybe I can find a cheap Motherboard somewhere on the internet. Thanks, anyways

Blasted kingroot - bricked my phone?

Ahh, hind sight is a wonderful thing.
After trying to use kingroot to get root access, it failed. And a few days later after rebooting.
I'm now stuck at bootup with Start Up Failed.
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
I've now tried lot's of different things, over the last few hours.
RSDLite (show device brings no thing up)
Unlock bootloader (request key, but error regarding OEM unlock not being set - no access to now set it LOL)
Downloaded stock X_Play_UK_Retail_XT1562_LPD23.118-10_CFC.xml.zip, and tried using various guides on fastboot but keep getting remote failed.
I'm on stock recovery (obviously still locked).
Any thoughts, or hope from anyone?
Obviously, not sure what support Motorola would provide for what is essentially my own fault?

Have you tried manually flashing each bit of the stock firmware/image. That might help. There's a good guide here which I followed to unbrick my device. Just follow the instructions http://theunlockr.com/2015/09/22/how-to-unroot-the-motorola-moto-x-play/

Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926

Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s

sharebubbles said:
Tried the first fastboot oem lock begin but get ... (althought my phone is locked already)
(bootloader) Not supported command in current status!
FAILED (remote failure)
finished. total time: 0.063s
So stepping to next command, I get:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
(bootloader) has-slotartition: not found
target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.166s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.078s
Click to expand...
Click to collapse
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!

DTLblaze said:
I think you need to unlock the bootloader and then start with the 'fastboot oem lock begin' command. You can't flash a system image with a locked bootloader. Let me know how it goes!
Click to expand...
Click to collapse
I run the unlock command, with my unique key but I get ..
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.013s
And since I can't get into the phone, I can't therefore check the "allow OEM unclock"

Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.

DTLblaze said:
Have you tried any erase data commands or reset commands? Perhaps you could reset the phone so kingroot is un-installed and then try to turn on the phone. Short of that I'm stuck for ideas really, accept booting into 'fastboot and then erasing all data and factory reset in there. Let me know.
Click to expand...
Click to collapse
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode

Sickaxis79 said:
Or try this one.
http://forum.xda-developers.com/showthread.php?t=2499926
Click to expand...
Click to collapse
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.

sharebubbles said:
I tried the wipe data/factory reset and wipe cache partition from the stock recovery.
And if I try from fastboot:-
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase userdata
(bootloader) has-slot:userdata: not found
erasing 'userdata'...
OKAY [ 0.196s]
finished. total time: 0.198s
And then a fastboot reboot.
Back to the now standard "start up failed"
And the
AP Fastboot Flash Mode (Secure)
hab check failed for boot
Failed to verify hab image boot
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason: Fall-through from normal boot mode
Click to expand...
Click to collapse
That really does sound like you bricked the device. If you where on lollipop software you wouldn't have the issue with check bootloader OEM unlock. If it was me I would either contact Motorola or go to a repair shop and have a motd experienced person take a look at it.

Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.

sharebubbles said:
Have downloaded, and tried that - but the crux appears to be the fact that my bootloader is locked and I can't access the OEM checkbox. And therefore the tool itself can't unlock or equally install TWRP.
Unless I'm missing something in it's usage.
Click to expand...
Click to collapse
Strange. This is the tool I used to unlock my bootloader.

drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
I've ben used the latest rom so far why trying to flash (and failing) when I look at recovery I have a LPD23.118-10 number that matches to an earlier 5.1.1 rom (I had been upgraded to 6.0.1 via OTA updates) - do I therefore take that LPD ID to mean that I should actually use the 5.1.1 rom - I'm in the UK, so I'm assuming I'd use the UK one rather than Europe (I'm looking at roms on https://github.com/motoxplay/stock).
Thanks

Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)

sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
And also never try kingroot.

sharebubbles said:
Dooh!!
Looking back at what I was doing yesterday, within the mix of downloading various roms - appears that I was actually using the LPD23.118-10 and NOT the latest.
I figured, I'd give it one last whirl using the latest not expecting much - and hey presto, it's worked. Just in the process of resetting it all up again.
Thanks for everyone who contributed, and a lesson learnt about always rechecking what you attempt (and not to try to root if you're not 100% sure of what I'm doing)
Click to expand...
Click to collapse
Most in the threads suggesting using rsdlite or manual flash/root and you decided to use kingroot,haha.
Welcome back.

Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
---------- Post added at 05:26 AM ---------- Previous post was at 05:14 AM ----------
Guys I have been searching EVERYWHERE on how to unbrick my moto x play, I used kingroot and it bricked, been a week and I TRIED everything. CAN ANYONE HELP PLEASE!!!!!!
Tried restoring it, deleted everything and the phone is still on bootloader (LOCKED) and i dont even know how to fix it, I know nothing on how to root, friend suggested it, downloaded it, installed it, didnt work and then i restarted my phone and now its stuck on bootloader screen and the screen has the message "Start up failed: your device didnt start up successfully. Use the software repair assisstant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant." <- Downloaded it, tried it and it was stuck on 6% on repairing, left it over night and it was still on 6%.
ALSO under the message "AP Fastboot Flash Mode(Secure) is there)

Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)

pravin kkr said:
Hai same problem for my moto x play ple.......s help contact.7708892303(WhatsApp no.)
Click to expand...
Click to collapse
Download and flash this firmware
https://mega.nz/#!H5YlDCrD!T8tAAW7nHVS-erizRiqg5-Yp_p23hKParMjjHD4diQA credits @kumeipark
Use RSD lite to flash the firmware
http://rsdlite.com/rsd-lite-download/
Moto drivers
http://motorola-mobility-en-in.custhelp.com/app/answers/detail/a_id/88481
If you have problems installing device drivers using Windows 8.1 or Windows 10 follow this guide
https://www.youtube.com/watch?v=gmw86KplqmU
And don't post your contact no. in public forums for everyone to see.

what is the decryption key for the mega link
drmuruga said:
Try this, not necessary for unlock bootloader
Recognized Contributor3,144 posts Thanks: 1,591
Quote:
Originally Posted by sheikh.sami17
but i have locked bootloader. can i flash stock firmware with locked bootloader?
YES you can flash stock Moto roms meant for your model and carrier only.
Also, Never attempt to downgrade.
In this page
http://forum.xda-developers.com/moto-x/moto-x-qa/q-how-to-flash-to-stock-firmware-t3041813
I edit and made one firmware autoflasher for my x play Indian version and flashed successfully . everybody should check sparsechunk files no in flash file of your extracted stock firmware and edit my autoflasher files according to number of sparsechunk files and flash your firmware. It is definitely safe and I flashed my firmware by this but use at your own risk .
https://mega.nz/#!aoETEL7b!6WUe8tXeh...HHohpfYf2duoLc
First you have to download your phone's correct firmware and extract in fastboot folder , and add my autoflasher and check your sparsechunk files number and make changes according to that in autoflasher then save ..Enter your phone in fastboot mode or in bootloader and not in stock recovery and run autoflasher.
IF YOU HAVE ANY DOUBT AT TAKING RISK , CONTACT Motorola AND MAKE EVERYTHING EASY.
Click to expand...
Click to collapse
provide the decryption key

[GUIDE] Update with fastboot

Guide for installing new security update with fastboot and with a bootloader-unlocked Pixel XL.
This is basically the same thing as usual but with the new structure.
If you have modified a little the stock android (hosts file, root, kernel, etc.), you may experience a fail in OTA update;
If you have a bootloop/soft brick/not sure of the state of your android system;
This is the solution.
This WILL NOT delete your data and apps. This will remove your custom kernel/root/hosts/recovery through (which is a good thing because it will be clean then).
I assume you already have anything to do fastboot command. If not, see this good thread.
1) Download your system image for Marlin (Pixel XL) on google website.
For November update, there are 3 versions:
NDE63U Europe
NDE63V US, except Verizon
NDE63X Verizon
2) Unzip the file marlin-nde63v-factory-a66866ba.zip
3) Unzip inside the new directory (marlin-nde63v) the image-marlin-nde63v.zip
4) Reboot into bootloader
Code:
adb reboot bootloader
5) Execute fastboot commands (assuming the bin is on your PATH)
Code:
fastboot flash bootloader bootloader-marlin-*.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-*.img
fastboot reboot-bootloader
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system system.img
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img
fastboot flash modem modem.img
fastboot reboot
Here we go, you have a fresh unrooted vanilla android with latest security patch.
6) To add TWRP and Root:
Code:
fastboot boot /path/to/twrp.img
In TWRP, install twrp.zip
Reboot into the installed recovery
In TWRP, install supersu.zip
Root thread for more information.
TWRP thread for more information.

** Reserved **

cam30era said:
@firewave,
Thanks for posting the guide. Just like Nexus devices except for the slot files. After unzipping the factory image, I do notice 15 additional files (other than boot, system, vendor, etc) that I've never seen before on a Nexus device. Do you happen to know what those are for, and why we don't flash them if doing a manual fastboot flash?
Thanks, in advance....
Click to expand...
Click to collapse
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.

firewave said:
Other files are more for complete reset. There are for example, time-zones data, default crypto key, default /sdcard, bootlocker state, etc.
Only aboot.img is obscure for me. I'm at work so I can't dig into it, but I updated my pixel xl without issue that way.
I'm also add EX kernel and root again without issue.
Click to expand...
Click to collapse
aboot is actually part of the bootloader.

death2all110 said:
aboot is actually part of the bootloader.
Click to expand...
Click to collapse
yep, it's why I'm unsure what to do with. Probably nothing.
I will loopmount the file at home and see.

Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.

wx9kvh said:
Will this FDR the phone or just apply the update? I am currently on a Verizon Pixel XL Rooted/Unlocked and on the P build. Thanks for any information.
Click to expand...
Click to collapse
In the op in bold, he said it will not erase your data or apps

C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result

dablitzkrieg said:
C:\android>fastboot flash bootloader bootloader-marlin-*.img
error: cannot load 'bootloader-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.105s
C:\android>fastboot flash radio radio-marlin-*.img
< waiting for any device >
error: cannot load 'radio-marlin-*.img'
C:\android>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.047s]
finished. total time: 0.048s
C:\android>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (26405 KB)...
FAILED (command write failed (No error))
finished. total time: 0.001s
C:\android>fastboot flash system system.img
< waiting for any device >
target reported max download size of 536870912 bytes
I am getting the above error but it proceeds to do all other commands. Then I get hung up at the Google screen. Any suggestions? I can get into the bootloader. I've tried the fastboot commands twice now...same result
Click to expand...
Click to collapse
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.

chapelfreak said:
In the op in bold, he said it will not erase your data or apps
Click to expand...
Click to collapse
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.

wx9kvh said:
That was not in the original post. I screenshot the OP, the part about adding a kernel or custom ROM at the bottom was also added. But thanks for the update.
Click to expand...
Click to collapse
That makes sense, our posts are an hour apart or so.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
I appreciate the help. The link you provided me, I've downloaded it, but for some reason cant launch the app after I unzip the file. I've been at this for like 4 hours. I've tried so many different things and can't get past the Google screen. Please help

I was able to utilize the old tool. I'm all set. Thanks

chapelfreak said:
That makes sense, our posts are an hour apart or so.
Click to expand...
Click to collapse
Lol. No big deal haha.

Scott said:
Yes! Your using an old ADB / Fastboot combo...
See my post here: http://forum.xda-developers.com/showpost.php?p=69578798&postcount=74
Post if that does not resolve.
Also stop using wildcards "*". Use absolute paths.
Click to expand...
Click to collapse
Scott...can I flash the radio.img from V to the Verizon X. This radio is horrible

ADB Sideload Works too
Alternatively, use the instructions found on this page followed by a re-flash of your preferred kernel and a fastboot boottoroot to regain root.
https://developers.google.com/android/nexus/ota

So i just followed all of these instructions, and when going into about phone, it shows that i am now on an N build and still with the October security patch. What did i miss?
Update :
I believe I fixed the issue. The little window with the commands in it for some reason had scrolled up and I missed the flashing the "bootloader-marlin-*" step.
Update 2 :
I am now on X with the November security update. GREAT GUIDE!

Followed it to a T and soft bricked mine so now trying to find a way to fix or toss it out the windows haha. Just a heads up guys.
Ended up using the skipsoft tool and pushing a factory update same results but lost data/apps no biggie.

This is odd i followed the instructions trying to flash X to my phone coming from NDE63P and somehow ended up on NDE63N (Ignore this i missed a command)

What steps do I need to add if I want to completely restore back to factory settings (format userdata)? Or would it be the same to just factory reset through the newly restored stock recovery?