Related
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
br0adband said:
Well I decided to sell this Atrix HD I just recently acquired and of course because I have no luck at all not even 5 mins after posting the ad on craigslist I ended up potentially bricking it, sadly. I've spent the better part of the past 2 hours scouring threads and posts hoping for a solution but so far I've had no luck so I'll take this last step and ask if anyone might have any advice or solutions. Here's the situation:
- Atrix HD, originally with JB 4.1.1 on it (pre-final AT&T update, mind you)
- rooted with motochopper then bootloader unlocked with motopocalypse, no issues over the past 10 days or so that I've owned this AHD at all)
- was running CM11 nightly without issues (installed with CWM 6.0.5.1, had flashed several ROMs over the past 10 days including CM12, the Mexican retail ROM, and then back to pure AT&T several times, actually
- about 2 hours before making this post I listed it on craigslist and then used Myth Tools to go back to stock (stock being MB886_att-user-4.1.1-9.8.0Q-97_MB886_FFW-20-27)
- no issues with the flashing process, booted up as expected, worked fine for a few mins then I connected to Wi-Fi and grabbed the final JB update released by AT&T, when it finished I clicked "Install now" to do the reboot and install it
- rebooted into the install and seemed to finish ok, didn't glitch or error out in any respect
- somewhere in the middle of the final reboot after the upgrade it crapped out and then went into the bootloader loop to AP Fastboot (S) mode
- got the following error (which is known to a few other members in the past based on postings I located):
Code:
(typical info at the top of the screen)
Device is LOCKED. Status Code: 0
Battery OK
Connect USB
Data Cable
downgraded security version
update gpt_main version failed
failed to hab check for gpt_backup:0x35
failed to load GPT
CID Read Failure
Invalid CID status 0x69
No SP partition found
Fastboot Reason: Invalid GPT
usb connected
As stated, this AHD was bootloader unlocked without any issues but for whatever is now showing as LOCKED. The thing that concerns me is that if I use fastboot devices it doesn't show the proper info as it used to (the typical TA00etcetcetc model number) - it's showing an 8 digit alphanumeric number I've never seen before so that's a big red flag right there.
I've attempted every process I can locate so far and had zero success at all - only one single fastboot command gives me an OKAY message and that's fastboot oem fb_mode_clear. Every other fastboot command offers up a FAILED (remote failure) error, all of them and I've tried pretty much all of them.
I cannot flash anything to the AHD it seems so I'm guessing that means it's 100% "bricked" in the sense that it's powering up, can be seen from the PC/laptop using fastboot devices, but that's it just not actually there at all for whatever reason.
I've attempted to use 2 different laptops, 1 desktop, multiple various USB ports, cables, you name it I'm pretty confident I've attempted to use it in some respect and still nada, zip, zilch, nothing has come from my efforts. If it's totally bricked then so be it, I'll live, but I keep holding out hope that something I missed will help but it's starting to look like this is beating a dead horse now.
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
So apparently for whatever reason the final JB update pooched this device (even in spite of it not doing it in the past week when I rolled back to stock at least 3 prior times in testing). I'm suspecting - but can't say for certain - that potentially the CWM 6.0.5.1 which I just installed like 2 days ago could be the culprit here; previously using 6.0.4.4 I had no issues whatsoever and that is the only variable that's changed in my flashing process that I can recall.
Anyway, that pretty much covers the situation - if anyone has any advice that might bring this AHD back to life I'm definitely interested in hearing it. I don't have JTAG hardware, don't have a factory cable (if one is required), don't have anyone in the area that does that I'm aware of, etc. Basically if I can't get it resolved on my own then it's a dead device I'll toss in a drawer till that miracle comes along...
Thanks for reading, regardless.
Click to expand...
Click to collapse
Did you edit the script when flashing the stock JB with Mythtools or RSD lite?
Sent from my ATRIX-RAZR HD using XDA Free mobile app
Yep, it even states that in my post:
I've attempted using RSD Lite to push the Mexican retail ROM to it (with the edited xml file), the AT&T retail ROM, etc - I can't locate any FXZ files at all so that might still be an option but I simply cannot find any of them if they exist.
Click to expand...
Click to collapse
Nothing will flash to the device which is the biggest issue of all; if I could flash the gpt_main0.bin file I'd be getting somewhere (since as I understand it that sets the partition layout for the partition img's that will follow in the flashing process).
As stated, the only thing that works in terms of a fastboot command is fb_mode_clear which gets an OKAY response (although fb_mode_set does too, actually). But no other fastboot commands are functional - I tried fastboot -w and get:
Code:
D:\motopocalypse\motopocalypse>fastboot -w
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.140s
so then I try:
Code:
D:\motopocalypse\motopocalypse>fastboot erase userdata
erasing 'userdata'...
Invalid partition name userdata
FAILED (remote failure)
finished. total time: 0.141s
and so on and so forth. No attempts to erase data nor write it in any manner are successful. RSD Lite basically is useless as well (pic attached below). Since I can't write any data to the device at all then as I've said, it's dead in the water unless a miracle comes along. Was looking at eBay in the hopes of finding a busted/broken AHD (damaged glass, etc) and swapping the mobo from that one back into my housing but they're a bit expensive for busted ones at the moment, guess I'll just keep hoping for that miracle.
I've never used a JTAG or factory cable on any devices I've ever owned but I have to wonder if such a contraption might get this back to a working state. Suppose I'll need to do some research into things - I tried to contact Motorola about it but of course since the AHD is so old now and I'm not the original owner, even though I registered the device in my name they won't honor the warranty without a proof of purchase (meaning the retail one years ago when it was new).
Out of over 100 smartphones and other devices I've owned over the decades this is the first time one's actually up and died on me and go figure: it died when doing an OTA update on a clean stock ROM installation.
How ironic...
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
bmatney said:
Have you tried this http://forum.xda-developers.com/showthread.php?t=2259661
Sent from my LG-D850 using XDA Free mobile app
Click to expand...
Click to collapse
Yep, it's all the same basic process whether it's done scripted or manually, same result: as stated, nothing will flash to the AHD and kicks back the same error each time (partition errors). I have no idea what that damned OTA did but it totally wrecked the whole thing...
Even tried doing this under Linux - the issue isn't with fastboot or the builds, it's with the AHD itself because it's not writing anything I'm trying to flash to the device and I'm confident it's because the partition structure is pooched for whatever reason.
I'm still wondering about using a factory cable (will have to buy one off eBay I suppose) will make any difference at all, I just have no experience using them and if the phone isn't flashing/writing data to the device because the partitions are pooched, I can't imagine using a different albeit specific cable will make that much of a difference.
Bleh... I hate it when crap goes wrong, I really do.
Need some help. This is my 3rd Moto g 2014 XT1063 and my drivers have been removed and r-installed and every time I get the following when trying to get my code to unlock the bootloader
C:\adb>fastboot oem get_unlock_data
...
(bootloader) Failed to get unlock data, please try again!
FAILED (remote failure)
finished. total time: 0.144s
its driving me nuts since I have done this before with no issues
Im using wind 8.1 64bit
tested alternate usb also
Tested 32 and 64bit drivers also
debug is on, drivers work with other devices. I dont know
Also when doing adb devices nothing shows
C:\adb>adb devices
List of devices attached
but I can boot into fastboot using adb commands when phone is plugged in and turned on
when you use the command "adb devices" your device should be listed
its driver issues. Try Motorola Device Manage
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
I did and hot the same results
This was bugging me so I tried the following.
I had an old computer so I freshly installed Windows 8.1 with all the windows updates and installed nothing else other than Firefox.
I installed the ADB drivers as usual and install the Motorola drivers directly from Motorola's website.
The exact same issue occurred with all the commands.
Not sure if this makes a difference for the device was a replacement from Motorola so I'm not sure they could have locked this or something else.
I'm not too sure what to do at this point.
Do you have a solution?
Android51 said:
Do you have a solution?
Click to expand...
Click to collapse
No I was not able to root it
You were not able or your device? Are you stil testing?
Android51 said:
You were not able or your device? Are you stil testing?
Click to expand...
Click to collapse
Testing what? Like I said I was not able to root the phone and after a while I stopped trying. Can't expect a different result after a few days of trying
I have the same problem. But my device is a Moto X Play. In that area, there is nobody with the same problem. So I think there is a way to get the unlock data. In the next few day, I'll try to get the unlock data on a different Laptop/pc.
Today, i have tried it on an another Laptop. Both of the Laptops run Windows 10. It was not successful. Which Software are you running? Maybe the reason is Windows 10?!
By the way, I have contacted the Motorola Support. They wanted to have a Screenshot of the cmd console. I'm waiting for the answer.
Android51 said:
Today, i have tried it on an another Laptop. Both of the Laptops run Windows 10. It was not successful. Which Software are you running? Maybe the reason is Windows 10?!
By the way, I have contacted the Motorola Support. They wanted to have a Screenshot of the cmd console. I'm waiting for the answer.
Click to expand...
Click to collapse
Tested 8.1 and 7.
Im fed up of dealing with Motorola.
I sent my XT1064 for repairs and they sent back a XT1063
I spent 2 hours explaining telling them I needed an XT1064 back since I need the 1700 band
The didn't know what frequencies where and I spoke with 3 people
Are there any follow-ups on this? I have the exact same problem. Been trying to unlock for nearly three months now. Motorola had me send the phone in three times - to no avail.
No, I sold the device to a friend, who doesn't want to root the device. Yesterday, he told me that the normal OTA Update to Android 6.0 Marshmallow doesn't appear. Far as I know, Motorola is already rolling out Android 6.0.1.
Do you get the OTA Update?
Any1 gt out of this issue ?
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Rodrigo_Codina said:
Hi everyone,
I tried to install the CM 13 in my moto X 2014, but I forgot to install Gapps before rebooting my phone. So I had to flash android 6.0 and try all over again. I dont´t know if my mistake in the procedure has something to do with the problems below.
I realized that my phone is not vibrating anymore and the battery drain has been drasticaly increased, like 10% per hour while in idle. When I use my phone (whatsapp, chrome etc) the battery drain seens to be like in idle (no apps running on background).
A full charge takes 4 hours with normal charger or 8 hours if connected to my computer.
I Tried android versions 4.4.4, 5.0, 5.1, 6.0, NX 10.1 and CM13. I don´t know what to do. Motorola assistance said the motherboard is the source of my problems just because i unlocked my bootloader.
Click to expand...
Click to collapse
What is currently installed on each of the phones partitions?
JnNn98 said:
What is currently installed on each of the phones partitions?
Click to expand...
Click to collapse
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Rodrigo_Codina said:
You mean the S.O. version?
I´ve flashed these firmwares via fastboot/RSD Lite 6.2.4.
mega.nz/#F!kd9WULBb!m_X_fQGJ6UnEOMJXzcv-Yw
Click to expand...
Click to collapse
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
JnNn98 said:
I feel like it's possible that you downgraded the bootloader in the process, and that could be the only problem. In that case flash this to get stock, as it'll be the latest firmware.
http://www.filefactory.com/file/13ee8myr4sjh/VICTARA_RETBR_XT1097_6.0_MPE24.49-18_cid12_CFC.xml.zip
Use the instructions from this thread.
http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Also check the cable you're using to charge the phone, with regards to the slow charging.
If there's still things wrong afterwards it is probably a hardware problem. Good luck.
Click to expand...
Click to collapse
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Rodrigo_Codina said:
Sorry I did not reply you earlier, canaval holidays... back to real life today.
I tried what you suggested but without success.
When I try to execute "fastboot flash partition gpt.bin" it fails (I´m not at home right now and I don´t remember exactly the message I got), but all other commands runs like expected.
I saw this thread " forum.xda-developers.com/moto-x-2014/help/managed-to-screw-phone-bootloader-to-t3309241?nocache=1 ". It has a command that in the other you suggested has not.
"fastboot getvar max-sparse-size"
What is it for?
Click to expand...
Click to collapse
The error for the flash partition may be a result of using fastboot and not motorola's own fastboot. I've attached a motorola fastboot in a zip, so you can try again using that fastboot file. The extra commands don't help with anything really because they do not affect the flashing of partitions.
The fastboot getvar command is literally "get variable", so in that case it would just return the maximum file size that can be flashed I believe, and in case you were wondering:
fastboot oem fb_mode_set - Makes the phone automatically reboot into bootloader mode.
fastboot oem fb_mode_clear - Just resets the above commands setting back to normal booting.
The message I mentioned when I execute the command "fastboot flash partition gpt.bin"
sending 'partition' <32KB>...
OKAY [ 0.030s]
writing 'partition'...
<bootloader> Preflash validation failed
FAILED <remote failure>
finished. total time: 0.130s
Nevermind... I was trying to flash an old gpt.bin.
I guess that's the end, I give up. I don't know what to do, nothing works.
I'm thinking of buying an used device with broken screen for 1/3 of the price of a new one (350 reais, almost 100 dollars), disassemble everything and assemble only the motherboard in my device.
I really appreciate your help but I guess I need the Blanckflash and I searched and no one has it because motorola did not released for us.
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
RandyThor said:
I get this error on my moto x dev edition with verizon xt1060 in fastboot. i cant flash any images. i was told to use rsd lite but it doesnt detect my phone.
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
CID Read Failure
Invalid CID status 0x69
CustomerID error. Contact Dealer: 0xdead
Click to expand...
Click to collapse
Do you install Motorola drivers..?
Salik Iqbal said:
Do you install Motorola drivers..?
Click to expand...
Click to collapse
yes the newest drivers are installed. It shows up in device manager as "MOT Single ADB Interface". I can also detect it in fastboot, though most commands won't work.
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
varunpilankar said:
i had a similar kind of problem on my ghost. Firmware crash, due to which phone was stuck at the bootloader. No recovery nor did any fastboot worked at that time. I referred this and this. It worked for me.
Click to expand...
Click to collapse
when following the second link steps i get stuck at step 8. Im not sure what he means by click on the device. does he mean the 'Mot Single ADB Interface' device? i clicked properties on that then i clicked update and i selected the folder where i kept the signed sys files. there was nothing about QHSUSB_DLOAD as it said in the tutorial though. anyway afterwards there was no port called Qualcomm HS-USB QDLoader 9008 so i couldn't get a portnumber to continue the process.
The other link you gave i assumed id go to Moto X BE\1_Repair_Boot (RSD Lite)\1060 and flash the gpt.bin and the motoboot.img but i got this error:
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.290s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 1.210s
C:\Users\Jake\Desktop\New folder\Moto X BE\1_Repair_Boot (RSD Lite)\1060>mfastboot flash motoboot motoboot.img
sending 'motoboot' (1604 KB)...
OKAY [ 0.420s]
writing 'motoboot'...
Motoboot: Unknown partition name
Preflash validation failed
FAILED (remote failure)
finished. total time: 0.700s
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
OrlandoAlex said:
I'm in basically the same situation with my XT1060 Developer Edition. Tried a long list of fixes, none has done the trick. All I have available is the fastboot menu. Phone won't boot into OS, won't go into recovery, hasn't accepted any flashes or erases. This happened because after downgrading to 4.4.4 I allowed an OTA update to 5.1. Phone rebooted and hasn't left the flashboot menu since. I, too, am looking for any help I can get on the matter.
Just like you, I tried that trick involving the fancy drivers, but my phone shows up as "Mot Single ADB Interface" in device manager, so that fix doesn't apply. If my phone reported as QHSUSB_DLOAD in device manager, it would be a different story. Though my phone was rooted and unlocked before downgrading to 4.4.4, at this point it's locked (happened without my knowledge), which I believe is why I can't reflash a recovery image.
It seems pretty clear to me that the phone has either an absent or corrupted partition scheme, as gpt.bin won't flash AND my phone doesn't acknowledge the existence of partitions. I suspect my phone began writing the 5.1 OTA update before erroring out, thus leaving me in a limbo mode halfway between 5.1 and 4.4.4. If anyone out there has experience with this seemingly unique brick situation, I would appreciate it. OP, good luck with your phone.
Click to expand...
Click to collapse
For both of you.. @RandyThor and @OrlandoAlex check thread after 12hrs.. i have something for you which may hopefully fix thay issue.
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
PiArc said:
I'm in the same boat. At least I've finally learned why I always refuse OTA updates (until now it hadn't really dawned on me that I had to blankflash because I downgraded after having updated official firmware).
A solution would be much appreciated, as nothing I've done has worked to this point. I'll read more on here to see whether someone has already posted a solution, and I should be able to check back on this thread in a couple of hours.
EDIT:
It does not look like there is a common solution, from what I can tell in the Q&A. Will search elsewhere next.
Click to expand...
Click to collapse
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Salik Iqbal said:
Was busy and forgot that sorry, i put alarm for that now will update this thread in some hours.
Click to expand...
Click to collapse
No worries. Whenever you get the chance.
RandyThor said:
No worries. Whenever you get the chance.
Click to expand...
Click to collapse
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
PiArc said:
@Salik Iqbal, you've done it! Can you tell me exactly why that worked? Which version of the bootloader was that? Also, THANK YOU!
Click to expand...
Click to collapse
It was from att latest firmware gpt and aboot.
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
you are the GOAT my friend
Salik Iqbal said:
Try this.. 2 things you must needed:
rsd lite too flash xml
battery should be 30%+ means battery okie when you put cable in it.
Caution:
Dont flash it with mfastboot, use Rsdlite to flash the xml. hope your device will boot.
cheers..
https://drive.google.com/open?id=0BxZBxVJDPGZjaUFlSmt4cDFLYW8
Click to expand...
Click to collapse
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
RandyThor said:
One last thing. The phone is working fine now but recovery doesn't seem to work. I've tried reflashing it and it works but when i enter recovery i just get that dead android guy with the error symbol. Any ideas?
Click to expand...
Click to collapse
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
RandyThor said:
Oh nevermind i apologize. My recovery was working fine i forgot i have to hold vol up and tap power to get to the recovery options...
Anyway thanks again you're a life saver!!!!!
Click to expand...
Click to collapse
So lets close the thread by requesting moderator..
Salik Iqbal said:
So lets close the thread by requesting moderator..
Click to expand...
Click to collapse
do i have to do that lol? im a noob
I have never had a phone that has caused headaches like this one!!!
I have a jeter xt1922-2 and for nearly a month now.....suffered problems galore..... Ill explain....so take a seat.....and listen
I unlocked the bootloader the official way, all went swimmingly, then i followed quiksilvers guide to twrp....etc
but suffered problems with the phone in a reboot loop....
so, i thought, as its early days, i will flash a stock rom (i could only find a ALIJETER image, which was the only firmware i could find.....
So i did all the fastboot commands but the bootloader.img and partition thing said fail (phone said BAD KEY) but phone booted, after encrypting......
so for a week or so, I disabled a lot of items, and used non-root adblocker......was enjoying using the phone...
after a bit more time....I thought i would do the ota.....well that installed, and funnily enough, my OEM locking in dev settings was usable again.....so i did that, and installed twrp and root (phone now saying N/A), and had the phone purring like a cat.....but.......
i started to see firmware images becoming available, including JETER firmware, so naturally i downloaded the only one for my region - the UK.... file name : JETER_RETAIL_8.0.0_OPP27.91-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so i tried flashing, but after the same sort of errors as before, it booted into the blue moto screen, and stayed there...
I saw somewhere, that if you relocked bootloader, it should be okay.....
so i tried fastboot oem lock ......... it gave a lot of errors and didnt lock........so i read a few more forums
and was told to try 'fastboot flashing lock' ......... and it worked.....locked again! but when trying to flash anything it failed.....so i tried everything to unlock again, but spent 6 hours trying to sort it, no luck....so i went to bed....
this morning, i thought to myself.........try unlocking via the way i did before, get code from motorola, so did all that, still not unlocked, and thought i would try fastboot flashing unlock .... it unlocked again!!!
and that brings me to the present time.......
tried the jeter firmware.....still the same as before........
tried the original alijeter firmware as i first tried, it boots and works, albeit with the BAD KEY message.....
How did i get that OEM option NOT GREYED OUT in dev settings???
How can i get the OTA to update again, as when i try again, it downloads, but when updating, it goes straight to the BOOTLOADER ...... ?!?!?!
I just want the phone to get back to normal......working twrp, root....etc like i did have it....
Fellow Moto G6 play users....please help a old man!!!!
biggary said:
I have never had a phone that has caused headaches like this one!!!
I have a jeter xt1922-2 and for nearly a month now.....suffered problems galore..... Ill explain....so take a seat.....and listen
I unlocked the bootloader the official way, all went swimmingly, then i followed quiksilvers guide to twrp....etc
but suffered problems with the phone in a reboot loop....
so, i thought, as its early days, i will flash a stock rom (i could only find a ALIJETER image, which was the only firmware i could find.....
So i did all the fastboot commands but the bootloader.img and partition thing said fail (phone said BAD KEY) but phone booted, after encrypting......
so for a week or so, I disabled a lot of items, and used non-root adblocker......was enjoying using the phone...
after a bit more time....I thought i would do the ota.....well that installed, and funnily enough, my OEM locking in dev settings was usable again.....so i did that, and installed twrp and root (phone now saying N/A), and had the phone purring like a cat.....but.......
i started to see firmware images becoming available, including JETER firmware, so naturally i downloaded the only one for my region - the UK.... file name : JETER_RETAIL_8.0.0_OPP27.91-35_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
so i tried flashing, but after the same sort of errors as before, it booted into the blue moto screen, and stayed there...
I saw somewhere, that if you relocked bootloader, it should be okay.....
so i tried fastboot oem lock ......... it gave a lot of errors and didnt lock........so i read a few more forums
and was told to try 'fastboot flashing lock' ......... and it worked.....locked again! but when trying to flash anything it failed.....so i tried everything to unlock again, but spent 6 hours trying to sort it, no luck....so i went to bed....
this morning, i thought to myself.........try unlocking via the way i did before, get code from motorola, so did all that, still not unlocked, and thought i would try fastboot flashing unlock .... it unlocked again!!!
and that brings me to the present time.......
tried the jeter firmware.....still the same as before........
tried the original alijeter firmware as i first tried, it boots and works, albeit with the BAD KEY message.....
How did i get that OEM option NOT GREYED OUT in dev settings???
How can i get the OTA to update again, as when i try again, it downloads, but when updating, it goes straight to the BOOTLOADER ...... ?!?!?!
I just want the phone to get back to normal......working twrp, root....etc like i did have it....
Fellow Moto G6 play users....please help a old man!!!!
Click to expand...
Click to collapse
Bad key is on all Moto devices after you unlock the bootloader. Once you get rid of dmverity it should change to n/a. Don't know why you keep flashing things like that. Your lucky the bootloaders didn't flash.