Related
while attempting root on my sprint moto x using the moto x tool kit I decided hey the verizon root might work since theyre both cdma. bad idea. now every time i turn on my phone. com.android.phone force closes and it tells me sim card error. ive already flashed the stock image and I still get the error. any help would be greatly appreciated. thank you.
I attempted the slapmymoto method in the motoxtool kit and selected verizon
bradsinram said:
I attempted the slapmymoto method in the motoxtool kit and selected verizon
Click to expand...
Click to collapse
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
dray_jr said:
not sure what you did at all because all the phones are rooted the same way.
i would download the 4.2.2 firmware here
http://sbf.droid-developers.org/download.php?device=0&file=18
then go to this guide
http://forum.xda-developers.com/showthread.php?t=2603358
and follow the guide for returning to stock.
then after you are stock decide if you want to unlock your bootloader or not. then pick the guide based on what you decide and follow it for root
Click to expand...
Click to collapse
I've my device is 4.4 and ive already returned to stock and am still having the issue?
bradsinram said:
I've my device is 4.4 and ive already returned to stock and am still having the issue?
Click to expand...
Click to collapse
ok but if you did it threw the toolkit you might of still returned to the stock firmware for a different device
i restored completely to stock and am still having the same issue. please help
bradsinram said:
i restored completely to stock and am still having the same issue. please help
Click to expand...
Click to collapse
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
dray_jr said:
im going to bump this in hopes someone else takes a look.
can you look under settings/About phone/Status
what dose it way for
Network
signal strength
Mobile netowork type
also do you have a valid imei/meid please dont post this number here just check the number there with the number on the side of the box the phone came in
Click to expand...
Click to collapse
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
bradsinram said:
it says sprint for network then com.android.phone force closes. then it switches to searching for service. it say no signal strength and mobile network type is unknown. but it seriosuly force closes ever 2 seconds.
Click to expand...
Click to collapse
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
dray_jr said:
if it keeps force closing then you are not returning the phone to stock. because if you did that would not happen.
so i need you to explain to me what you are using when returning your phone to stock because it is not taking for some reason.
Click to expand...
Click to collapse
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
bradsinram said:
im using the 4.4 file that the motox toolkit downloads then i extract it to my adb folder and run these commands
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
everything appears to sucessfully flash
Click to expand...
Click to collapse
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
okay I will do. so i just find it weird they have an almost identical name and both say sprint. but thank you and im download the one you provided now.
dray_jr said:
so what your now telling me 3-4 post later is that you did not listen to me at all so you asked for help and when i gave you the correct answer on what to do you did not listen.
so i will try this one more time the 4.4 firmware package you keep using from the Moto x toolkit is not the Sprint firmware so STOP using it and download the firmware from the link below. and flash it with the above commands like i told you to do in my first post
http://sbf.droid-developers.org/download.php?device=0&file=734
Click to expand...
Click to collapse
so ive used the file you provided me with and am still having the same exact issues. I appreciate your help.
I feel like i need to rewrite the radio partition but which I'm assumung is the NON-HLOS but every time i try to write to it i get permission denied
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
dray_jr said:
ok sorry i left out a command i think i know what is going on
Code:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
mfastboot flash system system.img
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase userdata
fastboot erase cache
fastboot reboot
i know you just did this but do it one more time and make sure you do the erase userdata and cache commands and then reboot.
after wiping everything i am not sure what would be wrong i have a sprint device and i have never had this issue.
Click to expand...
Click to collapse
yeah I've tried it about ten times now and i think theres something else from the verizon root that mustve gotten flashed and is causing this
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Steve-x said:
Well you have to flash the NON-HLOS.bin or it is not going to work.
Why not just download the full Sprint firmware file(I believe you've already done this) download rsdlite, remove the var line from the xml, and with one click your phone will work fine again.
Click to expand...
Click to collapse
Thank you so much! I was wondering what kept causing rsd lite to fail. Im lead technician at a spring store and could just AE it but really dont want a refurb, especially since this phone is two days old
sorry but how do I remove the var line?
ive got it figured out thank you for your help
Soooo i was a big dumby and i wrote over the modem in order to get the update.
Now i have no signal/service available , or compatible baseband flashed.
Wifi works, everything else is amazing !!
Currently
Android 5.0
Baseband: Unknown <------
System version: 22.11.6.victara_tmo.tmo.en.US tkpca
Build Number: LXE22.39-6
If any one successfully backs up the telus baseband could you please post it ?!!?
So screwed at the moment
If you can tell me how to do so I would be happy to.
---------- Post added at 03:32 PM ---------- Previous post was at 02:51 PM ----------
pipesdl said:
If you can tell me how to do so I would be happy to.
Click to expand...
Click to collapse
I might have figured it out, use at your own risk.
https://drive.google.com/file/d/0B5ErTnQGFRMaVjRaWDV2dFlqMzg/view?usp=sharing
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Ah, didn't realize two files were needed. Links below.
FSG
https://drive.google.com/file/d/0B5ErTnQGFRMaN0JjLUx1RDVZakk/view?usp=sharing
NON-HLOS
https://drive.google.com/file/d/0B5ErTnQGFRMaWHVXZEhwS2UwU2M/view?usp=sharing
pipesdl said:
Ah, didn't realize two files were needed. Links below.
FSG
NON-HLOS
[
Click to expand...
Click to collapse
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
I think I did extract it with an mbn extension, don't know if it will make a difference but I'll upload shortly.
Let me know if it works.
https://drive.google.com/file/d/0B5ErTnQGFRMaQk9fcC05amJvTDg/view?usp=sharing
OscarAlert said:
Thanks!!! I tried flashing the FSG but it wants the file as a mbn. I tried changing the extension but it still didnt take it.
Although the modem bin file flashed fine, rebooted but still no service
Click to expand...
Click to collapse
You need the following commands. Just keep your mbn file.
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
I would love to know if those modem files work for the Telus phone after flashing, as the only thing holding me back is that it currently won't let me back up my own. If it does then lollipop here I come!
Those two files worked! Thanks so much to everyone who helped out in this thread. Successfully running Lollipop on my Telus Moto X now!
Awesome, can you let me know what steps you followed in addition to the steps above?
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Kodiak1 said:
Hi floepie, does the adb shell and su commands provide temporary root? ie Upon rebooting root will no longer be accessible? I'm looking to back up my modem files before flashing to xt1095 Lollipop.
Also, for anyone else following this thread, I'm a bit confused by the discussion about fsg.bin vs fsg.mbn; are there two different fsg files or is it simply that when pulling fsg.bin you save it as/rename it to have an mbn extension?
---------- Post added at 11:20 AM ---------- Previous post was at 11:13 AM ----------
And I'm wondering what impact the different modems even have... Is it possible that I can run the Telus Modem even though my provider is Wind Mobile (a Telus roaming partner)?
And what if I were to hypothetically take this phone (assuming sim-unlocked) and switch to say Bell, Telus, or Rogers; without tampering it'd still have the original Wind Mobile modem so what impact would that have on functionality/operation if I switched to a new service provider?
Click to expand...
Click to collapse
I'm pretty sure that in order to make an image of your baseband files, you need to be rooted. Root access is granted by SuperSU. As for the extensions on the fsg file, it doesn't matter what you call it. You just have to be consistent when copying it or applying it back to your device. I think someone posted on the forum using mbn and then used bin for applying it, which for obvious reasons wouldn't work.
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Take pity on me
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Update on xt1092 worked! I did this:
1. Downloaded the 4.4.4 system image from xt1905 (first post for download link)
2. Extracted the zip
3. flashed over mfastboot.exe
Code:
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 flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
4. sideloaded the OTA update from first post
5. reboot
6. flashed back the original modem and fsg from xt1902, without erasing modemst1 and modemst2 -> https://www.androidfilehost.com/?fid=95784891001608300
Click to expand...
Click to collapse
Then realising I had no signal I followed this post:
YES!
I finally have Lollipop on my XT1092!!
I followed steff999's guide but encountered several problems with the modem and data connections etc.
I just couldn't figure out why flashing the XT1092 modem files didn't work.
Then I went back to my original firmware and did the procedure again.
But now I did not let it boot after the OTA Update and directly booted into fastboot mode and flashed the modem and fsg files.
Then after reboot I immediately had mobile service. IMEI and Baseband is back again.
I use Linux and it is very easy with Linux.
In a terminal just go to the folder with the files (no matter where they are!!).
After getting Android SDK I did:
Code:
$ sudo apt-get install android-tools-fastboot <<-- to install fastboot
$ cd /directory with your files...<<--- choose your folder
$ fastboot flash logo logo.bin
etc
after flashing the files put OTA.zip on phone. Go in recovery mode and apply update.
Then when it reboots directly go in fastboot mode and type:
$ cd /directory with your XT1092 modem files/
$ fastboot flash modem NON-HLOS.bin
$ fastboot flash fsg fsg.mbn
$ fastboot reboot
now it boots into lollipop and it should recognize your sim card.
This is how it worked for me with Linux. Should be similar with Windows but I think the files for flashing have to be in fastboot directory then.
I did not use erase modem commands
I hope this will give hope back to people who encountered similar problems with the modem. I was about to give up but decided to give it a last try.
Click to expand...
Click to collapse
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
THE-M1GHTY-BUKO said:
Ok, so I unboxed my new phone UK (XT1092), unlocked the bootloader after it updated to Lollipop, and messed up somewhere causing me to have to install stock rom again. After installing the stock rom (4.4.4) I do not have signal and the baseband is unknown as with the OP. I have attemped to follow multiple guided concerning the same fixes but have gotten no where and am now extremely stressed and confused. Previously if I had problems with signal I just reflash a radio but times seem to have changed. The phone now shows as a xt1095 when plugged into pc.
Where I went having messed up:
Where I then went having found I had a xt1092
Then realising I had no signal I followed this post:
I am unsure how to get the OTA update onto the phone memory unless I power up and download, attempt at sideloading via adb resulted in the phone "aborting" at 100% sent.
So, could someone here please attempt to explain exactly what needs to be done
Currently about phone:
Android version: 5
Baseband version: unknown
System: 22.21.11.victara_tmo.tmo.en.US.retgb
Build number: LXE22.46-11
kernal: 3.4.42-gd7d30ea
Please.
Click to expand...
Click to collapse
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
drolgnir said:
I converted my xt1097 to xt1095, with the tmo 4.4.4 firmware, I boot it but complete no setup, and just copy the OTA from PC to phones internal storage. No adb sideload.
I've had Brazil radios work on my rogers RAZR before. There is a full lollipop BR firmware in the development section. Is might try it.
Click to expand...
Click to collapse
My problem is now fixed, thankyou.
For future reference for others, how did you fix the problem?
Sent from my XT1095 using Tapatalk
halfez said:
This might be a dumb question, but do you have to always flash the baseband files or modem files (not sure which is correct) every time there is a new update once you have converted to XT1095
I have a moto x 2014 (XT1097 ) from Wind Mobile and am trying to decide if i should keep it or not.
Nvm .... see the answer to my question here......
http://forum.xda-developers.com/moto-x-2014/help/converting-xt1097-to-pure-edition-t2912729/page5
Click to expand...
Click to collapse
Any chance you have a copy of the modem files for your moto x 2014 (XT1097 ) on Wind? I flashed the T-Mobile 5.0 xt1095, and don't think I properly backed up my files.
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
floepie said:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/NON-HLOS.bin
adb pull /sdcard/NON-HLOS.bin
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/sdcard/fsg.bin
adb pull /sdcard/fsg.bin
The two modem files are now on your SD card and you can share them with Drive or something else.
Click to expand...
Click to collapse
halfez said:
If you can explain to me how to extract the files from my phone using adb, sure. Coming from a nexus, not so good with adb
Click to expand...
Click to collapse
Come on, just do it!
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 everyone,
I have a problem with my Moto G 2014:
Many times the screen locks, and when i try to slide to open it, it will not open but gets locked again and again and I can't use the phone.
I had this issue with 4.4.4 and also after i updated to 5.0.2.
I tried:
1) factory reset.
2) clear cache partition.
3) I try to slide the option bar ad get to the settings but its not alway working to bypass the lock.
4) I tried also to cancel the "slide" option in the security setting to "none" but it still get locked..
what causes the issue? problem with the system? with some sensors? is it a fixable problem?
Did you try to flash stock/ custom rom?
Is your bootloader unlocked?
Have you tried re flashing the firmware. It's just a guess but your system partition may be corrupted.
Thanks you both
I never tried flash custom rom or anything, and I don't know if my bootloader is unlocked.
To flash ROM I need to unlock the bootloader? the only way to fix system partition is to flash new ROM/reflash frimware?
gifnooky said:
I never tried flash custom rom or anything, and I don't know if my bootloader is unlocked.
To flash ROM I need to unlock the bootloader? the only way to fix system partition is to flash new ROM/reflash frimware?
Click to expand...
Click to collapse
Well, restore to stock firmware with adb and mfastboot at it should be fixed.
Which model are you using? (XT1064 usa single sim, XT1068 international dual sim etc. etc)
The site for the official moto g stock firmwares is down so it is pretty hard to find a legit stock firmware file these days.
Here is one for the xt1064 http://www.rootjunkysdl.com/files/M...AWS_XT1064_4.4.4_KXB21.85-17_cid9_CFC.xml.zip
and one for XT1068
http://d-h.st/VOw (use the BLUE download now button not the orange download button. the orange one tries to get you to use dev host's bad download manager)
You can flash it by installing this 15 second adb installer by Snoop5
http://forum.xda-developers.com/showthread.php?t=2588979
If the latest version does not work then use 1.3
After you have everything downloaded open a terminal at the location you extracted the firmware. Reboot you device into bootloader mode by powering it on while pressing both volume buttons. Plug it into the computer and let the drivers install.
Run these commands. It is normal that the first two give you error if you are currently on 5.x firmware.
Code:
fastboot.exe 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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
My model is XT1063
Is there a trusted original firmware to this version?
No solution found yet after searching for 2 months .
http://forum.xda-developers.com/showpost.php?p=61901608&postcount=65
gifnooky said:
Is there a trusted original firmware to this version?
Click to expand...
Click to collapse
sumondhk1 said:
http://forum.xda-developers.com/showpost.php?p=61901608&postcount=65
Click to expand...
Click to collapse
Yep. https://mega.nz/#F!pxxUyIDI!zjgWxdJzrZrjTum9xBpfCg Not my work, thank them from the original thread here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
ethanchow said:
Yep. https://mega.nz/#F!pxxUyIDI!zjgWxdJzrZrjTum9xBpfCg Not my work, thank them from the original thread here http://forum.xda-developers.com/mot...riginal-motorola-firmware-collection-t3153533
Click to expand...
Click to collapse
You did not get it, See my screen shot , its a hardware issue .
Nothing gonna change with stock rom.
sumondhk1 said:
You did not get it, See my screen shot , its a hardware issue .
Nothing gonna change with stock rom.
Click to expand...
Click to collapse
I know the screen ghost touches is hw problem but u asked for the original firmware.
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
gebcruz06 said:
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
Click to expand...
Click to collapse
the 4g network here does not work, I've tried several tutorials
juniorhonorato1986 said:
the 4g network here does not work, I've tried several tutorials
Click to expand...
Click to collapse
What problem do you have?
No imei, no 4g, what have you done
gebcruz06 said:
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
Click to expand...
Click to collapse
Thanks for this. Wish it was up when it happened to me. I was ready to try and take back the phone while it was dead and hope they didn't try to turn it on. Lol. I loose my 4g everytime and 3g sometimes after flashing. In theroy I can do this after flashing a custom rom to get my 4g back right? I hope so cause I'm gonna try it. Once again, thanks for this!
always6s said:
Thanks for this. Wish it was up when it happened to me. I was ready to try and take back the phone while it was dead and hope they didn't try to turn it on. Lol. I loose my 4g everytime and 3g sometimes after flashing. In theroy I can do this after flashing a custom rom to get my 4g back right? I hope so cause I'm gonna try it. Once again, thanks for this!
Click to expand...
Click to collapse
You don't need to do all that - just flash stock (remove SIM before flashing and pop it back in after you've booted to stock).
Phazmos said:
You don't need to do all that - just flash stock (remove SIM before flashing and pop it back in after you've booted to stock).
Click to expand...
Click to collapse
On my experience, I have flashed every stock ROM for xt1805 there is as it is my model, flashed and reflashed modems, cleared modemst1 and modemst2 to no avail. IMEI=0. I removed sim before flash and popped it after booting, but still same result. It went on for almost 2 weeks. One thing I noticed is that the modem version becomes MSM8953_27.36.07.41u while the version in the xml file in stock zip is ***.41R. I don't know what that means, I flashed the latest firmware for xt1805. I am thinking that the letter stands for your region (u=US, e=EMEA, etc). My phone now after it has regai ed IMEI is ***.41e. Maybe it's a mismatch of modem since the bad flash that wrecked my phone and it changed something that makes it swtich to the right bands. I'm not quite sure though.
gebcruz06 said:
On my experience, I have flashed every stock ROM for xt1805 there is as it is my model, flashed and reflashed modems, cleared modemst1 and modemst2 to no avail. IMEI=0. I removed sim before flash and popped it after booting, but still same result. It went on for almost 2 weeks. One thing I noticed is that the modem version becomes MSM8953_27.36.07.41u while the version in the xml file in stock zip is ***.41R. I don't know what that means, I flashed the latest firmware for xt1805. I am thinking that the letter stands for your region (u=US, e=EMEA, etc). My phone now after it has regai ed IMEI is ***.41e. Maybe it's a mismatch of modem since the bad flash that wrecked my phone and it changed something that makes it swtich to the right bands. I'm not quite sure though.
Click to expand...
Click to collapse
Fwiw - I'm in the us, my baseband is 40e, so I think you might have the us firmware.
Where did u get the firmware? And how are you flashing it?
Edit , just noticed your baseband is 41e , disregard the above - but - do answer the questions.
Phazmos said:
Fwiw - I'm in the us, my baseband is 40e, so I think you might have the us firmware.
Where did u get the firmware? And how are you flashing it?
Edit , just noticed your baseband is 41e , disregard the above - but - do answer the questions.
Click to expand...
Click to collapse
Q: Where did u get the firmware?
A: I got the firmware I am using here:
https://androidfilehost.com/?fid=889964283620776326
Q: And how are you flashing it?
A: I am flashing it by following the sequence in flashfile.xml. I put it in a proper syntax in notepad and paste it line by line.
gebcruz06 said:
Q: Where did u get the firmware?
A: I got the firmware I am using here:
https://androidfilehost.com/?fid=889964283620776326
Q: And how are you flashing it?
A: I am flashing it by following the sequence in flashfile.xml. I put it in a proper syntax in notepad and paste it line by line.
Click to expand...
Click to collapse
Sounds like the flash procedure is correct , as long as each step flashed successfully.
I believe you mentioned flashing every firmware available - including from firmware center?
If so - all I can say its contact your carrier - if it was ok out of the box, and you've flashed the original firmware, it should work again.
Good luck!
not woring jio sim
umair09 said:
not woring jio sim
Click to expand...
Click to collapse
If u went to service centre for fixing volte then pls share Ur experience here
Your link to my twrp stock zip 404's, just saying.
I am following this so far, but i can't figure out where you got those files from:
fastboot flash modemNON-HLOS.bin fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Are they from the ROM you decided to be your Stock ROM? Because the Custom ROM doesn't contain those. And i am not sure i want to put just some random ROM Files in there...
Thanks for the help you provided with this Thread so far anyway =)
Edit: I tried it with the Files from the Stock ROM and it actually worked =)
Phazmos said:
You don't need to do all that - just flash stock (remove SIM before flashing and pop it back in after you've booted to stock).
Click to expand...
Click to collapse
I got my 4g back but I still lose it when I flash a custom ROM. I've tried flashing the room then restoring my efs. Nothing. Taking out sim card for flash then reinserting it. Nothing. I can get 3g just fine in all roms but 4g only in stock.......
always6s said:
I got my 4g back but I still lose it when I flash a custom ROM. I've tried flashing the room then restoring my efs. Nothing. Taking out sim card for flash then reinserting it. Nothing. I can get 3g just fine in all roms but 4g only in stock.......
Click to expand...
Click to collapse
When will u install custom rom.. after that just do 1 thing open bootloader menu and paste this commonds.... 1. fastboot erase modemst1
2. fastboot erase modemst2
Tadaaa you get 3g and 4g network
Thanks..Successfully did But VOLTE is not working...
gebcruz06 said:
Hi, all
To anyone experiencing IMEI = 0, therefore no cellular network, this here is a workaround. This happened to me firsthand, and I thought I should pay it forward and share with anyone who experiences this.
Your IMEI is not lost, it's just sitting there. You can see it in fastboot using "fastboot getvar all" command, and in the "Barcode" in bootloader menu.
Any attempt in writing IMEI via QPST tool is futile, because our device is write protected.
I have recovered my IMEI by doing the following:
1. Install Validus-sanders-8.1.Beta.1.3-OFFICIAL-20180128-0506.zip
https://androidfilehost.com/?fid=818070582850488560
2. After 1st boot in Validus you will see that your IMEI is now recognized, but still you are missing 4G. To recover this, reboot to bootlaoder and reflash the modem using the following fastboot commands:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
Reboot to connect to 4G.
3. Important: Reboot to TWRP and Create EFS Backup!
(Optional)
4a. Reflash stock ROM via fastboot, flash TWRP and restore your EFS partition using the backup you made.
4b. Reflash using TWRP flashable stock ROM in the thread below by @Ae3NerdGod and restore your EFS partition using the backup you made.
https://forum.xda-developers.com/mot...nps26-t3738502
Special thanks to
@Sri Datta for discovering this workaround
GZOSP and Validus Devs
@premaca and GZOSP/ Validus devs
Thanks and best regards.
Click to expand...
Click to collapse
Thanks..Successfully did But VOLTE is not working.
---------- Post added at 09:44 AM ---------- Previous post was at 09:41 AM ----------
umair09 said:
not woring jio sim
Click to expand...
Click to collapse
Hi i did successfully ,network is coming but my jio sim is not working..i mean i am unable receive or make the calls ...what should we do...please reply immediately..
I have tried everything. Restoring efs. Flash non hlos. Erasing modemst. I cannot get my 4g back after flashing custom ROM. So so aggravated. 3g sucks so I can't run a rom that won't do 4g. If any new info comes up someone please let me know.
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Kdemwa said:
When will u install custom rom.. after that just do 1 thing open bootloader menu and paste this commonds.... 1. fastboot erase modemst1
2. fastboot erase modemst2
Tadaaa you get 3g and 4g network
Click to expand...
Click to collapse
Tried that. Nothing still just 3g.
Always6z said:
I have tried everything. Restoring efs. Flash non hlos. Erasing modemst. I cannot get my 4g back after flashing custom ROM. So so aggravated. 3g sucks so I can't run a rom that won't do 4g. If any new info comes up someone please let me know.
---------- Post added at 06:38 PM ---------- Previous post was at 06:37 PM ----------
Tried that. Nothing still just 3g.
Click to expand...
Click to collapse
Try *#*#4636#*#*
Sri Datta said:
Try *#*#4636#*#*
Click to expand...
Click to collapse
Then what?
I am.coming from regular Moto G5 where this was a problem too. The solution over there was, if you are on a custom 8.x oreo rom, you needed, before going to stock, flash 32 bit twrp and a 32 bit rom. Then, after first boot, you could go back to stock with no problems. Just got this one and not planning to move from stock as I feel official oreo is right at the corner, but give it a try like this and report back if you were able to