Related
I'm fairly new to ROMs (this is my second). I have followed the instructions and successfully installed the ROM, modem, and update.
2 questions:
1) Wifi does not work (will not turn on). I had wifi problems on my last ROM. I have reinstalled this ROM numerous times today thinking something must have failed since wifi does not work. This seems to be unique to me since I can't find anything in the thread regarding wifi problems. Any suggestions?
I've gone so far as to use darkside superwipe as suggested in a different thread. Still can't get wifi to turn on (just sits with "Turning Wi-Fi on..." message on screen). Never errors out, just stays like that.
2) ROM Manager: Fix permissions fails. I get the following error when I select fix permissions: "An error occurred while attempting to run privileged commands!" Any suggestions?
Thanks so much for the help!
You should post your question in the ROM thread. The developer (seanscreamz) or one of the other testers will see it and be able to address your problem and help you out.
I can't post in the Dev section yet. 6 more posts and I will ask there.
starting over...
Ok, I figured I might as well make sure that my wifi woes are not a hardware issue. I've reverted back to stock Skyrocket OS to make sure wifi is available and working in stock form.
Following this link http://forum.xda-developers.com/showthread.php?t=1342348, I reverted to stock and I can confirm that wifi works in stock form.
I've also reformatted my sd card in case there is any chance a corruption on it would cause my problems.
Now going to reinstall SkyICS...
bored4long said:
Ok, I figured I might as well make sure that my wifi woes are not a hardware issue. I've reverted back to stock Skyrocket OS to make sure wifi is available and working in stock form.
Following this link http://forum.xda-developers.com/showthread.php?t=1342348, I reverted to stock and I can confirm that wifi works in stock form.
I've also reformatted my sd card in case there is any chance a corruption on it would cause my problems.
Now going to reinstall SkyICS...
Click to expand...
Click to collapse
Are you on CWM touch?
have you went into the busybox app and clicked install?
wifi broken again
I have followed these instructions here http://forum.xda-developers.com/showthread.php?t=1321582 to regain root. After getting root, I installed ROM Manager and selected "Fix Permissions". On reboot, I lost the ability to connect via wifi.
Did I miss a step?
Thanks again for holding a n00b's hand!
AT&T Samsung Galaxy S II Skyrocket Android Development
http://forum.xda-developers.com/forumdisplay.php?f=1383
You have to install busy box
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
john: I'm sure you mean well, but I don't know what your intent was with your posted link.
crazyD: digging your avatar. I'm currently trying to decide between a G26 and XD9sc...
btw, installed and ran busybox. not sure what it did for me. I also updated ROM manager to latest. Accidentally initiated a backup from ROM manager. Will see if wifi is back after that has completed.
Edit: wifi still errors, won't connect. I'm not clear what steps I may have missed or screwed up between being stock to rooted. I will revert back to stock again and try again...
Are you running juice defender? Its giving me problems with my wifi connection!
Sent from my SAMSUNG-SGH-I727 using xda premium
I'm not running Juice Defender. At this point, I'm trying to revert back to stock form again with working wifi.
Edit: ok, reverted back to stock by doing the following
1) reboot into CWM recovery
2) factory reset x3
3) clear cache x3
4) format system x3
5) clear dalvik x3
6) format emmc x3
7) restart and pull battery
8) boot into download mode
9) push stock tar (k0kane) via Odin3 v1.85
I now have wifi again!
So now I get to try to get back to SU and CWM without losing wifi...wish me luck.
still have wifi!
OK, rooted and CWM installed. I still have wifi, which is good. I'm afraid to select 'Fix Permissions' for fear that will break my wifi.
I'm going to install Sky ICS now and see what happens.
sky ics and wifi!
OK, It took a few attempts, but I now have SKY ICS installed and wifi is still working.
I've installed the base ROM and the modem...not the updated yet. My download speeds are terrible, but at least I have wifi. I think the data speeds get better on the update.
Sean's instructions say to let the phone "cache and settle". I have no idea what that means...so will try to wait 10 minutes or so before installing the update.
bored4long said:
OK, It took a few attempts, but I now have SKY ICS installed and wifi is still working.
I've installed the base ROM and the modem...not the updated yet. My download speeds are terrible, but at least I have wifi. I think the data speeds get better on the update.
Sean's instructions say to let the phone "cache and settle". I have no idea what that means...so will try to wait 10 minutes or so before installing the update.
Click to expand...
Click to collapse
My uneducated guess with the data speeds is the modem for UCLE2. I haven't had the chance to go to LTE on SKYICS yet, but data is definitely slower on "4g" networks.
Sent from my cm_tenderloin using Tapatalk 2
quick update
Here is a quick update:
I spent some time redownloading all my apps and in general setting up the phone. I then ran the SKY-ICS update. Everything seemed to be working great.
As an added bonus, the email app in SKY-ICS syncs with my employer's exchange server! Which is so awesome. The stock ROM, and the last gingerbread ROM I had on the Skyrocket would not connect to our exchange server. I was very pleasantly surprised by that functionality.
I then lost wifi again. Wifi seems to be unpredictable and I'm not sure if it is hardware or software related. I again have wifi this morning, but didn't for the last two days. Also, my phone won't restart, it appears to get stuck in a powerdown state.The haptic buttons stay lit, but the screen is blank. I have to pull the battery to get it to restart.
But overall, I'm very happy with the performance and functionality of SKY-ICS. I will do some digging on the restart problem.
It started I think after I put the 1st JB TW ROM on my phone (eg Incubus). Since then, every time I try out any AOSP/AOKP based ROM I lose WiFi.
Wipe and format everything (data, cache, dalvik). Install AOSP/AOKP ROM, do the initial setup, get WiFi working and then after 1st reboot -> no WiFi. I tried many ROMs based on the above platform. Same thing.
If I toggle the wifi on/off/on some times I get the wifi back but just until the next reboot. Sometimes when I try to toggle the wifi screen freezes.
I odined back to stock. Unrooted and locked. I rooted and unlocked and right away I reinstalled a CM10. Same problem.
When that happens there is no wifi network found and scan finds nothing (i have many netorks around me). It is like the wifi service is not present.
I tried different kernels and different radios. No go.
All the TW stock ROMs (ICS or JB) work fine.
Any idea? Did you hear about this anywhere?
Thanks for your help.
jb_alphamale said:
It started I think after I put the 1st JB TW ROM on my phone (eg Incubus). Since then, every time I try out any AOSP/AOKP based ROM I lose WiFi.
Wipe and format everything (data, cache, dalvik). Install AOSP/AOKP ROM, do the initial setup, get WiFi working and then after 1st reboot -> no WiFi. I tried many ROMs based on the above platform. Same thing.
If I toggle the wifi on/off/on some times I get the wifi back but just until the next reboot. Sometimes when I try to toggle the wifi screen freezes.
I odined back to stock. Unrooted and locked. I rooted and unlocked and right away I reinstalled a CM10. Same problem.
When that happens there is no wifi network found and scan finds nothing (i have many netorks around me). It is like the wifi service is not present.
I tried different kernels and different radios. No go.
All the TW stock ROMs (ICS or JB) work fine.
Any idea? Did you hear about this anywhere?
Thanks for your help.
Click to expand...
Click to collapse
its gonna sound stupid but just make sure your bootloader is unlocked
KennyCap said:
its gonna sound stupid but just make sure your bootloader is unlocked
Click to expand...
Click to collapse
The phone wouldn't boot into the rom if they were rooted but had a locked bootloader.
Sent from my SCH-I535 using xda app-developers app
jb_alphamale said:
It started I think after I put the 1st JB TW ROM on my phone (eg Incubus). Since then, every time I try out any AOSP/AOKP based ROM I lose WiFi.
Wipe and format everything (data, cache, dalvik). Install AOSP/AOKP ROM, do the initial setup, get WiFi working and then after 1st reboot -> no WiFi. I tried many ROMs based on the above platform. Same thing.
If I toggle the wifi on/off/on some times I get the wifi back but just until the next reboot. Sometimes when I try to toggle the wifi screen freezes.
I odined back to stock. Unrooted and locked. I rooted and unlocked and right away I reinstalled a CM10. Same problem.
When that happens there is no wifi network found and scan finds nothing (i have many netorks around me). It is like the wifi service is not present.
I tried different kernels and different radios. No go.
All the TW stock ROMs (ICS or JB) work fine.
Any idea? Did you hear about this anywhere?
Thanks for your help.
Click to expand...
Click to collapse
Try wiping System before flashing AOKP as well. Wipe them a few times just to be sure. Im thinking that possibly recovery doesnt always wipe like it should but im not sure.
I did it.I tried too many times not to get it right at least 1 time.
Sent from my SCH-I535 using Tapatalk 2
have you tried the official cm10 m1 release?
I tried the last CM10 from Sep the 23 rd.I don't know which version is that.
Sent from my SCH-I535 using Tapatalk 2
Well, I have news. Problem not solved but something new came up.
I had a nand of an official cm10 from Sep the 9th. I recovered and voila the wifi works perfect. More than that. I dirty flashed the nightlie from today and everything works fine
I then wiped and format again everything and flashed the CM10 from today. WiFi lost again after 1-3 reboots.
By the way if I reboot after losing wifi next time I get a screen with activating which stays there forever. Also my phone no and MIN are gone.
I recovered them but the wifi is still gone.
I live in Ca so I'm in roaming if this is of some importancce.
Can somebody mimic this? Fresh install of CM10 official and then reboot.
It does the same for me for any AOSP AOKP JB based.
I have a netgear router that provides wifi service on 2.4 and 5 Ghz on both bands 20 and 40 Mhz. The SSIDs have different names.
I specified already that when that happen I cannot see any other wifi around me and there are many.
So I'm totally at a loss of where to go or what to even search for.
I have a verizon Galaxy s3 that I rooted and unlocked the bootloader on. I flashed a couple ROMs and now it won't connect to the network. It tells me it is in roaming mode only. I called verizon, but they said to just return the phone because it won't talk to their network.
I've read some things about "triangle away" and I kind of tried that. But it kept telling me that my flash count was 0 anyway. So it didn't do anything.
My IMEI and ICCID are correct to my sim card and phone. I originally flashed CM10 for the verizon s3 and it worked great for a few weeks. Then I tried a couple others and they worked also. Then I flashed the euroskank ROM, and that's when it no longer would connect. I went back to a previous nandroid, and still no connecting.
I don't know what the problem is, or what to search for, or where to go.
Should I try to install a stock rom. I know I keep seeing things about odin and installing the stock rom. Should I do that? That's something I haven't tried yet.
So, I tried reprovisioning the phone with *2767*3855#
And when I did that, it said sorry, your phone is not yet activated.
But I know it is, or, at least was activated. And when I call verizon they tell me it has been activated already. I don't know what to do. I'm thinking of trying to go back to stock
Same Problem
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
SpencePatriot said:
Flashed CM10.1 nightly just to test it out and then boom, no more connection. On any ROM. Scariest part? I have gone through the restore process and am now back to an unrooted phone with out of the box firmware. I believe I will take it back to Verizon now and see if they will give me a new one.
Click to expand...
Click to collapse
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
sin 7227 said:
I also flashed a cm 10.1 Nightly this one to be more specific http://forum.xda-developers.com/showthread.php?t=1843628 and it caused me to not be able to make any phone calls. I tried what you did and it worked and just to make sure that it was that rom causing problems i rooted and flashed it again and it happend again.
Click to expand...
Click to collapse
Well that's good to know that you got it back working again. Sounds like it might be just be the ROM and not anything weird that we did to cause the loss of connectivity.
Thanks nertskull
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Input
halfgod85 said:
Thanks nertskull, I had this problem after trying to downgrade from CM10.1 to CM10 and was stuck. I tried so many different methods and nothing worked until this one, thanks so much!
Click to expand...
Click to collapse
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the Cyanogenmod update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Mitch90 said:
I had the an issue with my phone stuck roaming and this method worked great! Only problem I came across was trying to run Samsungs update for Jelly Bean, Every time I attempted to update my phone would crash and go back to ICS. Luckily I had a back up so I wiped my phone, restored from my previous backup (which had Jelly Bean) and worked without roaming issues!
My input is if your having roaming issues is to use a backup you made before you had the roaming issue. Follow this tutorial above to get your phone back to stock, root your phone, then restore from your backup through CWM or whatever you are using.
I am not too sure what causes the roaming issue but I did notice while looking for networks, my phone found ATT ad TMobile haha.I am assuming what happened was that the CM update I was downloading automatically was set for another carry which changed my wireless settings. I will be downloading nightly's manually for now on lol
Thanks for this fix, Saved me a lot of time and aggression
Click to expand...
Click to collapse
My S3 is having the same issue after a CM10 modification. Reflashing to a stock ROM fails, wiping and reflashing fails, trying a different rom on cwm fails, no backups to flash to (all result in error). So I stumbled upon this thread, read about reprovisioning, and I took it to mean input the numeric code into the phone dialer. I did that, and nothing happened. Can anyone provide insight on reprovision and how to do it? Google search on reprovision isn't giving me any hints.
If the reprovision is just failing and I've been doing it right, does anyone have any other suggestions? Really hoping my phone isn't soft-bricked with no ability to call/text.
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Darthbull said:
I know this is a few weeks old, but I have to say thank you for this. It worked perfectly for me, and rather than wait 48 hours for Verizon tech support to call me back, I was able to solve my own problem. Thank you, again.
Click to expand...
Click to collapse
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
stuck...
I tried all the above, stock, radios, kernels, codes, ##RTN#, none of it works, my radio works cause i tried 911 and it jumped on roaming and began to make call at which point of course i hung up before letting it connect any words of wisdom... at this point just a tablet for wifi
stang68x said:
Hey guys, when you provision does it wipe the entire phone, including the SD card? (internal SD card and external SD card)
Click to expand...
Click to collapse
Bump
no sd wipe
stang68x said:
Bump
Click to expand...
Click to collapse
neither *2767*3855# nor ##786# wipe sd card, files on sd card stay intact
I have a galaxy note 2 on Verizon. This used to happen to me on CM 10.1 first stages but issue got fixed as the nightlies started. It only happened to me when I sometimes rebooted the phone or when the battery completely drained from 100-0% then when I would charge it and boot the phone it would show me an x and no signal bars. I would have to restore to a TW rom to get it to activate again but going into settings and switching to CDMA/LTE mode. Now I'm on ParanoidAndroid 2.99beta ROM and it still gives me that issue. Hopefully soon it will be fixed.:fingers-crossed:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
This worked for me after trying everything else. I wish I found this 4 hours ago.
wwonka69 said:
This worked for me after trying everything else. I wish I found this 4 hours ago.
Click to expand...
Click to collapse
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
wwonka69 said:
Spoke too soon. I wanted to try Miui and backed up and then installe miui but it was flaky so I tried wiping and then restoring but Now I have the No radio problem back.
Even after I restore to a clean install I still get this issue.
Click to expand...
Click to collapse
Ok it only works if you are on 4.04 as far as I can tell.
bump:good:
nertskull said:
So I don't know if we have the same issue or not. But I got mine working for now. Don't know if I'll run into problems later, but this is how I got it working right now.
First, I installed back to stock settings and radio. I followed the instructions in this post
http://forum.xda-developers.com/showthread.php?t=1762709
I did the stuff in section 5. Including Flashing a Stock Radio. So I went back to the VRALG1 4.0.4 ROM.
And I did the I535VRLHE radio.
But it still didn't work. BUT, once in stock settings, I did the reprovisioning.
*2767*3855#
And then that finally worked, it went through, and my phone activated. So it works now. Hooray!
But I REALLY really want to know what happened. So I can avoid this happening again in the future. Can anyone tell me what happened, and why this fixed it? And how to prevent it happening again as a flash more ROMs in the future?
Also, SpecePatriot, let me know if that works for you. It'd be good to have more than one source to know that works.
Click to expand...
Click to collapse
Thank you buddy,
This helped me get my phone back in working order -- For those of you wondering why the "*2767*3855# is not working is because you are using the wrong flash. You must use "Official VRALG1 4.0.4" - and currently the link is down on the thread - I just googled it and found it elsewhere. I tried one of the other OTA's and it would not work. Also, do exactly as netskull described - even regarding the antenna. When using VRALG1 4.04 - The second i entered the last "hashtag (#)" it popped up another screen which helped get my phone working. I did not have to press send or anything. Kind of sucks that I lost all data on my internal card, but I DID back it up and now I will have to go through and restore. Since some people were wondering -- It did not mess with anything on the external card... It did unroot my device, however, so I will have to do that again as well.
For some reason, flashing the latest MIUI messed up my phone and put it in roaming all the time. Oh well, happy i got it working, and subscribed . Thanks once again Nertskull.
I was running slim 4.2.1 for quite some time with no problems, i loved it. I flashed 4.2.2 and my phone got stuck in NV and my phone number would come up as 000-000-3370. On first boot everything seems to be fine except that i get an error when i try to open up the play store. On my next boot is when I would see these problems. I tried everything from dirty flashing from a working 4.2.1 rom to completely formatting everything, even my external sd, and the same thing happens. This happens with every 4.2.2 rom out there. When i reboot i get stuck on the activating screen and my phone will get stuck in NV and ruim/sim wont stick no matter what i do. i don't know what else to do. someone please help!
It isn't a rom issue it is an S 3 issue that randomly occurs when flashing ROMs. You will have to flash the stock rom and reprovision your phone. I know because it has happened to me twice and both times it was with a Touchwiz ROM. You should have backed up your IMEI just in case this happens.
my imei is backed up. but why is it only 4.2.2 roms that do this?
I was able to flash back to a 4.2.1 Rom, namely pure Google for now, with no problems. but when I flash any 4.2.2 Rom the same thing happens.
All 4.2 ROMs used to do this to me.
However.
Only also happened when I flashed miui.
Now I run liquid smooth and haven't had the problem since.
sent from that young galaxy.
God bless the American people!
do u guys think I should Odin back to stock, then root, unlock, and try to flash 4.2.2?
Actually, there is an easier way
I have had this happen numerous times and it lef me to mess with my phone a little bit. I originally thought that setting it to CDMA/SIM and then rebooting would fix the problem, but I found a simpler solution to that. The last time I encountered the problem I simply set the phone to RUIM/SIM under mobile networks and then Turned on airplane mode for a few seconds then turned it off and I found my number under phone settings and everything. Try that and let me know how it goes.
Edit: Sorry, the term is RUIM/SIM, not CDMA/SIM. My bad.
hmmm, I'll definitely give that a shot later on tonight.
well I tried it, it works. but only temporarily. once I reboot it reverts back to how it was. any other thoughts?
anyone?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
try this. i had the same problem. http://forum.xda-developers.com/showpost.php?p=35600769&postcount=2
nope, none of that works either. no matter what I do ruim/sim will not stick on a reboot on any 4.2.2 Rom. I'm really getting frustrated with this.
no one has any other solutions for me?
Chitala383 said:
anyone?
Click to expand...
Click to collapse
Does your phone display an IMEI number?
Settings->About->Status
Don't need the number, just to know if you have it there....
Also do you still have Root/Unlocked bootloader?
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Chitala383 said:
yes, i have an imei. i lost it once before so now its backed up, i'll never make that mistake again. it was a nightmare trying to get it back. and yes, i am rooted and unlocked.
Click to expand...
Click to collapse
Have you done a complete factory restore through Odin? You would lose root and unlocked bootloader, but it may be faster to restore to stock, and reroot/mod than to try to find an "easy" fix. I was having some issues the other day in between a few ROM's, but I just factory restored, and restarted from "scratch". Now I am running perfect.
You may have already tried, but on page 1 you asked if you should, and I did not see a confirmation you did so.
Had the same problem... And yes, the phone must be reprovisioned. Although sometimes you can just adjust the network settings and change it from NV. That worked for me also.
Sent from my SCH-I535 using Tapatalk 2
I flashed root 66 via Odin, bootloop. flashed the ma2 stock image, bootloop. then flashed the lk3 stock image with success. but still with the same results as before.
tomorrow I'll try flashing g1 and start from scratch there. what do u guys think?
well, I odin'd back to bone stock G1, rooted with rootdebugfs, flashed cwm with ez recovery, unlocked my bootloader with ez unlock, flashed liquidsmooth 4.2.2 rc2 and guess what. same ****!!!!!!!!!!!!! i'm really getting fed up with this. someone has to have a solution to this cuz this is really pissing me off.
Hi Everyone,
On my TF300T I am running the 4.2 bootloader, I have put TWRP 2.5 recovery on and it is working perfectly. The only issue is that on the two custom roms I have tried (Unofficial CM10.1, CROMi-Xenogenesis 4.6.4) my wifi won't turn on, I have flashed back to stock and the wifi works again. I have tried a couple of kernels on CROMi but that didn't help. I have tried searching but I couldn't find any useful results, what I am missing?
Cheers,
Wipe
jezzam said:
Hi Everyone,
On my TF300T I am running the 4.2 bootloader, I have put TWRP 2.5 recovery on and it is working perfectly. The only issue is that on the two custom roms I have tried (Unofficial CM10.1, CROMi-Xenogenesis 4.6.4) my wifi won't turn on, I have flashed back to stock and the wifi works again. I have tried a couple of kernels on CROMi but that didn't help. I have tried searching but I couldn't find any useful results, what I am missing?
Cheers,
Click to expand...
Click to collapse
I had this same issue when I first tried CROMI-X. I reflashed doing a full wipe (data, system, factory reset, and caches) and everything worked great. It is slightly more time consuming since you have to reinstall all of your custom apps. Also be sure to make a backup of all data and personal files on an sd card.
Once I had the custom ROM installed, I didn't have to do the full wipe for any later updates, only the caches.
Ok I reflashed after doing a wipe of data, caches, and system, then a factory reset. Still no wifi, it just won't turn on, it gets stuck at 'Turning Wi-Fi on..." and eventually times out and the switch goes back to off.
Any other ideas?
Bluetooth works so I have been able to tether through my nexus 4, no wifi is pretty annoying.
Figured it out, had encrypted my tablet, decrypted by going back to stock rom and recovery and then doing a factory reset. Now all is working fine.
Good deal!
jezzam said:
Figured it out, had encrypted my tablet, decrypted by going back to stock rom and recovery and then doing a factory reset. Now all is working fine.
Click to expand...
Click to collapse
Glad to hear you got it figured out. I will make a note of this for future reference should somebody else have the same problem.