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

[Q] Continuous reboot after 4.2.2 downgrade

I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.

UberSprode said:
I tried following this guide to downgrade to 4.2.2 so that I could root my AT&T device.
I was able to adb and fastboot into the device. And I flashed the ATT CU update with fastboot.
After that the device constantly reboots after reaching the M logo screen,
I can boot into the bootloader, and I can send fastboot commands, but not any adb commands.
I also cannot load any of the options in the bootloader (Recovery, Factory, etc), they simply reboot the phone.
I don't care what version of Android I go to as long as it gives me a working phone. Please help!
Thanks.
Edit: I was able to recover my phone by flashing the 4.4 update. I would like to know where I went wrong, so that I could possibly still do the downgrade>root>upgrade path.
Click to expand...
Click to collapse
You know there's a way to unlock your bootloader for $43ish. Many success stories. Your phone playing life would improve greatly.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....

[Q] 1092 TWRP on 5.0 bootloop, stuck in recovery [SOLVED]

Hi,
I was on 5.0, running stock recovery and rooted. Today, installed TWRP for 5.0 on my device. I tried to flash the droid command center widget on my phone usng twrp, and it failed. I also hit the fix permissions option. After that the phone does not boot up, simply flashes the unlocked bootloader sign and shows the moto boot animation for a second or two before shutting down.
I can boot into recovery, and the computer detects the phone. But adb doesn't detect the device. I have the 1092 5.0 OTA on my computer and saved it on the phone in an attempt to flash it thru TWRP, but that failed with the message shown in the img attached. I also tried flashing stock 4.4.4, but that gave an error "Updating partition details" failed.
Can someone help me get back into my phone? :crying: ADB doesn't seem to be detecting my phone, else I'd have tried to install a rom via fastboot.
I have multi-tool v4.1 installed, would I be able to flash a rom (stock unrooted and full wipe is perfectly fine too) via that considering adb does not detect my phone, but the computer does?

Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657

oldcynic said:
Well, that looks annoying.
I've found myself in similar situations when I've accidentally flashed something I shouldn't have. The good news is that if you can boot to recovery you can also probably boot to the bootloader and use fastboot.
Have you tried wiping everything and going back to stock? It's time consuming but at least you'll end up with a working phone.
I had to do this when I put the wrong recovery on a phone and it mangled partitions. Device wouldn't boot.
There are instructions for the moto x here
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657
Click to expand...
Click to collapse
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?

HAXTREME said:
Thanks for the reply! Color me silly, but would I be able to use fastboot given that when I run adb the 'adb devices' command does not show my phone?
Click to expand...
Click to collapse
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.

oldcynic said:
Because fastboot mode can start on your device even before Android loads (and can even run when Android isn't installed at all), fastboot mode is useful for updating the firmware quickly, without having to use a recovery mode.
Adb relies on android booting and usb debugging being enabled and the computer being authorized for debugging (L feature). Fastboot does not. Try booting into the bootloader and then run "fastboot devices" . Mine shows up. I suspect yours will too. If it doesn't then I'm out of my depth here.
Click to expand...
Click to collapse
Ah yes. For some reason, my fastboot file had gotten deleted from the folder and so the command didn't run. Everything went smooth once I noticed that. Had to downgrade to 4.4.4., but w/e. Thanks @oldcynic

XT 1093 Bricked after flashing- Stuck in Bootloader

Hello everyone,
I unlocked my Moto X 2014's (US Cellular) Bootloader, and I was running Android 5.1. When setting up the Phone I had connection errors, and I wanted to flash the phone back to 4.4.4 KitKat. I used the wrong image (for the pure edition) and ended up with the phone not booting. I tried to reinstall the 5.1 Image (VICTARA_USC_XT1093_5.1_LPE23.32-21.3_cid9_CFC) from here: teamuscellular.com/Forum/topic/7738-moto-x-2014-victara-xt1093-latest-firmware-and-flashing-instructions-updated-to-51/ , but while flashing I got the following errors: "version downgraded for primary_gpt" after flashartition command and "version downgraded for boot" after the flash:boot" command line on the phone. After everything is finished, and I reboot the phone, i see the unlocked bootloader warning, and afterwards only a, for a brief second flashing, "no command" message, like when entering recovery mode. I'm probably in a bootloop. :crying:
I would be very thankful for help!
Simon

softbrick moto g2

hi guys, i've a problem with my moto g xt1068, i was on oreo pixel experience when my phone and my battery was completely discharged, i connected the charger but my phone went in bootloop, i've tried to get into recovery by the AP fastboot screen, but the phone stuck in the twrp logo, so i've tried to use fastboot tool e reinstall twrpl, the log was succesful but nothing change in the phone, when i try to reboot in recovery i've the same old twrp logo, after if i try to reinstall the whole system the fastboot log still succesful but nothing change in the phone, still the old bootanimation/recovery logo, my bootloader version is 48.87 and i can't downgrade it, the only positive result was the command "fastboot boot recovery.img" that restarted the phone in stock recovery, but i can't do nothing all adb command are blocked, i'cant wipe data/chache partition, anyone can help me ?
sorry for my bad english guys :/

try fastboot erase cache
or try downloading and flashing twrp again (fastboot flash recovery twrp-x.xxxxxx.img) then cleaning cache