IMEI Unknown ... flash Stock ROM without USB or ODIN? - Samsung Galaxy S7 Edge Questions and Answers

I've been running LightROM (for some time) Pie, latest v20 with BL_G935FXXS8ETCO, CP_G935FXXS8ETCM and TWRP 3.3.1, and decided to change over to latest Lineage 16.0 Build 27.
Full wipe for LOS flash, but after boot-up and config found that it had no mobile signal and checking Settings | Software saw that IMEI is Unknown and Baseband version is empty/null.
Prior to LOS flash, I took a TWRP backup of Boot, Recovery, Baseband, and EFS. This was all I thought I needed for IMEI issues, and just restoring EFS would fix it. Unfortunately, not. Tried restoring all Boot, Recovery, Baseband, and EFS but still no IMEI.
I've been using wireless charging for a long time, and have found that my USB is not working (cleaned out socket, multiple cables, different PCs) but just cannot get it USB charging let alone data connection.
So, in order to get my IMEI back I believe I need to flash a stock ROM or COMBINATION. Both of which need ODIN and a working USB connection.
Thus, my query ... is there a STOCK ROM or COMBINATION that I can flash within TWRP to get my IMEI back?

mouth said:
I've been running LightROM (for some time) Pie, latest v20 with BL_G935FXXS8ETCO, CP_G935FXXS8ETCM and TWRP 3.3.1, and decided to change over to latest Lineage 16.0 Build 27.
Full wipe for LOS flash, but after boot-up and config found that it had no mobile signal and checking Settings | Software saw that IMEI is Unknown and Baseband version is empty/null.
Prior to LOS flash, I took a TWRP backup of Boot, Recovery, Baseband, and EFS. This was all I thought I needed for IMEI issues, and just restoring EFS would fix it. Unfortunately, not. Tried restoring all Boot, Recovery, Baseband, and EFS but still no IMEI.
I've been using wireless charging for a long time, and have found that my USB is not working (cleaned out socket, multiple cables, different PCs) but just cannot get it USB charging let alone data connection.
So, in order to get my IMEI back I believe I need to flash a stock ROM or COMBINATION. Both of which need ODIN and a working USB connection.
Thus, my query ... is there a STOCK ROM or COMBINATION that I can flash within TWRP to get my IMEI back?
Click to expand...
Click to collapse
Did you by chance did a backup of the full phone from twrp? If yes try to flash back in everything including the rom.
I always make a full backup on twrp after flashing a new custom rom and finish setting everything up. Just in case I did something wrong down the road I can just wipe everything and restore everything from the full backup. And I won't need to go through the hassle of setting the phone up.
Sent from my SM-G985F using Tapatalk

mouth said:
I've been running LightROM (for some time) Pie, latest v20 with BL_G935FXXS8ETCO, CP_G935FXXS8ETCM and TWRP 3.3.1, and decided to change over to latest Lineage 16.0 Build 27.
Full wipe for LOS flash, but after boot-up and config found that it had no mobile signal and checking Settings | Software saw that IMEI is Unknown and Baseband version is empty/null.
Prior to LOS flash, I took a TWRP backup of Boot, Recovery, Baseband, and EFS. This was all I thought I needed for IMEI issues, and just restoring EFS would fix it. Unfortunately, not. Tried restoring all Boot, Recovery, Baseband, and EFS but still no IMEI.
I've been using wireless charging for a long time, and have found that my USB is not working (cleaned out socket, multiple cables, different PCs) but just cannot get it USB charging let alone data connection.
So, in order to get my IMEI back I believe I need to flash a stock ROM or COMBINATION. Both of which need ODIN and a working USB connection.
Thus, my query ... is there a STOCK ROM or COMBINATION that I can flash within TWRP to get my IMEI back?
Click to expand...
Click to collapse
Nope, you need odin and combination rom and ofcourse pc - per my best knowledge..
But if you have pc, but can't get odin/combination due to whatever reason.. follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911/post79889098
Sent from my S7 Edge using XDA Labs

