I have a nexus 5 on T-mobile running 5.1.1, every time I am on the phone whether it is a hangouts voice call or regular call it gets very hot around 150 F ... ive already tried booting into safe mode still does it...anyone know what I can do or why it does this??
Hardware is damaged
dicecuber said:
Hardware is damaged
Click to expand...
Click to collapse
I don't really understand how it could be hardware?
Android.is.better94 said:
I don't really understand how it could be hardware?
Click to expand...
Click to collapse
Can be as simple as a burned connection on a board. But finding it is another story.
Sent from my Nexus 5 using XDA Free mobile app
Full wipe and flash.
Full wipe.
Full wipe.
Full wipe.
NOT FACTORY RESET. FULL WIPE.
Hope that came across clearly. You might honestly have a "virus" on your phone. I had issues somewhat similar to this after installing a sketchy apk off google because I couldn't afford it at the time. A full wipe and reinstall of my ROM fixed the issue.
I am firmly convinced it was a bitcoin miner malware app or something along those lines.
I am not saying that is definitely the issue, but it can't hurt to try a full wipe and reflash at this point.
fwayfarer said:
Full wipe and flash.
Full wipe.
Full wipe.
Full wipe.
NOT FACTORY RESET. FULL WIPE.
Hope that came across clearly. You might honestly have a "virus" on your phone. I had issues somewhat similar to this after installing a sketchy apk off google because I couldn't afford it at the time. A full wipe and reinstall of my ROM fixed the issue.
I am firmly convinced it was a bitcoin miner malware app or something along those lines.
I am not saying that is definitely the issue, but it can't hurt to try a full wipe and reflash at this point.
Click to expand...
Click to collapse
Can you give an explaination of what you mean when you say "Full Wipe"? How do you achieve this?
Thanks
unlock, and install custom recovery twrp.
boot into recovery, and use the wipe -> reformat option. it will require you to type the word 'yes' before formatting the device if you are at the right screen.
be prepared to immediately flash a rom, as this will completely and entirely wipe the device. the device will not boot without flashing a rom after formatting.
Related
just a quick question, do you have to wipe your phone (alt+w) everytime theres a new rom update? for example if going from JF ADP 1.5 to JF ADP 1.6, do you need to wipe phone before applying the 1.6 update? or is it only necessary to wipe if your going from different roms for example JF to Haykuro..etc..etc
thanks
anyone have an answer to my question?
I'm curious as well. The impression is that you do not as long as you've wiped when you originally rooted.
I'm sure the safe answer is yes, you should wipe but that's a pain in the a**.
You should wipe IMO.
If you don't wipe and run into esoteric issues most likely you will be asked to do so anyways as it is the only useful troubleshooting tool most of these people have because
1.They don't know any better (no ones fault)
2.They don't have time take a look at your debug logs and then instruct you through some most likely intermediate-advanced commands to fix the issue.
Say you moved into an apartment and it's filled with the last occupants stuff. There's a blood stained sofa, stacks of magazine around the WHOLE apartment and a dirty toothbrush. Are you going to be comfortable sitting on that sofa? Would those magazines get annoying? Would you brush your teeth with the dirty toothbrush?
If you have to walk 10 miles, do you wear your own shoes or the last runner's leather shoes that are two sizes too small? If you can even get the shoes on you, you're gonna be in pain and give up within the first mile.
^_^
My answer is: Always wipe. Let the new OS use his own shoes.
ok i understand where you guys are coming from, but what if its only a small update to say JF ADP 1.6, and you are on JF ADP 1.5, it wouldn't make sense to do a wipe just for a small update. am i wrong here. now if ur going from JF to Haykuro then a wipe is definitely necessary. I read somewhere before, that mentioned you didn't have to wipe if you were staying within the same rom. i guess i just need a better understanding on this.
See the quote in my signature
hahaha! ok so I guess I will wipe before applying any new updates. what about the JFupdater app, it says it applys any updates, i dont believe the app wipes your phone before applying it, so is it best not to use the jfupdater when flashing an update?
boricuaace said:
hahaha! ok so I guess I will wipe before applying any new updates. what about the JFupdater app, it says it applys any updates, i dont believe the app wipes your phone before applying it, so is it best not to use the jfupdater when flashing an update?
Click to expand...
Click to collapse
My suggestion is generally this: Try it without a wipe. If it works, then great, you keep all your stuff the way you had it. If you run into issues that seem blaringly obvious(home process crashing, many force closes, boot looping, etc) then go back to the recovery image and do a wipe. There aren't any problems I know of caused by not wiping that can't be solved by going back and doing it after the fact.
[email protected] said:
My suggestion is generally this: Try it without a wipe. If it works, then great, you keep all your stuff the way you had it. If you run into issues that seem blaringly obvious(home process crashing, many force closes, boot looping, etc) then go back to the recovery image and do a wipe. There aren't any problems I know of caused by not wiping that can't be solved by going back and doing it after the fact.
Click to expand...
Click to collapse
thanks! thats exactly what i was thinking but wanted to be sure.
now wiping wouldn't mess up any links to the sd card(apps2sd) correct? wiping basically justs wipes the data from the phone....i guess what i mean is would I have to set up apps2sd again?
i'm with marcus, if you can get away with not wiping great, if not oh well wipe. or you could perform a nandroid bakup and then wipe, then after the update just fastboot flash your data.img
boricuaace said:
now wiping wouldn't mess up any links to the sd card(apps2sd) correct? wiping basically justs wipes the data from the phone....i guess what i mean is would I have to set up apps2sd again?
Click to expand...
Click to collapse
You would only need to restore the symlinks (if that's the method you were using).
I am relatively new to flashing ROMs & kernels for Android. Currently I'm using MIUI 1.5.6 and would like to upgrade to the newest version of 1.5.13.
My question is, do I have to wipe data if I'm just upgrading to the same ROM or would wiping cahce & Dalvik cache be sufficient?
Before anyone flaming me I have searched the forum prior to posting and surprisingly didn't find anything useful as I thought this would be a frequently asked question.
Thanks in advance!
I never clear if i'm gonna do the same rom and it seems to work perfect. So I'd say dont it takes less time but if your worried do it. clearing that stuff wont really loose anything so its your choice really
I think you ALWAYS should do a backup, just in case something goes wrong.
You have the device at the Computer, you have the cable hooked up.
What would it take... about 5 minutes to do the backup up ??
oddball69 is right. You should always do a wipe.
Just to avoid problems
Most of the Devs will specify for each version if a full wipe is not required. If you can't find anything about it then do a full wipe.
If they directly say a wipe is not required then it's probably just some small fixes.
Thanks for all the responses.
I was going to do a backup for sure I just wanted to avoid having to wipe everything and then reinstalling and re-setting up all my apps which could be quite a pain
Depends on the ROMs used, usually the developers state if this is necessary.
It wont hurt if you try without wiping, if it makes problem just wipe and do it again.
What is there to loose?
Hey guys,
I'm running the Octane ROM on my SGS4G, and suddenly both my home and search touch keys stopped functioning. However, they ARE triggering haptic feedback (a vibration in the phone when pressed)
Does anyone know what causes this and what's a common trouble shooting route?
I updated my binary in super user and updated busybox...nothing changed.
Also, I don't know if this is related to the problem but it happened at the same time: text msg notifications are permanently as if the phone is on silent; no sound or vibration. Just a status bar icon.
Thanks in advance to anyone who can help, this phone is my only daily.
Sent from my SGH-T959V using XDA App
Have you rebooted the phone? If so, I'd suggest doing a backup then performing a factory data reset.
Yea I rebooted several times..
could I just wipe the dalvik?
If I only do that, what information is lost on my phone?
Also the update from busy box said it might require I do a package reinstall "without" a factory wipe for the update to take effect... Any suggestions on that?
Sent from my SGH-T959V using XDA App
Stafaa said:
Yea I rebooted several times..
could I just wipe the dalvik?
If I only do that, what information is lost on my phone?
Also the update from busy box said it might require I do a package reinstall "without" a factory wipe for the update to take effect... Any suggestions on that?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
You could always try wiping caches first. No data loss that way. The Davlik cache will rebuild itself over time.
I'm nto sure about BusyBox, though. Maybe someone else has an idea?
What about the cache partition?
I guess my question is, what exactly are you wiping when you wipe the dalvik and when you wipe the cache partition?
and is it a safe practice for when strange problems like this arise?
Just wiping the cache.completely safe and the first thing to try after a reboot.also I would suggest fixing permissions when clearing the cache
Sent from my SGH-T959V using Tapatalk
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Stafaa said:
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Click to expand...
Click to collapse
Fix permissions in the advanced option of cwm
And no factory reset does not wipe sd unless you tell it to when you're doing it from your settings menu
Sent from my SGH-T959V using XDA App
ah, gotcha.
Wish I woulda have tried that before wiping.
Another question: After the wipe, I lost all the fonts that were originally there after I first installed Octaine ROM.
I'm thinking I should just reinstall the package, but I'm afraid I cant remember if I had to disable VOODOO lagfix first and whether or not i still have to change the mounting points before i reinstall the rom..
Stafaa said:
ah, gotcha.
Wish I woulda have tried that before wiping.
Another question: After the wipe, I lost all the fonts that were originally there after I first installed Octaine ROM.
I'm thinking I should just reinstall the package, but I'm afraid I cant remember if I had to disable VOODOO lagfix first and whether or not i still have to change the mounting points before i reinstall the rom..
Click to expand...
Click to collapse
Glad you got it working though sucks you had to wipe everything. To be safe I would disable voodoo though I do not know if it's necessary. Definitely go into CWM and re-check the mounts first before flashing.
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Stafaa said:
Well I found the answer to what they both are Here
Figured I'd post it for anyone who every comes across this thread.
But thank you for going into more detail about it Somairotevoli.
where is it i fix permissions? In super user you mean?
And i just finished doing a full wipe =/
fixed the problem...but just sucks. Im glad i removed the SD card before hand, I think it tried to format it.
Does a factory wipe touch any SD files?
Click to expand...
Click to collapse
I'm running the Octane rom too, and have started having problems with all four buttons, but mainly the outside settings and search ones. Other roms do the same for me now, so I don't think it's the problem. I have fully wiped, reformatted, fixed permissions, you name it.
It dosen't seem to matter what happens, they still resist working properly. So are you saying that doing a wipe/reinstall/permission fix did it for you? I can't tell if it's a physical thing or a software thing, but I'm leaning more toward software.
Stafaa said:
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Click to expand...
Click to collapse
You should probably re download your desired rom, do a full wipe (data, cache, and dalvik) and re flash. this sucks but should work. Did you by chance ever flash a kf series 2.3.3 ROM?
Sent from my SGH-T959V using XDA App
Stafaa said:
Well, unfortunately, after a full wipe... everything worked fine for one day... then suddenly the phone froze and restarted. After reboot, some apps had the android image on their icon and ALL OVER my wallpaper was a skull and cross bones image...cascaded in rows and columns all over the background..
and ofcourse.. my home and search buttons are non-functional once again...
What does this mean??
Click to expand...
Click to collapse
After the wipe did you install a new ROM or stay on Octane? Maybe try wiping & install Raver's KJ6 stock via Odin or CWM. Run stock for a few days and see if the problems persist.
Sent from my SGH-T959V using XDA App
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
alexdzk said:
So I bought a Nexus 5 off of craigslist for a pretty good price about a week ago and he had already rooted and installed a custom recovery onto the phone. He had some sort of rom that I didn't like so I decided to flash my own. So I downloaded cyanogen mod (the latest nightly build at the time) and flashed it along with g apps and rebooted the phone. When I it was turning on it said "upgrading apps xxx out of xxx." I was very confused because coming from a Nexus 4 and flashing many ROMs I have never seen this before. When the phone finally powered on it started giving me errors every 5 seconds and I realized soon after that I had my previous apps from the old rom still installed and everything else was in place. I managed to get into settings after clicking ok to errors every 5 seconds and saw that my ROM did indeed change to Cyanogen Mod. I decided to try to factory reset the phone through the settings menu and that fixed the phone seemingly until today. I tried installing another rom but this one is giving me multiple errors and then rebooting my phone. I could not get into the settings to factory reset the phone through there.
I was thinking that maybe the recovery was broken but I'm not sure of how to fix it. I tried to find a flashable recovery but only found IMG versions which I don't know how to install. Is there a possibility of any other issues? I am resetting/wiping cache/wiping dalvik cache every time in that order. When I'm installing the roms it says something about e:/ volume not existing or not being found could that be the problem? I don't recall ever seeing this on my nexus 5. If anyone knows how I could fix this issue I would greatly appreciate your help.
Thanks, Alex:laugh::laugh:
Click to expand...
Click to collapse
Did you wipe data and cache before flashing the new rom?
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
jd1639 said:
I see your doing a clean install. I'd return it to stock and start over, especially considering you bought the phone used. Who knows what's been on it. See this http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
I'll try this then if it doesnt work ill try the factory reset/ relock whatever, thanks.
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
no its CWM
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
mistahseller said:
This happened to me loading some ROM previously. You need to make sure that you do a factory reset and wipe the cache and dalvik. I also redownloaded the ROM just to be sure but I do not think that is necessary. It sounds like you dirty flashed. Is the recovery Team win? If so there is a setting under mount that you need to uncheck and it is called system.
edit: I re-read and saw that you are wiping the cache and dalvik cache, by resetting do you mean you are factory resetting? The img files are for you to do through the command line in fast boot and you can find out more by clicking this link: http://forum.xda-developers.com/showthread.php?t=2507905 and also this link: http://forum.xda-developers.com/showthread.php?t=2513701. <--- familiarize yourself with both of those threads and you will be better off than a lot of people that come asking for help. Not saying that you are not well off just knowing is good for the soul.
2nd edit: Since it sounds like he did not wipe the SD card were there good things on there?
Click to expand...
Click to collapse
housry23 said:
You didn't wipe/factory reset.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. I said it in my post.
alexdzk said:
Yes, I did. I said it in my post.
Click to expand...
Click to collapse
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
housry23 said:
I see. Well, if you really did do a factory reset before flashing a new Rom, then maybe you have an old version recovery, or something is borked with your phones partitions. Honestly, buying a used one like that, I would do a full factory restore by flashing the stock images(sticky in general for directions) but don't relock the bootloader. This will erase everything and repartition the phone. Then install recovery and flash away.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
alexdzk said:
I fixed the issue by flashing a new recovery through adb already and it works fine now thank you. I guess it was really my recovery that was broken.
Click to expand...
Click to collapse
Good. Glad you got it worked out. Was probably an old build of whatever recovery and because of the way KitKat changed things, there were a lot of problems wiping when the phone first came out. If you find any more good deals on your local Craigslist, PM me. I want a black n5 instead of my white one.
Sent from my Nexus 5 using Tapatalk
Hey all,
So ever since I updated my OPO to Cm12.1, I've been having boot issues. Essentially, what happens is when booting the phone, the phone is forever stuck on the OnePlus Logo without going ahead to the Cyanogen Logo and then the phone starting up. The way I deal with this is, I boot up into stock recovery and then "Clear Cache Partition" and then I reboot a couple of times, and this works and has worked for me over the last couple of weeks. However, I wanted to know how can I get rid of this issue once and for all, so I'm able to boot the phone normally without having to clear the cache partition all the time.
Thanks
Did you wipe properly when updating?
I think so,do you think that's the reason I'm having issues?
What would you recommend to sort it all out?
dialsquare1886 said:
I think so,do you think that's the reason I'm having issues?
What would you recommend to sort it all out?
Click to expand...
Click to collapse
It's possible. I'd perform a full wipe (system, data, cache, dalvik cache) and flash again.
If you don't mind, could you share links that describe the easiest way to do all those things.
Thanks!
dialsquare1886 said:
If you don't mind, could you share links that describe the easiest way to do all those things.
Thanks!
Click to expand...
Click to collapse
Here's one I prepared earlier:
http://forum.xda-developers.com/showthread.php?t=2839471