Related
while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.
I attempted the slapmymoto method in the motoxtool kit and selected verizon
bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?
bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device
i restored completely to stock and am still having the same issue. please help
bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.
I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied
ok sorry i left out a command i think i know what is going on
Code:
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
dray_jr said:
ok sorry i left out a command i think i know what is going on
Code:
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 erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old
sorry but how do I remove the var line?
ive got it figured out thank you for your help
I have a stock pure edition Moto X 2014, I received the update today. It downloads fine, but when it tries to install, it Error, and then reboots, and tells me the install is unsuccessful. This has happened 3 times. I'm rooted, but everything else is stock. How do I troubleshoot or attempt to resolve. I don't even know where to go from here. Thanks for any help!
Can't be rooted. You need a stock system partition.
crap, thanks for the reply. I was worried that was the case. Can I go back?
randyklein said:
crap, thanks for the reply. I was worried that was the case. Can I go back?
Click to expand...
Click to collapse
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
bradley26 said:
Go to http://www.graffixnyc.com/motox.php and grab the 4.4.4 stock image. Extract and place in platforms-tools folder with fastboot.
After downloading the image for your device:
Put your device in fastboot mode.
NOTE: You must use the Motorola fastboot utility to flash (included in the Darwin/, Linux/ or Windows/ directory). Please do NOT use the Android fastboot utility
Follow the flashing steps in the .xml file that was included in the package.
A typical flashing sequence includes all these partitions, but might vary depending on your product - so please use the sequence in the .xml file in your package:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
Hope this helps. Copied and pasted the commands from Motorola.
Click to expand...
Click to collapse
Thanks so much! You are awesome.
For anyone else with this issue, here is how I solved this.
-Download mfastboot v2 from here, extract into your ADB folder.
-Download "Official 4.4.4 Full Restore Images" from http://www.graffixnyc.com/motox.php# and extract. Move recovery.img, boot.img, and system.img into adb folder
-Boot into fastboot, plug in USB
-Using mfastboot v2, run the following commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Reboot and the update should now work. Good luck.
I am at encryption unsuccessful... No fastboot, no recovery.. not adb or mfastboot foes not recognize my device. But computer device managerr shows device...
Any workaround to get mfastboot detect my moto x xt1053.
Thanks
affineer said:
I am at encryption unsuccessful... No fastboot, no recovery.. not adb or mfastboot foes not recognize my device. But computer device managerr shows device...
Any workaround to get mfastboot detect my moto x xt1053.
Thanks
Click to expand...
Click to collapse
If you cant access bootloader fastboot and the device is only black screen and the green light notification you have HARD BRICK.
this means you have downgread the device and you try to update ota to newer version.
If you do this you bricked your phone and there is no solution.
If not try to charge your battery for long time and after try to boot on fastboot mode.
Oh sorry you have xt1053?
This is not moto x 2014.
What device do you have?
Moto g,moto x1 ?
The tread is for moto x2.
papsr6 said:
If you cant access bootloader fastboot and the device is only black screen and the green light notification you have HARD BRICK.
this means you have downgread the device and you try to update ota to newer version.
If you do this you bricked your phone and there is no solution.
If not try to charge your battery for long time and after try to boot on fastboot mode.
Oh sorry you have xt1053?
This is not moto x 2014.
What device do you have?
Moto g,moto x1 ?
The tread is for moto x2.
Click to expand...
Click to collapse
sorry for wrong posting,
my device can boot. run boot up animation after bootloader unlocked warning. and stays at ENCRYPTION UNSUCCESSFUL. Reset button does not work.
Power button works fine. but key combination does not help booting to fastboot or recovery. Have tried "mfastboot reboot bootloader" but it does not sense device.
Device manager detects it as MTP device.
Any help.
I will continue seeking help in xt1053 forum till I get it working.
affineer said:
sorry for wrong posting,
my device can boot. run boot up animation after bootloader unlocked warning. and stays at ENCRYPTION UNSUCCESSFUL. Reset button does not work.
Power button works fine. but key combination does not help booting to fastboot or recovery. Have tried "mfastboot reboot bootloader" but it does not sense device.
Device manager detects it as MTP device.
Any help.
I will continue seeking help in xt1053 forum till I get it working.
Click to expand...
Click to collapse
First time i hear this.
Youmust ask in xt1053 tread if someone know what can you do.
Moto x2 not showing this problem i think.
You are sour you use the right combination of buttons for fastboot mode?
Hold power and volume up for turn off the device first and afte try combination buttons for fastboot bootloader mode.
Is it possible to downgrade from lollipop to KitKat? Is there any guide out there?
I have a simfree uk motox 2014 from Motorola, currently unrooted
Please let me know!
Thanks and happy holidays
If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Edit: You can't just flash factory image to downgrade. See my post below.
_MetalHead_ said:
If your X has an unlockable bootloader you can flash the KK factory image, if it's available for your model.
Click to expand...
Click to collapse
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L
varignet said:
Bear with me as I'm quite new to the motox world (...I have experience with custom roms for other older xperia devices):
1) I purchased the sim-free uk version from motorola, how can I check if my bootloader is locked?
2) if locked, is there a way to unlock it without permanently loosing warranty?
2) do I need to root in order to flash the kk factory image?
Cheers
L
Click to expand...
Click to collapse
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.
_MetalHead_ said:
1.) Go here- http://goo.gl/pt01c
2.) There are no unofficial means to unlock your bootloader. If it is unlockable via Motorola's official tool, it still might void your warranty. I am unfamiliar with warranties anywhere other than the US so you'll need to check and see.
3.) No.
Click to expand...
Click to collapse
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks
fbiryujin said:
Sorry to revive an old thread but there are no bootroms or any files that will have an issue with downgrading if I use the factory image? I remember some phones brick when downgrading. I'm using a pure edition from the U.S.
Thanks
Click to expand...
Click to collapse
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Edit: Also I take it that I should use mfastboot?
fbiryujin said:
Thanks. I Take it RSD Lite is not an option? Don't have the Pure Edition right now. (Returned to get another wood option) I'm just hoping to have options in case it comes with 5.0 (I really want Xposed/XPrivacy)
Click to expand...
Click to collapse
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.
Huh, I had never heard of RSD Lite before... I have just been using mfastboot.
_MetalHead_ said:
It shouldn't come with 5.0. I just got a replacement one last week and it still had KK on it so I'm betting they're all still shipping with KK. Not sure about RSD light, but if you're familiar with fastboot, it really is all quite simple to do. Probably take you 3 minutes total. But again, you shouldn't have to worry. And I agree, xposed is a necessity.
Click to expand...
Click to collapse
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it
fbiryujin said:
That's good to hear. I'm ok with fastboot but I stil get nervous when a command takes a bit of time with it
Click to expand...
Click to collapse
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.
_MetalHead_ said:
Just saw your mfastboot edit, you might have to use it. I haven't done anything fancy on my X, so I've just been using fastboot on my Nexus 5. I guess on the X people have been using mfastboot instead.
And don't be nervous, some things just take longer to flash than others.
Click to expand...
Click to collapse
Thanks. I'll use mfastboot just to be sure (If I even need to downgrade). Now to wait for that Walnut Finish to come back in stock :/
mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
NWKENT said:
mfastboot is especially for Motorola devices..
with the adb commands posted earlier, one could use RSDLite, but one would need to modify the XML file included in the firmware zip, IF an XML file is included, some of the later available firmware doesn't include the XML file..
RSDLite is particular software for Motorola devices..
Sent by my Motorola Droid XYBoard MZ617-32 10.1_ICS 4.04
Click to expand...
Click to collapse
I wonder why they stopped including XML files...
_MetalHead_ said:
You can do it but apparently it's not as simple as flashing the factory image. Here are the instructions, given to me by a friend who got them from Motorola. Proceed at your own risk, I am not responsible... yada yada.
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
Good luck.
Click to expand...
Click to collapse
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.
divergens said:
Just an FYI:
I downgraded back to Kitkat yesterday, and it worked perfectly. Just too many bugs in Lollipop...
I used the steps above, except for flashing the bootloader. I have heard that people have bricked their Moto G trying to flash older bootloaders when going back to Kitkat (something about the bootloader not loading pre-Lollipop kernels or something). Wasn't sure if this would be the same for the Moto X. Thought I would try without it first.
Edit: I used mfastboot as well.
Click to expand...
Click to collapse
So you skipped "fastboot flash boot boot.img"?
No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img
divergens said:
No, that is the kernel I think.
I skipped: fastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.
fbiryujin said:
Ok so just the below steps then?
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
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 (MUST do if going back to KK)
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
So people with the Nexus 6 are stuck with buggy Lollipop. I guess I'm glad I couldn't get the 64GB one I wanted when they sold out so fast.
Click to expand...
Click to collapse
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.
divergens said:
Yep, I think you can skip the reboot-bootloader right after it too. Can't remember if I did that... Of course doing that step won't hurt anything, so just do it anyways I suppose.
Also remember to use Motorola's fastboot when flashing the system image, I don't think the regular fastboot supports such a large image size. I used mfastboot for everything so that I would remember to do it.
Yeah, lollipop bugs need to be ironed out first. I messed around a bit with my friend's Nexus 6 before I bought the Moto X. It was just ridiculously huge. The Moto feels like a more properly sized and refined design, even though the Nexus 6 feels like a stretched out Moto X. I wish 64 GB was available when I bought my Moto, oh well, I will have to make do with OTG.
Click to expand...
Click to collapse
Haha my main device is sadly an iPhone 6 right now, and that's too big. I prefer the size of the iPhone 5S or the first gen Moto X. I want to be able to use the entire device with one hand while being secure in the fact that a movement or gesture won't loosen my grip on it. Sadly the world is just making bigger phones now, and the few smaller ones out there are "cheap" low budget/power options.
let me explain what exactly happened. l was running LiquidSmooth v3.2 on my Moto X. I have flashed few roms previously as well. I was facing no issues whatsoever but still wanted to upgrade to LiquidSmooth v4.0. So this time when I got on fastboot menu
and chose recovery, I got invalid kernel/ ramdisk size error. I was not able to enter recovery menu and this has happened to me for the first time. I chose normal reboot and then even the phone was working fine. But now, things have gone worse. I entered fastboot menu again and by mistake chose factory option instead of recovery. Phone started rebooting i think. As i had installed LiveLog app on my phone all I could see was logs on the screen. I waited for around 45 minutes but phone didnt boot up. I switched off and restarted again but same result. I think it is bricked. Is there any way I can get my phone back to working state? Any kind of help would be appreciated.
Thanks.
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
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 oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
crazyworm said:
Returning to Stock
Step one
Downloading the required drivers and software
Motorola Device Drivers
https://motorola-global-portal.custh...ail/a_id/88481
Android SDK
http://developer.android.com/sdk/index.html
MFastboot(Used for manually downgrading to 4.2.2)
http://mark.cdmaforums.com/X-STUFF/mfastboot-442.zip
For firmware Download from the link below
http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Step Two
Returning device Stock and Locking Bootloader
1. Open your firmware and extract the files to the same folder as adb/fastboot and mfastboot.
2. open a CMD window and CD into the directory that we just extracted all the files too
3. type below commands one by one
Code:
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 oem lock
i recommend wiping your device also but that is up to you if you dont want
to then skip the next two commands and just type the reboot command
fastboot erase userdata
fastboot erase cache
fastboot reboot
after your phone is done rebooting you will be completely stock firmware of your choice
Enjoy
Click to expand...
Click to collapse
you can def do that but if you want to try to bring it back to life without going to stock you can try this.
Flash your custom recovery again threw fastboot. then after that if you can boot into it just reinstall LS rom and try and boot your phone up if no luck then just follow the above guide from my thread and return to stock and redo everything
Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app
d1nesh said:
Thanks for the help guys. I have a question here : Will returning to stock undo root ? And do I have to unlock the bootloader again ??
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yes Root Romoved, don't use last command "fastboot oem lock" if you want bootloader still unlocked
Sound advice above... Except there's no reason to lock your bootloader again. I'd skip that part. And remain unlocked. ?
Thanks a lot. I will try this method today and then flash LiquidSmooth v4.0. Just in case if I face any problem, I'll be back.
Sent from my GT-S5360 using xda app-developers app
I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app
d1nesh said:
I'm facing problems downloading the firmware from the filefactory. Is there any mirror link ?
Also, for this operation do I have to use this file only or can I use LiquidSmooth v3.2 file as well?
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
what carrier is your phone from i will try and find a good like for the stock firmware.
but like i said i would try to just flash the custom recovery and see if you can boot into it. if you can you might not have to go back to completely stock from the recovery you can iinstall liquid smooth rom. it has its own kernel so it should fix the kernel issue and system issues. if not then you can go back to flashing everything to stock.
It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Also, can you please guide me through the steps so that I do not make any mistakes this time. I'm really scared this time and I don't wanna hard brick my phone. I'd be really very thankful.
Sent from my GT-S5360 using xda app-developers app
Thank you for your help, guys.
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA
d1nesh said:
It didn't come with any carrier. I bought it here in India.
Sorry for the noobie question here, but does USB debugginv needs to be on for this, as I dont remember if its on or not.
Click to expand...
Click to collapse
No. USB Debugging does not need to be on when using RSDLite or mFastboot.
d1nesh said:
I think I am back to factory because I'm no longer getting the LiveLogs on the boot up screen. I'm getting the stock Motorola bootup screen that means LiveLogs and all other apps have been removed. But again, I'm still stuck on boot. Its not going past Motorola logo.
One more thing, while returning back to recovery, on cmd screen I was getting <bootloader> Variable not supported error.
PFA
Click to expand...
Click to collapse
At this point, I would consider redoing the steps outlined by @dray_jr earlier in this thread.. with a few tweaks...
its important to be using the correct ROM for your phone. Is there fine print on the back of your phone, does it say XT1052? If so, the link to the Asia XT1052 4.4.4 rom should be correct.
Next... use mfastboot for ALL parts, not just system.img, and follow these steps.. Yes, the are very similar to what you did already, and yes, i know some are repeated, that is intentional.
mfastboot getvar max-download-size
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 reboot
OPTIONAL, but in your case might be necessary: just before the final mfastboot reboot command, issue... mfastboot erase userdata this will erase your apps and data.
If any of these commands fail, please make sure you capture it and post it. (NOTE: there is a way to select and copy on the text from the CMD Prompt window, please do that, rather than screen shot)
Once your phone boots up properly, it will be back to stock, unrooted, but as long as you don't do the "oem lock" command with mfastboot or fastboot, your bootloader will remain unlocked. You can then flash TWRP or other custom recovery and re-root.
INDIA VERSION
This is my first post to this community pardon me for any novice mistakes.
Bought moto x from Flipkart ( Pelase search as i am not able to post link)
Moto X 2013 is a great device in that small size.
Due to OTA delay, i used my guts to flash my Moto X. ( I have flashed Nexus 7 2012 before )
with CM 12
but to flash cm 12 i had to flash cm 11, then cm 12.
This link was helpful (official CM ghost site link )
now there was a bug in device name detecion while flashing ROM. so then only recovery image which worked was cwm recovery (cwm6.0.3.6.img)
But then google Apps got failed with that recovery. to install google aps i installed another recovery twrp. and it wokked.
REAL PROBLEM
I wanted to go back to STOCK ROM
I followed the thread which i used to get my unlock key.
there i found this link after requesting them the access to download
motorola-global-portal.custhelp app/standalone/bootloader/recovery-images
I followed the recovery steps which are as follows..
Alternatively, you can reboot into fastboot mode if you have adb...adb reboot bootloader.
Next flash the images using fastboot:
$ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ 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 reboot
You also have the option to erase all the data on your device with
$ fastboot erase userdata
$ fastboot erase cache
After performing this sequence, you can relock your device with
$ fastboot oem lock
It got Flashed, After it got started i found there was no network.
i checked the IEMI number it is 0.
I panicked and tired going back to CM 12.1. ( in between i got reboot loop ).
But finally after side load and recovery image change i am back to CM 12.1 but i have lost my network. any help will be much appriciated.
You sure you installed xt1052 Asia retail firmware?
If not you need to flash it
Sent from my XT1058 using Tapatalk
Thanks a Million
adity said:
You sure you installed xt1052 Asia retail firmware?
If not you need to flash it
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Please send me the link or file to my email -> [email protected]
Thanks you so much for your help.