vash_h said:
Did you by chance did a backup of the full phone from twrp? If yes try to flash back in everything including the rom.
Click to expand...
Click to collapse
No, just Boot, Recovery, Baseband, and EFS. That's what I thought is all I'd need for any low-level recovery, since I was wiping and flashing anyway (a process I've done many times over the years). I thought the IMEI came from EFS anyway.
Thanks for thought.

shah22 said:
Nope, you need odin and combination rom and ofcourse pc - per my best knowledge..
But if you have pc, but can't get odin/combination due to whatever reason.. follow this thread :
https://forum.xda-developers.com/s7-edge/how-to/fix-imei-downgrading-g935f-fd-t3947911/post79889098
Click to expand...
Click to collapse
Thanks, unfortunately it appears that thread needs working USB though, which I don't have.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965 looks interesting. Could that work for an S7e?

mouth said:
Thanks, unfortunately it appears that thread needs working USB though, which I don't have.
https://forum.xda-developers.com/note-4/general/fix-drk-dm-verity-factory-csc-serial-t3422965 looks interesting. Could that work for an S7e?
Click to expand...
Click to collapse
Yes follow this thread for imei repair using twrp. Should work
But be careful about the file paths..
S7 edge on oreo fimware path maybe different..
Also your phone must be in working condition..
https://forum.xda-developers.com/no...rity-factory-csc-serial-t3422965/post67840769
Sent from my S7 Edge using XDA Labs

shah22 said:
Yes follow this thread for imei repair using twrp. Should work
Click to expand...
Click to collapse
Hasn't worked
Also found /efs/.nv_backup.bin[.md5] but using these didn't't help either.
Any other steps available?

mouth said:
Hasn't worked
Also found /efs/.nv_backup.bin[.md5] but using these didn't't help either.
Any other steps available?
Click to expand...
Click to collapse
Follow steps to letter, should fix your issue.. make sure you have su access in adb and you use the right file paths, don't know why a solution won't apply to your situation, it should as i think ..
Sent from my S7 Edge using XDA Labs

Related

[Info] EFS/Lost IMEI - Must to read for every Newbies.

What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM (older to first ME6) on newer ROM (ME6 or any other rom released after ME6) it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Here is different common methods for EFS Backup/Restore [There are hundreds of tools available on play store and don't use blindly, as unsupported tool can cause EFS partition failed to mount and to recover it need to use adb shell and more. Better use one of the below mentioned time tested tools]
You must have device rooted. Read post #2 of this thread, how to root Note2
you can use any of method said below.
1.With Aroma installer - No need to have PC, need CWM/TWRP installed. Here is Other Tool I recommend to must have for Newbies, Which also have many other options.
2.From Device itself - No need of PC, just requires installing application from play store.
3.Philz recovery - Also you can find this option on other CWM/TWRP, but i have tested only this.
4.EFS Backup/Restore Tool - you needs to use PC to work this.
How to recover lost IMEI that happens with downgrading ROM
If you have lost IMEI just by downgrading (as said by above by flashing older ROM), still you can recover IMEI without having EFS backup.
-Again upgrade ROM will restore IMEI OR
-Flash latest Modem. You can find it here.. You can download MG1 modem and flash using PC Odin with 'Phone' tab instead of PDA.
Remember above said works only if IMEI is corrupted by downgrading ROM only, if it was corrupted by other things, this won't be helpful.
Also Read This, if you have issue restoring EFS OR device stuck to factory mod.
Hope this will find helpful to all newbies regarding question about EFS and IMEI problem. I have posted this to general section so newbie can post to it if they have any queries.
Informative
Very informative and helpful thread Brother :good::good::good::good:
:good: great guide ketan :good:
you are one of the best things to happen to Note 1 and Note 2 as well..!!
god bless ya bro..! :good::good:
Very informative in precise words!
Thanks, +1:good:
There is already a post about this.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Zionator said:
There is already a post about this.
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can you link to it? I have not found in general section where newbies can post. Though you can report it to moderator if double post.
Sent from my GT-N7100 using xda premium
The EFS image backup has proved to be immensely helpful all the way with the Terminal emulator!:good:
Please confirm: can the EFS backup image be flashed with Philz Recovery as an alternative to the Terminal emulator?
Provided you put it to correct place.
Sent from my GT-N7100 using xda premium
Thank you for info and helpful Pro ^_^
Sent from my GT-N7100 using XDA Premium 4 mobile app
You can easily make efs backup and restore with this app Andromizer(free version) with one click
https://play.google.com/store/apps/details?id=com.j.y.daddy.customizer
These models of note 2 supported
GT-N7100,GT-N7102,GT-N7105,SHV-E250S,SHV-E250K,SHV-E250L
SPH-L900,SGH-T889,SGH-T889V,SGH-L317,SGH-I317M,SCH-I605,SCH-R950
dr.ketan said:
Can you link to it? I have not found in general section where newbies can post. Though you can report it to moderator if double post.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Finally you have listened my request.
Dr.Ketan, he may be talking about this thread.
This guide is very helpfull. :thumbup:
May helps and warn all mates before flashing different roms.
Please make this thread sticky.
sent from my GT-N7100. Press thanks if I helped..
It's already been added to sticky roll up (list of thread worth to stick)
Sent from my GT-N7100 using xda premium
dr.ketan said:
What is EFS
This part of the device contains some important and some basic info related to our device identity like Bluetooth MAC address, wireless devices MAC addresses, product code (also in the nv_data.bin) and the very main IMEI address (nv_data.bin), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things. So you can guess it's will be different for each device and one can't use others.
How it can corrupt :
- Any bad flashing, mishandling system modification can cause this.
- Also It can be corrupted by downgrading stock ROM. If you flash any old ROM (older to first ME6) on newer ROM (ME6 or any other rom released after ME6) it can corrupt EFS. Basically newer ROM believed to have new kernel that changes EFS data which older Modems can't read and results to fail in reading IMEI.
Impact on device/How I know I have corrupted EFS
When there is EFS partition is corrupted, device loses IMEI and due to this device can't gets connected to network. Baseband info also sometimes shows unknown.
-Check your IMEI in setting / by dialling *#06# if it is null OR if it starts with 0049** then IMEI is generic and corrupted. In Normal case IMEI which you can see in device setting or dialing *#06# is exactly same you can see on bill/box/sticker under battery compartment
-If you are unable to connect to network in spite of correct IMEI, chance are
A. Your device is Locked to specific Network OR
B. Your device is banned due to tempered IMEI
-If your AP,CP,CSC all are correct and even you are getting error (unknown CSC XXX) on kies update, it may be due to corrupt Product code in EFS. Read This for detail.
What care should i take
Before flashing anything, first thing you should do is to make EFS backup. Every person who have rooted device should make EFS backup earliest and place it to safer place on PC and /Cloud.
If you are on older ROM, make EFS backup on older ROM as well make another after upgrading ROM too.
If you have already updated to newer ROM, make backup on current ROM.
Here is different common methods for EFS Backup/Restore
You must have device rooted. Read post #2 of this thread, how to root Note2
you can use any of method said below.
1.From Device itself - No need of PC, just requires installing application from play store.
2.Philz recovery - Also you can find this option on other CWM/TWRP, but i have tested only this.
3.EFS Backup/Restore Tool - you needs to use PC to work this.
How to recover lost IMEI that happens with downgrading ROM
If you have lost IMEI just by downgrading (as said by above by flashing older ROM), still you can recover IMEI without having EFS backup.
-Again upgrade ROM will restore IMEI OR
-Flash latest Modem. You can find it here.. You can download MG1 modem and flash using PC Odin with 'Phone' tab instead of PDA.
Remember above said works only if IMEI is corrupted by downgrading ROM only, if it was corrupted by other things, this won't be helpful.
Also Read This, if you have issue restoring EFS OR device stuck to factory mod.
Hope this will find helpful to all newbies regarding question about EFS and IMEI problem. I have posted this to general section so newbie can post to it if they have any queries.
Click to expand...
Click to collapse
Dr. Ketan,
Kem chho bhai!!
I am facing problem with EFS , i read your post and come to know that my IMEI is corrupt. It is starting with 0049*** and not matching with phone sticker. Following procedure mentioned in your post but no success!! STill am not able to connect network how should i proceed now??
Already flashed kernel, recovery, modem from pc odin also tried to switch to stock rom. i.e. UAE i guess now downloading Saudi Arabia and will gong to try all.
Please help!!!
You need to mention how does it happen in Details.
How does happend it, i mean what did you flashed? And what rom you had when you flash it.
Do you have efs backup?
Sent from my GT-N7100 using xda premium
Hi Dr. Ketan,
No I don;t have EFS backup and till today flashed many times but not faced any problem like this.
I recently flashed PRobam rom which works on 4.3 android and later return back to my region flashing CWM recovery. Later i tried toolkit for note 2 and tried mod for camera HD.But later come to know that toolkit has no support for my rom.
I think i lost my IMEI while flashing Probam but using wrong baseband trough toolkit can also be problem.No so sure.
Tried to go back on regional rom by different methods but no success.
Thanks!!
Basically it happens if you flash older kernel (it may happened by wrong selection in toolkit)
Reflash latest modem and try.
Just want to get this straight into my head here before I go diving into flashing a ROM sorry for being silly I just like to get it clear lol
Ok my phone is on DME6 so that means I can't flash any samsung based custom ROM that is using a version lower than that yes? but AOSP ROM's don't matter as they don't use the modem so won't corrupt the EFS correct? I am aware that for the SIII there was a flashable zip you can use to make the modem the newer one for flashing older firmware custom ROMS is there one for this? I want to flash this ROM or the HD revolution ROM (HD rev showing an older version in the title) mainly want a custom stock ROM that gets rid of that pesky SMS conversion thing
Thanks for your time
You have already flashed ME6 so you will have latest modem so yes flashiung older ROM you will lose IMEI. regarding AOSP ROM i am not sure, i have never used any AOSP ROM and not following so not familiar with that.
1.Make EFS backup Use one of the tool mentioned in OP)
2.Flash desired ROM, if you select older ROM and lose IMEI, you can find latest modem from my All in one thread (look signature) post #7. simply extract and use modem.tar.md5 to flash with 'Phone' tab (Not PDA) of Odin.
yeah I made a backup of the EFS (on the ME6 version not the older as this is how i got the phone) so I can use any stock based ROM as long as i flash that modem? think i'll probably stay with a ROM labeled as ME6 anyway to keep it easier on myself

[GUIDE] How to restore EFS on I9300

It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
FAQ
If you need the ODIN, you can find theme over here. Myself I've always used version 3.07. And as always under options you only need the 'Auto Reboot' and 'F. Reset Time' checked. Whether it a modem or stock ROM, click on 'PDA' choose the correct file and than click on start.
Q: Won't flash the EFS image I provide means I'm getting your IMEI?
A: I've wondered this as well. If it were so simple, there wouldn't be so many thread on recovering and so may people cry for help... (I'm included). As my last resort before I buy Chimera Tool's license, I flashed over my bro's S3 EFS, which I didn't want to, as I said it was a last resort. And as it turned out, I didn't get his IMEI. Instead I got his phones' Update S3 product code and serial number. And that was it. IMEI has changed from my previous 'NULL' to the infamous generic 004999010640000.
Q: Why do I still need to do EFS recovery if Chimera Tool can restore it.
A: I've experiment this myself, as I also absolutely did not want my bro's EFS. But unfortunately Chimera can only restore the IMEI and serial number, not rest of the missing files in the EFS folder. If I repartition the EFS folder and using Chimera to restore my IMEI, it would show the correct IMEI but still refuse to connect to the network. And it will have the annoy overly showing my CSC and other bunch of info on my homescreen, as if my EFS is still corrupt.
Q: Does Chimera need some special box?
A: No, a normal USB cable will work. That pretty much means standard ADB command would work, but unfortunately I can't find any info on that. I wish I did, so I don't need to get the Chimera Tool but there was no other way for me. I was also sceptical at first, as I read over many forums and they say it impossible with some sort of service box/tool. I gambled, and luckily it worked out.
Q: Where does the EFS image go for kTool?
A: Sorry, don't remember. Google it, or use the backup option first than overwrite the EFS.IMG file. That what I did.
Q: Now that I got my IMEI back, how do I back it up?
A. Use kTool again? Personally I use TWRP, as I think it the easiest. Since you can do it at a recovery level. No trying of ODIN the OS for corrupt OS before restoring the EFS. In any case, Chimera would still be function for the next couple of month and you can still mess around until than.
Q: Why the need of ODIN the original firmware?
A: I was on a custom TW ROM and Chimera didn't work. Maybe CM and other custom ROM will will work, you can give it a try. But this is how I did it and I know it works.
EFS / Baseband(modem)
It easy to criticize a member and simply tell him use the 'search function', but without realize sometimes the article will help you the most, simply just doesn't come up. Murphy's law. I was on stock 4.1.2 and after restore IMEI and EFS, the phone indicate it register on the network, but I couldn't make calls or connect to the net. This is a vary good article regarding EFS, and sadly it didn't come up easily on my search result. I came across it after I fixed the issue with tones of Googling and was searching for a different topic. But I understand people that desperate need to solve the problem quick (like I was) simply spent hour reading over hundreds of post under that article is just testing a persons sanity. So I'm going to summarised some of the stuff along with my experience. First thing you need to know:
- EFS v2 Basebands (modem) was introduced at Android 4.3 and can read EFS partition v2 and EFS v1
- EFS v1 Basebands (modem) CANNOT read EFS v2, ONLY EFS v1
If you phone is still under warranty and cannot connect to network, the best way is to stay on stock firmware and use TriangleAway to reset the flash counter and sent back to Samsung. With your IMEI number correctly showing, Samsung has absolutely no excuse on not fixing it. If you are no longer warranty, read on.
Q: My IMEI is now showing correctly but I still cannot make calls!
A: This is where the Ariza Patch kicks in. If you are on stock fimware 4.1.2, you need the Ariza Patch to fix the baseband. But after long reading over plenty post, it seems once this patch has been done, it irreversible. So beware. Before you try this patch, you may want to try update to the stock 4.3 firmware and see if it solves the problem before applying the patch.
Q: I'm on stock 4.3, now what?
A: If you still have problem connecting to the network, you need a patched modem (baseband) file. You can find them here. I think this is from the original author who did it. Instead of searching over the forums and files scatter all over the place, I'm pretty sure I dug the link out of XDA while reading through. Someone please tell me if it isn't and provide the the proper link. I'll fix it.
Q: I was on stock 4.1.2 and went to a custom 4.3 ROM, what fix shall I apply?
A: This was my scenario. And I was kind of desperate as well since I just fix my IMEI and was expect the phone to work. I wish I could come across the article on top earlier. I would've tried stock 4.3 first instead of applying the Ariza patch. Any ways, I was on stock 4.1.2 and it didn't work, so I tried a modified 4.3 TW ROM. I wish the OP would mention the EFS thing, which he didn't. I'm not blaming him or anything, but seriously not everyone keep in track of what happening with Android. The OP should mention about the EFS thing or simply post a link such as the topic above and just let people know instead of wasting hours on figuring out why it wasn't working. What I did was, after using the mod 4.3 TW ROM, the IMEI went crazy. So I thought it was corrupt again, so I ODIN back the stock 4.1.2 TW. Than I applied the Ariza patch, wolla, I could call and browse again. So I decide to give the mod 4.3 TW ROM another try. To my surprise, the IMEI still went crazy. So after more Googling only I found out because I wasn't on stock 4.3, my baseband would still 4.1.x. I tried the modem (baseband) patch which for some reason still did not work for me. So I decide to keep the stock 4.1.2 baseband and simply use a custom kernel that could read EFS v1 and v2 - Boeffla Kernel. Remember to download the 4.3 kernel not the 4.1.x! That it, you should now have a working phone.
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
nainaabd said:
I just use SA manager .It will backup EFS & MODEM .store it in Ext SD .If EFS corrrrupted just install SA mgr back & restore .
Most important is backup and its very simple process
Click to expand...
Click to collapse
Didn't try SA manager as I was in a rush and looking specifically for Samsung phones only. But it definately somehting I want to try if I get a Sony phone. Though I still prefer at a recover level. It just so simple.
keenimo said:
u need HKCtool to backup efs both img and tar files first of all.
if this is not possible u need a stock rom and odin .after installing stock rom the efs will be repaired.
Click to expand...
Click to collapse
TAR file is just a compressed version of IMG file.
im in nairobi kenya, unfortunately i can not buy the chimera tool because we dont have the necessary paying methods. anyone who can lend me theirs please? my S3 has the generic imei, repair would cost 15k here, which is too much. anybody that can help will be highly appreciated.
TNCS said:
It started when I was trying Swapper 2 from the Play Store. Will, I guess I should read the comment, but I didn't. And yes, it corrupted my EFS and my phone was stuck at the Samsung boot logo. I have tried many method I can search over XDA, but non works. (I'm not sure about this one, which I only find while writing this guide.)
This is by far the easiest method for me, and it doesn't involve Linux, which was a pain since I haven't use Linux in years. I had to VM one for some of the XDA method, which didn't work at end of the day.
1. Flash the firmware with ODIN (original firmware) with original version that you had before. Not the custom ROM, but the original firmware version.
2. Recover with EFS with the EFS image attached in the thread. I used kTool as it faster and easier than any other tool. (Yes, I tried them all...)
3. Download Chimera Tool and buy their cheapest license (or whatever you want) which is €12.90.
That it. Yes you pay, but it the easiest, and most time saving. I spent a week Googling, trying all this various method over ADB, and no, non works. And for Samsung to repair, which they refuse and simply want to change a board and charge me US$ 200 for it, I rather pay €12.90 and do it myself. If you still have problem connection to the network after restoring IMEI, please read post 3.
Click to expand...
Click to collapse
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Xubair91 said:
you can also downgrade to 4.0.4 and do flash i9300 efs.tar via odin 3.07 but first backup your EFS with helroz's app from here https://market.android.com/details?id=com.boiteoutilssgshelroz&feature=search_result or use any other efs backup maker
But YOU NEVER NEED TO RESTORE EFS after a flash or whenever, just in case you have an issue with it.
if u have 0049xxxx or 00xxxx imei just flash I9300XXUNA7 or any latest android 4.3 and that's it you have your unknown baseband and null imei fixed aka efs corrupt issue.
Warning!!!!
i am not responsible if you get any damage to your device as per my experience i have fixed many i9300's efs and didn't get any problem .
Good luck!
(CHANGE THE ATTACHED FILE'S EXTENSION TO .md5)
Click to expand...
Click to collapse
From what I understand, that still under the condition of prior having an EFS back-up first, right? My guide is for people who doesn't. Like in my situation, where the app screwed up the EFS partition and I had no back-ups.
If you really want in details - Swapper 2 moved the EFS partation on to my ext SD card and format the EFS partition. I was in a flat panic with the soft-brick froze at the Samsung boot logo, assume the SWAP was on the ext SD and screwed it up than format the ext SD. Well, boom, without expectation the app would do something like that and had no prior experience with EFS - no back-ups of EFS at all. And no, full nandroid back-up from CWM does not contain EFS, I've tried that. This isn't some normal scenario of incompatibility between kernel/ROM and EFS/Modem. This is recovery guild for corruption of EFS with NO back-ups.
trying ....
mezo_mmm said:
trying ....
Click to expand...
Click to collapse
And how did it go? The suspense it killing me .

(help) baseband unknown n-9005

i've got a baseband problem in my galaxy note 3 snapdragon variant. i try to backup mg efs partition on note 3 using efs pro and it is running on qualcomm mode. after i click backup efs, it reboots and i've got baseband problem. please give some solution. thanks a lot xda.
Your going to have to completely reprogram the radios, I can help you do this...but you need to use Kies 3 and backup EVERYTHING FIRST!
Then message me your exact model and serial number off the sticker under battery! I will get what you need and post instructions
PAPalinskie said:
i've got a baseband problem in my galaxy note 3 snapdragon variant. i try to backup mg efs partition on note 3 using efs pro and it is running on qualcomm mode. after i click backup efs, it reboots and i've got baseband problem. please give some solution. thanks a lot xda.
Click to expand...
Click to collapse
Do you have custom Recovery? If so, enter Recovery and do a backup. Then simplest is to flash a ROM and if that doesn't work, get the latest firmware from Sammobile website and use Odin to flash that, then Restore your data.
Info you should provide for this kind of thing is what firmware or ROM you are running, do you have root access, do you have custom Recovery and if so which one... Also can you get into the phone itself or are you bootlooping? If you can get into the phone does your IMEI still show the same as what is under the battery?
And TBH, no offence KaosMaster, but I am unsure why you'd need the serial number for a fix.
Journyman16 said:
And TBH, no offence KaosMaster, but I am unsure why you'd need the serial number for a fix.
Click to expand...
Click to collapse
I use the serial number to download the OFFICIAL Samsung service files thru KIES to use with ODIN. I use the files to help others. And, IMHO, repairing radios with a messed up device, using ROMS, is kind of a waste....when you can fix everything...and start clean and better off!
KaosMaster said:
I use the serial number to download the OFFICIAL Samsung service files thru KIES to use with ODIN. I use the files to help others. And, IMHO, repairing radios with a messed up device, using ROMS, is kind of a waste....when you can fix everything...and start clean and better off!
Click to expand...
Click to collapse
How is that different to DL'ing the firmware and flashing it? i.e. the 2nd suggestion
I suggest ROM's first because very often, others have had a problem and have constructed the fix into a full system - simple flash can fix things without returning the phone to stock. It's only software after all, and it may be easier to simply flash the non-hlos and modem files than to do whatever it is you're suggesting.
And I am still unsure why you'd need a serial number to get the firmware.
Journyman16 said:
How is that different to DL'ing the firmware and flashing it? i.e. the 2nd suggestion
And I am still unsure why you'd need a serial number to get the firmware.
Click to expand...
Click to collapse
The firmware on SamMobile are images. They are not the same as service files that Samsung uses. These files have everything to re-flash and fix all parts. Including partitions usually. You have to input the model and serial in Samsung software to download the correct service files for that device, and the ones like it.
My method allows ODIN, with the checkboxes marked to completely reprogram the EFS and all parts that are messed up by ROMS.
AND...This method takes 10 minutes to fix everything
KaosMaster said:
The firmware on SamMobile are images. They are not the same as service files that Samsung uses. These files have everything to re-flash and fix all parts. Including partitions usually. You have to input the model and serial in Samsung software to download the correct service files for that device, and the ones like it.
My method allows ODIN, with the checkboxes marked to completely reprogram the EFS and all parts that are messed up by ROMS.
AND...This method takes 10 minutes to fix everything
Click to expand...
Click to collapse
Ah... cool. Not something I'd heard about before. Is the Samsung SW you mention something service agents use or is it available for the rest of us?
Samsung Kies Software
This is my current project...take a peek and what I have done!
http://forum.xda-developers.com/showthread.php?t=3122222

OEM_NV_BACKUP Invalid, sim1 has imei sim 2 doesnt and No signal

Ok I have been an xda member for almost 8 years and this is my first thread , I have always found through search the answer to my problems with phones, but I cant for the life of me come up with anything on this. After ota upgrade to oxygenos 2.1.2 I lost lte (att/cricket) at first I thought it was imei related on att side, nope, then I tried reflashing modem manually through fastboot and somewhere in the procees went back and I had to reflash using hard bick method, after that I lost both imei and no signal , after a bunch of tinkering ive managed to get sim1 imei back but no signal!???? any ideas?
Same issue i got. Have sent a note to Support @ OnePlus. I have a Team Viewer session on coming sunday. Will let you know how it goes
hopefully it is software "fixable" and you we dont have to send it in to a repair center
Try to reflash full rom with firmware via fastboot.
acmerw said:
Try to reflash full rom with firmware via fastboot.
Click to expand...
Click to collapse
All options tried. Only one SIM restores successfully. Hopefully OnePlus support team fixes it. Will keep you posted.
ive Hard brick restored, manually fastboot flashed each partition, efs backup restored through twrp
fesar said:
All options tried. Only one SIM restores successfully. Hopefully OnePlus support team fixes it. Will keep you posted.
Click to expand...
Click to collapse
any news?
bump
androidbrick.com

Mi A1 Wifi Issue after flashing stock ROM

Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Wifi works, but sim = 0
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Thank you soo very much. you are the best, I followed your instructions step by step and my phone wifi is working as charm. my phone is alive now. Thanks a ton again.
-Bimlesh
colegui said:
Wifi works, but sim = 0
Click to expand...
Click to collapse
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
I'm trying some methods but I have not luck yet.
colegui said:
I'm trying some methods but I have not luck yet.
Click to expand...
Click to collapse
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
dmbardal said:
I managed to fix the WiFi and SIM (no imei).
Just flash persist.img if you only have the WiFi-issue.
There's a somewhat complicated guide here in the forums as well. Just google "mi a1 imei fix xda".
I'll help you tomorrow if you cant fix it.
Click to expand...
Click to collapse
I'm fixing imei downgrade to 7.8.23 and repair imei with rbsoft tool, but when I upgrade to oreo with OTA, imeo=0 again....
I'm trying again other method....https://forum.xda-developers.com/mi-a1/help/efs-partition-eraised-boot-t3753619
dmbardal said:
Have you figured out a way to fix this?
My SIM does not work either, but WiFi is AOK after flashing persist.img
Click to expand...
Click to collapse
Here is solution: : How to restore IMEI permanently after using factory flash
I have the same problem with IMEI, the fix is permanent.
After the repair can be uploaded any rom, including Oreo .
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
coda00 said:
I also twisted up my IMEI. When I tried to downgrade to 7.8.23 it was boot looping. I was trying to solve it for 6 straight hours. Eventually, somehow the phone became unable to boot into fastboot (or anything else) for no reason. (a random shutdown occured during fastboot mode while no command was given). I had to turn to the Xiaomi service, since nothing could be done with the phone. Guess I'll have to use my old nokia flip mobile for 2-3 weeks.
Click to expand...
Click to collapse
Sorry I cant posting outside links,
You can try EDL mode:
solution how boot EDL mode via ADB or fastboot: link>> 99mediasector.com/edl-mode-boot-edl-mode-xiaomi-devices​I think this will not work for you​But you can try EDL:​via Deep Flash Cable (how quickly make Deep Flash Cable): link>> en.miui.com/thread-310325-1-1.html​or​via disassembly Mi A1 (Guide to Flash Bricked Mi A1): link>> en.miui.com/thread-1680467-1-1.html​
Excellent
Ecoda00
Click to expand...
Click to collapse
amazing bro Thanks, i work fine for me...
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
Now that my wifi issue is solved, can I delete the persist.img from my device? Please advice.
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
pooniaprashant said:
Mods please edit the op with a warning not to flash someone else's persist partition, this can permanently damage your chances of recovering your OEM Mac address and other sensors data, there's already a better solution out the called "persist resurrector" on XDA. !!!!DO NOT USE THIS!!!
Click to expand...
Click to collapse
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
amithiel said:
Great, so now im tired of resurrection rom, want to go back stock, and since i didn't backup previously my persist img, i'm done with wifi?
seriously, why did i flashed the damn rom. What options do i have now? (thanks for the warning)
---------- Post added at 21:14 ---------- Previous post was at 20:15 ----------
Oh man, thank you so so much!! I used Persist Resurrector. and i'm back on wifi. really, thanks so much!!!!
Click to expand...
Click to collapse
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Bimlesh1681 said:
Can you please let me know the steps you did with Persist Resurrector or the link which has the steps? Thanks!
Click to expand...
Click to collapse
Sure, here you go: https://forum.xda-developers.com/mi-a1/how-to/tool-persist-resurrector-v1-0-0-0-t3781095
Edit: But you need to have you original persist file
Thank you so much, Bro. You saved my day. I am getting the similar problem. And ended up flashing multiple ROMs. but nothing worked out until I found your post.
i used this tool to solve wifi issue.
while using this tool make sure you enable USB debugging or it won't work.
coda00 said:
Greetings!
I have been using Resurrection Remix for about a month now, but when the stock April patch came, I decided to return to stock firmware. I downloaded the most recent flash package from the official Xiaomi site and flashed it via MiFlash. When the phone booted up, I could see every wireless network, but when I chose to connect to any of them, the signal dropped a bit and it said "Connecting..." then immediately "Saved". After a few automatic try, it would just say "Disabled". The router settings are just fine, the phone could connect to it before I flashed stock rom. I also tried to download a bit older patch (9.5.4), which was neither good. After it I tried Nougat, but it still won't connect to the network. The hardware must be fine, since it was working an hour ago with Resurrection Remix. Could anyone help me out? Thank you in advance!
EDIT: Solved. The problem was with the persist partition, which is not flashed during the firmware flash process, so you have to flash it separately in TWRP. You'll have to download THIS FILE (persist.img), move it to /sdcard of your device, then boot to TWRP (you don't have to flash TWRP, only boot in it), tap on "Advanced" -> "Terminal", then type in the following: "dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27". After it, reboot the phone into fastboot mode, and flash the firmware again. That's all.
Click to expand...
Click to collapse
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
infuerano said:
I am on TWRP and using custom ROM( DOT OS). DO I have to go to fastboot and flash the firmware?
Click to expand...
Click to collapse
try flashing the latest void kernel.

Categories

Resources