[Q] [HELP!] Moto X XT1058 unbrickable!!!

[duendemago]

Dear XDA community. After several days of trying alot of things I dare to bother you because Im really in need of your expertise (Excuse my english please, Im not native speaker).

I will explain everything in ordered manner, so the help may come easily:

Original state when device was gifted to me:
Device: Moto X XT1058 (Ghost Version 2013)
Bootloader: Unlocked
Rooted: Yes
Android Version: 4.4.4 (RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF)

FIRST PROBLEM DETECTED: Wifi suddenly stopped working
Fix attempted: Hard reset (wipe, etc etc).
Result: Nothing changed
Alternate fix: Installed Lollipop 5.1 and wifi stayed the same (I used the method of going from 5.0.2 to 5.1).
Lollipop versions used: Blur Version 221..41.31 and 38 (5.0.2) and 222.21.2 (5.1) all of them ending in ghost_row.Brasil.en.BR
MEthod used: ADB, succesfull install (The tutorial I followed asked for use OTA for installing the first upgrade of the 5.0.2, but my wifi is not working and I havent payed my phone, so no Data for me this month )
So until that, everything was fine except wifi. I read in some forums that I should try the original stock rom for the device, so I succesfully downgraded to 4.2.2 version---> WIFI STILL NOT WORKING

Ok. I know Im stubborn, so I said, what the hell, lets return to the 4.4.4 version I used to have. I re installed and EVERYTHING WAS FINE also there.

Now, here is where it gets super weird because I really made a bad mistake, but I know there is some hope in this forums: I tried to install again 5.1 for the second time (using the little by little upgrade from 5.0.2 to 5.1) but I forgot that the first time, the tutorial demanded to install the 5.0.2 through OTA (By placing the file inside the root folder of the device). But as you may probably know, unless you have wifi or data the OTA wont let you go with the update (and I as I explained above, I dont have nether!!!, so thats why I used ADB with good results), so I stupidly tried to flash the 5.0.2 directlty from the device using recovery mode instead of using ADB (as an alternate step to OTA)--->Device bricked???

This is all the error list I have after all that mess, and I dont know what else to do:
-------------------------
START OF LIST

Status Code: 0 (it was on 3 before)
Boot Mode: Working but seems to be locked (used to have the "unlocked bootloader warning" before)
Error Showing when starting phone:
"downgraded security version
update gpt_main version failed
Failed to hab check for gpt backup: 0x35
CID Read Failure
Invalid CID Status 0x69 Customer ID error. Contact Dealer: 0xdead
Fastboot reason: Invalid CID"

Error showing when trying to go to Recovery Mode:
Boot Up Failed

Fix #1 attempted: Flashing Team Win Recovery from Fast Boot and Moto Fast Boot
Error #1 Shown on CMD prompt on PC:
"(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (9136 KB)...
OKAY [ 0.835s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)"
Error #1 Shown on device:
"Fastboot Reason: Invalid CID
USB Connected
getvar partition-type: recovery
getvar max-download-size
downloading xxxx (9355264) bytes
done"

Fix #2 attempted: Flashing stock rom using different Fastboot commands (RDB doesnt recognice device, but Fastboot do recognice device) such as "fastboot oem, etc etc--> its a big list)
Error #2 shown: Variable not supported! (in all cases)

Fix #3 attempted: Trying to re unlock bootloader in case is still locked using "fastboot oem get_unlock_data" command
Error #3 shown on CMD window: Could not get unlock data!
Error #3 shown on device: Process oem command: get_unlock_data

Fix #4 attempted: Trying to flash the stock rom from fastboot (version RETAIL-BR_4.4.4_KXA21.12-L1.26_52_cid12_CFC_1FF.img)
Error #4 shown on CMD on PC:
"(bootloader) Variable not supported!
target reported max download size of 805306368 bytes
sending 'recovery' (1 KB)...
OKAY [ 0.279s]
writing 'recovery'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.379s"
Error #4 shown on device:
"getvar partition-type: recovery
getvar max-download-size
downloading 1364 bytes
done"
Possible solution found (not working for me): To open the stock file with note pad and erase all get var lines and save, and try again. This stock rom im using doesnt have those lines. But any way, any attempt of flashing whatever ends in a "not valid" or something similar error

END OF LIST
____________________________

So I guess I have tried many things, I know Im missing something but Im not but a noob user, so I dont know how to interpetrate this errors and messages!! My only guess is that my device became "non rooted" and the bootloader is screwed in some way. I just... I just dont know what to do, I seriously need your help guys!!!!! I know it maybe is easier to go to a repair technician but I really would appretiate your help so I can learn from my mistakes!!!

Questions: Is there a way to root the device and fix the bootloader from Fastboot mode?

Thanks and more thanks to you all!!!!! May the gods of technology help us all!!! :angel:

 

[KidJoe]

I'm going to tell you what caused it, and why...

