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
Related
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.
I downloaded Android Marshmallow after reading news about it through settings/about/system updates.
After downloading, the phone restarted but updatation was stuck after flashing TWRP screen (error screen photo attached)
My phone is
bootloader unlocked,
recovery TWRP
rooted
ROM is stock.
It seems the OTA update will be completed once I have stock recovery,
I have following queries
Is it necessary to revert to stock recovery to complete OTA update?
If yes, how to achieve it, what i learnt through search, I need to find Stock ROM zips and extract recovery (boot.img) and then flash it through adb?
where to look for thea stock rom and is there any easier method
It's risky, a lot of users here for some reasons got stuck whit locked/unlocked bootloader unable to boot and flash anything.
Here you can find all the motog stock roms http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=50
You should wait for the complete rom image for your country/model to pop there instead doing that risky thing you want do.
Thanks
Recently stock rom for xt1079 has been added to the list.
But I m trying to download from filefactory since yesterday but due to some reason, it stops in between and resume isn't supported.
Are there any other hosts
Are you sure the region of that xt1079 is right for your phonr ? check the phone box and the info inside settings to know which region/carrier you have, you must use the same identical 100% stock to avoid problems
And, do no relock bootloader !!!
yes i bought this through online retailer in India.
It is xt1079 Asia
I see in xda forum of moto g 2nd gen most of the time ppl are talking about xt1078.
What's the difference between xt1078/1079 and can't I use xt1078 ROM.
Rooting procedure meant for xt1078 worked fine for me
And Sir is relocking bootloader very risky ? suppose something goes wrong wont I be able to unlock or restore nandroid backup.
Thanks to support from Dr.nic I am finally on android 6.0
Although I have relocked my bootloader, but it is recommended to leave as it is.
If anyone stumbles here with same problem like mine i.e. unable to upgrade to android 6.0 just because of custom recovery, then pls download the firmware from filefactory.com link and flash. I'll add flashing commands as well to this post in near future.
if you have already done this rom change etc, the you must already be having fastboot, adb etc.
after connecting in fastboot mode holding VolDown and Power for few secs
run following commands
[this is for android 6.0 firmware]
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
I am not great expert, do this only if you have some idea, I may not be able to help you much if something goes wrong.
I can only say it worked for me
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
How to fix this? what file I should flash in fastboot or recovery?
Maps and others apps not recognize mi GPS
2-When I wipe cache partition or restore, twrp says error
(3.0...)
I have a moto x xt1058 with rom epsilon project (flashed over 5.1 stock) *When I flashed stock 5.1 with fastboot, fastboot give some errors.
sorry for my bad english
As to the GPS, clearing the modem using fastboot worked for me.
fastboot erase modemst1
fastboot erase modemst2
You might need to your device's stock NON-HLOS.bin as modem before issuing these commands. Download your device's latest stock firmware, extract the requisite file and flash it with the following command.
fastboot flash modem NON-HLOS.bin
I do not know how to help you with issue number two. Maybe just try flashing the official TWRP image again.
Hi everyone, first of all sorry my bad English. well I downgrade from oreo to nougat, stock Rom, and I realize that my connectivity was gone, so I tried many methods like "erasing modems" in cmd even installing modules of xposed, but nothing, then I started to find out what was the real problem, and I found that imei is lost... So I checked it and its true, my imei is 0. Actually I didn't know that this could happen, else I would made a backup, please friends I really need your help
D13Gho said:
Hi everyone, first of all sorry my bad English. well I downgrade from oreo to nougat, stock Rom, and I realize that my connectivity was gone, so I tried many methods like "erasing modems" in cmd even installing modules of xposed, but nothing, then I started to find out what was the real problem, and I found that imei is lost... So I checked it and its true, my imei is 0. Actually I didn't know that this could happen, else I would made a backup, please friends I really need your help
Click to expand...
Click to collapse
Flash any Oreo rom,you may get imei
first your twrp should be 64 bits, second flash rom oreo aop extended or pixel and if it goes back to stock never pass the modem commands, I will leave here the only commands that can execute
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 flash fsg fsg.mbn
fastboot erase cache*
fastboot erase userdata*
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
akshu2697 said:
Flash any Oreo rom,you may get imei
Click to expand...
Click to collapse
Thank you very much, it worked! I installed the last update of resurrection remix
D13Gho said:
Thank you very much, it worked! I installed the last update of resurrection remix
Click to expand...
Click to collapse
Now if your volte is working then not to worry but if it's not then follow thread for volte and recover volte after that take EFS backup of working volte and IMEI, so in future it will be helpful whenever your IMEI is gone,
akshu2697 said:
Now if your volte is working then not to worry but if it's not then follow thread for volte and recover volte after that take EFS backup of working volte and IMEI, so in future it will be helpful whenever your IMEI is gone,
Click to expand...
Click to collapse
Oh if you didn't tell me I don't notice, my volte is not working, I didn't know that volte also get lost too... Thank you again