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)
Hey guys, ok so I am coming from two HTC Heros (CMDA Sprint)
Was running cyanogenmod on both (me and the wife) loved it.
Now that I have the E4GT, I went ahead last week and used ODIN to install LoStKernel.
Now it did give me root and I have used apps like rom toolbox and setcpu.
My main problem is it seems these samsung devices are a lot trickier to tinker with.
Basically I am looking to get Clockworkmod so I can flash roms and make nandroid backups.
From what I have read, I need a kernel that supports and/or has CWM in it.
I tried flashing CWM with rom manager, and it installed - but I have no option to backup/restore I can only flash a zip or clear cache.
There are SO MANY things posted in the development section and I do not know which kernels are the latest, best etc.
I need:
a) CWM/busybox
b) overclocking support
c) FULL stock functionality (no loss of wifi or something stupid like that)
From what I am understanding the kernel is included with a rom. But I can't flash a rom without CWM. So I am rooted but stuck with stock rom and it's kernel.
Confused, lol!
Can someone point me to a proper thread to get me CWM and a well supported ROM to install? Can I get CWM working fully on the stock kernel/rom?
If someone can point me to the right direction, maybe I can find a developer to donate to lol!
No love?
At this point I'm just trying to get cwm. Seems I may have already had it just didn't know it came with lostkernel and now I botched it using rom manager.
Sent from my SPH-D710 using XDA App
You can actually flash a new kernel with CWM in odin
Thats the easiest method
There are several, as for the best I dont know yet
Im still tinkering with my setup
I guess that's my main issue - I can't find one that has CWM, everything I am seeing is a ROM that needs CWM to install.
If I had CWM I'd be all set because then I can backup my setup and try new things without worry, but I don't want to use ODIN to try a kernel that CWM won't take, or isn't there, and then lose what I have ya know?
All set, seems I flashed a kernel that wasn't what it was supposed to be. I apparently flashed his earlier version (pre-LoStKernel) that did not have CWM5 it it.
Just used ODIN last night to drop in LoStKernel and kept root, but also have CWM5 now. After clearing my SD Card, made my first backup. 1.5GB, jesus! lol. Nearly my whole SD card... yes, it's from my old Hero, so, time to get a 32GB.
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.
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Yesterday i updated to the at the time latest CM9 nightly, and im not sure if that is the cause but before then my backups were aroud the 1gb mark, then, when i tried to do another backup after updating it kept failing. when i restarted my phone the entire memory was full of the aborted backup.
I deleted stuff until the free space outweighed the used space so i could definitely fit whatever size the backup was and it worked but the result was 6gb!!
Is this a problem anyone else has had with or without cm9? as i said im not 100! sure that was the cause but it does seem likely.
If theres a better place to ask this question please let me know.
... Ive tried re flashing clockwork mod recovery and re installing rom manager. I also flashed the touch version with rom manager. None of that has made any difference so far. Any help would be greatly appreciated as im no expert.
Updating/Installing/Uninstalling ROM manager doesn't affect ClockworkMod recovery at ALL. ROM manager's sole purpose is to install Clockworkmod and help beginners with flashing ROMs. And if you have the money HELP you find ROMs as far as I can see.
As for your problem, it looks very weird, Reflashing a ROM would probably solve it, but you would love to make a backup first.
Try using Titanium backup to backup your apps and some information. Sync your contacts and calendar most importantly and make sure you backup everything. Then try flashing a different ROM. Remember the ROM is nightly for a reason; this could be the reason.
Cheers
well i think i've found what it was... its a known problem with recovery version 5.8.4.5... its backing up everything resulting in huge backups... the weird thing is its the same version ive been using for a few weeks and ive never had that problem before. Now i just have to work out how to replace this version with the older version.