So I had a custom rom on my phone and it went in to a boot loop and after messing about I wiped the wrong partition and now have no IMEI on the phone. Worse still cant find the back up of the phone so unable to restore. Its ok as I have a second Mi4c with sMiUI on and working flawlessly but I would like to recover the non working one. I still have the IMEI, SN etc on the box but need a way to get it back on to the phone.
The phone is not bricked, I have sMiUI back on and can flash back to MIUI if needed but the phone works just no IMEI so unable to connect to the network.
So after a lot of googling and translating Russian and Chinese posts it seems my best option is QPST however I cant seem to find a diag driver for this phone. So QPST isnt recognising my phone.
I dial *#*#717717#*#* to enter diag mode, run device manager and see my phone showing that there is issues as no driver for this mode. I tried the Mi2 diag driver in the hope it would be compatible but it doesnt seem to be.
So now Im at a wall that I cant seem to get over and was wondering if there was anything else I am missing. A fresh pair of eyes is needed as I have flipped through so many browser tabs. Maybe I have missed the correct driver or another route is needed.
Any help is appreciated.
D.
Bump for help?
what qualcomm chip do you have
nckfrs said:
what qualcomm chip do you have
Click to expand...
Click to collapse
Thanks for replying. Its a Qualcomm Snapdragon 808 hexa-core 1.8GHz
Maybe you can find it here :
http://www.technokick.com/2015/05/find-imei-number-of-a-lost-android-phone/
But putting it back on your phone is an other thing...
---------- Post added at 11:26 AM ---------- Previous post was at 11:19 AM ----------
For putting a french IMEI, I saw this :
with terminal emulator try :
echo ‘AT+EGMR=1,7,”IMEI_1″‘ >/dev/pttycmd1
echo ‘AT+EGMR=1,10,”IMEI_2″‘ >/dev/pttycmd1
If you have a $
It did something
On the tutorial I saw, reinitialisating should recreate an IMEI.
It's weired but it's something I saw there :
http://www.android-mt.com/tutoriel/hackzone-changez-numero-imei-16379
No guarantee it will works...
What did you use to wipe the wrong partition?
Can't you flash miui ROM with their recovery tool?
Cool ill check out those links now.
I wiped with TWRP as formatted and cleared the entire phone. Im in Beijing and theres a Xiaomi store I may end up taking it to if I dont get any further and see what they can do.
Didn't know twrp had such a dangerous setting that wipes the imei
Dosk3n said:
I wiped with TWRP as formatted and cleared the entire phone.
Click to expand...
Click to collapse
There's no such option to clear the entire phone in the wipe menu of twrp. It's dalvik cache, system, data, internal storage, cache and USB.
What did you do to have imei removed?!?!
As stated in the quote you posted I formatted the phone. I wiped first when I first flashed the rom and the phone worked fine. I changed the phones band in the phone settings and it went in to a boot loop and wiping wouldnt fix, flashing wouldnt fix so I first formatted it again didnt fix so I then MiFlashed and it was working but with no IMEI. Although it could have been changing the band that corrupted the IMEI now thinking of it I assumed it was the format that removed the partition with IMEI. Regardless though the phone now has no IMEI. I have another Mi4c working fine with SMIUI so its in no rush to fix this broken one and since it doesnt look like its possible publicly Ill have to get in contact with Xiaomi at some point.
Can't you change the band again?
Dosk3n said:
As stated in the quote you posted I formatted the phone. I wiped first when I first flashed the rom
Click to expand...
Click to collapse
I don't understand you saying "I formatted the phone." Meaning you wiped dalvik cache, system, data, internal storage and cache? None of those partitions have anything to do with IMEI. You might have flashed a mal ROM with MiFlash??
qtotter said:
I don't understand you saying "I formatted the phone." Meaning you wiped dalvik cache, system, data, internal storage and cache? None of those partitions have anything to do with IMEI. You might have flashed a mal ROM with MiFlash??
Click to expand...
Click to collapse
He deleted the modem. it happend to me to,i mannage to write it back searching internet but still no sim signal..
nvm. pls delete
Related
Hello,
This is going to be kinda long, I want to give all details I can remember in case it helps.
I decided this morning that I was going to try out the unofficial CM11 rom for Galaxy Nexus GSM. So, first thing I do is a backup from Clockwork Recovery (latest touch recovery flashed).
After that, I flash the rom, and the gapps. I reboot to see if it works, and after 5 minutes of use everything looks pretty sucessful.
So, adb pull my backup and offload it to my computer in the case that something goes really wrong, because I'd like to get a clean start. So, I wipe the device as completely as I can in Clockworkmod Recovery. I then adb push the cm11 rom and the gapps roms referenced above. I use Clockworkmod Recovery to flash those onto the device, reboot and start playing around then realize that I have no cell service. Try manually registering on my T-mobile to no avail.
I think this is a baseband problem, so I fastboot flash radio (stock nexus radio rom from 4.3), reboot into the system and still no service.
Then I begin thinking my phone radio has completely failed, so I take a simcard from my girlfriend's phone pop it into mine, reboot and still no service. Reinstall my original sim card.
Then I am REALLY thinking my radio has failed, so I figure I'll just flash the full 4.3 stock suite in case I'm missing something small because I don't understand how something works. Still no service.
So, as a last resort, I push the Clockworkmod Recovery backup back into the /sdcard/0 directory, restore in Clockworkmod Recovery, reboot and it works(!).
Now I start wondering what I'm failing to understand about this problem, so I go ahead and do a factory reset in Clockworkmod Recovery and back to no service(!).
I really thought I understood how it worked, but I must be missing something here, or maybe Clockworkmod Recovery is wiping something it shouldn't be? The final thing I can add is each time I fail to get service in the installation, the service bars light up for 1/2 second to 2 seconds during boot. Maybe someone could help me spitball what's happening here?
Thank you very much in advance.
I think all yu must do is download the latest stock firmware ment for for your device.. from internet.. and install that properly on yur device.. this will do every thing right.. see I too am not at all good with using programme stuff and so.. therefore I keep the copy of firmware with me always.. that helps when I almost destroy my phone
tc and good luck..
---------- Post added at 04:01 AM ---------- Previous post was at 03:56 AM ----------
and it might be possible thet the rom which yu are trying is not ment for your device version.. chack that too correctly..
Problem found (not yet solved, but that's another question)
OK, I found the problem. My non volatile memory got corrupted. I pulled an image from the EFS nv memory partition devfs file, mounted it as loop on my localhost and got nothing but a lost+found directory. It's not a terrible thing, but from now on when I wipe this phone, I will need to adb push my /data/radio backup to the EFS nv memory partition. That is, at least until I find out exactly what I need to do to reconstruct the memory partition. Shouldn't be that hard, but I really need a good description of what is in all the EFS memory partition files for the Galaxy Nexus. :good: I'll dig around the forums a bit, maybe ask someone for the directory structure, maybe I'll be able to, at least, partially restructure that memory partition with a good old dd'ing. Maybe I'll root my girlfriend's Galaxy Nexus so I can get the structure proper.
Hope this helps someone else!
SOLVED! see solution in the first comment.
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
hbhc123 said:
I really need some help...
I installed manually 4.4.1 version using this guide: http://forum.xda-developers.com/showthread.php?t=2523217
(I am having a rooted device with TWRP without any modifications or deletions - used section B)
after the install successfully worked, i chosed to wipe. it was stuck and i used the powerbutton to reload device.
when the device turned on it used emulated storage which means no imei and no efs.
using the twrp (in recovery mode) i can see my full data and efs files.
when i am trying to rewipeqinstall update i get this error: "E:/Unable to mount /cache"
please help me.
Click to expand...
Click to collapse
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Synyster06Gates said:
Do not turn the device off while clearing the cache.
Reboot to recovery, go to TWRP settings and enable rm -rf option, go back and wipe the cache/dalvik. If THAT doesn't work, you will need to flash the cache.img from the factory image found here http://forum.xda-developers.com/showthread.php?t=2513701
After you do that, make sure you have the latest version of TWRP installed (2.6.3.4) If you don't you can also choose to install that via ADB before clearing the cache.
Click to expand...
Click to collapse
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
hbhc123 said:
First of all - thanks for help.
already tried the rm -rf option unsuccessful.
2 question before I'm starting the flash process:
1. Is there a way dumping the efs folder to my computer before?
2. is this the command i should use: "fastboot flash cache C:/image-hammerhead-krt16m/cache.img"?
thanks a lot.
Click to expand...
Click to collapse
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
chi_heng said:
clearing cache/dalvik is very slow on N5, I found, and so is resetting the phone in recovery. though the progress bar may not move the process isn't stuck, it's still going on in background.
Click to expand...
Click to collapse
Flash the newest version of TWRP. The issue is fixed.
Synyster06Gates said:
1. Use TWRP to back up your EFS data if you would like. You won't lose any data by just flashing the cache though. All your apps and everything should still be there.
2. If you installed the drivers correctly and that is the correct directory for the file on your computer, that is right! I put mine on the desktop for simplicity.
Click to expand...
Click to collapse
I have done what you said and it worked perfectly
many thanks!
hbhc123 said:
I have done what you said and it worked perfectly
many thanks!
Click to expand...
Click to collapse
No problem! Glad you got it taken care of.
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
any one else
benbailey84 said:
What should one do if fastboot flash cache doesnt fix it? im having same issue and i have tried restoring stock, flashing cache, etc. still no imei showing in settings and sim doesnt get reconized. Hangouts fc, google search fc and i cant access sd card in windows or the phone.
Click to expand...
Click to collapse
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
ddloco said:
I guess me and you are screwed I tried every suggestion on the forums but nothing works I'm just gonna RMA mine and pray that Google doesn't say its my fault I wish someone could help us I gotta send mine off as fast as possible im already looking at two weeks minimum for the RMA so every day I wait is just more time I won't have a phone thanks
Click to expand...
Click to collapse
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
benbailey84 said:
yeah i have a rma out for mine. Luckly i have a spare phone (its a damn $15 go phone) but mine is already shipped. biggest issue is the $440 is tied up in my account until they get the bad phone back. basically i would suggest to anyone that if they are going to flash a rom first thing they should do is back up their efs to their pc and also some sort of could (dropbox, drive, mega, box, etc).
Click to expand...
Click to collapse
Well in our case I have my efs on my PC from weeks ago restoring it doesn't fix whatever the ROM changed lol
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
oble said:
It could be an issue with the modem not being flashed properly when you went from Lollipop to Marshmallow due to TWRP 2.8.7.0. Try TWRP 2.8.6.0, and then either restore the nandroid backup or clean wipe + reflash CM13 nightly.
Click to expand...
Click to collapse
Thanks a lot for your response. I've been searching a lot and the problem effectively seems to be the modem not being flashed properly. So I tried to flash it manually, (found the file 2 threads higher, sorry I can't post links yet) via fastboot and then flashing cm13 (with twrp 2.8.6.0), considering the fact it seems to have worked for others.
But no matter what I do, the issue remains : the phone isn't able to detect SIM card and goes into crash, rebooting every 2mn..
I've tried to flash cm13 unnoficial version by sultan, following his instructions, but no improvement either.
Even my nandroid backup (running cm 12.1) can't detect SIM anymore, have serious wifi connectivity issues, and keeps rebooting randomly at very reguliar intervals..
I'm really beggining to feel hopeless,
but thanks again for your time and your advices, really apreciate it.
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
gersa said:
It seems that I have same problem..... after flashing CM13 and restoring backup
Any progress with this problem?
Edit - If my phone is connected into PC with USB cable it doesnt restarts
Click to expand...
Click to collapse
Same for me, the phone stops crashing and rebooting randomly once connected to pc via USB cable. But still doesn't recognize SIM card. Wifi also seems to work better.
No further progress unfortunately, I've tried everything, from restoring the phone to its factory state to flashing all "stable" roms (cyanogen), nothing worked.
MethylHaine said:
Hi everyone.
Let's start from the beginning, and by advance excuse me for my poor English : I happen to be a delighted owner of the Oneplus One by the Oneplus company. I've flashed different versions of cyanogen on my phone, rooted it multiple times and I never encountered any kind of problems. Thus, until I decide yesterday to flash the latest release of cyanogen, cm13 (nightly). I did some researches, followed the usual steps, flashed the right opengapps version along with cm13 and.. everything went great. Except that my phone couldn't resolve himself to detect my SIM card anymore. I tried different things in order to solve the problem, including re-wipe the phone "factory reset" style, removing SIM card, wait for the phone to cool down and played with data roaming, but nothing worked. Fortunately I had my fresh nandroid backup waiting to be restored. That's when the real deal start :
even after having restored the full nandroid backup (which make me downgrade to cm12.1), the SIM card wasn't detected.
So I decided to wipe data, dalvik, cache and system, in order to get my phone back to its original state. But the problem remains, and worst of all, the phone now tends to reboot punctually without any reasons.
I surely did something wrong for the phone to end in this state, but I can't see what..
I use TWRP 2.8.7.0 custom recovery, and the phone OS is now cm12.1-YOG4PAS3JL.
Oneplus One 64GB.
Sorry for the length of the complaint, and by advance thanks for your answers.
P.S : I did tried to search for similar threads in the forum, but I didn't manage to found anything that was directly related.
Click to expand...
Click to collapse
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
Already saw it, but thanks ^^ that's where i found my file modemst.bin
so did it work for you ?
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only this solution worked for me, and I had to do it twice. I don't know why.
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
jp.esteban said:
The same thing happened to me last week. I was using Materialized TWRP 2.8.7.0, which I think caused issues with my updating of Sultanxda's 13.1 ROM. SIM card was never detected, phone would restart shortly after every boot. I tried everything I could find to get my baseband and IMEI back.
In the end, only [link] this solution[/URL] worked for me, and I had to do it twice. I don't know why.
Click to expand...
Click to collapse
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
ashishsaggu said:
I had the same problem. I got back to TWRP 2.8.6.0 and then flashed the latest CM13(wiped System). after that without wipe i flashed sultans's CM13 then gapps and got the sim working again.
Click to expand...
Click to collapse
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
MethylHaine said:
I've tried multiple times, it doesn't work. SIM card is not recognized, phones goes to reboot after 30s of use.
Whatever rom I flash the problem ain't solved, even after factory reset from original OS (cm 12.1)..
I really begin to think there is no solution, I've tried to flash my phone at least 20 times with different roms, fix, firmwares, modem, everything that is available on the net and I couldn't notice even the slightest change in the comportment of my phone.
Anyway, thanks a lot for your proposal, I guess it HAVE to work, but for some irrational reason it doesn't...
Click to expand...
Click to collapse
Did U flash over TWRP or ADB?
Just popping in to say I have the same problem. I'm trying the various solutions presented in the thread and I'll come back and report if anything worked. I would also appreciate any other suggestions that you may have
For the record, I got into this predicament through the following steps:
1. I was flashing some CM nightly (sorry, I don't remember which one), and after reboot the touch screen didn't work anymore
2. I flashed the OxygenOs .zip that I had saved on internal storage through TWRP
3. After flash touch screen worked but no sim detected
4. Flashed CM 12.1 still no sim
5. Flashed back to OxyOs, still no sim. Curiously I am unable to reboot via software.
Anyway, I basically have all weekend to work on this, so awayyyy we go!
---
<Edit>
Wow that was fast. I followed this guy's instructions (fastboot flashing modemst, then CM12.1) and it seems to be working like a charm! Good luck everybody else!
gersa said:
Did U flash over TWRP or ADB?
Click to expand...
Click to collapse
I flashed via TWRP(2.6.8.0) and via ADB for modemst1.bin and modemst2.bin.
By the way, there's a little improvement : I flashed kalkulin's_stock_OPO Rom and that stopped my phone from rebooting.
Now cm13 is running kinda fine, except it still doesn't detect SIM card, even after reflashing modemst1 and modemst2
Edit : When I try to flash oxygenos, oneplus fix or cm12.1, (roms that are supposed to fix sim detection problem), it doesn't work : Error flashing Zip file. via adb or twrp, that's the same. (excepting the fact that error in adb is about trustzone)
I think my efs partition is somehow corrupt, and unfortunately i have no way to restore it.
MethylHaine said:
Thanks for the link. I tried to flash the zip, but twrp(2.8.6.0) gave me an error : Error flashing ONEPLUS+ONE-FIX-Windows.zip
I tried to clean flash it and dirty flash it, nothing seems to work.
Click to expand...
Click to collapse
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
jp.esteban said:
It's not supposed to be flashed. Unzip the archive on a Windows PC, then use the .bat files in there to fix your phone.
Click to expand...
Click to collapse
Effectively, I kinda did things completely wrong there, sorry. (I'm an exclusive linux user for my defense ^^)
Okay guys, I finally solved my problems.
Here's what I did to fix reboot crashes and SIM detection issues :
-Flash TWRP(2.8.6.0)
-Wipe everything except internal storage
-Flash Calkulin's_Stock_OPO_XNPH44S_ROM_v1.0.zip (can't post links yet, sorry)
-Boot system
-Once done, reboot to bootloader (in command prompt : sudo adb reboot bootloader)
-In command prompt, type the following commands (It will delete modem and /persist partition ! be careful) :
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
-If you need to fix "Unable to mount /persist" error in TWRP :
adb shell
make_ext4fs /dev/block/mmcblk0p15
-Flash Oxygen OS (i flashed oxygen_1.0.0_flashable.zip)
That should restore EFS and fix the issues.
Well, that was kind off a pain in the ass, but now my problem is solved, and i'm currently running cm13 quite fine.
Make a backup of your EFS partition.
Thanks to all the people that helped me by posting in this thread !
It's a nightly build, it bound to have some problems.
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
---------- Post added at 03:08 AM ---------- Previous post was at 03:07 AM ----------
gersa said:
`
Here is solution (for me)
http://forum.xda-developers.com/showpost.php?p=64768887&postcount=3
Read whole, its short
Click to expand...
Click to collapse
i am having bootloop issue, tried many roms, erased partition too, still no use. continuous bootloops
Hey guys,
and thank you in advance for helping me!
Well, yesterday I wanted to install the latest Lineage OS on my S7. As usually I installed TWPR (latest version) first, put the Lineage image on the SD Card and flashed it. However sth went wrong and my "data" partition was wiped as well... Now ithe phone was only booting into the TWPR Bootscreen. Nothing else happend. So I thought i messed it up.
So i formated everything possible into "EXT 4". Finally I could run TWPR again and also install the Lineage OS. So far so good... However now my Sim Card is not detected. I tried to reinstall the Lineage OS serveral times - the issue stays the same!
I used latest Odin3 on a Win 10 machine to install the TWPR...
My provider is 1&1 if that matters.
Can anyone please help me? Because I just called a Samsung certified reseller and they told me, that the only chance is to install a new motherboard, which will cost around 300€!!!!! Thats not an option, when u take a look at the prices right now for a new S7
Thank u sooo much!
Have you also formated your EFS partition? Your IMEI is stored into this partition and without IMEI the phone cannot log in into a mobile network.
If you have a backup of your EFS partition, restore this, and the SIM should work fine.
Phone does not detect SIM
profi_fahrer said:
Have you also formated your EFS partition? Your IMEI is stored into this partition and without IMEI the phone cannot log in into a mobile network.
If you have a backup of your EFS partition, restore this, and the SIM should work fine.
Click to expand...
Click to collapse
Hey,
I have the same issue today, how can I get EFS partition if for some reason I have lost it?
I still have phones imey at the back of the phone though.
Just male a backup of the EFS and store it at a save place (PC/Cloud). If the IMEI on the phone wont work, just copy it back from the PC to the Phone
I currently own a GT-N8000 running the lineage 16 os, but theres no sim detection going on, & I'm having issues with efs partition staying mounted.
Tweaker Z said:
I currently own a GT-N8000 running the lineage 16 os, but theres no sim detection going on, & I'm having issues with efs partition staying mounted.
Click to expand...
Click to collapse
Hi,
you are the first person who mentioned this problem.
In usual cases, this is working fine.
How was it before you've installed LOS16?
Is there general a mounting problem with EFS?
Is your baseband working or unknown?
It works sir, even sim detection started working, but no signal at all, i assumed so because i saw some threads about using sim, and bugs with phone calls.
html6405 said:
Hi,
you are the first person who mentioned this problem.
In usual cases, this is working fine.
How was it before you've installed LOS16?
Is there general a mounting problem with EFS?
Is your baseband working or unknown?
Click to expand...
Click to collapse
Yes sir, there's a mounting issue with the efs partition
Tweaker Z said:
Yes sir, there's a mounting issue with the efs partition
Click to expand...
Click to collapse
Does it work with stock rom?
The most important thing, dont wipe or format efs!
This will destroy your imei data.
html6405 said:
Does it work with stock rom?
The most important thing, dont wipe or format efs!
This will destroy your imei data.
Click to expand...
Click to collapse
Never wiped the efs, i got the note as a christmas gift from an aunt, it wouldnt boot up, checked stock recovery, it said "failed to mount efs (invalid argument)" i didnt know any thing about that, so i thought flashing stock rom would fix it, it didn't. One way or another i finally got it to boot, but it displayed a transparent window with yellow letters on the home screen. If i left the home screen, the window disappeared. So i decided to switch to custom rom, but anytime i enter twrp, i still get the efs not mounted error, i usually mount it manually to stop the error from showing, i still have imei so i'm not sure the efs is corrupt.
Tweaker Z said:
Never wiped the efs, i got the note as a christmas gift from an aunt, it wouldnt boot up, checked stock recovery, it said "failed to mount efs (invalid argument)" i didnt know any thing about that, so i thought flashing stock rom would fix it, it didn't. One way or another i finally got it to boot, but it displayed a transparent window with yellow letters on the home screen. If i left the home screen, the window disappeared. So i decided to switch to custom rom, but anytime i enter twrp, i still get the efs not mounted error, i usually mount it manually to stop the error from showing, i still have imei so i'm not sure the efs is corrupt.
Click to expand...
Click to collapse
Ok this doesnt sound so bad, if the shown imei is yours (and not a 0049****** IMEI),
you just have to disable factory mode and your sim card detection should be back.
But TWRP should be able to mount it!
I'm pretty sure, that I could fix your problem (build some things years ago to fix a corrupt efs dumps, withoult loosing the imei and certificate).