SIM not recognized after restoring TWRP backup - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi! I have a hlte/SM-N9005 with LineageOS.
Today I tried to turn on encryption, but then I was stuck in a boot loop. I did a full wipe in TWRP and restored everything from the backup I made before (including the modem partition).
My phone boots again (without encryption), but isn't able to detect any SIM card suddenly. Not sure if something went wrong with the restored modem backup?
I tried downloading a Swiss firmware from this link, extracted it, and flashed modem.bin and NON-HLOS.bin via Heimdall - this didn't help either, though. I'm kind of out of ideas now... Any idea what's going wrong?

IMEI correct ??

Phone Status > Status > IMEI information says "IMEI: unknown" :-/ I'm guessing this is supposed to be there, even without a SIM?

Restore your backed up EFS folder .

Restoring the EFS folder from the TWRP backup is what got me into this mess in the first place. There's probably supposed to be a /efs/.nv_data.bin in the backup, but there isn't for whatever reason. I don't have older backups anymore either.

Related

[HELP][Q] I9500 Stuck at samsung logo + an empty EFS folder

Hy everyone,
I'm a little desperate now. my i9500 is stuck at Samsung logo even the animation sound that not complete, i had mokee rom 4.4.2, made a restore from a previous nandroid backup, barebone prism rom V3.0 worked perfectly, installed nandroid manager and restored some access point passwords, worked perfectly so far, my phone reached 1% in battery then turned off after a while. when i wanted to reboot it, the phone freezes in Samsung logo.
Recovery: Philz touch recovery
I tried everything that i know about,
1° reboot in revocery and restore from a previous nandroid backup (NOT GOOD)
2° reboot in recovery, perform a full wipe, restore from a working previous backup (NOT GOOD)
3° reboot in recovery perform a wipe reset (NOT GOOD)
4° restore via odin in download mode last stock firmware for my phone I9500XXUEMJ8 (NOT GOOD)
5° i tried mounting all partitions for check and .... Eroor mounting /efs!
i checked efs folder with aroma file manager ... 0 files inside :crying:
i had a previous backup for EFS found in kies in .tar.gz format
i tried to restore it with several methods
http://forum.xda-developers.com/showthread.php?t=2392632
guess what ?? NOT GOOOD
i tried manually to copy files in EFS folder and changed the permission for EACH file with the same permission from the backup in my laptop then i reboot in recovery, the files still inside but when i reboot the system, the files are gone
i've read somewhere that there is two type of efs , and the efs made by some old stock rom won't work for a new one (Personally i don't know but like i said i'm desperate) so i downloaded from sammobile the FIRST rom that was in my phone and put it via odin (Re partition was never checked) then i tried the methods above ... :crying::crying::crying:
because i only have .tar.gz i tried restore it and witout rebooting the phone ===> (EFS Folder not empty YET) made a backup in .img format so that i can restore in /dev/block/mmcblk0p3 still not good
so i REALLY need your help and plz do not ask me to go to service center, warranty binary status is 1
Thanks everyone and have a good day
Was i mistaken in the section or there is really no solution for my problem ??
solution
shinka110 said:
Was i mistaken in the section or there is really no solution for my problem ??
Click to expand...
Click to collapse
you need to flash a efs partition via odin. in tar format.
the your phone will boot normally. unistall knox and only then you could put your efs backup to the phone.
nefsation said:
you need to flash a efs partition via odin. in tar format.
the your phone will boot normally. unistall knox and only then you could put your efs backup to the phone.
Click to expand...
Click to collapse
where i can get efs in .tar? i have my old efs but in a single folder.
i have a big problem, more than a simple copy paste, but with prove i don´t miss anything.
this is my original problem and i´m still stucking there.
http://forum.xda-developers.com/showthread.php?t=2665161

TWRP "Cannot restore Modem -- mounted read only"

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

EFS folder deleted and not recoverable from TWRP backup - Verizon Note 4 N910V

