I have always had my I9300 rooted, there are way too many apps I don't use to keep it stock. But ever since I had it in for repair (unrooted of course) and got a new board because it lost Bluetooth connection, it has lost the network connections every time I root it. Network being both phone networks and hence, the internet connection. I got it back with Android 4.1.2, I rooted it and within 4 hours, it lost the network. I flashed a Android 4.1.1 and sent it in again, they did nothing butupdate it to 4.1.2 and it worked fine. I rooted this 4.1.2, and it lost connection again. This time, I overlooked the fact that I had forgotten to reset the flash counter and got it back with a polite note that they could not treat it under warrenty since I had rooted it and root frequently provoked the specific error, losing networks. And if I could install the official Android and show NO on the flash count, they would repait it for me. Nice treatment in a root-hostile world of warranty repairs ;=) I reset flas counter using Triangle Away, sent it in again, got it back for the third time and rooted it, same mess. No connection to network. Is this a device-specific error or IS it true that rooting can cause this error? It started with the new board, do the new boards have special sensitivity to rooting as a extra "HAH- you rooted and lost warranty"-function??????
Try a full wipe and fresh stock rom installation before using CF autoroot, backup your efs first though.
Rooting itself can't make any harm because it's just an app and binary, which is optional and works independent to your OS.
Personally I'd flash other rom and check if issue persists. Make /efs backup before.
Related
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.
Hi,
Firstly thanks for time and sorry if this is a noob question but I only have a fairly small amount of experience regarding custom roms.
Here goes...
I have changed the rom on my phone about 5 times over the last couple of years and never had a problem. I have the latest version of teamwin and I'm currently running Android Revolution HD 50.0 by mike1986. This rom works great as have all the other I have used in the past ie Cyanogenmod, Omega etc but the problem I am having is over the last 4 months I am completely losing network and even if I try to search for a mobile operator my phone can't find any unless I run a full power cycle.
I have been reading as much online mainly xda-developers to find a solution to this problem but I'm afraid I'm now just running into a brick wall. I understand this could just be a hardware fault but I have read somewhere that I may have the wrong modem installed for my phone.
How likely is this? Can having the wrong modem cause intermittent problems? Also if this is the case where the I find a tutorial on correcting this issue. Plus which modem should I be using in the UK?
Again thanks for you time and any help would be much appreciated.
Mike
Do a full wipe and flash the latest stock firmware for your country, then factory reset.
Test fully before you install or restore anything. If it is still the same then probably hardware.
Sent from my GT-I9300 using Tapatalk
ok, Will do. I am just waiting for the UK stock firmware to download. I left it downloading while I was out this afternoon and for some reason it failed and now is asking me to wait an hour before retrying
I'll let you know if this solves my problem.
Thanks
ok..
I managed to get hold of the stock firmware from another site. I first installed a version of ICS so I could run triangle away properly after rooting with CF auto root as without doing this I couldn't reset my binary counter even after flashing stock recovery. Then I installed the latest version of JB and ran the official Samsung update to get my phone up to the very latest Official software with device status official.
So now my phone is completely back to if it just came out of the box. I finished late last night and installed nothing but WhatsApp. Then at about 3pm today again I completely lost network and couldn't restore in without a full power cycle. Even searching for Network operators in settings couldn't restore the connection. I can't think of anything else to try.
Any ideas what to try next please?
P.S. The firmware I installed is as far as I can tell for my location. I'm in the U.K. and I'm using the stock BTU version on baseband version I9300XXUGMK6
the same i9300 problem
Mike_aMPLe said:
ok..
I managed to get hold of the stock firmware from another site. I first installed a version of ICS so I could run triangle away properly after rooting with CF auto root as without doing this I couldn't reset my binary counter even after flashing stock recovery. Then I installed the latest version of JB and ran the official Samsung update to get my phone up to the very latest Official software with device status official.
So now my phone is completely back to if it just came out of the box. I finished late last night and installed nothing but WhatsApp. Then at about 3pm today again I completely lost network and couldn't restore in without a full power cycle. Even searching for Network operators in settings couldn't restore the connection. I can't think of anything else to try.
Any ideas what to try next please?
P.S. The firmware I installed is as far as I can tell for my location. I'm in the U.K. and I'm using the stock BTU version on baseband version I9300XXUGMK6
Click to expand...
Click to collapse
Hi I am have the same problem.. I've tried 2x reapir store.. but just can say: "you need put new main board".
But I have trust that its not better solution (at least for me).
So if you find some solution, please dont forget reply here.
Thanks
O2 by any chance? .. if so it's a network issue. It happened to me a while back but cleared up after a day or two.
shivadow said:
O2 by any chance? .. if so it's a network issue. It happened to me a while back but cleared up after a day or two.
Click to expand...
Click to collapse
This is exactly the issue I have now - I can get some signal, but can't get anything in terms of using 3G/Mobile data :/
Hi everyone. I'm having some serious (or at least I think so) problems with my I777. I live in Colombia, and I bought it over two years ago, had it shipped over by a friend, unlocked. Up until today I'd been using it normally, without any major problems.
However, the last couple of days it started behaving strangely, (turning itself off every once in a while, losing data, etc), so I decided to update my rom today.
I tried to install a new CyanogenMod 4.4 from this site, but I got some kind of status 7 error and it didn't behave properly after that.
Next thing I did to try to fix it was flash a stock JB 4.1.2 rom via Odin.
It worked, but that's when the major problem struck... Apparently my phone got locked for AT&T again or something. It's not recognizing my sim-card anymore. It shows the "no-sim" notification on the top bar, yet it also shows it has a signal (no data, just phone signal), even when my sim-card isn't inserted. When I go in the settings to try to access the mobile networks it says insert sim card even when it's in there.
I did a lot of searching and I used GalaxSimUnlock, which I got from this site too, and it confirms my phone is unlocked.
So basically... What the heck happened?? Is it possible that after three years of using it perfectly with my Colombian sim, the AT&T lock just "came back" or something after flashing a stock rom?
Any clue guys?
If you used galaxsimunlock the unlock is permanent.
Sent from my SGH-I777 using XDA Free mobile app
After you flashed back to stock, did you try to root again and flash another custom ROM?
I could be wrong on this, but the AT&T stock firmware may not be giving you the choice to register the SIM or change the APN settings for you particular network. I can't confirm this though as I never flash to stock long enough to actually use it. I always root and go back to something else immediately afterwards.
The only suggestion I have is to go back to a custom ROM and try again.
If you are trying to go to KitKat, be sure you have the newest compatible recovery (CWM or TWRP) as the versions of those that work with JB will not allow you to flash a KitKat ROM. There are plenty of threads that will tell you what versions you need. If it's an SGH-i777 model then all you should need to get the proper recovery is to flash one of the two KK compatible kernels as the recovery is packaged with them.
Good luck!
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.
Hello all.
New poster here, been coming here for some time though for the loads of great information and generally helpful people.
I'm having an issue with my Honor 5x, and I seem to be the only one i can find on this forum having this issue.
The issue that I am having is that I lose the ability to connect to the cellular networks (I am actually running dual-sim) when I load a custom ROM after the first reboot.. The first time this happened, it even lost the IMEI numbers (WTF). I restored from the backup I made, and tried again. I got the same result, after the first reboot, it can no longer find the cellular networks, and when i try to search for network providers, it gives me an error simply saying "Error searching for networks." Restore backup again, flash resurrection rom to see if maybe CM13 is just being stupid with my phone, got no signal right off the bat, and could not find networks.
At this point, I restored the stock recovery, and let it recover my phone to stock, which is where I am at the moment, since it works. Also noteworthy, that every time I restored from backup, the phone had no problems at all connecting to the cellular networks. as well, it never had an issue through all of this with connecting to WiFi.
Relevant Information:
Phone Model: KIW-L24
Build Number: KIW-L24C567B331
Emui Version: 4.0
Android Version: 6.01
Kernel Version: 3.10.49-g472a5b3
Location: United states
Carriers: Cricket, MetroPCS
Bootloader is unlocked
I have not restored root access
I have Flashed TWRP and made a full backup (again)
I'm getting the feeling that it is due to to something that I have forgotten, but I can't seem to think of anything.
Help?
So close, but no cigar.
Still having issues, here's what Ive done so far:
Restored phone completely to stock, leaving only an unlocked bootloader.
Loaded the latest version of TWRP
Re-Rooted the phone
Made a complete backup of the phone, with no partitions left unchecked, in case of a catastrophic failure
Used TWRP to wipe Dalvik/ART, Cache, System, & Data
Loaded the latest CM13 nightly build
Loaded GApps pico version (I don't use many of the Google apps, so I prefer to download the ones that I want)
Wiped Dalvik/ART
Rebooted Phone
At this point, the phone went about its first boot business, loading stuff in the background, optimizing apps for the first use.
I skipped almost all of the first-time setup stuff, no sense in setting it all up if it didn't work this time as well, but connected to WiFi, selected the primary SIM, and activated data on that SIM. This is all normal from my other attempts as well.
Rebooted the phone, when it came back up, I had signal on my phone, and it successfully sent and received messages.
Added my Google account, rebooted again, not getting signal. checked network operator settings, and I get the message stating "Error searching for networks" for both SIM cards.
Removed Google account, changed SElinux settings to permissive, soft reboot, no change.
In the past, I did try wiping Dalvik/ART & cache once this happened, but the only thing that changed is that it caused the process com.android.phone to crash on me repeatedly.
Currently digging around on the net some more to see if maybe there's something that I missed.
Try 1 Sim? Its some bug with dual sim i guess
I will try that when I get a chance, I am currently trying to restore the phone back to stock again after another failed attempt.
Also noteworthy, I had it completely lose the sim cards on me after a restore to the working stock backup that i made earlier in the day yesterday, I had to completely revert to stock (Restore stock recovery, let it rest the phone to stock) then the SIM cards started working again.
This is starting to get rather frustrating.
I'll keep you updated, as I've kinda decided to make this a log of sorts of my experience with this.
Hellspawn119 said:
I will try that when I get a chance, I am currently trying to restore the phone back to stock again after another failed attempt.
Also noteworthy, I had it completely lose the sim cards on me after a restore to the working stock backup that i made earlier in the day yesterday, I had to completely revert to stock (Restore stock recovery, let it rest the phone to stock) then the SIM cards started working again.
This is starting to get rather frustrating.
I'll keep you updated, as I've kinda decided to make this a log of sorts of my experience with this.
Click to expand...
Click to collapse
Did u fixed it? im having the same issue, although i dont have a backup.....
Tried updating to stock marshmallow first before installing CM?
stanley08 said:
Tried updating to stock marshmallow first before installing CM?
Click to expand...
Click to collapse
I tried that, see my thread http://forum.xda-developers.com/honor-5x/help/network-help-t3445510
i dont really know what to do, could the problem be MODEM.img???
Im having the exact same Issue, All roms loose the SIM card so I loose all signal and basically everything... a restart sometimes helps it, tried installing different ROMS, going back to STOCk 5.0.1 or 6.0.1 nothing Helps... NO clue what to do.
Same issue here. Happens on every Rom.
EDIT: Using KIW-L21 (UK)
Unlocked, single sim.
Maybe the it has something to do with modem.img