Database Users

Can not flash anything, PLEASE HELP

ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks

zendick said:
ok so here is the deal, been running mytouch4g for a while now rooted, cm7 etc last week phone started acting funny, required batt out reboots if camera app was on when unit went to sleep, now will not boot only boots to fastboot, can not flash anything.
Any ideas? at least an idea to remove cm signs so I can exchange unit.
thanks
Click to expand...
Click to collapse
There should be an option on fastboot to go to bootloader and then from there recovery should be available, is that option available to you?

yes but recovery won't boot, sits at mt4g boot screen or sits at 3 skaters in center screen, depending on how I access it (ie go to fastboot then back again)

Power down your phone, hold volume down and the power button. That will take you into the hboot screen. You can then select to go into recovery from there.

thats what I have tried, it goes to three skaters center screen does nothing

I have tried flashing recovery from fastboot
tried hboot from fastboot
tried radio from fastboot
NOTHING flashes trust me I have been androiding for a while now never had I had a problem like this.

zendick said:
thats what I have tried, it goes to three skaters center screen does nothing
Click to expand...
Click to collapse
Is three skaters your boot animation or splash screen? Not sure what that is referring to.

the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens

zendick said:
the three skaters is the image at bottom of hboot screen, when i select recovery they go to center screen and nothing happens
Click to expand...
Click to collapse
Oh ok, i know what your talking about now. Your on the bootloader screen under fastboot. And when you select recovery option it does not boot into recovery?

correct and like i said I have tried to reflash everything from fastboot but no go

Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error

got recovery to boot but get
e:can't mount /cache/recovery/command
etc
tried to mount, tried to format
no go

What do you mean tried ruu??
zendick said:
Just tried RUU it doesn't work it says rebooting to bootloader phone reboots to mytouch4g splash and ruu eventually gives usb error
Click to expand...
Click to collapse
Edit: nvm. Is doing RUU better option than loading PD15IMG.ZIP on sdcard and doing it that way?
Sent from my SGH-T959 using XDA App

tried a pd15 and it doesn't complete, drops a failed message

Sounds like you maybe victim of fail-pu. But if thats not the case and you don't care about your "/data" and just want working phone again then I suggest from fastboot you do "fastboot flash recovery recovery.img" which will replace the current recovery.img and flash it to mmcblk0p21. Once thats done do "fastboot erase system -w" and it will nuke everything so /system, /data, ect will all be erased. After that you can enter recovery by selecting it from hboot and then do factory wipe and flash another rom.
Keep in mind you will run in to errors in recovery after -w as its normal but depending on the fail-pu if you do get the failed partition update flag you can't make any changes as the errors will stick because you can't format the drives. Also the new recovery.img for CWMR can be found in dev section if not post here and ill send you.

I don't care at all about the data (I am well backed up) but I can't flash a recovery I have tried through fastboot, I agree the partition is F_D but I will try the erase system -w and see if that lets me do anything
thanks

uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s

Exactly what I got too, seems we have bricked our phones. Wish I had a way of making the phone unable to boot to recovery or at all.
zendick said:
uhg i think i may be foooked
C:\android-sdk\tools>fastboot flash recovery recovery2512.img
sending 'recovery' (4000 KB)...
OKAY [ 1.273s]
writing 'recovery'...
FAILED (remote: image update error)
finished. total time: 4.161s
C:\android-sdk\tools>fastboot erase system -w
erasing 'system'...
FAILED (remote: erasing error!)
finished. total time: 0.014s
Click to expand...
Click to collapse
Sent from my SGH-T959 using XDA App

I dont get how a phone can run for weeks since its last flash and have this happen, I made no changes updates etc just running as normal.
Is there a way to wipe evidence of cm of so I can get this phone repaired? To me this obviously a faulty emmc, I just can't see it being anything else.
or is it possible to boot recovery on sd like the nook?

any ideas on how to wipe cm bits atleast?

Stuck on Google Screen after flash