Guys i need help as I have lost my EFS folder. Summary of how it happened is as below:
Initially I had Note 4 Verizon version running Lollipop 5.0.1
I used a method to turn it into Developer Edition (DE) and I was successful in doing that.
Once got through that I installed customer Recovery (TWRP) and made a backup for it (including EFS folder and everything else)
After that I got SUPERSU installed and root access to my mobile.
Everything until this point was smooth and no issues until I installed XPOSED FRAMEWORK and my mobile got stuck on the boot screen.
After alot of hit and tries I used TWRP for Factory reset and WiPE DATA.
Since then I was totally lost in a boot loop.
I used ODIN with official ROM (downloaded through SAMMOBILE) for my variant and restored the boot but again my mobile went back to stock version.
Now the problem is that my phone gives me a message "FACTORY MODE IS ON ........................................."
Now my WiFi turns OFF automatically and everytime I bootup my mobile I have to enter passcodes for WiFi every single time.
I have again got it into Developer Mode and got the root access as well but when I check the EFS folder using TWRP, ROOT EXPLORER or any other software which has access to root files I can see that EFS folder is empty.
I even tried restoring the backup through TWRP (first time complete and 2nd time only EFS folder). It shows success but still EFS folder is empty.
Now I need support if anyone can either help me with the EFS file or help me restore the EFS file that I have available through TWRP backup.
In desperate need of help because I have tried every method I can find on this forum or after google results but none is working...
Any support to help it work will be very helpful and save me from losing my only source of mobile communication.
ThankS!!!
Try this:
https://play.google.com/store/apps/details?id=ma.wanam.efs
It saved me before =)
ledzpg said:
Try this:
https://play.google.com/store/apps/details?id=ma.wanam.efs
It saved me before =)
Click to expand...
Click to collapse
Dear this is a software to backup already existing EFS folder whereas my efs folder is totally empty...
Need someone to help me either with Verizon note 4 efs folder or help me on how to recover already backed up efs folder through TWRP..
Hello, I have the same problem with my sm-n910t. have you found the solution.. it would be a big help. thanks in advance.
Find the efs file compatible for your phone from google and install it into your phone using Odin

So this just happened...

So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Kochoa940 said:
I tried flashing the factory image via command prompt but still bootlooping. data partition has not been modified it is still same as stock.
Click to expand...
Click to collapse
Did you try to flash the OTA image or full factory image? I think there is a known problem with the latest build of Pure nexus where some people can't boot past the Google logo. If that's your issue there are workarounds. You should check the Pure nexus thread.
Try a full wipe(without internal) and restore your nandroid without the data partition and let me know how it went.
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
Kochoa940 said:
So I have been running Pure Nexus rom with Elemental X kernel and SuperSU and it's been working just fine. Well I made a nandroid, and flashed a couple new roms to try out. Didn't like any of them better so I decided to restore back to my nandroid. I used TWRP 3.0.2-2 to make the nandroid and when I tried to restore using same version it just constantly bootloops between the Google splash screen and the"Your device software cannot be checked etc etc screen". I did update my radio and bootloader to the newest versions via a flashable zip and also updated my vendor to the latest vendor image N4F26J. One of the roms said my vendor image was out of date or whatever but still booted fine for me to try out. Regardless I have factory reset phone including internal storage and flashed the factory OTA image and still no luck. Odd thing is I can still boot TWRP and also access my internal storage and move files from PC to my phone. It will even flash Roms and everything but it will not get past the Google splash screen. So wth do I do lol?
Click to expand...
Click to collapse
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Vaseag said:
Maybe stupid answer : 1 did you flashed boot.img ?
2. Is your data partition anything like ex4 or f2fs ?
Will it stuck on google logo ? (I had stucl for 10 min once ) or it just bootloops
Why not try to flash 3.0.3.0 recovery and try again?
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
Click to expand...
Click to collapse
Eric214 said:
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
---------- Post added at 05:00 PM ---------- Previous post was at 04:54 PM ----------
If your nandroid contained the efs backup (3.0.2-2 backs it up by default) and you restored your backup with the efs partition your borked since you used TWRP 3.0.2-2. That TWRP has a bug restoring EFS as there is efs.1 and efs.2 and I think it writes both efs 1 and 2 to just efs.1 on the phone which causes the boot loop.
You need to have had an EFS backup and then roll back your twrp to 3.0.0-0 and restore your EFS back from there.
Click to expand...
Click to collapse
Ok I am gonna try and revert to 3.0.0 and restore the EFS and then the backup. Would that be the correct resolution?
Ok so I fixed it!!!!! Btw thank you guys for all your responses!!!
Even though my version of TWRP was 3.0.2-2 this still worked for me following these commands. I randomly found this page and said what the hell I have nothing to lose so I did it and it freakin' worked! anyways here's the link in case anyone else has this issue of not booting past google splash screen
http://www.droidorigin.com/warning-nexus-6p-users-twrp-3-0-2-1/
Again thanks to those who responded and tried to help!

Backuped MODEM via TWRP(cust,permist,firmware, and efs)(mido)

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

Categories

Resources