Database Users

[Q] MT3G 1.2 -the process android.process.acore has stopped unexpectedly at startup

Hi,
I have a tmobile mytouch 3g 1.2 (3.5mm jack phone). I tried to root my phone and it failed during the SYSTEM---UnZipping process. (it stuck there forever). I then looked at options of unrooting it. When I apply SAPPIMG.zip it says Main Version Older! Update Fail!
Then I reboot the phone in recovery mode (tried to reset to factory settings and then reboot). The phone gives me the below error upon startup. The only thing i can see is an notification bar.
the process android.process.acore has stopped unexpectedly. "FORCE CLOSE"
Please can someone help me how to get my phone working? Appreciate all your help!

If you go to tmobile.com then go to there forum under android development you will see a topic called how to unroot the mytouch. In that topic they have a link for the original sappimg .. download to your zip cars in the root of the card (no folders) then just boot into hboot and apply the sappimg. I have done it many times so I know it works. Then when you go to root your just us the universal androot method. Feel few to pm me i
ent from my HTC Magic using XDA App

Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)

I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.

mumilover said:
Type this in fastboot:
Code:
fastboot getvar version-main
Then we can try to see if we can update it.
If not, you can always try to flash RUU.
The system starts, that's a good thing -> you have adb access!
Just don't go around and flash all kind of sapphire.nbh/zip...
Wait intil you have the right info :0)
Click to expand...
Click to collapse
I tried the command - fastboot getvar version-main
it just says < waiting for device > and then nothing happens...
also when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...) can this number be used in any manner for anything

housry23 said:
I have had this problem and solved it. I would either get this acore stopped working error or just a loop in the boot screen. I think what caused this is there is not enough internal room for the ROM and gapps. Make sure you wipe everything. Do you have a nandroid backup? Can you get into recovery? Which recovery do you have installed? Do this, make a goldcard. Use fastboot to reroot the phone because you may have halfway unrooted it and made root useless. Boot into recovery and wipe. Install from sd any MyTouch ROM without Gapps. This should get you into the OS and now you can use other methods of getting your phone back. When I got here I used nandroid backup to get my phone back to a date it was when it worked and have had no problems since.
Click to expand...
Click to collapse
i did not take any nandroid backup ...i got into revovery boot...but whn i did the wipe clean option and reboot i get this error.
to make a gold card i would need to have the USB debugging enabled right? I am not able to go past the error screen (Home does not work, settings does not work )
and when i run the adb devices command, it does not display my devices. (But i have the number noted down when i tried to root the phone which failed...)
is there any other way to enable the USB Debugging as I am not able to open settings or even see anything on my phone...?
Would there be any option that's something like doing a System Restore to an earlier date on Windows OS on the computer?
please let me know the next steps...appreciate all of your help...

It's driver related.
Fix the drivers and try again to run the commands.

mumilover said:
It's driver related.
Fix the drivers and try again to run the commands.
Click to expand...
Click to collapse
You mean re-install the USB drivers for mytouch 3g? i tried that but still nothing happens...

Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...

mumilover said:
Well you have to...
In fastboot mode this command shall give you the device nr .
Code:
fastboot devices
If not, the drivers are still bad!
You could also try to do a HARD RESET from hboot ( volume - together with power)...
Click to expand...
Click to collapse
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?

ganesh.raj.ms said:
Thanks for the steps. I got the version details.
by executing the fastboot getvar version-main in fastboot mode.
version-main: 2.53.707.2
finished. total time: 0.001s
What will be the next steps...how to I update?
Click to expand...
Click to collapse
Hey, i tried the below. can you please let me know if this is correct? and what do i do next?
userdebug-img-14721_1.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 1.33.0013
Baseband Version.....: 2.22.23.02
Serial Number........: HT03TPB01582
--------------------------------------------
checking product... FAILED
Device product is 'sapphire'.
Update requires 'trout'.
finished. total time: 0.042s
how do i try to rectify the checking product...FAILED???

OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...

