Database Develop

Help me please! 0x56

Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English

Well you tried to flash a rom through stock recovery with a locked bootloader. Not the best decision. Go look at the tutorial in general.
Sent from my PACMAN MATRIX HD MAXX

iv-med said:
Good people, help:
Trying to install a mod from the camera of Nexus, rebooted, I see the icon lying android.
Tried to install xenonhd (4.2.2), reboot, and see the inscription on a black background:
Device is LOCKED. Status code: 0
Battery OK
Connect USB
Data Cable
failed to hab check for boot: 0x56
fastboot reason: boot failure
Please help me!
Sorry for bad English
Click to expand...
Click to collapse
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.

skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
i have the same problem but flashing back to stock rom with rsd will not work
I get a 1/23 partition type erro
and myth will now work due to fastboot, adb and attrib is not known as and internal or external command

skeevydude said:
Flash your stock rom with RSD....about all you can do.
Not true, but I'm not gonna write up a tutorial on how to dd back to the correct bootloader or make a stock bootloader in a flashable zip, etc. Not when the solution is plug phone into PC, Open RSD, click, click, clickity, click, reboot, and done.
//Unlock your bootloader and you won't have issues like this. If you don't wanna do that, ya gotta use the old roms, all the new ones are for unlocked devices.
Click to expand...
Click to collapse
Having this same problem when trying ota Kit Kat update from T-Mobile. The only way I can get back into 4.2.2 is to use Minimal Fastboot and give the command 'fastboot erase cache'. Even when I do this the phone never says if the cache erasure is complete but Minimal Fastboot says that it is. I have RSD lite installed on my CPU but can't seem to find a working link to the stock T-Mo images. Any help would be appreciated.
Just to add...if I attempt ota I get 'failed to hab check boot'. When trying to boot into recovery I get 'failed to hab check recovery'.
Edit: could I just unlock and root to solve this problem? If so, would someone point me to a different method than the Moto Toolkit found here? It doesn't recognize my moto even though all drivers and Motorola Device Manager are installed.
Sent from my XT1053 using Tapatalk

Ota KitKat update?
What phone do you have?

I have the T Mobile motomaker. Solved the problem with RSD Lite and factory Kit Kat images.
Sent from my Galaxy Nexus using Tapatalk

Helo! MotoX might be bricked.

Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.

shartwell said:
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
Click to expand...
Click to collapse
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X

flashallthetime said:
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!

shartwell said:
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
Click to expand...
Click to collapse
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X

flashallthetime said:
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.

Follow what flashallthetime is suggesting.
btw, Rogers firmware is correct for your phone as there is no Fido specific firmware.

shartwell said:
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Click to expand...
Click to collapse
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X

flashallthetime said:
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
Click to expand...
Click to collapse
Getting somewhere...
The command prompt can seemingly now interface with my device. It runs commands but clearing the cache didn't fix the problem. I've ran the command though so if there is a next step...
EDIT: Okay it's charing and I can interface with it via cmd. I can now use RTDlite with it as it's battery is charging. Should I flash the other Rogers now? I have my unlock code for the bootloader if that's what I've got to do first.

Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA

Steve-x said:
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Click to expand...
Click to collapse
It's all fixed up. Thank you everyone who contributed to this! Time to enjoy my phone.
Last thing would be flashing twrp. Does someone have a link to the proper files?

Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X

flashallthetime said:
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
Click to expand...
Click to collapse
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?

shartwell said:
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
Click to expand...
Click to collapse
Here's twrp http://forum.xda-developers.com/showthread.php?t=2458449
Flash with fastboot( fastboot flash recovery twrp 2.6.3.IMG)
Place the recovery image in platform tools folder. After it flashes make sure you go directly to recovery by pressing the volume up bottom to make it stick
Sent on my Moto X

[Q] Wiped system by mistake, now i'm stuck at loading screen...

