I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Nandroid backup didn't work?
And what problems are you having with gapps?
Me myself have problems in CM7 as well -> the gapps cannot be installed (well, CWM didn't mention any error when installing) but after boot up no gapps is there, after tons of research here and no solution too, and I rolled back to froyo.
Barfaroo said:
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Click to expand...
Click to collapse
CM7 working fine on my HD2. I'm running it from my SD though because I don't want to root.
From what I understand the GPS will not be fixed by a cm update its got something to do with the hardware you have to do http://forum.xda-developers.com/showpost.php?p=11853529&postcount=2085 this to fix it. After I did the gpsclr fix mine has worked flawlessly. Also I don't think its only cm roms that have this issue.
Sent from my PC36100 using XDA Premium App
ah i mistook gps for gapps. my mistake... lol
Odd... CM7 works perfectly on my Motorola Droid and Nook Color and I've also never had a GPS problem (even on older nightlies). What make and model is your phone? And are you running off a CM7 nightly (if so what build?) or an RC (the latest is RC4 as far as I know)?
Gps worked perfectly using Froyo (rooted, ROM from AddictiveTips). I have an HTC Desire (CDMA) from US Celular. No, I'm not running off nightlies. I installed CM7 RC4.
The fix suggested above sounds like I would have to first flash a sense ROM and then come back to CM7. Other than giving me extra space for apps, it isn't worth it. I could get by with Froyo since everything worked with it. With CM7, the gps doesn't work at all. Maps keeps searching for satellites and never finds them. I really miss not having voice directions.
Barfaroo said:
I wish I had known before flashing CM7 that many have had problems with the gps. I certainly do. I tried using my nandroid backup to go back to the Froyo ROM I had flashed from AddictiveTips, but backup and restore on ClockworkMod just leaves me with a blank screen. I've seen some tips on fixing gps, but most involving going back to a sense ROM and starting over. I'm not a computer whiz and some suggestions are hard to follow. I tried one involving Fast Reboot and Faster Fix, but it didn't work. Since ClockworkMod's restore won't work, I have to either wait for the CM7 gps problem to be fixed later or try re-installing the Froyo ROM from the SD card (which may or may not work). The gps with Froyo worked great. Any suggestions?
Click to expand...
Click to collapse
all you need to do>
get a fresh rom myns or any that you like in reality it doesnt have to be sense if you just want to get away from cm7 altogether
but then boot into cm7,
plug it into your computer
load the new rom onto your phone
boot into recovery
then install the new rom.
sound good?
I appreciate the suggestions, but I decided to go back to Froyo and my gps is working again! Unfortunately, Clockworkmod won't let me re-install any backups, and I have no idea why. All I get is a blank screen. Fortunately, I can install from the SD card, which I did to get Froyo back. Since nandroid backups don't seem to work, I have to setup my phone from scratch everytime I make a ROM change.
Related
Hey guys, ran into a problem, I was able to root mytouch 3g and installed
http://forum.xda-developers.com/showthread.php?t=538633 3.6.8 release 4. Problem is when the phone goes sleepmode (screen turns black) after you wake it up the screen turns fuzzy/blurry. Is there an easy solution to this problem? or should I install a different ROM? Any suggestions? I really like this rom besides the blurry screen issue.
thanks for any help!
Hey same thing is happening to me...I wiped and reflashed but still having the problem
This is a problem many of us has encountered, I don't know why, try other ROM's I have found 1 that works for me.
I think it's a issue with the refresh rate of the screen.
Ditto. I have this problem as well with Cyanogen v4.0.1.
I've done the customary wipe prior to installing the ROM but the problem is the same.
This is the ROM I am using at the moment with no blurry screen problem.
http://forum.xda-developers.com/showthread.php?t=549755
i'm not using cyanogen but i am experiencing this issue with ZeroXd's Casper-4.2r2. i'm going to wipe the phone again and start over. So far, the Casper ROM is the only one that won't work for me and it was working well too
I'm having the same issue, but have ONLY noticed it with HERO-based roms. The Cyanogen 4.0.1 rom looked/worked fine.
Interested in the "fix" here...
Screen turns blurry
I am having the same issue but ONLY with the Hero roms. Cyanogen's new 4.xx roms are the frackin bomb so I'm not too sad. They work great for me. Definately want to know how to fix the issue though.
alot of ppl have this problem most of hero roms there is no fix yet sucks i know
yipcanjo said:
I'm having the same issue, but have ONLY noticed it with HERO-based roms. The Cyanogen 4.0.1 rom looked/worked fine.
Interested in the "fix" here...
Click to expand...
Click to collapse
what fix >?
Just experienced it for the first time after installing Drizzy's NoName V3. Have installed 10-15 roms prior and never experienced it until now. Trying out another Hero rom at the moment, will let ya know.
Update: QTek's rom seem's to work alright for me without the blur.
format sd card
seems to fix the problem....at least it did for me...
korndub said:
seems to fix the problem....at least it did for me...
Click to expand...
Click to collapse
The v3 noname I tried was on a newly partitioned/formatted sd card. :-\ QTek's is still going strong though. With the v3, after the first sleep it was blurry. I've been running QTek's for about 30-45 minutes now and no issues.
+1 to this issue. i had the same problem with some cyanogen ports in the sapphire thread, but using new cyan roms has not given me any issues. also noted that formatting does not help.
possibly an issue with engineering SPL?
i also noticed that a rom would flash fine, but as soon as my screen would lock thats when the issue would occur.
i wonder if it is a kernel / spl incompatibility. I had this same issue with JACxROM that runs great on and ION and is bassically the same phone. So I am a little confused. I am going to try and use Cyanogens newest 4.0.1 build and copy the boot.img to a JACxROM v1.3 and see if it does the same thing or not. Will report back to let you know what happened.
I have tried to use following HERO ROMs but they all turns blurry after sleep mode (when I unlock screen by pressing menu or similar button)
Champion v2, Fullv2 No Name, Superlite Hero etc.
Installed on myTouch 3g after rooting it using one click.
arunchowdhary said:
Installed on myTouch 3g after rooting it using one click.
Click to expand...
Click to collapse
Is this possibly *part* of the issue here? I'm using the "1 click" root method as well. Also, my SD card does have the proper 3 partitions, if that means anything.
Just installed the JACxHEROskiv1.4 ROM, which does not appear to exhibit this behavior. Nice ROM so far!
yipcanjo said:
Is this possibly *part* of the issue here? I'm using the "1 click" root method as well. Also, my SD card does have the proper 3 partitions, if that means anything.
Click to expand...
Click to collapse
I used the gold card method to root and I am experiencing the same thing with all the HERO roms. When you try to reinstall Cyanogens ROM's afterwards you experience the same thing. Only way I found to fix it was to format the SD card.
:/
We really need a fix for this. I am dying to use some Hero ROM's.
Well I fixed mine, I clean wiped everything and installed the cyanogen 4.0.1 rom. All is good now. I haven't messed with Hero, but I am liking the new cyanogen rom and he fixed the screen problem as well.
timafey said:
Well I fixed mine, I clean wiped everything and installed the cyanogen 4.0.1 rom. All is good now. I haven't messed with Hero, but I am liking the new cyanogen rom and he fixed the screen problem as well.
Click to expand...
Click to collapse
how did you go about clean wiping everything? I went ahead and bought a brand new sd card just to see if a fresh sd card cures it as well.
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
beast6228 said:
Well I ordered a G2X the other day and finally I received it. It came with Gingerbread 2.3.3 from the factory. (worked flawlessly) Keep reading.
After a couple days I wanted to try out CM7 on it. So, I rooted the phone by using NVflash and doing all that good stuff, then I flashed the phone with (Gingerbread OTA 2.3.3 Rooted flashable zip v1.0.0) I couldn't get root with SuperOneClick so that was my only option. Well I got root and that's when the fun started.
I installed CM7 on it, seemed to run fine, looked fine. But simple me, I wanted to go back to Plane jane 2.3.3 So, I did all the usual stuff (backing up, wiping data, formatting caches), then I ran OneClickRecoveryFlasher...and restored the phone with LG-P999-V10f.zip (supposedly a stock flash for 2.2.2)
well it all seemed to work fine apon finishing. It booted fine, ran ok. However now I have some really bad problems. The major one is that my wifi doesn't work worth a damn now, the connection is highly intermittent. I can't use the market to download apps because it dies out often, along with anything else network related. (browsing works 5% of the time) You catch my drift. My other android phones have no trouble with anything. Now here where it gets weird, I supposedly restored my phone back to stock. However, the phone reports a proper android version 2.2.2 which is what I flashed it to. However it shows kernel 2.6.32.9 Baseband is July 15th 2011. When I use LG's phone update tool it says I am running V21E which is Gingerbread 2.3.3 ...but that's not true because it is actually 2.2.2
I have no clue what to do, I am stuck. I just want to either have a stock G2X running either 2.2.2 or 2.3.3
Click to expand...
Click to collapse
You are probably going to have use Xboarders ROM then flash the unroot.zip he has in this thread http://forum.xda-developers.com/showthread.php?t=1158513.
See if that works to get you back to 2.3.3 completely stock.
It says that because it checks the baseband to see how recent it was, that's why it thinks you're on v21e.
As of now, there's no way to flash back to the old baseband, since people don't include the baseband in their ROMs, as that can cause a whole host of problems. The solution is to do exactly what tidewaterns said, that just gives you a little extra background info.
I am going to give this a try and see what happens, I will post results.
Well I tried the slimmed down version of Xboarders's rom and it seems to be working well so far. I originally installed his Stock OTA rom and that's when I started having problems. Oh well. thanks guys for all the help.
Crash course about root and roms: Superoneclick roots the rom you have in place. Flashing xboarders rom didn't "give you root" for the other roms you flashed, it is simply one rom out of many that is pre-rooted by the dev who packaged it up. When you flash it you have a rom that is rooted. If you had flashed CM7 (another rom that provides root access to its system files) then you'd have had a different rom that was pre-rooted by its dev.
Are you catching what I'm saying? Flashing xboarders rom didn't "give you root" any more than CM7 "gave you root." Root is built in to those roms.
If you want to restore to an unrooted stock rom browse the threads in the development section. There are a couple of stock nandroid backups posted that you can restore via clockworkmod recovery and then you'll have a stock unrooted rom. You can even do that and still have clockworkmod recovery in case you want to flash a different rom to your phone again.
And PLEASE remember when flashing from one rom to a different rom, WIPE WIPE WIPE data, cache, dalvik cache, then flash rom, then fix permissions, then reboot. This will save you SO MANY headaches.
G2X CM7
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
beast6228 said:
I learned something new Thanks for the info. And yes, this last time when I installed, I wiped and formatted just about everything I could possibly do, including fix permissions..seemed to do the trick.
Click to expand...
Click to collapse
Sweet! If you're simply updating to a newer version of the same rom you can probably get away with just wiping cache and dalvik cache and then flashing. Its just when you switch to a totally different rom that you need to do a full wipe. Gives you a clean slate to start with.
G2X CM7
I'm curious about one thing though. What would I accomplish by using Nandroid and flashing a bin? I see there is a BIN_LGP999AT-01-V10f-310-260-MAR-27-2011+0.zip file that is available for this phone, although I have no clue on how to install Nandroid. Anyways, wouldn't flashing a BIN be the ultimate way to restore the G2X?
Hi All,
I own a Motorola Defy. I am kind of new to android developement. i had 2.2 on my phone and wanted to upgrade, followed all the steps available online for cyanogen 7.1, liquid arc, etc. with all the ROM's i had the same problem. Everything goes fine, until i reboot my phone. The moment i do that after installing new ROM. I loose network connectivity and a pop up msg comes up continously saying android.phone.com stopped responding. From there i have to do the complete wipe once again. i read in some forum about flashing radio, however i dont see this option in my recovery mode at all.
Anybody who knows how to resolve this????????
I looked this up in the forums. This applies to going from 2.1 to 2.2, but sounds like it may help you. http://forum.xda-developers.com/showthread.php?t=947578
Thank you for the reply.
However, I was already running Froyo on my defy. I can also go back to that via RSD or by restoring it to the ROM i backedup before i started this testing. My concern is why i am not able to Install this custom ROM and make it working when all others can do it without any issues. I am still running Cyanogen nightly ROM (2.3.7). I also know the moment i restart my phone it will loose network connectivity and will keep getting those pop msgs. Is there a way to curb that.
Appreciate the help...
You can look for MIUI for the defy. I have also MIUI on my Defy and it works perfect
Sent from my Galaxy Nexus using XDA App
Thanks for your reply....
I was missing the defy baseband update. Thank fully that fixed the network connectivity issue. Now i am running ICS 4.0.1 perfectly. Except the camera everything is working smooth. Had little issue with restore from Titanum backup. But an unregistered version of TB fixed it.
I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?
Nandroid restore, if that won't work nvflash?
you mean use NVflash to do the rom install vs the recovery?
I made a topic about this, check my post (not able to give you a link right now sorry)
I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?
Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612
You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.
I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.
This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.
Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.
If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app
It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8
rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.
The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.
Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!
You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.
So to put it simple, I flashed ICS CM 9 release 5. It was nice and all, but i wanted to try a different rom so i wiped everything and flashed on RemICS-UX. It was nice, but i found CM 9 to be better, so i tried to restore using my nandroid backup. That resulted in the phone getting stuck on the team acid logo. I can still access the recovery. I tried to go back to the barebones rom, but that results in the same problem. It seems that i can only flash ICS roms now, and i just wanna go back to my good old stable gingerbread rom as it is more useful for now. I have been searching for hours on how to fix this, and i know its probably a simple fix, but its flying right over my head. Any help would be greatly appreciated.
http://forum.xda-developers.com/showthread.php?p=22596598
koolfoolx said:
So to put it simple, I flashed ICS CM 9 release 5. It was nice and all, but i wanted to try a different rom so i wiped everything and flashed on RemICS-UX. It was nice, but i found CM 9 to be better, so i tried to restore using my nandroid backup. That resulted in the phone getting stuck on the team acid logo. I can still access the recovery. I tried to go back to the barebones rom, but that results in the same problem. It seems that i can only flash ICS roms now, and i just wanna go back to my good old stable gingerbread rom as it is more useful for now. I have been searching for hours on how to fix this, and i know its probably a simple fix, but its flying right over my head. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Release 5 has a broken backup/recovery. Updates coming soon.
Sent from my SAMSUNG-SGH-I717 using xda premium
That makes sense. So I'm assuming in the next release, the recovery will be good to go? I just want to have a just incase backup to the barebones rom. Cause as stable as ICS is, i still use gps sometimes.Thanks alot for clearing things up.
koolfoolx said:
That makes sense. So I'm assuming in the next release, the recovery will be good to go? I just want to have a just incase backup to the barebones rom. Cause as stable as ICS is, i still use gps sometimes.Thanks alot for clearing things up.
Click to expand...
Click to collapse
Honestly, GPS works better for me on ICS then GB. I just made sure under location services that GPS source is internal, and mine locks on to my location within a ½ a mile in about 4 seconds