I've noticed other people seem to be having this same problem and there hasn't really been a distinct solution that I can see, so hopefully this question will be helpful in the future and not repeatative.
I've been trying to update to CM7 from CM 6.1.2 on my Evo. I followed instructions from here http://forum.xda-developers.com/showthread.php?t=902051 and downloaded all the recommended software. First I tried to just flash the rom, then the kernal, then the gapps. All seemed well at first, and I got past the Evo 4G screen, but it got stuck booting on the Cyanogen animation (the arrow just keeps going!)
Then I tried to wipe the Davlik-Cache, and rebooted again. I left the phone alone for about 45 minutes, and it still got stuck on the Cyanogen animation.
Finaly, after searching through the forums, I found another post which suggested I do a hard reset then flash the rom, kernal and gaaps then clear the cache and davlik-cache. Still, I'm stuck on the animation. I have a nandroid backup, so I can get back to 6.1.2, but I'd really like to get CM7 working, anything else I should try?
You should't have to do the kernel separately unless you have a specific reason for doing so the ROM comes with a kernel for you. I had a similar problem with my HTC however I was able to get it resolved by installing gapps. Here's what I did -->
Used ROM Manager to go back to working ROM
From working ROM, accessd ROM Manager and chose rebooted into recovery mode
Once in recovery cleared/wiped everything (cache, data, delvik) installed gapps then cm7
Restarted
It did take awhile after restart to get going however once it did it worked marvelously!
Hope this helps and good luck!
Reboot
Similar Problem, Defy CM7 Bootloop
The first time i tried installing CM7 I got a boot-loop. I have tried at least 7 different tutorials all with different variations of flashing this and wiping that yet none yield results. Still stuck at boot-loop.
The most recent thing i have done was used RSD Lite to flash
"JRDNEM_U3_3.4.2_179-002_DEBLUR_SIGN_SIGNED_UCAJRDNEMARAB1B80AA03A.0R_PDS03C_USAJRDNFRYORTCEE_P016_A016_HWp3_Service1FF.sbf"
this got my phone running again, i then pulled off some magic by rooting using a combination of super1click, Z4 and installing superuser myself. after that i copied the files for a bootmenu into my /data/ folder. using CWM Recovery v2.5.1 flashed
"freq_F_US_342_107-850-1700-2100-signed.zip"
to get my 3G running again, and gave up of CM7.
If anyone has anything that could help id appreciate it.
(ps. i've tried many variations of wiping things and re-flashing things)
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.
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
tom0779 said:
A notification popped up in CM10 alerting me that there was a nightly build update available (stable & evita). I decided to go ahead and run the thing to see if it worked/what the deal was and it followed normal process.. Booted into recovery, attempted flash, rebooted to a black screen.
It appears that it attempted to update and subsequently failed so I booted into recovery and flashed the cm10.0.0.zip myself. Fortunately nothing was lost or bricked and even my phone settings were all there when I booted back up again after (what appeared to be) a successful flash. Any knowledge of this? Seems pretty weird to me so I figured I would ask.
THanks
Tom
Click to expand...
Click to collapse
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
mittortz said:
Which One X do you have? I'm on the AT&T version and went through what you just said identically... however, after manually installing through recovery I'm still stuck in a boot loop/black screen. Unsure what to do at the moment. I don't know this stuff that well so I'm afraid to flash the build I had before without wiping (which I would really rather not do haha). I'd love to move to the stable version, although mine was pretty perfect as is. I just went ahead with the update for the hell of it, but that looks now like it was a mistake Any advice?
Click to expand...
Click to collapse
Cm10 stable works for me. But I installed it in recovery
Sent from my HTC One X-
I figured out the issue. I forgot that with the 2.20 firmware you have to flash the boot.img separately from the ROM. So after the update all I had to do was flash the boot.img and it was all ready to go again
First of all, thanks for all the hard work you guys do.
I have a problem with my tf101 running a Cyanomod. I tried searching on the forum, but there are so many keywords i don't even know how to input a proper query, so sorry if the problem has already been covered.
My tf101 was working just fine, i mounted a new rom (a nightly based on Jelly Bean 4.1.2), everything was nice and smooth, until one day i forgot to plug the charger to my tablet. The battery ran down to 0%, the first time it ever happened. Since then, everytime i try to power my tablet it gets stuck on the cyanogenmod rotating logo. I have to force reboot it several times before it starts working again, even if the battery id completely charged.
The first time it happened i tried wiping all data as well as the cache, i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly. Until the battery accident, everything was perfect.
Why is this happening? Is there a way to fix it?
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
ZigaG said:
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
Click to expand...
Click to collapse
Yeah it does, but only after countless attempts. If i do nothing and let it go, it gets stuck on the cyanogen logo forever.
I will try your solution and let you know, thanks.
Which recovery are you using ?
TWRP is the one to use, CWM has issues
I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?
I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app
I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.