Related
Long story short, I lost my IMEI. After reading a lot and trying a lot of thing, I was able to restore the product code but still, my IMEI is a generic one.
I can still access network and make calls, but it bugs me so I have yet one last thing to try; revert to stock eclair rom.
Only thing, I can't find any of those...
Actually, I "found" I9000UGJH2 but when I push it with Odin, I get a boot loop (with the samsung logo)
So, doest anyone can provide me with a stock Eclair rom?
IE:
-I9000UGJH2
-I9000DTJG4
-I9000UGJG8
Thanks!
Get a GB stock ROM and flash it via Odin...
FYI: If I ask for a specific version I have already tried those easely available, from JL2 to KG3 to JL2 then upgrade via kies to KG3.
as stated on the original request, I want to test eclair as it was the original rom on it.
Then try FroYo. It's better than Eclair.
Bro, you have to learn to read...
JL2=froyo
KG3=GB
ALL ALREADY TRIED...
I specificaly asked for those rom FOR A REASON!
Hey.
Take a look at samfirmware, a quick search told me they have it there. You need to register (think it's still free, i haven't gone there in a while)
http://www.sammobile.com/
I've seen there:
Android 2.1 I9000HVJH1
Android 2.1 I9008ZMJG1
Android 2.1 I9000DXJG4
Android 2.1 I9000DDJF2
so pick your poison and good luck.
Also, since your chances of actually recovering imei that way are 50% at this point (it'll either work or not ), i'll also leave a document that tells you how to rebuild the /efs folder. Sorry, portuguese was the only language i found this (picked from another forum). I guess you can always use google translate if you need or shoot me a pm if you have any trouble understanding the language at some point, i'll be glad to help.
https://docs.google.com/document/d/...NQ__7Xmy7vS7KTxY/edit?authkey=CL3S_f8M&pli=1#
Again, good luck with that. I'm guessing if you ever recover your imei, an /efs backup will be the first thing you'll do
None of them actually works when you click on "download" on samfirmware.com
Thanks for the guide, I'll check this out!
t1mman said:
None of them actually works when you click on "download" on samfirmware.com
Thanks for the guide, I'll check this out!
Click to expand...
Click to collapse
Listen carefully;
The reason why you got a boot loop while flashing eclair,that could happen if you're flashing ONE FILE ROM (which is same as rooting,onnly PDA)..
I %100 recommend that;
Flash a rom that HAS 3 FILES ,and with that , also PIT file which makes it 4 files BASE flashing...
Roms that are containing 4 files..
XXJVU (2.3.6 GB)
XXJVQ(2.3.4 GB)
JVQ could looks like older but belive me flash JVQ then you can GET JW4 latest offical european Value Pack firmware FROM KIES!.
All you have to do ;
https://docs.google.com/file/d/0B_UDv0VHoyaRak95b0NSX3Q1Tlk/edit?pli=1 download this (this is my recovery rom )
in zip file,there are 4 files and they are;
s1_odin_20100512.pit (which goes to PIT in odin)
CODE.tar (which goes to PDA in odin)
MODEM.tar (which goes to PHONE in odin)
CSC.tar (which goes to CSC in odin)
MAKE SURE RE PARTITION is CHECKED.Then flash it .)
After that when you get your imei back,
type *#272*imeinumber# in dialer then change CSC to XEU (united kingdom).. Then connect to kies and voila!!!!!! You 'll get JW4
Again, thanks for the heads up but I NEED an eclair rom for a SPECIFIC reason, a specific test, I have already tested GB and Froyo and it doesn't work.
I don't need it for JW4 or any other already available rom out there, I can already flash them with Odin or flash with CWM.
So, if anyone has the 3 files for I9000UGJH2 and can provide it, please let me know! I can provide an FTP for you to drop it.
BTW, I've tested the portugeese walktrough to no result.
Hmm.Okey then but ,if gb/froyo flashing didn't get your imei back..I dont think eclair wont get that too
Is it must be UGJH2? Or any other eclair roms.. ?
Sorry for your imei bro btw...i hope you can get it back... Did you ever take a backup of your efs folder on any custom roms before this thing happened?
GT-I9000 cihazımdan Tapatalk 2 ile gönderildi
try to flash any eclair rom you find,preferably stock
I would think that, since the IMEI and Product number are "related" (in the /efs folder), it would need to, at least, have the product code (sell code, with *#272*IMEI#), that's why I'm looking for thoses specific roms.
And no, I didn't made a backup prior to this... :S
snchep drgs
t1mman said:
Long story short, I lost my IMEI. After reading a lot and trying a lot of thing, I was able to restore the product code but still, my IMEI is a generic one.
Click to expand...
Click to collapse
Would you mind to tell me how? because i lost my generic imei too. Thanks...
zakrilex said:
Would you mind to tell me how? because i lost my generic imei too. Thanks...
Click to expand...
Click to collapse
Wow, that was long ago!
I think you can change your product code this way:
To change the CSC (otherwise known as product code) dial *#06# to get your imei and write it down carefully.
Then dial *#272*your imei# (replace "your imei" with the 15 digit code you just wrote down) and you will get to the CSC selection screen.
Choose the one you want then hit "install".
Be aware that changing the CSC will effectively do a 'wipe data' on your phone.
Click to expand...
Click to collapse
But for the IMEI, you'll have to get it reprogrammed by a provider or something similar.
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
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 .
So, my Note 3 N9005 worked fine, then i tried to install CM 12 The phone kept locking so i tried to install CM 12.1 instead. It did the same thing. Then i tried to install CM11. Phone got stuck to a bootloop. Then i tried to install the stock firmware. It launched but the phone lags like hell, apps don't open at all. Waking up the phone takes a lot of time. And the phone doesn't recognize the sim-card anymore. I used CWM to install all the custom roms, and i wiped cache, dalvik cache and did a factory reset every time before i installed a new rom. I used Odin v. 3.04 to flash the stock firmware.
So my question is this, how do i get my phone back up and running smoothly again, like it was fresh out the box? I'll appreciate all the help i can get because i am starting to get very desperate, i really wouldn't like to tell my mom i need a new phone. Note 3 cost like hell after all.
I am from Finland so i used the N9005XXUEND5 version of the stock firmware, KitKat 4.4.2.
The only thing i can think of that can cause this problem is that if the OS's i installed didn't get deleted fully, so there would be multiple OS's on my phone running at the same time. This may be a bit far fetched.
Please help as fast as possible. And i'm not that good at these things so i would appreciate if you could walk me through this step by step and explaining each step as specifically as you can.
Judging from your post, you didn't even bother to read the install instructions of the roms you were flashing.
And this is the result you get.
In CWM recovery mounts and storage format sdcard system cache data preload .
Reboot to download mode and flash stock rom .
The last time i flashed the stock ROM I formatted everything, including the firmwares and such. Now i flashed AOKP ROM and the phone is working fine, except it doesn't recognize the sim card. Any idea how to fix that. Thanks for all the help so far
Basics check you have correct IMEI and correct modem change sim card .
I'm sorry, i have no idea what IMEI and correct modem change sim card. :/
If you don't understand the very basics of flashing and firmware then i suggest you take your phone to a repair shop .Its not a game you are going to end up with a dead phone with no chance of a fix .
I think i understand the very basics of flashing, considering i have done it before twice and on both times it has worked. My sim card worked on my moms Lumia, so is it possible that the sim card reader broke. Can flashing a rom or formatting system do that? Are there a kernel i should flash? I heard it might fix problems like these. And when i go to settings there are no options for IMEI or modem change, that's why i'm confused.
**********************************************
I do have my backup still, but when i try to restore it with CWM, it says something about md5 sums, any idea how to deal with that, because i think that would help if i could use that backup. The stock rom that i downloaded wasn't from any known page. Mostly because SamMobile doesn't have my version anymore for some reason. And i tried to download it from samsung-updates.com but it said that the download would take about 9 hours. I think that the download time would only keep growing and growing so eventually it would be a waste of time.
I think i understand the very basics of flashing,
No you don't and that's your problem this post only makes it more obvious and makes it nearly impossible to give guidance .
MD5 and cwm basics turn off MD5 check in recovery .
You cannot go flashing kernels for no reason .
Modem change is not settings neither is IMEI .
Broken sim reader yes its possible but highly unlikely from a firmware bad flash .
Its entirely possible that you have downloaded a bad firmware .
You also have a non Samsung rom flashed now (aokp)
suggest you read up on that for problems .Though i cannot see any 9005 AOKP roms here .
But first you need to check you have the correct IMEI if your IMEI does not match then you restore the EFS folder you backed up before you started flashing .
I said that i would appreciate that if you would guide me through this step by step. How can i check IMEI? I'm sorry i'm making this so hard for you. The only thing i care about now is that i get my phone back stock and running smooth.
*****************************************************
That is also true that i might have downloaded a bad firmware. Are there any other place to get a stock firmware other than samsung-updates.com?
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
WhateverMan said:
Download from sammobile.com. It is advised to flash the newest 5.0 firmware on your N9005 (N9005XXUGBOB6) with Odin 3.09 or later.
Check your IMEI from Settings/About device/Status/IMEI. If it starts with 0049, your phone has lost its IMEI. Try flashing to the newest 5.0 firmware to fix it.
Click to expand...
Click to collapse
I checked and it sais my IMEI is unknown. But i will try to flash that software you suggested
Restore the EFS folder you backed up .
JJEgan said:
Restore the EFS folder you backed up .
Click to expand...
Click to collapse
I think i already said something about it not working because of incorrect md5 sums.
You said backup that's not your EFS backup .
Solution given for MD5 .
JJEgan said:
You said backup that's not your EFS backup .
Solution given for MD5 .
Click to expand...
Click to collapse
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
The EFS folder contains your phones unique identification code or IMEI . Without correct IMEI your phone cannot connect . That is why the EFS folder is backed up before anything is ever flashed . No backup and wrong IMEI then you probably need a service centre repair . EFS/ IMEI can be damaged during flashing that is why rule one is backup your EFS folder first .
Nansus said:
I'm sorry that i have to make this hard for you again, but can you tell what EFS backup means and what i'm supposed to do with it?
Click to expand...
Click to collapse
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
You can restore your backed up EFS folder .
CWM backup restore does not include EFS .
You can flash lollipop .
You can flash a matching modem .
All these may restore IMEI or make the situation worse that is why a service repair is recommended .
phonexpert_alex said:
Dude you are like 12 years old. Why do you even have such a phone? Your attitude toward the dude that was helping you was very rude.
If you don't know what EFS is, it is highly likely that you don't have a back-up. In that case you can try to flash the stock firmware suggested previously. But I really doubt that it will actually magically "cure" your IMEI. I would really go to a service center before you do anymore damage. It could be a little expensive, but at least they do know what they are doing.
That being said, I'm not sure even a service center could help you.
Click to expand...
Click to collapse
I'm sorry if i sounded rude towards to anybody, that is totally not what i'm trying to be. I know you guys are trying to help so i really don't see why i would be rude towards to anyone. I guess my english is still so bad that i'm sounding rude.
I think the best option now is to take the phone to a service repair. Especially if flashing anything can make the situation worse.
I thank everyone that has tried to help. It seems like that i have to accept the fact that i ****ed up my phone. At least this will serve as an example to anyone who's trying to flash custom roms and don't know what they are doing.
Oh, and the reason i have this phone because i'm a student i high school. I just started doing flashing and trying custom roms and i guess i thought it would be really simple. Clearly it wasn't.
Hi Guys.
This is a Mediatek Helio X25 Redmi Pro and it came to me bricked from its owner who tried to root it the wrong way. I managed to flash an official rom and bring it back to life but as apparently is the case with these phones, the nvram has been corrupted/rewritten and there's no Imei numbers on the phone, which means no calls and stuff. WiFi works fine. I've already had permission to unlock the bootloader but obviously I can't do anything about it since the software won't ID the device. I believe I might be able to flash a backup of nvram.bin, but I don't have one from this phone, which is why I am posting this here, hoping that maybe one of you can help me by sending me a copy of his own Redmi Pro nvram.bin file. Of course I only need it to get the thing back in the system, after which I can unlock it and use the original Imei numbers. Or if someone has another suggestion, I would greatly appreciate it.
Thanks in advance.
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Binnylaw said:
Search for SN writer. Then follow the steps from en.miui.com/thread-198017-1-1.html
Of course you have to have the original imei stickers for the numbers. Entering random numbers is illegal AFAIK.
This will fix your IMEI.
Click to expand...
Click to collapse
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
nsterjo said:
Thanks for the reply, friend. I have tried that, as well as almost every other solution provided on the internet apart from the deepflash cable, but I keep getting error messages. And yes, I do have the original Imei numbers and it's those that I'm trying to restore. It just seems that something has gone really wrong in the boot partition and it won't let me do anything there. I'm out of ideas. The phone works fine, except for sim service; I am able to flash roms, but not fully. There's always 3 files that won't be downloaded to the phone using SP Flash Tool. I cannot use MiFlash because the phone won't boot on EDL mode. Any other suggestions you might have, I appreciate them.
Cheers
Click to expand...
Click to collapse
Tried this method?
http://en.miui.com/thread-411112-1-1.html
Sent from my Redmi Note 4 using Tapatalk
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Binnylaw said:
If your phone is booting, I am pretty sure your snwriter version is wrong. Please use this exact version and let us know.
snwritetool.com/download/sn-write-tool-v1-1648
Click to expand...
Click to collapse
I have tried maybe 3 different versions of Sp Flashtool, including this one. I usually get a timeout message. But I will try again. Is there any specifics I should observe regarding the mdb files I need to use? I have tried all the ones that come with the roms I've tried, but without luck.
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
No, you understood fine; it was me who typed SP Flashtool instead of SN Writer, which was what I meant. Everything else is as I wrote. I have tried 3 different versions of SN Writer, I connect fine and it starts the procedure following the same instructions you mentioned, but it stops half way, giving me an error message. I have tried different combinations of MDB and APDB files from several different ROMs I've downloaded, but they all fail. I'm not very familiar with these things but I can follow instructions and am quick to learn. Still, I have no idea why SN Writer or Maui Meta are not working. I tried to download an nvram.bin file I got from the internet with SP Flashtool, but it would not accept it as it was for Helio X20 I believe, which is why I was hoping someone would make available a copy of nvram.bin for this particular phone. I will also try to make a deepflash cable, hoping that might get me into EDL after which I can use MiFlash to reflash a new official Rom, but I don't know if it will work.
help please
Binnylaw said:
MaYbe I misunderstood.. You said ur phone is booting fine... and u are on an official ROM. If that is so, you should not use SP FLash to fix IMEI.
SN writer is needed to fix IMEI.. MDDB_InfoCustomAppSrcP_MT6797_S00_MOLY_LR11_W1603_MD_MP_V13_18_P69_1_ulwctg_n.EDB is the MDb file for developer ROM 7.3.6 and APDB_MT6797_S01_alps-mp-m0.mp9_W17.09 is the APDB...
Click on Dual IMEI and enter the two IMEIs.. Switch off the phone before connecting to the USb cable... Make sure you use the original Mi black cable. Now connect the phone without pressing ANY button at all.
That should do the job!
Click to expand...
Click to collapse
Hi there, please can you tell me where I find the files (mdb and adb)? Are they somewhere on the phone's firmware? Or somewhere in the rom i flashed?
I'm a beginner having a very similar issue having flashed a rom in rescuing a bricked phone and now have invalid IMEI numbers.
Thanks so much