Related
Hello everyone,
I am trying to fix my IMEI on SGS3 but without success. I cannot select RMNET+DM+MODEM in hidden menu (*#7284#). On UART there is only (MODEM, PDA) and USB (MODEM, PDA).
I've even tried SGS3-Exploiter-GeeK.exe but when I select this mode nothing happend, it just goes back to MTB+ADB.
TNX
http://forum.xda-developers.com/showthread.php?p=31051731
exploit20 said:
Hello everyone,
I am trying to fix my IMEI on SGS3 but without success. I cannot select RMNET+DM+MODEM in hidden menu (*#7284#). On UART there is only (MODEM, PDA) and USB (MODEM, PDA).
I've even tried SGS3-Exploiter-GeeK.exe but when I select this mode nothing happend, it just goes back to MTB+ADB.
TNX
Click to expand...
Click to collapse
try using HC-kTools app from play store...
Dehaani thank you but I know already for that thread... I cannot enter that diag mode... :/
and don't have backup to restore using hc-ktool
dehaani said:
http://forum.xda-developers.com/showthread.php?p=31051731
Click to expand...
Click to collapse
exploit20 said:
Hello everyone,
I am trying to fix my IMEI on SGS3 but without success. I cannot select RMNET+DM+MODEM in hidden menu (*#7284#). On UART there is only (MODEM, PDA) and USB (MODEM, PDA).
I've even tried SGS3-Exploiter-GeeK.exe but when I select this mode nothing happend, it just goes back to MTB+ADB.
TNX
Click to expand...
Click to collapse
Are you using International or US Galaxy S3 ?
Methods using Diag mode and software like SGS3-Exploiter-GeeK or QPST (Qualcomm Product Support Tools) are made to work ONLY with the United States variant of Galaxy S3 (based on Qualcomm SoC).
Now, I don't know software to fix International SGS3 without EFS folder backup (Sorry :crying: ) when nv_data.bin and .nv_data.bak are broken.
lelinuxien52 said:
Are you using International or US Galaxy S3 ?
Methods using Diag mode and software like SGS3-Exploiter-GeeK or QPST (Qualcomm Product Support Tools) are made to work ONLY with the United States variant of Galaxy S3 (based on Qualcomm SoC).
Now, I don't know software to fix International SGS3 without EFS folder backup (Sorry :crying: ) when nv_data.bin and .nv_data.bak are broken.
Click to expand...
Click to collapse
I had this problem on my S£ (international) a while back. It happened after flashing cm10, I had a generic IMEI code. I f'd around with it a bit using root explorer and the EFS folder and the .bak files but this did not work.
I tried ktools etc. nothing seemed to work..
oddly enough, i got it back by flashing back to the stock ics rom via Odin, since then my IMEI has been fine after flashing JB roms.
worth a try!
@lozfromcorby : I just saying they have not software to do that now on I9300. But I'm agree with you ! Sometimes, we can recover wrong IMEI when flahsing stock ROM.
Yep it's international ((
Ok I will try to flash stock rom again :/ I will post result here....
TNX
lelinuxien52 said:
Are you using International or US Galaxy S3 ?
Methods using Diag mode and software like SGS3-Exploiter-GeeK or QPST (Qualcomm Product Support Tools) are made to work ONLY with the United States variant of Galaxy S3 (based on Qualcomm SoC).
Now, I don't know software to fix International SGS3 without EFS folder backup (Sorry :crying: ) when nv_data.bin and .nv_data.bak are broken.
Click to expand...
Click to collapse
IMEI is still corrupted after going back to stock ROM
I've tried with my friend Z3X box to repair IMEI but without success ...
exploit20 said:
IMEI is still corrupted after going back to stock ROM
I've tried with my friend Z3X box to repair IMEI but without success ...
Click to expand...
Click to collapse
Why do you care anyway when your device is working? You corrupted it so deal with it.
Sent from my GT-I9300 using xda app-developers app
exploit20 said:
IMEI is still corrupted after going back to stock ROM
I've tried with my friend Z3X box to repair IMEI but without success ...
Click to expand...
Click to collapse
I have seen that the Z3X box can fix all Samsung Galaxy devices excepted SGS3 !
I think you need send your phone to repair center.
But before, you can try this :
Save remaining files contain on your EFS folder. For that, use EFS Tool Pro for example :
http://forum.xda-developers.com/showthread.php?t=1308546
Try this tutorial (with a full official stock firmware/kernel | Flash it with ODIN before trying repair) :
http://forum.xda-developers.com/showthread.php?t=1264021
Caution : DO IT ON YOUR OWN RISK.
If it doesn't work, you must :
- reset binary counter (with Chainfire tool : Triangleaway)
- perform total wipe data / wipe cache (from recovery mode)
- flash the latest stock firmware corresponding to your region
- verify the phone status : must be "Normal" and not "Modify".
Device is working... but no network thats why ((
Jack Barrett said:
Why do you care anyway when your device is working? You corrupted it so deal with it.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Thank you, it seems thats the only thing I can do right now :/
lelinuxien52 said:
I have seen that the Z3X box can fix all Samsung Galaxy devices excepted SGS3 !
I think you need send your phone to repair center.
But before, you can try this :
Save remaining files contain on your EFS folder. For that, use EFS Tool Pro for example :
http://forum.xda-developers.com/showthread.php?t=1308546
Try this tutorial (with a full official stock firmware/kernel | Flash it with ODIN before trying repair) :
http://forum.xda-developers.com/showthread.php?t=1264021
Caution : DO IT ON YOUR OWN RISK.
If it doesn't work, you must :
- reset binary counter (with Chainfire tool : Triangleaway)
- perform total wipe data / wipe cache (from recovery mode)
- flash the latest stock firmware corresponding to your region
- verify the phone status : must be "Normal" and not "Modify".
Click to expand...
Click to collapse
I had the same problem tried different ways but no luck so I have sent off to Samsung been 2 weeks now, luckily for me a service centre isn't that far from me so I didn't have to pay postage
Sent from my HTC Desire S using xda premium
I might be able to help you. Pm me your efs backup + partition backup made with efs pro. If the information is still present I should be able to recover it.
@can't see who in tapatalk
Could you tell me which ics stock room version helped you recovering your imei?
Sent from my GT-I9300 using xda app-developers app
I have a temporary solution for you. if you still have the backup of the the EFS folder in your internal or external sd card than follow the following steps,
1. copy ALL the files from the EFS BACKUP FOLDER.
2. go to the root of your your phone with root explorer of ES file explorer and find the folder EFS. it should be with all the system folders like acct, config,data,dev,efs,etc so on and on.
3. now paste all the copied files in to EFS folder. tap on REPLACE THE FILES if ASKED...
4. close the app. and go to the home screen and wait for few seconds.
if your simcard have pin than it will ask the pin after few seconds and if it doesnt have any pin than it will just get the network.
good things is you have your IMEI number restored and can use the phone like regularly. NO PROBLEMS AT ALL. WITH NETWORK.
bad thing is NEVER LET YOUR PHONE SWITCH OFF. If it will switch off than you will have to follow all the steps again... annoying but works... let me know the progress buddy... best of luck...
Your other option is to to flash the stock rom but not let it finish. You will get a loop screen. Then just send it off for repair saying it doesn't turn on.. It will be diagnosed as a broken bootloader and fixed and the imei number will be back to the original. This happened with my old s1
Sent from my GT-I9300 using Tapatalk 2
No, I don't have a backup of the EFS folder I will try to send EFS folder to Spocky12 and hope that he can recover information...
Chaitanyapatel8880 said:
I have a temporary solution for you. if you still have the backup of the the EFS folder in your internal or external sd card than follow the following steps,
1. copy ALL the files from the EFS BACKUP FOLDER.
2. go to the root of your your phone with root explorer of ES file explorer and find the folder EFS. it should be with all the system folders like acct, config,data,dev,efs,etc so on and on.
3. now paste all the copied files in to EFS folder. tap on REPLACE THE FILES if ASKED...
4. close the app. and go to the home screen and wait for few seconds.
if your simcard have pin than it will ask the pin after few seconds and if it doesnt have any pin than it will just get the network.
good things is you have your IMEI number restored and can use the phone like regularly. NO PROBLEMS AT ALL. WITH NETWORK.
bad thing is NEVER LET YOUR PHONE SWITCH OFF. If it will switch off than you will have to follow all the steps again... annoying but works... let me know the progress buddy... best of luck...
Click to expand...
Click to collapse
Sorry buddy... I hope you will recover it...
exactly the reason i stopped messing around with my s3 :| i had screwed up my s2 like this and all the efs backups were corrupt too -_- hope you get your s3 fixed man.
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 .
Hi,
Phone restarts automatically with no imei and unknown baseband, I download stock firmware 4.4.2 and install on it but same situation,
any suggestion or help pls,
thanks
br
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Elite49 said:
Isn't IMEI used for phone identification along with MEID? If thats blank, would it be an issue on Verizons side?
Click to expand...
Click to collapse
imei is unknow
2 Choices
nsnobel2 said:
imei is unknow
Click to expand...
Click to collapse
Hi
I don't know if you've fixed your issue with your g900v or not, but i have the same problem and the same phone and obviously the same symptoms ...
As far as I've tried, nothing worked not ODIN flashing ROMs, or QPST to write IMEI or EFS professtiona ADB .... etc.
What I've come to know is this :
1- keep the phone in a safe place till next months reveal a solution through developers here or elsewhere.
2- Flash the Original Samsung Verizon Rom ( Full Package with efs and bootloader mounts and all partitions " Clean Flash" ) which costs about 100$ .
3- Change the board for a (200$) new one .
So, I would try to pay the 100$ and flash the original ROM, and comeback to tell if it solved the Problem.
I wish if you share any different approach or feedback . I would love to hear it .
Bye
It could possibly be that your EFS folder is damaged. This is where your IMEI and Baseband info is stored. If that's the case for your device, these steps should work. I've done this on two phones (one being an S5) and it fixed this problem.
I'm assuming that you're rooted. If not then you'll need to root your device first. And you need to have debugging enabled. What this does is backups the files from the EFS folder, repairs the partition tables, then restores the files to the repaired folder.
1. Connect the phone to your computer. (Windows)
2. Download this: https://www.dropbox.com/s/v2h5dzisjd0rgj5/EFS_Professional_2.1.73_Release.zip?dl=0
3. Extract and run the program
4. Click EFS Professional... It will open a window showing that it found your phone
5. Click on the Backup Tab and make sure all of the partitions are checked, and your Device Filter is recognized
6. Hit the Backup button to backup the EFS folder
7. After that's done, click the Restore button and it will restore your files to the EFS folder.
I hope this helps you.
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
joshw0000 said:
There used to be a tool for the Note 2 I believe, maybe S4, that would let you re-write your EFS if it accidentally got erased. Not a backup/restore deal, but a tool to key in your IMEI and it would write it to the phone. Maybe research that tool for a fix?
Click to expand...
Click to collapse
Was it a tool specifically for the Note 2, or multiple Samsung devices, or maybe a universal program like CDMA Workshop? I love that program. It's what I use when it comes to actually entirely rewriting files like this. Most of the time a full rewrite isn't needed though if the EFS folder has just been damaged. Which "damaged" is totally the wrong word here, but that's what it's called for some reason. I really don't even know how it happens, but I do know when it does, it usually just jumbles and/or fragments the info in the folder and needs to be put back in it's correct order. Kind of like defragging in Windows. Just a tool like you're talking about would definitely be cool for me to have though. I shall start my quest to find it. Lol
Please some help
Any luck yet ???
Got the same issue here, and none of the threads here worked .
Same problem
Hello,
I have the exact same problem. I bought the phone here in Mexico, and the phone came with erased EFS folder. Phone restarts automatically when screen turns off. When I'm using the phone, it works just fine, but some seconds after screen goes off, phone restarts automatically. EFS folder is messed up, I've tried out a lot EFS restoring tools with no luck.
I tried QPST but it does not detect the phone, only appears "?" and "No phone" blinking. The same happens with DFS Tool.
I will try to look for that tool joshw0000 talks about.
I hope we can find out a solution for this excellent phone.
Bye.
Hey ...
I did a factory reset and cache wipe, and now the phone stopped restarting when the screen goes off, but still got the "Unknown" issues.
But at least I got rid of the annoying restarts.
570 ppl read this and still no answer, I got to admit ... it's tough.
Sent from my SM-G900V using XDA Free mobile app
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
Hey, I started flashing custom ROMs to my S4 (GT-i9506) about three months ago and everything was okay, but just recently I tried to return to my stock i9506 4.4.2 ROM and i succeeded in doing so, but afterwards I noticed that my S4 wasn't recognising my SIM.
At first I assumed it was a faulty SIM card (my SIM had multiple scratches on it), so I bought a new SIM card and yet the problem persisted. I tried to make calls and etc but my phone retuned an error stating, "Mobile network not available". I decided to check my settings and I noticed that my Baseband Version was labelled as "unkown".
After seeing this I searched for solutions online and came upon S4 service codes, I used the "*#06#" code and it returned a message saying "IMEI... null/null". Yet again I searched for a solution and came upon none to help me
I soon found out that my problem had something to do with the EFS parition in my phone. I re-rooted and installed ES File Explorer and opened up my EFS folder. In her everything looked ordinary, but then I noticed that my .nv_data file was missing, which, if i remember correctly, is responsible for important functions such as the IMEI and Baseband
I tried every solution I could find online and nothing fixed my issue - I'm only writing this as it's the only option which doesn't require me to go to my local Samsung Experience Store.
TL;DR
My GT-i9506 doesn't know its own IMEI and Baseband version and I'm all out of solutions at this point.
Am I better off going to the Samsung Store?
BUMP
More BUMP
Please help me
BUMP
IMEI no longer inhabits the EFS folder, so you're not missing anything. Flash the modem for your ROM again through Odin and see if that corrects the issue. If it does, use Wanam's EFS Backup to properly backup the hidden partitions where the IMEI is now stored.
Flash the latest stock lollipop rom for your device and you will be fine. Sounds to me you were on Lollipop stock and you downgraded to Kitkat.
Strephon Alkhalikoi said:
IMEI no longer inhabits the EFS folder, so you're not missing anything. Flash the modem for your ROM again through Odin and see if that corrects the issue. If it does, use Wanam's EFS Backup to properly backup the hidden partitions where the IMEI is now stored.
Click to expand...
Click to collapse
So then where is the IMEI stored? I'd just like to know for future purposes
The modem didn't fix it
Lennyz1988 said:
Flash the latest stock lollipop rom for your device and you will be fine. Sounds to me you were on Lollipop stock and you downgraded to Kitkat.
Click to expand...
Click to collapse
Tried this too, but failed also
I don't know which of the hidden partitions the IMEI is stored in. I only know where it's not, and that's not in the EFS folder. However, based on the partition names, the IMEI is likely stored in any or all of the following partitions: m9kefs1, m9kefs2, m9kefs3. While unlikely, it could also be stored in the following partitions: modemst1, modemst2.
Strephon Alkhalikoi said:
I don't know which of the hidden partitions the IMEI is stored in. I only know where it's not, and that's not in the EFS folder. However, based on the partition names, the IMEI is likely stored in any or all of the following partitions: m9kefs1, m9kefs2, m9kefs3. While unlikely, it could also be stored in the following partitions: modemst1, modemst2.
Click to expand...
Click to collapse
Would it be possible to mount any of those partitions?
jakeshekukanneh said:
Tried this too, but failed also
Click to expand...
Click to collapse
I need more info then this.
jakeshekukanneh said:
Would it be possible to mount any of those partitions?
Click to expand...
Click to collapse
You can try it, but I doubt you'll find anything human readable within them.
Lennyz1988 said:
I need more info then this.
Click to expand...
Click to collapse
I flashed the stock I9506XXDOA6 NEE ROM in Odin once more but my IMEI remained null.
So I decided to extract the modem.bin after installing the Lollipop ROM and it too didn't work
jakeshekukanneh said:
I flashed the stock I9506XXDOA6 NEE ROM in Odin once more but my IMEI remained null.
So I decided to extract the modem.bin after installing the Lollipop ROM and it too didn't work
Click to expand...
Click to collapse
Maybe I didn't elaborate enough....
Try This Maybe This Help!!
use samsung kies fimeware upgrade and instalition then it waant youre imei or s/n and its rightet under battry
Note: Do That in download Mode
I've already tried that multiple times though. Thanks for the suggestion however
Sent from my GT-I9506 using XDA Free mobile app
Strephon Alkhalikoi said:
I don't know which of the hidden partitions the IMEI is stored in. I only know where it's not, and that's not in the EFS folder. However, based on the partition names, the IMEI is likely stored in any or all of the following partitions: m9kefs1, m9kefs2, m9kefs3. While unlikely, it could also be stored in the following partitions: modemst1, modemst2.
Click to expand...
Click to collapse
Hi, I used to use Optimus G, it has IMEI in m9efs* and Modem in modem, modemst*. I never had IMEI problems but on S4 it is really scary. Will backing up EFS in TWRP, manually dd'ing EFS, modemst*, m9kefs* block10 make me stay on safe side?
Sent from my GT-I9505
Just use Wanam's EFS Backup tool. It backs up all those partitions, so no need to run commands in a terminal.
jakeshekukanneh said:
I've already tried that multiple times though. Thanks for the suggestion however
Sent from my GT-I9506 using XDA Free mobile app
Click to expand...
Click to collapse
There was a guy that claimed that his method fixed it for him:
https://www.youtube.com/watch?v=LgPEIeXDPNA
Lennyz1988 said:
There was a guy that claimed that his method fixed it for him:
https://www.youtube.com/watch?v=LgPEIeXDPNA
Click to expand...
Click to collapse
Hey, I've already tried that method prior to posting, unfortunately it didn't work. I might just go see the Samsung Experience Store tomorrow