Database Info

[Q] Phone shuts down.

My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody

What kernels have been used with the roms?
Sent from my HTC Sensation Z710e using XDA App

The used kernels were default kernels of the roms I used. Problem started wen using CM7 alpha. and now using Android Revolution with Faux123

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Same for me, but ONLY with Revo HD ROM...

SadMac said:
Same for me, but ONLY with Revo HD ROM...
Click to expand...
Click to collapse
You don't have it in any other ROM?

I had the same problem before, I changed my kernel to bricked 0.91 and the problems are gone now.

I'm downloading Insertcoin rom now. I'll report back if the problem still occurs.

Frazzy said:
My phone shuts down all by it's self once or twice a day. It occurs on multiple roms. I really want to find out why. Can someone tell me how I can log wat happens?
Since I don't know when and why it shuts down I would likely need a logger wich writes to a log file so I can look back what the problem is.
I suspect it to be a hardware problem... (Don't hope so but it happens on multiple roms)
Thanks everybody
Click to expand...
Click to collapse
Change kernels. Go from 1.5ghz to 1.2 via daemon controller or another CPU adjuster.
The bricked 0.91 also fixes most issues too as stated above
Sent from my HTC Sensation in UR-Quan subspace.

Before you suspect Hardware.. Check first your software.. I'f i were you, i'll back up all my roms.. full / super wipe, then check it on by one.. lets say IC for first 2 days then ARHD on the 3nd-4th day.. If it does not shut down, it only means one thing, its not HARDWARE, it can be software.. Check also your chosen Kernel on your flashed ROM.. there might be an incompatibility running multiple different roms and kernels..
hope i'd help.. click thanks if i enlighten you so far..

Okay, I'm back from a weekend away.
What I did before I went away (Friday afternoon) is:
- Reboot to Recovery
- Wipe cache, wipe dalvik, wipe data
- install zip: Super-wipe (just to be sure)
- Install zip: InsertCoin 3.3.0
- install zip: InsertCoin 3.3.1
It all went well until Saturday evening. It was off when I got it out of my pocket. i tried to turn it on and it booted up. If it is on there is no problem at all. It stays on all the time...... Until I unlock my sim with my personal code. 2 seconds atfter that the phone turns off...
Since the problem reoccurred I tried the following things:
- Wipe cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, reboot (problem still exists)
- Wipe cache, wipe dalvik cache, wipe data, Super-Wipe, re-install rom, reboot (problem still exists)
Is there a way to test the hardware to rule it out? The problem occurred in three different roms and got worse. I really can't see how this could be a software problem.
I'm now going to download the latest stock rom and see what happens...

I had the same problem I'm on tmobile sensation 4g in the us and I think all us sensations have the problem... When I was using any rom that was based on the experimental sense 3.5 base my phone would turn off/crash I tried all different Roms but the problem still occured, I though about it and installed revolution hd with sense 3.0 and still on the old base and the problem is gone. I'm waiting for the official release of the new sense 3.5. Hope it helps

I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?

Frazzy said:
I had the problem on 3.5 and non 3.5 based roms. CM7, Android revolution XE, android revolution sense 3.5 and Insert Coin XE sense 3.5. The last one I mentioned was the worst and I even couldn't get past the security code.
I now installed a shipped Rom. Let's see what happens.
In my first post I asked if there was a log file in which I can see why it shuts down. can anyone shed a light on that?
Click to expand...
Click to collapse
I am having the same problems. I tried all of the same roms you have tried and as of last week I have decided to unroot my phone and return it to stock rom and recovery. after a week I am still getting the same random reboots. the only non stock part of my phone is that it is still S-Off, but I think im going to have to learn how to put stock S-On and go yell at the T-mobile guys to see if I can get a new phone.
If you can come up with anything better I would be willing to try it. the reboots are killing me.

This issue sucks. I'm glad I'm not the only one that has it though lol. I've also gone back to stock rom, no root/S-ON etc. Just to rule out the possibility that it's something funky going on with custom roms, kernels etc. So far I do still have random shutdowns, possibly a little less than I did before, but still there nonetheless. To get S-ON again, flash the RUU appropriate for your phone, then get into fastboot and type
fastboot oem writesecureflag 3
and then
fastboot reboot-bootloader
More on all this is here: http://forum.xda-developers.com/showthread.php?t=1201773
As far as logs to track down what is going on, I think it might be in lastkmsg. Unfortunately I don't know exactly where to find that or what to look for exactly.

And as stated twice before me, the problem still exists. I'm going to undo all changes to the Sensation and see what happens. If the problem is still there the phone will go back for warranty.
And again my old trustworthy HD2 saves the day as a backup...

I've never experience having a reboot with a super wipe then flashing a custom rom.. i do it almost everyday.. maybe its already a hardware since software installation (roms, and kernels) are clean when you do the flashing.. Has your phone experience some accidents? like fell on the ground?

Not that I know of.
I'm not new to flashing and I'm a real flashoholic. Nothing ever went wrong with flashing. Where other people would have problems with a certain ROM I could always enjoy the Rom without trouble.
I installed the eu version of the shipped roms. the problem seems to be different again. Nof it shuts down far less then before but I have to pull the battery to get it to boot up again.
I hope I have enough time today to S-on the phone. Does anybody know if the box states which version number it was shiped with? I know it's EU but there are different version numbers. (or is that not impotant)
Thanks for your help everybody.

I think the problem is the battery. I bought a new battery, the evo3d batery and so far I have not had this issue again.

Problem is solved. I got a free board swap and now everything is working again. So it was a hardware defect.
Thanks for the help all.

[Q] 4 separate ROMS. Gets stuck at Turning wi-fi on, nothing else

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.

WiFI - turning on and on and on... RESOLVED!!!

Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
EDIT: wifi was not working about half a hour...but than...voila!!! It is for no reason back working the phone was just liyng on the table, than i took it and just set wifi on, "what if"... that´s really strange, but. But great! Now go back root, s-off and some awesome custom rom

lord5619 said:
Hi all!
I was trying some kernels and the last one was Bricked 1.36 and ViperS 1.1.0 ROM, wifi and other things worked, but today morning i woke up and wifi says "turning on" for 1O minutes, so i restart it. Still turning on. So i reflasherd kernel. Still turning on. So i clear cache, wipe dalvik and fix perimissions. Still turning on.So i flashed whole ROM with kernel Bricked 1.4 and did full-wipe. Still turning in. So i flashed come CM ROM with their own kernel. Still turning on....After some time for try turn it on, it says something like "fault, Fail..."(i am using other language, than english)
My vacation starts just great...
I am of cource S-OFF, HBOOT 1.27, Rooted, Sensation XE.
Can someone give me some advice? i am at the end of my experiences. Thanx!!!
Click to expand...
Click to collapse
Have you tried to restore the stock ROM?
http://forum.xda-developers.com/showthread.php?t=1529941

I agree I would recommend flashing the full ruu to take you back to stock Rom I did the same thing to get rid of my problem and flashing the full ruu did the trick I'm now s off Revolutionary style and flash 4ext custom recovery and su file and custom Rom the correct way
Sent from my HTC Sensation 4G using xda premium

Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....

lord5619 said:
Finaly i am here
I have flashed RUU 3.33.401.106 firmware and, did full-wipe and flash stock odexed ROM, but still the same issue :-/
and now i have HBOOT 1.29 and status *LOCKED*....
Click to expand...
Click to collapse
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?

malybru said:
Hi,
I believe THIS PATCH will restore your hboot to 1.27 and not "LOCKED"
Silly question,did you try rebooting your router?
Click to expand...
Click to collapse
will try your patch, thx
EDIT: it says -Revolutinary- and HBOOT is 1.27.1100 Thanks!
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?

lord5619 said:
will try your patch, thx
router works, coz we are using several phones and notebook @home...
I am afraid the worse scenario...burned chip or motherboard.
Or maybe if i get back to S-ON, unroot and restore complete stock...?
Click to expand...
Click to collapse
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.

malybru said:
Hi,
The other thing worth considering are the 2 gold pins inside the phone,just above the camera lens.
GENTLY lift them to make a better contact.
Click to expand...
Click to collapse
I am afraid, even this is not working. Pins definetly have some resistance and resting to its place. :-/ when i return from vacation, i´ll take my precious Sensation XE to a doctor, he will know perhaps.

I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.

i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance

alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I honestly don´t know, i thought, wifi is (almost)only kernel related, but now i see, that it is not :/ It is almost exactly my problem, i was using ViperS and changed kernel...but it didn´t suit me, so i restored the previous one...than i woke up and wifi is gone i cant solve it for now, i don´t have any freetime at this moment for making full stock condition.
i have tested stock rom with stock kernel, with some other HBOOT but still the same.

bhma said:
i also have the same problem with the wi fi turning on for 10 mins then it shows error
mine came with the initial ics ota update a very common problem i see on the net not only wifi but bluue tooth also not work
i installed the latest ota a week or so ago which cured a few bugs but still no wifi or bluetooth
so.... i did jb s offf , root etc installed CM9 this fixed the blue tooth and made the screen move reactive and smooth this is one cool ROM BUT still no wifi
any and all suggestions welcome but please consider i am a noob http://forum.xda-developers.com/images/smilies/confused.gif and may need a few signposts
thanks in advance
Click to expand...
Click to collapse
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.

lord5619 said:
Your wifi stops working through an official update? You should claim it! it is not your fault...for me, everything works, except thing about wifi like tethering etc., thats a serious problem, even reflasing the whole phone (rom, radio, hboot, kernel) doesn't help :/
I had Xperia Arc before Sensation XE and reflash always helps, no matter what happens.
Click to expand...
Click to collapse
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma

bhma said:
i read that the wifi tether(hot spot)......phone company pressure:cyclops: wont work on any htc phone with ics
dont know if its true though
yes wifi problems after the official update seems quite common and from what ive read htc dont seem to want to know about it
please remember im a noob:fingers-crossed: i installed jb hboot and cm9 rom but that rom is based on 3.33 i think
ill try another rom on the weekend and see what happens
thanks for your reply
cheers bhma
Click to expand...
Click to collapse
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...

lord5619 said:
I thing, if you changed rom, kernel etc. and wifi is still not working, another rom will be no help i am afraid but take your chances! it is not working for me. I can flash any ROM, any Kernel and the result is the same...
Click to expand...
Click to collapse
Originally Posted by Zeustopher
Wanted to update on my progress. I solved the issue on my phone:
I was messing around with it today while waiting for a meeting to start and I found where the wifi settings, etc are stored. It ended up being a corrupt/invalid wpa_supplicant.conf file. All I had to do was pull that file out from the directory and turn on wifi and *poof* it worked again. When I turned wifi on it created a new file and everything has been great so far this afternoon.
In case anyone wants to give it a shot who is having wifi issues you can find the wpa_supplicant.conf file in /data/misc/wifi/ directory on your phone. Simply cut/rename the file and put it somewhere else. If you have wifi passwords you want to save, you can open the original file using a text editor and copy the settings over to the new file.
I believe the cause of my issue was actually Titanium Backup. Looking at the last time it backed up my wifi settings was back when I wasn't running ICS yet. Yesterday I did restore an app using it and must have accidentally restored that old backup. Their formats are different from Gingerbread to ICS apparently and it was causing errors.
i found this on another post dont know if it will help but it could be the problem with the ota update from gb to ics
now the silly noob question how do you access the directory ????http://forum.xda-developers.com/images/icons/advanced/sign.png
i got into the directory but it doesnt seem to work in another thread someone got it to work with a virtuous rom
ill try that on thr weekend
enjoy your vacation

hmmm thats iteresting, but if you do full-wipe and flash some rom and kernel, these files are rewriten...but because i am curious i tried it and!!! it is not working for me :-/
And how to get into this directory?Simply... download dome file manager from Play Market(i lika Total Commander), but you can use whatever you like, set in options "root function everywhere" and allow superuser. than you can go in any directory and read/write/change
EDIT: ou, now a see whole post, ignore my instruction i am mega-sleepy

alphaz1 said:
I have this problem too. I've been using ViperS 1.1.0 for a few weeks without any wifi problem. Yesterday, the wifi was working like normal then in the evening I flashed HyperNonsense 3.3 just to try it. Didn't like it, so I restored nandroid of my ViperS, then flashed yank555's faux123 kernel v2.52. I only realised wifi is not working today morning. It just shows "Turning On", but nothing happens. Could it be kernel issue? Previously i was using yank555 v1.9 without any issue thoguh.
Click to expand...
Click to collapse
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.

alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
Yank v2.52? hmmm that´s kernel by Faux?

lord5619 said:
Yank v2.52? hmmm that´s kernel by Faux?
Click to expand...
Click to collapse
yep

alphaz1 said:
I fixed it by doing a full wipe, flashed ViperS 1.2.1, reboot, use the phone for a few minutes, then flashed Yank v2.52.
Click to expand...
Click to collapse
No help for me still the same "turning on"

Phone stays in Roaming mode.

I've Installed this yesterday, but I'm experiencing a couple of bugs.
I first did a format (disk + dalvic),
then flashed Codename Android v3.3.2
then Camera + Backlit Fix
and then Codename Android GAPPS
Because I have a S-on device, I flashbooted the boot.img from the CA Gapps zip. (other zips didn't have that file)
Everything works very smoothly, but the errors/bugs I encounter are:
4. When I insert my SIM-card, I'm always Roaming, untill I enable WIFI, then I can make phonecalls.
So when WIFI signal is lost, I'm at Roaming and mobile-internet doesn't work.
Does other people have these issues, or is it because of a wrong Boot.img I flashed?
Click to expand...
Click to collapse
Since I don't want to post this in the dev section anymore, I'll continue here.
This problem first started with Codename Android.
When I install an other ROM; for example Blindbean, the problem stays.
Then I tried MIUI from Shrome, same problem.
(always with format disk and clean dalvik cache)
This night I installed the ICE-DS v4.4 ROM, and everything works fine again.
But when I install Blindbean again, problem is back.
You guys have any idea how this is possible.

Boot.img isn't suppose to be in gapps. Should be inside the rom itself.
When flashing a new rom always do a full wipe.
Sent from my HTC Desire S

Ok, so I did again couple of hours of googling and stuff, and found some interesting stuff.
In our country, we have 3 mobile networks with their own towers. (proximus, mobistar, base)
But 2 of them rent these towers to other carriers. (mobistar for example to Telenet)
It appears Jellybean (I have it on every JB rom) sees a difference between the carrier and the tower-network. (If you get my point)
So I have to enable Roaming to be able to use my carriers network.
So far I can see, no additional costs.
But this still is a strange bug, that started with JB.

[Q] No cellular wireless signal after Cyanogenmod 9 - ICS on i897

Not getting a cell phone signal at all on my Captivate. very rarely I get it and it stays on until I reboot for some reason, or sometimes goes off on its own. No problem with wi-fi or anything else.
Have had Gingerbread 2.3.5 - KK4 (official) for a long time, and did not have this problem. Here is what I did:
Installed Cyanogenmod 9.0 (ICS 4.0.4) on my Captivate that had the stock Gingerbread KK4. Also installed the gapps-ics package from 29 April 2012
I did this after rooting, and installing clockworkmod.
Even updated it to Cyanogenmod 9.1, but have the same issues.
More detail on it:
- The cellular radio shows no signal, but Wifi is on fine.
- When I press the power button, I see the power off and reboot options, including one that says "Airplane Mode is ON", although it clearly isn't since Wifi is working
- A couple of times, I rebooted into recovery, and did a "repair permissions" and rebooted, and it got a signal, but does not happen always
- Once the signal is on, it stays on for the whole day, but goes off again after a reboot
- Turning Airplane mode on and off does not help
Is this a modem issue, that seems to be a popular problem. It's almost as if there is a software bug that fools the phone into switching off wireless radio
Please help me fix it, or share successful fixes

I had same problem when I went to helly bean then back to remics-jb I flashed back to stock then back up to what I wanted it fixed the problem so I think its the modem.
Sent from my SGH-I897 using xda app-developers app

You need to flash to stock and back.
Sent from my SGH-I777 using xda premium

How do you flash your rom?
Im a little bit afraid to bricked again my cappy.
Sent from my SAMSUNG-SGH-I897 using xda premium

KOROCK is right
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?

up_on1 said:
So were you able to fix? I had a similar problem as well; I made the mistake of putting cm9.1 on and it bricked because I followed the instructions that popped up when I thought I had flashed it correctly. I tried everything; this is my daily driver so I had no choice but to find a fix, and find it fast as my clients were unable to get a hold of me for a few hours.... Anyways, got a little off track; but did you fix?
Click to expand...
Click to collapse
Not fixed yet. Wheredo I get the stock rom.?

rdugar said:
Not fixed yet. Wheredo I get the stock rom.?
Click to expand...
Click to collapse
A little search/reading goes a long way.. http://forum.xda-developers.com/showthread.php?t=1300843
KK4 is what you'll want to go back to stock but I highly suggest you read this before you do anything http://forum.xda-developers.com/showthread.php?t=1350266
Also, before returning to stock, you could try flashing a different modem.

Check to see if your baseband is still there. If it said "Unknown", you need to restore it. CM9 is supposed to have the modem.bin file included though. Check to see if the /radio folder have modem.bin in it, if it does, and the baseband still say Uknown, then manually delete the modem.bin, do a wipe and reflash a CM rom that have modem.bin included.
If Baseband is still there and still no signal, then check to see if IMEI is corrupted or lost (if its null or doesn't match the back of the phone). You can either copy over the efs backup folder if you have one and "fix permission" in CWM. If not, then you need to ODIN the phone to stock to fix it.