Related
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Sent from my GT-I9300 using XDA Premium HD app
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
solarisrulez said:
Hey there,
I have a factory unlocked Samsung Galaxy SIII, international, GT-I9300, freshly rooted and using CWM-based recovery v5.5.0.4::CF - v1.5.
Today I've flashed 2 custom ROMs, one after the other, by following some guides that I've found (cannot post yet links):
1. Android 4.3 via SuperNexus: URL hidden
and after the SuperNexus this one:
2. Android 4.3 via ParanoidAndroid 3.97 ROM: URL hidden
Managed to flash these two successfully, but with both of them I've faced the same problem during initial device setup: could not connect to my Wi-Fi network. Wi-Fi signal was strange too: strong, then suddenly weak. Could not authenticate and connect. :crying:
So, fortunately, made a backup before these two ROM flashes, so I guess I'm back with my stock Samsung TouchWizzy ROM (Android 4.1.2). That I hate. I want something bloatware free, stock-android feel, something like my Nexus 7 tablet.
Can you suggest me a "Wi-Fi capable" stock-like Android 4.3 custom ROM or am I missing something? Maybe a Radio flash (have no idea what's that) but maybe that what I was missing? And if I do that somehow, is that reversible? Never done it before.
Thank you in advance for any help and suggestion! :good:
love,
sz
Click to expand...
Click to collapse
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Guys, Thank you all, trying to reply to everyone:
Enea307 said:
Im using CM 10.2 (4.3)and i dot have any problem whith wifi. I used before PacMan Rom and the same, no problem. Just try a full wipe. And try it again.
Click to expand...
Click to collapse
Thanks, maybe I'll give that one a go as first try.
converse5 said:
This happened to me once with JB 4.1.2 i couldnt figure out what was the problem and in the end it turned out that i was putting the password for WiFi wrong. Just put the pass right and i got connected. Just sharing my experience.
Click to expand...
Click to collapse
No, I'm pretty sure that's not the case. Checked my router admin configuration tried to enter my wi-fi pass about 30 times before giving up.:laugh:
chrismast said:
(1) did you do a full wipe including manual wipes of /system? If not do so and try again (mega wipe can be of help here)
(2) if this doesn't work, did you play around with custom kernels? (wifi is connected to the kernel and less to the baseband/modem used)
I am running SlimBean 4.3 (beta5) without any WiFi issues, also all other roms before that, no issue.
Click to expand...
Click to collapse
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
lefttobleed said:
This must be a modem issue as android 4.3 does not change the modem from the previous samsung rom.
try upgrading to latest samsung 4.1.2 and then install android 4.3.
install 4.3 after doing a mega wipe.
remember to backup everything.
and dont forget to take an efs backup as many ppl are facing major problems after upgrading to latest samsung roms.
Click to expand...
Click to collapse
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
solarisrulez said:
1. Thanks, will do a mega-wipe next time, although with CWM did these in the following order: Wipe data/Factory reset, Wipe Cache Partition, Wipe Dalvik Cache several times. Also, with MegaWipe wiping Preload partitions does what exactly? Just don't want to brick my phone/do something irreversible, as I try to understand everything I do to it
2. No, did not played around with custom kernels. Do not know how to change/flash them. Same as flashing a custom rom? Newbie here :laugh:
Click to expand...
Click to collapse
(1) The best would be to read the mega wipe thread. I use it all the time, it will delete ANYTHING excep the external SD card (also not EFS etc, hence dont worry). Therefore you need a flashable rom on the external sd or via Odin later on. But basically your phone won't start after a mega wipe, just download & recovery will work.
Your wipes are correct I think, whereas /system is missing wich is needed, at least for SlimBean (4.3).
(2) The best would be to read the guides & kernel thread's how-to's first. It is basically the same as flashing a rom, yes.
solarisrulez said:
Thank you! If a modem issue, how to update to the latest Samsung rom? From Sammobile? http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=0#firmware These are carrier-locked roms, cannot find mine, I guess... Newbie here :laugh:
Also, what do you mean by "an efs backup"? How to do one? Thanks!
Click to expand...
Click to collapse
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Misleading title .
#There have been a number of identical posts and some have fixed by copying older WiFi files over . But you need to search and read and no i don't know where they are . .
Its not a custom rom problem but a non Samsung custom rom problem on 4.3 .
jje
lefttobleed said:
Well if u r a newbie. Read all the guides available here. Dont proceed further without doing that. You will learn how to backup efs and all.
U can install any latest custom samsung rom. Again.. Read the guides/warnings before proceeding.
Click to expand...
Click to collapse
Yes, reading the guides, so first of all decided to backup my EFS (coz that sounds reassuring before doing more ROM flashes) with EFS Professional from this thread: http://forum.xda-developers.com/showthread.php?t=1308546
Installed BusyBox on my phone, and I'm stuck because of a missing applet: http://cl.ly/image/1a1J1A0I3V0H.
I think I'm going deeper than what I can handle
BTW, Enea307, tried CM 10.2 (4.3) this morming, and same wi-fi problem. So it's most likely not a custom rom issue, as most of you suggested.
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
JJEgan said:
The only logical; way to rule out firmware is by wiping the phone and flashing stock rom .
jje
Click to expand...
Click to collapse
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
Done everything according to http://forum.xda-developers.com/showthread.php?t=1671969
And the firmware is also the one for my phone, and the *.zip that contained the tar (md5) is not damaged http://cl.ly/image/322h3634211J
Any ideas? thx!
solarisrulez said:
I'm having problems flashing stock firmware. Check of my screenshot: http://cl.ly/image/473N1E0Q3G2X
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
JJEgan said:
That reads as a bad file download Odin unable to open a file .
Or PC problem Kies running usb cable usb connection .
Have you tried installing / updating from KIES
Tools
Click to expand...
Click to collapse
Not installed KIES yet, as I read that that's a big brother or something to Odin, and that his little brother is much better at flashing. Should I give KIES a go? Anyways, trying to redownload the firmware.
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
JJEgan said:
No Kies ?? Unless you installed Samsung USB drivers that's where your problem is .
Click to expand...
Click to collapse
I had installed Samsung Drivers beforehand, before even rooting / doing anything. Did not had KIES until now.
Still cannot flash to stock firmware with Odin.
BTW in the guide: http://forum.xda-developers.com/showthread.php?t=1671969 i see that it should be blue, but mine is yellow when I connect my phone to Odin: http://img600.imageshack.us/img600/9231/odin4c.jpg and mine: http://cl.ly/image/473N1E0Q3G2X
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
IC3CR34M said:
Some roms, mostly PA (paranoid android) just happen to have wifi probs.
I used to have pacman rom earlier and as it was a combination of cyanogen mod, paranoid android, and AOSP roms. It had a part of all three in it, so the wifi bug persisted. Went back to stock rom later.
Usually stock roms are the best and most stable for your phone, No matter how much the hype is, features are, or however big Nd bold letters STABLE is written in. Just delete the bloatware given by samsung to get ur phone clean and ram light. You can delete system apps by using titanium backup.
Happy to help
Click to expand...
Click to collapse
Thing is, that I am rooted, done with Odin, by following this guide: http://www.androidrooting.com/how-to-root-samsung-galaxy-s3-gt-i9300-or-gt-i9300t-cwm-recovery/
So I have CWM, and with I tried Android 4.3 via SuperNexus, Android 4.3 via ParanoidAndroid 3.97 ROM, then, lastly CM 10.2 (4.3). With none of them did I managed to get the Wifi going.
Here is my current "About device": https://www.dropbox.com/sc/8hp04dn5o5flytd/LpoJCgZ7sK
Is this stock samsung firmware? Coz I can't tell. It seems stock, but maybe it changed with the rooting procedure.
So I repeat, only with this setup/build does the wifi work. With no other custom rom does...
I did backup and recovery to my current working wifi rom. That's how I recovered after trying these custom roms mentioned before.
Guys, help me pls, with at least flashing to the stock samsung rom with Odin or Kies (Odin failed, scroll up see my recent posts with screenshots)
Note that on my last try, Odin just froze yet again: http://cl.ly/image/0o0o0k2L3J3m
If not with Odin, then how do I restore it to stock samsung rom with KIES?
thx!
You dont do it with kies. Kies is such bull**** software. Dont use it at all. You wanna backup, use TI(titanium backup) or nandroid backup. Take a system backup from CWM. As you said in your post, u want to go back to stock, dl the stock rom, do the same procedure u did to root your phone via odin (pda, etc etc), just this time instead of the root zip file, just put the stock rom zip file.
It should take some time, and aftet its done, your phone will be as good as new. To restore the backup via TI, dont select system apps. Only the apps which are in green font or downloaded apps. Other wise u will have force closes.
Also, when u flash the stock rom via odin from your pc, you will not have root. Just a note.
You can simply remove bloatware like live wallpapers, samsung "never gonna use" features like Svoice via TI by just uninstalling them, but note, if fiddling with system apps, them make sure u take a backup.
I have written it all in simple language so that you understand every essential part and have fun with your rooted phone.
Happy to help
As always last resort restore original firmware with Kies and probably a better method than some others posted.
SEE The how to restore your original firmware using Kies post .
Sent from my GT-N8010 using XDA Premium 4 mobile app
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
monolithcog said:
Hi Team,
I have a GT-19100T which had the carriers firmware (Vodafail AU) 4.1.3 (rooted) running with no problems until recently (2 wks ago), prior to the fault I have had this phone for years no glitches great phone for its age.
I had let the battery drain, upon re-energizing the phone and attempting to turn on the wireless i noticed it just reported "Turning WI-FI on" and the toggle switch was greyed out. this would last all day. switching the phone off and on would not stop the process of the phone attempting to turn wi-fi on.
I immediately went searching forums and people suggested hardware fault or perform factory wipe through CWM.
Troubleshooting I have performed so far is:
- factory wipe and cache cleanup (not resolved)
- flashed to CM 10.1.3 (not resolved) (multiple times)
++++
OS: 4.2.2
Baseband: 1900TDULP4
kernal version: 3.0.64-cm-g9c2e2bc
++++
I have found from research that the Bluetooth and wi-fi are the same module (I maybe wrong) and Bluetooth is working fine.
So this leads me to suspect a software/firmware fault.
I'm currently downloading I9100TDVLSM_I9100TVAULSF_VAU.zip from (sam mobile) the latest release for this phone from the carrier to see if firmware will resolve the problem.
In the mean time any suggestion, advice, help or solutions would be greatly appreciated.
Maybe if someone knows of a file i can flash specifically for wi-fi module that I could try.
Thanks in advance
Click to expand...
Click to collapse
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
huytrandinh said:
I have same problem few weeks ago when my galaxy on Stock Rom 4.1.2.
Later, I try to reflash again through Odin, then install CWM and I flash CM 10.2 4.3 through CWM and it solved.
I think you should try to flash Newer Rom version, example CM10.2 or SlimKat.
Good luck
Click to expand...
Click to collapse
Thanks mate for your reply,
I installed cm 11, this did not resolve it.
need the file for the radio/modem, i'm hoping this will fix it but not sure exactly what I am looking for.
**Update***
Just finished installing I9100TDVLSM_I9100TVAULSF_VAU (latest release from Sam Mobile) 4.1.2
Still wi-fi not working.
will try and install cm 10.2 on your recommendation huytrandinh
Okay latest nightly of CM is installed cm-10.2-20131216-NIGHTLY-i9100.
Still has not resolved the wi-fi issue.
anyone have a potential solution?
there is this post for S4, but obviously only viable for S4
http://forum.xda-developers.com/showthread.php?t=2192025
There is also this video tutorial which is for S4
http://www.youtube.com/watch?v=YL8H70Es4wg
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
jedzkiiii said:
Try to flash a modem using odin,
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
Have been trying that, still no success.
have spent all day trying to find a solution
I tried the modems from here:
##hxxtp://###.veyka.co.uk/sgs2/radios/## (unable to post links ffs)
and few other random links from the forums
MistahBungle said:
Modem won't solve the issue as WiFi/BT drivers are in the kernel on the S2. OP was on the right track, but for whatever reason a clean install of stock didn't fix the problem.
Maybe try the 3 part firmware in Hopper8's Odin Troubleshooting thread, then a clean install of the Voda stock rom after that ?
There's 'WiFi fixes' (which are actually the LTE modem) for the I9505 as it actually has two separate modems, and the LTE modem also controls WiFi (which isn't the case with the S2 as per my comment above).
Click to expand...
Click to collapse
Thanks Mistahbungle,
I checked out that thread http://forum.xda-developers.com/showthread.php?t=2345831
Nothing i could really use.
But I did try a few other kernels:
Siyah-s2-v5.0.1
Unfortunately as soon as flashing with other kernels the screen would go black after the initial boot logo.
Only way to resolve it not booting into the OS was to roll back to:
1. GT-I9100_JB_ClockworkMod-Recovery_6.0.2.9 (flashed with odin)
2. flash CWM-SuperSU-v0.97 with CWMRecovery
3. install cm-10.2-20131216-NIGHTLY-i9100
4. then your general cleaup through cwmrecovery
I'm not sure if I'm doing something wrong when trying to apply another kernel.
anyone able to offer assistance please with right kernel?
cheers
**Update**
Just found a post in that thread - http://forum.xda-developers.com/showthread.php?t=2345831&page=6
Will try the 3 part rom XXLSJ for GT-I9100.
Fingers crossed
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
MistahBungle said:
Yeah, that's what I suggested in my PP. Sorry, seems the 3 part was on HotFile & Hopper didn't have his own copy up somewhere.
The rationale was - there's possibly something from a previous installation causing your issues, and flashing the 3 part would wipe your phone. I realise you've done this manually, but at this stage you're fast running out of ideas before you declare it a possible hardware issue, and it was worth a shot.
So...What I'd try is - while you have a rooted phone, go into CWRecovery and format everything/ (not EFS though obviously, or your external card if you have one), then try re-flashing whatever stock firmware you have with Odin in download mode.
Edit - Also, maybe do a Google search for that 3 part firmware (details are still on Samfirmware, just that the files are gone), you never know, you might find it somewhere.
Click to expand...
Click to collapse
Okay just finished testing the rom by installing it via odin (3 part)
still has not yielded any favorable results .
Little disapointed as this was a great backup phone and served for the past 12 months as a mp3 player
Guess as they say; It is all planned obsolescent which is fracked ...
Thanks for the suggestion/help anyway.
I know this is an old thread but my gs2 had this problem and I was able to fix it. Using es file explorer made my way to /data/misc/wifi pulled up the properties to wpa_supplicant.conf and changed group to wifi...then wifi finished initializing...hope this helps somebody
Sent from my SM-T310 using XDA Premium 4 mobile app
for consideration.
I have this phone. the GT-i9100. Had this issue also. I took it apart. The little onboard battery had blown and corrosion got all over all it.
and guess where WiFi hard is. Right Next door. I cleaned it up real good. Put it back together and WiFi came back to life.
So give it some thought guys.
This might help someone having these no service/ no sim card no GPS fix issues with the galaxy SGSIII i9300, that might have to do with efs folder change and IMEI corruption.
Okay so i solved these no service issues and ill share my experience so maybe someone will find it helpful.
So the issue has to do with the famous efs folder conundrum, though tbh im not a developer so i cant say exactly what was the issue or even be a 100% sure it was the efs folder.
So I got me a used malfunctioning i9300 which i then repaired at a lab and proceeded to install a new TW based ROM, my first mistake was not backing up efs folder and creating a nandroid, but i havnt realized that yet. After flashing, I noticed that i have no GPS, but i didnt know if the GPS was working with original firmware because i neglected to check that or back it up, so i decided to put a pin in it for the time being and went on to check out some ROMs.
At first, I flashed couple of JB tw based roms, all was well (except for the gps), then i started to check out some KK roms, those didnt play well with my device, I got no service in every single rom i tried, You name it ive tried it, none fixed the service issue. Moreover i also tried a few JB AOSP based ROMs, among them the 4.3 JB PAC-man ROM, those had the same no service/no sim issues. Meanwhile whenever i un-root and flash with odin back to stock or restore a nandroid i made while on 4.3 foxhound ROM (with service working and a supposedly good copy of the efs folder) service is restored. I would also mention that I had more backups of the efs from the working “foxhound” i made with different tools and when i restored these folders when on a ROM with no service it didnt fix the issue.
Here are the solutions ive encountered and tried that didnt work:
-restoring efs with efs pro, samsung tool, efs backup -restore cmd tool.
-flashing latest firmware and flashing back to KK
-flashing all kinds of modems (those pre efs folder change (XXEMG4) and those after)
-flashing latest TWRP/CWM recovery
-flashing kernels
-trying to edit “nv_data.bin” with hex editor
-some more ways in trying to manipulate the efs folder.
-using samsung service codes on stock, which i found regarding this issue, except from the *#06# code, for imei, pretty much none worked for me.
Its important to mention that when on stock firmware or a JB TW based ROM i would see my baseband version in settings and when I tried the *#06# code for checking my imei it gave me a serial number with many digits that I assumed was indeed my correct IMEI number, and when i was on KK ROMs or non TW JB ROMs i would get the same popup with no numbers and in settings i would see “unknown baseband” .
To add to that, whenever i rooted and installed a KK ROM or a JB non TW ROM and tried to restore efs with efs professional i would get a message the device is not perm rooted (but thats neither here nor there).
This research took me about 5-6 days and the end of which i was ready to give up on having a KK rom or a non TW rom for that matter, NOTHING seemed to fix the problem. I just had some fight in me for one more hopeless attempt. I read somewhere that a flashing of cm 10.1 and then going to settings -> more and there change some network stuff from this to that would help -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
I said what the heck thats simple enough. I flashed CM 10.1.3 for i9300 and went into the settings but the options i read about werent the same as the settings i saw in my case,
so i did move one settings around in the settings-> more section, cant remember what it was and im on a different ROM by now,
it was nothing i knew about anyway (but you should give it a go and have a look, there are few options to choose from so you can eliminate your way to what makes sense).
I then went on to recovery to flash carbon rom 4.4 and to my enormous surprise i had service and connection and to my astonishment i also got back the GPS as a bonus ! yay ! I bet you forgot about that too by now…
This ends on a weird note though, though everything is at working order now and the IMEI number i get is the same as the one i get when on stock rom,
it does not match the number on the back of the phone under the battery. well mehh.. as long is its working.
Hope this helps someone.
You didnt mention that exact step. Changing "something from this to that" doesn't really count as being helpful.
Thanks for the post anyways.
~ RazorMC
RazorMC said:
You didnt mention that exact step. Changing "something from this to that" doesn't really count as being helpful.
Thanks for the post anyways.
~ RazorMC
Click to expand...
Click to collapse
Youre right, i couldnt find the thread that had the suggestion to install the 10.1 cm but my point was it didnt even apply to my situation because the options in "Setting -> more" werent compatible with what was suggested in the thread so i had to improvise and I just changed some setting i cant remember in "Settings -> More" but I realise that it would be more helpfull to say what i changed there exactly, but im not on cm 10.1 anymore and cant see what in there now.. the good news is that there werent many options to change there.
But i did went out and looked for the original comment that made me try this an it says -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
so in my case i didnt see these exact same options so i changed what seemed to me the most related to the issue at hand.
I dont think i had to touch the roaming, again i dont have CM 10.1 installed so i dont recall exactly what were my options.
is it a solution mostly for Qualcomm chipset based I9300 ? someone can say ? European providers use different frequencies I guess hence different chipsets and parameters.
Olek94 said:
is it a solution mostly for Qualcomm chipset based I9300 ? someone can say ? European providers use different frequencies I guess hence different chipsets and parameters.
Click to expand...
Click to collapse
mine is the international version but as i mentioned it didnt work like described but the end result was the same. I f you have the LTE version Im not sure which option youre going to get in CM 10.1 settings -> more , but if youre having trouble with service and GPS and stuff like that i do suggest you try flashing CM 10.1 (compatible with LTE - not sure how it goes with CM and LTE compatibility) and check if you got the same options to make the changes to, if not, try and improvise based on what makes even a little sense, thats what i did.
It might be that the flashing of CM 10.1 itself is what fixes the problem, so if you change nothing it might help still, anyway this is pretty simple and quick to do so better start here than starting with other messier solutions.
help
hi i was on stock 4.1.2 then i rooted flashed twrp recovery using toolkit and flashed revolutionary 5 4.3 straight away i didn't backup efs i know it was dump thing to do but i was new to galaxy s3 flashing so basically i f***k up. then i flashed official 4.3 firmware using odin.now i have a network reception but can't make or attend calls.i was thinking to go back to 4.1.2 in hope of getting things to work. please help n reply asap!! thanks
5668892 1021
jabirrockzzz said:
hi i was on stock 4.1.2 then i rooted flashed twrp recovery using toolkit and flashed revolutionary 5 4.3 straight away i didn't backup efs i know it was dump thing to do but i was new to galaxy s3 flashing so basically i f***k up. then i flashed official 4.3 firmware using odin.now i have a network reception but can't make or attend calls.i was thinking to go back to 4.1.2 in hope of getting things to work. please help n reply asap!! thanks
Click to expand...
Click to collapse
I believe I shared every bit of helpful information i can share with you about this issue and my process of handling it in the main message of the thread, Read the entire thing and the comments followed, then follow my suggestion, if you wish to do so.
samuelaviv said:
mine is the international version but as i mentioned it didnt work like described but the end result was the same. I f you have the LTE version Im not sure which option youre going to get in CM 10.1 settings -> more , but if youre having trouble with service and GPS and stuff like that i do suggest you try flashing CM 10.1 (compatible with LTE - not sure how it goes with CM and LTE compatibility) and check if you got the same options to make the changes to, if not, try and improvise based on what makes even a little sense, thats what i did.
It might be that the flashing of CM 10.1 itself is what fixes the problem, so if you change nothing it might help still, anyway this is pretty simple and quick to do so better start here than starting with other messier solutions.
Click to expand...
Click to collapse
Thank you, I was suspecting that you have a similar version than me. Well, in desperate cases anything can be tested (But some have told me not to mess with US versions as there is a risk of burning something )
Anyway the last version I could not flash , the CM 10.1 it was ejected with a file error soon despite 3 downlowd.
I will try with another more compatible version with Cyanogen.
Have a nice day
samuelaviv said:
This might help someone having these no service/ no sim card no gps fix issues with the galaxy s3 i9300, that might have to do with efs folder change and IMEI corruption.
Okay so i solved these no service issues and ill share my experience so maybe someone will find it helpful.
So the issue has to do with the famous efs folder conundrum, though tbh im not a developer so i cant say exactly what was the issue or even be a 100% sure it was the efs folder.
So I got me a used malfunctioning i9300 which i then repaired at a lab and proceeded to install a new TW based rom, my first mistake was not backing up efs folder and creating a nandroid, but i havnt realized that yet. After flashing, I noticed that i have no gps, but i didnt know if the gps was working with original firmware because i neglected to check that or back it up, so i decided to put a pin in it for the time being and went on to check out some roms.
At first, I flashed couple of JB tw based roms, all was well (except for the gps), then i started to check out some KK roms, those didnt play well with my device, I got no service in every single rom i tried, You name it ive tried it, none fixed the service issue. Moreover i also tried a few JB AOSP based roms, among them the 4.3 jb pac-man rom, those had the same no service/no sim issues. Meanwhile whenever i un-root and flash with odin back to stock or restore a nandroid i made while on 4.3 foxhound rom (with service working and a supposedly good copy of the efs folder) service is restored. I would also mention that I had more backups of the efs from the working “foxhound” i made with different tools and when i restored these folders when on a rom with no service it didnt fix the issue.
Here are the solutions ive encountered and tried that didnt work:
-restoring efs with efs pro, samsung tool, efs backup -restore cmd tool.
-flashing latest firmware and flashing back to kk
-flashing all kinds of modems (those pre efs folder change (xxemg4) and those after)
-flashing latest twrp/cwm recovery
-flashing kernels
-trying to edit “nv_data.bin” with hex editor
-some more ways in trying to manipulate the efs folder.
-using samsung service codes on stock, which i found regarding this issue, except from the *#06# code, for imei, pretty much none worked for me.
Its important to mention that when on stock firmware or a JB TW based rom i would see my baseband version in settings and when I tried the *#06# code for checking my imei it gave me a serial number with many digits that I assumed was indeed my correct IMEI number, and when i was on kk roms or non tw JB roms i would get the same popup with no numbers and in settings i would see “unknown baseband” .
To add to that, whenever i rooted and installed a kk rom or a jb non tw rom and tried to restore efs with efs professional i would get a message the device is not perm rooted (but thats neither here nor there).
This research took me about 5-6 days and the end of which i was ready to give up on having a KK rom or a non TW rom for that matter, NOTHING seemed to fix the problem. I just had some fight in me for one more hopeless attempt. I read somewhere that a flashing of cm 10.1 and then going to settings -> more and there change some network stuff from this to that would help -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
I said what the heck thats simple enough. I flashed CM 10.1.3 for i9300 and went into the settings but the options i read about werent the same so i did move one settings around in the more section, cant remember what it was but it was nothing i knew about anyway, then went on to recovery to flash carbon rom 4.4 and to my enormous surprise i had service and connection and to my astonishment i also got back the GPS as a bonus ! yay ! I bet you forgot about that too by now…
This ends on a weird note though, though everything is at working order now and the IMEI number i get is the same as the one i get when on stock rom it does not match the number on the back of the phone under the battary.
Hope this helps someone.
Click to expand...
Click to collapse
:crying: :crying: :crying: :crying: :crying: Dude!!!!! I understand!!!!
I had a similar experience only I also tried flashing CM 10.1 and it did not work. Although I have another imei, I have all my services running on the Stock 4.3. Now the only problem is that if I change to any other rom, does not connect to the wifi network.
I found something like this: http://forum.xda-developers.com/showthread.php?t=839367&page=4
But neither worked. Yesterday I tried to repartition the phone and almost killed. I spent two weeks looking for a solution, and tried them all, but did not work, I think I will draw on the last and the only thing I think work ... The box.
The octopus box (or similar).
KK roms are beautiful ... but no matter what, I have no wifi in another rom than the stock 4.3 lol.
Thank you for your contribution! as you say: I hope you serve someone else.
VIOShero said:
:crying: :crying: :crying: :crying: :crying: Dude!!!!! I understand!!!!
I had a similar experience only I also tried flashing CM 10.1 and it did not work. Although I have another imei, I have all my services running on the Stock 4.3. Now the only problem is that if I change to any other rom, does not connect to the wifi network.
I found something like this: http://forum.xda-developers.com/showthread.php?t=839367&page=4
But neither worked. Yesterday I tried to repartition the phone and almost killed. I spent two weeks looking for a solution, and tried them all, but did not work, I think I will draw on the last and the only thing I think work ... The box.
The octopus box (or similar).
KK roms are beautiful ... but no matter what, I have no wifi in another rom than the stock 4.3 lol.
Thank you for your contribution! as you say: I hope you serve someone else.
Click to expand...
Click to collapse
yeah thats some BS those signal and issues on the i9300.. they really did a number on that one.
sorry my thing didnt help, i too tried everything and got nothing.
Maybe try flashing CM 10.1.3 and changing those options in settings-> more, Might be that just flashing CM 10.1 wont do it, I did change something ther but cant remember what it was, i wrote in my post what someone else had ther in the options but i had different ones but I still changed one option there ( what i thought might be connected to the issue ).
anyway dude i feel you its crying shame whole thing, and so many are posting about these issues all the time, im kinda hating on samsung cause they always seem to mess up like that.
Hope you solve this somehow..
So the other day my S3 gave up the ghost, and developed the hard-brick "QHSUSB_DLOAD" error. I have insurance so I was overnighted a new phone, and am sending the old one away. I believe this was related to a long-term power button issue I was having, perhaps a virus, or something. I had not changed anything to the ROM I was using since about October, and the issue just happened now in May.
At any rate, the new S3 I received is an MJB version, Android 4.3, Knox and all that other good stuff. After several failed attempts, I found a method to root this phone and disable Knox. The Warranty Bit is already tripped, so clearly I'm not sending this phone back until it hard bricks as well. I am trying to install the StockMOD ROM that is very popular, however I am being plagued by problem after problem.
I was able to flash a version of CWM Recovery onto my phone, but it was too old and couldn't mount any of the folders. Using ROM Manager, I was able to flash an update to my Recovery, and now it mounts and views all folders properly. However, when I go to install the StockMOD ROM, I continuously get a Status 7 error, something about "expects 5 args, got 3." I wiped the data, cache, and Dalvik, but kept getting this error. So, I had to recover my backup of stock, which didn't go well either. Once my backup was installed, all of my apps kept crashing. Gapps, ROM Manager, everything kept giving me constant FC errors. I had to wipe my data, cache, and Dalvik again and go back to factory default, and reinitialize the phone. Luckily I haven't installed anything of importance on here yet.
A quick search through here states that I need to use TWRP as my Recovery. I've flashed TWRP several times, first using the 2.6... version and then the most recent 2.7.0.0 version, and neither of these will mount any of my folders. It just gives me a litany of errors trying to mount the various locations. I've done Fix Permissions and everything else, TWRP will just NOT mount anything. Other folks say I need the latest PhilZ Recovery. I've downloaded the latest PhilZ Touch 6 and flashed it via Odin. It is giving me the same errors as regular CWM, Status 7, "expecting 5 args, got 3."
I don't know what else to do. My S3 that ran Android 4.0 was so much easier. I had that thing rooted and running a TW based ROM with Nova launcher in about 30 minutes. This phone has been a disaster since I turned it on. I'm just trying to get a 4.3 TW based ROM. I like the Samsung Camera, Calendar, Clock, Messaging, and Contacts apps far better than AOSP versions. But I also want much more customization to my notification drawer toggles. Stock TW doesn't have the toggles I use frequently like the data toggle as well as the torch toggle.
I don't know what I'm doing wrong, because unlike a lot of folks out there, once I find a ROM I like, I stick with it. I'm not constantly updating, changing, or searching for the newest version of Android. There's nothing wrong with that, it just isn't my cup of tea. So does anyone know what I need to do? At this point, I'm about to just give up and use Nova over top of rooted stock TW and call it a day.
Thanks!
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
nosphor said:
Have you tried to go back stock rom using Odin ? I think it might resolve your recovery problem
Click to expand...
Click to collapse
Everything is stock except the recovery. I'm using CWM 6.0.4.7 with PhilZ Touch 6. I'm still using the stock TW 4.3 ROM that shipped with the phone. The only exception is that I'm rooted now.
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
nosphor said:
I suggest you to go back to a 4.1 official stock rom with odin to be sure to have no more issue.
This can help you : http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
Also, don't forget to backup your apps with titanium backup and all your sms :good:
Click to expand...
Click to collapse
Unfortunately, I've heard that it is not possible to revert to anything prior to 4.3 once a phone comes factory installed with 4.3, due to all of the security enhancements and etc. My kernel, modem, and baseband are all factory stock 4.3 MJB. Everyone else on the boards, under various other topics, warn of immediate and sudden death to the phone if you attempt to install a baseband prior to 4.3 MJB.
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
nosphor said:
I'm very surprised to hear that, because recently i've flash stock 4.3 rom and then go back to 4.1.2 to flash a 4.4 rom without any issue and i've got nothing for issues.
Maybe it depends on which country you are ( i'm from France ) ? For what i know , there is a VERY little chance that this downgrade cause dammage to your phone
Click to expand...
Click to collapse
I'm in the USA. The security features on the I747 US version are far different. I don't know how everyone else is succeeding. I am completely lost.
You are in the wrong forum, anything you try from here will hard brick your phone.
Sent from my GT-I9300 using Tapatalk
Sorry to tell you that, but what you say is not completely true.
Yes, there is a lot of people that rush to give an answer to the question, but there is also people that really like to help people that are in trouble :good:
Please, don't take most of the case for a generality
http://forum.xda-developers.com/showthread.php?t=1756338
Sent from my GT-I9300 using Tapatalk
Yes, i've read this, i know that, that's why i talk about the difference between country, different phone model
My apologies. Thought this was the 747 board. Go ahead and lock this, I'll repost in the correct forum.
Tried TWRP?