Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.
e4noob said:
Purchased used moto g6 (xt1925-6) US unlocked version (that's what the rom says).
I'm a total noob with roms and recovery and so on. I'm hoping someone will tell me the steps briefly and I'll try to look up the detailed steps and try to restore the phone to factory settings.
Here is the situation at hand:
-Phone has twrp recovery (I need to restore the factory recovery. Weird thing is can't seem to find the file to download).
-Has bootloader unlocked (I would prefer to relock it). Not rooted.
-Rom says its the unlocked version (don't know if the phone was actually a different version or not). It receives notification and downloads ota updates but can't install updates.
-Phone was purchased used and it was a hobby fixer project for me. Now I would like to sort out the android end and get rid of it as long as its in perfect condition.
Thanks for helping out with the steps to achieve factory settings. Also, if there is a chance that the phone might have been a different version and it has flashed unlocked rom or something, what would it mean? Can it be restored to factory settings of the unlocked version? Are there any catches to it?
EDIT: I think I have mistakenly used the phrase recovery. The issue in that respect is twrp and I need to remove it and restore default mode so that its back to factory settings.
Click to expand...
Click to collapse
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.
madbat99 said:
Get the stock firmware from here and flash all of the partitions with either fastboot (commands are in the XML) or use RSDlite. Easy peasy
---------- Post added at 02:43 AM ---------- Previous post was at 02:39 AM ----------
Get RSDlite 6.2.4 from here
Or rsd light XML to batch to make a .bat file for fastboot.
If your using RSDlite and wiping data, select flashfile, if keeping data use servicefile.
Click to expand...
Click to collapse
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.
e4noob said:
Hey man, thanks for the quick steps. Feels like it'll take days to decipher the steps. But I'm on it.
Click to expand...
Click to collapse
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!
madbat99 said:
It really doesn't.
Install RSDlite on your PC.
Download the full firmware package.
Put phone in fastboot mode. Plug into PC. Open RSDlite.
Navigate to the firmware package.
RSDlite will extract it and everything.
RSDlite will ask either flashfile or servicefile
Flashfile wipes data, servicefile does not
Install (flash) package.
Done
Root if you want. Instructions are in the forum
Good luck!
Click to expand...
Click to collapse
Thanks. That helps a lot.
e4noob said:
Thanks. That helps a lot.
Click to expand...
Click to collapse
Good luck!
madbat99 said:
Good luck!
Click to expand...
Click to collapse
Again, appreciate the help a lot.
So I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas?
madbat99 said:
Good luck!
Click to expand...
Click to collapse
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )
e4noob said:
Hey man, any idea what might be the issue?
I just tried it out and rsd lite doesn't see the device. Phone has debugging enabled. I browsed around for solutions and followed some common steps. I checked with minimal adb fastboot command 'fastboot devices" and the phone's serial number pops up. Phone is detected by pc (win10) device manager when on fastboot mode. I have installed motorola device manager as well. But so far rsd lite doesn't see the device. Any ideas? I prefer to use rsd lite method for obvious reasons.
(Posting this question a second time. Hope I don't get banned or anything )
Click to expand...
Click to collapse
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.
madbat99 said:
Not sure on that. Did you get the RSDlite that I linked to? Some versions dont recognize device with Windows 10. But the version I linked works for me. In RSDlite, the imei shows n/a but it does show a fastboot device connected.
You have the phone in fastboot mode when connecting?
On that same page I linked, there is an XML to batch program as well. You can turn the XML file from the firmware package into a .bat file. Then you just have to run the .bat file and will run all of the fastboot commands for you (which is what RSDlite does with the XML file)
May be an option if you can't get RSDlite to recognize, but fastboot does.
Click to expand...
Click to collapse
Yes the same version. I have it on fastboot when connecting (also tried normal bootup and pc recognizes phone just fine). Good to know there is the bat file option for last resort. I'll try installing android sdk and may be it'll solve this driver issue. So I'll have to ask you for the steps to make the the bat file and how to make it work.
You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.
Ragarianok said:
You could have also tried Lenovo Moto Smart Assistant. I've used it and it works pretty well.
Click to expand...
Click to collapse
What does it do and how do you use it?
e4noob said:
What does it do and how do you use it?
Click to expand...
Click to collapse
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
I'm gonna try it out if it works for moto g6. Thanks, man.
Ragarianok said:
It has a Rescue function that returns the phone to stock firmware.
Here's the link if you want to try it:
https://support.lenovo.com/us/en/downloads/ds101291
It's fairly intuitive.
Click to expand...
Click to collapse
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?
e4noob said:
Hey man, its very intuitive. It worked in first try and phone is back to stock with stock recovery. Only issue I have is bootloader is unlocked. Should I use minimal adb fastboot to perform a relock command? Are there any other steps to it or just the command?
Click to expand...
Click to collapse
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.
Ragarianok said:
You should be able to run "fastboot oem lock" to re-lock the bootloader.
You may get an error message though; something like "flash signed images" or something like that. Let me know if that happens.
Click to expand...
Click to collapse
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Yup! That's completely normal.
e4noob said:
I'm getting a warning message that it erases all user data and instructing to rerun command to continue. Should I proceed?
Click to expand...
Click to collapse
Do you really need it locked?
Ragarianok said:
Yup! That's completely normal.
Click to expand...
Click to collapse
I'm getting this message.
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.010s]
finished. total time: 0.011s
Related
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
shartwell said:
Got this phone today with my new carrier.
Ran the pwnmymoto apk.
I made the mistake of downloading the latest update because it didn't seem like it actually rooted my phone(No root).
Spent a good amount of time trying all different aspects of things after encountering the reboot loop.
Flashed one of the Rogers(I'm with Fido) firmwares.
"no valid piv block in sp for system"
RSDlite won't detec the device to try again.
It's MotoX xt1058
What can I do? This whole firmware thing is complicated and I just want to restore to stock and never ever touch rooting with this phone again.
Click to expand...
Click to collapse
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
flashallthetime said:
Does fastboot recognize your phone? First thing is forget slapmymoto , you can unlock your bootloader and flash twrp recovery. Second issue rsdlite will only flash your existing carrier firmware with a locked bootloader, flash other sbf firmware requires a unlocked boot loader. Third item is to stop the bootloops try clearing the cache, fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
shartwell said:
Flashboot says USB Connected. I assume that's a yes. My computer does as well but only as "motorola phone" likely because I have no real stuff on the phone now. Oh and the computer makes the little "boop" noise of removing a device.
What are the next steps I have to take to fix things? Thanks for the quick response btw!
Click to expand...
Click to collapse
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
flashallthetime said:
OK , put your phone into fastboot mode by holding down the power button and volume down button for 3 seconds and let go( must he done while phone is completely off) plug your phone in and open a fastboot screen ( I assume you have SDK) right click and hold shift while in SDK platform tools. Type fastboot erase cache
Sent on my Moto X
Click to expand...
Click to collapse
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Follow what flashallthetime is suggesting.
btw, Rogers firmware is correct for your phone as there is no Fido specific firmware.
shartwell said:
I installed the SDK and followed a guide to allow me to use fastboot and other platform tools, but when using "adb devices" I don't have any entries, and when I did the command you mentioned It sticks at "waiting for device."
Seems my phone isn't actually seen by the adb tools.
Click to expand...
Click to collapse
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
flashallthetime said:
Make sure your drivers are up to date, Motorola device manager has the correct drivers
Sent on my Moto X
Click to expand...
Click to collapse
Getting somewhere...
The command prompt can seemingly now interface with my device. It runs commands but clearing the cache didn't fix the problem. I've ran the command though so if there is a next step...
EDIT: Okay it's charing and I can interface with it via cmd. I can now use RTDlite with it as it's battery is charging. Should I flash the other Rogers now? I have my unlock code for the bootloader if that's what I've got to do first.
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Steve-x said:
Yes, reflash it with rsdlite, this is the version you want - Blur_Version.139.12.36.ghost_row.RCI.en.CA
Click to expand...
Click to collapse
It's all fixed up. Thank you everyone who contributed to this! Time to enjoy my phone.
Last thing would be flashing twrp. Does someone have a link to the proper files?
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
flashallthetime said:
Now after your up and running, please don't accept any ota if you are rooted, we expect the Rogers kitkat ota soon. If you accept the kitkat ota while rooted and with a custom recovery you will end up in endless bootloops.
Sent on my Moto X
Click to expand...
Click to collapse
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
shartwell said:
I certainly won't be accepting ota updates while rooted anymore. Like I said I didn't think that it had actually modified anything with my system, otherwise I wouldn't have accepted the ota update.
Where can I find the twrp for moto x 4.2.2? Do I flash through rtdlite as normal?
Click to expand...
Click to collapse
Here's twrp http://forum.xda-developers.com/showthread.php?t=2458449
Flash with fastboot( fastboot flash recovery twrp 2.6.3.IMG)
Place the recovery image in platform tools folder. After it flashes make sure you go directly to recovery by pressing the volume up bottom to make it stick
Sent on my Moto X
I went to flash a new rom and everytime i try to do the set up wizard it force closes when i hit the arrow from the language. I try to reboot into recovery but it either boots to the bootloader and i tried recovery from there and I get nothing or the device just reboots itself.
What can i do to fox this?
I will give you some advice when starting into this ROM scene. What I learned along time ago was always know how to FXZ back to factory with your phone. We have all been where you are and as long as you can get to bootloader there is a way out. So I would fxz back to stock if I were you.
Sent from my XT1060 using Tapatalk
meat-rack said:
I will give you some advice when starting into this ROM scene. What I learned along time ago was always know how to FXZ back to factory with your phone. We have all been where you are and as long as you can get to bootloader there is a way out. So I would fxz back to stock if I were you.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
What is FXZ and how do i get it?
meat-rack said:
I will give you some advice when starting into this ROM scene. What I learned along time ago was always know how to FXZ back to factory with your phone. We have all been where you are and as long as you can get to bootloader there is a way out. So I would fxz back to stock if I were you.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
I have tried rsdlite and my moto x will not show up i have uninstalled and re installed the drivers
GhostSoldier_US said:
I have tried rsdlite and my moto x will not show up i have uninstalled and re installed the drivers
Click to expand...
Click to collapse
Try this:
First, unplug the USB from the phone. Now, turn the phone off.
Next, Hold the VOL DOWN button, and turn the phone back on. You should boot into bootloader mode. The screen should say "AP Fastboot Mode".
NOW, plug the USB cord into your computer. It will probably "search for drivers" and then recognize the phone.
Let us know if this helps...
samwathegreat said:
Try this:
First, unplug the USB from the phone. Now, turn the phone off.
Next, Hold the VOL DOWN button, and turn the phone back on. You should boot into bootloader mode. The screen should say "AP Fastboot Mode".
NOW, plug the USB cord into your computer. It will probably "search for drivers" and then recognize the phone.
Let us know if this helps...
Click to expand...
Click to collapse
Still nothing
GhostSoldier_US said:
Still nothing
Click to expand...
Click to collapse
OK, are you able to use fastboot commands at all? You must have flashed custom recovery at some point if you are able to "flash roms"...
There are some reports where people for whatever reason were unable to use RSD Lite, but the manual restore method worked fine for them.
Assuming that you are able to use fastboot, follow the instructions in this thread (Under MANUAL METHOD):
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also, if you need help with the manual commands, let us know what your carrier/model is.
samwathegreat said:
OK, are you able to use fastboot commands at all? You must have flashed custom recovery at some point if you are able to "flash roms"...
There are some reports where people for whatever reason were unable to use RSD Lite, but the manual restore method worked fine for them.
Assuming that you are able to use fastboot, follow the instructions in this thread (Under MANUAL METHOD):
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also, if you need help with the manual commands, let us know what your carrier/model is.
Click to expand...
Click to collapse
I cant find the moto fastboot (mfastboot) I found a download to it but it doent work
GhostSoldier_US said:
I cant find the moto fastboot (mfastboot) I found a download to it but it doent work
Click to expand...
Click to collapse
The link is IN the thread I linked. Near the top, right under "stock firmware" download link. Please try that link.
samwathegreat said:
OK, are you able to use fastboot commands at all? You must have flashed custom recovery at some point if you are able to "flash roms"...
There are some reports where people for whatever reason were unable to use RSD Lite, but the manual restore method worked fine for them.
Assuming that you are able to use fastboot, follow the instructions in this thread (Under MANUAL METHOD):
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Also, if you need help with the manual commands, let us know what your carrier/model is.
Click to expand...
Click to collapse
I just got it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
GhostSoldier_US said:
I just got it!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WOOOOOOOOOOOOOOOOOO!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Excellent! So you flashed all the partitions manually, and your device is working again, correct?
samwathegreat said:
Excellent! So you flashed all the partitions manually, and your device is working again, correct?
Click to expand...
Click to collapse
Yes did everything manually and it worked like a charm im back up and running installing all my apps now!! Thank you so much!!
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Hi guys, I'll just start things off with saying that I am far from being anywhere near as technologically advanced as the majority of you so I would like your help if possible.
I had wanted to flash back to Stock and unroot my Moto X but for some reason I had gone into TWRP and decided to delete everything. Now every time I try to reboot from TWRP, it'll just say that the phone does not have an OS Installed and therefore if I reboot it, it will just stay on the 'Warning Bootloader Unlocked" screen.
I've read quite a few threads on various forums but I am unable to get my laptop to recognise the device in fastboot. That's my only problem so far as I've downloaded the Motorola Device Manager and all those other things but still cannot get my laptop to show the device for me to put the files into. When I plug it in, I am able to hear the sound and the device recognizes that it's been plugged in but I can't see it on my laptop.
Any and all help is GREATLY appreciated. Thanks guys and forgive my ignorance.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
samwathegreat said:
You don't put files on the phone and you don't use twrp. Follow the instructions in the return to 100% stock thread.
Click to expand...
Click to collapse
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
I've tried following the steps but I was unsure of step 3 where it says to download and install the proper firmware for the device but still unsure on how to install it. RSD Lite won't pick up the device nor will it show up when I type 'adb devices' in CMD. And finally, how do I go about turning on USB debugging when it won't boot up past the bootloader unlock screen?
Appreciate the help
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
samwathegreat said:
Turn the phone off. Unplug it. Hold down VOL DOWN, and press power. The phone will boot into the bootloader. This is how you flash with rsd lite.
Adb does not work in bootloader, and isn't used for this. Once in bootloader (ap fastboot mode), rsd lite should recognize the device.
Make absolutely sure you do not downgrade to a previous version (you will brick), and make sure you flash the correct firmware for YOUR device/carrier.
You can only flash the same version or higher than what you were on before you erased everything.
Click to expand...
Click to collapse
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Thanks for the help! Unfortunately RSD Lite doesn't recognise the device in bootloader. Am I supposed to put the files into a certain place for things to start working properly and is it also because I'm using windows 8.1? I've already installed the Motorola Device Manager as well.
Really sorry for all the questions - complete newbie right here
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
samwathegreat said:
You said you downloaded moto device manager... Did you install it? If so you are one of the unlucky ones and will have to use the manual method with fastboot and mfastboot. Take it slow and follow the instructions. Leave out the config carrier line.
To make sure fastboot is working, type fastboot devices while in bootloader mode.
Click to expand...
Click to collapse
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
Oh okay that makes sense. Yeah I had installed but still nothing. Okay, I'll try the manual method, thanks heaps!
I've typed it fastboot devices in CMD and it came up with T017500PDP fastboot. I assume that's good? Haha
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
samwathegreat said:
Yes perfect.
Run one command at a time - copy/paste them.
Remember to use mfastboot for system.img - regular fastboot will NOT work. Also remember to skip the config carrier command.
Click to expand...
Click to collapse
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
boss. said:
You my friend are a legend. Last round (hopefully) of questions though: where the code says to type in fastboot flash .... .gpt.bin and all those other things, am I supposed to put the files somewhere in particular? Because just regularly typing them into CMD comes up with (bootloader) Variable not supported! Then error: cannot open 'gtp.bin' or cannot open 'recovery.img' and so on but on the phone it says getvar partition-type:recovery or boot and so on.
Also the when the instructions say to use mfastboot, CMD says that it is not recognized as an internal or external command. Thanks!
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Awesome!
samwathegreat said:
First: yes, you have to put those files in the same folder as you are running the commands from. If your command prompt shows C:\users\jimmy\
Then that is where the files should be! You should have extracted the zip file you downloaded to the same folder you are running the commands from.
Second, you obviously have not download mfastboot.exe (it is linked in the return to stock thread) OR you didn't put it in the same folder as the rest of the files.
The "variable not supported" messages are normal. The error cannot open.... errors are NOT.
I'm attaching mfastboot.exe (it's zipped - extract it to the same folder as everything else) to this post so you don't have to go looking for it.
DON'T move on if the first command doesn't work. Make sure each one gives success before you move on.
Click to expand...
Click to collapse
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
boss. said:
Thanks so much, it worked great! The colours are a bit out of wack though (the blues are now orange and so on) and the bot animation is messed but still better than nothing. Thanks so much for your help!
Click to expand...
Click to collapse
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
samwathegreat said:
You're welcome....but that isn't normal. I suggest doing it again from the beginning. A full SBF to stock re-writes all the partitions and there shouldn't be anything "out of wack". Sounds like something went wrong....OR your device has physical damage?
Anyways, please consider hitting the "THANKS" button under any and all posts that help you. :good:
Click to expand...
Click to collapse
Re-did the whole thing from scratch again and now all problems are solved. Really appreciate the help my friend!
Sent from my SM-N9005 using XDA Free mobile app
Help! My Motorola RAZR I XT890 cannot be "unbricked" and I tried several methods...
Hello!
I unlocked the bootloader successfully, then I tried to root my phone using The Razr guy method and I used the "RAZRi_Root_Windows" file, while rooting my phone went to the "warning bootloader unlocked" screen and it just loops forever from that screen, the bat file, showed that it successfully rooted my phone. I tried to fix it using rsd lite, but it never detects my phone, so I searched for a way to make my pc able to detect it, so I found I could use Intel xFSTK, installed it but still nothing it doesn't appear as shown in the tutorial, I even downloaded the dll file that it needed to run, but after running the xFSTK DLDR or something like that, the application is completely empty, and I saw it should show some tools to download something. Also tried using Linux Zorin, but it only says that my XT890 cannot be accessed and shows an usb error code.
I am able to enter the fastboot screen, the one you get by pressing POWER and VOLUME DOWN, also it charges my batter completely normal. Also my pc is able to show that the XT890 is connected, but only before installing the drivers and it shows the CD installer for the Motorola Device Manager and some other files (all this while looping), and if I enter the fastboot flash mode, it appears as "fastboot smi S", with a yellow triangle and an exclamation sign while in Windows device manager. It has Jelly Bean update from telcel (mexico), and I already have the xml.zip file to reinstall it.
I use windows 8.1 , and as mentioned Linux Zorin on my PC.
Could some help me with it...if you now how to fix it please list every single step on how to do it T_T, THANKS IN ADVANCE!!!!
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Hazou said:
It looks like the root method changed something bad in your system partition and that's why it won't boot up. First thing to do is installing the correct Motorola drivers. When in fastboot the device should be normally listed and could be acceded by fastboot. If fastboot is working well, use rsd lite to recover it or flash the system partition manually.
If everything is working well, consider installing a custom recovery and flashing a SuperSU zip for root access.
Click to expand...
Click to collapse
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
weird_user said:
Thanks for answering!!
I've checked on some websites that if the phone is not detected by RSD Lite it maybe due to a bug in the phone's driver that happens only on windows 8/8.1, so I will try to do the same thing on windows 7 and see what happens...
Hope it works...T_T
Click to expand...
Click to collapse
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Thanks again!!!
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
Hazou said:
That could be it.
I just noticed u have unlocked your bootloader. That means u have used fastboot earlier to get the unlock code into the device. So the drivers should work perfectly if u are in the good device modes. Try to flash the system_signed image manually though fastboot and see what happens ("fastboot flash system <path-to-system_signed-image>", u may need mFastboot for that(is inside the rsd-lite package))
Just for the record if u didn't know:
Adb: works only in selected recovery's and normal boot(sometimes in charging mode as well)
Fastboot: works only in AP fastboot mode (power+vol-down, black screen with white/blue text (rsd-lite needs this mode))
XFSTK: works only in medfield flash modues, something u don't need to be with that kind of error
Click to expand...
Click to collapse
I am able to enter RECOVERY MODE NOW (I installed CWM, before this I was only able to see the android lying on the floor ans saty dead right there, I was supposed to press Volume + and - and the camera button at the same time, but nothing happened), it seems to be easier to unbrick it this way, but now the problem is that after I follow the steps to reinstall the original ROM, it aborts installation. I read this may be caused due to a file on the zip file, I looked for it, but nor the Folder META-INF, whic is supposed to contain a "update-script" file, nor that file is anywhere in the ROM folder...
I've even tried cyanogenmod (after first trying Telcel original ROM and then the retail GB ROM) cuz it actually contains the folder previously mentioned and the file is in a different path, but it is there, I modified it, but got a "Can't open tmd/update.zip (bad) Installation aborted" error...I don't know what else to do T_T...
Note: I also used sideload and CWM to install it, but the same thing happens. Also checked some other post about this issue, but none has helped me...
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Hazou said:
What zip file are u installing?
If u want to go back to stock, just use a RSD lite package for 4.1.2 or install TWRP and restore a TWRP backup to go to 4.4.2. There is no official RSD lite package for 4.4.2 and the update.zip doesn't work if your system doesn't boot already.
Click to expand...
Click to collapse
It's done! Thanks!
I actually used another computer with windows 10, also I used RSD Lite and it worked just fine, now I have the stock ROM from Telcel and it it is working almost normal. The only abnormality I've seen is that my phone turns itself off when battery is at 20%, I searched info about that problem and it says I may re calibrate the battery, so it may work fine again, but now I need to root again to be able to do that T_T, hope it works this time...
THANKS! again!
Morning everyone. I'm having some troubling problems with my bootloader. I've had it soft bricked before and was fairly easy to fix. But something is drastically different now. It seems every time I try to restore one of my saved backups, it freezes after a certain point, and sends me back in the boot loader loop. Every time I try to wipe system/data/cache it freezes and back to the bootloader loop. I tried opening a command prompt in adb, but it just says device isn't connected. I can still get into twrp and into the bootloader selection modes. It's just when I do certain things it freezes. For my backup I was able to get it to 36% completed before it froze. My phone is a Moto X 2nd Gen xt1097, and I am running a nightly CyanogenMod on it. Updated it last time about 2 days ago. I just cant find anything on how to fix this. Any help will be much appreciated!! Thanks!
Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?
USA1791 said:
Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?
Click to expand...
Click to collapse
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?
Gus Ghanem said:
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?
Click to expand...
Click to collapse
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.
USA1791 said:
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.
Click to expand...
Click to collapse
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have
Gus Ghanem said:
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have
Click to expand...
Click to collapse
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.
USA1791 said:
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.
Click to expand...
Click to collapse
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.
Gus Ghanem said:
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.
Click to expand...
Click to collapse
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?
USA1791 said:
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?
Click to expand...
Click to collapse
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?
Gus Ghanem said:
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?
Click to expand...
Click to collapse
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.
USA1791 said:
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.
Click to expand...
Click to collapse
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working
Gus Ghanem said:
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working
Click to expand...
Click to collapse
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.
USA1791 said:
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.
Click to expand...
Click to collapse
Yes it looks like fastboot is working, you should delete those screenshots now.
Gus Ghanem said:
Yes it looks like fastboot is working, you should delete those screenshots now.
Click to expand...
Click to collapse
Oh. Okay got them deleted. Didnt think they'd show anything personal?
After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 0 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
USA1791 said:
Oh. Okay got them deleted. Didnt think they'd show anything personal?
Click to expand...
Click to collapse
Sort of, unique to your own phone, like IEMI, Serial Number, etc.
Gus Ghanem said:
After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 9 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
Sort of, unique to your own phone, like IEMI, Serial Number, etc.
Click to expand...
Click to collapse
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!
USA1791 said:
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!
Click to expand...
Click to collapse
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2
New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?
Gus Ghanem said:
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2
Click to expand...
Click to collapse
Oh thanks, I guess they are dated lol.
USA1791 said:
New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?
Click to expand...
Click to collapse
No don't flash supersu, it causes problems
Yes try copying the CM and Gapps zips to you phone, and try flashing them with TWRP...
which version TWRP you have on the phone?