Problems with I777 wireless after Rom

[fifthmanstanding]

I am at my wits end and hopefully one of you can help.
The phone in question is is the AT&T Galaxy S2 SGH i777. It was running a jellybean ROM and there were problems with the GPS and google maps not working at all about four months ago. Not sure what happened. I went through the usual process of putting a ROM on the SD card, wiping cache/davlik and installing, then installing the gapp.apk for that rom. Everything was fine. Except wireless. Wireless would not connect. Just wouldn't do it. Googled forever, found no real solution. Thinking it was the rom I reinstalled. Wash rinse repeat. Same issue. Thinking it was a bad rom I proceeded to go through about six more roms. Same issue. Four hours later I resolved to unroot, take it back to stock. Took it back to stop with no issues. Wireless worked just fine. Everything was great. Rooted it again with the stock gingerbread. Wireless worked fine. Made a backup of the rom and was feeling lucky so I installed the Carbon ROM from the Sept 29th post on galaxys2root.com (I don't know if you guys allow linking here) and the gapps from that post. I boot. Everything is looking fine....yet the wireless doesn't work. This has been consistent across every rom I installed. I am quitting for the night.
It is currently running android 4.3, kernel version 3.064-CM-gbc8f4c9 (if that helps). The phone service is fine and makes/receives calls/texts just fine. No other blaring issues. Worth pointing out: all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect.

I had this phone for years (girlfriend has it now) and Rom'd it many times with next to no issues, especially not with wireless. I don't understand why it was working fine on a JB rom and trying to change rom suddenly screwed the wireless.
I am literally at my wits end and it's probably the result of me being an idiot somehow and missing something. Can anyone suggest a fix?
God bless in advance.

 

[cyril279]

[...]all roms in question came from galaxys2roms.com under the section for the AT&T i777 s2, so they should be compatible. Followed all directions/video ect. [...]Can anyone suggest a fix?
God bless in advance.

My advice is to avoid downloading ROMS from galaxys2root.com

If you want the insider scoop, keep up at xda or at each group's G+ community.

if you want:
-Carbon; get it from: http://download.carbon-rom.com/?dir=./i777/nightly
-Cyanogenmod; get it from http://download.cyanogenmod.org/?device=i777
-Omni; get it from http://dl.omnirom.org/i777/

The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)

Happy Flashing
-Cyril

 

[fifthmanstanding]

My advice is to avoid downloading ROMS from galaxys2root

If you want the insider scoop, keep up at xda or at each group's G+ community.

The installation is generally the same for all of them. Don't skip steps or take shortcuts.
flash:
-mr cooks rom wipe (good housekeeping is a must)
-chosen_ROM.zip
-Gapps (choose appropriately; only use 4.3 Gapps on 4.3 Firmware, etc)
-SuperSU (for Omni)

Happy Flashing
-Cyril

So would you suggest I revert back to the rooted gingerbread image and go from there?

I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?

 

[creepyncrawly]

So would you suggest I revert back to the rooted gingerbread image and go from there?

I mean are we attributing the lack of wireless to this particular Carbon rom? I mean I had the same problem with like 6 different roms which leads me ot believe maybe it's missing something like a wireless apk or something (im not even going to pretend I know what the term is ). The reason I say it is that if it's consistently an issue with the roms, it must be the roms lacking something the hardware needs to function right?

You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.

 

[fifthmanstanding]

You want to know if the problem is hardware related or firmware related. The test is to flash stock. You can flash any version of stock to find out, not just Gingerbread. UCMD8 will also give you a working wifi if the hardware is good.

Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.

Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.

 

[creepyncrawly]

Like I said I took it from what I think was a stock jellybean rom (where the wireless worked fine) and upgraded it to a kit kat rom and it stopped working, continued flashing roms with no success. Then flashed back to stock gingerbread and it was fine, then I rooted the stock gingerbread and it was fine. Then I took it to a non stock jellybean rom and the wireless didn't work. I mean I realize it's a lot of variables but if , consistently, I come from stock to a rom and wireless is not working, wouldn't that imply that the rom did not have something to support the wireless hardware? I had a similar problem years ago where I had to download a patch for the baseband to work after ATT changed the baseband. I was thinking maybe this was a similar problem where I could patch the wireless firmware with something to make it work. It just seems odd that like 6+ roms consistently left the wireless not working. And by not working I mean I can turn it on and off, see the available connections broadcast, see my network, put in my wireless pass word and it either suddenly shows as 'out of range' or will not connect to it at all.

Where would I find stock versions of rooted roms (jellybean or higher) for this phone. I didn't have much luck on google looking for stock.

There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.

Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.