mumilover said:
OK....
Let's get the facts right.
You tried to root with wrong guide.
The sapphire.zip/nbh image you used if for the 32A.
How do i know that ?
Well the main version nr tells me that you have flashed this:
2.53.707.2 SEA WWE test-signed (from this page: http://forum.xda-developers.com/showthread.php?t=659403)
That's why you have troubles!
The solution....
I need all your fastboot info.. ALL.
Then i can figure out what to do. Or else i will work in the dark...
Click to expand...
Click to collapse
Is it the below that you want?
[FONT=&quot]SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-2.22.23.02
Oct 21 2009,22:33:27[/FONT]

Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices

mumilover said:
Yes...
You have the right radio/spl combo. That's good.
The problem is that your main version is set to high.
If you try to flash any RUU for the 1.2 magic, you will get main-version older error...
Even if you use a goldcard.
Do you still have access to adb?
Even for a little... then we can flash a custom recovery and get the system back.
Even if your system don't start up... as long you can boot more then 20 sec and you don't get reboots.
If not, then we have to flash a 32A sappimg.zip using a goldcard.
From there we flash custom recovery. Then eng spl. Then flash system,boot, userdata. Then flash the 1.2 spl... Then we are done :0)
So it's a long one... but first test if we have adb access.
Code:
adb devices
Click to expand...
Click to collapse
adb devices does not give me anything...its not working

Does the computer recognise the device?
Maybe it's driver related...
PS: check your pm

[OFFICIAL STOCK.IMG] WIFI ONLY MZ604_HWI69 - Official Motorola software

The files were posted today. Remember to grab the MZ604 files if you have the Wifi only version of the Xoom.
http://developer.motorola.com/products/software/ <------ Grab the files here. The files are for the US version of the Wifi Xoom only.
Instructions to return it to stock
1) First you need the Moto Drivers - Read this thread to START you - http://forum.xda-developers.com/showthread.php?t=981578
Should have these drivers installed if you have rooted your Xoom before.
2) Make sure you have the latest SDK - adb and fastboot should be in /platform-tools - http://developer.android.com/sdk/index.html
Should have the android SDK if you have rooted your Xoom before.
3) Place all the downloaded stock image files into the SDK Tools folder.
4) If you are booting up from scratch, you can get the Xoom in fastboot mode by doing the following. Use command prompt to perform the rest of the steps
Hold VolDown and Power button will boot unit for fastboot mode
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
If you Xoom is booted up already follow the commands below using command prompt to perform the steps
adb reboot bootloader <---- reboots the Xoom into fastboot mode.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

You noticed this too I see. Glad you posted this as a new thread. I was just randomly posting that link in threads where stock images may have helped.
I'm not home to try it yet but I'm guessing that's a US image?

Ahhhhh finally.

i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!

vista64 said:
i just followed this process, everything worked on the xoom wifi (US), im back to stock and everything is ok so far.
but im an idiot and pressed vol up instead of down on the last step (oem lock) which aborted the oem lock step. before i did this i was rooted, so i think technically im still rooted.
can i simply go back into fastboot oem lock and try again and press the rightbutton this time to re lock the xoom or would that brick it?
ok thanks guys!
Click to expand...
Click to collapse
If you want to be extra safe, start over from the beginning. You're probably still unlocked (but not rooted) if you managed to flash boot and system.

i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??

DinarQ8 said:
i have error failed to boot lnx 0x0004 - starting rsd mode 2
can i use this file ??
Click to expand...
Click to collapse
Only if you can get into fastboot mode AND your computer can see it. But if I recall, neither ADB, Fastboot nor RSD Lite will see your Xoom?

maybe solution i wait SBF file

Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody

what he said ^

Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...

If i remember correctly, scourge said that both devices are exactly the same hardware. Therefore flashing either version's set of images is irrelevant as long as you do WIFI for that model and 3G for that one.

odyseus said:
Hi Scourge1024,
Are you going to try and flash the images to your Canadian Xoom AND then see if you can OEM re-lock it again??
I haven't been able to find out if all the WiFi images ie US, Canadian or European are all interchangeable on a Wifi only xoom??
I guess what I'd like to know is, if I ever wanted to re-lock my UK xoom, could I simply flash the Motorola MZ604_HWI69 files, then oem re-lock OR would have to wait for European Motorola backup files?
Cheers
Ody
Click to expand...
Click to collapse
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.

