Hello guys! After 2 days reading and trying all the methods, i will try to demonstrate the problem here.
My wife Moto X (5.1 Lollipop) start to appear the Camera Problem. Please, reset the camera. Well, after formatting, erasing, etc etc., i found a tutorial in internet to downgrade the Moto X to 4.4.4. Everything ok, procedures ok, deleting this lines from XML.
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="d2a411c57c3f37832702bda0c23484b4" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="2b664024c8a421245b814e3b7c4c5077" />
Moto X start ok, but the camera problem persist. Ok, give back to my wife and she start to use. After 1 day, the OTA 5.1 appear on status bar. And she Accept the OTA. Ok, my bad. I forgot to say to not update.
After the update, phone stuck up on boot failed. And the bootloader locked again.
I tried to unlock bootloader again, no way. Try to flash via RSD 4.2, 4.4, 5.1, no success.
When i try to use RSD, during GPT, error.
Im running out of options.
P.S.: sorry for my bad english, brazilian here.
Solved. Used this file: h t t p s : / / mega.nz/#!7ksR3aaR!Eou63oRpNqFKKUqOdGniAmImPEI22cIvMaX-JRQSkjQ and after "Repair Boot", smart comes alive.
Thanks admin.
Related
AT&T Unlocked Atrix HD.
To recover from a radio band mistake, I downloaded the SBF file matching the current firmware and tried to flash it using RSDLite. Encountered three fail messages. Now, the phone wouldn't even boot and goes into Fastboot saying reason as flash failure. I don't even know why I did all this. I was trying to get 3G and now ending up with an unusable phone.
Can anyone please help me understand what I should do?
Thanks.
Thank heavens for the xml file. I deleted these lines:
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="7FBB0F82F9BB621DB0F1151C59A27D5C" />
<step operation="flash" partition="system" filename="system.img.ext4" MD5="2D89F1EF6C574C6B210F1ABC09DF8011" />
<step operation="flash" partition="cdrom" filename="cdrom"
Deleted those because those were the ones that were failing. Now, I am able to boot into the OS, BUT I am still not getting a signal, thanks to me using "Phone Info" app to select a band. I guess it might be because I could not flash the modem above.
Do I still have options?
Thanks.
Oh My Sweet Lord! It seems to have done the magic. I now have the blessed 4G symbol AND have phone signal! What an experience this has been!
Blue Bell said:
Oh My Sweet Lord! It seems to have done the magic. I now have the blessed 4G symbol AND have phone signal! What an experience this has been!
Click to expand...
Click to collapse
Nice to hear that your phone is ok now.
Sent from my MB886 using xda premium
Hey ,
seems like you guys are my last chance. I will try to explain my situation:
So today I was just messaging when suddenly some process.google.media (cant recall exactly) error was spamming my phone. I restarted the phone and then the problems started happening. The moto X was stuck in the boot screen.
I read that i should install TWRP and factory reset. So after doing that I was pretty much stuck in recovery.
Whenever i turned the phone on, It was immediately booting the TWRP.
So I thought fine, I will probably have to install a ROM, so it can actually boot something.
I went for the xt1052 Lollipop 5.1 untouched EU version of the forum. Still It somehow didnt boot.
Next I came across the following youtube video: youtube /watch? v=ne46LQ3n7nA
(cant post url)
Followed all the instructions in the video and it actually got my phone to work.
I thought that now everything would be just like when I bought my phone.
So I installed the official lollipop update which popped up on my screen.
And now Im stuck again...
Im sitting in Fastboot Mode and get the following error:
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
Fastboot Reason: Invalid CID
Dont know how many threads I read by now on here to find a solution but I cant find any..
I installed RSDLite, but Im not sure which version to use to flash now.
Tried two zip folders, but apparently the xml file was missing.
Im kinda scared to use the wrong zip anyways and screw my phone completely if it isnt already.
Id really appreciate any help since im currently clueless.
Thanks boys!
downgraded security version
update gpt_main version failed
Failed to hab check for gpt_backup: 0x35
This is likely your problem and the result of flashing a lower version onto your Moto x. I would start looking how/if you can recover from a downgrade.
I might add some additional error description to make ppl find this thread in the future :
Stuck in bootloader - Fastboot - cant enter recovery - when choosing any options from fastboot: Load kernel (boot) failed
-----------------------------------------------------------------------------------------------------------------------------------------
Alright seems like i got it working again.
Since this forum helped me so much I want to contribute something to it by giving u guys my solution.
So I stumbled across alot of threads with @KidJoe replying. He really knows his stuff, when it comes to the MotoX.
I dont know how to quote off of other threads, but this quote of KidJoe got me on the right track:
" GPT.BIN is the partition table. Its important. When GPT.BIN and MOTOBOOT.IMG are mismatched from the rom on your phone you could brick when taking an upgrade.
In most cases, the GPT.BIN has matched from model to model when on the same rom (i.e. GPT.BIN from XT1060 4.4.4 rom has matched GPT.BIN of XT1053 4.4.4 rom).
However, try Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html and see what happens. "
Alright so, here is what I grasped:
before things went bad for my phone, I was already on lollipop. Following the youtube video I downgraded it from 5.1 to 4.4.4.
While downgrading I already noticed that some commands failed, which was the gpt.bin stuff.
So after my phone was working on 4.4.4 and I used the Motorola Upgrade to 5.1 , there must have been a problem with the gpt.bin and motoboot.img , just like KidJoe said. Hence why I got stuck in Fastboot.
As I said in the first post, I had to find the right image for my phone.
In the Fastboot mode I saw that I was on 30.BE, and from what I understand that means im on lollipop and since I cant downgrade, I had to find the right lollipop version for my device.
Im also german, so I found this version:
XT1052_GHOST_RETDE_5.1_LPA23.12-15.5_cid7_CFC.xml.zip
KEEP IN MIND, my problem was having the wrong version all along, so you have to find the right version for your smartphone, dont make the same mistake I did!
I found my file on filefactory through this link here:
http://forum.xda-developers.com/moto-x/general/info-tip-web-sites-official-leaked-roms-t2923347
(EDIT: I recommend using something like jdownloader to manage the download)
After I had the right version, I used rsdlite, chose my new file and my phone was working again.
However, I noticed that even tho my phone was working, the rsdlite actually failed somewhere between the lines. (I think it was step 7 or 9)
I was really happy to see my device boot up again, but wasnt happy with those errors and followed this link:
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Option 5.
Now finally all the commands went OKAY in my cmd window.
After the motorola took some time to boot up again, I performed a factory reset via settings.
Just to make sure its fine and it seems like it is.
To end this thread off, I hope KidJoe will read this post.
Big thanks to you, your the man!
And even tho on some posts you came along a bit harsh, which really got me worried my phone would be completely dead, I wish you a nice christmas time dude!
Note- Please read thoroughly and answer my question with the utmost honesty if that is okay------Hello, developers, I am in need of help. I currently own the unlocked (gsm) Motorola Moto G 2nd Generation, US Version. Around February, I rooted my XT1064 with Kingroot. I did this, to get iOS 7 emojis, and nothing else. My phone is soft bricked. I recently recieved an OTA notification for Android 6.0 (marshmallow). While rooted, I tried to update the phone 3 times. Each time, the update downloaded fine, but when it came to installation, it went halfway through, flashed the android bot with the x (for errors) for a half second, then rebooted. About 2 minutes after boot, I receive an on screen pop up saying that "the installation had an error. no changed were made to your moto g" with no error code. After getting tired of this, I went to King Root settings, and did "uninstall and clear root" I kept the root backup checked. So, after unrooting, I factory reset and thought that I was all good with the update because factory reset right? WRONG. It still shows the same error message, even after factory reset. Does anyone know if this is a phone common OTA error, or if King root took some files that were needed for the OTA when I uninstalled? Help, please! PS: Marshmallow has been a long awaited update, and I hope you can help me. PPS: If you tell me to flash stock android, please provide instructions for my specific device. Also, please name the risks involved. I am fine with a soft brick, but tell me if a hard brick is possible.
Please Help
My xt1064 died after the marshmallow update. Ended up buying a new phone.
I have installed custom rom 4.4.4 on moto g2 but after some time i have got an ota update of 5.0 lollipop update & when i have downloaded that update & installed it & after the installation process, when my mobile was restarted, then it shows completely blank screen & it is not switching on neither it shows fastboot mode. Pls help me for resolving this issue.
Try holding the Power+VolumeDown button for a few minutes and see if you can enter Fastboot then. If nothing happens, see if the phone is getting charged.
Try holding the buttons again while the phone is plugged in. Hold the buttons till the notification light goes off and stays in that state (it might turn off and back on a couple of times). Then you might be able to get to fastboot mode. Hope this helps
Excuse my English, I used google translator:
It happened to me for three days with my Moto G XT1069 2 and is happening with hundreds of consumers in Brazil. Motorola is not responsible and their authorized workshops are charging about $ 60 for the device's release. There is a group in a community on Facebook striving for a solution, but so far without success, since they require the release of the MBM CI 5.0 by Motorola.
The technical support company claims to downgrade to Android 4.4.4 KitKat, it is necessary to unlock the bootloader, procedure provided by the company's website, but with warnings that may occur problems with the device. But the problem occurs only at the time of update 4.4.4 KitKat for Lollypop 5 via OTA and not the implementation of the bootloader unlock.
In my opinion Motorola does have full responsabidade by default, because in addition to offering unlocking the bootloader and + firmware Android 4.4.4 KitKat.
I think the way is to report and put pressure on the company and wait for satisfactory results. Meanwhile my Moto G 2 is in "induced coma" waiting for a miracle
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.