Related
[UNLOCKED BOOTLOADER ONLY ]
Okay i have found the solution ! but i take no responsability if you brick your phone !
My device is an XT925 ! from Rogers Canada !
I never lost IMEI during this downgrade ! Your bootlader must be unlocked !
1 : Charge your phone !
2 : Download the DROID RAZR HD Utility 1.10 - http://forum.xda-developers.com/showthread.php?t=1970267
3 : Go to fastboot...
4 : Downgrade ( yes is for XT926 but it work for XT925 )
5 : Go to fastboot don't let android start ( push 10 seconds power on - vol- - vol+ if the verizon logo start ...the phone shutdown go back to fastboot )
( i don't try to start the phone with the xt926 rom... )
6 : Download and flash via rsd the rom you want ( work great with O2 and LATAM retail )
( off topic : latam retail have only 3 language ... English spanish port...)
7: Downgrade security error ? or get var error ? Edit the XML Inside the rom : delete the 2 get var line :
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
and delete :
<step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
8 : Enjoy your ics stock rom...
9 : Upgrade to Jelly Bean if available and if you want
ROOT ALL JB ROM ( and ICS rom )
No need to use OTA rootkeeper when bootloader is unlocked !
Flash CWM
http://forum.xda-developers.com/showthread.php?t=1973904
and Flash SuperSU Via CWM
http://download.chainfire.eu/298/SuperSU/CWM-SuperSU-v0.99.zip
Need LTE on JB rom ?
Flash via fastboot your modem and fsg...
fastboot erase modemst1
fastboot erase modemst2
Fastboot flash modem modem_signed
Fastboot flash fsb fsb_signed
I really love the o2 ROM... no bloatware...Fast... many language ( french ... arabic... etc )
OP you're a genius thank you so much for figuring this out!
Hey do you know if the Rogers software will work for Fido? Well I got all of the Fido custom software?
SickBeast said:
OP you're a genius thank you so much for figuring this out!
Hey do you know if the Rogers software will work for Fido? Well I got all of the Fido custom software?
Click to expand...
Click to collapse
Rogers and Fido have the same firmware ! ( XT925.RCI... )
o2qc418 said:
Rogers and Fido have the same firmware ! ( XT925.RCI... )
Click to expand...
Click to collapse
Thanks for that. I'm going back to the stock software because I cannot do tethering on LTE with the jelly bean ROM.
Well done!! Will try that today, kudos to you!!
Do not delete this line
<step operation="oem" var="fb_mode_set" />
Click to expand...
Click to collapse
Why ... if you do not delete ... there are an error when you flash...
This method is listed in many others topics ...
The only line anothers line i have deleted is
<step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
if i don't delete i have the downgrade security error
I really have no error with my XT925 ! from Rogers Canada !
Flashed 4 friend with the O2 rom
matias-c-18 said:
Do not delete this line
Click to expand...
Click to collapse
Why not? I deleted that line and the last line (see below) that was similar. No issues whatsoever, in fact the whole thing worked a treat!
The other line I also deleted was:
<step var="fb_mode_clear" operation="oem"/>
I figured if you're not setting it at the beginning, then there is no need to clear it at the end.
If you have problem with your LTE
Make this before flashing the modem and fsg via fastboot
fastboot erase modemst1
fastboot erase modemst2
Worked perfectly for me now in original Telcel firmware.
Followed steps to the letter.
thank you!!
So, what exactly is the point of the DROID RAZR HD Utility 1.10? I reverted back to stock ICS by deleting that partition line and the getvar line and flashing via RSD Lite.
If you have to delete the <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" /> line, that just means that there's still something irreversible after going JB.
Update: My SD card is not accessible after doing things my way.
Update 2: I think I'm retarded... I had my USB settings in Mass Storage mode (which blocks me from my SD card from my phone).
Hi,
What is that "partition" line do anyway? Can we delete it without consequences ?
Sent from my XT925 using xda app-developers app
I am on stock ICS Telcel Rom with unlocked bootloader.
Tried to upgrade to Brasilian Retail 4.1.2 FW using RDS lite 6.0.
1. The power in the house went down, resulting a Fail in the flashing process.
2. Booting up the phone brings me straight to Fastboot saying: Fastboot reason: Flash Failure.
3. Selecting "Normal Powerup" the phone boots to my stock ICS.
4. I tried flashing the Stock ROM through RDS Lite, but it gives me a "Partition_signed" error
I believe that my Fastboot is somehow corrupted and i want to try the following method to recover:
1. Download Telcel Stock Rom
2. Edit the .xml file removing the lines:
a. <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
b. Getvar line
3. Install the ROM using RDS lite 6.0
Is this the correct way? Also: what does eliminating the "Step operation.." line means?
---------- Post added at 08:21 PM ---------- Previous post was at 07:47 PM ----------
Scourge1024 said:
So, what exactly is the point of the DROID RAZR HD Utility 1.10? I reverted back to stock ICS by deleting that partition line and the getvar line and flashing via RSD Lite.
If you have to delete the <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" /> line, that just means that there's still something irreversible after going JB.
Update: My SD card is not accessible after doing things my way.
Update 2: I think I'm retarded... I had my USB settings in Mass Storage mode (which blocks me from my SD card from my phone).
Click to expand...
Click to collapse
What do you mean when you say: "...That just means that there's still something irreversible after going JB".
elcacho said:
I am on stock ICS Telcel Rom with unlocked bootloader.
Tried to upgrade to Brasilian Retail 4.1.2 FW using RDS lite 6.0.
1. The power in the house went down, resulting a Fail in the flashing process.
2. Booting up the phone brings me straight to Fastboot saying: Fastboot reason: Flash Failure.
3. Selecting "Normal Powerup" the phone boots to my stock ICS.
4. I tried flashing the Stock ROM through RDS Lite, but it gives me a "Partition_signed" error
I believe that my Fastboot is somehow corrupted and i want to try the following method to recover:
1. Download Telcel Stock Rom
2. Edit the .xml file removing the lines:
a. <step operation="flash" partition="partition" filename="partition_signed" MD5="0c0917493a29c487f87434a0997c3048" />
b. Getvar line
3. Install the ROM using RDS lite 6.0
Is this the correct way? Also: what does eliminating the "Step operation.." line means?
Click to expand...
Click to collapse
It shouldn't harm your cellphone, it is weird that it boots normally on your stock ics rom though..
Try to do a full revert to stock and see what it gets you.
My understanding is that the "step operation" delete eliminates some verifications that Rsd lite does before flashing, it is useful if your phone is hanging in some part of the process, it it isn't, it doesn't make any difference (but it normally WILL hang in some part of the process )
Hi Everyone,
First of all, you are welcome to bash my noobness to the moon and back.
I have a VZW DE Moto X, Unlocked Bootloader. I accepted the 4.4.2 OTA update today and it broke Rootcloak for this app that I use, so I decided that I was going to SBF back to 4.4 (I know, mistake #1). So I followed the reference guide to a T to "return device back to stock" and once I was done running the commands, I booted up the phone and now it is in funky colors and I cannot read the display.
So here's where I'm at: I do have two TWRP recoveries on my PC, one from 4.4 and one from 4.4.2. I do have TWRP recovery on the phone, but since I did a device wipe I don't have the recoveries on my phone. Lastly, I can't get ADB to recognize my device now when it is in fastboot mode. so I don't know how to get the recoveries back on my phone. Can anyone save me? I would forever be grateful! :crying:
CartlandSmith said:
adb doesn't work in fastboot mode.
Can you boot into TWRP?
Click to expand...
Click to collapse
yes I can boot into TWRP
No it is gone... there is nothing there
CartlandSmith said:
While in TWRP, connect your phone to your PC via USB cable and open a command prompt in windows and then navigate to where you have adb.exe on your PC. Then type adb devices. Do you see your phone's serial number?
Click to expand...
Click to collapse
No.. it says list of devices attached and there is nothing.
I guess my only question is; how can I flash this if I can't send ADB commands to my phone?
dkoon1987 said:
I guess my only question is; how can I flash this if I can't send ADB commands to my phone?
Click to expand...
Click to collapse
download RSD Lite.
Unzip the file and use the XML file in RSD Lite. The unofficial one I used was pre-rooted.
CartlandSmith said:
you flash in fastboot mode using motorola's fastboot. You said you could get into fastboot mode, right?
The motorola fastboot is in the zip from what he said. I am downloading it now I will check.
Click to expand...
Click to collapse
There seems to be no mfastboot in his zip... I've got it downloaded and I'm reviewing the XML file for the fastboot commands... here is what is contains:
<step operation="flash" partition="partition" filename="gpt.bin" MD5="DA86065451752C9FAA4EE3AE41E91EE5" />
<step operation="flash" partition="sbl1" filename="sbl1.mbn" MD5="9C2172736B46F2B15CAC2E2A3B3A8974" />
<step operation="flash" partition="sbl2" filename="sbl2.mbn" MD5="144CEB8AB2DD962B5D304434383E8D5A" />
<step operation="flash" partition="sbl3" filename="sbl3.mbn" MD5="40CF68C879ADDC29671D9E7834BACCC7" />
<step operation="flash" partition="rpm" filename="rpm.mbn" MD5="A4E0ED1376D8468C7C353795D3D91D5F" />
<step operation="flash" partition="tz" filename="tz.mbn" MD5="D955C418C4F1C2F2D126575BF52CC9AF" />
<step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="933F1588597DD5D9A3D3E26F59957D38" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="5C8C2A8BA7F9E6F77DF5BEC5481A31A9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="B813274A74FF1278A41C19905E76768B" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="9A3EA0D90080200826EE7B50164012BF" />
<step operation="flash" partition="system" filename="system.img" MD5="C4579F834CB69D40E93DEDEBE95ABDBB" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="B98C55D09B5650EE93E49A6252AD7B41" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="EC92255E54062C65AE72A4926361429B" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
Should I flash these all?
Yes you can flash them, you could remove this command if you don't want it to wipe all your installed apps and files:
<step operation="erase" partition="userdata" />
rebretz000 said:
download RSD Lite.
Unzip the file and use the XML file in RSD Lite. The unofficial one I used was pre-rooted.
Click to expand...
Click to collapse
I downloaded RSD lite but I couldn't get my device to show in the list... any ideas?
dkoon1987 said:
I downloaded RSD lite but I couldn't get my device to show in the list... any ideas?
Click to expand...
Click to collapse
You should be able to recover from this as I believe I had the same or similar issue. I had horizontal lines through the boot operation then the screen would go black and I would have to hold the power button down for several seconds before I could get into recovery. I used fastboot to reinstall the fxz linked above and am back up and running. I actually did it twice while trying to push the tether hack. the only difference is that I never installed the new bootloader or GPT.
Sent from my SM-P600 using Tapatalk
---------- Post added at 03:59 AM ---------- Previous post was at 03:58 AM ----------
dkoon1987 said:
I downloaded RSD lite but I couldn't get my device to show in the list... any ideas?
Click to expand...
Click to collapse
Extract the files and use fast boot to install its actually easier than RSD Lite.
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
If you have to flash manually:
fastboot flash partition gpt.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl2 sbl2.mbn
fastboot flash sbl3 sbl3.mbn
etc.
Just do them in order.
Click to expand...
Click to collapse
don't forget mfastboot for system.img.ext4 but I'm not sure it's necessary
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
well it looked to me like Q9Nap included motorola's fastboot but he just called it fastboot. I can tell by the size of the file (210kB) that is it not Google's standard fastboot (157kB). He said he included it for windows, linux and darwin.
Click to expand...
Click to collapse
I made a rescue folder on my server with all images and files before I got the phone so I use my own fastboot files. In any event I'm 99% certain he'll recover just fine from this.
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
got it. I am sure that fastboot.exe in the windows subdirectory is motorola's fastboot for windows.
ITA and if he does, he should send a few dollars Q9Naps way since he would have had to wait for the sbf firmware or factory images otherwise.
Click to expand...
Click to collapse
Ahhhh!!! The X is alive! You guys are the bomb! I don't think you know how much I appreciate this! Thank you so much! And thank you for pointing me to Q9Naps thread as well!
edthesped said:
I made a rescue folder on my server with all images and files before I got the phone so I use my own fastboot files. In any event I'm 99% certain he'll recover just fine from this.
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
So guys... now that I am back to factory... should I be able to restore my backup from 4.4? And then eventually take the OTA? Or should I just stop playing with fire.
CartlandSmith said:
got it. I am sure that fastboot.exe in the windows subdirectory is motorola's fastboot for windows.
ITA and if he does, he should send a few dollars Q9Naps way since he would have had to wait for the sbf firmware or factory images otherwise.
Click to expand...
Click to collapse
And I will be sending some dough his way :good:
dkoon1987 said:
So guys... now that I am back to factory... should I be able to restore my backup from 4.4? And then eventually take the OTA? Or should I just stop playing with fire.
Click to expand...
Click to collapse
I don't believe you can go back because of the bootloader, you can always try but you may end up redo ing the fastboot thing. The fxz is true 4.4.2 so there really is no reason to go back
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
I would be careful with the 4.4 nandroid and no, don't take the 4.4.2 OTA if you are on the 4.4. system but the 4.4.2 bootloader. If you restore to the 4.4 system but are on the 4.4.2 bootloader, you will brick your device if you take the 4.4.2 OTA from what I have read. This is because the 4.4.2 OTA will be trying to patch the 4.4 bootloader and partition table but you are already on the 4.4.2 bootloader and partition table.
http://forum.xda-developers.com/moto-x/moto-x-qa/running-4-4-4-4-2-unlocked-bootloader-t2665531
Anyhow, if you restore to 4.4, but freeze the OTA app and don't take the 4.4.2 OTA unless you are back on 4.4.2 stock.
Click to expand...
Click to collapse
Can he restore it? Also do you still have twrp installed? If so you should be protected. If you just want your data back you can restore then push 4.4.2 with fastboot without any of the erase commands and be upgraded.
Sent from my SM-P600 using Tapatalk
dkoon1987 said:
And I will be sending some dough his way :good:
Click to expand...
Click to collapse
so where's my money? haha just kidding
edthesped said:
I don't believe you can go back because of the bootloader, you can always try but you may end up redo ing the fastboot thing. The fxz is true 4.4.2 so there really is no reason to go back
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
unlocked devices ARE able to downgrade to 4.4, probably 4.2.2 as well; read the updated op and the rest of the thread for details. it's not that much reading.
CartlandSmith said:
I would be careful with the 4.4 nandroid and no, don't take the 4.4.2 OTA if you are on the 4.4. system but the 4.4.2 bootloader. If you restore to the 4.4 system but are on the 4.4.2 bootloader, you will brick your device if you take the 4.4.2 OTA from what I have read. This is because the 4.4.2 OTA will be trying to patch the 4.4 bootloader and partition table but you are already on the 4.4.2 bootloader and partition table.
http://forum.xda-developers.com/moto-x/moto-x-qa/running-4-4-4-4-2-unlocked-bootloader-t2665531
Anyhow, if you restore to 4.4, but freeze the OTA app and don't take the 4.4.2 OTA unless you are back on 4.4.2 stock.
Click to expand...
Click to collapse
you CAN reapply the ota after flashing back to 4.4. the updater script sees that the motoboot parts and gpt are already upgraded and just skips them; you will not brick.
Q9Nap said:
unlocked devices ARE able to downgrade to 4.4, probably 4.2.2 as well; read the updated op and the rest of the thread for details. it's not that much reading.
Click to expand...
Click to collapse
Going to do that now.
Sent from my SM-P600 using Tapatalk
CartlandSmith said:
Ok, good to know. Everyone is scaring me so much on these forums that I will brick my device that I am afraid to even take the OTA myself, lol! I froze the OTA app for now until I am sure I understand the fire I am playing with.
Click to expand...
Click to collapse
Yes this forum is full of conjecture. And at this point I may be adding to it. The whole bootloader thing is a nightmare.
Sent from my SM-P600 using Tapatalk
Hi everyone!!
I was wondering if you could help me. I am a bit of a noob in this flashing phones, so here it goes:
I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked . I am getting very similar errors like this similar thread and it now appears to be Device LOCKED: http://forum.xda-developers.com/moto-x/moto-x-qa/bootloader-bricked-recovered-fail-t2634982/page8
I saw they did something like flashing separate partitions to get it at some point that you could unlock it again or something.
Could you please help me? I am very desperate
Thanks!
I think your phone is full bricked.
I'm from Mexico too
Enviado desde mi XT1053 mediante Tapatalk
motox1983 said:
Hi everyone!!
I was wondering if you could help me. I am a bit of a noob in this flashing phones, so here it goes:
I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked . I am getting very similar errors like this similar thread and it now appears to be Device LOCKED: http://forum.xda-developers.com/moto-x/moto-x-qa/bootloader-bricked-recovered-fail-t2634982/page8
I saw they did something like flashing separate partitions to get it at some point that you could unlock it again or something.
Could you please help me? I am very desperate
Thanks!
Click to expand...
Click to collapse
Assuming you can get to the bootloader screen, you can TRY using RSD Lite or manual method to flash the 4.4.2 SBF:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Just make sure you use the 4.4.2 SBF File for your carrier from here: sbf.droid-developers.org/phone.php?device=0
Good Luck
EDIT: Reading through the thread you linked, it looks like the key was to FIRST, JUST flash the gpt & motoboot.
So using manual method,
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
NEXT, Reboot BEFORE continuing (mfastboot reboot-bootloader)
THEN, you can use the RSD Lite method, or the manual method in the thread I linked.
Let us know if this helps.
motox1983 said:
I got my Moto x in Mexico XT1058 with 4.4.2 preinstalled. I unlocked the bootloader and flashed 4.4 Retail from Tmobile.
Then upgraded via OTA to 4.4.2
Since I lost some configurations (Like disabling 4G) I decided to Flash again to 4.4.2 from Telcel Mexico. It succeded, but came a OTA upgrade and that is when it Bricked .
Click to expand...
Click to collapse
So you had 4.4.2, downgraded to 4.4, and taking the OTA caused you to brick?
That is why there are warnings to NOT downgrade (to 4.4 or below) once you have 4.4.2 on your phone...
What @samwathegreat suggested (using mfastboot to flash gpt.bin and motoboot.img first, then RSDLite to flash full 4.4.2 SBF for your carrier) should hopefully work.
Try and charge your phone to above 80% if at all possible before you start.
It lives now!!!
samwathegreat said:
Assuming you can get to the bootloader screen, you can TRY using RSD Lite or manual method to flash the 4.4.2 SBF:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Just make sure you use the 4.4.2 SBF File for your carrier from here: sbf.droid-developers.org/phone.php?device=0
Good Luck
EDIT: Reading through the thread you linked, it looks like the key was to FIRST, JUST flash the gpt & motoboot.
So using manual method,
fastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
NEXT, Reboot BEFORE continuing (adb reboot bootloader)
THEN, you can use the RSD Lite method, or the manual method in the thread I linked.
Let us know if this helps.
Click to expand...
Click to collapse
Thanks a lot samwathegreat. It helped me change the DEVICE Status to UNLOCKED again, but now I am in a bootloop. It boots every couple of minutes or so. I am going to try a full 4.4.2 flash with RSD Lite to see if it solves. What other reason would you think it would be?
The key is the reboot to boot loader after flashing the gpt.bin and Moto boot.img. That will allow the new boot loader to continue flashing the rest of the images.
You have a mismatched aboot image and it is incompatible with the new images and reports as locked and cannot flash any images until the proper aboot is flashed and the device reboots into the new boot loader.
Edit: I see you have gotten past the boot loader issue already.
Just flash the full XML.zip with RSD Lite and you will be fine.
Bad news
cellzealot said:
The key is the reboot to boot loader after flashing the gpt.bin and Moto boot.img. That will allow the new boot loader to continue flashing the rest of the images.
You have a mismatched aboot image and it is incompatible with the new images and reports as locked and cannot flash any images until the proper aboot is flashed and the device reboots into the new boot loader.
Edit: I see you have gotten past the boot loader issue already.
Just flash the full XML.zip with RSD Lite and you will be fine.
Click to expand...
Click to collapse
Hey guys, bad news. I flashed what it supposed to be the full XML.zip from the sbf droid-developers web page (I am not allowed to post URL links yet) and it all seemed well, but when I turned it off and then back on, it got again into a bootloop, rebooting every couple of minutes . What do you think it would be the reason? I am from Mexico, so I used the Telcel Mexico 4.4.2 firmware, so I don't use any firmware below 4.4 (the other two options are 4.2.2). I noticed that the Telcel 4.2.2 has more files than the Telcel 4.4.2. Any suggestions? Should I try to flash other firmwares?
motox1983 said:
Hey guys, bad news. I flashed what it supposed to be the full XML.zip from the sbf droid-developers web page (I am not allowed to post URL links yet) and it all seemed well, but when I turned it off and then back on, it got again into a bootloop, rebooting every couple of minutes . What do you think it would be the reason? I am from Mexico, so I used the Telcel Mexico 4.4.2 firmware, so I don't use any firmware below 4.4 (the other two options are 4.2.2). I noticed that the Telcel 4.2.2 has more files than the Telcel 4.4.2. Any suggestions? Should I try to flash other firmwares?
Click to expand...
Click to collapse
Is the Telcel Mexico 4.4.2 what you were running when you first got the phone and it was on 4.4.2?
Based on what cellzealot said.. try this...
First, make sure you are using the latest mFastboot.EXE -> download mFastboot, and unzip it. It has folders containing the Windows, Linux and Mac versions of Moto's fastboot.exe. After unzipping, find the windows version of the moto fastboot.exe, rename it to mfastboot.exe (so you don't mix it up with the one that comes with the Android SDK) and move it in your Android SDK Platform Tools folder.. usually C:\Android-Sdk\platform-tools.
Open a command prompt and change to the folder where you unziped the SBF to, and run the following...
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
EDIT the XML from the SBF. and look for the following lines...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxx" />
and right after it, add...
<step operation="reboot">
save it.
Then use RSDLite to flash the entire XML.
KidJoe said:
Is the Telcel Mexico 4.4.2 what you were running when you first got the phone and it was on 4.4.2?
Based on what cellzealot said.. try this...
First, make sure you are using the latest mFastboot.EXE -> download ..., and unzip it. It has folders containing the Windows, Linux and Mac versions of Moto's fastboot.exe. After unzipping, find the windows version of the moto fastboot.exe, rename it to mfastboot.exe (so you don't mix it up with the one that comes with the Android SDK) and move it in your Android SDK Platform Tools folder.. usually C:\Android-Sdk\platform-tools.
Open a command prompt and change to the folder where you unziped the SBF to, and run the following...
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
EDIT the XML from the SBF. and look for the following lines...
<step operation="flash" partition="partition" filename="gpt.bin" MD5="xxxxxxxxx" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="xxxxxxx" />
and right after it, add...
<step operation="reboot">
save it.
Then use RSDLite to flash the entire XML.
Click to expand...
Click to collapse
I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).
Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?
I flashed separately. First edited the XML to flash only gpt and motoboot and rebooted to fastboot. Then modified again XML so it would flash the rest of the SBF. I will see how it works.
motox1983 said:
I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).
Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?
Click to expand...
Click to collapse
I ask about the version because, to play it safer, we want to make sure you are flashing the SBF of what was on your phone... No matter what way the phone got to 4.4.2, the SBF you are using should be of the same 4.4.2 that was on your phone. i.e. don't flash a T-Mobile 4.4.2 if you started out with a Telcel 4.4.2 rom on your phone. And don't flash a Telcel 4.4.2 if you had a Movistar 4.4.2 rom on there.
Post the contents of the XML, its easier to see what might be wrong with it. Or post the original, un-edited XML, and I will make the edits for you.
motox1983 said:
I am not completely sure if the 4.4.2 version stated in SBF is the one I had when I bought it . Maybe it was 4.2.2 and updated to 4.4.2 via OTA and then I unlocked and rooted the device (with 4.4).
Ok, so I flashed the gpt and motoboot as you said, with the modified mfastboot. Then when I modify the XML, and select the file on the RSD lite, comes up an error that says: "Please check input file. Either XML format is wrong or image files associated with it are missing". Am I missing something?
Click to expand...
Click to collapse
Do this instead:
Once you have flashed the gpt.bin and motoboot.img, type "mfastboot reboot-bootloader"
Phone will reboot back into bootloader.
Now, assuming you have extracted the contents of the SBF file to the same folder where fastboot and mfastboot reside, run these commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Now reboot. Is everything back to normal?
KidJoe said:
I ask about the version because, to play it safer, we want to make sure you are flashing the SBF of what was on your phone... No matter what way the phone got to 4.4.2, the SBF you are using should be of the same 4.4.2 that was on your phone. i.e. don't flash a T-Mobile 4.4.2 if you started out with a Telcel 4.4.2 rom on your phone. And don't flash a Telcel 4.4.2 if you had a Movistar 4.4.2 rom on there.
Post the contents of the XML, its easier to see what might be wrong with it. Or post the original, un-edited XML, and I will make the edits for you.
Click to expand...
Click to collapse
This is the XML: When I open it as it comes when I downloaded, It does not get the error, but when I add the line you told me, it gets the error:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_amxmx-user 4.4.2 KXA20.16-1.26 23 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="7ed24e75a2bfb3f8c02be2a269e9881b" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="167bd75bf0414558616f2a5343f7d1f4" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="96acde1a2233244bbf9828cfa041cb75" />
<step operation="flash" partition="system" filename="system.img" MD5="cf6d51b5ae957d150a693cbf3eef4432" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="f247fbd71d9a80821ecdc952c9116893" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="e50401645391cc7acfb96163748d966f" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
Click to expand...
Click to collapse
samwathegreat said:
Do this instead:
Once you have flashed the gpt.bin and motoboot.img, type "mfastboot reboot-bootloader"
Phone will reboot back into bootloader.
Now, assuming you have extracted the contents of the SBF file to the same folder where fastboot and mfastboot reside, run these commands:....
Click to expand...
Click to collapse
@motox1983 yup, that is the other way.
Because if issues people had flashing logo.bin and recovery using the stock fastboot, I usually recommend using mfastboot instead of fastboot with the moto phones.
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
motox1983 said:
This is the XML: When I open it as it comes when I downloaded, It does not get the error, but when I add the line you told me, it gets the error:
Click to expand...
Click to collapse
Edited version..
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_amxmx-user 4.4.2 KXA20.16-1.26 23 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="7ed24e75a2bfb3f8c02be2a269e9881b" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation="reboot">
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="167bd75bf0414558616f2a5343f7d1f4" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="96acde1a2233244bbf9828cfa041cb75" />
<step operation="flash" partition="system" filename="system.img" MD5="cf6d51b5ae957d150a693cbf3eef4432" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="f247fbd71d9a80821ecdc952c9116893" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="e50401645391cc7acfb96163748d966f" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
or use fastboot/mfastboot to do it manually as samwathegreat has just suggested.
KidJoe said:
@motox1983 yup, that is the other way.
Because if issues people had flashing logo.bin and recovery using the stock fastboot, I usually recommend using mfastboot instead of fastboot with the moto phones.
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Edited version..
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_amxmx-user 4.4.2 KXA20.16-1.26 23 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="7ed24e75a2bfb3f8c02be2a269e9881b" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation="reboot">
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="167bd75bf0414558616f2a5343f7d1f4" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="96acde1a2233244bbf9828cfa041cb75" />
<step operation="flash" partition="system" filename="system.img" MD5="cf6d51b5ae957d150a693cbf3eef4432" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="f247fbd71d9a80821ecdc952c9116893" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="e50401645391cc7acfb96163748d966f" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
or use fastboot/mfastboot to do it manually as samwathegreat has just suggested.
Click to expand...
Click to collapse
Still getting the error message . Will try the manual process and let you know. Thanks!
KidJoe said:
@motox1983 yup, that is the other way.
Because if issues people had flashing logo.bin and recovery using the stock fastboot, I usually recommend using mfastboot instead of fastboot with the moto phones.
---------- Post added at 02:39 PM ---------- Previous post was at 02:36 PM ----------
Edited version..
Click to expand...
Click to collapse
It looks like the proper syntax for the reboot is this:
<step operation="reboot-bootloader" />
Perhaps this is why he is getting the error from RSD Lite?
motox1983 said:
Still getting the error message . Will try the manual process and let you know. Thanks!
Click to expand...
Click to collapse
Once you have finished the manual method and reboot, it is normal for the first boot to take longer than usual.
samwathegreat said:
It looks like the proper syntax for the reboot is this:
<step operation="reboot-bootloader" />
Perhaps this is why he is getting the error from RSD Lite?
Click to expand...
Click to collapse
Could be. But I copied it directly from the XML of the Dev Edition 4.4.2 rom (which has it, where as the others up on SBF Dev.org, and the 4.4 and below SBF's are missing it)
samwathegreat said:
It looks like the proper syntax for the reboot is this:
<step operation="reboot-bootloader" />
Perhaps this is why he is getting the error from RSD Lite?
Once you have finished the manual method and reboot, it is normal for the first boot to take longer than usual.
Click to expand...
Click to collapse
Ok, so I finished the manual method and rebooted. I realised that if it is updating or downloading applications it wont reboot, so I stopped them all and after a couple of minutes it rebooted again. Now it has been about 10 min and it has not rebooted anymore. I am not sure if it is alright or is normal or what would be the reason for it to reboot again.
motox1983 said:
Ok, so I finished the manual method and rebooted. I realised that if it is updating or downloading applications it wont reboot, so I stopped them all and after a couple of minutes it rebooted again. Now it has been about 10 min and it has not rebooted anymore. I am not sure if it is alright or is normal or what would be the reason for it to reboot again.
Click to expand...
Click to collapse
So the phone is just randomly rebooting itself? Like it has crashed or something?
All I can say is give it a while and see if it continues to happen. Since we have returned your software to 100% stock, if your phone continues to randomly reboot, I would suspect a hardware issue...but it is difficult to tell.
If it doesn't happen again I wouldn't worry about it, but definitely post back and update us.
samwathegreat said:
So the phone is just randomly rebooting itself? Like it has crashed or something?
All I can say is give it a while and see if it continues to happen. Since we have returned your software to 100% stock, if your phone continues to randomly reboot, I would suspect a hardware issue...but it is difficult to tell.
If it doesn't happen again I wouldn't worry about it, but definitely post back and update us.
Click to expand...
Click to collapse
Ok it is rebooting again now, every couple of minutes I guess it would be a hardware problem. And obviously I lost the warranty when I unlocked. So no last ideas before I give up? hehe
motox1983 said:
Ok it is rebooting again now, every couple of minutes I guess it would be a hardware problem. And obviously I lost the warranty when I unlocked. So no last ideas before I give up? hehe
Click to expand...
Click to collapse
boot into recovery and wipe cache and dalvik
Phone: Moto X (XT1052) India
Version: Kitkat 4.4.2
Problem : Boot Loop, Stuck on Warning Bootloader Unlock
Things Done Till Now :
1. Recovery: Leads to Boot Loop
2. Factory Doesn't Work
3. TWRP flashed ok, REBOOTED, Vol Dwn+Power, Chose Recovery = boot loop again.
4. Downloaded Original Stock Firmware. Flashed all with right commands, went to every forum, done everything right, result boot loop.
5. Tried Relocking Bootloader: Look status failed <too many links>
6. Tried to go back to stock result boot loop.
Actually I think I have tried everything. Should i throw this phone away. I am desparate and frustated. Please tell me I am wrong and there is a way. If I am missing any thing please help me out.
If anny want to have my steps (what i have done so far) with screen shots, I will be happy to post them.
him25tyg said:
Phone: Moto X (XT1052) India
Version: Kitkat 4.4.2
Problem : Boot Loop, Stuck on Warning Bootloader Unlock
Things Done Till Now :
1. Recovery: Leads to Boot Loop
2. Factory Doesn't Work
3. TWRP flashed ok, REBOOTED, Vol Dwn+Power, Chose Recovery = boot loop again.
4. Downloaded Original Stock Firmware. Flashed all with right commands, went to every forum, done everything right, result boot loop.
5. Tried Relocking Bootloader: Look status failed <too many links>
6. Tried to go back to stock result boot loop.
Actually I think I have tried everything. Should i throw this phone away. I am desparate and frustated. Please tell me I am wrong and there is a way. If I am missing any thing please help me out.
If anny want to have my steps (what i have done so far) with screen shots, I will be happy to post them.
Click to expand...
Click to collapse
Try to use the fastboot method of flashing back to stock. It will get rid of everything on the device and replace it.
UbuntuBrandon said:
Try to use the fastboot method of flashing back to stock. It will get rid of everything on the device and replace it.
Click to expand...
Click to collapse
I ahve tried fastboot and mfastboot. But got same result. Boot loop.
him25tyg said:
I ahve tried fastboot and mfastboot. But got same result. Boot loop.
Click to expand...
Click to collapse
Well ain't that a son of a b. Hmm, well have you tried to replace you twrp with the stock recovery?
yeah. I have stock recovery too. Flashed it, but it didn't work.
The batch File
This is my Script
SET fastboot=mfastboot.exe
%fastboot% getvar max-download-size
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% reboot-bootloader
pause
%fastboot% oem lock begins
%fastboot% oem fb_mode_set
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase customize
%fastboot% erase clogo
%fastboot% oem lock
pause
XML file reads
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_retasia-user 4.4.2 KLA20.16-1.38 32 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="260bebe1a4d89dfd6af548099d2df688" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation='reboot-bootloader' />
<step operation="oem" var="lock begins" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="089ed9114b09dfecc28ca703bc8b9d7d" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="c27e0c2289afa4cf2d159c32761fd547" />
<step operation="flash" partition="system" filename="system.img" MD5="62392494a161ce3a4cdf52dcce636723" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="8fb12c2f68505542c017e58efe4428e9" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="88fae0b85f15212e1a181a4ff31c308c" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="lock JCVIDXAVG5J2S3VMIWEB" />
</steps>
</flashing>
him25tyg said:
This is my Script
SET fastboot=mfastboot.exe
%fastboot% getvar max-download-size
%fastboot% flash partition gpt.bin
%fastboot% flash motoboot motoboot.img
%fastboot% reboot-bootloader
pause
%fastboot% oem lock begins
%fastboot% oem fb_mode_set
%fastboot% flash logo logo.bin
%fastboot% flash boot boot.img
%fastboot% flash recovery recovery.img
%fastboot% flash system system.img
%fastboot% flash modem NON-HLOS.bin
%fastboot% erase modemst1
%fastboot% erase modemst2
%fastboot% flash fsg fsg.mbn
%fastboot% erase cache
%fastboot% erase userdata
%fastboot% erase customize
%fastboot% erase clogo
%fastboot% oem lock
pause
XML file reads
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="GHOST" />
<software_version version="ghost_retasia-user 4.4.2 KLA20.16-1.38 32 release-keysMSM8960PRO_BP_2323.031.111.00R" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="partition" filename="gpt.bin" MD5="260bebe1a4d89dfd6af548099d2df688" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="32232cae7ca8459bd52fb9fc9a0e57f6" />
<step operation='reboot-bootloader' />
<step operation="oem" var="lock begins" />
<step operation="oem" var="fb_mode_set" />
<step operation="flash" partition="logo" filename="logo.bin" MD5="5c8c2a8ba7f9e6f77df5bec5481a31a9" />
<step operation="flash" partition="boot" filename="boot.img" MD5="089ed9114b09dfecc28ca703bc8b9d7d" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="c27e0c2289afa4cf2d159c32761fd547" />
<step operation="flash" partition="system" filename="system.img" MD5="62392494a161ce3a4cdf52dcce636723" />
<step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="8fb12c2f68505542c017e58efe4428e9" />
<step operation="erase" partition="modemst1" />
<step operation="erase" partition="modemst2" />
<step operation="flash" partition="fsg" filename="fsg.mbn" MD5="88fae0b85f15212e1a181a4ff31c308c" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="customize" />
<step operation="erase" partition="clogo" />
<step operation="oem" var="lock JCVIDXAVG5J2S3VMIWEB" />
</steps>
</flashing>
Click to expand...
Click to collapse
What operating system are you doing this in? First, some of your syntax is not correct. In addition to that you don't need to lock your bootloader at all - completely unnecessary. Third, even if you do, you don't need the code to do it.
You have the right idea, but messed up syntax. Advise me what your OS is and I will assist you with manual operations and hopefully we can get you fixed up.
Also advise: At the bootloader screen (AP Fastboot Mode), does it say Device Status: 3 Unlocked ?
And finally, how did it get messed up in the first place? Were you on 4.4.4 and attempted to downgrade?
samwathegreat said:
What operating system are you doing this in? First, some of your syntax is not correct. In addition to that you don't need to lock your bootloader at all - completely unnecessary. Third, even if you do, you don't need the code to do it.
You have the right idea, but messed up syntax. Advise me what your OS is and I will assist you with manual operations and hopefully we can get you fixed up.
Also advise: At the bootloader screen (AP Fastboot Mode), does it say Device Status: 3 Unlocked ?
And finally, how did it get messed up in the first place? Were you on 4.4.4 and attempted to downgrade?
Click to expand...
Click to collapse
Operating System : Windows 8
Okay You are right, I don't need to relock the bootloader. Actually Now I juts want my phone to run, I am totally okay about unlocked bootloader. So I am gonna drop it.
About the code, I was searching many forums and found this link :
https://forums.motorola.com/posts/029f68b0a0
But now we can totally drop it.
Yeah My bootloader screen says Devise Status 3, Unlocked. No, I was waiting to get 4.4.4, i was on 4.4.2 when it happened. I was uninstalling couple of games, Ashalpt 8 and Golf. everyhting went great. after a couple of hours just while i was using chrome, everything freezed. Message startung to appear up, chrome freezes, play store freezes, Google service and it got restart. next thing you know I was in boot loop.
Recovery, custom recovery tried everything. found nothing but loop. And I am glad that syntax has some error, i thought it's done. at least now there is hope. Please guide me.
him25tyg said:
Operating System : Windows 8
Okay You are right, I don't need to relock the bootloader. Actually Now I juts want my phone to run, I am totally okay about unlocked bootloader. So I am gonna drop it.
About the code, I was searching many forums and found this link :
https://forums.motorola.com/posts/029f68b0a0
But now we can totally drop it.
Yeah My bootloader screen says Devise Status 3, Unlocked. No, I was waiting to get 4.4.4, i was on 4.4.2 when it happened. I was uninstalling couple of games, Ashalpt 8 and Golf. everyhting went great. after a couple of hours just while i was using chrome, everything freezed. Message startung to appear up, chrome freezes, play store freezes, Google service and it got restart. next thing you know I was in boot loop.
Recovery, custom recovery tried everything. found nothing but loop. And I am glad that syntax has some error, i thought it's done. at least now there is hope. Please guide me.
Click to expand...
Click to collapse
Based on your description of how the issue started, it is possible that this is an actual hardware failure, which I would not be able to help you with. We will hope that it is only a software problem though, and try anyways.
OK, here is my suggestion. (Apologizes if any of this is redundant - I'm just trying to be thorough) This is assuming you never updated past 4.4.2:
Download the full XT1052 SBF file for your variant from here: http://sbf.droid-developers.org/phone.php?device=0
Extract it to the folder on your PC containing "mfastboot".
Place your device into bootloader (AP Fastboot Mode)
Run the following commands, one at a time. If it fails on a particular item, just keep going. Also, don't worry that some commands are being run twice - it is intentional.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot reboot
Do you boot into android? Let me know what, if any errors you receive.
Good Luck! :good:
No result
samwathegreat said:
Based on your description of how the issue started, it is possible that this is an actual hardware failure, which I would not be able to help you with. We will hope that it is only a software problem though, and try anyways.
OK, here is my suggestion. (Apologizes if any of this is redundant - I'm just trying to be thorough) This is assuming you never updated past 4.4.2:
Download the full XT1052 SBF file for your variant from here: http://sbf.droid-developers.org/phone.php?device=0
Extract it to the folder on your PC containing "mfastboot".
Place your device into bootloader (AP Fastboot Mode)
Run the following commands, one at a time. If it fails on a particular item, just keep going. Also, don't worry that some commands are being run twice - it is intentional.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot reboot
Do you boot into android? Let me know what, if any errors you receive.
Good Luck! :good:
Click to expand...
Click to collapse
I have done this too, anyway I did it again but no result. Everything flashed okay. And yet after reboot I am stuck on boot loop and recovery won't work. Same situation.
you were saying it could be hardware problem. How?
him25tyg said:
I have done this too, anyway I did it again but no result. Everything flashed okay. And yet after reboot I am stuck on boot loop and recovery won't work. Same situation.
you were saying it could be hardware problem. How?
Click to expand...
Click to collapse
OK, so nothing failed?
Recovery won't work huh? Are you pressing VOL UP + POWER after you enter recovery? Normally you just get a black screen until you press VOL UP + POWER multiple times. But if you are flashing the full SBF as instructed, recovery really isn't necessary...
How could it be a hardware problem? Good question. These devices have thousands of tiny intricate parts. I won't pretend to be some kind of expert, but random failure is always a possibility. It is rare, but the fact that this whole issue happened seemingly randomly would suggest that a Hardware failure might be the case.
Now, Since the Moto X has only been out for about a year, consider the possibility of getting a warranty replacement! The USA models carry a 1-year warranty. You might check with Moto to see if your XT1052 variant does as well.
Good Luck
samwathegreat said:
OK, so nothing failed?
Recovery won't work huh? Are you pressing VOL UP + POWER after you enter recovery? Normally you just get a black screen until you press VOL UP + POWER multiple times. But if you are flashing the full SBF as instructed, recovery really isn't necessary...
How could it be a hardware problem? Good question. These devices have thousands of tiny intricate parts. I won't pretend to be some kind of expert, but random failure is always a possibility. It is rare, but the fact that this whole issue happened seemingly randomly would suggest that a Hardware failure might be the case.
Now, Since the Moto X has only been out for about a year, consider the possibility of getting a warranty replacement! The USA models carry a 1-year warranty. You might check with Moto to see if your XT1052 variant does as well.
Good Luck
Click to expand...
Click to collapse
Nothing failed Right. I pressed VOL DOWN+POWER, then chose recovery and the screen went blank for about 5 minutes bfore it restarts itself.
No lying Android symbol, nothing.
So I guess its pretty much it. This is hardware failure. This is just two months old phone, and since boot loader is unlocked, the warrenty is void. Replacement can be very costly now i guess.
him25tyg said:
Nothing failed Right. I pressed VOL DOWN+POWER, then chose recovery and the screen went blank for about 5 minutes bfore it restarts itself.
No lying Android symbol, nothing.
So I guess its pretty much it. This is hardware failure. This is just two months old phone, and since boot loader is unlocked, the warrenty is void. Replacement can be very costly now i guess.
Click to expand...
Click to collapse
OK First, it is normal to have the screen to blank after you enter recovery. Once you see the blank screen, you are supposed to press VOL UP + Power (sometimes multiple times) before the recovery with the dead android appears.
Second, many people have advised that even though they unlocked their bootloader, Moto replaced the device under warranty anyways. I'm not saying that they WILL, just that they have for others in the past. It is definitely worth checking with them to see if they will replace it. If they don't ask you, don't mention that you unlocked it.
Hope you are able to obtain a replacement.
samwathegreat said:
OK First, it is normal to have the screen to blank after you enter recovery. Once you see the blank screen, you are supposed to press VOL UP + Power (sometimes multiple times) before the recovery with the dead android appears.
Second, many people have advised that even though they unlocked their bootloader, Moto replaced the device under warranty anyways. I'm not saying that they WILL, just that they have for others in the past. It is definitely worth checking with them to see if they will replace it. If they don't ask you, don't mention that you unlocked it.
Hope you are able to obtain a replacement.
Click to expand...
Click to collapse
So I guess I will keep trying this recovery option or mAaay be twrp till tommo. First thing in the morning will be mOto serivice centre. I hope they replace it.
Thanks for guiding me.
replaced
samwathegreat said:
OK First, it is normal to have the screen to blank after you enter recovery. Once you see the blank screen, you are supposed to press VOL UP + Power (sometimes multiple times) before the recovery with the dead android appears.
Second, many people have advised that even though they unlocked their bootloader, Moto replaced the device under warranty anyways. I'm not saying that they WILL, just that they have for others in the past. It is definitely worth checking with them to see if they will replace it. If they don't ask you, don't mention that you unlocked it.
Hope you are able to obtain a replacement.
Click to expand...
Click to collapse
So, it was a hardware failure and moto x replaced it
Yo moto
I recieved 5.1 OTA but want to go back to 4.4.4.
As I found out, Moto says, that we cant donwngrade to 4.4.4 with RSDlite. So I want to install TRWP and use a backup to install 4.4.4
In best case there is a backup of the Stock-Rom. Is there one? If not, which one is the one nearest to the stock (moto x features, ....)
if you want to use the motorola features than you need stock rom. ask someone to make twrp backup of system and boot running 4.4.4 and flash it in your device
T-1311 said:
I recieved 5.1 OTA but want to go back to 4.4.4.
As I found out, Moto says, that we cant donwngrade to 4.4.4 with RSDlite. So I want to install TRWP and use a backup to install 4.4.4
In best case there is a backup of the Stock-Rom. Is there one? If not, which one is the one nearest to the stock (moto x features, ....)
Click to expand...
Click to collapse
You can use this ROM or just delete few lines from XML in FW for RSD.
If You delete this lines
Code:
<step operation="getvar" var="max-download-size"/>
<step operation="oem" var="fb_mode_set"/>
<step MD5="e059929f2668935282b8248b028d015d" filename="gpt.bin" operation="flash" partition="partition"/>
<step MD5="2b664024c8a421245b814e3b7c4c5077" filename="motoboot.img" operation="flash" partition="motoboot"/>
You can flash stock 4.4.4 ROM with RSD.
Really? I'm already on STOCK 5.1_OTA. As I wrote I can't flash 4.4.4 through RSDlite.
T-1311 said:
Really? I'm already on STOCK 5.1_OTA. As I wrote I can't flash 4.4.4 through RSDlite.
Click to expand...
Click to collapse
Is your phone bootloader locked? Hardware model, installed system version? More details, pls.
You could flash via fastboot then. Or I can give you 4.4.4 TWRP, but it's for unlocked only.
Sorry, here are the missing infos
XT1052
Bootloader locked (but will be unlocked soon)
Stock 5.1 recieved automaticaly OTA
Baseband MSM8960PRO_BP_23255.138.89.00R
System: 222.21.15.ghost_row_Retail.en.DE
LPA23.12-15
T-1311 said:
Sorry, here are the missing infos
Click to expand...
Click to collapse
Good. Now I get why can't you install via RSD. Unlock it as soon as possible, but don't flash anything (especially including bootloader). I'll give you TWRP flashable 4.4.4 today evening.
P.S. And I also need your byke and clothes modem dump ) Instructions will follow.
. . .
UPDATE. Well, it isn't ready yet (( But after unlock you can flash any system+boot easily by fastboot commands:
fastboot flash boot boot.img
fastboot flash system system.img
But DON'T flash bootloader!!! It can brick the phone
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
Or similar in RSD:
<step operation="flash" partition="partition" filename="gpt.bin" MD5="e83806da807e62fd6ffa08e330abe582" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="2b664024c8a421245b814e3b7c4c5077" />