And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.

 

[fifthmanstanding]

There is a working link to stock UCMD8, 4.1.2 in the Download Repository. It is said to be easy to root with Framaroot using the Aragorn exploit.

Cooked rom is based on UCMD8, deodexed, debloated, rooted with busybox.

And yes, it sounds like the roms are missing a compatible driver. Have you looked and asked about the issue in the rom threads. If there are not other people experiencing the same thing, then you need to look elsewhere for the reason and solution.

I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums

 

[cyril279]

I apologize but where is the download repository, I'm not seeing it anywhere http://forum.xda-developers.com/galaxy-s2-att#subForums

hint: http://forum.xda-developers.com/member.php?u=2916435

 

[fifthmanstanding]

hint: http://forum.xda-developers.com/member.php?u=2916435

Yeah I'm an idiot. I literally just saw that in the signature.

So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here

http://forum.xda-developers.com/showthread.php?t=2130276

and run it?

 

[cyril279]

We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.

Yeah I'm an idiot. I literally just saw that in the signature.

So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here

http://forum.xda-developers.com/showthread.php?t=2130276

and run it?

 

[fifthmanstanding]

We understand that you're in a hurry to get the device fixed, but please take the time to read through one of creepy's links, or one of the many guides that explain the steps that you are about to take. Rushing it can make a worse mess of the device.

I agree.

Which links?

I read through the notes on the repository:

There is always some risk involved when flashing bootloaders and Param.lfs. Please don't flash this unless you absolutely need to.

"This is the complete stock UCMD8 Binaries downloaded from samfirmware at sammobile.com. Please note, this package contains boot.bin, sbl.bin and param.lfs, plus cache.img, factoryfs.img, hidden.img, modem.bin and zImage.I777UCMD8 Full Odin Flashable tar: I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5.7z 427.02 MB (Contains I777UCMD8_I777ATTMD8_I777UCMD8_HOME.tar.md5)
(MD5: 307cc8fcbb8f220d3ae75d387569da40)"

And I'm downloading the file now. I've used odin before so I assume that goes by the standard process ( download mode, open, pda, select file, hit start, wait, finish) and then I went here http://forum.xda-developers.com/showthread.php?t=2130276 and he says "Version 1.3: Add Aragorn and Legolas exploits" so I assume based on Creepy's previous statement that's the one I need. I would download the apk and run it.

What am I missing?

 

[fifthmanstanding]

Yeah I just installed the tar file using odin and before I even get to rooting process, wireless isn't working. This time it sees the network, password goes in as usual, it attempts to obtain IP address and says that forever. Never connects. Then goes back to scanning. Then attempts to connect again. No dice. No other device in the home has this issue. I'm out of ideas.

Edit:

Yeah I just tried again, using odin, took it back to stock, wireless works, using odin took it to stock with root, wireless works, using the tar file located here http://forum.xda-developers.com/showpost.php?p=20229527&postcount=46 took it to I777UCMD8 Stock Binary. Wireless is not working.

Does anyone have any insight? I've got a pissed off girlfriend an a perment dent in my desk from my head.

 

[fifthmanstanding]

update: took it back to i777 UCMD8 with odin, just for kicks I tethered it to my nexus 4. Works fine. Turned off data, disconnected the wireless just to be sure. Turned it back on. Working fine. Still will not connect to my router. This would imply there is a router issue and I have less knowledge of how/why that would work. Thoughts?

 

[creepyncrawly]

So I download this as a tar file, run it like the usual Odin fare and then download framaroot v 1.3 from here

http://forum.xda-developers.com/showthread.php?t=2130276

and run it?

The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.

I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.

Edit: Failed to click on the latest page of the thread before I posted this. Yes, it sounds like an issue with your router, perhaps. So find other routers and test the wifi. If that's the issue, then the other roms will probably also work on a different router.

 

[fifthmanstanding]

The file downloads as a 7z. Extract the .tar.md5 and put that in the PDA slot in Odin. Odin3 v1.85 is preferred for this phone, but the other versions usually work. There is a working link for the Odin download at the top of the page in the Download Repository. If you are unfamiliar with Odin, I can post more detailed instructions.

I am not personally familiar with Framaroot. It is an apk, so install on your phone and go.

Yeah I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.

This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.

The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?

At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.

Any thoughts?

EDITosted before I saw your edit

 

[creepyncrawly]

Yeah as stated, I'm familiar with odin. I've been using v 1.85. See above posts. UCMD 8 did not work. I have reflashed UCMD8 for the third time.

This third time followed the same as previously but for some reason wireless works all the way around. So that's progress.

