Okay, guys...
I have a big, big, big issue and If it's possible, I'd like all the help in the world.
I unlocked my bootloader, upgraded to mm 6.0 and decided to root and install TWRP because bloatware, right?
Anyways, I did a big no-no and after a series of unfortunate events, I don't have a recovery and I can only boot into the bootloader.
Don't ask HOW I got here, I couldn't tell you with a gun to my forehead.
Now, I have tried ways to get myself out of this:
Installed an earlier TWRP recovery - doesn't work
Installed CM recovery - Doesn't work
Looked on motorola.ca for stock images - doesn't work
I can boot my phone with TWRP but I can't install it. (the inapropriate partition size error in pink)
whatever. Whenever I boot into twrp, I see all my partitions and with modifications on, I cannot format my /sdcard/ partition (internal memory)
it was being detected by my pc a few times and after a few more tries to flash ANY rom compatible with my phone, I simply have no luck.
Any advice right now is more than appreciated!
Awaiting answers with impatience.
EDIT: Forgot to mention the model number is the XT1097 canadian Moto X 2014 (Telus mobility)
Thanks for the help in advance
Have you tried this? Put ROM/gapps on internal storage. Fastboot boot twrp, then flash ROM/gapps with twrp. Once booted you should be able to install twrp via playstore without the partition mismatch issue. I had to go this route to get twrp to stick on my XT1096
I cannot access the internal memory for some reason!
I hear my pc make a sound for connected but it doesn't show up in explorer
Have you tried ADB sideload? Try flashing the stock MM Rom Zip located in the Moto X 2014 XDA Thread. It might work, if it doesn't, I can send you a toolkit that might fix the phone.
I did try to sideload and I get the following:
Installation failed: unable to mount (all the partitions are listed)
E: Failed to mount
E: Can't mount
And if you're talking about RDS Lite, I am completely unable to find my phone with it.
What I really need is a tool that will fix the partition table.
I don't know how, but I messed it up REAL GOOD!
also, for some reason I Have 2 recoveries atm.
When I completely power off my phone and then power on, I boot into the CyanogenMod Recovery.
THEN, when I reboot into recovery, I go into the TWRP recovery.
And every time afterwards I Reboot to recovery, I come back to the TWRP
Install Motorola USB Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Download and keep full firmware VICTARA_RETCA_XT1097_6.0
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
If you are able to flash with fastboot, maybe you can go back to stock, then go on from there.
Try these, one by one:
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
I know you wouldn't, but hope you do. But if you could tell me how you got here, I could assist you better.
Thank you, Mate!
This restored my phone to retail!
I am in your debt!
You're welcome. We are all here to help each other.
Hi, I am in the exact same situation right now. I tried the fastboot method to flash all the files for the XT1096 VZW version. Every time I boot up after flashing everything, the dead andy with read exclamation point 'No Command' logo pops up and blinks every 5 seconds or so. Any help please? Thanks!
So I managed to get TWRP to install. Now I can't flash anything. All the partitions are somehow corrupted and I can't mount anything. Any ideas on how to fix the partitions?
OK
My apologies, Gus. I just posted a new QA thread on here. Can we discuss there? Thanks.
Related
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 I don't know what to do at this point. I will try to provide as much info as I can for you guys to help me out. I bought the Verizon 2014 Moto X variant off Swappa new. The phone was new, but old. It was manufactured in 2014 and upon first boot, it still had KitKat installed. I OTA'd all the updates before unlocking the bootloader from Motorola's website. After unlocking the bootloader, I tried flash TWRP recovery via fastboot. It didn't work - I got a pink message line on the output that I don't remember what it said. I read that there were some issues installing recovery for VZW (?) so using flashify was my other option. So I then rooted the phone and used flashify to install TWRP. It worked. After that, I flashed a 2014 MM Pure Edition rom. It booted fine, but no signal. Yes, I forgot that it doesn't support CDMA, so I then went tried to flash CM13. Today, I started experiencing battery drain on radio and wifi so I tried to flash the official firmware of 5.1 VZW Victara variant. Fastboot and drivers are running fine and fastboot recognizes the phone. So I flashed everything, booted up, and...nothing. Every time I tried to reflash the firmware, I boot to a blinking No Command dead andy screen. Guess recovery wasn't installed? It just kept bootlooping. Out of desperation, I went to see if TWRP worked - it did. Now I ADB pushed the CM13 rom files on my phone to flash. Unfortunately, every time I try to flash anything, every partition is unable to be mounted. I can't factory reset, flash, nothing. Every time I try to wipe, one of the errors is, 'Failed to mount '/data' (Invalid Argument)'. Now at this point, this is where I'm stuck. I still have the bootloader/fastboot, a recovery, but no OS and I can't flash anything. Fastbooting the firmwares won't go through to boot. Can anyone help me on this? I will provide answers to any questions you have. Thanks.
EDIT: I tried to turn off the phone to prevent the phone from dying but I can't even do that. Tried to turn it off via TWRP but it just reboots to TWRP. I have to keep it plugged in. Sigh.
DroidOnRoids said:
So I don't know what to do at this point. I will try to provide as much info as I can for you guys to help me out. I bought the Verizon 2014 Moto X variant off Swappa new. The phone was new, but old. It was manufactured in 2014 and upon first boot, it still had KitKat installed. I OTA'd all the updates before unlocking the bootloader from Motorola's website. After unlocking the bootloader, I tried flash TWRP recovery via fastboot. It didn't work - I got a pink message line on the output that I don't remember what it said. I read that there were some issues installing recovery for VZW (?) so using flashify was my other option. So I then rooted the phone and used flashify to install TWRP. It worked. After that, I flashed a 2014 MM Pure Edition rom. It booted fine, but no signal. Yes, I forgot that it doesn't support CDMA, so I then went tried to flash CM13. Today, I started experiencing battery drain on radio and wifi so I tried to flash the official firmware of 5.1 VZW Victara variant. Fastboot and drivers are running fine and fastboot recognizes the phone. So I flashed everything, booted up, and...nothing. Every time I tried to reflash the firmware, I boot to a blinking No Command dead andy screen. Guess recovery wasn't installed? It just kept bootlooping. Out of desperation, I went to see if TWRP worked - it did. Now I ADB pushed the CM13 rom files on my phone to flash. Unfortunately, every time I try to flash anything, every partition is unable to be mounted. I can't factory reset, flash, nothing. Every time I try to wipe, one of the errors is, 'Failed to mount '/data' (Invalid Argument)'. Now at this point, this is where I'm stuck. I still have the bootloader/fastboot, a recovery, but no OS and I can't flash anything. Fastbooting the firmwares won't go through to boot. Can anyone help me on this? I will provide answers to any questions you have. Thanks.
EDIT: I tried to turn off the phone to prevent the phone from dying but I can't even do that. Tried to turn it off via TWRP but it just reboots to TWRP. I have to keep it plugged in. Sigh.
Click to expand...
Click to collapse
So you have the full stock firmware 5.1 for Verizon XT1096, like the one here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Can you try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
TWRP 3.0 seems to be causing problems, maybe corrupting partitions, stick to 2.8.7.1 or earlier.
http://www.invisiblek.org/
Maybe we can try RSD Lite...
Gus Ghanem said:
So you have the full stock firmware 5.1 for Verizon XT1096, like the one here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg
Can you try:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
TWRP 3.0 seems to be causing problems, maybe corrupting partitions, stick to 2.8.7.1 or earlier.
http://www.invisiblek.org/
Maybe we can try RSD Lite...
Click to expand...
Click to collapse
I did not get the file from there, but instead got it from AFH. As for the 2 fastboot commands, what should I do with them? They flashed fine when I was putting them in fastboot earlier. As for TWRP, I will flash to 2.8.7.1.
As for RSD Lite, I am running Windows 10 and several versions I have tried will not recognize the phone at all. I'm 95% sure the drivers are in OK status and I am using the OEM cable.
DroidOnRoids said:
I did not get the file from there, but instead got it from AFH. As for the 2 fastboot commands, what should I do with them? They flashed fine when I was putting them in fastboot earlier. As for TWRP, I will flash to 2.8.7.1.
As for RSD Lite, I am running Windows 10 and several versions I have tried will not recognize the phone at all. I'm 95% sure the drivers are in OK status and I am using the OEM cable.
Click to expand...
Click to collapse
I downloaded your firmware just to check the number of files, and the flashfile.xml, and it's exactly like this:
VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml
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
fastboot reboot
Gus Ghanem said:
I downloaded your firmware just to check the number of files, and the flashfile.xml, and it's exactly like this:
VICTARA_VERIZON_XT1096_5.1_LPE23.32-25-5_cid2_CFC.xml
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
fastboot reboot
Click to expand...
Click to collapse
I appreciate you providing help so far. I downloaded the firmware you linked, fastbooted line for line, rebooted, bootloader unlock warning pops up, then the next boot sequence is just the blinking dead andy No Command logo that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm still stuck. I'm going to flash the 2.x.x TWRP version again. But that's all I'll be able to get right now. Still not able to get an OS installed.
DroidOnRoids said:
I appreciate you providing help so far. I downloaded the firmware you linked, fastbooted line for line, rebooted, bootloader unlock warning pops up, then the next boot sequence is just the blinking dead andy No Command logo that looks like this:
I'm still stuck. I'm going to flash the 2.x.x TWRP version again. But that's all I'll be able to get right now. Still not able to get an OS installed.
Click to expand...
Click to collapse
Any errors on the phone during fastbooting firmware files, like "downgrading" etc.
I hope TWRP 2.x will allow you to flash CM.
UPDATE: So I made a little progress. There was a problem mounting and this thread helped with that: http://forum.xda-developers.com/showthread.php?t=2683787
Now I can wipe data, factory reset, flash, etc. in TWRP v2.8.7.1. But when I flash a rom, I reboot system and it boots back to recovery. WTF. Ugh.
EDIT 2: Sad news. Based off this thread, http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147, looks like I FUBAR'd the phone. Unfortunate that this phone isn't like a Nexus.
its the phone will reboot back to TWRP event you restore backup file on TWRP ?
did you try flash custom rom from TWRP?
---------- Post added at 05:33 PM ---------- Previous post was at 05:32 PM ----------
DroidOnRoids said:
UPDATE: So I made a little progress. There was a problem mounting and this thread helped with that: http://forum.xda-developers.com/showthread.php?t=2683787
Now I can wipe data, factory reset, flash, etc. in TWRP v2.8.7.1. But when I flash a rom, I reboot system and it boots back to recovery. WTF. Ugh.
EDIT 2: Sad news. Based off this thread, http://forum.xda-developers.com/moto-x-2014/general/warning-downgrade-bootloader-partition-t3105147, looks like I FUBAR'd the phone. Unfortunate that this phone isn't like a Nexus.
Click to expand...
Click to collapse
its the phone will reboot back to TWRP event you restore backup file on TWRP ?
did you try flash custom rom from TWRP?
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
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Slupvee said:
So I been up all night trying to figuring out to fix this, so make things short i'll tell you what's wrong. My moto x is stuck at the warning bootloader unlocked screen and the only thing i can go to is the bootloader. I was flashing cyanogenmod 13 and i made some dumb decisions while trying to fix things. I trying to go into recovery but every time it boot back to the warning screen. At this i'm clueless at what to do and i'm just trying get my phone back to working condition, any help is appreciated.
Click to expand...
Click to collapse
It's always a good idea to put your phone in bootloader mode and do:
fastboot getvar all
So you get all the specs of your phone, and copy the info into a Notepad file.
Did you try reflashing TWRP (twrp-3.0.2-1-victara.img)?
If that's not working, you may be able to reflash stock firmware.
https://firmware.center:8081/firmware/Motorola/
Something like this:
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
fastboot reboot
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Slupvee said:
thank you!
I'm all the way up to Fastboot flash system system.img and it is saying Invalid sparse file format at header magi, I don't know if that telling me something wrong or continue.
Click to expand...
Click to collapse
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Gus Ghanem said:
Which XT variant do you have, on which carrier? Are you sure you got the right firmware for your phone model?
Click to expand...
Click to collapse
Verizon moto x 2014 5.1
Hey did u fixed it?
Whenever I try flashing a custom ROM i either loose my IMEI numbers and baseband version or simply get a NO SERVICE. The most recent custom rom i tried was Pixel Experience android 10, for this ROM i had my IMEI numbers and baseband version but got a "no service" - it did however detect my service provider.
Also when i flash the stock ROM back i don't get data(imei and baseband) immediately, i have to perform 2 OTA updates to get them.
So here's what i tried, flashed stock ROM did the 2 OTA updates to get my SIM to work and took a TWRP backup of EFS. Then flashed custom ROM and restored EFS but still didn't get the SIM working
I also took an entire backup of the stock ROM but when i try restoring it i get an error " Extract tar fork 255" in TWRP - now i believe this has to do with the fact tht i'm unable to flash TWRP recovery when on stock ROM (i keep getting a "no command" when i boot to recovery like this) but instead i have to directly boot into twrp every time - fastboot boot twrp.img and when i do it this way TWRP asks for a decrypt(?) password for which i press cancel.. which leads me to believe the backing up doesn't work properly because of this.
Any idea of to fix any of this?
Try to flash validus rom then back to stock.
While flashing stock skip
fastboot erase modemst1
fastboot erase modemst2
Then flash whatever you want.
And also in twrp try to repair data partition. Decrypt message could be bad disk sign.
I faced this issue, can't get 4G signal and speaking myself "how can validus rom solve this problem, nah just another silly solution"
But it solved!
flashe stock (august19 ROM) using codes
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
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 system system.img_sparsechunk.10
fastboot flash oem oem.img
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
then after first boot again flash this coades
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
baseband and imei showing
sushiada said:
Whenever I try flashing a custom ROM i either loose my IMEI numbers and baseband version or simply get a NO SERVICE. The most recent custom rom i tried was Pixel Experience android 10, for this ROM i had my IMEI numbers and baseband version but got a "no service" - it did however detect my service provider.
Also when i flash the stock ROM back i don't get data(imei and baseband) immediately, i have to perform 2 OTA updates to get them.
So here's what i tried, flashed stock ROM did the 2 OTA updates to get my SIM to work and took a TWRP backup of EFS. Then flashed custom ROM and restored EFS but still didn't get the SIM working
I also took an entire backup of the stock ROM but when i try restoring it i get an error " Extract tar fork 255" in TWRP - now i believe this has to do with the fact tht i'm unable to flash TWRP recovery when on stock ROM (i keep getting a "no command" when i boot to recovery like this) but instead i have to directly boot into twrp every time - fastboot boot twrp.img and when i do it this way TWRP asks for a decrypt(?) password for which i press cancel.. which leads me to believe the backing up doesn't work properly because of this.
Any idea of to fix any of this?
Click to expand...
Click to collapse
lynxrz said:
Try to flash validus rom then back to stock.
While flashing stock skip
fastboot erase modemst1
fastboot erase modemst2
Then flash whatever you want.
And also in twrp try to repair data partition. Decrypt message could be bad disk sign.
I faced this issue, can't get 4G signal and speaking myself "how can validus rom solve this problem, nah just another silly solution"
But it solved!
Click to expand...
Click to collapse
which version can you share the link of Which version orpost link or download link
[email protected]!vam said:
which version can you share the link of Which version orpost link or download link
Click to expand...
Click to collapse
Trying it out on a Moto G5s plus. Validus to stock to dot OS. Let's see if it brings back the baseband and IMEI. Fingers crossed
Editidn’t work