Hey guys. Hoping to get some assistance here. My N10 seems to always freeze on the google (with the unlock icon) screen. I was coming from Mr Robinson's Buttered AOKP 4.2.2 to PAC MAN 4.3. I performed a factory reset and formated my data. Flashed the appropraite ROM and GAPPS after which I performed a reboot. This is when it decided to freeze up. Saw this and said to myself "no biggie" and repeated the aforementioned steps again just in case there was an error on my part. After performing this again it was a success. Started up the setup procedure and began downloading TBU to restore my apps. After downloading TBU I turned it off, took a break, and about 15 minutes later, powered it back on and to my surprise it was stuck on the Google screen again. I thought maybe the ROM file I flashed was corrupted so I tried flashing CM 10.2, and a few others. Every initial boot after installation I have no problems but any reboot afterwards brings me back to the frozen Google screen. At this point I'm stuck. Anyone have any ideas? Suggestions? Any help will be appreciated.

The Google screen represents the bootloader, and has nothing to do with the ROM. Two reasons I could think of.
1. Your bootloader's funky. I find that hard to believe, but it's possible. A full factory image flash(including manually erasing the bootloader) would fix this.
2. Your partitions are funky. You may have seen/heard about issues like this from the Kindle Fires I see in your signature. If even one partition is out of place(from a bad flash or otherwise) the system will refuse to boot. It sounds like it's either the userdata(media) or the cache partition, seeing as how the system boots fine once, but gets corrupted later(when these partitions get altered). Again, a full factory flash should fix this issue.
Or it could be something really simple, but that's all I've got. I've never heard of this issue before.

Just my luck to have an uncommon issue lol. I did notice now that when I boot into the bootloader on my way to recovery it always starts being stuck in download mode and only after holding down all of the buttons does it allow me to use the volume buttons to select starting up in recovery. The tablet also doesnt want to stay shut off and immediately reboots after powering off. What you said definitely makes sense especially with the two other issues I just mentioned. Definitely wont be the quickest fix and wqs hoping that there would be a quicker remedy but off course will do it if I have to. Are the root and unlock steps similar to the methods of the earlier versions of Jelly Bean? How does one go about manually deleting the bootloader?
Sent from my SGH-I317 using Tapatalk 4

Koopa777 said:
The Google screen represents the bootloader, and has nothing to do with the ROM. Two reasons I could think of.
1. Your bootloader's funky. I find that hard to believe, but it's possible. A full factory image flash(including manually erasing the bootloader) would fix this.
2. Your partitions are funky. You may have seen/heard about issues like this from the Kindle Fires I see in your signature. If even one partition is out of place(from a bad flash or otherwise) the system will refuse to boot. It sounds like it's either the userdata(media) or the cache partition, seeing as how the system boots fine once, but gets corrupted later(when these partitions get altered). Again, a full factory flash should fix this issue.
Or it could be something really simple, but that's all I've got. I've never heard of this issue before.
Click to expand...
Click to collapse
I think I have a similar problem myself. However, my device wont boot into bootloader. It won't turn on. How would you typically do a full factory image flash if that's the case?
I also got some message when I tried to flash my device saying that it failed to update the partition table, so that matches what you just said.

I'll update this post with a guide for both of you later tonight, as I'm out of town. IBalic, try to press and hold all 3 buttons to attempt to boot into fastboot. If that doesn't work, put it on the charger for awhile then try.
Sent from my MB855 using xda app-developers app

Koopa777 said:
I'll update this post with a guide for both of you later tonight, as I'm out of town. IBalic, try to press and hold all 3 buttons to attempt to boot into fastboot. If that doesn't work, put it on the charger for awhile then try.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
That would be much appreciated. I was searching around xda earlier and came across a factory 4.3 image thread that also had a seperate bootloader zip file. I'm assuming it wouldn't be that easy but just in case I asked them if there was a way that I could just flash (recovery/fastboot) it to replace the corrupted one.