The problem I'm having now is that I don't believe Framaroot is working. I followed the instructions and used the Aragorn exploit. It installed the SU app and it verifies that root is there. I downloaded rootchecker just to be sure. It verifies that root is there. I tried to boot into recovery to make a backup of the current state. It goes to stock android system recover. So I downloaded the clockwork mod recovery tar file. Ran odin with the CWM tar file, failed. For no apparent reason. I tried shutting it off, putting it back in odin mode, running the tar file again. Same issue. I took an alternative approach by downloading CWM Rom manager and tried installing CWM Recovery the the CWM Rom Manager app, it downloaded, requested SU permission, granted, installed and required reboot. Rebooted. Now if I try to boot into recovery (power off, power button +up/down buttons) it still boots into android system recovery stock mode. If I boot it, go to ROM Manager and tell it to boot into recovery mode it boots into CWM Recovery Mode with no issue. But CWM Recovery is not accessible through power+volume up/down buttons. Why is that?

At this point I want to get CWM Recovery to work, make a backup of current state and then push forward to getting this thing on a Jellybean rom because stock JP with touchwiz and the samsung nonsense and ATT Bloatware is horrd.

Any thoughts?

Apparently you are moving too fast, with too little information.

On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.

To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.

 

[fifthmanstanding]

Apparently you are moving too fast, with too little information.

On this phone, recovery is compiled with the kernel, and they are installed as one unit. You will not successfully install a separate recovery. Also, rom manager has been know to cause issues on this phone, and should be avoided. There is a sticky about this at the top of the forum.

To get recovery you need to install a custom kernel. For UCMD8, that would be AJK v4.9 no swap. Someone said yesterday that the download didn't install for them. Don't know if they checked md5 on the download or not. I'd start with a download from the AJK thread and see if you can install it. You will use Mobile Odin lite or Mobile Odin pro on your phone to install the kernel. You will have to extract the boot.img from the CWM flashable zip and use that in Mobile Odin.

Fair enough.
I've downloaded the AJK no swap from here http://forum.xda-developers.com/showthread.php?t=2110542
I've downloaded Mobile Odin lite and am going to work on that.

Assuming it all works out and I get to make a backup. Where to next? This rom is terrible. What do you recommend for a jellybean experience as stock nexus 4 as possible.

 

[fifthmanstanding]

Yeah the ajk no swap 4.9 is giving me a consistent java error that kills the download. I attempted to move it to the sd card and open in odin lite but am not seeing it on the card. Am I doing something wrong?

Edit. I tried connecting the phone to the computer and opening in explorer, following directions from here http://forum.xda-developers.com/showthread.php?t=2197157 , created a folder and attempted to drop the zip in there and it's not letting me drop files to the phone. nor to the sd card.

Edit 2: suddenly file xfer is working again. I dropped the .zip to the new folder on the internal and also created a new folder with the boot, METAINF folder and system folder that shows when you unzip. It's not detecting the zip file so I assume you're supposed to select the Boot file. I select it. Nothing happens.

Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?

 

[creepyncrawly]

Edit 3: looks like the actual download contains a boot disc image file. nothing md5. I'm assuming that's why when I click it it won't do anything. Any ideas?

Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.

If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.

Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.

 

[fifthmanstanding]

Open the AJK 4.9 ns zip file with an archiving program such as win zip, 7 zip, etc. You will see one file and two directories. The file is boot.img. Extract that and flash it in Mobile Odin. Ignore the directories.

If you were going to want to use AJK with UCMD8, you would then enter recovery and flash the full AJK 4.9 no swap zip file in CWM.

Otherwise, enter recovery and flash the firmware of your choice. For Samsung firmware based on touchwiz, I suggest SHOstock3 v4.0. It's still actively supported. I don't use AOSP based firmware so can't make any suggestions there. There's lots of info in the development forum.

Ok by the looks of it that worked. Thanks for that.

In terms of roms I'm looking for something stable, jelly bean and non-touchwiz. As close to possible as nexus 4's jelly bean. Nothing comes to mind?

Edit: apparently the home key now no longer works properly, hitt it brings up a selection box and selects whatever is the left most side whether it's 'apps' tab or an icon on the home screen. Also the search magnifying glass soft key doesn't work, same function as the home key it seems.

Edit 2: And the wireless is no longer working. Was working fine before flashing the kernel. Put the phone directly on top of the router. It shows the network, allows for password input, says 'connecting' and never ever connects. Then it drops and goes to 'out of range'...sitting directly on the router. Just for kicks, like last time, I enabled the hotspot on my N4 and it connected fine. I attempted to connect to the router again and it does the same...connecting and drops to out of range. Sigh.