Related
For those who flashed the 1.29 RUU and are boot looping and a wipe isn't fixing it:
Go into the recovery.
Go to wipe.
Go to advanced.
Tell it to reformat your cache partition.
I've only tested it on one phone but it may be that the RUU is corrupting the cache partition before failing and thus leaving you with a boot looping phone.
Or, since you're already in fastboot...
Code:
fastboot erase cache
CNexus said:
Or, since you're already in fastboot...
Code:
fastboot erase cache
Click to expand...
Click to collapse
Yep, if you have access to a computer, you can also do that as well.
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
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:
Hi Friends,
i lost after flashing to 5.1 nearly 40GB of storage.
i flashed via fastboot.
Any idea to fix this?
Just do a factory reset it happen .after flashing . don't worry when u do a factory reset it will show the storage .
Dont help.
i started from the beginning again and uses this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
fastboot reboot
Click to expand...
Click to collapse
and when i try to get into the stock recovery, i see just a dead android-guy with a red alarm-sign
Hold power and press up once while that is showing.
Muchas Gracias.. it worked.
pauernet said:
Dont help.
i started from the beginning again and uses this:
and when i try to get into the stock recovery, i see just a dead android-guy with a red alarm-sign
Click to expand...
Click to collapse
That is because those are NOT the right commands.
You should be using this (assuming you want to start fresh):
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot format userdata
fastboot reboot
Or this if you want to keep your data:
Code:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot flash radio radio.img
fastboot reboot-bootloader
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot reboot
Both of these methods will not reduce your reported storage space.
I had similar issue i have the 32 GB variant and before I flashed the update 5.1 I had 25.89 or and now I only have 23.03 gbs what gives
beachbum40 said:
I had similar issue i have the 32 GB variant and before I flashed the update 5.1 I had 25.89 or and now I only have 23.03 gbs what gives
Click to expand...
Click to collapse
Same thing happens to me. In fastboot the command "fastboot -w" will fix it. You lose all your data though since it formats everything.
Evo_Shift said:
Same thing happens to me. In fastboot the command "fastboot -w" will fix it. You lose all your data though since it formats everything.
Click to expand...
Click to collapse
How do u do that fastboot w- thing I had to fastboot each IMG one by one when updating.
I dont believe that fastboot -w will work in this instance......pretty sure you need to format the partition.
I have had this happen twice now after flashing the factory images....huge PITA if you dont catch it immediately before loading up your apps and data.
beachbum40 said:
How do u do that fastboot w- thing I had to fastboot each IMG one by one when updating.
Click to expand...
Click to collapse
Yeah, I meant I flashed each image one by one to update to 5.1. Then the first time I booted up I noticed I had 23.03GB available. Then I went back into fastboot and did fastboot -w, it formats everything or whatever, and the next time I boot up it acts like you just did a factory reset but the memory lists 25.98 now. I think fastboot -w must do more than simply reformat the space listed. It spits out a ton of information after you do it like it is creating the proper amount of space rather than simply reformatting what is being displayed.
Evo_Shift said:
Yeah, I meant I flashed each image one by one to update to 5.1. Then the first time I booted up I noticed I had 23.03GB available. Then I went back into fastboot and did fastboot -w, it formats everything or whatever, and the next time I boot up it acts like you just did a factory reset but the memory lists 25.98 now. I think fastboot -w must do more than simply reformat the space listed. It spits out a ton of information after you do it like it is creating the proper amount of space rather than simply reformatting what is being displayed.
Click to expand...
Click to collapse
Ohh OK gotcha yeah I'll give that a shot and see what happens. Thank
Evo_Shift said:
Yeah, I meant I flashed each image one by one to update to 5.1. Then the first time I booted up I noticed I had 23.03GB available. Then I went back into fastboot and did fastboot -w, it formats everything or whatever, and the next time I boot up it acts like you just did a factory reset but the memory lists 25.98 now. I think fastboot -w must do more than simply reformat the space listed. It spits out a ton of information after you do it like it is creating the proper amount of space rather than simply reformatting what is being displayed.
Click to expand...
Click to collapse
Yeah I did what you said and all is back to normal. I have 25.98 gbs like I'm supposed to now.! ? Thanks for your help
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
D.A.N. said:
After following the directions to the T i restarted my phone and now the only thing that is happening is my moto x blinks the android figure. Is my phone bricked? i can get into recovery. How do it fix my phone? Thanks ahead!!!
Click to expand...
Click to collapse
You need to be more specific. Hopefully you didn't downgrade the bootloader or partition table. Can you put the phone in bootloader mode and type this?
fastboot getvar all
You need to find the latest stock firmware for your variant and region, and flash it like this (example from my variant):
fastboot getvar max-sparse-size
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
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
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
D.A.N. said:
Hello, I just tried that and it's stuck at boot loader unlocked screen. Thank you for the advice. Am I able to get past this screen or is it bricked?
Click to expand...
Click to collapse
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Gus Ghanem said:
I don't think it's bricked, it wouldn't show the bootloader unlocked screen. Can you power it off by long pressing the power button, then getiing into bootloader by pressing power and volume down at the same time. then do:
fastboot getvar all
Click to expand...
Click to collapse
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
D.A.N. said:
Yes, i type that in and i get the long list of options. Once i restart the phone I get the blinking android guy again.
Click to expand...
Click to collapse
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Gus Ghanem said:
Can you flash TWRP 3.1.1-0 and boot into it.
fastboot flash recovery twrp-3.1.1-0-victara.img
If you can, then it's not bricked.
https://dl.twrp.me/victara/
Click to expand...
Click to collapse
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
D.A.N. said:
I just did that and it worked, but an error at the bottom says "mismatched partition size (recovery)
it does go into recovery now. Tried to install rom and it reboots over and over into recovery. Weird.
Click to expand...
Click to collapse
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
D.A.N. said:
It says fails to mount data, dalvik, cache and storage. invalid arguement for each is the reason. unable to repair.
Click to expand...
Click to collapse
What storage type should i have?EXT4 or something else?
D.A.N. said:
What storage type should i have?EXT4 or something else?
Click to expand...
Click to collapse
I think it's normally ext4, not sure if it's for all partitions. Data might be f2fs.
Gus Ghanem said:
The "mismatch" is normal because you're flashing a non-stock recovery.
In TWRP, tap wipe, advanced, and do repair for each partition, then do format data. In case you have corrupt partitions.
Click to expand...
Click to collapse
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
D.A.N. said:
It wont let me wipe or repair anything. it just is red all over the place with errors. I seem to be stuck.
Click to expand...
Click to collapse
Even if you reboot TWRP?
Is your stock firmware MPES24.49-18-7
Gus Ghanem said:
Even if you reboot TWRP?
Click to expand...
Click to collapse
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
Your stock firmware files, are they MPES24.49-18-7
I have a XT1097 RETCA
You could try reflashing the partition table and bootloader if you're absoluitely sure you have the latest firmware.
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
D.A.N. said:
yes, i am attempting to restore from twrp a from a folder i have. It seems to be working but said when it started it failed to mount storage so i don't know if it will work? Do you know how to wipe everything completely and start all over again or have I screwed it up to much? Thanks for your help.
Click to expand...
Click to collapse
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
D.A.N. said:
I am wondering if its because I changed the file system type to ext4 and it should be something else. Do you know what the normal file system should be?
Click to expand...
Click to collapse
It is ext4 except data, which is f2fs
File system
\
Gus Ghanem said:
It is ext4 except data, which is f2fs
Click to expand...
Click to collapse
it was the file system types. I changed them to what you said and it wiped them. attempting to reinstall rom and if it works i can try to go to stock again i guess. Thank you Gus for taking time to help.
Gus Ghanem said:
File system
Click to expand...
Click to collapse
I installed stock rooted rom. It booted backed into recovery. I had to reboot into bootloader, rebooted from there and it is turning on. I think something is still screwed up though because it always boots back into recovery.