My GSII I9100 got pretty wet in the rain recently - I was so stupid!
I was running CM10.1 nightly on it.
After this, it was working fine for a few days and then started to loose network quite often. So I decided to factory reset to see if that fixes it. I also flashed the latest nightly when I did the reset. This got me in to a boot loop, which did not get resolved by another wipe data. So I flashed a Stock JB 4.1.2 via Odin. This also resulted in a boot loop but got resolved when I did a wipe data. At this point, I lost my IMEI.
My next action was the biggest mistake of all - I deleted the EFS without a backup so finally ended up with a generic IMEI.
I already know the solution for this problem - I took it to the service center; they tried to flash the software etc., and finally said this can be fixed only by a motherboard replacement.
Following are the questions that I have for the experts:
1. I cannot receive or make calls but I get HSPAP as well as EDGE data. Does getting EDGE connectivity means that my Radio hardware is working fine?
2. Are there any Apps or API calls that can indicate that the Radio works fine? I don't want to replace the entire motherboard without an actual hardware problem.
3. Are there anyone in the forum who has/knows people with a box to get my IMEI repaired? I'm from Chennai, India.
I thank you all for a patient reading. Looking forward to your advice.
Take it to a local phone shop they will be able to sort imei out pretty cheap compered to a mb replacement.
--------------
alliances+siyah
Related
Hello,
After searching about 10 pages & search engine i haven't find exactly same problem as mine but i think i'm not the only one who had this problem...
I saw that all guys having same problem as me have an IMEI problem with a file on /efs, which is not my case for the IMEI
Problem : no phone, no sms, all data is OK. is someone calls me it rings busy.
Here's what i tried
- My SIM on another S2 = everything OK, the other S2 sim on my phone gives same problem.
- Many ROMs official or non official (also a release using pit+pda+phone+csc), without solving my problem
- Using the appli GSII_Repair but i can' t download (message appears 2mins after click on install, from PC or from market)
- Phone is operator free and with no signal problem.
- At the moment i just put an official rom (nothing more) with baseband i9100xxki3, kernel 2.6.35.[email protected] #2, Version number gingerbread.xxki3. Network State=Connected, IMEI= same as behind battery, IMEISV=01
I bought the phone to someone living 150km from me and when i wanted to test it...i locked my SIM (and no puk code with me) so i bought it for not having done the 300km for nothing...and i can't use it since a week i'm trying & reading things everywhere on the net but i think here is the best place, great members, great place, and great roms i used on my HD2 before the USB connector broke. The guy to wich i bought the phone kept it a month and have no idea to what has been done the phone
So help needed....Thanks
Stal_076 said:
Hello,
After searching about 10 pages & search engine i haven't find exactly same problem as mine but i think i'm not the only one who had this problem...
I saw that all guys having same problem as me have an IMEI problem with a file on /efs, which is not my case for the IMEI
Problem : no phone, no sms, all data is OK. is someone calls me it rings busy.
Here's what i tried
- My SIM on another S2 = everything OK, the other S2 sim on my phone gives same problem.
- Many ROMs official or non official (also a release using pit+pda+phone+csc), without solving my problem
- Using the appli GSII_Repair but i can' t download (message appears 2mins after click on install, from PC or from market)
- Phone is operator free and with no signal problem.
- At the moment i just put an official rom (nothing more) with baseband i9100xxki3, kernel [email protected] #2, Version number gingerbread.xxki3. Network State=Connected, IMEI= same as behind battery, IMEISV=01
I bought the phone to someone living 150km from me and when i wanted to test it...i locked my SIM (and no puk code with me) so i bought it for not having done the 300km for nothing...and i can't use it since a week i'm trying & reading things everywhere on the net but i think here is the best place, great members, great place, and great roms i used on my HD2 before the USB connector broke. The guy to wich i bought the phone kept it a month and have no idea to what has been done the phone
So help needed....Thanks
Click to expand...
Click to collapse
Have you already tried to do a factory reset?
Shut down the phone, reboot into recovery mode (Volume UP + Home + Power, hold the keys until the recovery menu appears), choose factory reset and then reboot the phone.
If that does not help, you could try to flash a newer stock ROM, such as XWKJ3.
Have a look at Intratech's Official Firmware thread here => http://forum.xda-developers.com/showthread.php?t=1075278
If that does not help either, it could be a hardware issue.
Hope that it is not.
Good luck !
I already have done both, and i just have done the 2 things again just in cas
Factory reset => still having problem
XWKJ3 => i'm getting permanently a message like com.android.phone crashed, i now remember why i changed for an older ROM
Sounds like flashing many roms syndrome .
Also the no no of using PIT files .
Suggestion
Download full stock rom .
Backup all data .
Go to recovery Mounts and storage Format > Cache System Data > SD Card .
No boot now clean empty phone .
Download mode and via Odin flash stock rom .
Test if still faulty return under warranty .
jje
I dont want to be a negative ned and throw a spanner in the works here but if the IMEI is intact and the phone was bought second hand(and no offence with what im about to say) but is it possible that the IMEI has been blocked cos yourve unknowingly bought a stolen phoneIt just seems strange that only calls and sms are blocked with the IMEI no being changed.Sorry if ive miss understood the question.No offence intended.
I've bought a Samsung SGH-I717 locked with Rogers that's was working perfectly with my Koodo sim on LTE. Here's what happened. I was doing all right, starting by unlocking my phone (First success!). Rooting my phone (Second success!!). Installed CWR (Third success!!!) Why stopping there? I wanted to install LiquidSmooth JB. So, I've started the installation following every steps to the letter. Restart the phone... Hello? No more phone. Just got a nice brick...:crying: So, as a humble guy, I sent it to an unbricker. Don't plan to brick it again so to pay for the JTAG won't have been cost wise. I got my phone back (less 85$ ) but...with the AT&T rom (4.0.4). My problem is that my data isn't working anymore. The WIFI works fine but I won't see the LTE logo next to the WIFI one and as soon as I close the WIFI, no more data. I've tried the plain reflash from Kies. It worked, for the flash, but didn't resolved my data connection issue. I've turned on every things in the Wireless settings, it's not from there, I'm sure. Packet Data and roaming are checked. So, what can be my problem? Just to be sure, do I have to use AT&T rom from now on? No more canadian stuff? Thanks from a desperate guy...
You can install CWR and flash Canadian ROM. The ROM will be already rooted. That liquidsmooth ROM broke lots of phones. The ROM was actually for an S3.
It's worst now. :crying::crying::crying: Since the phone was unrooted, I want to root it again. I've followed this steps : droidgator.com/root-att-galaxy-note-sgh-i717-running-android-4-0 and now... It will only boot up to the Samsung logo. I can at least access the download mode. I'm so [email protected][email protected]$ tired of this.
Hello all,
I am facing a problem with my S2(bought 1.5 yrs ago)...
I rooted my handset and installed RootBox rom. After a while I started facing a problem like, my handset would be functioning properly but, if someone would try calling me he would get the message that the number is switched off and I would not be able to make a call or send any message either. I would have restart my handset after which it would start recieving and calling.
This problem could happen anytime.
So, yesterday I flashed official samsung ICS rom(with Siyah kernal) but today I just faced the problem again.
I am not able to understand whether it is due to some hardware problem or it is a software issue.
Please if anyone knows anyting about this type of issue it would be of much help.
Thanks
Flash the leaked 3 part JB firmware via Odin. And do a factory reset. That should give you a pretty clean slate to start troubleshooting. Then see if the issue persists. If it does, off to the Service Centre.
My friend asked me to look at this phone that was softbricked and kept going to CWM recovery everytime it was booted. I updated the CWM to the latest touch version via ODIN then formatted the phone clean. :good: Then I flashed 4.3.1 stable AOKP ROM and the GApps. It was fine, everything else was working. I connected the wi-fi, used bluetooth, signed into google account everything was normal and stable.:highfive: But then I tried calling and it said "no mobile network". Tried sending a text, could not. I went in and searched for network signals then registered to the correct(I AM SURE!) one.:silly: Still no luck. Then I let it choose automatically. Nothing. Then I thought maybe installing another ROM will somehow fix it and flashed CyanogenMod 10.2 stable. Still no luck. I searched around for a flashable radio but could not decide if that would fix it because as far as I am aware if the radio wasn't working no wireless connectivity should've been either.
The phone is Samsung Galaxy S III GTI9300 white 16GB (unlocked) and has been here in Nepal with Nepal Telecom Sim since it was bought. I have no Idea how the soft brick happened but I think this guy tried to manually update the phone with a stock firmware during which some **** must've happened.
Can you guys please let me know if this could be fixed?
Any help would be highly appreciated.:fingers-crossed::fingers-crossed:
There are hundreds of identical threads, search and read about efs and imei issues.
Sent from my GT-I9300 using Tapatalk
Hi guys and gals,
I've had a problem for a week or so, neither my wifi or Bluetooth will turn on. I originally started getting intermittent errors such as "Unfortunately, Bluetooth Share has stopped" in connection with Android wear app. These errors started to roll over to new roms following *complete* wipes.
I've re-locked my bootloader, repaired to complete stock 23.4.A.1.264 with no joy. I'm at a loss now and I'm wondering where to go next, could someone advise me before I return for a warranty repair?
Cheers!
D_JWhite said:
Hi guys and gals,
I've had a problem for a week or so, neither my wifi or Bluetooth will turn on. I originally started getting intermittent errors such as "Unfortunately, Bluetooth Share has stopped" in connection with Android wear app. These errors started to roll over to new roms following *complete* wipes.
I've re-locked my bootloader, repaired to complete stock 23.4.A.1.264 with no joy. I'm at a loss now and I'm wondering where to go next, could someone advise me before I return for a warranty repair?
Cheers!
Click to expand...
Click to collapse
I had the same problem before.In my case,wifi chip burned off.They will give you a new motherboard.Just wipe everything and leave no evidence it was rooted or that it has any other customisations which voids warranty.My advice,dont wait for a fix.there is none.
goaway1234 said:
I had the same problem before.In my case,wifi chip burned off.They will give you a new motherboard.Just wipe everything and leave no evidence it was rooted or that it has any other customisations which voids warranty.My advice,dont wait for a fix.there is none.
Click to expand...
Click to collapse
Thanks for the heads up. In my case, I got wifi yesterday, but only briefly. I found that on other phones (nexus) there's what's known as a persist partition, and this can sometimes become corrupted.
Logcat says my Bluetooth and wifi are still there, just there's something going on at the software level that I can't figure out. I'll try the method above today then it's back to Sony for a warranty repair.