Scourge1024 said:
Just tried downloading the Wi-fi files... On both my Mac and PC, it's saying it can't extract the ZIP. Crap crap crap crap crap...
Click to expand...
Click to collapse
FYI,
$ md5sum MZ604_HWI69.zip
ae9b9f5693c4b49c745cb017afe1a4b5 MZ604_HWI69.zip
$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip
You might be OK if you can get something that'll handle errors better.

In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Code:
mac-mini:mz604_img Howard$ md5 MZ604_HWI69.zip
MD5 (MZ604_HWI69.zip) = ae9b9f5693c4b49c745cb017afe1a4b5
mac-mini:mz604_img Howard$ unzip -t MZ604_HWI69.zip
Archive: MZ604_HWI69.zip
warning [MZ604_HWI69.zip]: 36325409 extra bytes at beginning or within zipfile
(attempting to process anyway)
testing: MZ604_HWI69/boot.img OK
testing: MZ604_HWI69/recovery.img OK
testing: MZ604_HWI69/system.img OK
testing: MZ604_HWI69/userdata.img OK
No errors detected in compressed data of MZ604_HWI69.zip.
mac-mini:mz604_img Howard$

Scourge1024 said:
In Windows, WinRar worked. On my Mac, I did what you posted and well, it seemed to work. I also did a compare against BeagleBoy's ripped images and boot was perfect. System was 1 byte off. Maybe a counter for the file system being mounted?
Click to expand...
Click to collapse
Yep, IIRC, ext maintains a mount count. One'd need some file system tools to properly verify.

Can someone post a walk through on how to do this?

pricej636 said:
Can someone post a walk through on how to do this?
Click to expand...
Click to collapse
from the op:
Instructions to return it to stock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock

Scourge1024 said:
Nope. I'm done being the guinea pig (with the OEM locking). I bricked my first Xoom trying to OEM lock it. I managed to lock it a few times. Then I tried a different boot.img and bricked...
Personally, I have no issues flashing the US image on. It's just the re-locking. There's really no point to relock it. The Americans with the 3G/4G Verizon ones had to be able to relock for a hardware upgrade. I have managed to flash US images onto my Xoom but they were extracted by BeagleBoy here. I posted a comparison here: http://forum.xda-developers.com/showthread.php?p=13070124
The software is interchangable between the MZ604 Xoom models (Wi-fi only). There are a bunch of other Brits using the Canadian images I extracted from me and my friend's XOOMs. I've used the US ones. You just need to do a "fastboot -w" after flashing both the system and boot images because going between versions sometimes requires userdata to be wiped.
Click to expand...
Click to collapse
Fair do's - I don't blame you! You've done enough As you say why re-lock on WiFi?
What I would really like to do is flash all the images to my UK WiFi Xoom and then try to install Bignadad's BigDX Xoom|Zoom Theme..
Previously flashing this theme soft-bricked my UK xoom - got loads of Force Closures. Installing the extracted images from you, still caused the same problem. Maybe it only works on the US WiFi Xoom, but I might re-flash with 'stock' ROM to see if that makes any difference? (I do have CWM nandroid backups in case of another soft brick!)
Cheers
Ody

Is there a risk with using these cause of zip extra bytes warning?

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

Meizu PRO 5 bootloop no recovery locked bootloader

Hi all,
I am in trouble with the PRO 5.
Actual situation:
No recovery mode available
The phone boots but when is time to go in the home screen, the screen becomes black and only the power button response so I only turn it off or restart.
Fastboot mode available but the bootloader is locked
I tried many time with the Multiupgrade tool and TestPCTool but the answer is "Token sign failed"
Could someone help me before to put the phone in the trash

Upppppp!!!!!

You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/5376/meizu-pro-5-have-rooted-rom-but-lost-recovery-phone-can-boot-pls-help

Daniel Abrecht said:
You could try to unlock it using "fastboot oem unlock", but if it works it probably wipes the userdata partition, and it may fail. If you manage to unlock it, just reflash the stock image, but without the bootloader.
If this doesn't work, there is a similar thread in a different forum which may help you:
https://forum.meizufans.eu/topic/53...rom-but-lost-recovery-phone-can-boot-pls-help
Click to expand...
Click to collapse
I know the italian guy of this 3D and I can tell u, "fastboot oem unlock" doesn't work unfortunately :crying:

