Database Develop

Can't flash anything to XT1056

I recently purchased a Moto X XT1056 through eBay to use as a guinea pig for flashing custom ROMs without risking my primary phone. When I first booted the phone, the last owners account was still present and alot of apps were crashing. I didn't care because I was going to wipe it anyway. I do eventually, and frustratingly, make it to the Settings Menu that allows me to factory reset the phone. It restarts, does its thing and reboots, but it didnt get wiped. I thought, 'No worries, I'm going to unlock it and that will wipe it.'
I started following the instructions on the CM website.
First thing I did was use the Moto web site to get an unlock code and unlock the bootloader. I'm assuming that succeeded because I get the Bootloader unlocked boot screen and the bootloader screen says 'Device is UNLOCKED. Status Code: 3'.
Then I tried to flash twrp-2.8.7.0-ghost.img per the instructions and get this result:
Code:
[[email protected] phone]# mfastboot flash recovery Recovery.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'recovery' (8498 KB)...
OKAY [ 0.834s]
writing 'recovery'...
OKAY [ 0.949s]
finished. total time: 1.783s
[[email protected] phone]#
I assume everything is fine and reboot into Recovery using the bootloader screen, but all I get is the dead android and red triangle. Pressing VOL+ and Power get me to the stock recovery where I can reboot the machine. It boots into Android and I notice that the unlock didn't wipe the device. I turn it off and using the button combo boot into the bootloader then select Recovery and use the stock recovery to factory reset the device. I reboot the phone and see that the previous owners account is still there and there are a bunch of popups stating that apps are crashing. I have tried a number of things from a few threads I have read, but nothing seems to work. Trying to flash anything to any partition just seems to succeed without an error, but nothing changes. The only time I get anything different is when i try to erase or format a partition, then I get 'Permission Denied'.
I haven't been able to find any help using search on these forums or using Google.
Please Help.
I do know that it has 4.4.4 on it and Bootloader 30.B7.
I use Linux only and do not have access to a Windows machine.
Android SDK is installed so I have 'adb' and 'fastboot' and I also installed 'mfastboot.'
And, yes, I issued all the commands with root privileges.

its dead already! problem is inside emmc chip! its fried ;(..

Honor 4x factory reset and recovery menu not work

Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.

If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).

oppili said:
If you are sure bootloader is unlocked and using Linux OS, run fastboot commands as root/admin (as sudo).
Click to expand...
Click to collapse
Yes, im sure. On bootloader mode is in red color - Phone unlocked, but i not using Linux, im on Windows 7 and this not help me....

Try fastboot oem unlock - command again.
If still not works, try fastboot erase of that *.img file before flashing that new img file.

oppili said:
Try fastboot oem unlock - command again.
When i try this command...
c:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.004s]
finished. total time: 0.006s
If still not works, try fastboot erase of that *.img file before flashing that new img file.
Click to expand...
Click to collapse
I know about this but im above when i try erase all after this fastboot send me "Failed..." and i will be have dead phone, tell me - when i try erase command for all partitions - will be phone work wit fastboot after this??
THX

Are you the only user in pc ? Do you have admin rights ?
or
try any other pc
or
use Ubuntu OS

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked

thilak devraj said:
the reason for this case, that you should not apply updates while you are rooted.
(assuming that you are in lollipop stock )I suggest you check for the driver .. try to run adb (when your phone is in the active state, not powered off)
now, reboot to bootloader and try any other fastboot commands, like fastboot reboot (just to check that fastboot is responding to the device drivers..)
if it does respond, then I'm afraid you have a serious problem, if it doesn't respond, then you have to deal with the drivers, or you have to double check if your phone is unlocked
Click to expand...
Click to collapse
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
then you should take it to the service center. the only best thing you can do now..

Lulu_568 said:
Yes, i allready try, commands like fastboot reboot, or devices - its work, but when i try fastboot flash .... or erase cache - Command not allowed, when fastboot oem unlock - data parse fail...fastboot just respond but i cannot write or erase flash - dont know why....
Click to expand...
Click to collapse
erase cache command is blocked by huawei in fastboot irrespective of locked or unlocked state. somewhere i read unlock lost permissions after update. if you have not tried unlock after update try it. driver can also be an issue, install hisuite it comes with drivers.

