So I got the dreaded "network unavailable" problem, and after hours of searching and flashing different ROMs there doesn't seem to be an easy way to fix this issue (seems to be an IMEI issue and none of the suggested fixes has helped). I want to now restore the phone to out of box condition so I can send it to Samsung with warranty intact.
It is now unrooted (previously had CM7 installed when the problem first arose), but the build number is now "VillainRom 1.0" after my numerous flashing of ROMs (returned to stock, got a boot loop, went to VillainRom, then tried to go back to a stock). Will the phone suffice as is, or do I have to flash another ROM? If so please state which, perhaps my carrier ROM (O2 Ireland).
Baseband: I9100DDKE2
Kernal: 2.6.35.7-I9100DXKH2-CL483911 [email protected]#2
Solved.
For anyone stumbling along to this thread in the future with a similar problem - I simply flashed a stock carrier ROM and that restored the Build Number, Kernel and Baseband
what about custom rom flash counter?
Buy the USB jig from Ebay
Sent from my Overpowered 1.8GHz Samsung Galaxy S2
I think you need to flash a full wipe stock rom with odin... The rom has to be made up of three files and then, after flash, you'll have a cleaned phone...
Sent from my GT-I9100 using Tapatalk
Related
I bought a used GT-I9100M phone that looks new (locked to Bell Canada). But the wifi doesn't turn on.
I click the button to "Turn on Wifi" and the checkmark turns green. Then it scans, finds nothing, and the checkmark turns grey again.
I tried flashing the stock rom (no re-partition), and then doing a factory reset, but it still doesn't work.
Can someone help me?
My guess - Whatever kernel you have is not compatible with the system image. I know this was a problem with UCKK6 for the SGH-I777 - the initramfs of kernels had to be updated for compatibility. Did you flash the stock kernel when you flashed the stock ROM?
Entropy512 said:
My guess - Whatever kernel you have is not compatible with the system image. I know this was a problem with UCKK6 for the SGH-I777 - the initramfs of kernels had to be updated for compatibility. Did you flash the stock kernel when you flashed the stock ROM?
Click to expand...
Click to collapse
I thought I was already on the stock kernel. I will flash it now and update you in a minute.
Ok I flashed the stock kernel, and there is no change.
Any ideas for me? I'm desperate!
Check q&a section several threads about it.
You bought phone with damaged board due to moisture whether humidity, sweat, condensation or dropped in water. Now not sure which board controls wifi whether it's one connected to usb which is cheap and easy to replace, or motherboard which is basically your phone.
Warranty! Try directly samsung since bell will refuse since phone is not tied to your account even if you are bell customer.
Make sure you flash stock Bell kernel, modem and rom before sending for warranty.
Sent from my GT-I9100
I recently installed WanamLite V7.7 XXLP6 Android 4.0.3 Final LP6 on my phone, but the signal was awful, so i tried to install [KERNEL] SpeedMod SGS2 [K2-20 CWM5 CIFS ROOT], hoping that it would fix my problems with the signal.
After that, the phone is permanetly stuck on the Samsung logo and won't go any further. I tried to re-flash the ROM but the problem is still there.
After that I've tried to fix the problem by following instructions on this thread: http://forum.xda-developers.com/showthread.php?t=1108499, but still nothing.
Can someone please help me to fix this problem?
Thanks for your time
I think that you need to do a restore or to flash a gingerbread rom before the ics one... Speedmod is not for ics roms...
Sent from my Galaxy S II powered by CheckROM
You said you followed pulsar's "boot loop" thread... so does that mean you cleared cache, wiped data, factory reset, all that?
Also, a future FYI. Kernels will never address your problems with phone signal. Flashing modems will, but kernels, never.
However, they might affect wi-fi signal, as some kernels have wi-fi drivers included.
Thanks for your responses. I';ve managed to fix my problem by flashing a gingerbread rom. After that i had major signal issues. I've flashed the main modem for my S2 (ki4) but i'm still facing the same issues. Any ideas how to fix the signal problem?
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Or have just not a clue what they installed .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
jje
Try different modems until you find one that works well for you. That's what I and many other people on here have done. This is one thread with CW flashable modems (there are others, search), there are other threads on here (search) with Odin flashable modems if you prefer to use that.
i tried many... right now i'm using XLP6 which shows -93dBm but still when i'm on the phone, 90% the connection is lost and the phone hangs up
I've found that how well a modem works for you depends on where you live and service provider. For me, in Germany on T-mobile I've found XXKI3 to have the best results (with CM7)
I would be trying the modem that came with the phone .
jje
im also running wanamlite 7.7 but with the LP6 kernel...and indeed the kernel has nothing to do with signal levels
i did change the modem to XXKPA and the battery, signal has improved a lot so im sticking with it, my phone originally came with KK1 which kinda sucked even with stock rom
so follow the link they gave you and try the modem untill you find one that suits your needs
by the way, before flashing stuff you should read what is made for what rom so you can avoid bricks/bootloops
My Galaxy S3 GT-I9305 LTE was running Liquid Smooth 2.37. Recently I lost notification and phone ring sounds and now I have lost baseband and I have no cell signal.
In the phone's 'about' section the baseband field is empty. Android version showing is 4.3.
I'm not quite sure what I did wrong, first to try and get back the sounds and then baseband, I have been playing around with various custom and stock ROMS and kernals to get full functionality back.
I've read tons of help posts but nothing works.
Here's a few of the things I've tried with results in brackets, used CWM recovery to restore working backup (failed 'unsupported file' message),
reflashed kernals (neither Boeffla nor yank555 have worked, wipe/data restore in CWM (it still takes me back to 4.3 with no baseband).
I thought I'd re-flash back to the phone's original stock ROM using Kies, but the weird thing is Kies doesn't restore, it upgrades to the latest 4.3 ROM which fails to restore baseband.
I wanted to send the phone back to the 4.1.2 it came with or was it an earlier ROM? I can't remember as I didn't note it down, I bought the phone second hand, it arrived loaded with a stock ROM for Australia's Optus network. I promptly rooted and flashed the phone to Liquid Smooth and the phone ran fine for months on the 2 Degrees Network in New Zealand.
Anyway, I must have tried reflashing a dozen stock roms I've found online using Odin. Some of them partially work, I get sound back, (it seems only the 4.3 ones work, with the german I9305XXUEMKC reliably loading - it even gives me a NZ english install option) but don't restore the baseband
. All the ones I've found for Optus are rejected, I get the 'unsupported device' or status 7 error in Odin.
So I decided to flash one that works, install cwm, root the phone and try installing different baseband kernals to fix the (probably corrupt) efs.
But I'm going round in circles trying to root the phone. Using CWM, supersu shows as successfully installed, but when I boot into the OS root checker shows my phone is not rooted. Knox seems to obstruct every attempt I make to disable it as well. I keep getting these 'knox stopped etc...from working messages'.
I'm sorry if my description is a bit confusing, I'm happy to clarify anything.
I'm at my wits end. I want to try everything before I have to ship the phone off to a repairer who may charge me hundreds of dollars to fix the phone.
This is I9300 not I9305 Q&A
Use the report button and ask a mod to move to the correct forum .
I can offer no help as i fail to understand the post .
As said before you are in wrong place and are not giving us a clear question to answer. If its a root problem there are fixes for it. Status 7 error is discussed in many threads. Flashing MG4 modem fixes efs problem. Downgrading causes problem. Learn to search before making a thread.
I have a I9300 that is not getting any network, the IMEI is 0049... and the serial number is a string of zeros. It was previously running stock 4.1.2 but I wanted to upgrade to at least the latest official ROM - 4.3 and thats how I ended up in this situation.
I've been a Linux user forever and I've owned and flashed a few Android phones in the past but this is my first Samsung Android handset and so the first time I've been bitten by efs. I did lots of reading before attempting the upgrade so I knew to backup the efs partition before doing any flashing. I did this with ktool but restoring my efs backup to various ROMs hasn't restored my network connectivity.
I'm on the 3 network in the UK so when I've been using Odin to restore stock ROMs (I've tried restoring both 4.3 and 4.1.2) I've been using the BTU versions ie
I9300XXUGMK6_I9300OXAGMK6_BTU
I9300XXEMG4_I9300OXAEMG4_BTU
I have now spent four full days reading and trying various solutions suggested in an array of threads on this forum, I've read all the stickies in http://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 plus many more threads and now I've just about given up. I've tried flashing various unofficial ROMs too like CM 10.2, 11 and RevolutionS5 but they all have no network.
My phone is not in factory mode and I've tried zuluman's patched kernel/modem with 4.3 without any luck. I've tried factory resets, deleting /efs, changing the permissions of and editing nv_data.bin with a hex editor amongst other tricks. No go.
So it seems my only remaining option is to take / send my phone to be repaired or fork out for one of these hardware devices that claim to be able to repair IMEI issues. Problem is then I'm back to square one, I've not learned what I wanted to about my phone (how to safely reflash/upgrade it) and I'll be stuck on whatever the repair shop leave me with.
I'd much, much rather fix this myself as then that opens the doors to experimentation, it will prolong the (so far all too brief) life of my phone and be much more satisfying. Until now I thought the SGS3 was (is?) a class phone and I think its much better than the Nexus 4 I had previously, despite inferior specs in many respects.
I'm sure its possible to recover from this without buying dedicated hardware or at least it should be..
I bought my phone 2nd hand less than three months ago but its no longer under any warranty. Another thing that could be an issue is that I was sold it without a box and there is no IMEI printed under or on the battery.
Thanks for your help!
It would seem from my experimentation that reflashing stock ROMs with Odin on the I9300 doesn't affect the efs partition, or at least the stock ROMs I've been flashing don't repair/recreate efs.
I'd be perfectly happy using the Samsung generic IMEI if it will let me connect to my phone network. If anyone knows how might enable that, please speak up!
Same problem encountered before until now...
This are when the problem starts.
My GS3 International had CynagenMod stable build.
1. I've noticed one morning that my GS3 is stuck in a bootloop.
2. Tried reflashing the stable CM ROM, but still stuck n the bootloop.
3. Tried flashing my stock rooted firmware from my TWRP backup.
- after this, I've noticed that only emergency calls and not registered on network always appears.
- my IMEI becomes now generic with 0049...00 but with serial number.
4. Tried sending it for repair in our local cellphone repair shop. Network signal is fixed now but it always ask for permission for the radio. So battery drain is massive.
5. I didn't send it back. Tried to fix it myself. Installed the stock firmware 4.3 using jellybean. To my surprise, the IMEI and serial number comes back. But still no network signal (emergency calls only).
Lastly, still looking for a fix. If anyone had a fix for this one this will be a great help. Also tried restoring/updating through Kies. All the process I took had failed.
Not sure if the problem was the EFS/IMEI or the modem or radio install from the firmware I just installed.
For now, I'm using the stock 4.3 firmware. The only problem now is the network signal. Any suggestions or fix is a great help. TIA!
I have read of people fixing the no network by flashing a known good efs image but I suppose it would have to contain a working generic IMEI. Please PM me if you have such an image for a i9300. I'll have to find such a thread again and get PM'ing.
I've been disappointed by a few things in trying to upgrade my SGS3.
* There is no well documented fix for this EFS/IMEI/no network issue
* This issue seems to be very common for SGS3 owners who have attempted an upgrade to 4.3 or flashing alternate ROMs yet there is no mention of any of this on
http://wiki.cyanogenmod.org/w/Known_Issues_page_for_i9300
and
http://wiki.cyanogenmod.org/w/SGS3FAQ
There needs to be.
* It doesn't seem Heimdall is able to flash a tar.md5 in one hit like Odin can which is a shame for us Linux and OSX users
Great phone but not for hackers and tweakers it seems.
Sounds like the efs was already corrupt before you tried the upgrade, probably a previous botched repair which only worked on 4.1
Take it to a repair centre and pay for them to recode it for you, there is no other fix. Make sure it connects on 4.3 before you pay.
Suggestion: flash a firmware older than MG4 and let it update OTA or by KIES. Generating the efs-v2-data may solve.
the battle rages on...
rp158:
That sounded like a good suggestion to me so I used Odin to install I9300XXELL4_I9300OXAELL4_BTU, which predates MG4. Because the aim was to try an OTA update, I did not root or flash a custom recovery as I know they don't like that.
Like all the ROMs I've tried since my prob, it installed fine but I get no network. After connecting to wifi I first tried OTA via Settings -> About Device -> Software update -> Update but it just says "Failed to update firmware due to network or server problem". I can browse the internet fine so could this be a problem with Three (my telco)? I've heard of some providers blocking OTA.
So next I tried Kies (not Kies 3) under Windows 8. I went to Tools -> Firmware Upgrade and Initialisation but I just get the error 'GT-I9300 does not support initialising'. Fail, fail and fail!
I've yet to run 'Triangle away' and so I have several flash count points listed on the download screen. Could this stop OTA from working? Is there a limit to the number of flashes you can perform before something nasty happens? I presume its just something retailers check before they refund or repair phones.
Something else I noticed while fighting my phone today was that recovery says the CSC code is now KOR. Could that stop OTA working?
Likes me a good idea to run 'Triangle away': I think there is no max. count for flashes, but perhaps counter>0 and status=custom block the update-procedure. So try after unroot both methods again. (CSC-code I down't know.)
Whilst still running I9300XXELL4_I9300OXAELL4_BTU, I rooted it then successfully ran Triangle Away to clear the flash counter before running csc changer to change my CSC to BTU (from KOR). I would've changed it to XEU but that wasn't an option. I checked that worked fine, which it did, and running CSC changer also (conveniently, in my case) un-roots your phone.
After that I tried updating via both Kies and 'About Device' software update but both just gave me the same errors as before so scratch another idea off my very long list then.
Then go to #5
rp158 said:
Then go to #5
Click to expand...
Click to collapse
?
Do you mean Odin flash I9300XXEMB5, which I think is the last release before MG4?
pfmdan said:
?
Click to expand...
Click to collapse
Sorry, too short. Post 5 = repair by Samsung.
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Maybe the US/Qualcomm models of the S3 are safe to flash with alternate ROMS whilst the Exynos-based models aren't?
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Thanks for your suggestions rp158!
pfmdan said:
So, if I choose to get my phone fixed, has this proven that I will be unable to flash any alternate ROMs on it without losing my network/IMEI/serial again?
Click to expand...
Click to collapse
No, that's unnormal. But read before flashing, what users say (some beta's or nightlies are buggy).
Maybe I should've backed up my EFS with philz recovery or dd insteal of ktool, then I might not have ended up in this situation?
Click to expand...
Click to collapse
Probably. I suggest Philz, TWRP or by TerminalEmulator.
Can anyone recommend a good repair service in the UK if my local repair shops can't help?
Click to expand...
Click to collapse
Official Samsung repair-service.
I thought Philz was the only recovery that gave you the option of backing up EFS? I didn't think TWR supported EFS backup/restore? CWM doesn't.
TWRP can, of course.
A corrupted efs can also effect the stability and use of wifi as mac address etc is also stored there.
Check if there is a backup of your efs. Some roms make a backup of it also - neatrom for example. Try flashing xxemg4 or later baseband to see if it fixes it because after having the later bb you also have efs v2
FIXED
Thanks to everyone who made suggestions in trying to get my phones connection back. Its working again now. My 0049 IMEI has gone, my real IMEI come back and my serial number has returned so I can make and receive calls again!
The thing that was preventing my connection and leaving me to suffer the dreaded 'Emergency Calls Only' and 'Not registered on network' errors was nothing to do with EFS but because I had an incorrect CSC. I had flashed stock BTU roms instead of H3G, which is what I should've used being on Three. As soon as I flashed a rom with the correct CSC, my IMEI and serial numbers both returned and this allowed the zuluman patched modem / kernel combo to work. I'm now happily running 4.3 whereas I was previously on a rooted stock 4.1.2.
There are literally 100's of threads on the S3 forums here with S3 owners ending up with a generic IMEI and no serial after attempting a 4.3 upgrade and the standard response is nearly always 'your EFS is probably corrupt' or 'your EFS in the wrong format'. That will be the case sometimes but I'd bet that more often than not the EFS is fine (if updated) and users have flashed a CSC for the wrong region for their telephone network.
Key tools in getting this prob fixed that hardly get any mention are the csc changer app (downloadable via Play but requires root and also factory resets/unroots when run) and A.S_id's rescue firmware
http://forum.xda-developers.com/galaxy-s3/general/odinfirmware-sgsiii-i9300-prerooted-t1825272/
I'd recommend I9300 users flash A.S._id's ROM if they can't find a firmware with the correct CSC for their network and/or csc changer doesn't restore their IMEI and serial.
Lets fix these forums by getting this info into the FAQs in both the general and QA stickies because I know it to be missing hence the endless invalid IMEI / no network postings.
I'll be back shortly wth more details and suggested additions to the S3 FAQs / stickies.
Thanks all!
I've ended up running A.S._id's 4.3 deodexed 'stock' ROM w/ Boeffla 5.3 kernel and zuluman's patched XXUGMK6 modem.
When I used zuluman's patched XXUGMK6 kernel, I would experience small but frequent glitches in 3G streamed audio. I don't have this problem with Boeffla 5.3.
I'd also highly recommend stock TW users turn off smart screen to massively increase your battery life very easily.
Decided to update my GT-i9300 today.
These are the steps I took before I flashed new rom.
Format and factory reset
Wipe cache
Davlik cleaned
Flash new rom
Reboot
I have tried Lollipop 5.0, 5.1 and KitKat all with the same results. Phone keeps losing network connection (Three), I have tried suggestions like airplane mode, delete and reinsert APN detail,remove sim card, switch off phone. I have also reflashed all 3 ROMs twice and still exactly the same error.
Install my backup (Original) Rom and all works fine.
I have the latest CWM too.
Can any help and advise please?
No one willing to help?
I have googled and searched this forum and that is where I found the suggestions that I have tried.
Is your imei and your phone's serial number original?
You can find it in Settings-about device-status
It seems correct to me.
I purchased phone in used condition with broken screen from a work colleague two years ago (no longer works here). I repaired screen but replacement did not have sticker under battery, I stupidly did not remove original sticker or keep a record (stupid I know). Well about two weeks ago I tried to flash a new rom but bricked phone, would not turn on whatsoever. Sent phone off to get repaired (Ebay) but because there was no IMEI number and I did not have box or the original sticker the guy would not repair (which I understand), I located my IMEI number from Google Dashboard and then got a Checkmend Certificate to prove that the phone was legit.
Since it's return I have had this problem. He has flashed an image on which seems to work but no other image that I try will work.
IMEI number is correct as far as I am aware but I am not sure how to confirm the Serial number is correct, any advice?
Just been to an IMEI checking website, inserted my IMEI number and listed serial number on phone and all details came back correct.
Your efs is corrupted and will no longer work with firmware that requires v2 efs.
Only solution, which is what your repair guy did, is to flash the patched modem and kernel -which enables the efs to be read again.
Each time you flash a firmware you will need to then flash patched modem and kernel before you can get connection.
boomboomer said:
Your efs is corrupted and will no longer work with firmware that requires v2 efs.
Only solution, which is what your repair guy did, is to flash the patched modem and kernel -which enables the efs to be read again.
Each time you flash a firmware you will need to then flash patched modem and kernel before you can get connection.
Click to expand...
Click to collapse
Thanks for your reply. Decided to try one last time. Flashed CM 12.1 and it seems to have worked except for one thing, my serial number is not the same as before. IMEI is fine.