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
Related
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
Hey everyone
So my i9500 has this problem since while and that's really boring
When I install a stock Samsung ROM or a based one every thing is working correctly
But when installing a stock android based like cyanogen mod based ROMs I get no service
And I can't see me imei
I have lost my imei once and restored it by overwriting efs folder with that I had a copy of
And then flashed a modem and every thing went back normal
Since then no stock android based ROM doesn't have this problem
Tried flashing bootloaders modems nothing solve the problem
So please any help
Thanks
after 2 months of trying i finally solved it thanks any way it was about the way i restored my EFS with i've deleted the folder restored the 2 imei files can't remeber their names then flashed samsung stock took a backup with TWRP then removed the efs folder installed the rom wiped cache restored the back up installed gapps wiped cache the flashed a modem then wiped then restarted then every thing is working correctly
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...
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.
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
fred06007 said:
Hi,
I've flashed TWRP for a sm-G900f via heimdall, booted into TWRP-Recovery, made an backup from the working Stock ROM to sd card, flashed lineage open gapps etc., all works well.
Because of somtimes not working Sensors I've tried to test if the sensor problem is an hardware or an software issue, so recovered the stock rom backup using the installed twrp 3.2.1-0. Therefor I've made these steps :
Boot into recovery
Wipe cache, system, davlink-cache, format data
restore the stock rom backup
reboot
Every reboot results in booting to recovery, Samsung system won't start.
Tried to disconnect battery for a few minutes etc.
Where is my mistake ? Could someone give me an advice ?
Every restore of the lineage backups using this way works well.
Regards
Fred
Click to expand...
Click to collapse
Corrupted backup maybe?
A long time ago I made a backup of stock and was able to go back and forth with no issues. You can try and go back to stock, root again and try another back up.
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
fred06007 said:
Corrupted backup ? It's the only one I've made after flashing TWRP and before installing Lineage.
Click to expand...
Click to collapse
It happens sometimes, I had an SD card with a bad sector so every time I would make a back up it would get corrupted if I deleted the back up. I ended up leaving the backup so it will no longer write on the bad sectors.
fred06007 said:
Where is my mistake ? Could someone give me an advice ?
Click to expand...
Click to collapse
I think, you have to flash or restore the right kernel.
Which partitions have you backed up?
Sorry for the late response, the backup includes in my mind system, data and boot partition because the backup consit's of the following files:
boot.emmc.win
boot.emmc.win.sha2
data.ext4.win
data.ext4.win.sha2
data.info
recovery.log
system.ext4.win000
system.ext4.win000.sha2
system.ext4.win001
system.ext4.win001.sha2
system.info