Lulu_568 said:
Hi,
i need help with this strange problem, i want update my phone to android 6.0 but when i start local update phone reboot and freeze on Honor logo, when i try factory reset or reboot to stock recovery menu - its same, again only Honor logo. Bootloader work ok, its unlocked, phone rooted, but when i for example try flash twrp recovery - fastboot send me "Failed...command not allowed"...Cant access recovery menu by fastboot, any app in phone and by keys combination too..also vol up, vol down and power for update from sd card not work, trying to seek for solutions to more than 2 weeks, can anybody here help me please?Thx.
Click to expand...
Click to collapse
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down

shady143 said:
Try this once,
copy firmware in folder 'dload' in sdcard root.
press vol up + vol down + power for 20 secs then release power but keep pressing vol up and vol down
Click to expand...
Click to collapse
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.

zzztidurvirus said:
okay. are you sure the bootloader is unlocked? no harm done. just hold vol down + power up. and you get that green android with white background and the text in RED that says UNLOCKED. if its LOCKED, get the UNLOCK CODE first. just a reminder, you can only fastboot flash those *.imgs if you are UNLOCKED. and there are only some files will be flashed properly (recovery.img, recovery2.img, boot.img, you can try). yes, you can use Huawei Update Extractor to get those files, even in Marshmellow files. but for reviving the phone, use B067 Kitkat or any Kitkat you can get from Huawei Downloads.
1. Get into bootloader mode. I guess you already know how to do that. Plug the phone to wall charger. Yes, leave it charged with white screen showing. Leave it until you finished preparing the PC.
2. Make sure you can use fastboot. You can use Minimal ADB and Fastboot.exe found somewhere in XDA. And make sure that it can detect the phone when you write fastboot devices. It will show up if set up properly.
3. Huawei Update Extractor + Any Kitkat firmware. Extract everything. Note the tags beside each .img inside that Update Extractor. Youre gonna need those tags in order to flash properly.
4. Copy all those *.imgs that extracted into Minimal ADB and Fastboot folder. Check program files (x86).
5. Now ready the pc by launching that minimal adb and fastboot.exe as admin. THIS IS IMPORTANT!
6. fastboot devices. pull the phone from wall charger. plug it to pc. listen to usb connecting sound and driver installation. hit enter and the device should show up.
7. This is where its getting interesting. remember the tags? use that tags like this.
RECOVERY.img = fastboot flash RECOVERY RECOVERY.img
BOOT.img = fastboot flash BOOT BOOT.img
CHECK THE TAGS BEFORE FLASHING!!! and yes, just 5 or less files will be flashed successfully. Ignore it. fastboot reboot it. Yes, its stuck, plug it to the wall again while we prepare the microsd.
8. update.app file. Put that update.app file inside /microsd/dload/update.app folder. Put the microsd inside the phone. Yes, its stuck.
9. Now do the force update. when you see the emui logo, immediately plug it back to wall charger. wait until 100% and it rebooted itself, and you can see the language selection screen again.
DO WITH YOUR OWN RISK. Ive already done it, I hope it worked for you too.
Click to expand...
Click to collapse
First...many thanks for your interest!
Look, about bootloader, on boot mode is in red PHONE UNLOCKED, i try this command in fastboot:
C:\Minimal ADB and Fastboot>adb reboot bootloader
C:\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Minimal ADB and Fastboot>fastboot oem backdoor info
...
(bootloader) FB LockState: LOCKED
(bootloader) USER LockState: UNLOCKED
OKAY [ -0.000s]
finished. total time: -0.000s
so what is FB Lockstate??Is my bootloader unlocked or locked??
Here is another command which i try....
C:\Minimal ADB and Fastboot>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: 0.000s
Cant derermine partition type - is this problem?
I also try this....
C:\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 524288000 bytes
sending 'recovery' (25034 KB)...
OKAY [ 0.783s]
writing 'recovery'...
OKAY [ 1.033s]
finished. total time: 1.831s
C:\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
It seems that fastboot write recovery (with your help i need use admin rights now this work) but i still cant boot to recovery no matter how...
I can also flash and backup boot and recovery via Flashify or Rashr and when i open backup with HEX editor it seems that i succesfully upload TWRP but still cannot acess TWRP recovery....
This is all what i try in this time, of course i read your help words about Huawei extractor etc. but not try at this time, i hope i explain more detailed my problem. Look im not a newbie, i allready flash etc. my Lenovo and P9 lite what i have here but not understand where can be problem in this Honor 4x, it seems like corrupted recovery partition or can be problem in read only/write partition - i play with this option before....
anyway - run as admin - this help me a lot i think, THX and wait your answer.
EDIT: one thing, you think that when i try flash stock recovery (i can, no problem of course) it will be work?
Update: Big success, i just try flash stock recovery B064b and now im in stock recovery menu, im surprised but what now? I want update to Marshmallow 6.0....?
But in stock recovery is: phone and the data cannot be recovered. Continue?
Oh sorry, this is about "not sd card inserted" problem
What will now progress? I have inside B130 firmware and want Marshmallow, also TWRP recovery must i flash now especially for B130 firmware for work?
Update: Yes, all working now, factory reset, recovery etc. you help me a lot, only if you can tell me what number of firmware must i upload for Marshmallow, thx
Last update: So finally, coz im too hurry and dont want wait for your answer :angel:, i just upload from local update first Android 5.1.1. after this 6.0 and all is perfect and working!
My big thanks and kisses goes to you zzztidurvirus, im lucky and still cant beleive that all works, again thx!!