IBalic said:
I think I have a similar problem myself. However, my device wont boot into bootloader. It won't turn on. How would you typically do a full factory image flash if that's the case?
I also got some message when I tried to flash my device saying that it failed to update the partition table, so that matches what you just said.
Click to expand...
Click to collapse
Hey. I saw a similar issue somewhere else, the tablet simply wouldn't boot, the problem was solved leaving it charging for 1h, then unplugging, putting back while trying to power on and leaving overnight charging. Maybe you can try this .
Gameraddikted said:
That would be much appreciated. I was searching around xda earlier and came across a factory 4.3 image thread that also had a seperate bootloader zip file. I'm assuming it wouldn't be that easy but just in case I asked them if there was a way that I could just flash (recovery/fastboot) it to replace the corrupted one.
Click to expand...
Click to collapse
To factory reset follow this:
Download and get the factory image, I'd recommend you getting them from http://developers.google.com/android/nexus/images.
Extract it and later I'll update this post with a link to a fastboot/adb environment, that way it'll ease your life, if you want to do this now, extract the zip to your fastboot folder, plug your tablet on bootloader mode and type the following:
Code:
flash-all.bat
After that, if worked, you may got it flashed back to stock. If you're with partitions problem, then I'll think a little more and try to solve your problems for you .
Disclaimer: I'm not responsible for any damage!
Cheers,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD

XxLordxX said:
Hey. I saw a similar issue somewhere else, the tablet simply wouldn't boot, the problem was solved leaving it charging for 1h, then unplugging, putting back while trying to power on and leaving overnight charging. Maybe you can try this .
To factory reset follow this:
Download and get the factory image, I'd recommend you getting them from http://developers.google.com/android/nexus/images.
Extract it and later I'll update this post with a link to a fastboot/adb environment, that way it'll ease your life, if you want to do this now, extract the zip to your fastboot folder, plug your tablet on bootloader mode and type the following:
Code:
flash-all.bat
After that, if worked, you may got it flashed back to stock. If you're with partitions problem, then I'll think a little more and try to solve your problems for you .
Disclaimer: I'm not responsible for any damage!
Cheers,
~Lord
"We think so supersonic and we make our bombs atomic" - Eagle Fly Free (Helloween)
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I appreciate the help. I downloaded the factory image via the link you provided. When you say extracting the zip file to my fastboot folder do you mean my adroid-adb (aka. platform-tools) folder? Should I make a separate folder or just put everything in the root? Just to get the ball rolling I extracted the download to the root of the folder and ran the flash-all.bat command which started but kicked out some errors. I also noticed that the actual image is "zipped" inside the tgz file. Should I extract that as well or leave it be? Thanks

Gameraddikted said:
I appreciate the help. I downloaded the factory image via the link you provided. When you say extracting the zip file to my fastboot folder do you mean my adroid-adb (aka. platform-tools) folder? Should I make a separate folder or just put everything in the root? Just to get the ball rolling I extracted the download to the root of the folder and ran the flash-all.bat command which started but kicked out some errors. I also noticed that the actual image is "zipped" inside the tgz file. Should I extract that as well or leave it be? Thanks
Click to expand...
Click to collapse
As far as I remember the file you downloaded contains a folder with some files, if you feel more convenient copy all the files in the platform-tools to a new folder and copy also the files from the extracted download to this folder as well, then try again. If you don't get again, please send me the error report and the flash-all.bat file .
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505

XxLordxX said:
As far as I remember the file you downloaded contains a folder with some files, if you feel more convenient copy all the files in the platform-tools to a new folder and copy also the files from the extracted download to this folder as well, then try again. If you don't get again, please send me the error report and the flash-all.bat file .
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
I tried both ways just in case. One with the embedded zip file extracted and the other "as is." This is the error I'm receiving although afterwards attempting it seems everything (bootloader, recovery, etc) has been deleted just as the command prompt states but for some reason they weren't replaced by the factory items:
C:\Users\Ben>flash-all.bat
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.095s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.026s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.149s]
finished. total time: 0.150s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.456s]
finished. total time: 0.457s
error: cannot load 'bootloader-manta-mantamd03.img': Unknown error
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
error: failed to load 'image-mantaray-jwr66v.zip': No error
Press any key to exit...