After flashing my xt1058 with a custom ROM (Eclipse), i realized my phone was having some issues.
So i tried to factory reset it. I accidentally wiped system (TWRP) and now i'm currently looking at the loading screen. It just stays there, white with the moto logo and nothing happens. I tried running 'Factory' in fastboot too, but nothing changed.
Can anyone help me to restore my 4.4.2?
Hope i haven't bricked my phone. Fastboot shows no errors.

You probably will need to rsdlite or fastboot back to stock 4.4.2 image.....IF its available yet for your phone.
Sent from my N5 cell phone telephone....

kj2112 said:
You probably will need to rsdlite or fastboot back to stock 4.4.2 image.....IF its available yet for your phone.
Sent from my N5 cell phone telephone....
Click to expand...
Click to collapse
It is available. I was running Kit-Kat, but i decided to mess it up and to use a new rom I'm yet to try RSD Lite though...
Let's see if i'm a lucky man

same situation, same screen, help please?

ericizzy1 said:
same situation, same screen, help please?
Click to expand...
Click to collapse
RSD Lite did it for me. Download the 6.1.6 version along your retail rom and follow these steps here:
http://wccftech.com/steps-to-restor...lite-att-sprint-t-mobile-us-cellular-verizon/
Note: If you can't get adb to boot to bootloader, just use the common method, down volume+power buttons.

fastboot flash system system.img
or
In TWRP with sideloading activated: adb sideload rom.zip

i think i bricked my moto- please help me decide

the first question:
From fastboot, (or mfastboot,) I'm attempting to write and reflash my system. Would cyanogen mod have named the partitions anything other than what they are?
(example of command i attempted : mfastboot format system
Mfastboot replied something about variables, and system not being one of them)
Can someone tell me how to get a sort of cm11 device map, or diagram with all partitions and file path names?
So how did i get here?
I was running low on storage and decided to stop by my buddies place to use his pc and clear some space in my device. (recently unemployed, evicted, completely screwed, yea- REALLY.) Quickly after i plugged into the pc i had to unplug for a moment so i just pulled the usb cable from the port, like i have done many times before, bypassing the pc's directions to disconnect first... Immediately my phone started boot-looping only the "bootloader unlocked" screen over and over... The first thing i attempted to remedy the situation was hold the power button for 10 seconds in an attempt to restart the device. When it began doing things the same way, i went to recovery, via fastboot, and attempted to 'install zip from sdcard'. The reply was that recovery couldn't mount storage. I tried to reboot recovery and try again but got the same result. Next i rebooted to recovery and attempted to factory reset but it froze recovery after i confirmed the command. Had to hold power + volume down for 10 seconds and let it reboot to fastboot, choose recovery, then mounts/storage, format system, and that froze recovery again, so, now I'm realizing that recovery is broken.
I hooked up top the pc and went to fastboot mode, made sure my device was recognized, then read up on some commands, because, honestly, I've rarely used it outside of doing strictly what some tutorials told me to do. (Although, the last time i had to use it, i had great success using minimal reference and mostly luck, i saved my moto x from what i thought was certain death.)
Unfortunately, this time, I'm pretty certain. But at the same time- i can get to recovery, that's a great sign, right? To me, it means it's not dead yet!
First i used fastboot in an attempt to format the caché, just to 'feel it out.' I wish i could remember what it told me, but the gist of it sums up to the cache being erased, but the rest if the reply was negative.
I tried similar commands from formatting the system to the recovery in order to rewrite the recovery image, but no luck there... All commands give me responses regarding variables or they are bring denied by the device, which brings my next question, (which is not a cm question, but a general one... I only ask here because i began this post with a question regarding cm)
When a moto x with an unlocked bootloader boots to AP fastboot, at the end of the first line at the top there is
(S)
I believe on my past rooted devices that either (S-ON) or (S-OFF) would be there regarding their status as superuser.
With my device displaying only ' (S) ' in this place, does that indicate that I've lost superuser privileges our anything at all, for that matter?
I am so lost, friends... That device is everything to me, even without cellular service, when i get close to wifi, i contact my family, look for a job, read, and keep up with my medical requirements.
As i live to say at this point, any and all info and input will be greatly appreciated!!!