I did once on Win to revert back to Stock from CM12.1 by using img from update.app file. For my case, it's the MM update.app not working, I couldn't flash img files into phone, then I tried to flash files from LP, it worked. I boot into LP ROM and update from there to MM.

Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?

Lulu_568 said:
This not work, when i try this - phone freeze on Honor logo, same as on factory reset or when i try go to Recovery menu...
I check 100 times that is bootloader unlocked, can be problem in bad root or...?
Click to expand...
Click to collapse
I had faced same issue but get back by using the that method.

Sumea said:
Hey hey people.
I was trying to upgrade my friend's Honor X4 Che2-L11 variant to 6.0 age from it's lollipop and ****ed up - big time. It seems to have a recovery, and it bootloops. I can't get it to install any update.app though, it either errors or gets stuck/crashes at 5%.
Now I am trying to flash a individual stock recovery with fastboot. Like the guide by zzztidurvirus there, but whenever I try to issue flash command this is what I get:
target reported max download size of 471859200 bytes
sending 'RECOVERY' (9304 KB)...
OKAY [ 0.258s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.261s
- so basically any flash command sends OKAY, Writing Fails with Command not allowed. Bootloader is unlocked, "PHONE unlocked" on screen and same status messages from fastboot as Lulu up there when making queries.
What gives, what could I try still?
Click to expand...
Click to collapse
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...

Lulu_568 said:
In this case help me i think run adb/fastboot as a admin and i use stock recovery .img from Huawei extractor when i got first success with writing as i remember, hope this help you...
Click to expand...
Click to collapse
Sadly not, as I tried both running ADB fastboot as admin from administrator command line and I tried three different recovery images from huawei, 6.0 (because the flash went bad during attempt to flash a 4.1EMUI with 6.0 B506 ROM for CHE2-L11) - And it keeps denying the write attempt with the same message. More info on the flash: I tried to TWRP flash from 5.1 rom to the EMUI4.1 6.0 ROM following guide someone made with updateappflasher.zip or something, during the flash the phone just crashed 60% in the bar and after that the phone is boot looping into recovery but it can't do anything. Like said any attempt to flash a stock rom even if a recovery seems to exist when booting VOL+ & POWER at the same time, but it will fail if attempting to do wipe data/factory reset in 40% mark. Forced updater can also be accessed but again, thanks to the firmware situation the phone is in it does not flash anything beyond 5% without crashing and being stuck or just giving an error message outright.
Only thing I might have not have is the right kind of ADB drivers but googling about CHE2-L11 I really cannot find a ADB drivers for this phone for life of me and dealing with windows 10 these days makes it worse. At least it used to be that I was with windows 7, back when I myself unlocked the bootloader of the phone and rooted it myself, I have some memory of that being harsh to deal with too, as I had hard time getting drivers that worked right with the phone etc.
I will check into this... At this point my friend bought a new phone already but I still will try to fix the phone for him since I feel personally pretty bad for pretty big mess I made.
I will also try this with a windows XP machine I have still, it is meant entirely for different things but at times like these it is somewhat nice to have a XP around. At least the darn driver problems are not a problem.
UPDATES:
I unbricked the phone. The stock recovery was intact enough for just a normal dload install of a update.app from huawei - why it did not initially work was probably the USB connection to computer and/or 64gig microSD card my friend had, not being compatible with Huawei's recovery updater. I myself had a 8gig card around which worked and I restored the phone ultimately to a 6.0 official ROM. I also went ahead to root it - and final find really was that the reason why recovery etc. would not flash, was because I wrote "fastboot flash RECOVERY twrp.img" - instead of "fastboot flash recovery twrp.img" - the latter works, and the all caps for "RECOVERY" results in illegal command error - and it was no bigger than that.
Meanwhile even after sorting this all out my friend already ended up buying a new phone so it hurts but I hope some other people find some info here useful.

Recovery bootloop

Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?

ziembus said:
Guys, here's the problem:
I've clicked reboot to recovery in power menu in Pure Nexus ROM and now I'm stuck in recovery bootloop.
The phone tries to boot into recovery, shows the leeco recovery message and then flashes red triangle android robot and just shows black screen. If I connect to PC at that point, adb recognises a device in recovery mode. But I can't flash anything.
If I try long enough I can boot into fastboot, but then I get the "Android Bootloader Interface" in the device manager - but adb doesn't see the device.
Any suggestions? Can i somehow make ADB see the device so I can reflash TWRP?
Click to expand...
Click to collapse
Dear
Press and hold vol - and power button together, then your phone will boot into fastboot mode.
then simply you can use fastboot commond below to flash recovery.
fastboot flash recovery recovery.img

OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?

ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
I want to know which recovery you tried to flash through fastboot. It may not allow you flashing twrp ultill oem is locked. You can try flashing stocking recovery.

ziembus said:
OK I've managed to get my PC to recognize the device. Now fastboot sees the phone.
The thing is that I can't flash anything. I had probably disabled "Allow Oem Unlock" in Developer options.
So I have fastboot but can't flash anything there. Any suggestions? If I reboot without holding Vol- the phone tries to boot into recovery and fails.
EDIT: At this point I can either boot into fastboot, where I can't do: "fastboot oem unlock-go"
Or boot into recovery, which doesn't load properly, all that's left is a blank screen - but ADB sees a device in recovery mode"
Is there anything I can do to get out of those two options?
Click to expand...
Click to collapse
When in fastboot mode, you can try to boot twrp from the pc with
Code:
fastboot boot nameoftwrp.img

JamBax said:
When in fastboot mode, you can try to boot twrp from the pc with
Click to expand...
Click to collapse
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far

ziembus said:
Tried that, it tells me that I can't do this because the phone os locked. Now I'm looking for Stock recovery IMG for x522
EDIT: Trying to flash stock recovery gets me this message:
target reported max download size of 536870912 bytes
sending 'recovery' (13904 KB)...
OKAY [ 0.435s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.451s
Its the same whether its TWRP image or stock recovery image.
I was thinking of using this:
https://forum.xda-developers.com/le-2/development/tools-unbrick-thread-leeco-le-2-x52x-t3634609
But, unfortunately, there is no file for American x522.
It sucks to be able to get into fastboot and not be able to do anything.
Thanks for the suggestions so far
Click to expand...
Click to collapse
Try Leeco AIO tool kit to reboot your device into recovery . It's working for me

leco le 2 x520 recovery problem
I have a problem with recovery in le 2 x520. It installs via fastboot by unlocking the bootloader but stops at the Le recovery logo and nothing else happens. I installed from version 3.0.2.0 to 3.1.1.1 and nothing happens, I do not have recovery and writes everything okey went. what is going on ??

I have same problem. how to fix

I have a new one (acutally two, got them for U$D 108.99 each one)
Using ADB devices it recognize the UID like 0123456789ABCDEF, so I think the recovery is corrupted, intentional or not, it is blocking fastboot and recovery to load normally.
At this point I can't do anything.... any suggestions?

You solved it ?
I having the same issue maybe the issue is with stock rom since i flashed in normal twrp,chinese twrp and also that stock recovery.
****!

Can't flash TWRP on a Moto X (xt1052)

Dear friends...
I tried to root a Moto X (xt1052). I installed Android SDK plus newest USB Drivers from Motorola. USB Debugging is activated.
I could successfully unlock the bootloader and tried different times to flash a TWRP. The commandline told me, that is sucessfuly flashed the TWRP (I tried it with 2.8.7, 2.8.6 and 3.1.0).
But I can't go after that into recovery. Nothing happens.
It starts normally and works fine but i can't find any recovery to go into and to install SU and to root it.
OS is Android 5.1 Lollipop
andoid-securitypatch-layer ist 2016-04-01
Systemversion 222.201.1.ghost_row.Retail.en.DE
Build Nummer: LPAS23.12-15.5-1
Does anybody have an idea, where my mistake lays?
If there is already a thread with this or a similar issue, pls move my post to that thread.
Thank you, folks
legalize_it66

legalize_it66 said:
But I can't go after that into recovery. Nothing happens.
Click to expand...
Click to collapse
Enter recovery RIGHT AFTER you flashed it, using Vol Up button on "Recovery" text field.

I did so direct after TWRP flashing without reboot. Select recovery by volume down button and than pushing power button to enter. Screen becomes dark and after a few seconds appears the charging screen when I'm still connected via USB. When I disconnect my device before and push recovery, the mobile goes off and the screen becomes black.
This mobile dont give me even a chance to enter twrp. I found a couple of websites with a step by step tutorial and I followd them but nothing happens.
C:\Users\PC\Desktop\Moto X>fastboot flash recovery twrp-2.8.6.0-ghost.img
(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9488 KB)...
OKAY [ 0.834s]
writing 'recovery'...
OKAY [ 1.147s]
finished. total time: 1.983s
It seems, that TWRP was sucessfuly flashed but I cant enter TWRP like I described above.
For this trial i used the tutorial from this site: h##ps://www igadgetsworld com/moto-x-how-to-root-moto-x-running-on-android-5-1-step-by-step-process/
EDIT: SOLVED
after flashing TWRP i scrolled to "recovery" and than i pushed power & volume up an i found my TWRP. Thanks anyway

Soft Brick Nexus 6 with No Recovery and Bootloop

Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks

You're screwed.
In situations where there is a locked bootloader and a soft brick like this, sideloading a Google OTA image using the stock recovery would have been able to restore the device to operating condition. Unfortunately you have no recovery, and thus no way to restore this device.

If you are stuck in boot loop and have no recovery, there is a way to fix your problem. If fastboot commands work then download Wugs Nexus Root Toolkit and use that to return to stock. There might be a way to unlock the bootloader first and then go from there. Have you tried to get the bootloader unlocked through fastboot commands then flash TWRP. Dude thinks this through. There is always a way to fix a soft brick. I hard bricked not long ago and was able to fix my device on low level systems code. Just don't give up

Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.

Strephon Alkhalikoi said:
Regarding the locked bootloader, the only way that the OP can make changes to the device's system and recovery partitions is if he can unlock the bootloader. To unlock the bootloader a copy of Android must be in the system partition. He would need to enable Developer Options in Settings, then enter Developer Options to enable the OEM Unlock toggle hidden there.
Pretty standard stuff, right? The problem here is that the bootloop the OP encountered is not the typical one. In a normal bootloop, the device enters the boot animation and gets stuck. In this instance, the bootloop as described doesn't even present a boot animation, but immediately flashes the Google logo present in the bootloader repeatedly. This is due to there being no software in the system partition at all. Since there is no OS in the system partition, it's impossible for the OP to enter Developer Options to enable OEM Unlock, which he has to do in order to be able to unlock the bootloader with fastboot.
So, explain how a toolkit which leverages fastboot and ADB to do its work is supposed to help this poster when the naked software Google provides cannot.
Click to expand...
Click to collapse
I flashed a faulty bootloader image via fireflash app instantly bricked. I went through low level fastboot recovery options. I fixed my device. This is a mid level soft brick it can be fixed just needs some patience and perseverance. If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible. When I bricked it was a black screen, qhusb Qualcomm level I needed to restore my bootloader, I did it. This guy can fix his situation, I could do it for him if I had the device in hand.

Rondeau79 said:
If fastboot commands are available then he can do a fastboot unlock command and fastboot a TWRP img. It might take some work but it isn't impossible.
Click to expand...
Click to collapse
Look, we can go back and forth on this until blue in the face. The facts of the matter are as follows.
1. The bootloader is locked.
2. There is no OS in the system partition.
3. There is no stock recovery.
4. An OS in the system partition is required to be able to unlock the bootloader.
5. A stock recovery is required to sideload OTA images.
6. The original post does not mention whether the OP tried unlocking the bootloader.
You mentioned Fastboot. Everything you described in the quoted portion of your post works, but only if the bootloader can be unlocked. I'm assuming however the OP tried that already, failed, and went straight into flashing system images. If he didn't try it, he should, although I believe the attempt will fail.

Any help here. I have the exact same situation. Should I take my phone to Motorola/Google for repair? Anything else i can try?

@sumit.nathany: If you are in the same situation (locked bootloader, no OS, no recovery) you'll need to contact Motorola. But it won't hurt to try unlocking the bootloader before you do.
The only other option requires hardware hacking, and both the tools and methods can't be discussed here (against XDA rules).

Not that I know much about this, but what about the fastboot boot recovery.img command? If used with a Google recovery image, it might get around the bootloader lock?

Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.

Strephon Alkhalikoi said:
Fastboot boot recovery.img doesn't work with a locked bootloader.
Think of the ramifications. If one could simply fastboot boot a TWRP image, it would be possible to root the device without unlocking the bootloader. That would mean every AT&T and Verizon device could be rooted as well as devices from Samsung, Huawei, and Lenovo, all of which lock their bootloaders. The carriers would not be happy, and the OEMs that lock their bootloaders won't be happy either.
Click to expand...
Click to collapse
Making it work, but only with an original recovery from Google, would not open any opportunities.
BTW, do you, or anyone else have any theories why this happens? Hardware error?

It probably could be made to work, but then you'd run into an issue of people spoofing the stock recovery, which would still open up the whole can of worms. Better to simply block the ability completely unless the bootloader is unlocked.
As to how this happened I will not speculate. Reason being that any speculation would be useless without seeing the devices firsthand and examining them. Not to mention the people that would be throwing hissy fits thinking I accused them of something. All that really matters here is that a device in this state is not something that can be fixed without a trip to the repair center.

fix it
truwrxtacy said:
Hi everyone i got a Nexus 6 that is stuck in bootloop, its on 6.0.1 with january security patch, cant remember which version though. It boots to google and shuts off and boots back up to google, i have tried to reload the software on it by downloading it from google and and installing it, but it always gives me error that because the bootloader is locked it cannot install the s/w even if i choose the newest one. Since it does not go into recovery, i cannot adb sideload the software into it, does anyone have any suggestion on how i can get this phone back up and running again?
I also cannot flash the system img or boot or recovery into the phone because the bootloader is locked.
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (8901 KB)...
OKAY [ 0.278s]
writing 'recovery'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.297s
C:\Users\admin\Desktop\shamu-mob31s-factory-c73a35ef\shamu-mob31s\image-shamu-mob31s>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (8183 KB)...
OKAY [ 0.269s]
writing 'boot'...
(bootloader) Not allowed in LOCKED state!
FAILED (remote failure)
finished. total time: 0.269s
thanks
Click to expand...
Click to collapse
I found a solution for this problem i know is late in the game but better late than never jijiji

Did you try unlocking the device with?
Code:
fastboot oem unlock

Zombie

Rezz577 said:
fix it
I found a solution for this problem i know is late in the game but better late than never jijiji
Click to expand...
Click to collapse
Hi sir.
Can you tell me the solution, please?
I am in yhe same situation, no recovery and bootloader locked, and bootloop
i wait for your answer