Thanks Pycon.
He is right, no way to unlock the bootloader, at the moment

just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678

tzzzz said:
just try this. good luck man. http://forum.xda-developers.com/meizu-pro-5/how-to/meizu-customer-service-flash-tools-save-t3447678
Click to expand...
Click to collapse
Thanks but tried many times: Token signature fail...

Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?

st0rm77 said:
Have you tried flashing the whole system (20150923195421_demo_prd_stable) as described in the M86 firmware upgrade tutorial.pdf ?
Click to expand...
Click to collapse
Where is that tutorial?

DarginMahkum said:
Where is that tutorial?
Click to expand...
Click to collapse
It resides in the Meizu Tools post, but never mind that. I dove into the security and fastboot uses secure boot so unless there is an exploit your stuck.
Are you able to flash the boot partition ?
If so, you might be able to flash the recovery.img onto the boot (bootimg) partition. Then drop an update.zip into the root of userdata and reboot.
Good luck.

Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:

st0rm77 said:
Hey Grumpy,
I extracted the kernel and ramdisk from the recovery image (flyme_5.6.1.19_daily). Unpack these files into a directory, then run
# fastboot boot kernel ramdisk
If it boots you can:
- erase to factory default
- maybe ?? flash /sdcard/update.zip ??
Good luck :good:
Click to expand...
Click to collapse
Nope...
creating boot image...
creating boot image - 15699968 bytes
downloading 'boot.img'...
FAILED (remote: permission denied!)
finished. total time: 0.000s

Phone stuck on Essential Logo (Powered by Android) screen while trying Oreo B2 OTA

I have tried everything to get this phone to boot up. I was downloading the Oreo B2 via OTA, not sideloading. While the update was installing, I went about my business. I walked away for a few minutes and came back to a phone that just sat at the boot screen. I let it sit for about an hour, thinking that was some how normal. After an hour, I hard powered down and it came back to the same screen. I have rebooted at least 50 times now with no luck.
I can boot into fastboot, but not recovery. If I try to go into recovery, it goes to the boot screen and sits there. I have tried to switch partitions, it is stuck on A, without luck. The bootloader is locked and I can not remote unlock it via fastboot. Nor can I manually change the boot partition to B.
I have an open ticket with Essential, but they have been blowing me off and basically told me I'm out of luck since I was in their Beta program. They told me to go to XDA. A$$wipes! Any help you can offer is greatly appreciated since I'm stuck with a bricked phone and having to use an old iPhone since I cannot be without a phone.

Exact problem happened to me last week and a very helpful XDA member saved me.
Just hook up phone to pc by adb, type in 'fastboot devices' (while in fastboot mode) and install 7.1.1 os again. You'll lose everything but at least you won't be softbricked anymore.
Edit: sorry, just read you do not have unlock bootloader so this probably won't work.

Have you tried wiping data in while in fastboot? That might get it to boot.
Sent from my PH-1 using Tapatalk

You don't need an unlocked bootloader to sideload the install (following the BETA instructions: https://www.essential.com/developer/beta-builds
Since you can use fastboot, it looks like you have working ADB environment, so you should be able to follow those instructions. The STOCK recovery works very differently than TWRP, so make sure you follow those intructions, particularly the "Apply update from ADB" part. It took me a while to understand this, especially because the type on the screen is so tiny, I couldn't tell any words were changing.

I'm having the same issue (stuck on the boot logo "powered by android" screen) and I can get into fastboot mode, however if I try to go into recovery mode it just gets stuck on the boot screen again.
When in fastboot mode, the device state is "locked" is there any ways to get this fixed?

You could try: (you will lose all your data)
fastboot -w
fastboot reboot

ilpolpi65 said:
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Here's what I've got
Code:
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
It's still having the same issue..

update im still stuckk

Have you tried booting to bootloader and mounting /system?

This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.

I also have my phone stuck The bot is closed and I can not do anything
V0idst4r said:
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
Click to expand...
Click to collapse
I also have my phone stuck
The bot is closed and I can not do anything

Same here
It can't get passed the logo and I can't get any command in adb to go in fastboot. And recovery is a no go. Yay

Ph-1 stuck at boot, bootloader locked
kuyzz said:
update im still stuckk
Click to expand...
Click to collapse
We're able to fix the issue???