Here’s the reason for anyone of you who is facing this over-heating problem with your P50* phone: your Kernel is NOT compatible with your ROM. Colors will likely be displayed properly, but the over-heating problem will be persistent, and will shut-down your phone as soon as it’s booted. Don't panic; there’s a very easy solution to this problem; however, it will involve installing another ROM which is compatible with that Kernel (or back to your original ROM). I’d suggest you do some research on the ROM you are using with that Kernel, and to get a compatible one flashed, or just to get the previous ROM installed on it again. Follow the following steps.
1. Plug-in your phone to its charger. The ‘over-heating’ sign will disappear.
2. Open your internet. If you had done a complete factory reset before installing the ROM, just connect to Wi-Fi.
3. Install your previous ROM back to get your phone back to normal and not get that ‘over-heating’ sign again. (Hopefully you know it! If not, PM and tell me.)
4. Now, if you want a different ROM installed, you’d be better off installing one that comes WITH a Kernel. Separate ROMs and Kernels are for experienced users; hence, sticking with those which come with both wouldn’t hurt until you are aware of what you’re doing and know how to handle any problems that may occur.
If you have any questions, please ask. I am extremely busy with exams, but still managed to get this post written.
Note: No CPU frequencies or anything else had caused the problem. It's not very easy to get a phone over-heated.
Good luck!
Related
I get this message when I boot up.
I cannot access settings so I cannot perform a factory reset.
Is there any way to factory reset when you cannot access "Settings" because of constant force closes.
I am running stock but with lots of side-loaded apps.
I can access the file explorer. That is the only thing I can open that will remain open even though I get constant force close popups like "android.process.acore has stopped... android.process.media has stopped unexpectedly...
Is my gtab toast? Can it be saved or should I return it?
I get this all the time, with all the mods I do. Don't worry, your system is fixable.
For me, I use clockworkmod recovery .08. There's a "fix permissions" option and this always fixes the problem for me. It also allows a data wipe within recovery.
If you are 100% stock, you could try one of the stock ROM's here as well - that might get you working. You have a few options, here. Check out the FAQ in my signature. I'm actually posting up the new stock update that I pulled from TnT, today.
EDIT: Direct link the the stock ROM updates -- http://forum.xda-developers.com/showthread.php?t=842000. You'd need to understand how to actually run these, which I mention in the FAQ section.
thx Roebeet, I was able to update to the new stock rom.
But I still have the same problem. Is there any other way to wipe my data. Can it be done while connected by usb or do i have to root it?
Is there any hardware button method to do a factory reset?
I still cannot open settings... it gets canceled by the force closes.
I am ready to give upon my G-Tab which I was enjoying so much.
Does anyone know how to wipe the date if you cannot open settings???
Try clockworkmod - it really is a great tool. You can find it in the Tnt Lite dev section as I have a link for .08.
For UID issues, "fix permissions" will correct it. And you can wipe data via clockworkmod as well. You can even remove it by flashing back to stock -- the latest stock firmware works as I've done it myself, the other day.
Btw, there are so many threads here that I sometimes miss replying. I dont ignore, I just might miss a post. Always feel free to PM me if you have a question.
I had a similar issue where something got corrupted in my user data and I was completely unable to start the settings or open the keyboard. I had to flash back to the full vanilla ROM because it contained clockworkmod, which was the only option available to accomplish a factory reset. That wasn't a fun day.
Think I figured out a key reason for sudden UID issues
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Again, the Tap UI team and who hired them and approved it on the Gtablet should be fired, rehired for a minute and then fired for good. Word.
This sounds kind of "preachy," but don't give up.
There is a learning curve to the G-Tablet, and it takes a good bit of reading on this site and assimilating the info.
I will testify that I had a hugely bad malfunction and and even worse fix on my tablet.
Using suggestions from helpful folk -- and carefully researching what I needed to do -- I was able to get my tablet back working just fine. To be sure, it's not stock any more!!! But I actually believe that with all I learned about flashing, mods, etc., I now could go back and make it stock again if I wanted to.
Don't give up. Just keep reading and researching the learning.
Rev
rushless said:
People including me are getting UID errors even after having a stable rom and several reboots with no issues. Based on guinea piggin' my G, I can confirm the issues happen on apparently stable installs anytime you update a Google app.
Case in point, I updated Google Voice and Gmail and soon after I rebooted the G- UID city. I have started with a clean rom and installed many different apps to test. The only apps that hose the device at reboot are the GAPPS and it is not just if you update with the package. Simply updating from market will work fine, until you reboot and then it is a few minutes for trying to shut the device down and then perhaps two reboot attempts using fixed permissions.
TnT 2.20 (at least) does NOT like GAPP updates. How could VS bork this up so bad that fundamental apps for Android bork the device?
Click to expand...
Click to collapse
Not true for me, I installed the new Gmail from the Market with no problems. I am on TNTLite 2.2.1.
Google Voice has always been a hack for a tablet, since it is not actually phone. You might want to pull it out and see if your issues are solved.
I am back up and running thanks to clockwordmod. Thanks again!
ninjaprofessor said:
I am back up and running thanks to clockwordmod. Thanks again!
Click to expand...
Click to collapse
Good to hear and thanks for the update!
I am currently having this problem. I am hoping to sell my 10" Android 2.2 Tablet PC on Craigslist... I need to fix this Error... I've only used it 10 times to play Angry Birds. The forum with the links I am confused as to what one to use... I am younger I must say. I am not a 21 year old "computer whiz"/.NET/OS maker... I do make websites. Besides that... I do not know how to "Wipe my system partition" as my Error message says to. Especially due to the fact I cannot open Settings. PLEASE HELP. I may have repeated things said above in his problems but I would like a "NOOB" walk through... (Because I am one). Please help. Thanks in advance. -Sophomoric
Hey, I had a same after my phone battery was empty and it turned off. I kept it off and recharged it, then I had the feeling "I'm feeling Lucky" -.-' so nice from google. xD
Had to wipe everything then full reinstall... such a pain.
Probably the cleanest solution HERE
my wifi worked for awhile then stopped connecting. tried wiping cache/davlik 3 times. tried re-installing the rom. i nandroided back to an older version which wifi worked before and now it doesn't. tried flashing a different rom no success. tried flashing a different kernal anthrax b-02 via recovery no success so i tried flash gui image app in the market. all with no luck. im on h-boot 1.40.
my 4g connects just not my wifi. if anybody can help it would greatly be appreciated.
ro2themax said:
my wifi worked for awhile then stopped connecting. tried wiping cache/davlik 3 times. tried re-installing the rom. i nandroided back to an older version which wifi worked before and now it doesn't. tried flashing a different rom no success. tried flashing a different kernal anthrax b-02 via recovery no success so i tried flash gui image app in the market. all with no luck. im on h-boot 1.40.
my 4g connects just not my wifi. if anybody can help it would greatly be appreciated.
Click to expand...
Click to collapse
The 4G and WiFi drivers are stored in the same directory. Generally, if one is not working due to a mismatch with the kernel, the other one will not work either.
Since you're taken some initial steps to gaurantee the WiFi module definitely matches the kernel version, I would move on two more detailed troubleshooting.
There are two approaches I would suggest to get at the root of the issue quickly without wasting more time/effort.
1) When you toggle WiFi on/off from the Settings screen, what message does it display there? It should also be displaying detailed error out put in at least the logcat if not also in dmesg/kmsg. If you are able to post up these logs, it should help narrow down the issue.
2) Nandroid your current setup, you can revert back later and then flash a completely 100% stock ROM and kernel. Use a modified version of the RUU if needed.
Personally, I would glance at the logs from Step 1, but to make sure the hardware on the device is in deed working 100% and there are no hardware issues, I would revert to 100% stock ROM and kernel. If the WiFi doesn't work with 100% ROM and kernel, this would appear to be a potential hardware issue and I would look into getting the device repaired/exchanged.
If the WiFi works on the 100% stock ROM and kernel, then the issue now lies with either the previous ROMs/Kernels or the methods used to load them.
Hope that helps and appreciate the support!
hey, thanks for the reply and help.
when i try ti connect in the settings, it attempts to connect and obtain the ip address but it doesnt connect and just times out. i dont know how to look at or even find the the logcat or dmesg/kmsg. if you could tell me how to find it, i would post it.
im going to try to flash a stock rom with stock kernal, hope fully its not a hardware issue. i will post my results on the stock rom flash.
i just flashed Shooter_S_Sprint_W...8.651.3_deodex.zip and still no wifi.
am i just screwed or is there another way to fix this problem?
joeykrim said:
The 4G and WiFi drivers are stored in the same directory. Generally, if one is not working due to a mismatch with the kernel, the other one will not work either.
Since you're taken some initial steps to gaurantee the WiFi module definitely matches the kernel version, I would move on two more detailed troubleshooting.
There are two approaches I would suggest to get at the root of the issue quickly without wasting more time/effort.
1) When you toggle WiFi on/off from the Settings screen, what message does it display there? It should also be displaying detailed error out put in at least the logcat if not also in dmesg/kmsg. If you are able to post up these logs, it should help narrow down the issue.
2) Nandroid your current setup, you can revert back later and then flash a completely 100% stock ROM and kernel. Use a modified version of the RUU if needed.
Personally, I would glance at the logs from Step 1, but to make sure the hardware on the device is in deed working 100% and there are no hardware issues, I would revert to 100% stock ROM and kernel. If the WiFi doesn't work with 100% ROM and kernel, this would appear to be a potential hardware issue and I would look into getting the device repaired/exchanged.
If the WiFi works on the 100% stock ROM and kernel, then the issue now lies with either the previous ROMs/Kernels or the methods used to load them.
Hope that helps and appreciate the support!
Click to expand...
Click to collapse
joeykrim, thanks bud for your help. I got it to work. i really do appreciate the quick reply and assistance.
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Drachen808 said:
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
Click to expand...
Click to collapse
Drachen808 said:
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Click to expand...
Click to collapse
A bad flash can occur but generally they aren't prevelant. The best place to look for feedback on ROMs is in that specific ROM thread. If that specific ROM isn't setup well, or has bugs, these will cause random reboots.
If you're really interested in helping out the devs, the best first step in technically troubleshooting a random reboot is to grab the /proc/last_kmsg file. This is a log of the kernel as of last boot and will indicate whether or not the kernel was involved in the random reboot. If the issue is in the kernel, will narrow down the focus. If the issue is not in the kernel, will eliminate that possibility.
Another common cause of random reboots can be poorly coded 3rd party apps. Unfortunately, depending on the number of 3rd apps installed, this process can take a while to troubleshoot as the best method is to remove all and start installing in batches waiting to see if any random reboots occur.
Hope these few suggestions and some technical information help!
Thank you Joeykrim. I will look into that, but I am fearing more and more that it may be my phone. I have tried probably every sense 3.0 rom (need wimax and camera so no 3.5) and several different kernels, and it keeps happening.
after updating my ray to ics 4.0.4 wifi and bluetooth not working. when trying to turn on it shows turning on for 10 seconds but it doesn't. please help
hello there
i will try and help you but i have to ask you something
1.which android 4.0.4 were you trying to flash the unofficial one or the official one
2.this is a development section not q and a
for me wifi and Bluetooth is working fine.i will need more detail in order to help you.
i installed ice cream sony ka19.1 after that blutooth and wifi not turning on .
Please, make sure you do full wipe before flashing...
and reflash you rom.
i didn't find any problem with KA rom
i wiped every thing and tried to install several roms. but same problem all the roms...
well try two things
1.try changing kernels could be kernel issue than the rom.
2.flash official android 4.0.4 then root it with cwm(by flashing kernel) then install the rom.
i tried several roms and kernels . but the bluetooth and wifi is not turning on . what should i do?
Then just flash the official kernel with offical 4.0.4 rom as normal
Please update...i have the same problem. With me the phon turns itself off once the screen is locked. (
yeah, me too, i have same problem
not only in 4.0.4, but also 4.0.3, i flash my ray to 4.0.4 and 4.0.3 and do a full wipe, but wifi and bluetooth still not working
i don't know what happened with my phone, but suddenly at morning, my phone was already like this, i'm not installing something at my phone
please, help me, someone
there is a Help thread in this section, so please post your queries there
now, there's something wrong with what you did (your process)...
I've been flashing roms for the past 3 months without any issues (aside from the bugs on the roms themselves)
better clean up your phone first before doing mods...
sometimes people do not read instructions and do their own research
i have the same problem too...
please help..!!!
please update soon...
I think all the most popular custom kernels have the necessary modules embedded – so it’s unlikely to be a software problem.
For some rom/kernel/mod combinations I find that wifi doesn’t work on the first boot – I just reboot and it works.
These issues aside the only problems I have with custom kernels/roms/mods will be because I have conducted a lazy install (i.e. I’ve not followed instructions to the letter, or I haven’t flashed the stock ftf first).
The best way to trouble shoot is to start again and just re-flash the stock ftf – if your phone is not working properly after this it is 99% likely that your issue is hardware related - this might your phone, but the faulty hardware might also be your USB cable or the USB port – so swap the port/cable or even use a different computer and test again. The last thing to remember is that your file might be bad – so if what I’ve said already fails download the files again and try once more.
Similarly, if you constantly flash custom roms, without reverting to stock before hand – it is my perception that eventually your device will start to misbehave. You can get away with flashing JJ’s Hybrid and then Ice Cream Pureness, but this may not be the case with all kernel/rom combinations.
The best way to achieve clean installs of customs roms is to do it over a clean install of the stock ftf – if you’ve backed up this is a minor inconvenience that only adds 5 minutes to the installation time. If you’re lazy you may have bootloops or soft bricks or an unstable system (lots of fc’s or things not working e.g. wifi) – these will inconvenience you much more.
Finally I’ve had some hairy moments where I thought I’d permanently damaged my phone – but what every noob must remember is that you can always just re-flash stock and start again.
What's good, guys? I'm using CM10.0 (relatively)stable on my SGH-i717. I've used the bundled kernel as well as the h0tcakez kernel (currently using that) 3.0.2 and the UCLF6 modem.
These random reboots are exactly what they seem, random. I haven't been able to accurately fund a concrete reason they appear and I've done numerous swaps of sdcard, battery, radio and firmware. Everyone else seems particularly stumped on this one, so this thread is just me doing digging on a good way to read the logs from the last boot. I've tried outputting logcats to a text file on my external sdcard but I have only succeeded in filling up my sdcard or having terminal emulator crash. What I'm going to try next is take my SIM out, put it in my captivate, then plug the note up to my computer, use adb to pull the log and/or the kmsg to my desktop and use tasker or something to run some apps in a cycle to (hopefully) automate the process.
I used the search function and didn't find any threads like this (maybe in blind).
Anyone else have any good suggestions?
Wipe your phone...
I was having pretty much the same problem. I have BB insurance on it, but wanted to see if I could figure out something software wise first. Since I rooted, I've installed pretty much every i717 ROM. I finally settled on flapp's cm10 based one, as it seemed the most stable. After a week of running it, I started to get about >10 random reboots/day. I tried flashing different roms, and sticking with them to no avail. My last ditch effort was to return the phone to stock, see if it still happened, if so, bring back to BB. I hooked it up to Kies, did an emergency flash thru there to get back to stock, but couldn't bring myself to keep it stock for more than 30 seconds. I immediately rooted, and flashed ParanoidKANGdroid. I have only had 1 random reboot in the last 4 days. I'm hoping it stays the same. I briefly tried Xylon and supernexus, but came back to PK, where I will stay (for now anyway). Hope this helps.
Use kies to bring back to stock. (you need your serial number for this, not IMEI)
Root using some method from super everything thread.
Flash favorite rom and enjoy
Also, if you have to update Kies, wait for it to finish. It gets to the point where you think something is wrong and you want to throw your computer away. But after the hangups, it actually finishes the sequence....