Related
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Have you tried flashing different radios (baseband)?
http://forum.xda-developers.com/showthread.php?t=1785999
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Take a look at this thread, it may help. http://forum.xda-developers.com/showthread.php?p=25172599#post25172599
thanks for the replies...
I've flashed UCM1 and UCLL3 radios, they flash fine but no change...still can't flash to stock and no imei/baseband/service.
That fix thread was one of the first I found, but as I still have my keystr file in the efs folder, I didn't think it would apply to me...I suppose I could make an external backup of my efs, delete it and try one of those methods from scratch.
read through the restore to stock sticky http://forum.xda-developers.com/showthread.php?t=1652398 and go through the trouble shooting sections, if that doesn't help u could have bad hw
causticfix said:
so I have a SR I just put a new (used, off ebay but new to me) motherboard in, and it works fine except for no imei/baseband, so obviously no data/voice/etc.
the efs folder seems to be fine...imei folder is in there, keystr file is there...I don't understand what the problem is.
the worst part is, only certain roms will flash...I cannot flash to stock, I've tried with odin and from recovery, a couple different stock versions of GB, ICS, and still no luck. It actually flashes, then does the "android is upgrading" screen, but then bootloops on the optimizing apps part. I've tried to flash to stock probably 20 times now, wiped everything, fixed permissions, etc...without fail it bootloops every time.
the only roms Ive gotten to flash are slim and jedi...no stock rom will flash, nor avatar and a couple others I've tried. but slim and jedi flash and boot right up...just have blank imei/baseband.
I've scoured threads for days trying to figure out what to do here...nobody seems to have my exact problem, and everything I've found about restoring efs/imei/baseband has involved flashing to stock...which I can't do.
anyone have any ideas?
Click to expand...
Click to collapse
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
Just factory reset when it boot loops
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Vgkiller said:
Hey, Im facing the exact same problem! just that my imei turned to 0 and basband to unknown after i upgraded to cynogenmod 10.1-rc.2.
It was working fine till suddenly one day i lost network. I tried everything like you did. So far ive had no luck fixing my efs!
What you can do is download QTPS and in it there is a RF NV Item manager to rewrite your efs. For that you need to put you phone into DIAG mode unfortuantely i cant get to that on 10.1nightly cynogenmod that im using.
I m stuck. I know for sure flashing roms or radios wont help at all. the same boot loop problem happens when I flash using odin, it use to work perfectly fine earlier.
Some how the nv_data.bin and such files are missing from my efs>imei folder that contain the imei data.
If you find something please lemme know too [email protected]
Click to expand...
Click to collapse
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
causticfix said:
will do.
also, you may know this already, but just in case, be aware the skyrocket doesn't use nv_data.bin...I thought it did too when I first started searching around about this, and when i couldnt find it I was pretty freaked out...but then i found out the skyrocket actually uses 3 encrypted partitions rather than a nv_data file. so if you have at least some files in your efs/imei folder you may be in a better spot than it seems. of course if its totally empty, you'll likely have a lot more work to do.
I'll update if I have any luck.
Click to expand...
Click to collapse
Yes I have two files in my imei folder i,e keystr and mps_code.dat!
I tired changing them from root explorer! pasted someones else's efs folder! but still I cant fix my imei is stays 0.
i donno how to get to diag mode with this rom, otherwise i could have tried my luck with QPTS.
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
lingowistico said:
Incase you have broken your imei without backing it up, there is another way. And yes it is legal.
Here's the tutorial http://goo.gl/wtW29 and here's the needed tools (software & hardware) http://goo.gl/54mtk.
Click to expand...
Click to collapse
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
causticfix said:
I actually have octopus box as well as the z3x samsung tool installed, however, they're both server activation based...the software is useless without an $89 (octopus) to $120( (z3x) activation.
I'd rather not spend that kind of money for something I'll likely only need once, so I'm gonna do as much as I can in the way of free solutions, and if I have no luck there I'll probably just send it to mobiletechvideos for their $40 efs/imei repair. I'm guessing they use one or more of these repair box programs themselves anyway, and will do the same job for only $40.
thanks for the suggestion anyway though..
Click to expand...
Click to collapse
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
lingowistico said:
There's this polish guy who probably also has all the same boxes and he takes €10 for imei repair by remote desktop.
http://forum.samdroid.net/f70/repair-imei-s2-5729/
And finally you could try helping the op of this thread to add compatibility for skyrocket, this would be free.
Click to expand...
Click to collapse
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Vgkiller said:
Isn't there any way to fix my imei on my own ?
Mt efs folder also looks good now with all the files it should have but still the imei remains unaffected.
Also i'd like to know that the qualcom nv tool showed my esn as dead and mied as 000....000 does the dead thing mean it isnt repairable ?
I tried using QPTS but this is where I get stuck.. (img attatched)
Click to expand...
Click to collapse
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
lingowistico said:
Obviously there is since some random polack can do it for you on his PC, the problem is the lack of knowledge.
Those who know won't tell you how, because they want € for it :crying:
Click to expand...
Click to collapse
This totally defeats the purpose of this forum then. Its sad.
Vgkiller said:
This totally defeats the purpose of this forum then. Its sad.
Click to expand...
Click to collapse
People want money for it because it's mostly used for making stolen phones work again.
That means real life risks like fines, jail etc.
Of course there are lots of examples when people experiment with this or that and delete their imei accidentally, or want to change the imei for some other reason. But these are more rare.
An update...
I managed to finally get flashed to stock...still null/null imei & baseband unknown. Efs folder is still there with files, keystr file is on...not sure what else I can do myself at this point so, I guess its time for the Polish dude or mobiletechvideos.
Hi People,
Did any1 found any solution?
talk2sharn said:
Hi People,
Did any1 found any solution?
Click to expand...
Click to collapse
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
causticfix said:
unfortunately not for me. I finally got the polish dude to try restoring the imei remotely...he used like 3 or 4 different programs, nothing worked.
so, i just got a broken SR with a cracked lcd off ebay for $50 and used the motherboard from it.
Click to expand...
Click to collapse
Ohkies.
Did you ask the polish guy about the reason why he was not able to fix your mobile. Coz, I'm just having similar problem like yours. I tried working with all the local samsung service centre guys, nothing worked. One guy said that my mobile IMEI is locked in some database, so it is not picking or detecting my SIM, hence locked. I know that my mobile is unlocked and is valid, I ignored his comments.
I assume you changed your MotherBoard of the mobile with the new cracked SR's, so that it could take new IMEI instilled in new board. Is it so?
Also, please suggest me about any alternatives on how to fix this problem.:crying:
Hi,
some issues with my brand new Xiaomi Mi 4i.... I'm getting reaaaally tired of this.
My story with this phone went well for a day. Then I tried to install a french ROM and I guess I did something wrong cause my phone was hardbricked. I managed to recover from that (throught steps I couldn't really remember, I tried so many things) but when I put my SIM card on my phone, it's not detected anymore, despite working on another device (a Lumia 1320)
I read it might be an hardware issue (and not covered by warranty, which is a real shame), but some stuffs tells me otherwise :
- the card was working before the hardbrick;
- MiPCSuite is messed up: it worked perfectly before the hardbrick, but now it's considering my phone as a "mi device" (and not a Xiaomi Mi 4i), I can't backup anything because my phone "isn't up to date" (despite having installed MiUI7 to check if the issue came from MiUI6 for some reasons)... I know it's nothing really important, but it might indicate that it's software related... right ? :crying:
I took the hardbrick well because I know it was my fault, and my fault only. But now that I have this issue... I'm kinda pissed. And the fact is that I don't have any center near me, because I'm in France (explaining why I tried to install a french rom and why my english isn't the best), so if I have to send my Mi 4i back, it will cost me a lot AND I won't have my device for monthes...
If you have ANY information that could help me, I would gladly take it. Thanks !
Edit : "baseband" is marked as unknown. Guess it matters...
did you backup your EFS (EFS Backup) before flashing custom rom? if yes then try tro restore your efs with twrp (i assumed you used twrp)
Danusyakti said:
did you backup your EFS (EFS Backup) before flashing custom rom? if yes then try tro restore your efs with twrp (i assumed you used twrp)
Click to expand...
Click to collapse
My motto always has been, and I know it's a very stupid motto, "if you backup, things are going to mess up". I never backedup anything, assuming everything would go according to plan.
So no, sadly, I don't have any EFS backup (or any backup at all...). I used TWRP, but since my phone resurrected, I didn't have the guts to reinstall TWRP. If I don't have any backup, it would be useless, wouldn't it?
I'm gonna try when I'll can to redo a full factory reset + fastboot flash using MiFlash Tools. Read it worked for Xiaomi Mi4, but don't have much hope. I guess the issue relies on something else than just a ROM. ( but I might be wrong, once again I'm really not an expert and this is my first Android device ( and yeah, yeah, I was stupid ) ).
try FastBoot Flashing, open this link
http://en.miui.com/thread-112662-1-1.html
i hope it only software related, not hardware related
*btw can you do imei checkup with your phone?
Danusyakti said:
try FastBoot Flashing, open this link
i hope it only software related, not hardware related
*btw can you do imei checkup with your phone?
Click to expand...
Click to collapse
I hope the same thing than you
By IMEI checkup, did you mean verify if my MiPhone is a legit one? If yes, yeah, I tried and it's an official one.
If not, in the "Details", neither IMEI or IMEI SV are known.
poneyroux said:
I hope the same thing than you
By IMEI checkup, did you mean verify if my MiPhone is a legit one? If yes, yeah, I tried and it's an official one.
If not, in the "Details", neither IMEI or IMEI SV are known.
Click to expand...
Click to collapse
no i mean with *#06#
i you can't it meant you lost your efs, if detected just try flashing again with link above
good luck
Danusyakti said:
no i mean with *#06#
i you can't it meant you lost your efs, if detected just try flashing again with link above
good luck
Click to expand...
Click to collapse
It says "Invalid IMEI"... I flashed as your link said, but didn't work...
Well. "All I have to do" is to fix the two corrupted IMEI files. I found which ones are appropriate : mmcblk0p20 et p21.
I guess they are corrupted, I don't really know... Dunno if there is anyway to fix this, maybe by modifying the files with notepad or something like that. Really, I don't know, but I'm kinda despaired.
This might help
forum.xda-developers.com/mi-4i/help/strange-bricked-wifi-bt-radio-t3210529
This guy had the same problem.. I tired helping by using extended twrp and uploading it. He seemed to have fixed it. Try posting there
sharan.nyn said:
forum.xda-developers.com/mi-4i/help/strange-bricked-wifi-bt-radio-t3210529
This guy had the same problem.. I tired helping by using extended twrp and uploading it. He seemed to have fixed it. Try posting there
Click to expand...
Click to collapse
Thanks. Gonna try this.
Quick question : could you upload somewhere your mmcblk0p20 and mmcblk0p21 files for me to compare with mine?
Two ways to get it : with mi4i toolkit (EFS backup, it will be stored on /sdcard/efs-backup) or by following the tutoriel by magdag :
http://en.miui.com/thread-59832-1-1.html
Hi, it's me again,
I contacted the saler of my Mi 4i to ask if he knows any way to repair it or why. I was very surprised to see that the website proposed me 1) A partial refund (40%) on the websites account 2) A total refund (but the item is shipped at my cost) or 3) The same phone, half price, without the need of being reshipped.
I'm very surprised that it's covered by warranty... any ideas about that? Any chance that once I've shipped my Mi4i back, they'll ask me to pay for the replacement?
i am facing similar issue but my sim is not detecting on first slot but it is detecting on second slot
even my imei is showing correctly should is go for replacement coz i bought it few days back
If the SIM card tray is damaged (for example, a piece of plastic is chipped off or a metal plate is deformed), this can be the cause of the problem when the Xiaomi smartphone does not see the SIM card.
I had such a situation on my Mi 3. In the service center they could not find the cause of the problem, I found it myself.
I hope this information will help to somebody.
Hey everyone! I had flashed Lineage 14.1 on my Samsung J210F(https://forum.xda-developers.com/an...ageos-14-1-t3680656/post74433279#post74433279)
And everything was working perfectly until I wanted a file from the stock ROM. I flashed the stock ROM and after my work was done, I flashed Lineage again. Now in the middle of this flashing I lost my network. I tried changing the APN settings and even tried putting it on GSM Only but it's of no use. The network comes and goes abruptly. I even tried going back to the stock ROM but now it's the same over there too. My radio band and everything is as it is. I just can't figure out what's wrong. I have tried reflashing multiple times. There is no problem with the physical hardware or the sim as I have tried it with a different phone too. I haven't touched my efs file either.
Any suggestions would be appreciated!
Somebody please help. I just cant find any solution to this. I've been through each and every forum possible but I still cant find anything. IMEI and everything is normal. I did try to flash the stock rom and the stock rom receives network but as soon as I switch to custom rom, the network goes away. Please help
Bump
DoHave a look at your IMEI status with *#0011#
If it's NG you may have inadvertently corrupted your EFS partition. I dealt with that myself recently. If that's the case, if you've got a backup of the EFS, try to restore it. If not, backup your EFS to your PC or another secure external location, in case of worse emergency later. Then empty your EFS folder except for the FactoryApp and prov_data folders and their contents, then flash a clean firmware with Odin.
This can backfire. Read-up and Backup before proceeding.
I have no further expertise to offer. I just blundered out of messing up my EFS during flashing.
Crike said:
Have a look at your IMEI status with *#0011#
If it's NG you may have inadvertently corrupted your EFS partition. I dealt with that myself recently. If that's the case, if you've got a backup of the EFS, try to restore it. If not, backup your EFS to your PC or another secure external location, in case of worse emergency later. Then empty your EFS folder except for the FactoryApp and prov_data folders and their contents, and reboot.
This can backfire. Read-up and Backup before proceeding.
I have no further expertise to offer. I just blundered out of messing up my EFS during flashing.
Click to expand...
Click to collapse
Yes I have backed it up before but this case isn't about that. I have the proper IMEI number. I'm just not getting signal and it's becoming really frustrating now.
I even tried going back to the stock ROM but I'm not getting any signal there either. Please see the picture attached
darshan1504 said:
Yes I have backed it up before but this case isn't about that. I have the proper IMEI number.
Click to expand...
Click to collapse
I seemed to have the proper IMEI, too, but it's status was NG anyway. Check *#0011# if you haven't yet, to verify.
Crike said:
I seemed to have the proper IMEI, too, but it's status was NG anyway. Check *#0011# if you haven't yet, to verify.
Click to expand...
Click to collapse
*#0011# doesn't work for me but *#06# does and this is what it shows
If you can figure out how to get into servicemode on your device (which is what *#0011# does on my device) then you can check the IMEI status, or if you're confident you can restore the EFS partition try the method I described above.
Beyond that, I'm a virtual noob. My only counsel is to be patient and cautious. Someone with actual expertise may advise you yet in the sub-forum for your device or a thread discussing a similar problem.
Crike said:
If you can figure out how to get into servicemode on your device (which is what *#0011# does on my device) then you can check the IMEI status, or if you're confident you can restore the EFS partition try the method I described above.
Beyond that, I'm a virtual noob. My only counsel is to be patient and cautious. Someone with actual expertise may advise you yet in the sub-forum for your device or a thread discussing a similar problem.
Click to expand...
Click to collapse
The code for me for service mode is *#*#197328640#*#* but I can never get to open it. It just looks blank
There may be other ways to verify the IMEI Status, but that is beyond what I know. Someone more expert may have advice.
Crike said:
If you can figure out how to get into servicemode on your device (which is what *#0011# does on my device) then you can check the IMEI status, or if you're confident you can restore the EFS partition try the method I described above.
Beyond that, I'm a virtual noob. My only counsel is to be patient and cautious. Someone with actual expertise may advise you yet in the sub-forum for your device or a thread discussing a similar problem.
Click to expand...
Click to collapse
Also, I can find FactoryApp but I can't find prov_data folder. This is what my folder looks like. Can you send a picture of yours
If your backup is of your recent, working setup, it might be interesting to compare it to your current EFS. I have no suggestions as to how to inspect the contents of a backup.
Crike said:
There may be other ways to verify the IMEI Status, but that is beyond what I know. Someone more expert may have advice.
Click to expand...
Click to collapse
I'm quite sure there's nothing wrong with the IMEI number. I have confirmed it multiple times. I just feel so helpless. I don't even get to know if someone's calling me. I just hope I can fix this ASAP
Crike said:
If your backup is of your recent, working setup, it might be interesting to compare it to your current EFS. I have no suggestions as to how to inspect the contents of a backup.
Click to expand...
Click to collapse
This is not a backup. This is the actual EFS folder. Anyways thanks for the help. I'll keep bumping till someone else sees it
Also I would like to add that the network sometimes bounces on and off after a reboot so..
My IMEI seemed correct as well. The problem was with something in the EFS partition which resulted in IMEI status NG, and I only discovered this was the issue after seeing the actual IMEI status assessment by the servicemode. I repeat: the IMEI numbers shown by *#06# didn't indicate anything was wrong.
Should you proceed along the path I suggested, make sure to flash a fresh firmware from Odin directly after. It seems to be required to restore the EFS after the procedure mentioned before.
Google "FactoryApp" and "prov_data" before proceeding.
Beyond that, good luck.
Crike said:
My IMEI seemed correct as well. The problem was with something in the EFS partition which resulted in IMEI status NG, and I only discovered this was the issue after seeing the actual IMEI status assessment by the servicemode. I repeat: the IMEI numbers shown by *#06# didn't indicate anything was wrong.
Should you proceed along the path I suggested, make sure to flash a fresh firmware from Odin directly after. It seems to be required to restore the EFS after the procedure mentioned before.
Google "FactoryApp" and "prov_data" before proceeding.
Beyond that, good luck.
Click to expand...
Click to collapse
Btw I did try that code when I had flashed back the stock ROM and it showed IMEI Certificate PASS. I'm sure there's nothing really wrong here because as I said the network sometimes bumps on and off after reboot
I have a question what is the baseband number on the phone? My ROM hasn't been updated for sometime now and I have got official updates for the stock ROM. Does the new update for the stock ROM come with new baseband? Will flashing the update for the stock ROM update the baseband too? Or is that in the kernel? I've read that updating the baseband usually fixes network problems. Please help me fix mine
I just extracted the new update for the stock ROM but I couldn't find any modem.bin file in there. There's just usual system, recovery,etc. If I don't have the modem.bin file how can I flash the radio/baseband? Should I just flash the firmware via Odin through AP or CP option?
Bump
Edited in 2022 to make it look a bit better!
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it OR YOU CAN LEAVE Privo data and factory app, you have a backup anyways. *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma. You may try to skip this step. There have been comments saying that this guide also works without this step.
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while for the signal to appear. If your signal is returned then go to phone app and dial *#06# and look or the IMEI matches the IMEI of the box of your phone (make sure you have the original box if you don't have this then open the back of your phone (if you can), there is a sticker label with your s/n and IMEI. If you cannot open the back of your phone, then you will have to trust that the IMEI is right. If everything is functional then you're done with this guide. The next steps are more ''checking'' if everything is alright.
Step 7) If your s/n is ok skip to step 8 if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and IMEI and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Congratulations on getting past step 8. I hope this guide has helped you and that it worked for you. If not then I'm sorry for not being able to assist you. This guide is just me sharing what I did to solve this issue. Good luck on solving your problem if this guide did not work.
If the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) When you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version. You can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) If it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) If you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Happy flashing and please confirm in the comments below if it worked for your device or not
Guys please comment or it works on your device or not!
It works for me. But I have to manually change CSC on my phone after original rom flash to fix Network. TGP rom have that option.
I followed your guide and my model name changed from G930F to G930FD and my IMEI is just bunch of zeroes wtv
SOLVED AT LAST - MISSING IMEI and EFS DAMAGED SOLUTION
Hi Guys,
First off, please take GOOD note - I am NOT a techy, just an old boring flashaholic who works in an office and likes pyjamas more than partying. This is my account of me fecking up my phone and finally reaching a solution after three days and most of two nights to a missing IMEI, messed up EFS and non-working phone - hoping that it might help anyone as desperate as I was. You do what you do with your phone and that's your business and I'm not responsible if you mess it up, but my hope is that you have have a brain (that's all I have) and you get some helpful piece of info here as I did from a whole ton of posts I read that finally led me to this.
Next - I am not sure what landed me in this mess. I've seen Superman Rom mentioned a couple of times..I didn't use that but I did use Batman Rom which is by the same Dev. It was great to use, too, so I'm not faulting the Dev by any means. What did happen, though, is that when I flashed other ROMS, maybe 3 or 4 of them following, the Batman splash screen was always there before the new ROM's boot sequence, so there were clearly some residual things of it in there ...so perhaps the same coding is in there and could have had something to do with it, I don't know. The breaking point came when I flashed Sac23 Rom hoping to get Pie on my phone. It was cool but I decided to revert to Resurrection Remix - always my favourite overall - and all of a sudden I get errors.
What should have been a routine "Restore" of my backed up RR ROM via TWRP gave "Error mounting EFS". Reboot, wipe, retry. No joy, same again. A couple of tries to restore the EFS from the backup in TWRP didn't work either.
Next go to is flash "original firmware" (more on this wording later). I had that on my PC (not a phone backup, just the firmware so it's clean copy with no data).
Get Odin out, download mode, correct files in correct boxes, all that standard stuff you can find guides on most places - no joy.
Error showing was "Fail at pm.bin" or something like that. Install aborted.
Try again. This time "Fail at cm.bin" Install aborted. Reboot from recovery also fails. Oh sh1t.
Several more attempts made. I have five different Odin vers. I have seven different firmware vers. I have two USB ports and about 8 Samsung cables. Not a single combination I tried worked.
The XDA heroes will know what to do, I thought. I read and read. And read. And CubZ (who is a hero even if he IS from Lancashire ), says MAKE SURE YOUR PHONE IS RUNNING ORIGINAL SOFTWARE. Well...I kinda did that mostly already...but maybe I need to go RIGHT back to the rubbishy 6.0.1 version that came actually ON my phone when I got it....almost 2 years ago? Who remembers that stuff?? I'm about 18 ROMS down the line now. I was desperate. I'm telling you...I even got out my bank statements to trace when my first payment to my current provider was...I read about firmware numbers and country codes, and I chose one from Sammobile with a build date, country code, unbranded code (which my phone always was) and correct phone model (of course!) as I needed. And it WAS .."the ORIGINAL" firmware.
This time I swear Odin failed me a second BEFORE I pressed the start button! No joy.
Have a flask of coffee and a few valium sandwiches and off I go back to XDA again. I read a loooong series of "Missing IMEI" stuff and there's CubZ again with an IMEI/EFS fix guide guide...brilliant! And it WAS brilliant, and clearly he helped tons of people (kudos, man). But I had messed up MY phone in the time-honoured "right royal" way - worse than his guide could help me. My IMEI was Unknown, my EFS was empty, My SIM wasn't being recognised, no network info or signal...nothing. But genius that he is, he CubZ DID post a Combination file that gave me a base to keep trying on when firmware after firmware had failed almost immediately with errors either of pm.bin/abort or cm.bin/abort.
I almost wore the print out on CubZ guide, I read it so much and tried so many times. Then...I see people saying things about U1, U2 and U3 firmwares. Turns out you shouldn't mix the two. I got that snippet from CubZ too. More research and the little coffee-fuelled connections in my brain are like.....ok....
My ORIGINAL firmware has in its name "U1" and there are similar ones with "U2". Might that be it? My phone has been screaming "DEVICE 2 FIRMWARE 1" (or something like that) at every aborted 'original firmware' installation via Odin and download mode that I've tried, including the EXACT firmware that was on my phone the day it was unwrapped and I danced happily round the room with it.
So if DEVICE 2....FIRMWARE should be 2 maybe? Back to Sammobile. There are firmwares with the same model number, country code, branding info as mine..but with a "U2" where mine said "U1". But...they were Oreo and Nougat where mine was "originally" Marshmallow.
It's now day three in the Big Mother House. My valium and coffee and running out and my communication with the outside world has ceased. I've had about five hours sleep, my food is running low and I cannot call for takeaway cos I ficked my phone up good and proper. I even....get this....start looking up PAID services to fix this. I KNOW, right!!??
I pick up a Nougat firmware from Sammobile...careful to match model, country, branding AND U2 - wondering if I can match it up with CubZ's Combi file as a base to appease Odin......and then maybe revert to my 'original' stock from that to start another attempt at the IMEI/EFS thing.
It loaded. Odin was pleased with my sacrifice. And lo and behold, it had restored the whole lot WITHOUT me having to go any further with stock ROM reversions. It frickin' worked. I got my signal back. My SIM card was detected. My phone number was showing. My IMEI was showing. My E-Frickin-S was mended. I feel like Judd Nelson at the end of Breakfast Club.
So here's the semantic bit that I hadn't known and that is unclear in many many posts. My phone is now working 100% on stock firmware....but is is NOT REALLY the ORIGINAL software - it's the MODEL......COUNTRY......BRANDING.....LANGUAGE - specific firmware but it is Nougat where my original was Marshmallow, and it is a U2 firmware where my original FW was U1. THAT was the killer difference, it seems. Thanks to all of you who posted anything - many many of you - who helped me get this. It's a compatibility issue detail I've never seen or had issues with before.
I now have G930FXXS2DRDI_G930FXEU2DRB5_XEU
Where G930F is the model number, XEU is the country code for UK and Ireland (even though UK is a nation and not a country - just sayin' ) and the U2 sits there hiding in the middle of the second section of the name.
Which gives unzipped files as follows: NOTE - THESE ARE NOT LINKS.
AP_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship_meta.tar.md5
BL_G930FXXS2DRDI_CL12365438_QB17789072_REV00_user_low_ship.tar.md5
CP_G930FXXU2DRB6_CL648265_QB8952207_SIGNED.tar.md5
CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
HOME_CSC_XEU_G930FXEU2DRB5_CL13061583_QB16917099_REV00_user_low_ship.tar.md5
It's Nougat, but that's okay for now; I got my IMEI, EFS, SIM, BIN, probably ENT, RAC, SUV and BMX too, everything
And now, with my working phone, I am gonna phone the local Chinese Takeaway for food, answer all my emails that popped and binged and tinkled at me when it became resurrected, and leave CubZ with huge thanks and all of you guys with the hope that this helps somebody out there.
And maybe look at backing this sucker up and reverting to my Oreo RR ROM I love so much..... I HATE Touchwiz!!!!
Good luck!
:good::good::good:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
shabbir143 said:
I was also on similar problem and i lost my efc
Baseband unkwn
Imel null
No signal
I was on s9 port rom by teamexykings and when i update i did dirty flash and my phobe stuck on samsung logo somehow it was boot but it was keeps rebooting than i boot my phone in twrp
When i was trying to wipe system data and dalvic cache
In wipe menu i was shocked to see that it showed internal storage 0mb
I had this problem 1st time
And i have to format my phone to boot properly
U know my big mistake is that i haven't taken a back up of my all apps and my data
After 10-15 min latter it boots
But 2nd shocked was that
I lost my signal my imei my baseband vesrsion unknown
I was so scared to lost my imei
Than i searchon google and i have read lot of articals about restoring efc partition
And than i found similar thread like u have explained
It's really work for me
And this article will help most of device of samsung
And xda user
What i have done
In twrp i mount efc partition
Than in advance menu
File manager
Efc
And i have deleted all of file in efc
(Remember not efc partition it self)
Except privo
Privo data and factory app
Than reboot
After boot my phone i got signal back
I was so happy that it was very easy to do
Your guide will help for many device
Click to expand...
Click to collapse
You deleted all files and folders from EFS Mounted partition? how is it possible working?
You are awesome man!
I just deleted the files in EFS, restarted without installing custom rom and my IMEI was fixed.
I'm definitely donating. How to donate to you?
Thanks for your great work!
cisekpro23 said:
You deleted all files and folders from EFS Mounted partition? how is it possible working?
Click to expand...
Click to collapse
I think samsung phones are capable of regnerating their efs. But its not working for me on samsung galaxy s6. Guess I am screwed.
Hey everyone, I'm sorry for not responding to anyone in this thread. I've been inactive for a long time. I want to thank everyone for trusting the guide and I hope it has worked for you if you tried following the steps. If you have any questions feel free to ask me.
Also I have edited my guide to improve the reading experience because I see my English was absolutely horrible at the time when I wrote the guide.
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
vigilante said:
Edited in 2022 to make it look a bit better!
Hello people, first I want to say that this is my first guide so it doesn't really look professional but I am doing my best to be clear as possible.
In this guide I will be showing you how to repair your IMEI for free/without Z3X box
So lets get into it.
Its better to start fresh in stock rom
So flash the stock rom first
Now we are really starting,
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Step 1) flash TWRP and flash Magisk (if you weren't rooted yet)
Step 2) now search for a custom rom for your phone download it before doing something or just download on pc and move it later
Step 3) now go to mount and select efs or else your efs will be empty at the next step
Step 4) now go to file manager and goto /EFS
Just delete everything in it, you have a backup anyway *WARNING: DO NOT DELETE THE EFS PARTITION IT SELF, IT WILL MAKE YOUR PHONE NOT BOOTING ANYMORE ONLY DELETE THE FILES INSIDE OF IT SO DELETE ALL FILES*
Step 5) now flash the custom rom for s7 edge i would recommend kingrom, do full wipe at the aroma
Step 6) now reboot your phone, first reboot may take 5-10/15 minutes please be patient and make sure you put your phone in the charger if your battery is low now when your phone is in the welcome screen look or your signal is returned if not just setup your phone sometimes it may take a while if your signal is returned then go to dialer and dial *#06# and look or the imei matches the imei of the box (make sure you have the origional box if you dont have this then open the back of your phone, there is a sticker label with your s/n and imei if imei is not good then skip to step 9
Step 7) now if your s/n is ok skip to step... if its not right then download a root explorer and go to /efs/factoryapp and edit the serial no file with a text editor and enter your s/n there now save it and imei and s/n should be alright
Step 8) Now, for IF the IMEI is correct and everything is fully functional, then delete the earlier made backup of EFS and baseband and make a new one with the working partition, then save it somewhere safe on an external drive, the cloud or on an USB, or just a pc that you will never reset or wipe its data.
Step 9) now for if the IMEI is not correct or this guide doesn't work then I can't help you any further except for if you have any questions, however I found a guide for the Samsung galaxy s7/Edge (if you have s8 then click same link because the thread has a link to s8) by Cubz (thanks to Cubz for his guide)
Link: https://www.google.com/amp/s/forum....ow-to-fix-check-drk-imei-issues-t3379516/amp/
S7/E/8 only and some other models as long its an s7 (edge) or s8/+
******* Some tips when you follow the guide*******
1) when you flash combination firmware and it gives you errors then dial *#1234# and look at the cp it should have UX in it (X could be 1,2 or 3 download the correct firmware with the correct bootloader version you can upgrade from u1 to u2 and u2 to u3 but not downgrade from 3 to 2 or 2 to 1
2) if it didn't work then flash back to stock and fully delete everything in efs folder then retry (this is actually just guide B) its better to follow the guide above
3) if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
The first method was tested and worked on SAMSUNG GALAXY S7 EDGE SM-935F it may work on other Samsung devices and maybe other android devices but I cannot guarantee that it works on your device
** I take no responsibility for any damaged device, make sure you take a back up so you can go back to the state before you started following this guide!**
If the device gets bricked then always flash back to stock, if you cant enter download mode then just wait until your battery drains and then when you put it in the charger it may start up automatically so enter download mode fast or if you got bootloader exception error then keep tapping the home button fast until it reboots then just manually reboot and enter download mode
----------------------------------------------------------------------------------------------------------------------------------------------------------------
Please donate and like this thread if you found this helpful, I have experienced this problem my self and it costed me €60! I said NO its too expansive so then I found this solution and now I am sharing it to the world, I could have let this guide cost €61 but my guides and solutions are free a support would be great for finding this out
Happy flashing and please confirm in the comments below if it worked for your device or not
Click to expand...
Click to collapse
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
bamcarpio123 said:
oh no. i accidentally deleted the efs partition and it can't mount anymore what im gonna do now. im fvcked up please somebody help me
Click to expand...
Click to collapse
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
*WARNING* *TAKE A NANDROID BACKUP OF EFS AND BASEBAND BEFORE STARTING*
Click to expand...
Click to collapse
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
vigilante said:
Have you created a back up of your efs partition? I have clearly written it in the guide with all caps. If you haven't made a back up, please do so to avoid getting into this situation in the future.
Anyways, I'm sorry to hear you got your self in this situation. Even though it has been a long time since I did this kind of stuff, I still remember that it's possible to fix this issue. I am sure that I have been in this situation before my self and that I somehow managed to get it back. Try to back up all your data, then flash stock rom with CSC file and not Home CSC
Click to expand...
Click to collapse
I'm sorry for being so stupid because I continued without performing a backup in TWRP, I forgot to back up the EFS, and when I panicked because I was already screwed up, I deleted the efs folder—which is incorrect. I deleted the efs partition before I saw this thread. And now it always says, "failed to mount /efs (invalid argument)" and I've done everything, and it seems like everything is done, I have no idea what to do. I haven't slept for four days and there is still no hope. but my phone is still okay with the stock firmware, but it always restarts. I did almost everything but still nothing
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
If I lose my IMEI, it won't matter. But the thing is my phone is always restarting every minute.
(can someone know how to disable auto-reboot so i can still use my phone even the EFS is damaged?)
ALSO THANKYOU FOR YOUR REPLY! I APPRECIATE IT!
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER? HMM. BUT I WON'T GIVE UP
bamcarpio123 said:
My phone's current csc code is THL (Thailand), but the original is XTC (Philippines), which is my nation, thus I'm curious why THL? of course I flash the right firmware which is the csc is XTC but if I check the CSC the CSC is still THL. I tried to change the csc using tools, but it cannot be change. There may be no hope. I'm worried about losing my phone, yet I'm to blame.
Click to expand...
Click to collapse
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
EDIT: OH I FIX THE EFS PARTITION. NOW MY PROBLEM IS HOW TO GET OUT FROM THIS DARKNESS. HOW CAN I FIX THE IMEI AND BASEBAND WHAT EVER?
Click to expand...
Click to collapse
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
.
.
vigilante said:
Try to download this tool if you haven't already: https://samfirmtool.com/
I like to use this tool when flashing stock rom because I can download specific versions of stock ROMS and also enter the correct region in it. And to top it off the download is really quick (depending on your download speed of course)
Enter your device model number and at region enter the csc you need. It should download the correct files with the right csc. However, I did find this thread saying it is impossible to change your csc to XTC, but it is always worth a try.
If the CSC is XTC then try to follow this guide again to fix your EFS.
If it is not XTC then try to install a custom rom for your phone that has an aroma installer that allows you to pick a CSC, it might also help with the EFS problem but I am not sure.
Since you have mentioned that your EFS partition is fixed, try to follow the guide again but correctly this time. Maybe it will work this time.
Can you tell me how you checked what your CSC is? And which phone do you have? In case this didn't work.
Click to expand...
Click to collapse
My phone is Samsung Galaxy J8. Before i start to flash custom rom, I took a snapshot of the device's hardware information and discovered that the csc is really XTC. I have completed all the necessary steps. I did everything right, but nothing actually changed. I'm so exhausted that I might just give up. I appreciate your assistance.
If I can't retrieve the imei, it's fine, but unfortunately my phone is always restarting
EDIT: MY PHONE IS NOW FIXED. THE SIMS ARE NOW WORKING, THE SIGNAL IS BACK AND I FEEL SO HAPPY. HOW DO I FIX? WELL I USED THIS METHOD, I DELETE ALL THE FILES FROM EFS FOLDER (NOT THE PARTITION JUST THE FILE INSIDE OF IT) THEN I FLASH THE LATEST STOCK ROM WHICH IS ANDROID 10 BUT THE CSC FILE IS FROM ANDROID 9 AND AFTER THAT I USED TFT SAMSUNG MODULE WHICH IS VERY HELPFUL AND LEGIT TOOL AND ITS 100% FREE!. THEN I FIX THE IMEI AND BASEBAND USING THAT TOOL AND YES THAT SOFTWARE IS A BEAST. AND NOW ITS WORKING PROPERLY. IT TOOK ME 2 WEEKS TO SOLVE THE PROBLEM BUT IN REALITY ITS VERY SIMPLE HAHAHA! IT SAVES ME FROM SPENDING MONEY JUST TO SAVE MY PHONE BUT I DO NOT KNOW THAT I AM THE ONE WHO WILL FIX MY PHONE HAHA HOW COOL IS THAT. JUST DON'T GIVE UP NO MATTER WHAT HAPPENS!
#FVCKTHATZ3XBOX
THANKS TO THIS METHOD AND TO SIR VIGILANTE.
EVERYTHING IS POSSIBLE JUST DONT GIVE UP EVEN YOU'RE TIRED.
Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Juwapa said:
Hey all, I did a bad thing. Please help.
Just wanna start off by saying I'm really stupid and things like this make me not want to modify my device anymore. I recently updated to 10.3.0, and after flashing something in the wrong order, I soft bricked my OP6. Since I wanted to basically start over with Android 10, I decided to just do a full wipe, without reading how to. I wiped all partitions through TWRP (Which I very quickly learned is a stupid thing to do) because that it how I went about installing new ROMs on my old phone. That left me with just the bootloader on my phone and nothing more. So I used fastboot to flash recovery and 10.3.0 and everything was fine, or at least I thought.
Everything has been fine for about a week now, until my phone randomly restarted. Upon reboot, my sim card wasn't reading and whenever I tried going to it's settings, it would say "com.android.phone keeps stopping" and after a bunch of searching around... I learned what an EFS Partition is and I'm pretty sure that bad boy is gone. Putting *#06# in the keypad gives me a MEID number, but no IMEI number.
So my question now is, is there anything I can do? I found a few posts that say you could try flashing ColorOS (but there is only an unofficial port for OP6), one comment I found said to use a program called EFS Professional and flash back to stock, and some others suggested MSM tool? Which I haven't used, so I have no clue what that's about. Does anyone have experience or a suggestion for me, please? Any help is greatly appreciated.
My phone is also completely working right now, apart from sim card use. The sim was also 100% working for about a week, before it randomly rebooted, is that normal? I just want to get my phone back to working order, I'm done with modifying. I feel stupid and defeated lmao, oh man, pls help.
Click to expand...
Click to collapse
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video --> https://www.youtube.com/watch?v=jtc7EhNsfPA&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Mr.FREE_Bird said:
Alright calm down, yes what you have done isn't smart to do but nothing is gonna change that, we can't go back in time.
First of I would start with restoring your device by using the the MSM Download Tool which you can find here --> https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892
All you need to know is described in the thread, read it carefully before attempting to restore your device. It will re-lock the bootloader, wipe the internal storage and restore all the partitions on your device. Make sure you made a backup of all your important files which might be stored on your device. If those instructions are still not clear enough you could watch this video which shows how to restore your device, here is a link to that video -->
&feature=youtu.be
After restoring your device you should check if your device shows it's IMEI number again, if not I can't help you further. I've never used the EFS Professional tool with the OP6. So attempting to restore the IMEI with that tool is on your own risk.
I hope you learn from this experience, you should always make backups of the important partitions of your device before even thinking about modifying the system on your device in any way. This won't change your current situation by saying this but it will be helpful in the future.
Good luck!
Click to expand...
Click to collapse
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Juwapa said:
Hi, thank you so much for the quick reply. So apparently it was just a problem with xXx NoLimits, I think? I tried uninstalling it right after making the original post and now my sim is working like normal. I'm confused because I don't think I had any settings with NoLimits that should of affected the sim or even storage of my phone. So why would it work fine for a week and just randomly decide to kill itself like that? As you can see in the screenshots, my IMEI was missing and is now back.
But I'm still worried about when I had wiped all partitions, is there something funky going on with the partitions/storage of my device? Is the "EFS Partition" the only partition that can be permanently lost? If I can still make a backup of it, I should definitely do that, and is there anything else I specifically should make sure I have backed up?
Click to expand...
Click to collapse
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Mr.FREE_Bird said:
No problem!
Strange, sounds like something you configured in your xXx NoLimits config caused some trouble. Maybe you debloated an app that causes this behavior? It would be a guessing game for me.
If I was you I would restore the device using the MSM Download Tool to start clean again. After that I would make a full system backup using TWRP. So in case you do lose the EFS partition or something else you will have something to fall back on.
The EFS partition can indeed be lost but you would really need to badly mess with the system on your device. I've only once experienced a lost IMEI number after a system update on my LG G4 but I could restore it using the EFS Professional tool. The actual EFS partition was still there I think but got corrupted somehow. Luckily I had made a backup of that partition with TWRP but I still needed to write the IMEI number to it manually. You should just always make backups before attempting to modify the system on your device. Lesson learned right?
Click to expand...
Click to collapse
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Juwapa said:
Thank you so much for this info. May I ask what the best way to actually backup the EFS Partition would be? After a quick google search, a few different apps popped up. But based on your reply, I'm assuming you've done this before, so is there a certain method you would suggest for a noob like myself?
And as far as using the MSM Tool for a complete reset/backup, do you think that would really be necessary? From what I've read, newer versions of TWRP don't even let you delete/backup the EFS Partition, which means it would be unlikely that I even actually touched that partition, right? And my experience was most likely caused by some xXx NoLimits setting then, I'd assume. I think what messed me up when I first upgraded to 10.3.0, was that I accidentally wiped the Vender partition (which I believe is what the recovery is now on?) Which is why I had to flash via fastboot. But still, I would like to backup the EFS Partition just to be assured I won't have this come up in the future. But outside of the EFS Partition, isn't it pretty easy to fix any Partition/Bricks that might occur on the OnePlus 6?
And again, thank you so much for taking the time to respond to a silly goose like me. I've made it this far without damaging ant of my phones but I think it's about time I stop playing with fire and actually read/backup important stuff haha.
Click to expand...
Click to collapse
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Mr.FREE_Bird said:
I have always used TWRP for making a backup of the EFS Partition, the option to do so is still available in the backup section in TWRP. It is indeed very unlikely you ever touched that partition but as you experienced it isn't hard to mess up the installation of your system so you should definitely back it up just to be sure you could restore it if something goes wrong. If I'm not mistaken the recovery is actually written to the boot partition and not the vendor partition or that has changed since Android 10. But I don't see any reason to ever wipe the vendor partition. You should always carefully read instructions before installing any kind of software so you are sure you are doing it right. And yes, fixing soft bricks on the OP6 isn't hard to do when you know what you are doing. Doing research is very important, by doing so you know what you are doing, how you should do it and you will have a higher chance to fix errors in case things don't turn out to work as they should. Luckily things didn't go very wrong for you but I hope you'll spend some time doing research before you are going to modify the system on your device. It will prevent a lot of trouble. But by making mistakes you will learn to right. Oh and I almost forgot to mention that you should copy your backups to an other device or storage in case your internal storage gets wiped.
It's not a problem to give a helping hand, that's what this place is for. I'm always glad to help those who kindly ask for help. :good:
Click to expand...
Click to collapse
So I finally had time to sit down and make backups of my device. I made a backup of just the EFS and Modem Partition only and I made another complete backup of everything. This should be all I need right?
And yes, I will keep the backups on my PC and on the flash drive I keep my current rom, recovery, kernel, and magisk on.
Shyciii said:
Nolimit and random reboot in android 10.0.3? Turn off kernel tweaks in Nolimit profiles, and then flash Nolimit. It will be fine.
Click to expand...
Click to collapse
I could be wrong, but I don't think I had KernelTweaks on to begin with. I keep reading people are having problems with it, so I think I'll just stop using it. And it wasn't reboots that were the problem, I only had the one reboot. The problem was my phone wasn't recognizing my sim card nor did it give me my IMEI number, which is why I thought I might of messed up the EFS Partition. But thank you for the reply.
I'm about out of options anyone tried using smt download mode on msm tool.? Then restoring efs partitions.? And had any success. I'm getting a sha 256 does not match error on msm tool when trying to download super partition. Op8 verizon bricked.