You attempted to downgrade ROM version (you had 5.1 and flashed an older rom)... and that is what messed you up.

There are many many warnings in these forums telling people DO NOT DOWNGRADE, even if you have an unlocked bootloader! For example, an entire thread -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202

As for how to fix it... With what is available to us today, there is no 100% safe way. However, in the threads you'll find others in the same/similar situation. You should be able to find a process to try to get you back to a working phone, BUT not everyone has been successful in recovering from this situation.

 

[duendemago]

I'm going to tell you what caused it, and why...

You attempted to downgrade ROM version (you had 5.1 and flashed an older rom)... and that is what messed you up.

There are many many warnings in these forums telling people DO NOT DOWNGRADE, even if you have an unlocked bootloader! For example, an entire thread -> http://forum.xda-developers.com/moto-x/general/info-warning-risks-downgrading-impacts-t3058202

As for how to fix it... With what is available to us today, there is no 100% safe way. However, in the threads you'll find others in the same/similar situation. You should be able to find a process to try to get you back to a working phone, BUT not everyone has been successful in recovering from this situation.

Hi and thanks for kindly response. As you said, it was my silly mistake (in my desperate effort to see if the wifi issue was a software issue or not). Now I just had no other option than to take the device to a Motorola Lab, they said that some part of the hardware was burnen even befor I tried the downgrade...so nothing to do here.....thanks anyway

 

[miju12]

Hi and thanks for kindly response. As you said, it was my silly mistake (in my desperate effort to see if the wifi issue was a software issue or not). Now I just had no other option than to take the device to a Motorola Lab, they said that some part of the hardware was burnen even befor I tried the downgrade...so nothing to do here.....thanks anyway

maybe with this thread you can resurrect your moto x http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057

 

[glarepate]

If, as you say, the first thing that happened was that you lost WiFi then at that point in time a simple way to check for a hardware error would have been to look at what happens when you try to turn WiFi back on.

If WiFi tries to turn on and then just turns back off again in a second or so then the next step it to try turning on Bluetooth.

If Bluetooth does the same thing -- tries to turn on and then fails -- then that means, as Moto told you when they looked at it, that you have a hardware failure: If only one radio won't turn on then it's probably software/cache. If both won't turn on it's hardware.

 

[duendemago]

If, as you say, the first thing that happened was that you lost WiFi then at that point in time a simple way to check for a hardware error would have been to look at what happens when you try to turn WiFi back on.

If WiFi tries to turn on and then just turns back off again in a second or so then the next step it to try turning on Bluetooth.

If Bluetooth does the same thing -- tries to turn on and then fails -- then that means, as Moto told you when they looked at it, that you have a hardware failure: If only one radio won't turn on then it's probably software/cache. If both won't turn on it's hardware.

Thanks for response. In fact, Wifi turned on, but no wifi networks were shown at all, except some rare exceptions where you could see 1 or 2 maximum, but nether way it wouldnt connect to any, doesn´t matter if I was on 4.4.4 or 5.1, so my silly mistake was to downgrade to stock 4.2.2. I took it to Moto LAb and they warned me that their attempt to mount new software could lead to final total brick (no boot loader etc.), due to the lack of options, I accepted and now my Moto X is dead... RIP...and thanks to this wonderful community!!! :highfive:

 

[duendemago]

maybe with this thread you can resurrect your moto x http://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057

thanks i will try it

 

[JulesJam]

Status Code: 0 (it was on 3 before)

That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now

---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------

thanks i will try it

I don't think you need that - you can still get into fastboot and have your device recognized. That method is for those who cannot get into fastboot and have their device recognized as a Moto X. It says QHSUSB_DLOAD instead. Based on what you have written, yours isn't in that state yet.

Call Motorola if you have to and get the device's unlock code. You should have a motorola account and have your device linked to it in My Stuff or whatever the equivalent is in your country's motorola web site.

---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------

Error Showing when starting phone:
"downgraded security version
update gpt_main version failed
Failed to hab check for gpt backup: 0x35
CID Read Failure
Invalid CID Status 0x69 Customer ID error. Contact Dealer: 0xdead
Fastboot reason: Invalid CID"

Try reading these threads too:

http://forum.xda-developers.com/showthread.php?t=2273574

http://forum.xda-developers.com/showthread.php?t=2375197

 

[duendemago]

That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now

---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------

I don't think you need that - you can still get into fastboot and have your device recognized. That method is for those who cannot get into fastboot and have their device recognized as a Moto X. It says QHSUSB_DLOAD instead. Based on what you have written, yours isn't in that state yet.

Call Motorola if you have to and get the device's unlock code. You should have a motorola account and have your device linked to it in My Stuff or whatever the equivalent is in your country's motorola web site.

---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------

Try reading these threads too:

http://forum.xda-developers.com/showthread.php?t=2273574

