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.
Related
I formatted system in recovery and i dont have a ROM to flash...am i SOL or is there a way to get out of this mess?
You started another thread? here's the rsdlite thread
http://forum.xda-developers.com/showthread.php?t=2446515
Sent on my Moto X
flashallthetime said:
You started another thread? here's the rsdlite thread
http://forum.xda-developers.com/showthread.php?t=2446515
Sent on my Moto X
Click to expand...
Click to collapse
THANK GOD. Someone to help. I need my phone for tomorrow been like this ALL DAY
Prestige_DOPE said:
THANK GOD. Someone to help. I need my phone for tomorrow been like this ALL DAY
Click to expand...
Click to collapse
Just pick the kitkat sbf firmware for your carrier just to make it easy
Sent on my Moto X
Prestige_DOPE said:
THANK GOD. Someone to help. I need my phone for tomorrow been like this ALL DAY
Click to expand...
Click to collapse
follow the steps below
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the 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
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
dray_jr said:
follow the steps below
To Flash back to 4.2.2 Camera Update Manually Follow the Below Steps it is very simple.
1. download the correct 4.2.2 CU firmware for your Carrier
2. open the .zip files and extract the files into your folder with ADB and MFastBoot.
3. Boot your phone into the bootloader
4. Run the 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
fastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
i recommend wiping your device also but that is up to you
Code:
fastboot erase userdata
fastboot erase cache
Click to expand...
Click to collapse
Thank You for your help man. Everything is up and working. Felt like i had a paper weight on my hands
Why flash back to the 4.2.2 camera OTA with an unlocked bootloader?
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 totally forgot I was rooted and had TWRP and I took the OTA update.
Now the phone is in an infinite loop of rebooting.
What do I need to do to remedy this?
Thank you
Same phone, same problem but I was using clockwork mod recovery. You need to flash the stock recovery using Factbook, then the other update will take.
There are some existing threads that will fill you in with the details!
Good luck.
Sent from my Nexus 7 using Tapatalk
There are PLENTY of threads saying you can NOT install the OTA while you have a custom recovery like TWRP or CWM installed. Doing so causes a boot loop. Almost every one of those posts (at least the ones I've made) says if you get into this situation you need to erase your cache to get out of the boot loop
Boot the phone into fastboot/bootloader mode. Then use mfastboot on the PC to erase your cache. Return to stock and try again.
If you are close enough to stock, you can just try to boot the phone into mfastboot mode, flash STOCK recovery, and see if you can install the OTA, or if it will fail (due to varying too much from stock).
this sticky was helpful
MFastboot(Used for manually downgrading to 4.2.2)
MFastboot
For firmware Download pick what firmware you want from the link below... make sure its the one you have. you cannot downgrade
http://sbf.droid-developers.org/phone.php?device=0
reboot to the bootloader
i used only part of the code from the sticky
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
i was then able to then flash OTA whilst keeping the bootloader unlocked, kept root, kept all my files and settings intact.
Ditto. I just downloaded the pre update firmware and extracted the recovery.IMG file and flashed it with flashify uninstalled xposed framework and boom three reboots and the update is done . reinstall xposed framework and all my settings are still there . VZW Dev edition. Didn't even lose root.
Sent from my XT1060 using Tapatalk
That's how it's done simple and effective.
I did that code line that jadeddjay posted but only did the step through the recovery.img. I then rebooted and it worked perfectly and installed the OTA. I then went back into fastboot and installed TWRP and am rooted again.
Hi,
I have a Brazilan version XT1097, bootloader unlocked but no root yet.
I cannot install anything from play store because I get an error that does not say much.
All I did was trying to root using a guide I found that tells you to use CF-Autoroot, but it just did not work.
Then I installed TWRP to see if there was any ROMs available since I came from the Nexus 5 and was used to see tons of ROMs on xda to grab and flash.
To my surprise, none is available so far.
Now I am trying to find the original 1097 images to flash on my device and go back to stock.
Might even give up on root, if necessary, but I need the phone back
Any ideas on how to proceed?
A different problem now
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
leandroqm said:
The user seco2004 (http://forum.xda-developers.com/member.php?u=4946010) has provided me with his backup image.
I followed the steps on the motorola website to flash all the files but my phone is stuck at the bootloader warning message, that one that says that the bootloader is unlocked.
When I entered TWRP to wipe all over again, it says there is no system installed...
Any pointers are most welcome!
Click to expand...
Click to collapse
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
seco2004 said:
I'm not sure if this is what you tried before, but there's pretty much no chance of anything going wrong if you follow the commands:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img (maybe you missed this part? instead of the "system.img", you need to flash the system files one at a time, something like: mfastboot flash system systemfile_1.img, the mfastboot flash system systemfile_2.img, and then proceed with the commands below)
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem config carrier vzw
fastboot oem fb_mode_clear
After all this the phone should boot normally into stock 4.4.4. Sorry for the delay, Tapatalk didn't notify me , hope you got it fixed already.
Click to expand...
Click to collapse
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
leandroqm said:
Yes, I dit it that same night (morning, I should say) by the very same process you described.
Thank you a lot for the images and responses!
Click to expand...
Click to collapse
Did you get it working?
Sent from my XT1097 using Tapatalk
seco2004 said:
Did you get it working?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Yes, absolutely!
I upgraded it to lollipop and rooted right afterwards
How did you get a 1097 stock Lollipop image?
TheAquanox said:
How did you get a 1097 stock Lollipop image?
Click to expand...
Click to collapse
secco2004 shared me his backups
But is it 1097 lollipop or 1095 with the módem from 1097? Can you share dais backup? I'm Being unable to tether and would like to find out if it is the rom or the phone.
Greetings !
It was actually the KK 4.4.4 original images.
I had to update to lollipop right after via OTA.
IDK if secco2004 allows me to share it. Could you PM him, please?
He posted recently on the topic.
Yeah, it was actually the 4.4.4 Brazilian firmware, feel free to share it. For lollipop I have just the flasheable zip.
Sent from my XT1097 using Tapatalk
Since secco2004 said it is ok to share, tell me if you want me to sent it somewhere...
It is the XT1097 4.4.4 brazilian original images.
hey, can I have XT1097 stock images please?
I also need it
I flashed NX CM12.1 v3.0 rom and lost gps.
Someone in the thread said that i have to go back to stock, verify gps is working properly... blah, blah, blah.....
So the thing is that i don´t know what stock image to use on my phone and where to get it.
It is a XT1097.
Can any of you guys help me?
Need help please
I've flashed ATT_XT1097_5.0.2_system_ ext4_ root.zip using Mofo.exe and followed directions to the T but soon as its done flashing I reboot back into fastboot mode to wipe the cache but gives me error hab check failed for recovery failed to validate recovery image boot up failed. Please any help would be a life savor i'm lost. Anyone know where to find recovery.img file for Moto X XT1097 stock image file maybe I can flash in fastboot mode? I just hope I Dont have a bricked device. I am stuck in bootloop mode and can't wipe cache.
Thanks!
I really thank you, it worked for me! :good:
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Speedy712 said:
So the other day I tried to go back to stock from resurrection remix using a stock 5.1 file I found on this website. I used to flash and all that kind of stuff a while ago but haven't in a while and lost my touch. So basically I know I did it wrong and now there is no OS on the phone. I can access both TWRP and Fastboot mode but that's it. When I try to boot it shows the bootloader unlock screen, vibrates and then goes to a black screen that flashes the little android guy with his stomach open every so often. I tried flashing both stock and RR twice and still nothing. Any help would be greatly appreciated!
P.S. I have the Verizon XT1096 Variant.
Click to expand...
Click to collapse
So you have the Motorola USB drivers installed:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Recent versions of ADB/Fastboot.
Latest stock firmware:
firmware.center/firmware/Motorola/Moto%20X%20%282nd%20gen-2014%29/Stock/XT1096/
Probably VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml.zip
Extract the firmware and put the 4 ADB/Fastboot files in the folder with the firmware files.
Boot into Bootloader Mode and connect the phone, make sure the phone says "connected..."
Shift + right-click inside that folder, Open command window here... Paste these commands, BUT CHECK THE NUMBER of sparsechunks your firmware has:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Speedy712 said:
Thank you so much!! I tried this before with no avail. I think the website I used for the commands didn't have the first few that you had. But it worked, my phone booted up. Thanks again so much!
Click to expand...
Click to collapse
You're welcome, glad it worked!
If you want to try custom roms again, I've been using TWRP 3.0.2-1 and it seems to have no issues so far (and I'm running the latest CM Nightlies).
Gus Ghanem said:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
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_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
so with this method you dont have to use the motofastboot?
fakieskr8333 said:
so with this method you dont have to use the motofastboot?
Click to expand...
Click to collapse
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Gus Ghanem said:
If you mean Motorola's mfastboot, no you don't have to, I always use the lastest fastboot to flash stock firmware, custom recovery, etc.
Of course, it's always best to have an unlocked bootloader, but then you lose warranty.
Click to expand...
Click to collapse
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
fakieskr8333 said:
I am on mac so hopefully that is not causing any issues, but I am having the same exact problem as the OP. But I was missing that first command so I am thinking that'll fix it. When in twrp whenever I tried to flash anything or wipe partitions it threw up all kinds of errors about the partitions not being mounted and stuff. Do you think missing that first command would mess up the partition table or something?
This is the errors i got when trying to wipe.
http://imgur.com/0p3lH9Q
I have been out the android scene for over a year now so I am a little rusty lol.
Click to expand...
Click to collapse
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Gus Ghanem said:
The first two commands are not necessary, but they wouldn't cause any problems, nor fix any:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
But before you start flashing anything on a phone, you should have the latest stock firmware on it, so that you have the latest bootloader and partition table. Some versions of TWRP (3.0) may have been corrupting partitions. You should try reflashing the latest partition table and bootloader from the latest firmware, then reflashing the latest TWRP 3.0.2-1.
I'm not familiar with macs... Is the phone encrypted?
Click to expand...
Click to collapse
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
fakieskr8333 said:
no it was never encrypted. I have redownloaded the latest firmware on the chance that my download was corrupted or something. Should I flash the partition and boot images then restart into the bootloader before flashing the rest?
Click to expand...
Click to collapse
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Gus Ghanem said:
I guess it's safest to just flash the whole firmware as I have listed in the commands; these commands are contained in an XML file that comes with the firmware (flashfile.xml), the "reboot bootloader" after the partition table and bootloader flash, comes from Motorola's flashing instructions.
Click to expand...
Click to collapse
Thanks, I am at work now but as soon as I get home I will give it a go. I have been on iOS for over a year now and my moto has been dead since about a month after moto allowed us to unlock the verizon variant. Stupid thing lol.
how do I check the amount of sparsechunks that I have. Sorry for the dumb question
---------- Post added at 02:04 PM ---------- Previous post was at 01:44 PM ----------
I just finished doing this. I am kind of a noob at this so bear with me. I tried this and I get this message that says "Boot up failed" when I try normal powerup. I'm kind of scared..
ABSOLUTE LEGEND
i was stuck since almost 36 hours, good i dint lose hope and smash the x against the wall
YOUR A LIFE SAVER Fakieskr