The title pretty much says it all. This has been going on for a while now, and it's starting to annoy me. Does anybody have a fix for this? I couldn't seem to get any of the fixes from other Galaxy S devices to work.
did you revert to stock from cm7?
SpaceToast7 said:
The title pretty much says it all. This has been going on for a while now, and it's starting to annoy me. Does anybody have a fix for this? I couldn't seem to get any of the fixes from other Galaxy S devices to work.
Click to expand...
Click to collapse
The only time I have seen this happen is when returning to stock from either the CM7 betas or any of the ROMs built off of it, and the reason for it is you lost your EFS data and unless you have a backup of that (CWM backups DO NOT have this backed up).
If you do indeed have an EFS backup then you can use Zaclimon's recovery thread and just add the EFS to that, that is the proper fix.
If you where a total newb like I was and completely lost it because you thought a CWM backup was enough, the only "temporary" fix is to flash Klin's IcyFusion, Han's Etheral or Dream Ultra then reboot into CWM recovery and "wipe data / factory reset" then reboot player, this will restore the boot menu and lockscreen for aslong as you run any of those ROM's but if you go back to stock it will vanish again.
Well, I somehow lost it when I wiped data on klin's klassic. A restore of data fixed it, and I haven't wiped my data since or gone back to stock so idk if it is still there.
Sent using Tapatalk
Thanks. I guess i will be using one of those roms you mentioned.
UPDATE: Ethereal did not fix EFS. As a matter of fact, it broke my home button.
SpaceToast7 said:
Thanks. I guess i will be using one of those roms you mentioned.
UPDATE: Ethereal did not fix EFS. As a matter of fact, it broke my home button.
Click to expand...
Click to collapse
Using Zaclimon's recovery method to go back to stock is the only way i've been able to fix the home button when Ethereal broke mine (this seams to be another side effect of losing the efs). restore to factory with zac's method thru heimdall (using a different usb port other then the one used for Odin) then Odin flash to Icy Fusion and Terrasilent kernel and follow previous instructions.
I did go back to stock rooted, and i think i will be staying there for the forseeable future because it seems that there arent any mature kernels or ROMs for this device - too unstable.
At any rate, am i correct in assuming that my EFS issues are related to (the abomination that is) TouchWiz, and that AOSP builds of Android do not have this issue? Ive never heard of this outside of Samsung devices.
Sent from my YP-G1 using xda app-developers app
SpaceToast7 said:
I did go back to stock rooted, and i think i will be staying there for the forseeable future because it seems that there arent any mature kernels or ROMs for this device - too unstable.
At any rate, am i correct in assuming that my EFS issues are related to (the abomination that is) TouchWiz, and that AOSP builds of Android do not have this issue? Ive never heard of this outside of Samsung devices.
Sent from my YP-G1 using xda app-developers app
Click to expand...
Click to collapse
I don't think so, what happened to me was I flashed one of the CM7 beta's and since they convert every partition from rfs to mtd it messed with my efs partition and so since I didn't have a backup of the EFS it was lost (CWM backups DO NOT backup the efs), from what I have gathered it holds your serial number and stuff like that which is why the deviceID hack implemented in Icy Fusion is able to "fill in the blanks" and that is what causes it to come back while on that ROM, I don't see how it can have anything to do with touchwiz, I use LauncherPro myself.
Icy Fusion and Dream Ultra are stable ROM's I haven't had any problems with them (other then Dream Ultra coming up in Russian after doing a wipe data/factory reset, but thats easy enough to fix) and the Terrasilent kernel is totally functional as long as you don't reboot into recovery on a ROM where you've converted all partitions to ext4, just load up a program like Tegrak or my choice of No Fills CPU tuner and change the governor to smartass V2. I couldn't conceive running stock at this point.
Hi i am very new to the concept of rooting and flashing ROMs.
My phone is a SGH-I777 unlocked running stock 2.3.4
I have tried rooting my phone using CWM 5.0.2.3 for i777 and then user superuser 2.3.3 to root which went fine.
Now i wanted to install a custom ROM so i went ahead and downloaded the CM 9 stable for my i777 and the gapps signed package saved them both to the internal memory went into recovery mode and followed instructions as per CM wiki to wipe cache wipe factory reset and then installed the CM 9 Stable and then the gapps package. When the phone rebooted CM9 was installed but unfortunaltely no gapps and i was not gettinng any network on my phone.I tried reflashing but no good hence went back to stock and everything seemed to be working fine.
All i want to know is did i follow the right procedure or is there something else which had to be done or needs to be done while flashing any new ROM. Also if anyone can suggest a good stable ROM for the i777 i personally i like CM 9,CM 10,AOKP SHOSTOCK & MYSTIC GLORY.
If anyone can be kind enough to help me on how to install the above mentioned ROMs if its a first time for someone.
Thanks
You can try rebooting again after initial boot. Sometimes that will clear up data/network issues. Also you can go into settings-->more--->mobile networks and check your APN settings. When there you can hit menu button, then restore default apn, and reboot.
Also you mentioned your phone is unlocked. Are you using it on another carrier other than ATT? If so, make sure your APN are correct for your carrier.
Your basic procedure is fine, theoretically, it should work.
Why gapp didn't work? I don't know, I haven't run CM ROMs.
Try reflash gapp? Try reboot?
Did u download the correct gapps? I've had it happen that my big old fingers hit the wrong gapps package for the base I was running (cm9 (ics), cm10 (jelly bean) or gingerbread. Everything u did sounds right in theory, make sure not to use rom manager.
Sent from Team Pirate Headquarters. AKA yer moms basement.
I've had it happen that I needed to reboot into recovery and flash just the gapps again. Try that. Don't try to reinstall cm and gapps. Just do the gapps again.
Sent from my SGH-I777 using xda premium
It has been a long time but I do remember when CM9 first came out for our phone I would flash the cm zip and let it try to boot. Then after a few minutes I would hold down the volume +/- and power until I was back in recovery and flash cm a second time BUT this time then flash gapps BEFORE rebooting. On occasion I have still done that out of old habits when I am switching between different ROMs. Good luck
Sent from My SGH-I777 Running Red Reaper Rom
Hello all,
I have this Vibrant I’m trying to get to run JB 4.1.2 or 4.1.1 I’ve tried 5 ROMS and none of them seem to find a network... When I go back to my Backed up Stock ROM I get network no problem. And yes I’m wiping both letting sit for 10 to 15 before first reboot.
You are either losing baseband, or losing your imei. I don't know why this happens to some people?? It can be fixed but you will have to fix after you flash the JB ROM of your choice. Because I don't know if its baseband alone, I have to assume its your imei. You need to backup your /efs folder. This might already be done. You can check by going to /sdcard/backup/efs, if you have efs folder in backup, you are good. If not you need to use a root file explorer app to copy /efs and put it on your /sdcard.
The efs folder holds important phone/network specific info including imei.
Once you get a JB ROM up and running,
Go to settings>about phone what is your Baseband-????
Check imei as well
If only baseband is missing just flash a modem
If imei is missing you will need to copy and paste the efs backup you created to the root of your phone and reboot. There are some more detailed guides on this.
I approve this message.
xXy3kXx said:
... When I go back to my Backed up Stock ROM I get network no problem ...
Click to expand...
Click to collapse
What do you flash after you odin back to stock? I lose IMEI, APN, &, baseband if I go directly from stock rom to JB.
What works for me is: stock » GB BL (optional) » update.zip » CM7 (vibrantmtd) » CM10 (optional, I only use the kernel to full wipe) » JB.
yosup said:
What do you flash after you odin back to stock? I lose IMEI, APN, &, baseband if I go directly from stock rom to JB.
What works for me is: stock » GB BL (optional) » update.zip » CM7 (vibrantmtd) » CM10 (optional, I only use the kernel to full wipe) » JB.
Click to expand...
Click to collapse
When was the last time you tried? The issue where going from a non/old Cwm recovery would break your efs was fixed a while back (with the assistance of a user who was kind enough to send me the rundown of why it was not restoring)
Although you may still need to flash again once in a new recovery.
Sent from my Galaxy Nexus using xda premium
FaultException said:
When was the last time you tried? The issue where going from a non/old Cwm recovery would break your efs was fixed a while back (with the assistance of a user who was kind enough to send me the rundown of why it was not restoring)
Although you may still need to flash again once in a new recovery.
Click to expand...
Click to collapse
FE, always spreading solid wisdom throughout the Vibrant forum. Really appreciate all you do for our ancient rigs.
As for the IMEI issue, it was from a crack-flashing & Odin session - ie. I was testing out whether I could jump from an Odin .tar straight to Semaphore kernel .tar then to Slim Bean. I should mention that my phone is one of those post-EU (Encryption Unsuccessful) ones, so it wouldn't surprise me if that alone plays a hearty role.
IIRC, I had tried the T959UVJFD, GBBOOT-T959UVJFD, and Bionix-FishmanMod_odin tar's ... but none of those roms would boot up on my phone after the flash. Again, most likely EU related.
I then flashed Eugene_2E_JK2_Froyo.tar (+ 512 pit). IMEI, APN, & Baseband all fine once booted. Then, Odin'd a Semaphore JB 2.4.0sv.tar (CWM 6.0.1.4), wiped, and then flashed Slim Bean 2.7.0 (4.1.2). Once booted, there was no APN or Baseband, and IMEI was now the generic one (004999...).
What eventually worked was Eugene .tar > GB BL's > update.zip (s15274n's CWM 2.5.1.2) > cm-7.2.0-vibrantmtd > CM10 nightly (kernel only to do a full wipe) > Slim Bean 2.7.0.
For some reason if I don't flash cm7.2.0 before jb...My phone is off and then plugged into the charger it will reboot, its not 'stay awake during charging,' its just a fluke on my phone.
No two vibrators are the same...
I approve this message.
I also have one Vibrant that has a very strange issue that it can't keep its bootloader and the only way to fix it was flashing the Eugene odin file. Even with the factory odin and updating to Froyo via Kies. The bootloader retains with cm7, cm10 and aokp, but with any other roms like Paranoid and SlimBean the bootloader gone missing, even if the modem.bin is still in /radio. Not sure why the Eugene odin fixed this issue.
Here's the link if anyone need it: http://d-h.st/users/Big%20Dog%20KMc
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