If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk

Joseluize said:
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
That's such good news! I'm not familiar with rsd, though. What is it all about? And no, I didn't try stock firmware...

Here's the solution.
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Thanks to @TechSavvy2 for his guide.
Enviado desde mi XT1053 mediante Tapatalk

Have you tried mfastboot or fastboot erase instead of format?

Joseluize said:
If you can enter to recovery or fastboot mode your phone isn't dead. Have you tried to flash the last STOCK FIRMWARE that you installed? Whit RSD. There is no problem if you've lost root privileges while BootLoader doesn't says "Device Locked".
You can save your phone. Good luck!
Enviado desde mi XT1053 mediante Tapatalk
Click to expand...
Click to collapse
I've seen you help several users now by directing them to the "Return to Stock" thread. Excellent advice - thanks for helping out!!!!
Just FYI, you can flash the STOCK firmware even with a locked bootloader as long as it is the SAME firmware that came on the phone. This is because the stock firmware is signed with release keys, and the CID will match.
The only reason you need to unlock your bootloader to flash a STOCK firmware is if you are flashing a different carrier's firmware (which we don't recommend).

samwathegreat said:
I've seen you help several users now by directing them to the "Return to Stock" thread. Excellent advice - thanks for helping out!!!!
Just FYI, you can flash the STOCK firmware even with a locked bootloader as long as it is the SAME firmware that came on the phone. This is because the stock firmware is signed with release keys, and the CID will match.
The only reason you need to unlock your bootloader to flash a STOCK firmware is if you are flashing a different carrier's firmware (which we don't recommend).
Click to expand...
Click to collapse
Thanks! I am helping because I bricked my phone recently and I don't want that people do the same. I can't write too much (yet). My main language is Spanish and I'm just an English trainer. Greetings!
Enviado desde mi XT1053 mediante Tapatalk

[Q&A] [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition

Q&A for [Pure Edition][Root] Superboot style root for MotoX 2014 Pure Edition
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

MotoX Pure - UnRoot To Update Firmware
I used the Jcase method (fastboot boot pure2014sb.img) to root my new MotoX Pure. Worked great. However, the next day I received a notification on the phone that a firmware update is available: "New FIrmware Available" "Update to get the lastest Motorola Sensor. . ."
Because this method uses fastboot boot vs fastboot flash, I don't understand how I can go back to stock in order to update firmware.
Wondering if someone could school me on what the heck it actually means to fastboot boot vs fastboot flash. Basically looking for a way to be able to un-root, apply firmware update, and then re-root.
A

You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk

tyea said:
You need a factory image to flash using Motorola's mfastboot to get back to stock. Motorola has not posted a factory image yet, but they said they would.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
if they said they would, then i'm glad. getting worried here lol

root moto x 2014 followed by ota lollipop update
The moto x is delivered with KitKat initially and then updated via ota later once powered up etc. If I follow your method as soon as I get the phone and then later accept the ota update to lollipop, will it cause problems or lose root?

bootloop
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me

deelv said:
i tried to root my phone and i followed every step but now i am stuck in a bootloop. what do i do? please help
---------- Post added at 06:27 AM ---------- Previous post was at 05:53 AM ----------
I tried to root my moto with this method and now i am stuck in a bootloop. i followed every step including the fastboot boot. please help me
Click to expand...
Click to collapse
The same thing happened to me but I've gotten out of the boot loop by getting to fastboot (hold down the power button till the screen turns off and then you have to guess and hold the power and volume down button for about 5 seconds and then release the power button but hold down the volume button until you see the fastboot. If it doesn't get to fastboot try it again.)
When you're at the fastboot, connect to a computer and cmd a command "fastboot erase userdata" and then "fastboot erase cache" to pretty much factory reset and get you out of the boot loop. Then it should boot and tell you to set up the device.
I would recommend looking for the root boot image from chainfire them self, they recently released it. Just look for your model # (e.g. xt1095) and "fastboot boot (insert boot image)"
My Moto x 2014 is currently rooted with chainfire's boot image. It works like a charm.

