Related
I decided to write a new topic on this matter because there are still a lot of people like me with this problem.
My IMEI is shown as 0.
I've bought my phone at FastShop a non-carrier retailer. It is a XT1635-02 RETBR Dual-Sim.
On the process of loosing my IMEI, I was trying to get rid of the root I've installed before. I flashed a Cyanogen, got some problems with mobile data and decided to flash back to stock. When flashing back to stock I wanted a clean install, so I erased everything (EFS partition and every other tickable option) with the Chinese TWRP, the process gave me an error but I think it corrupted the data on EFS. (On the process of trying to fix this I've learned a lot of things I didn't knew and now I realize the kind of mistake I made...)
On "fastboot getvar imei" I can see my correct IMEI.
But dialing *#*#4636#*#* on phone info my IMEI is 0, also on Config>About both IMEI shown 0.
I've tried flashing the full stock ROM many times, even tried flashing different ROMS like LATAM, IUSMXLA, and others. Now I'm with the correct ROM running (RETBR).
I know that there are many people suffering from the same problem anything that could fix that anyway I would try.
I think you lost your IMEI forever.
DO NOT USE Chinese TWRP.
So basically all these reports of people getting their imei being 0 is them actually just wiping efs out of carelessness, got it. Not to be a jack*** but seriously...I always double check what I'm erasing. There's no recoveries, you've erased a unique identifier to the hardware. The manufacturer doesn't keep track of this.
DroneDoom said:
So basically all these reports of people getting their imei being 0 is them actually just wiping efs out of carelessness, got it. Not to be a jack*** but seriously...I always double check what I'm erasing. There's no recoveries, you've erased a unique identifier to the hardware. The manufacturer doesn't keep track of this.
Click to expand...
Click to collapse
That's my impression. I haven't seen anyone report categorically that they lost imei but absolutely did not wipe efs.
I think that when a signed firmware be available to download and install, the MZP will be able to regenerate the IMEI. Snapdragon have the capabilities to do it, but with an untrusted firmware, must "hide" it.
It is easy to get the IMEI back. Just restore the backup you did before wipe. Noone except you has the data on efs partition.
tag68 said:
It is easy to get the IMEI back. Just restore the backup you did before wipe. Noone except you has the data on efs partition.
Click to expand...
Click to collapse
This would require that people don't jump the gun and flash/wipe before making a backup.
A problem that shouldn't exist, but does.
I think you're SOL, dude.
rfameli said:
I decided to write a new topic on this matter because there are still a lot of people like me with this problem.
My IMEI is shown as 0.
I've bought my phone at FastShop a non-carrier retailer. It is a XT1635-02 RETBR Dual-Sim.
On the process of loosing my IMEI, I was trying to get rid of the root I've installed before. I flashed a Cyanogen, got some problems with mobile data and decided to flash back to stock. When flashing back to stock I wanted a clean install, so I erased everything (EFS partition and every other tickable option) with the Chinese TWRP, the process gave me an error but I think it corrupted the data on EFS. (On the process of trying to fix this I've learned a lot of things I didn't knew and now I realize the kind of mistake I made...)
On "fastboot getvar imei" I can see my correct IMEI.
But dialing *#*#4636#*#* on phone info my IMEI is 0, also on Config>About both IMEI shown 0.
I've tried flashing the full stock ROM many times, even tried flashing different ROMS like LATAM, IUSMXLA, and others. Now I'm with the correct ROM running (RETBR).
I know that there are many people suffering from the same problem anything that could fix that anyway I would try.
Click to expand...
Click to collapse
DISCLAIMER
Do it at your own risk.
SUMMARY
1. Reflashed back to stock Marshmallow
2. Sideloaded Nougat OTA right after (that is before booting into the freshly restored system)
-----------------------------------------------------------------------------------------------------------------
My IMEI became zero after trying to implement on Lineage OS a dual SIM mod originally intended for the stock ROM. "fastboot getvar imei" also displayed my correct IMEI. I eventually solved the issue purely out of trial by flashing the full stock (Marshmallow), and the nougat OTA right after that, as follows:
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 erase modemst1
fastboot erase modemst2
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 (repeat up to 10)
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot recovery
*recovery > adb sideload*
adb sideload nougat_ota.zip
WARNING
For downgrading, skip:
********************************
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
*******************************************
Proceeding otherwise will brick the device.
Just to clarify, I didn't made any backup before wiping my EFS.
I'm not used to go wiping everything, but I've already used the wipe function of the TWRP ticking all buttons and nothing was messed up.
Later I found that the Chinese TWRP give us the option to wipe our EFS.
I'm not blaming anyone but myself, I'm not that careless most of the times, I didn't had much knowledge as I do have now after all I've read and tried.
I have seen trough last months many people with problems on their IMEI, some problems was solved (flashing the ROM again), but the ones that continues looking for a solution probably have the same backstory as me.
VR25 said:
DISCLAIMER
Do it at your own risk.
SUMMARY
1. Reflashed back to stock Marshmallow
2. Sideloaded Nougat OTA right after (that is before booting into the freshly restored system)
-----------------------------------------------------------------------------------------------------------------
My IMEI became zero after trying to implement on Lineage OS a dual SIM mod originally intended for the stock ROM. "fastboot getvar imei" also displayed my correct IMEI. I eventually solved the issue purely out of trial by flashing the full stock (Marshmallow), and the nougat OTA right after that, as follows:
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 erase modemst1
fastboot erase modemst2
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 (repeat up to 10)
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase cache
fastboot erase userdata
fastboot erase DDR
fastboot oem fb_mode_clear
fastboot reboot recovery
*recovery > adb sideload*
adb sideload nougat_ota.zip
WARNING
For downgrading, skip:
********************************
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
*******************************************
Proceeding otherwise will brick the device.
Click to expand...
Click to collapse
I'll surely try that since you had the same problem and fixed, I have nothing to loose.
But I already flashed the stock ROM and updated to Nougat, but since I didn't actually sideloaded it I'll try again when I get home.
I m cool with it
as long as phone function is working
no data, coz data plan not activate
Welcome to the club. I wiped my /efs, lost my IMEI and had to pay £120 for a motherboard replacement. Now I've got a backup for my /efs partition, and never use the Chinese TWRP, but I learned an expensive lesson.
Really_Rekt said:
Welcome to the club. I wiped my /efs, lost my IMEI and had to pay £120 for a motherboard replacement. Now I've got a backup for my /efs partition, and never use the Chinese TWRP, but I learned an expensive lesson.
Click to expand...
Click to collapse
How did you back it up? With that chinese twrp?
rfameli said:
I decided to write a new topic on this matter because there are still a lot of people like me with this problem.
My IMEI is shown as 0.
I've bought my phone at FastShop a non-carrier retailer. It is a XT1635-02 RETBR Dual-Sim.
On the process of loosing my IMEI, I was trying to get rid of the root I've installed before. I flashed a Cyanogen, got some problems with mobile data and decided to flash back to stock. When flashing back to stock I wanted a clean install, so I erased everything (EFS partition and every other tickable option) with the Chinese TWRP, the process gave me an error but I think it corrupted the data on EFS. (On the process of trying to fix this I've learned a lot of things I didn't knew and now I realize the kind of mistake I made...)
On "fastboot getvar imei" I can see my correct IMEI.
But dialing *#*#4636#*#* on phone info my IMEI is 0, also on Config>About both IMEI shown 0.
I've tried flashing the full stock ROM many times, even tried flashing different ROMS like LATAM, IUSMXLA, and others. Now I'm with the correct ROM running (RETBR).
I know that there are many people suffering from the same problem anything that could fix that anyway I would try.
Click to expand...
Click to collapse
Tambien me he cansado de buscar, pero he visto un caso similar con un OnePlus One, el mismo tenia el problema IMEI 0 y lo soluciono por medio de la PC y unos driver, el titulo del post "REPARAR EL IMEI de nuestro ONEPLUS ONE tras perder el EFS" sin backup! link: forums .oneplus .net/threads/tutorial-reparar-el-imei-de-nuestro-oneplus-one-tras-perder-el-efs.264420/
chequealo
yeah. that was the only time i used it.
I was running my phone as a gaming tablet since I've lost my IMEI, connecting only trough wi-fi. I was running android MM 6.0.1 with december patch.
I've tried flashing Stock ROM RETBR version MPSN24.104-44-7, but it was not allowing me to install the OTAs giving an error by the end of the procedure.
I cleaned the system again and flashed the Stock ROM RETBR version MPSN24.104-44-10 and was able to sideload all the OTAs without any error.
Now my MZP is on Nougat latest available version but my problem was no fixed as I tought.
I really don't think I or the other ones that lost their IMEI like me (wiping EFS without having a backup) will be able to restore our lost IMEI.
I'm giving one last try, I'll buy a SIM from a brazilian carrier that doesn't seems to block IMEI, I don't know if this only apply for blacklisted IMEI's, but I'll try it with my IMEI 0.
The said carrier is "Oi".
I think you can pay Lenovo to replace the motherboard. You're probably better off doing that IMO.
IncendiaryPyro said:
I think you can pay Lenovo to replace the motherboard. You're probably better off doing that IMO.
Click to expand...
Click to collapse
The only problem is that the replacement of the motherboard cost almost the same as a brand new phone here on Brazil.
I thought I'd bricked mine. Rooted, then attempted to reflash back to stock, and had IMEI 0. Flashed CM and still IMEI 0. Did not take a backup of anything because I've been rooting around inside Androids since 2009 and never managed to fully brick a device.
I got it back by following these instructions. It works. I'm using it right now. All may not be lost.
Critically: some things need fastboot, and some things need mfastboot. Also, the order of re-flashing matters. Read the thread.
Hi People, I'm a Moto G5 (XT1676) user. After unlocking bootloader, rooting, flashing ROMs, etc. I "broke" my phone and now mi IMEIs are 0 and lost my phone signal.
I've been reading posts of older versions (Moto G1, G3) that people seem to fix this problem by flashing oher phone's back up of fsc, hob and dhob partitions. The problem is that in my Moto G5 only fsc partition appears.
I'm not expert and don't understand too much , I'm just asking for your help please, my phone turned into a tablet .
Do anyone of you guys know what partition do I have to fix in this phone?
Can you upload a back up of those partitions for me please?
Flashing those partitions on other versions of the phone seem to fix signal problem leaving IMEI = 0, I just need my signal back.
Something that I don't know if is relevant is that when I messed up flashing things, reading posts around internet I used some commands that I think modified "persist" and "misc" partitions.
Can anyone upload those just in case too?
Sorry if something is wrong, english is not my native language.
Please help me!
EDIT!!:
I've managed to revive my phone restoring someone's persist backup from twrp, "Backup & Restore partitions" doesn't work. The file I used to fix this problem is in this link: https://mega.nz/#!Yd82hSZZ!vdmbqAG0bQhNyR5g95KOrZjVvBw2QDrirpOwhD96gPc
The only file i needed was the persist backup in that .rar
It's no my partition, I've found it around internet, searching everywhere, but it worked.
Thanks for all the people that tried to help me!
IMEI stayed 0 but my mobile signal is back!!
How to restore that partition?:
1-Install TWRP.
2-Go into Backup and make a backup of any partition there. This will create a partition folder inside TWRP folder.
3-Copy the persist backup I've shared into that backup folder.
4-Boot into twrp, restore and select persist.
5-Restore.
6-Flash stock rom again for your device.
I hope that this help anyone in the same situation. This works for Moto G5 Plus too from what I've been reading.
It would be nice if people comment their results so we can help others.
Attention!: This doesn't fix IMEI, it stays 0 but mobile signal is back.
Good Luck and thanks!
flash stock rom via fastboot
never play around with partitions unless you know what you are doing - simply typing in commands without knowing their meaning will likely muck up your device
find your stock rom firmware via the power of google
Open a command/terminal prompt where you have fastboot (if you have added fastboot to the environmental settings you can run it from any location)
The commands you will likely need are
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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 have included fastboot in the link below - You will also need to download and install the moto usb drivers if you have not already done so
Platform-tools Download
TheFixItMan said:
flash stock rom via fastboot
never play around with partitions unless you know what you are doing - simply typing in commands without knowing their meaning will likely muck up your device
find your stock rom firmware via the power of google
Open a command/terminal prompt where you have fastboot (if you have added fastboot to the environmental settings you can run it from any location)
The commands you will likely need are
Code:
fastboot flash partition gpt.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk0
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot flash system system.img_sparsechunk4
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 have included fastboot in the link below - You will also need to download and install the moto usb drivers if you have not already done so
Platform-tools Download
Click to expand...
Click to collapse
I've already tried flashing stock rom but the problem is still there, I've also tried some custom roms too without success.
I know is my fault, I touched where I didn't have to.
I don't know what else to try, I think flashing other's back up partitions is my last shot.
I don't know if you are a Moto G5 user, but if you are, can you share those partitions to me?
Thanks for your reply.
Your gonna need an EFS / QCN backup. Do you know how to set the modem to diagnostic mode?
SvenRL said:
Your gonna need an EFS / QCN backup. Do you know how to set the modem to diagnostic mode?
Click to expand...
Click to collapse
From what I've been reading Moto G doesn't have a EFS partition, I've found in other forums that Moto G4 series have that data in "Persist" partition, and that partition is the one i've been touching..
That's why I'm asking if someone can backup that partition and share to me.
There is an app that does the job "Partitions Backup & Restore", I think you need root to use it.
I need that Persist backup just to try fix my phone, if you have Moto G5, can you help me with that?
Yes I know how to set it into diagnostic mode. (I've been trying apps and programs that in that mode fix qualcomm devices without success).
Thanks for your reply!
Can someone please help me with a "persist" partition backup please? I really need help.
Hi Jerito. Sorry to take a few days to reply to your PM. Been away.
Not sure i can help with this one as am not knowledgeable about copying particular partitions.
About the most comprehensive rebuild i have ever done was what i posted about doing it file by file and if i was in your situation, well, thats what i'd try.
Can you somehow extract the partition you are after out of a ROM??
I'll do you a qcn backup, wait till early hours of Monday morning. I'm curious cause i have the same issue with my lenovo P2, no persist partition, but I think the persist partition is created from the fsg partition
astmacca said:
Hi Jerito. Sorry to take a few days to reply to your PM. Been away.
Not sure i can help with this one as am not knowledgeable about copying particular partitions.
About the most comprehensive rebuild i have ever done was what i posted about doing it file by file and if i was in your situation, well, thats what i'd try.
Can you somehow extract the partition you are after out of a ROM??
Click to expand...
Click to collapse
No problem, the best way I've found of doing a back up of that partition is through the app I've mentioned "Partition Backup and Restore", I will watch your post!
SvenRL said:
I'll do you a qcn backup, wait till early hours of Monday morning. I'm curious cause i have the same issue with my lenovo P2, no persist partition, but I think the persist partition is created from the fsg partition
Click to expand...
Click to collapse
Ok, I'll be waiting, thanks both!
"No Sim Card detected" (due to TWRP backup restore) fix through fastboot commands?
Yesterday I had to restore my phone to a previous ROM (stock MM) from RR 5.8.5 Nightly. This was due to my working from home and needing to generate an RSA soft token, which is set up on an app on the backup, yadda yadda... Anyway, my restore worked fine, and I was able to generate my key and work from home.
However... when I went to use my phone, I noticed that the SIM card was no longer detected. I tried restoring my RR rom, and it too would not detect my Sim card.
In my attempts to find a fix, and then my attempt to restore the stock firmware and bootloader (that seems to be the only fix), I managed to royally hose my phone by attempting to flash the Full Stock LL ROM, which failed and must have overwritten the bootloader and recovery partitions. Trying to turn the phone on resulted in a vibration, but only a black screen. I was able to unbrick the phone using various guides I scrounged up and utilizing XFSTK and IntelSOC drivers, which must be installed when Windows 10 is booted with the special option to install unsigned drivers enabled (hold shift when you click restart, then option 7). I can post what I went through when I get home to my files and stuff if anyone requests it. Asus Flash Tool refused to flash the raw firmware (wrong format my ass), so I had to manually run the fastboot options. Everything was hunky dory after this.
Every fix for the SIM card issue pointed to reverting to stock firmware, which is what I did. However, I'm thinking there must be some key partition that I flashed in fastboot that revived the SIM. I performed the below commands from this thread . Does anyone see a command that screams "I'm fixing sim card issues"?
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Click to expand...
Click to collapse
If we can get the fix for an undetected SIM card after TWRP backup down to a few (or single) fastboot command, it'd be a nice convenience for us all.
Alternatively, does anyone know of a proper way to restore TWRP backups without losing SIM card detection?
UPDATE SECTION
I had found this site while searching for a solution yesterday, and it has the following fastboot commands for fixing the sim issue:
adb reboot bootloader
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
Click to expand...
Click to collapse
So in this case, the modem partition is being erased. But I don't see anything in the unbricking fastboot commands that erases the modem partition. Am I just missing it? I could see my IMEI in Sim Slot 1, so maybe it wasn't a modem partition issue.
-------------------------------------------------------------------------------------------------------------------
Found this thread (How did I miss it before?): https://forum.xda-developers.com/zenfone2/general/guide-how-to-zenfone-t3173314
The minimal boot options he listed are all in TWRP 3.1.1-0. The only thing I was missing before was config... I'm thinking that might be the key to preventing this. Next step is to determine if there's a config partition, and what happens when you do stuff to it (and ultimately how to restore the partition when you don't have a TWRP backup on hand).
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Hey man, have you have any success on this?
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.I will update this thread as I get new information on potential fixes.
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
ogabriel said:
Hey man, have you have any success on this?
Click to expand...
Click to collapse
I'm facing the same here. My problems started after the "erase modemst" command. After that I never was able to use my LTE connection again. I was able to use at least a H+ connection after I flashed a stock rom WITHOUT wiping nor formating data from a Lineage install. But, still no LTE. =/
I'm afraid this is caused by wrong modem driver w/ the downloaded stock rom. Don't know if there's a different driver for the Brazillian device.
CompostKicker said:
Yes and no. I was able to get a backup of the EFS partition from the LineageOS 15.1 ROM, which does restore cell service. However, it does not provide 4G LTE. I can get LTE on LineageOS, but when I reflash stock and then restore the EFS partition, it only gets me 3G connectivity. So far, the only way that I have been able to get LTE is to flash LineageOS, then run this:
Code:
fastboot erase modemst1 && fastboot erase modemst2
Apparently, those are cache files for something that has an effect on connectivity, though I don't know specifically what. Unfortunately, I must remain on LineageOS in order to keep the LTE. If I try erasing the modem caches on stock, it wipes all connectivity and returns me to IMEI 0. Downsides to this are bluetooth calls don't work at all, GPS navigation doesn't work, absolutely no torch (even with a third party app) and battery life is poo.
I am still looking in to this, including compiling my own ROM from source. Really, this whole ordeal has taught me two very important things:
1) Always make a complete backup of everything.2) Don't buy a phone that has no developer support on XDA. Honestly, this is the biggest one right here. Its revolting how little support there is for this device.I will update this thread as I get new information on potential fixes.
Click to expand...
Click to collapse
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
varun.katoch said:
Thank you compostkicker ..would apprentice if you post the solution if you find one..I am also going through a ditto condition
Click to expand...
Click to collapse
Sorry to leave you hanging, I stopped getting alerts on this thread for some reason. I am on shift until tomorrow and away from my computer, and it is a lot to type for a phone, but as soon as I am able I will type out the exact steps I used to fix the LTE issue, for both LineageOS and stock ROM.
Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
HTCDevil said:
Thank you bro, can you say which model you have and which retail firmware have you chosen for flashing via fastboot?
Click to expand...
Click to collapse
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
CHECK THIS LINK IF YOU WANT YOUR VOLTE TO WORK :
100% working
https://forum.xda-developers.com/newthread.php?do=postthread&f=6506
Rodrigo Fernandes said:
Moto Z2 Play - XT1710-07 and the retail firmware was NPSS26.118-19-1-6. Still working ok yet.
Click to expand...
Click to collapse
Without erasing modem1st and 2st, is it right?
HTCDevil said:
Without erasing modem1st and 2st, is it right?
Click to expand...
Click to collapse
That's right! But only after you follow the step 2. Otherwise it won't work.
Rodrigo Fernandes said:
That's right! But only after you follow the step 2. Otherwise it won't work.
Click to expand...
Click to collapse
I would like to pass from ZUI (on xt1710-08) to a retail one without flashing Lineage before. So, if the problem is about modem i should not erase them, so I would leave those present on the initial version unchanged
So, my situation is : signal is ok lte\4g bit IMEI is 0. I think i understand i must flash stock lineage rom with this commands, then backup efs (i've already had It), so flash stock nougat and restore efs and i should have IMEI. Is It correct?
Inviato dal mio Moto Z2 Play utilizzando Tapatalk
Rodrigo Fernandes said:
YEEEEEEESSS I FIXED IT!!! HAHAHAHAHA
I followed what you said installing Lineage OS and did the "erase modemst" command. After that, I formated data using TWRP and flashed a stock rom but I skipped "erase modemst" command. And now my LTE is working on the stock rom. OMG!!!! \o/
So...
1. Flash Lineage OS 15.1
2. Restart in Bootloader and run the fastboot code [fastboot erase modemst1 && fastboot erase modemst2]
3. Restart the system.
4. Restart and use TWRP to FORMAT data.
5. Flash the stock rom using Fastboot and the following commands:
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 modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot reboot
DON'T RUN THE MODEM ERASE CODE AGAIN!!!
This steps will fix the issue!
Click to expand...
Click to collapse
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
CompostKicker said:
I have an xt1710-01 which I am trying to return to stock ROM after trying out Lineage. Did not create a backup of EFS partition because I am an idiot. On Lineage, my IMEI appears just fine and I get cell service, though it isn't super great if I'm being honest. When I attempt to reflash stock, my IMEI shows as 0. Is it possible for me to still return my phone to stock ROM? I have tried manual fastboot method as well as a script called RSD Lite to no avail.
Click to expand...
Click to collapse
Try Moto lenovo smart asistant to rescue your device @CompostKicker
kevoroid said:
Hey, I just flashed 9 on my XT1710-8 and lost singal. do you think this trick works in my case? (havent tried yet cause didnt want to format my device!)
Click to expand...
Click to collapse
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Rodrigo Fernandes said:
I can't guarantee you can fix it using my step-by-step because I did it for the XT1710-07 model. Maybe you'll have to adapt the solution to yours.
Click to expand...
Click to collapse
I fixed it by flashing the original -08's Oreo ROM (Chinese ROM) and then reflashing Pie without doing the "erase modemst1.." steps.
moto z2 play imei repair
Hello everyone . i have moto z2 play xt1710-6 with stock rom. i wanna change my imei coz of lost signal. i tried many softs but i was not ablet to change it. i went to some techical shops , they used sigma and miracle , they couldnt as well. overall , how may i change its imei ? are there any way ?
does anyone know if there is some way to flash stock pie on a sprint variant??
Yes, see page 3 of following post:
https://forum.xda-developers.com/z2-force/how-to/verizon-update-t3952591/page3
Copying Hibinoh's work here for simplicity (not my work; this is a copy of the post of the person above):
Since someone asked Sprint, to get 9.0 on your sprint, following the steps:
1, get RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest Sprint 8.0(XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
2, unzip both ROM, find a copy of mfastboot, a copy of TWRP(use nash's TWRP)
3, copy the boot.img from RETIN 9.0 to your phone's sdcard
4, wipe your phone(data + cache)
5, use mfastboot flash following files from RETIN 9.0:
Code:
Code:
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot oem fb_mode_clear
6, use mfastboot flash following files from Sprint 8.0(!!!BECAREFUL, DO NOT FLASHED FOLLOWING FILES FROM 9.0!!!):
Code:
mfastboot oem fb_mode_set
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp adspso.bin
mfastboot oem fb_mode_clear
7, boot into TWRP
Code:
mfastboot boot YOUR_TWRP_FILE_PATH
8, use TWRP to flash the boot.img(step 3) to 'boot'
9, reboot
Well, I am happy on 9.0, but not happy to lost google pay(yea I know there is magisk hide)
quadcrap1 said:
Copying Hibinoh's work here for simplicity (not my work; this is a copy of the post of the person above):
Since someone asked Sprint, to get 9.0 on your sprint, following the steps:
1, get RETIN 9.0(XT1789-06_NASH_RETIN_9.0_PPX29.159-19_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip), and the latest Sprint 8.0(XT1789-03_NASH_SPRINT_8.0.0_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip)
2, unzip both ROM, find a copy of mfastboot, a copy of TWRP(use nash's TWRP)
3, copy the boot.img from RETIN 9.0 to your phone's sdcard
4, wipe your phone(data + cache)
5, use mfastboot flash following files from RETIN 9.0:
Code:
Code:
mfastboot oem fb_mode_set
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system_b system_other.img
mfastboot flash oem oem.img
mfastboot oem fb_mode_clear
6, use mfastboot flash following files from Sprint 8.0(!!!BECAREFUL, DO NOT FLASHED FOLLOWING FILES FROM 9.0!!!):
Code:
mfastboot oem fb_mode_set
mfastboot flash modem NON-HLOS.bin
mfastboot flash fsg fsg.mbn
mfastboot flash bluetooth BTFM.bin
mfastboot flash dsp adspso.bin
mfastboot oem fb_mode_clear
7, boot into TWRP
Code:
mfastboot boot YOUR_TWRP_FILE_PATH
8, use TWRP to flash the boot.img(step 3) to 'boot'
9, reboot
Well, I am happy on 9.0, but not happy to lost google pay(yea I know there is magisk hide)
Click to expand...
Click to collapse
I have done this twice and it's not working i followed all the steps one by one
I'm guessing the answer is no, but, has anybody tried this with the EU version for T-Mobile or ATT? Or Verizon version, even?
I'm tempted to try, but fairly certain it won't work.
worked like a charm, I had to factory reset after flashing the boot in TWRP though
Starkiller2 said:
worked like a charm, I had to factory reset after flashing the boot in TWRP though
Click to expand...
Click to collapse
A) You did this on a US Sprint phone, right?
B) Did you do the factory reset via TWRP, through the bootloader/Recovery Mode, or through the OS?
quadcrap1 said:
A) You did this on a US Sprint phone, right?
B) Did you do the factory reset via TWRP, through the bootloader/Recovery Mode, or through the OS?
Click to expand...
Click to collapse
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Screenshot
Starkiller2 said:
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Click to expand...
Click to collapse
So it sounds like you added two extra steps to the original instructions above:
1) Factory reset in TWRP after flashing boot image in TWRP
2) As a last step, rebooting to bootloader one more time and issuing the command
Code:
mfastboot flash modem NON-HLOS.bin
(where NON-HLOS.bin comes from the Sprint image, not the Pie image, just as when it was flashed the first time).
Correct?
quadcrap1 said:
So it sounds like you added two extra steps to the original instructions above:
1) Factory reset in TWRP after flashing boot image in TWRP
2) As a last step, rebooting to bootloader one more time and issuing the command
(where NON-HLOS.bin comes from the Sprint image, not the Pie image, just as when it was flashed the first time).
Correct?
Click to expand...
Click to collapse
Yes
So I've tried the above instructions on a Sprint Z2 Force. The first time, I got into an instant bootloop. So I went through the entire procedure again, and this time, I get to about 1 minute past when the Moto M is spinning around, to where the Lenovo color blocks are supposed to appear, and the screen goes black with occasional flashes on. Eventually, it just boot loops again.
Hmmm...
I do realize that I am using for the Sprint firmware (from which a few files come):
NASH_SPRINT_OCXS27.109_48_17_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
This is a nominally different than the xml file the OP mentioned:
NASH_SPRINT_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Unfortunately, I can't find a working link to the latter...I wonder if that could be the issue? Anyone have a working link for the 48-20 version?
quadcrap1 said:
So I've tried the above instructions on a Sprint Z2 Force. The first time, I got into an instant bootloop. So I went through the entire procedure again, and this time, I get to about 1 minute past when the Moto M is spinning around, to where the Lenovo color blocks are supposed to appear, and the screen goes black with occasional flashes on. Eventually, it just boot loops again.
Hmmm...
I do realize that I am using for the Sprint firmware (from which a few files come):
NASH_SPRINT_OCXS27.109_48_17_subsidy_DEFAULT_regulatory_DEFAULT_CFC.xml
This is a nominally different than the xml file the OP mentioned:
NASH_SPRINT_OCXS27.109-48-20_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Unfortunately, I can't find a working link to the latter...I wonder if that could be the issue? Anyone have a working link for the 48-20 version?
Click to expand...
Click to collapse
I used the -20 version from here
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
So I managed to get Pie up and running on a Sprint Z2 Force. Everything seems to be working. I'm using it for T-Mobile, and Visual Voice Mail and VoLTE seem to be working.
One thing I can't get to work is Netflix. It won't install. if I sideload it, it won't run.
I use the phone for work (work profile), so I can't use Magisk (and I have no other need to root).
Anyone have a trick to get Netflix installed on a Frankenstein install like this with an unlocked bootloader.
Note: I was able to get Netflix to run on the Z2 Force with the T-Mobile flash on Sprint for Oreo.
---------- Post added at 05:07 PM ---------- Previous post was at 04:58 PM ----------
Starkiller2 said:
I used the -20 version from here
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Thank you for the link!
where can I get the two files listed in step one?
delawaresace said:
where can I get the two files listed in step one?
Click to expand...
Click to collapse
The post two above yours has the link to one,
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
That's the other
Updated Tmobile Z2 Force to Pie
Starkiller2 said:
Yes I did, a Sprint variant, on boost Mobile.
The easiest way for me, if it helps, was to unzip the two firmware files and place the necessary files from each in a separate folder.
In twrp wipe dalvik cache and data.
Reboot to bootloader
Then flash them in the order above, but all in one go.
Boot twrp, flash boot image in twrp
Factory reset in twrp
Reboot to bootloader
Flash modem again
Reboot
I did find that no matter what I can't get twrp to stick or any recovery. It always reboots to fastboot
So you have to use the volume keys to press start
Click to expand...
Click to collapse
I want to report that I have followed these instructions and have updated my TMobile Z2 Force to Pie. I am not in an US network.
My steps were pretty similar:
I flashed to stock using the TMO Z2 Force 27.1.5 Flashall
Booted normally
TWRP Wipe Data, Cache and System
Followed the steps as in the Verizon Update thread making sure to follow the steps as indicated by Starkiller2 above (except Factory Reset in TWRP). Using the TMO Z2 FORCE FLASHALL files and NOT the Sprint ones
Voilà
I successfully flashed 9.0/Pie to a Sprint phone for use with T-Mobile the other day.
An update. It generally seems stable and working.
Things that do not work:
A) VoLTE: The phone drops down to "H" (HSPA) / 3G when I make/receive a call. That means that while I can use data, it unusably slow 3G. I am not sure how to fix this. It's using T-Mobile as carrier, T-Mobile US as the APN (same as a Sprint/T-Mobile Z2 Force flashed phone running Oreo I am using on T-Mobile and which gives LTE speeds during a phone call/VoLTE).
B) Netflix won't install. It doesn't even show up in the Play Store. If you try to sideload it, it will crash/stop before you can use it. This is probably related to the unlocked bootloader, although I use Netflix on the Oreo Z2 Force with unlocked bootloader with no issue.
Oh, and the Oreo running Z2 Force shows 4GLTE, while the Pie running Z2 Force shows just LTE in the exact same location. The Oreo phone gets download/upload speeds of 24.0/9.1, the Pie phone gets download/upload speeds of 28.0/9.99. FWIW.
When I make a call, I see "HD call" for the Oreo phone, I don't see it for the Pie phone.
quadcrap1 said:
So I managed to get Pie up and running on a Sprint Z2 Force. Everything seems to be working. I'm using it for T-Mobile, and Visual Voice Mail and VoLTE seem to be working.
One thing I can't get to work is Netflix. It won't install. if I sideload it, it won't run.
!
Click to expand...
Click to collapse
If I recall correctly when I flashed my Z2 I(Spring) phone to unlock it from the network and also installed Magisk for Google Pay and other stuff that did't like rootl Netflix also didn't initially. It wasn't critical since I have so many other ways to watch but out of curiosity I searched for a fix and I think it was this
'
https://forum.xda-developers.com/apps/magisk/module-netflix-enabler-enable-netflix-t3708126
I did atually take notes but they are at home and I am currently on the road so I can't confirm but it looks like what I did.
A few questions:
1. Will flashing Pie on a bootloader unlocked Sprint model require the modem from 48-20, even if the phone has only been on an earlier Oreo firmware?
2. Does using the Oreo modem mean the Sprint phone could be flashed back and forth between Pie and Oreo without issues?
3. Would there be any reason this mixed/unofficial firmware would not activate / operate normally on Sprint service?