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
Related
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?
Attempted to root & install TWRP, went to revert to stock, through about 6 different ROM variants for this phone, none of which have restored either the imei or baseband, some help/ insight would be amazing right about now
Did you ever figure this out, if not i can help you, i have had to restore both of them about 50 times, and i have an automated way of doing it, at this point. hit me up if you still need help.
for those having this problem, this is only for the MetroPCS variant xt1921-3 James model, flash back to stock build JAMES_T_OCP27.91-150-5-1_cid21_subsidy-MPCS_RSU_regulatory-DEFAULT_CFC from the bootloader using these commands -
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
fastboot reboot
- after you flash and reboot, it will boot up normally, setup up a wifi connection on it and it will tell you there is a new security update. Let it download and install the update, once finished, it will boot up and your baseband and IMEI will be working again.
What did you do to mess those up? I just got this phone, used to love doing this stuff, but it's become such a pain in the a$$ to just use a device I paid for like I want. I don't want that kind of problem. On a Samsung, that problem woud occur if your baseband and modem didn't match properly and the fix was to reflash the correct ones. Might not help you in this case tho.
Sent from my [device_name] using XDA-Developers Legacy app
So I think I'm going to return this Z3 play. Can someone link me to the process of unrooting?
Hear, HEAR. I second this, I am trying to work my way through the "No SIM Card" or sometimes "Invalid SIM Card" (on Sprint networks) error, and I am just wanting to unroot and relock the bootloader without breaking the thing beyond repair. Any help is appreciated. I located the latest stock firmware on here, but I am not 100% sure on the exact process as of yet.
mroneeyedboh said:
So I think I'm going to return this Z3 play. Can someone link me to the process of unrooting?
Click to expand...
Click to collapse
spyda256 said:
Hear, HEAR. I second this, I am trying to work my way through the "No SIM Card" or sometimes "Invalid SIM Card" (on Sprint networks) error, and I am just wanting to unroot and relock the bootloader without breaking the thing beyond repair. Any help is appreciated. I located the latest stock firmware on here, but I am not 100% sure on the exact process as of yet.
Click to expand...
Click to collapse
I have the Unlocked Z3, as well as the Sprint model, and have flashed between stock/CFW many tines. You simply need to use a flash all bat, paired with the stock firmware (current or newer).
However, please keep in mind that the verity message will remain during boot. Locking the bootloader will NOT fix this. If either of you need the bat file lmk.
Edit:
1. Enter fastboot/booloader on phone. Place bat file in SAME folder as unzipped firmware. Android SDK or adb tools must be installed!
2. Try USB2.0 port before 3+
3. Once done, use keys and switch to recovery mode
4. Perform a format
5. Reboot
https://drive.google.com/folderview?id=15hFa95l6bV1idoRXe5L1gt36jpG9s9DG
fastboot getvar max-sparse-size
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 bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.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_b system_other.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
pause
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