Ive had a long running problem with my tf101, where it sometimes dies with its asleep. Simply, i tap the power button to put it to sleep when im not using it, and when i come back to use it, i tap the power button to bring it back, and nothing. I have to hold the power button for 10 or so seconds to get it to reset. Seems like its freezing before it goes to sleep. Its done it on any rom i flash, so i dont think its a rom issue.
I'm running CM10 nightlies. Im wondering if this is a kernel problem, so i tried flashing the KAT kernel found here:
http://forum.xda-developers.com/showthread.php?t=1841851
It booted, but killed my wifi. I tried a few things to resolve the wifi issue. Cleared cache/dalvik, wiped all data, nothing helped. Restored my cwm backup from before the kernel install, and wifi came back.
Im having trouble determining what kernels are ok to use with CM10. Does it matter? Did i maybe run into some other issue with KAT that wasnt specifically a kernel problem?
Thanks!
Related
Is this the right place to post this?
Inspire 4G Rooted, S-OFF, Clockworked with Bubby's One Click, and attempted to flash CM7.
I can make it past the set up, all the way into the phone. Shortly after, it will just kind of randomly freeze up and go through the boot animation again and then take me to a lock screen. I can unlock it and go back into the phone, but it will almost immediately freeze and go back to the boot animation again.
Flashed 3 times, once on RC2 and twice on RC3, using ROM Manager 3.0.1.0, Clockwork 3.0.0.6, wiping data and cache each time.
Please help!
Did this happen when you were turning on Wifi?
Now that I think about it, the most recent flash I did, yes it did occur when I turned on Wifi...but I am not sure about the other times.
What would wifi have to do with it?
wberry85 said:
Now that I think about it, the most recent flash I did, yes it did occur when I turned on Wifi...but I am not sure about the other times.
What would wifi have to do with it?
Click to expand...
Click to collapse
Its a known niggle with almost every CM build. It doesn't like wifi on the first boot. Let it come to the launcher screen and then reboot the phone. Things should go smoothly after that.
same thing happened to me. I just rebooted it a few times and problem solved. Had no idea that wifi was the problem though.
Awesome! Flashing now...
This works!!
Thanks again guys...
I was running happily on a CM 10 build when I decided to upgrade to CM 10.1. I did this by simply downloading the latest nightly and flashing in CMW (wiped everything ect) however the touch screen didn't quite work and I assumed it had something to do with me not updating a bootloader or kernel or something to 4.2 as well. I decided to go back to the CM 10 build I had, flashed it, device booted, but none of the apps would work so I decided to reflash. Did a wipe ect only this time it hung in the middle of the install for a solid 15 minutes. After waiting another 5 minutes I held the power button until the device turned off thinking I would just go back into recovery wipe and flash. Now the device won't turn on and I'm afraid I've bricked it. Does anyone had any ideas of what I can do?
Fe_Man said:
I was running happily on a CM 10 build when I decided to upgrade to CM 10.1. I did this by simply downloading the latest nightly and flashing in CMW (wiped everything ect) however the touch screen didn't quite work and I assumed it had something to do with me not updating a bootloader or kernel or something to 4.2 as well. I decided to go back to the CM 10 build I had, flashed it, device booted, but none of the apps would work so I decided to reflash. Did a wipe ect only this time it hung in the middle of the install for a solid 15 minutes. After waiting another 5 minutes I held the power button until the device turned off thinking I would just go back into recovery wipe and flash. Now the device won't turn on and I'm afraid I've bricked it. Does anyone had any ideas of what I can do?
Click to expand...
Click to collapse
What version of CWM were you using? Specifically.
If you currently have a JB bootloader, it doesn't matter which CM 10x you install.
If you flashed the original back, you should have done all wipes first. They are 2 separate builds.
If you wipe Data, and it hangs at wiping Data, then your memory chipset is hosed. Send it in for repair. It will require a mainboard replacement.
You can try installing a full stock rom first though.
MD
Fe_Man said:
I was running happily on a CM 10 build when I decided to upgrade to CM 10.1. I did this by simply downloading the latest nightly and flashing in CMW (wiped everything ect) however the touch screen didn't quite work and I assumed it had something to do with me not updating a bootloader or kernel or something to 4.2 as well. I decided to go back to the CM 10 build I had, flashed it, device booted, but none of the apps would work so I decided to reflash. Did a wipe ect only this time it hung in the middle of the install for a solid 15 minutes. After waiting another 5 minutes I held the power button until the device turned off thinking I would just go back into recovery wipe and flash. Now the device won't turn on and I'm afraid I've bricked it. Does anyone had any ideas of what I can do?
Click to expand...
Click to collapse
Try seeing if you can get into recovery but holding i believe power and vol- or vol+
If not, see if your computer detects it, then try adb or fastboot
Sent from my Nexus 4 using xda app-developers app
Hello Peeps,
I was trying to flash a rom yesterday and had something strange happen to me.
The rom featured Aroma installer and I had flashed this particular rom roughly 5 or 6 times with no issues.
Yesterday, I did a full wipe and tried to do a new install of this rom.
There was an option screen in aroma that allows you to choose your own mods and features or use the developers defaults.
I was on this screen trying to choose the developers defaults option and Aroma simply froze up.
It would not let me choose with version to flash.
The touch screen wouldnt respond and I didnt know what to do.
I searched google and found nothing.
I decided to do a battery pull.
I know that a batter pull during a flash is something we should never do as it will brick our phones.
In this case, as the flash had not actually started yet I decided to try it.
I pulled battery and booted into recovery and was able to restore a nanroid.
I am just curious if anyone else has had this issue?
How dangerous was it to pull my battery?
Could I have bricked my phone?
Phone has been working just fine, I am just wondering if there is another way to resolve an issue with Aroma like that?
Thank you,
I never had that problem as for the pull battery it is fine as long as you're not flashing.
I was installing a ROM on my sister's s3 when the aroma installer completely froze. I pulled the battery and it boot looped but wouldn't go into recovery until around the 10th or so time (vol up + home + power). Flashed it again and it worked fine...really weird.
As for bricking your phone I agree with above poster, it should be fine if you aren't flashing anything.
Sent from my SCH-I535 using Tapatalk 2
I've had this same issue happen a couple of times. It usually happens when I try to install the Jelly 'Beans' rom...sometimes it will work, sometimes it will freeze. I usually have to do a battery pull and recovery will come right back up. I've noticed this seems to happen the most when the phone has grown hot...so maybe it has something to do with RAM, etc.
I am having issues when unlocking my phone
Whenever i click the unlock key it will unlock my phone, however randomly it will shut the screen off, turn it on again, shut it off etc. WIthout even touching the button this is happeneing. It will also occasionally bring up the power menu (cm10) for the phone. I dont think it is a hardware thing because my button feels fine and isnt broken. However i am wondering if it is cm10, i recently changed from stock cm10 to liquidsmooth and it still does it. Any advice would be great.
Did u data wipe/factory reset before u flashed the new ROM?
UNL◎CKED & L◎ADED GS|||
Yes i did at least through clock work mods factory reset
Have you been using the same kernel through all this?Also is it the correct kernel?
UNL◎CKED & L◎ADED GS|||
I have been using the same kernel i should probably check to ensure it is correct
Hello. I have a rooted OPO, running 05Q. Last night I finally succumbed to the temptation to flash a ROM. I used the app "CM downloader" to obtain the latest nightly of CM12. Using TWRP, I created a backup, then installed the downloaded ROM. It didn't work; the phone got stuck in what is, I think, called a bootloop. That is, it just kept showing "Updating Android" then going back to a CM animation, over and over.
After letting this go on for quite a while, I powered the phone down and rebooted into Recovery. From there I restored the backup I had created. That seemed to go without a hitch; everything looked as it did before I set out on this adventure. But when I let the screen go dark after 30 seconds of not doing anything, I found that double-tap wouldn't wake it, and neither would pressing the power button. It seemed to be still working, since notifications were coming in, but I couldn't get the screen to light up. So I did a reboot, which worked, but only until the screen went dark again, at which point I had the same problem.
So...I used Titanium to backup all apps and settings, and did a "reset to factory", then restored apps and settings. This seemed to work, but once again I found that once the screen went dark, the only way to wake it up was to reboot. And again, even though the screen was dark, the phone was working. I listened to a podcast while driving to work, even though I couldn't wake the screen up.
Any ideas what the cause of this might be? I did check the Settings to make sure the double tap to sleep and wake were turned on. Everything was as I'd left it. And in any case, even the Power button wouldn't do it.
You need to flash cm11 firmware, that is the radio and stuff to get your cm11 05Q to work properly again
Edit
You should flash this
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
waterdaan said:
You need to flash cm11 firmware, that is the radio and stuff to get your cm11 05Q to work properly again
Edit
You should flash this
http://boeffla.df-kunde.de/bacon/modems/Full-XNPH05Q-modem-flashable.zip
Click to expand...
Click to collapse
Thank you, that worked!