XT1092 bootloop after OTA
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers

HamRack said:
Hi,
Got my XT1092 and unlocked the bootloader and gained root using this method a while back, no problem there.
Downloaded and installed the OTA update to lollipop and went about reinstating the root access using this method. Subsequently have been stuck in a bootloop and have been unable to find a stock image to repair this with.
Does anyone have a suggestion on how to fix this?
When I have tried using
fastboot boot *whatever stock image I have found*
I get a little droid with a red exclamation mark with 'NO COMMAND' underneath.
Any suggestions of how to fix this/what I can boot/flash that can fix this?
Cheers
Click to expand...
Click to collapse
Boot this boot.img : http://forum.xda-developers.com/moto-x-2014/general/lollipop-root-achieved-t2937154
Its for xt1095 but some have confirmed working on xt1092
Sent from my Moto X 2014 Pure Edition

does it work on Android 5.0?

Yes, I'm currently running Android 5.0 Lollipop.
Sent from my Moto X 2014 Pure Edition

Bootloop
Stuck in a bootloop. Followed all your instructions carefully. :/ Not able to boot into bootloader.

Formatted Telus Moto X (2014) SD card and all data ... recovered.
I might make a tutorial video on how to recover from a mistake like mine, and I may not have done it correctly, but the phone is back operational.
What I did to screw it up :
1) Unlocked the bootloader and installed TWRP without doing research about development for the phone
2) The phone is already almost stock android and that's one of it's selling points so I don't know why I wanted to unlock and root
3) Got frustrated and wiped / formatted internal SD ... since I use to flash ROM's on my older Huawei this way ... it must be the same right ... smh.
4) Freaked the eff out, had thoughts of just running it over with the car because that qualifies under my 2-year warranty, since I voided it by unlocking.
5) Thought I knew it all when I really don't understand most of the lingo still
What I did to 'TRY' to fix it :
1) Scoured the internet for ROMS / Zips.
2) I was in 'Android Studio' ... unnecessary.
3) Tried flashing .zips in TWRP by draggin and dropping .zips ... contanst 'FAILED' signs.
4) Tried sideloading as I was grasping at straws by this point. 'FAILED'
5) Considered buying an OTG cable.
6) Spent hours going in circles
What I did to fix it :
1) Downloaded the SDK ... 'adt-bundle-windows-x86_64-20140702'
2) Installed the 'Google USB drivers' as I checked 'Device Manager' and there was an exclamation ... this is why when I went typed 'ADB devices' nothing showed up. I 'manually' installed the drivers. VOILA, first step.
3) Found a .ZIP file I believe was the correct one ... ;RETCA_XT1097_4.4.4_KXE21.187-42_cid14_CFC.xml.zip' (From this website I believe)
4) Watched a few youtube tutorials on how to flash from within 'SDK' > 'Platform-Tools'
5) Extracted the .ZIP file into 'Platform-Tools'
6) Had phone booted into fastboot mode
7) Opened the CMD from within 'Platform-Tools' with that .ZIP file within that folder, held 'SHIFT' 'Right-click" > 'Run CMD'
8) This is where I didn't do it properly, but the phone is booted for now and working ... with these Commands
- fastboot flash boot boot.img;
- fastboot.exe flash system system.img_sparsechunk.0
- fastboot.exe flash system system.img_sparsechunk.1
- fastboot.exe flash system system.img_sparsechunk.2
- fastboot.exe flash system system.img_sparsechunk.3
- fastboot.exe flash system system.img_sparsechunk.4
Got that nice Motorola earth screen and booted to the welcome screen. Froze. I reset. Froze. Walked away from phone, came back and tried to see if I could press 'OK' and it worked.
All-in-All , not worth it for the average consumer and not worth it for someone such as myself who was stupid and just wanted to 'play around' with a brand new 2-year warrantied $500 phone.