Hi XDA and a Happy New Year to everyone.
I recently bought a SGSII from someone, at a very low price, because of some software problems.
I could use it for spare parts, but I`d like to fix it if it is possible.
As far as I know, the phone was used to "test" different roms and tweaks by a kid who thought was a developer, and accidently messed up its efs folder without backing it up, so the phone now has a generic IMEI (0049..)
I found a final solution for this, in case nothing works, from user Odia, who can restore your efs folder without having a backup, and I`ll keep this option as a last resort.
But wait, there`s more.
The phone is acting really weird. Each time I start it, it reverts back to its default settings. From power options, to widget location, everything goes back to their original state.
Further more, while taking photos with it works perfect, when recording a video, it doesn`t save its self on to the flash memory.
I`ve tried flashing a different ROM (at the moment it has a default 2.3.3 Samsung ROM) from 2.3.3 to 2.3.5, using Odin. Everything goes well while flashing, with no errors in Odin. But after the phone reboots it has the same firmware/rom as before. Nothing changes. I`ve confirmed this by dialing *#1234#.
The IMEI problem isn`t that important (at the moment), but I`d like to be able to at least use the phone and to install a different ROM.
I don`t know what could be the problem, it`s like everything on it is on Read Only, or like a computer with Deep Freeze installed - everything looks ok while writing, but after a reboot, nothing was saved.
If you need anymore details regarding the device, please let me know and I`ll try to post them asap.
Hoping someone can help me with it.
No IMEI means your phone will not connect to a network as its part of the handshake process .
Suggestion would be .
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery or install CWM and ROOT kernel if needed
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware from stock firmware post
jje
Stuck again.
First of all, thank you JJEgan for your reply.
I`ve tried what you`ve told to, but failed.
Tried installing CWM (GT-I9100_ClockworkMod-Recovery_4.0.0.2 and GT-I9100_ClockworkMod-Recovery_5.0.2.3) from the official thread, using Odin (both 1.83 and 1.85) but after the phone reboots, it isn`t there.
If I try accessing it via VolUp + Home + Power, it goes directly into the Android Recovery System, the default one, and not CWM.
I`ve even installed it via Odin and immediately removed the battery in order to prevent the phone from rewriting itself after Odin said everything is OK, and got the same results.
Dialing *#1234# gives me the following:
PDA: I9100XEKDB
PHONE: I9100XXKDH
CSC: I9100XEKD9
Build Info: Tue Apr 26 09:10:03 KST 2011
Click to expand...
Click to collapse
I`ve tried locating the correct version of CF-Root for it but I can`t find one for KDB in the official thread.
As I said in the first post, when I try to write something on it using Odin, everything goes well, no error, it doesn`t freeze, but after it sends the reboot command, it`s like nothing happened. It reverts everything to stock.
Any other thoughts ?
I do not believe you have an international version of the sgs2, you may have 19100 G or other version which cannot be rooted by using the standard cfroot.
check the label under the battery for which version you have.
I do not trust any of the information from the firmware as it may have been altered as one of the tweaks.
as far as I know the was no XXKDH. the number system used is 2 letters followed by a number
k = year d= month 2011 - april is correct but the H is not.
you may have a chinese rip off of the sgs2.
# = version for that month.
Thank you for your answer Cosmic Blue
The phone isn`t a rip off. It`s a SGS2 from Orange, Ukraine (I believe).
Everything on the device is signed by Samsung. The phone`s specs are exactly what they should be. Kies identifies is perfectly and I can sync everything with it. Samsung drivers also work correctly.
Label behind the battery:
MODEL: GT-I9100
SSN: I9100GSMH
RATED: 3,7V = ; 1000 mA
FCC ID: A3LGTI9100
MADE IN KOREA BY SAMSUNG
Click to expand...
Click to collapse
Plus IMEI (The original one I`m trying to restore) and Serial Number.
Also, on the bottom rim, next to the speaker, there`s the Orange logo and I9100.
I had a brand new I9100 before, and this one isn`t any different from that one in anyway, except that the OS is all messed-up and the IMEI is a generic one, a problem a lot of people found themselves in around here.
Also, you can find the firmware version I mentioned above at samfirmware.com
As XWKDD was one of the first i would say KDH is probably correct but you are reading wrong info .
Therefore H is correct and phone is i9100 SGS 2 not a Chinese rip off .
First firmware on stock roms thread .
XWKDD
Firmware info
PDA:XWKDD
PHONE: XXKDH
Build date: 26/04/2011
However it looks like you have failed to install cwm and root .
Go to the cwm and root thread and flash the first one as below via ODIN
http://forum.xda-developers.com/showthread.php?t=1103399
CF-Root-SGS2_XW_XEU_KE2-v4.0-CWM4.zip -
Flash that one via ODIN report back
jje
Same problem with it.
Downloaded the mentioned CF-Root version, flashed it using Odin as PDA, rebooted with no SuperUser app in application drawer. Rebooted and tried accessing CWM with no success. Just Android System Recovery <3e>.
Also, reflashed CF-Root without Auto Reboot in Odin, and when it finished, I removed the battery and put it back in. Tried to access CWM with the same results as above.
I managed yesterday to root it by flashing XWKDD_insecure.tar as PDA and using SuperOneClick v2.3.2. The phone had a SuperUser app on it, but the phone was really lagging and after a reboot, it wasnt` there anymore.
The problem is definite then the read only memory is not holding the flash possible its a part that holds the ram during flash that is corrupt .
Sorry not a clue it looks like service job to me .
A thought have a look at Mobile ODin thread .
jje
Hi.
Sorry for the late input, I`ve been quite busy lately.
I can`t try Mobile Odin as rooting it doesn`t really work.
I flashed XWKDD_insecure.tar and then used SuperOneClick but all that it does is put a SuperUser icon in my Apps folder
I think that after the restart for for flashing XWKDD_insecure.tar it reverted its changes, as it usually does. SupeOneClick would probably have the same result on it without bothering to flash the insecure kernel.
Anyway, I got tired of using it just as a door stopper so I took it to a certified Samsung service. After a couple of days they called to let me know that motherboard needs changing and it would cost somewhere around $300 to change it.
I guess I`ll be selling it for spare parts or giving it to one of my nieces to learn typing on.
Thanks JJEgan for your effort.
proone said:
Hi.
Sorry for the late input, I`ve been quite busy lately.
I can`t try Mobile Odin as rooting it doesn`t really work.
I flashed XWKDD_insecure.tar and then used SuperOneClick but all that it does is put a SuperUser icon in my Apps folder
I think that after the restart for for flashing XWKDD_insecure.tar it reverted its changes, as it usually does. SupeOneClick would probably have the same result on it without bothering to flash the insecure kernel.
Anyway, I got tired of using it just as a door stopper so I took it to a certified Samsung service. After a couple of days they called to let me know that motherboard needs changing and it would cost somewhere around $300 to change it.
I guess I`ll be selling it for spare parts or giving it to one of my nieces to learn typing on.
Thanks JJEgan for your effort.
Click to expand...
Click to collapse
I have seen this before, basically the NAND controller is toasted so it cant write, only read.
As they said, only way is to replace the motherboard (Where the NAND/controller) is.
Its a shame they wont repair it under warranty, I suppose they noticed that its been flashed and killed
Model: GT-19100, SSN: 19100GSMH, made in korea by samsung, I flashed it back using a rom from Xda forums but now its Android 2.3.5, no super user, I have HC-kTool that I downloaded from new Android market, it says I need root to use HC-kTool. I have Root explorer and Rom manager but I dont have root, how do I fix imie, baseband, my Samsung galaxy s2 works well on wifi, everything works but it doesnt read my sim?????
Related
Hello all,
To keep it concise:
Received my SII from Vodafone yestersday - all is well.
Proceeded to flash the phone with XWK37 firmware and rooted the phone by flashing chainfire's insecure kernel, applying root and then flashing the stock XWK37 kernel - have used Odin before and all is well.
By the time I finish playing with the phone it's 3.00am so I put the SII on charge (battery at around 30%) - all is still suspiciously well.
Get up at 7am to take my kid to school and when I get back I discover that the menu key no longer does anything when pressed (home key and return key still work fine) - it doesn't light up nor does it bring up a menu - all is not well.
So far I've tried:
Reflashing both the firmware and kernal - no effect.
Removing sim card, sd card and battery - no effect.
Hard resetting (both via button method and android privacy menu) / formatting sd card - no effect.
Dialling *#*#2663#*#* and updating the touch firmware - no effect.
Accused my wife of breaking my phone before she went to work - no effect.
Now If it's a hardware problem (which would be disappointing since I've only had the phone for 1 day) then I'm stuck since there is no stock UK Vodafone firmware available yet to flash back to before handing in for repair - plus I don't want to go back to using my N97 in the meantime.
Yes I preordered the N97 before it was released and got myself stuck in an 18 year contract - words can't describe how much I hate that worthless piece of Nokia - I kept it to teach myself a lesson, early adoptions don't pay off.
The only other relevant thing I can think of is that I was trying to install ADW launcher (previously used it a lot) before I went to sleep last night however although the phone claimed that it downloaded and installed - no icon appeared and I was unable to launch it although it's wallpapers showed up when I was switching my live wallpaper.
Can anyone help with any idea's of what it might be aside from a hardware issue?
If it is a hardware issue, anyone know when the Vodafone UK firmware might shown up?
Tell you what, I'll throw in a free N97 for anyone who solves the problem
Thanks guys.
K37 firmware ????
I would flash old firmware like WKDD .
Possible with pit and repartition checked if that failed . Not used either yet on SGS2 but always cleared SGS1 by that method .
jje
Thanks for the reply jje,
The XWKE7 is the latest generic XEU firmware available from this guide:
http://forum.xda-developers.com/showthread.php?t=1075278
I flashed it exactly as the guide stipulated.
However I didn't even think to try flashing it to a earlier version to see if the problem might be with the actual firmware.
Should be finishing work in a couple of hours so will try flashing the older XWKDD
firmware and see if that relocates the menu key.
Will update as soon as I know.
Damn.
No luck - tried flashing KDD (and also KE1/KE2 for good measure) accompanied by full memory wipes - still no luck. All these firmware files come in one .tar package which i place into the PDA section of Odin.
Even tried one where the pda, modem and csc were split into seperate files from:
http://forum.xda-developers.com/showthread.php?t=1075278&page=11
Still no return of the menu key.
When I am flashing - I leave the pit section of Odin completely alone and leave re-partition unticked - I take it this is correct?
It's strange because apart from the menu key - the S2 is working perfectly.
The only other thing I can think of is that the Vodafone branded version of the S2 in won't work with any other generic firmware which is pretty unlikely methinks.
jje - "...possible with pit and repartition checked if that failed.." - I didn't quite understand what you were recommending there mate - should I be using a pit file and checking repartition?
Any other ideas guys?
Off to go glare at my wife's dumbed down yet fully working iphone - it's laughing at me...
I've got the same problem. The menu button works just when it wants. Sometimes it doesn't react at all, sometimes it works perfectly.
I have KE1 firmware, I have rooted it and unrooted (for sim unlocking), then installed original kernel via Odin. Everything was wonderful and I was the happiest guy in the world! One day later the button began behaving like a goast! as chronicpoetic mentioned.
I would like to try installing the new firmware via Odin, but I am afraid that if it's hardware problem, then it won't be taken by service.
Any suggestions?
sounds like hardware faults guys :/
Thank you for reply! I thougt it was too, but... read below
I found out something else.
The menu button works, but with an extreme long delay - 15-30 seconds! More often just right after screen unlock. It just appears and disappers 30 times if I pushed it 30 times before.
And still it can work just perfectly. Sometimes after connecting it to PC or charging it. That dosn't work like a rule.
I am trying to find the reason of such unusual behaviour, but I am lack of expirience.
Any help?
Hello man
I hope that my info will help you
I was in samfirmware.com site and i remembered your problem and i recall that you say Vodafone
so i saw "Provider Samsung I9100 Firmwares" and one of them looks like Vodafone firmware...... please see this site hope to helps you:
http://www.samfirmware.com/WEBPROTECT-i9100.htm
sorry for my bad english
Yeapp, I visited the partner of samsung service center, they said it was a hardware.
Same thing here, any progres?
Just revisited this post - I managed to get a hold of the original Vodafone Firmware from Intratech's thread, flashed it and returned the phone - turns out it was a hardware fault.
Vodafone promptly replaced mine folks.
Sent from my GT-I9100 using xda premium
I'm still pretty new to this, But what i've done so far.
Check out a few roms, install them, changed kernels all going fine. Noticed a few issues but they were rom related afaik.
What i didnt do, figure out a way to backup my original kernel. My first backup was after using cf-root.
In kies before i did anything, it said you have the latest firmware and listed check for updates button. Now it says This version of the device cannot be updated.
I've gone back to
Three UK
XWKI4:
Firmware info: PDA: XWKI4 Phone: NEKI1 CSC:H3GKI1
XWKI4 Stock Kernel:
Password: [email protected]
My issue is, even with this kies still doesnt want to even check for updates. What is confusing me is, this package seems to suggest my CSC will be H3GKI1 afterwards, where it only reads CSC:KI1 (KOR)
My understanding is that KOR isnt what i'm looking for, i'm starting to think this is just a kies issue as my phone does read as H3GKI1.
my question really is, does anyone have the default information noted down what 3 uk sgs2 ship with.
And what steps are needed to get kies to like my phone again. I may re ask this when i figure out a way to phrase it better.
You might need to change your CSC by typing *#272*<IMEI># into the dialler (obviously replacing <IMEI> with your IMEI). This will probably reset your phone (and maybe also to factory defaults). Even if it doesn't, you might need to do a reset to factory defaults within recovery to get the new CSC recognised properly.
After much searching i found something out
It appears its my product code that is incorrect, if i check the CSC on my phone, it comes up correct.
Kies still reads my phone as Kor, Ive now seen this is much more comment than i first thought.
Typeing *#272*<IMEI># up brings up what should be a list, but only has Kor listed and no way of changing it.
*#272*<IMEI># seems to be the way forward, but currently doesnt list anything other than Kor and i current have the stock 3 uk firmware on my device.
feck199 said:
Typeing *#272*<IMEI># up brings up what should be a list, but only has Kor listed and no way of changing it.
Click to expand...
Click to collapse
You might need to get the CSC from [ROM+Guide]Official i9100 Firmwares KG, KH1/2/3/4, KI1/2/3/4/8, KJ1/2 Download and try flashing it in Odin as CSC. I'm not familiar with this process though as I've never done it.
Intratech said:
3 Network UK H3GKI1 CSC: http://www.multiupload.com/P8DL2EMO9D
Click to expand...
Click to collapse
My situation was like yours just a day ago.
my galaxy s2 is also 3 network branded but with Danish firmware
I did get KIES to like my phone again.
first I formatted my internal memory (USB storage) in the firmware as it was since i flashed it. This is not the SD card.
In my USB storage internal, it was a mess.
second i flashed the stock 3 network branded firmware (xwke1). After flashed, i connected the phone to KIES and it found the latest update, Now my KIES likes my Galaxy s2 again.
Remember to backup, before erase/formatting the usb storage.
Try these steps, maybe this helps you as it helped me.
I'll try the formatting my internal storage option!
I have already flashed the 3 uk firmware to my device!
Edit, i'll try again later but formatting and flashing didnt do the trick.
Using the stock 3 Network UK H3GKI1 CSC: , my phone reboots, i see the csc on the phone correctly but kies still sees kor. The only thing i know to be out of place on my phone is the product code.
feck199 said:
The only thing i know to be out of place on my phone is the product code.
Click to expand...
Click to collapse
One other place you could check is /system/csc/sales_code.dat
That file says H3G, but the phone doesnt come up as that when plugged in.
I found forum.xda-developers.com/showthread.php?p=11164781 "[HOWTO] Universal CSC & recover product code [ANY ROM] (I5801 supported)
"
Which would let me change the CSC, but sadly there is no H3G file listed atm!
Alright
Maybe i just was lucky. i did this to get a new fresh start by cleaning out the internal storage (usb-storage)
Try erasing/formatting the data and cache in recovery mode and then restart, maybe this helps.
Recovery mode = original android recovery = volume up, home button and power pressing at same time
Kies started working again,
Formatting data + sdcard didnt work!
Installing a kernel with cwm, and formatting data+sdcard+system+cache then installing stock image did work.
Kies is now offering me KI8 update, and says H3G.
I did notice, after installing stock image it reboots once and does a mini install screen before it boots into the os for the first time.
It popped up an error about not been able to write to /system/csc/H3G . Noticed this ealier today, which is what led me onto formatting /system as well. Did still see the error after i formatted but kies worked so i'm happy.
Im glad, i could help.
Maybe the phone just needed a fresh start as a out-of-the-box.
This problem actually caused me to go out and buy another i9100 (which i've successfully rooted multiple times, so I don't think my process is wrong). I'm just trying to get it working so i can have a spare. I've tried searching and couldn't find anything relating to this problem.
Firstly, the problem is like the phones memory is locked. It works completely normally, but if there are any data changes (send/receive messages, install apps, take pictures, change settings... or even deleting things), as soon as the phone is restarted, everything is restored back to the state it was in on 9th November. I don't think the date is relevant to the problem, however
Taking that into account, I'm trying to fix my phone by rooting it and installing a fresh OS on top, but because of this "locked memory" anything i do is ineffective.
I've tried to go into download mode and flash CF-Root onto it, which appears successful, but when it boots back up it's as if nothing happened - no superuser app, no triangle at boot screen. See here: hxxx://i.imgur.com/M0LKW.jpg
I've also tried SuperOneClick. It goes through its process but hangs after "rooting device step#7". See here :hxxx://i.imgur.com/XcPwO.jpg
Entering recovery mode and performing a factory reset doesn't do anything
Deleting everything on the internal SD through windows doesn't do anything.
So because I can't get root, I can't flash CWM or a new OS on top and i'm stuck with a phone which won't change. If i use the phone normally, after a few days it gets stuck in a crash loop (crashes, hit force close, app relaunches and crashes immediately, repeat) and i'm forced to restart. See here: hxxx://i.imgur.com/ACFl5.jpg
I'm out of ideas. Is there anything else I can try?
Phone details:
Model: GT-I9100
Android v: 2.3.6
Baseband: I9100XXKI4
Kernel: [email protected] #2
Build: GINGERBREAD.XWKK2
Thanks in advance
chunkmo said:
This problem actually caused me to go out and buy another i9100 (which i've successfully rooted multiple times, so I don't think my process is wrong). I'm just trying to get it working so i can have a spare. I've tried searching and couldn't find anything relating to this problem.
Firstly, the problem is like the phones memory is locked. It works completely normally, but if there are any data changes (send/receive messages, install apps, take pictures, change settings... or even deleting things), as soon as the phone is restarted, everything is restored back to the state it was in on 9th November. I don't think the date is relevant to the problem, however
Taking that into account, I'm trying to fix my phone by rooting it and installing a fresh OS on top, but because of this "locked memory" anything i do is ineffective.
I've tried to go into download mode and flash CF-Root onto it, which appears successful, but when it boots back up it's as if nothing happened - no superuser app, no triangle at boot screen. See here: hxxx://i.imgur.com/M0LKW.jpg
I've also tried SuperOneClick. It goes through its process but hangs after "rooting device step#7". See here :hxxx://i.imgur.com/XcPwO.jpg
Entering recovery mode and performing a factory reset doesn't do anything
Deleting everything on the internal SD through windows doesn't do anything.
So because I can't get root, I can't flash CWM or a new OS on top and i'm stuck with a phone which won't change. If i use the phone normally, after a few days it gets stuck in a crash loop (crashes, hit force close, app relaunches and crashes immediately, repeat) and i'm forced to restart. See here: hxxx://i.imgur.com/ACFl5.jpg
I'm out of ideas. Is there anything else I can try?
Phone details:
Model: GT-I9100
Android v: 2.3.6
Baseband: I9100XXKI4
Kernel: [email protected] #2
Build: GINGERBREAD.XWKK2
Thanks in advance
Click to expand...
Click to collapse
This is the first time I have heard anything like this (it's like deep freeze(for pc) activated) Anyway I suggest you re flash a stock rom and then root by using something like Siyah latest both via Odin.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
king_below_my_lord said:
This is the first time I have heard anything like this (it's like deep freeze(for pc) activated) Anyway I suggest you re flash a stock rom and then root by using something like Siyah latest both via Odin.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
Click to expand...
Click to collapse
Thanks for the suggestion. Just tried this but the same thing happened - booted up with nothing changed
chunkmo said:
Thanks for the suggestion. Just tried this but the same thing happened - booted up with nothing changed
Click to expand...
Click to collapse
After flashing a stock firmware via Odin your phone booted up like nothing happened? It's quite impossible I tell you, you must have done something wrong, you must download a stock firmware for your phone (according to region if required) go into download mode flash the tar.md5 file selecting PDA in Odin don't check re partition tick factory reset, and after flashing your phone should be having a new stock rom, try jb or gingerbread stock if the problem persist (logically it shouldn't).
Locked memory huh good name, if you're memory is resetting because of a hardware fault then we can't do anything except send it to the service center, could you post a link to a video of this particular problem it's hm.. You know it's quite unbelievable and maybe a video of your phone resetting itself could maybe stir up some developers who know a bit of hardware.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
king_below_my_lord said:
After flashing a stock firmware via Odin your phone booted up like nothing happened? It's quite impossible I tell you, you must have done something wrong, you must download a stock firmware for your phone (according to region if required) go into download mode flash the tar.md5 file selecting PDA in Odin don't check re partition tick factory reset, and after flashing your phone should be having a new stock rom, try jb or gingerbread stock if the problem persist (logically it shouldn't).
Locked memory huh good name, if you're memory is resetting because of a hardware fault then we can't do anything except send it to the service center, could you post a link to a video of this particular problem it's hm.. You know it's quite unbelievable and maybe a video of your phone resetting itself could maybe stir up some developers who know a bit of hardware.
Using GT - I9100
I thank those who give helpful comments
I expect the same from others.
Click to expand...
Click to collapse
Yep i'll record a video later today.
I'm guessing i'll have to send it in, but it'd be good just to document this kind of problem
Reflashes via odin and nothing Changed
Hit me with a hammer....
Seems like your phone is alive and dont want to die
Sent from my GT-I9100 using Tapatalk 2
A video for your viewing pleasure: (delete the space)
you tube.com/watch?v=31gjELaVDm0
Any ideas?
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
This has been posted before and does not work in many cases .
Although the method can be useful to restore to original firmware .
jje
Yes, flashing a stock rom will sometimes fix the problem of the efs folder not being mounted or read. It won't fix a corrupt partition or damaged files.
The stock rom you flashed didn't contain any efs data so it isn't any substitute for a backup, you were very lucky it worked.
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Same problem
hello guys,
Well I'm to tell the story of how my aunt damaged apparently her phone
At first the phone is a samsung galaxy S3 from movistar (locked), and she bought a freaking iphone 5 to give the S3 to his husband and there it starts the problem he's in another company so she goes to a store to unlock the phone, the guys on the store supposedly unlocked the phone. So when she arrives home, she puts the sim into the phone and SORPRISE it says emergency calls only and not registered in network. After a week she calls me and hands me over the phone.
My surprise was when I put it in recovery mode, it says flash count 3, and then i did all these terrible things with thephone.
1) Flash it to a stock movistar rom 4.1.2.
2) Sorprise the IMEI sayd null.
3) Searching in the web, found the ariza patch, and I patched it without saving the efs (big mistake).
4) The phone imei's became 0049.
5) So I flash it back to the rom they put in the store and the imei went back I make sure it was the one on the back of the phone.
6) I still stuck in the emergency call not registered in the network thing.
7) Now I rooted the phone erased the whole content of the efs directory (this time with a back up).
8) Did the tutorial thing with samsung kies and I'm back with the movistar rom with the 0049 IMEI.
I don't what to do at this point besides going to samsung and send it to repair I really hope they can fix it at a low price.
Sorry for my english, I'm trying to improve it.
Best Regards
Andy Serrato... the spaniard
Start by reading the stickied faqs and guides EFS/IMEI sticky for one or just pay for a repair .
Galaxy S3(GT-I9300) having the same problem! HELP HELP HEEEELP PLEASE!!
Very unfortunately. this didn't solve my problem, the phone's Serial number is still that auto generated junk, and the EMEI is 00499901640000 as before. I had 4.1.2 on my S3 and Kies has updated it to 4.3 without resolving the issue!
can anyone give an idea on how to surely resolve this issue please. its about 3 months now ever since my phone got screwed up!
Pay for a repair
Perfect
I cannot believe this worked, but it did.
I messed up somehow by trying to flash the wrong cwm.tar file (for i9305) I needed i9300 of course and odin stopped halfway and got stuck, i then pulled the cable out and everything got very messy,.. i kept getting lots of errors etc. i somehow managed to install an old cm11 rom which worked lovely. BUT I had no baseband, no imei, no network, no number, nothing, #*06# or whatever it is, wouldn't work. nothing.
I then started to figure out how the efs filesystem worked, then foundout kies has an emergency thing where i guess they look into there database what your imei was when the phone was built. this would not work because I was using a custom rom (i think) but then I stumbled upon this post. thank goodness!!!!!
It's just restarted and internet, signal, imei is back, baseband version is back. all in order.
however, i think i was also very lucky, but for those of you who are in the position i was in, but this doesn't work, I do think there are ways to get an old efs going again and modify it to your "should be" imei,
if anyone needs an IMEI, I can give you one from a phone i had stolen in vietnam, (not sure its even legal to give it out but whatever)
thank you
Nev
EFS recovery
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
kangerX said:
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Click to expand...
Click to collapse
I have tried the method posted in the thread ..... but EFS didn't recovered ........ so i decided to follow your procedure
like making empty EFS folder.... so how can i do that ...and if so will it work .....as someone here mentioned that Download firmware package doesn't contains any EFS contains .... help me out :good:
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
i love u so much right now,.. worked like a charm,.. and after thjat i was able to unlock my phone,... thanks so much i would love to give u 10000 thanks
I cant get past entering my model number,, I read it right from under the battery and it still keeps telling me to enter the model number. G550T1 doesnt change from G550T1 no matter how many times you type it... I give up.. If I could just get a twrp backup for mine I may be able to fix it. It's metropcs! flashing to the T-Mobile twrp backup by mistake thinking it was the metropcs one is what got me in this situation... Should have paid better attention...
UPDATE: It took my numbers and I'm trying it now, wish me luck
Well I got it to take my model number and did the whole software thing. Everything is all back to stock but it didnt fix the problem.. Still no net work and says theres no sim card.
Which shop samsung
Which shop samsung or repair shop bro.
Please tell.?????? me I am facing too problem.
stwischu said:
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
Click to expand...
Click to collapse
Right I'm really sorry to have to burden all you lovely helpful people with this, as I know there's dozens of threads, of which I have sifted and sifted through for the past 2 days. Most of them have been helpful and I am now 95% fixed, but here is the down low:
Mid-last week, I finally decided to stick a custom rom on my old, laggy Galaxy S3. Up until this point I had been running on stock 4.1.2 Firmware, rooted, with things like Bloatfree cleaning the device up a bit.
I did some research and landed on the latest Paranoid Android build, based on 4.4.4. All was rosey for a little under a week with no problems whatsoever until this Monday afternoon. I was doing nothing other than opening Snapchat when my S3 turned itself off, only to get stuck on the bootscreen.
It took me all day yesterday just to get the thing to boot again, I must of tried 4 different stock roms, searching for ages to find CWM that would flash via Odin and any fix just to get it past boot. After finally getting it into Recovery it kindly let me know that "E:Failed to Mount /EFS".
Since that happened I have managed to get the phone booted up into a stock 4.3 rom, exited factory mode and got it rooted with busy box and terminal. It has become a WiFi-only Tablet, essentially.
I am at the last hurdle, where I have no network connectivity and my IMEI is wrong. I of course have my correct IMEI on the back of the phone which I wish to reintroduce to the phone. I do not have an EFS backup.
TL;DR
Phone on Stock 4.3 ROM SGS3INT-XXUGMK6-BTU-20131216, rooted with busy box, root explorer and terminal. Always had stock kernel.
IMEI incorrect, with no backup of EFS.
I have tried:
EFS Professional - EFS Format errors on mount read/write
NVitems_reader_writer, though I can not get my device to stay in RMNET + DM + MODEM mode to be able to connect via COM port as a serial device.
A few of the other simpler methods from the forums
Any help is much appreciated, and while I have read that modifying the IMEI number is frowned upon and illegal practice, I am simply trying to restore it to it's original state, no tom foolery here.
Regards
Dan
Take it to a repair centre, they can recode it for a small charge. Make sure it works on 4.3 before you pay them.
boomboomer said:
Take it to a repair centre, they can recode it for a small charge. Make sure it works on 4.3 before you pay them.
Click to expand...
Click to collapse
Unfortunately I have tried that with every local shop, and they don't seem to think they can do anything about it, and there is no other official Samsung repair centres nearby! Seems like a problem that independents don't come across too often.
On the methods you've tried you've stated this "A few of the other simpler methods from the forums",
Does this mean you tried flashing the latest modem.bin for your device through Odin or through the recovery?
Saad_ said:
On the methods you've tried you've stated this "A few of the other simpler methods from the forums",
Does this mean you tried flashing the latest modem.bin for your device through Odin or through the recovery?
Click to expand...
Click to collapse
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
D4 BCK said:
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
Click to expand...
Click to collapse
Is there a driver I could be missing for it to connect as a USB modem instead of a serial port when trying this?
Dan
I have a similar problem, efs restored, imei is showing right but cant get any signal, saying emergency calls only. After flashing stock.
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
D4 BCK said:
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
Click to expand...
Click to collapse
A nandroid does not back up the efs unless you are using philz or twrp and you specifically tell it to. There is no way in CWM.
Not sure if you new that or not since you said a full backup but just thought I would pipe in just incase so you don't have troubles next time.
D4 BCK said:
Well, after 3 different phone shops and 2 gruelling weeks, the phone is back in action.
I gave very detailed notes on everything I did to the 3rd guy and he eventually managed to get it working again for a nice £15.
I'm unsure if he did anything else, but for anyone who ends up with this problem in the future, rolling the latest stock ROM will not always work. My phone was successfully recovered by rolling back all the way to 4.0.4. I'm sorry I can't give more information as I've already rooted and stuck SlimROM on it to get it back to how I like it, though this time I have been clever enough to actually create a proper full nandroid backup. I had done a backup before, but in my relative noobness years ago it was not a full backup.
Click to expand...
Click to collapse
hey, i have this similar problem right now. So, what i have to do is rolling back all the way to 4.0.4? will it work? but i haven't coded the right IMEI.. do i have to? btw when you have that failed to mount efs, did you use the tutorial that uses adb shell and mke2fs?
D4 BCK said:
I have tried flashing an XXEMG4 modem onto it and unfortunately hasn't made any difference. My IMEI is currently posted as one of the generic 0049 numbers when *#06# is dialed.
As far as I can tell, my best bet would be finding a way to get the serial port working through NVitem_reader_writer, as I have generated my correct IMEI file to add to the phone, but it won't successfully switch to RMNET + DM + MODEM to be able to connect to my computer in that way!
Dan
Click to expand...
Click to collapse
Hi everybody,
I am trying the same, changing imei by using nv items reader. I have the problem that i got a phone from a friend that has a 0049 IMEI, I dont know what he or someone else did to that phone to kill the imei.
The phone: Galaxy S3 I9300
Buildnumber: JSS15J.I9300XXUGNG3 (Android 4.3)
Baseband: I9300XXUGNA8
Rooted with Odin using CF-Auto-Root-m0-m0xx-gti9300
I am stuck at the same part, i cant get the phone in rmnet + dm + modem mode. what I did is: *#0808# - tip "RMNET + DM + MODEM" - tip "OK" - it says "8 saved!" (but it is not saved, when i go into the *#0808# it switched back to MTP)
When i do this when the phone is connected to my computer there is an unplug sound and a plug sound. So I think the phone tries to get in RMNET + DM + MODEM mode but it does not get it. I can activate all other Modes shown in this menu, only the one i need does not get activated.
What can I do to access this mode?
Thanks for your help in advance.
vuli111 said:
Hi everybody,
I am trying the same, changing imei by using nv items reader. I have the problem that i got a phone from a friend that has a 0049 IMEI, I dont know what he or someone else did to that phone to kill the imei.
The phone: Galaxy S3 I9300
Buildnumber: JSS15J.I9300XXUGNG3 (Android 4.3)
Baseband: I9300XXUGNA8
Rooted with Odin using CF-Auto-Root-m0-m0xx-gti9300
I am stuck at the same part, i cant get the phone in rmnet + dm + modem mode. what I did is: *#0808# - tip "RMNET + DM + MODEM" - tip "OK" - it says "8 saved!" (but it is not saved, when i go into the *#0808# it switched back to MTP)
When i do this when the phone is connected to my computer there is an unplug sound and a plug sound. So I think the phone tries to get in RMNET + DM + MODEM mode but it does not get it. I can activate all other Modes shown in this menu, only the one i need does not get activated.
What can I do to access this mode?
Thanks for your help in advance.
Click to expand...
Click to collapse
Discussion is against the rules, and also illegal.
Changing to rmnet + dm + modem Mode is illegal?
Changing imei, which what your post stated, is illegal -don't ask for help here.
Take it to a repair centre and pay them to restore your efs folder.
I did not ask for help to change the imei.
I asked for help to get in the rmnet mode. Is this illegal too??