Gameraddikted said:
I tried both ways just in case. One with the embedded zip file extracted and the other "as is." This is the error I'm receiving although afterwards attempting it seems everything (bootloader, recovery, etc) has been deleted just as the command prompt states but for some reason they weren't replaced by the factory items:
C:\Users\Ben>flash-all.bat
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.094s]
finished. total time: 0.095s
erasing 'recovery'...
OKAY [ 0.025s]
finished. total time: 0.026s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.149s]
finished. total time: 0.150s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.456s]
finished. total time: 0.457s
error: cannot load 'bootloader-manta-mantamd03.img': Unknown error
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
< waiting for device >
error: failed to load 'image-mantaray-jwr66v.zip': No error
Press any key to exit...
Click to expand...
Click to collapse
Hmm... Let's try doing it manually then. The partitions are already formated so it's all cool. Extract the zip, you'll get a few .img files, copy them all to your fastboot folder, plug you Nexus in bootloader mode then open a cmd there. Type:
Code:
fastboot flash bootloader bootloader-manta-mantamd3.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot reboot
If this doesn't solve the issue I'll send you a reply later when I arrive home. Thanks for the patience
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505

XxLordxX said:
Hmm... Let's try doing it manually then. The partitions are already formated so it's all cool. Extract the zip, you'll get a few .img files, copy them all to your fastboot folder, plug you Nexus in bootloader mode then open a cmd there. Type:
Code:
fastboot flash bootloader bootloader-manta-mantamd3.img
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot reboot
If this doesn't solve the issue I'll send you a reply later when I arrive home. Thanks for the patience
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my GT-I9505
Click to expand...
Click to collapse
Boom! This worked perfectly! Thanks so much for your help. I'm up and running again on PAC. Now if I can only figure out a way to restore my game backups for games that require extra downloads. Off to the forums again. Thanks again for your help :thumbup:
Sent from my SGH-I317 using Tapatalk 4

[Q] OTA Relocked Bootloader, Bricked Device

Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e94557, 2013-05-24 14:49:34)
eMC Info: Size 8GB
Device is LOCKED, Status Code 0
Battery OK
Transfer Mode:
USB Connected
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
Click to expand...
Click to collapse
Anyone got any ideas what might have caused this, and what can be done to fix it?

Leraeniesh said:
Some strange experience to report.
Flashed my unlocked (had been running CM11 beforehand) RAZR M to stock using Matt's utility (all modems, kernel, system and recovery) and everything worked fine.
After booting, I decided to accept OTA update (had done this before without any problems)
Device booted into recovery, flashed the OTA, and booted straight into fastboot, telling me my device's bootloader is now locked (status code 0) and that I can no longer use Matt's utility to flash anything (my guess is something messed up the partitions)
AP Fastboot:
Anyone got any ideas what might have caused this, and what can be done to fix it?
Click to expand...
Click to collapse
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn

