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

Bootloop - Please help

Hi Guys,
Would appreciate some help, though I realise I may be out of luck. My device is rooted with twrp installed, I thought i'd lock my bootloader so that the new killswitch / device reset protection would have some use.
Basically, it's now stuck in a boot loop. I get a flashing teamwin (twrp) logo when I try to turn it on, that's all. Here's the kicker, I can't unlock my bootloader again because I didn't have "allow OEM unlock" ticked in the developer settings.
Anyone have any ideas? I don't care if I lose my data, just panicking right now.
My Thanks!

Someone smarter than I can tell you how to use fast boot to unlock your boot loader.
TLDR: someone can help you that someone is not me. Worry not.

ixa20 said:
Hi Guys,
Would appreciate some help, though I realise I may be out of luck. My device is rooted with twrp installed, I thought i'd lock my bootloader so that the new killswitch / device reset protection would have some use.
Basically, it's now stuck in a boot loop. I get a flashing teamwin (twrp) logo when I try to turn it on, that's all. Here's the kicker, I can't unlock my bootloader again because I didn't have "allow OEM unlock" ticked in the developer settings.
Anyone have any ideas? I don't care if I lose my data, just panicking right now.
My Thanks!
Click to expand...
Click to collapse
you can try flashing the system img. can you get into the bootloader?

simms22 said:
you can try flashing the system img. can you get into the bootloader?
Click to expand...
Click to collapse
Its locked. Wont unlock because allow OEM unlock in android is unchecked. This setting is crazy

Thanks for the replies guys, anyone else got suggestions? Would motorola fix this if I sent to them? I assume they must have some development tools or qualcomm software that could do it.

ixa20 said:
Thanks for the replies guys, anyone else got suggestions? Would motorola fix this if I sent to them? I assume they must have some development tools or qualcomm software that could do it.
Click to expand...
Click to collapse
I would assume they could.

The same thing happened to me and I thought for sure I was completely shafted. Turns out you can get back into your device by doing the following:
fastboot format users
fastboot format cache
I then rebooted the phone and voila, back into Andriod where I can click that unlock setting off and try installing the custom recovery yet again.

Lock-Bricked nexus 6

Hello,
I have trouble with my nexus 6. I tried to flash the latest factory image for 5.1. But my system.img did not flash... after hours, I did not found any solution, so tried to lock and relock the bootloader again. Locking worked as espected... but unlocking returns the following message:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Now I sit here, no booting device because of missing android version and I can not unlock the bootloader anymore... Somebody can help?
Thanks
Andy

Sorry - it's not good news:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497

**** that's really bad!!! But thanks for your reply!!!

ANDYx1975 said:
**** that's really bad!!! But thanks for your reply!!!
Click to expand...
Click to collapse
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk

narezese said:
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!

ANDYx1975 said:
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!
Click to expand...
Click to collapse
Im talking about mine.. Before flashing 5.1 the option was checked..
Sent from my Nexus 6 using Tapatalk

You sir have a brick. Your only option as of right now is to try to get Motorola to replace the device for you.
Sent from my Nexus 6 using XDA Free mobile app

ok... tkanks I have to try this... even if I think my chances are almost zero!!! Thanks anyway!!!

Have you tried to adb sideload the ota .zip?

yeah I only have access to fastboot... and he does not find the device

From fastboot can you get to stock recovery? After selecting recovery in fastboot, you'll get the Android dude ... But you have to hit the power and volume up/down as well (forget the exact combo) to get into recovery. From there you select install install via adb (forget the exact verbiage, but it's the second option from the top). From there you run adb, not fastboot
---------- Post added at 04:00 AM ---------- Previous post was at 03:58 AM ----------
http://www.droid-life.com/2015/03/1...1-ota-updates-for-nexus-devices-4-5-6-7-9-10/
^ d/l link with a link to (better) flashing directions

to be honest I do not know it's already out home to the repair service... ****... I should be more patient!!!

Gotcha ... Don't feel bad, you're not alone. I, and many others, did the same/similar and ended up in the same situation.
I been rooting/tinkering for 6+ years across 10 or so devices and it turns out a friggin NEXUS is the first device that I brick! ?
(I'm fully aware of the risks we take with unlocking amd rooting, but IMO Google screwed the pooch with this OEM Unlock "feature" in developer options! Why make unlocking dependent on a setting WITHIN the OS??!)

So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found

ANDYx1975 said:
So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found
Click to expand...
Click to collapse
You need to boot into stock recovery. From the screen you are in press volume up and power.

What ^ he said ... Then once in stock recovery select the second option (install update from adb (or something like that))

ok... I can not go into recovery... the google logo appears and nothing happens... ****!!! But hey thanks anyways!!!

That sucks! Sorry man!

@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6

Casper34 said:
@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, thats what I said.

Moto x 2014 XT1092 stuck in boot

So recently i unlocked my bootloader so i could root my XT1092. But without knowing, i booted a file for an older android version while i was on 6.0. So then i was stuck at the end of the boot. Somebody told me to flash original stock files from motorola site. Did that but now i'm stuck at the 'bootloader unlocked' warning, and when i trie to charge it stays at battery low and it doesn't charge. Also when i trie to lock the bootloader again it says:
C:\android-sdk\platform-tools>fastboot oem lock
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
OKAY [ 0.057s]
finished. total time: 0.063s
What should i do? PLEASE SOMEBODY HELP!!!

Sorry can't help..... But will you pls tell me what wrong step did you go through so that I can avoid them ( I need to unlock my X2)... Thanks!

had no problems with unlocking the bootloader. I flashed a twrp on the device and when i tried to get into recovery it said: no command
So i used another method that said i needed to boot a file but i forgot to read the comments and it was only for the moto x 2014 that are running on KITKAT. I was running on 6.0 and i saw that right after i booted the file. So always read the comments! That's the advice i can give. If you find a proper method please tell me too pls so i know what to do if i find a solution.

Ok, i fixed it i had some problems flashing the system img. but its solved.

OK i got the phone back working but it doesn't recognize my sim-card anymore and my internet speed is slow af. I got 101 kb/s for downloading and 22kb/s uploading speed. Sometimes i see a toast that says that it was unable to download the appendix?! What do i have to do to fix it?

benjg_ said:
OK i got the phone back working but it doesn't recognize my sim-card anymore and my internet speed is slow af. I got 101 kb/s for downloading and 22kb/s uploading speed. Sometimes i see a toast that says that it was unable to download the appendix?! What do i have to do to fix it?
Click to expand...
Click to collapse
You might have flashed an image for other variant. Now, flash the modems for your variant, you can find them in the threads! :fingers-crossed:

Could be true. Maybe it would work again if i install cyanogenmod 13?

XT-1063 Flashing errors

Hi guys! Its my first time posting a problem, i usually manage to fix it by reading and looking for info, but this time im really stuck
My cousins phone turned off one day and it never booted right again, got stuck in Moto logo... He tried to fix it (Not sure what he did, but my guess is that he somehow deleted a partition or someting), and now, it wont flash anything, just keep getting this error in every line:
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
Click to expand...
Click to collapse
I was able to unlock the bootloader (Device is UNLOCKED. Status: 3) but still cant flash anything, i tried almost every single post i could find in the web but no luck at all...
It boot directly into fastboot mode and when i press the power up button the logo image was replaced by this http://imgur.com/JH4CAq1
Bootloader version is 48.86 and when connected to the PC it is recognized as "Fastboot Titan S"
If anyone can help me i'll be really greatful!
Thanks for reading and sorry for my pooooor englando :laugh: