There has been problem with my radio/modem. I have tried everything but nothing works. I've tried flashing OOS modem files, going back to stock etc. I found one solution to restore my efs backup. But unfortunately, i dont have efs backup. Can anyone help me by sharing their modemst1.bin and modemst2.bin files ? It would probably solve the problem.
Related
Hey xda-forums,
after rooting my Samsung Galaxy S5 (Vodafone Germany) I did a backup of my data and copied it to my PC (It were 7GB).
Now I wanted to restore the backup, so I copied the Backup files back on my SD-Card. As soon as I start the restoring, TWRP says "Cannot restore Modem -- mounted read only" .
Is anyone able to help me?
-Issei
I get this all the time. I usually unchecked modem and restore everything else. I'd like to know why this happens, too, so I can fix it. In the meantime, just uncheck modem before restoring your backup. Someone will see this and know how to fix.
You can mount RW in mount section. Check modem partition
Did you manage to solve this? I check modem in the mount menu but it keeps giving me the same error.
Not solved. Any help?
Workaround
I have S5 Verizon (USA). Have the same issue. Member mjw1 found workaround:
"I realized that I am also facing this issue on my G900T. So at the moment, I'm using 3.0.2-3-M for nandroid backups, then dropping back to 3.0.2-1 to restore the modem. I know it's a hassle, but at least I'm still able to restore 100% from my backups with this workaround."
http://forum.xda-developers.com/showthread.php?p=67128647#post67128647
This worked for me.
why would you want to restore modem/bootloader? always get the latest version with stock ROM, install recovery, then restore everything back except modem, bootloader & recovery. you don't even need to boot to android to do all these.
badai said:
why would you want to restore modem/bootloader? always get the latest version with stock ROM, install recovery, then restore everything back except modem, bootloader & recovery. you don't even need to boot to android to do all these.
Click to expand...
Click to collapse
It depends. For example if I need to add additional LTE bands (in my case 3 & 20) to Verizon phone, I definitely need the possibility to backup – restore modem if something goes wrong.
Still not solved- anyone have another suggestion?
I found a solution.
I was not able to upgrade my modem with odin after knox became 1.
By using an usb JIG and going in "advanced downloadmode" I was able to update my modem.
I got the same error
And not only on the "Modem", but also on the "System" part. Except these 2 partitions, all other partitions could be recover. Anyone know why? and how to fix this problem? Thanks!
clockzhong said:
And not only on the "Modem", but also on the "System" part. Except these 2 partitions, all other partitions could be recover. Anyone know why? and how to fix this problem? Thanks!
Click to expand...
Click to collapse
What's your phone version?
It looks like you have locked bootloader
SOLVED- it is a twrp problem. You're using 3.0.2.2, right? Go back to 3.0.2.1 and all will be fine again. I flashed 3.0.2.1 and modem restores without a hitch
Hi guys
Does anyone have a TWRP A2017G backup their willing to share?
I've lost IMEI and MEID and am trying to recover
Seconded. I seem to be in the same situation. Don't know if a TWRP backup will help, but I've been unable to connect to the cellular network after restoring a full TWRP backup which I suppose I shouldnt've restored. Re-entering my IMEI via a TWRP module didn't help as well. Neither does the adb shell dd command that formats the EFS partition found in another thread... Restoring EFS I backed up a while ago didn't help me as well.
Thanks in advance.
I have tried going back to stock boot/recovery backups, flashing every single A2017G update and even tried Tenfar's tool to restore the removed backups in his thread. Cannot seem to fix
Only had this phone for 3 days and it's now useless.
Controllerboy said:
Restoring EFS I backed up a while ago didn't help me as well.
Click to expand...
Click to collapse
Do you have a backup you could share?
As far as I know, the EFS bit is unique to each device. It contains your IMEI code, for example, which is unique for each device.... I can give you mine, but I'm not sure if that will help you.
I'll probably make a new thread asking for some help because I've tried about everything and I can't fix this mess on my own... I hope I won't have to send it back, no way of knowing they'll believe me
I've been doing some googling and perhaps we need a modem.bin file from a A2017G?
this is really not looking good
I installed TWRP 3.0.2-0 on my axon A2017G B03, unlocked the bootloader, installed CM13 after a small hiccup (had to temporarily install A2017G B06 and Bootstack).
All went well, I really enjoyed my phone. The only problem was that I'm an audiophile and there was a big distortion on the speakers.
I tried to install a Dolby zip via TWRP to improve this. Before I did that, I took a full TWRP backup.
The Dolby app didn't help one bit, after which I wanted to rollback by restoring the backup. Appearently, restoring the EFS is a really bad idea, since after that, CM13 wouldn't boot anymore. So, I tried using DrakenFX' B06 bootstack and stock image. When I did that, my phone could not connect to Wi-Fi nor detect my SIM-card.
Using the commands
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I restored my Wi-Fi. My phone now recognises my SIM-card, but I can't connect to the cellular networks. I have no IMEI. It can detect cellular networks, but not connect to them.
I have "efs1.emmc.win" and "efs1.emmc.win.md5" files from the TWRP backup of CM13 from just before I killed my cellular and another EFS backup I took just before unlocking BL and flashing TWRP (A2017G B06).
When I do a clean install of A2017G B06 and restore the TWRP EFS backup I made when on B06, when the phone boots, the phone doesn't detect my SIM.
When I do a clean install of CM13 and restore the TWRP EFS backup I made when on CM, CM13 doesn't boot at all.
I've spent about a day trying just about anything. Nothing seems to work. Can someone pull their modem file? Or would flashing NON-HLOS.bin help? Is there a different way of restoring my EFS backups? I read something about TWRP 3.0.2-0 not playing nice with EFS. Would flashing TWRP 3.0.2-2 and then restoring EFS work? Or is there a way to restore the phone back to "just-out-of-the-box" status? I don't mind losing unlocked BL or TWRP, I can do that all again. I thought as long as I backup everything including EFS, nothing can really go wrong. A user in XDA posted that "shady" guides that "don't get discussed at XDA" can usually help you get IMEI back. I don't want to illicit illegal practices here, but I'm desperate enough to try just about anything.
Thanks a lot for your help. If no-one here can help me, I suppose it's back to amazon. And probably pay a decent amount for it, too
Perhaps try flashing newer twrp version and restore your efs backup?
Controllerboy said:
I installed TWRP 3.0.2-0 on my axon A2017G B03, unlocked the bootloader, installed CM13 after a small hiccup (had to temporarily install A2017G B06 and Bootstack).
All went well, I really enjoyed my phone. The only problem was that I'm an audiophile and there was a big distortion on the speakers.
I tried to install a Dolby zip via TWRP to improve this. Before I did that, I took a full TWRP backup.
The Dolby app didn't help one bit, after which I wanted to rollback by restoring the backup. Appearently, restoring the EFS is a really bad idea, since after that, CM13 wouldn't boot anymore. So, I tried using DrakenFX' B06 bootstack and stock image. When I did that, my phone could not connect to Wi-Fi nor detect my SIM-card.
Using the commands
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1 and dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
I restored my Wi-Fi. My phone now recognises my SIM-card, but I can't connect to the cellular networks. I have no IMEI. It can detect cellular networks, but not connect to them.
I have "efs1.emmc.win" and "efs1.emmc.win.md5" files from the TWRP backup of CM13 from just before I killed my cellular and another EFS backup I took just before unlocking BL and flashing TWRP (A2017G B06).
When I do a clean install of A2017G B06 and restore the TWRP EFS backup I made when on B06, when the phone boots, the phone doesn't detect my SIM.
When I do a clean install of CM13 and restore the TWRP EFS backup I made when on CM, CM13 doesn't boot at all.
I've spent about a day trying just about anything. Nothing seems to work. Can someone pull their modem file? Or would flashing NON-HLOS.bin help? Is there a different way of restoring my EFS backups? I read something about TWRP 3.0.2-0 not playing nice with EFS. Would flashing TWRP 3.0.2-2 and then restoring EFS work? Or is there a way to restore the phone back to "just-out-of-the-box" status? I don't mind losing unlocked BL or TWRP, I can do that all again. I thought as long as I backup everything including EFS, nothing can really go wrong. A user in XDA posted that "shady" guides that "don't get discussed at XDA" can usually help you get IMEI back. I don't want to illicit illegal practices here, but I'm desperate enough to try just about anything.
Thanks a lot for your help. If no-one here can help me, I suppose it's back to amazon. And probably pay a decent amount for it, too
Click to expand...
Click to collapse
It seems that I am having the same kind of issue with the newest version of TWRP. After having some issues with incoming and outgoing phone calls, I stumbled across the above command. After using the command I lost my ability to connect to my network operator. Therefore I tried to do a recovery from TWRP and now I'm stuck with an IMEI which shows "0".
Sadly it seems that I don't have a backup of my efs partition (noob) and now I'm desperately finding possible solutions.
Any ideas? I feel that the trying to connect to the network with no IMEI is the cause of my problem...
Dawacko87 said:
It seems that I am having the same kind of issue with the newest version of TWRP. After having some issues with incoming and outgoing phone calls, I stumbled across the above command. After using the command I lost my ability to connect to my network operator. Therefore I tried to do a recovery from TWRP and now I'm stuck with an IMEI which shows "0".
Sadly it seems that I don't have a backup of my efs partition (noob) and now I'm desperately finding possible solutions.
Any ideas? I feel that the trying to connect to the network with no IMEI is the cause of my problem...
Click to expand...
Click to collapse
Both myself, Controllerboy and many others pretty much tried everything to restore working imei numbers to no avail. Only solution for both of us was to RMA our phones unfortunately.
Tebor said:
Both myself, Controllerboy and many others pretty much tried everything to restore working imei numbers to no avail. Only solution for both of us was to RMA our phones unfortunately.
Click to expand...
Click to collapse
That's exactly not the answer I wanted to hear
I think in that case it would be advisable to go back t stock and lock the bootloader? And have you been presented with a bill from Amazon/ZTE?
Flash modemst won't work anyway, you have to flash full bootstack.
Install TWRP, then flash A2016G bootstack file that DrakenFX provided
tamahouse02 said:
Flash modemst won't work anyway, you have to flash full bootstack.
Install TWRP, then flash A2016G bootstack file that DrakenFX provided
Click to expand...
Click to collapse
Already tried going back to stock with the bootstack and files provided by DrakenFX, but the mobile network connection won't work.
It started of with connecting to the mobile network, at least it showed full bars, but without a data connection. After a few minutes
the connection to the network was lost and I haven't been able to register again.
So it seems that Trebor is right, sadly...
Hello guys. If you ever lost any of your wireless connectivity and sensors for flashing any other rom then I have a backup files here via twrp. I just don't know how to make them into flashable so I just compressed it in case you need it.
I've lost my sensors and wireless networks such as fingerprint, signal, Bluetooth and wifi when I restored a backuped system in twrp. I did so many things like restoring its efs, flashing its NON-HLOS.bin file, reverting back to stock to no avail. It just gave me a headache because my bootloader got unlocked again so I unlock it for the 2nd time and it succeeded.
What I did was:
Flash back twrp(persist error occured, then I cannot flash any rom)
Restored efs, and persist on my backuped ( I just remembered that I have backuped the persist)
Reboot to recovery
Flashed RR rom (as usual along with Gapps and SU)
And it succeeded
Waited to boot and I got shocked when everything on my phone was back to normal.
So I am sharing this twrp backup file for you in case you guys need it.
you are sharing your IMEI and other important things remove it or anyone can misuse it
I want to know which file is to be restored to get modem back from twrp backup folder ?
Thread closed at OPs request
So I flashed back stock through fastboot coming from root. I somehow lost being able to find any WIFI networks. It just searches forever. Mobiledata works tho. I have of course a nandroid backup, but before doing anything, what could help? Tried restoring EFS and flashing MODEM.IMG with no luck. Any ideas?
I answer this. I don't know what happened but if this happens to you, try flashing the fastboot rom again, it solved the problem.