ATTACK said:
Try flashing each file through Mfastboot.
Code:
mfastboot flash partition gpt_main0.bin
mfastboot flash logo logo.bin
mfastboot flash system system.img.ext4
mfastboot flash boot boot.img
mfastboot flash fsg fsg.mbn
Click to expand...
Click to collapse
When flashing anything via fastboot (or mfastboot)
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32KB)...
OKAY [ 0.074s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.383s
Click to expand...
Click to collapse

Leraeniesh said:
When flashing anything via fastboot (or mfastboot)
Click to expand...
Click to collapse
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.

ATTACK said:
Have you tried RSDLite? What version of firmware are you flashing? It looks like you flashed a downgraded GPT partition.
Click to expand...
Click to collapse
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
EDIT: Was able to get it to flash using HouseofMoto's RSD XML.
All good

Leraeniesh said:
Have also tried RSD Lite (5.6 and 6.1.5) with similar results
I just flashed the OTA that VZW sent my way.
Click to expand...
Click to collapse
And you tried to restore 98.30.1? I know with the leak, it is a two part flashing process. It will reboot after part 1, then you need to reboot into recovery to start part 2. You may need to wait until there's a FXZ to fix it.

This is scary. Ive just RSD'd back to stock and am about to update my phone with all the OTA's. Perhaps ill stop for now.
EDIT: And the OTA process just failed from Stock update. FML.

Maybe try this? This is sourced from Moto's website
https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/91999/p/1449,8620

If anyone else experiences something similar, you can follow jimyv's post regarding setting up RSD to flash (despite something going wonk with the partition table)

I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated

techfellow said:
I am having this same issue, I tried the house of moto tutorial and my result is everything failed. Any other suggestion will be greatly appreciated
Click to expand...
Click to collapse
How did "everything fail?" Just need more details.

xKroniK13x said:
How did "everything fail?" Just need more details.
Click to expand...
Click to collapse
I've been trying this for the past 2 days. I just tried it again so I can give you details, and it worked without any issues, so I'm good.
Thanks to all the previous posters, and the house of moto maker.

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

Moto Z 8.0 Full firmware [stock][oreo][griffin]

Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.

Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time

K1li4n said:
Hey, thanks for the tool, just few questions, will this relock my device bootloader ? and am i taking the risk to hard brick it ? Do i need to have adb and fastboot installed ?
thanks for this tool and for your time
Click to expand...
Click to collapse
No relock anything. No risk to hard brick. If you flash down to 711 and then OTA update,it will. No need adb and fastboot install. Install usb and motorola driver

thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?

thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and the phone went back to encrypted mode again, TWRP is not working any more and root access is gone..Any way to revert back ?

K1li4n said:
thanks for the quick answer. no relock, so if something go wrong i would still be able to flash some custom and rsolve the issue , right ?
Click to expand...
Click to collapse
Yes,sure.

[email protected] said:
Hi, at the end of the batch say
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
So all data will be erased ?
BTW, I ran the process and th phone went back to encrypted mode again
Click to expand...
Click to collapse
Yes,it will erese all.

thuybang said:
Yes,it will erese all.
Click to expand...
Click to collapse
And we lose custom recovery and root asscess

my phone reteu dual sim not retail can i flash this rom ?

t_assal said:
my phone reteu dual sim not retail can i flash this rom ?
Click to expand...
Click to collapse
If you unlockbootloader, i can say : yes.

Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?

lima002 said:
Nice it works to me ,
I just wanted to know if now im stock with unlocked bootloader , so no updates ? Like security updates ?
Click to expand...
Click to collapse
Unlock bootloader always get update as normal,guy. . Any update, security,system....

thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
Cool thanks

Thanx for this, updates working and all.. Only the wifi seems to be be working bad (no internet access, disconnecting) , although could be my connection..

Hi, can I flash 1650-05 retcn Android 7.0 with an unlocked bootloader on this firmware?

it should work on xt1650-03?
btw, my carrier is tefcl but i think that isn't important for flashing

thuybang said:
Many thank @erfanoabdi for the link
https://androidfilehost.com/?fid=890278863836283516
extract ROM ,extract file attack ,put all to the same folder, (hold power + volume down to get into bootloader mode) and run file: retail_AS_800.bat ( no need to run commands)
Done.
Click to expand...
Click to collapse
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot flash system system.img_spar
sechunk.14
target reported max download size of 536870912 bytes
sending 'system' (151532 KB)...
OKAY [ 4.038s]
writing 'system'...
(bootloader) Invalid sparse image data
(bootloader) Failed to flash sparse image
FAILED (remote failure)
finished. total time: 4.786s
Click to expand...
Click to collapse
And error on erasing DDR
C:\adb-fastboot-latest\adb-fastboot-latest>fastboot erase DDR
erasing 'DDR'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.035s
Click to expand...
Click to collapse
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.

mike331967 said:
I try to flash it, but where is error on system.img_sparsechunk.14 flashing..
And error on erasing DDR
Phone now in boot loop. Can't start, but goes to fastboot.
How to flash it correctly.
Click to expand...
Click to collapse
Can you try flash by RSD lite 6.2.4sofware?

thuybang said:
Unlock bootloader always get update as normal,guy. . Any update, security,system....
Click to expand...
Click to collapse
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.

Ceptoz said:
i got notification about security update (patch may 2018) but error while instaling. any solution? please help.
Click to expand...
Click to collapse
Same here.
Help!