http://forum.xda-developers.com/showthread.php?t=2375197

Thanks for kind response. Dont believe me...what do I know? Im also in shock with this 3 to 0 status!! An engineer in programing friend of mine told me that due to that locked state of the device, it was imposible to flash anything, no recovery, no nothing!!! I didnt know you could get the code by phone.. I will try to do that, maybe that could save my noob ass!!! Thanks sir!

 

[KidJoe]

That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now

And you shouldn't be able to change the CID, even with a Dev Edition.... But notice his says CID: 0xDEAD

We see this happen from time to time due to a failed downgrade attempt. It leaves the phone in an "unknown" state.

That being said, in the past we've seen some who are able to recover this by using mfastboot to flash the SBF which matched the newest ROM the user had on the phone (with some extra command lines). But in this case, since there isn't a 5.1 SBF, that is not an option.

 

[JulesJam]

Thanks for kind response. Dont believe me...what do I know? Im also in shock with this 3 to 0 status!! An engineer in programing friend of mine told me that due to that locked state of the device, it was imposible to flash anything, no recovery, no nothing!!! I didnt know you could get the code by phone.. I will try to do that, maybe that could save my noob ass!!! Thanks sir!

Read these threads I linked to. It looks like these people had the same problem you did and solved it themselves:

http://forum.xda-developers.com/showthread.php?t=2273574

http://forum.xda-developers.com/showthread.php?t=2375197

---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------

And you shouldn't be able to change the CID, even with a Dev Edition.... But notice his says CID: 0xDEAD

We see this happen from time to time due to a failed downgrade attempt. It leaves the phone in an "unknown" state.

That being said, in the past we've seen some who are able to recover this by using mfastboot to flash the SBF which matched the newest ROM the user had on the phone (with some extra command lines). But in this case, since there isn't a 5.1 SBF, that is not an option.

In the 2 threads I keep linking to, the people had the same problem that OP had but were able to solve it. He should read them.

 

[duendemago]

That shouldn't be possible to go from 3 to 0. If you were status code 3 unlocked and relocked your bootloader you should be status code 2 locked now

---------- Post added at 08:08 PM ---------- Previous post was at 08:05 PM ----------

I don't think you need that - you can still get into fastboot and have your device recognized. That method is for those who cannot get into fastboot and have their device recognized as a Moto X. It says QHSUSB_DLOAD instead. Based on what you have written, yours isn't in that state yet.

Call Motorola if you have to and get the device's unlock code. You should have a motorola account and have your device linked to it in My Stuff or whatever the equivalent is in your country's motorola web site.

---------- Post added at 08:16 PM ---------- Previous post was at 08:08 PM ----------

Try reading these threads too:

http://forum.xda-developers.com/showthread.php?t=2273574

http://forum.xda-developers.com/showthread.php?t=2375197

Read these threads I linked to. It looks like these people had the same problem you did and solved it themselves:

http://forum.xda-developers.com/showthread.php?t=2273574

http://forum.xda-developers.com/showthread.php?t=2375197

---------- Post added at 04:40 PM ---------- Previous post was at 04:39 PM ----------

In the 2 threads I keep linking to, the people had the same problem that OP had but were able to solve it. He should read them.

Thanks!!! I will try those...nothing to lose here. The device remains at its lonely bootloader state with the "Invalid Cid" error when turned on, etc. I chat with a Motorla assistant and he said they CAN´T PROVIDE the unlock code for the Bootloader because they don´t have that info, the only way is the traditional "go to a web page and unlock here" way, but that didn´t work for me at all (the device shown errors when trying to obtain unlock code). Soooo I will keep trying guys! Thanks for kind responses!!!

 

[JulesJam]

I chat with a Motorla assistant and he said they CAN´T PROVIDE the unlock code for the Bootloader because they don´t have that info,

The front line reps can't provide it but Tier 3 Tech support can. They are US based and you have to get a call back from them. It takes awhile before they will get back to you.

Try the other methods in the links first. I think that one link is in spanish too.

 

[viversba]

Here's what worked for me (I was in the exact same situation as you). For me the problem was to find the stock rom that was installed before it bricked, which in my case was the one in this link (Go down to: XT1053 Retail GSM Unlocked (Version: 222.27.5.ghost_row.Retail.en.US, Modded Version: 222.21.15.ghost_row.Retail.en.US) and choose the untouched version). Here's the thing, I don't know what was your las rom, so it is a matter of trying which retail rom was the one it got bricked in, it took me like 6 months of trying and trying. Btw, i'm using normal fast boot (not mfastboot) in Mac, and the instructions in this website. Please note that both of these commands gave me the error: FAILED (remote failure):

mfastboot flash boot boot.img
mfastboot flash recovery recovery.img

But it went ok when I rebooted it after finishing installation (took a long time to pass motorola logo tho).

PD. Phone status returned to UNLOCKED Status 3 after installing the OS.