Related
I was able to boot into android perfectly fine until about a week ago where it would just hand at the boot screen. today i tried to fix it by formatting my sd card and doing a clean install. now i can boot into android perfectly fine, but if i leave my phone idle and let it sleep, after a couple of minutes a green led will turn on and my phone will not wake up and i am forced to reset my phone.
anyone know what the issue could be? i flashed a new rom today, but i doubt that has anything to do with this.
is my sd card bad?
viper786 said:
I was able to boot into android perfectly fine until about a week ago where it would just hand at the boot screen. today i tried to fix it by formatting my sd card and doing a clean install. now i can boot into android perfectly fine, but if i leave my phone idle and let it sleep, after a couple of minutes a green led will turn on and my phone will not wake up and i am forced to reset my phone.
anyone know what the issue could be? i flashed a new rom today, but i doubt that has anything to do with this.
is my sd card bad?
Click to expand...
Click to collapse
Do you have it overclocked in your startup.txt? That will cause this issue.
ahh yes, i overclocked it to 700mhz. so basically, i cant overclock at all without facing this issue?
Does anyone know if the Windows Mobile ROM on the phone affect how high one can go with an overclock? Like would using the stripped down ROM help to achieve a higher clock speed as opposed to using a loaded ROM like EnergyROM?
Yes, it seems the OC will crash android once it tries to sleep. One workaround some people have said works is add "htc_battery_smem.fake=1" to your startup.txt cmdline. Your phone will not crash anymore, however your battery life will be a little shorter due to the fact its not sleeping as deeply.
Hey i just bought this Galaxy Nexus from a Guy. At first it worked perfectly but after a few minutes it rebooted non stop.
So after i got home i've reflashed the Stock Google rom with the Toolkit, it change nothing so i put a custom rom on it, it change nothing (tried ParanoidAndroid, CM9, Kang...).
SO flahsed a different Stock rom through GN Toolkit. Stil the same. Flashed trought ODIN nothing (even thought the Odin rom was an old).
Right now it boots. I can use it 4 or 5 minutes and:
-The android system restart and go to the Bootanimation.
or
-The shutdown very quickly in a *pop sound. Et restart from beginning.
I think i'm going to send it to the repaire center. But i had 2 alaxy Note which i've bricked due to the SuperBrick problem. And i took the GN to have no issue with Android. Turns out i have...
I'm sorry if this has been before but i can't find a solution. And i'd like to have a phone tomorrow.
Thanks to everyone who will help me or even read this.
Atomos33 said:
Hey i just bought this Galaxy Nexus from a Guy. At first it worked perfectly but after a few minutes it rebooted non stop.
So after i got home i've reflashed the Stock Google rom with the Toolkit, it change nothing so i put a custom rom on it, it change nothing (tried ParanoidAndroid, CM9, Kang...).
SO flahsed a different Stock rom through GN Toolkit. Stil the same. Flashed trought ODIN nothing (even thought the Odin rom was an old).
Right now it boots. I can use it 4 or 5 minutes and:
-The android system restart and go to the Bootanimation.
or
-The shutdown very quickly in a *pop sound. Et restart from beginning.
I think i'm going to send it to the repaire center. But i had 2 alaxy Note which i've bricked due to the SuperBrick problem. And i took the GN to have no issue with Android. Turns out i have...
I'm sorry if this has been before but i can't find a solution. And i'd like to have a phone tomorrow.
Thanks to everyone who will help me or even read this.
Click to expand...
Click to collapse
Well, have you tried doing a battery pull, leaving it for 1-2 hours and then restarting the phone?
That's just one way... Before freaking, chill...
Whether you want it, or not; I'm going to tell you, what your phone is doing.
It's not restarting, every time it restarts with the *pop* sound, it's rebooting, from a crash. Every time it restarts, directly to the bootanimation, it's doing a hot reboot...
You're doing a very sensible thing, sending it in, because this is a definite hardware issue, that's why the guy probably sold it... Anyways, before you send it in, relock the bootloader (Enter fastboot and type
Code:
fastboot oem lock
)
Then make sure you have a stock firmware...
What I think is causing these problems? The guy who sold you the phone probably overclocked & overvolted that phone too much and for too long.
familyguy59 said:
Well, have you tried doing a battery pull, leaving it for 1-2 hours and then restarting the phone?
That's just one way... Before freaking, chill...
Whether you want it, or not; I'm going to tell you, what your phone is doing.
It's not restarting, every time it restarts with the *pop* sound, it's rebooting, from a crash. Every time it restarts, directly to the bootanimation, it's doing a hot reboot...
You're doing a very sensible thing, sending it in, because this is a definite hardware issue, that's why the guy probably sold it... Anyways, before you send it in, relock the bootloader (Enter fastboot and type
Code:
fastboot oem lock
)
Then make sure you have a stock firmware...
What I think is causing these problems? The guy who sold you the phone probably overclocked & overvolted that phone too much and for too long.
Click to expand...
Click to collapse
Thanks! I just wanted to make shure it wasn't a software problème. I thought about the overclocking and overvolting i just wanted to make shure it wasn't software.
It's been two day. I left the phone without battery for two days.
You think if i flash a custom Rom and undervolt and underclock the processor it will work? Is it a good idea? I need a phone tomorrow ^^'
Atomos33 said:
Thanks! I just wanted to make shure it wasn't a software problème. I thought about the overclocking and overvolting i just wanted to make shure it wasn't software.
It's been two day. I left the phone without battery for two days.
You think if i flash a custom Rom and undervolt and underclock the processor it will work? Is it a good idea? I need a phone tomorrow ^^'
Click to expand...
Click to collapse
Sure, why not? It's worth a try. Just don't undervolt too much, leave the CPU at min. 700 MHz, and set voltage on 700 MHz, to 900-950 mv.
Do that, and it may just be daft enough to work
Thanks!
Fast and great answer!
If you have already flashed stock image then you would have had the stock kernel which runs at stock speeds and stock voltages. If it didn't work then lowering the CPU clock speed won't work. Its not even a solution to your problem.
If it won't work with completely stock image then all you can do is send it back, sounds faulty to me.
nodstuff said:
If you have already flashed stock image then you would have had the stock kernel which runs at stock speeds and stock voltages. If it didn't work then lowering the CPU clock speed won't work. Its not even a solution to your problem.
If it won't work with completely stock image then all you can do is send it back, sounds faulty to me.
Click to expand...
Click to collapse
I didn't say that, either. I said it's worth a try. Read my first post (I think it was) and you'll see that I said it's better to send it in ^^
But this is worth a try, just to double-check...
Jelly Bean saved my Nexus
Was having this same problem, flashed CM9, AOKP, stock (every version) to no avail. Saw that JB dropped on XDA and flashed that just to play with it, thought my phone was borked but I just wanted to screw around. Totally revived my phone. Haven't had a single reboot in the 12 hrs I've been using it (coming from a reboot every few min). Just as a further note I was wiping everything when I flashed (battery stats, Dalvik, data...). PS JB rules hardcore!
I myself have been having random reboots with this nexus.
Actually picked up this phone 3 days ago new from Verizon so the phone hasn't been rooted/unlocked yet.
I want to love this phone. But the bootloops,etc is making it difficult for me.
Might have to succumb to the sgs3 as the last resort. :L
Alright guys, basically whats happening to my phone is that I would just have my phone randomly surfing the web or checking Facebook then out of nowhere it just randomly reboots. Most of the time it ges stuck on the Google screen and I had to do a battery pull and retry and after a while of repeating that it finally would load properly. .Also my phone would say that its charging even when the charger isn't even in and even it reboots sometimes it shows the charging screen when i haven't even plugged the charger in
If you guys can solve this wouthout favtory reseting that would be great !
DETAILS
-Not rooted in anyway
- Android 4.2.1
- Got it about 7 or 8 months ago
- this happened before but it would just reboot it wouldnt do anything else, I reseted it and it went away but now its back and its worse.
Any answer would be greatly appreciated!!
Thanks
Sorry to say but when your phone is to the point where it has issues that seem to be system deep, the only thing you can do that is almost guaranteed to fix it is flash the factory image to your device. This is different that doing a factory reset which doesnt really do a full system wipe and reload as far as I know. Instructions can be found here:
http://forum.xda-developers.com/showthread.php?t=1626895
Note that you will need to backup everything off your storage (files/pictures/music/etc.). This will wipe your device clean.
Lastly, if your device thinks it is charging when its not, you could have a bad port. Hopefully its just the system though which can be fixed with the above suggestions. If not, you might need to have it fixed if possible. But it sounds like a system issue.
Hey guys,
since ~a week I got a heavy-ass problem with my Samsung Galaxy Nexus (GSM). I am using the Cyanogenmod Nightly Version cm-11-20150412-NIGHTLY-maguro.zip (bootloader version primemd04; cwm version 6.0.5.1). I know that nightly versions are not really stable and still have a lot of problems, but so far everything didn't went that badly. At least I was able to use the phone...
So last week I put my phone in airplane mode. That was when the disaster started.
Now what happens when I start my phone is, that it starts in airplane mode with wi-fi on and no matter what I do, restarts after ~1min. Sometimes it even shuts down, when starting it in recovery mode.
What I tried so far is:
factory reset ---> most of the time it shuts down halfway done and restarts as if nothing happened.
updating CM ---> restarts as if nothing happened.
I'm really lost right now, but still don't want to give up all hope.
Thanks for every kind of help!!
Cheers,
Lovis
Try to get a legit application that tells you the real CPU temperature like FKUpdater, in case you have franco.Kernel. Then just run heavy tasks on in. If it just ****s doen,might be a problem with the battery. Mine just shutdown on itself just by doing common tasks like calling. Replacing the battery fixed it. Another thing O realized was that if you plug it in the charger and use it was helping it not restart. Try this method. If it restarts then its pretty much a ROM or hardware related problem, if not then a battery problem for sure.
Sent from my Galaxy Nexus
It has to be some kind of ROM problem. Before I got in airplane mode the phone worked almost perfectly.
AdmiralulNipples said:
Try to get a legit application that tells you the real CPU temperature like FKUpdater, in case you have franco.Kernel. Then just run heavy tasks on in. If it just ****s doen,might be a problem with the battery. Mine just shutdown on itself just by doing common tasks like calling. Replacing the battery fixed it. Another thing O realized was that if you plug it in the charger and use it was helping it not restart. Try this method. If it restarts then its pretty much a ROM or hardware related problem, if not then a battery problem for sure.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
My phone was working fine and all of a sudden, it restart on me and started bootlooping.
I recently upgraded to 7.1.2 from MM, installed magisk, and like a few days ago, installed xposed.
I'm trying to find out if it's hardware related or it could be an xposed module.
Problem is, i can't even get into recovery.
I turn on phone, get the 'device is unlocked' screen, goes to the google screen, and reboots (~15 secs)
I am able to get into bootloader mode, but when i select recovery mode, the same thing happens
ok, i'm 70% sure it's hardware related...
i put the phone in the fridge, started the phone, and I am able to get to 1-3 secs of the boot animation before it bootloops
so sad right now...
ok, i'm 70% sure it's hardware related...
i put the phone in the fridge, started the phone, and I am able to get to 1-3 secs of the boot animation before it bootloops
so sad right now...
anonxlg said:
My phone was working fine and all of a sudden, it restart on me and started bootlooping.
I recently upgraded to 7.1.2 from MM, installed magisk, and like a few days ago, installed xposed.
I'm trying to find out if it's hardware related or it could be an xposed module.
Problem is, i can't even get into recovery.
I turn on phone, get the 'device is unlocked' screen, goes to the google screen, and reboots (~15 secs)
I am able to get into bootloader mode, but when i select recovery mode, the same thing happens
Click to expand...
Click to collapse
r.i.p. There are modified boot.imgs floating around here on XDA, flash those and you should be able to get into Android to at least get data off (they basically disable the big A57 cluster of CPU cores). As far as a permanent fix you should get a few more months out of the phone with the big cores disabled.
Try to avoid extreme temperatures/deviations- while mine is not bootlooping I'm a generally light user- I don't need the big cluster at all, and even more I underclock my little cores.
I am having the same issue with my Nexus 5X: I can (sometimes) get to the bootmanager. But when I try to boot recovery (which I have flashed to TWRP,) I get the "Google" boot banner image (with the unlock icon at the bottom.) This is still a bootloop, though. I can re-flash recovery with fastboot, but it still shows the "Google" banner and bootloops after that.
I regularly got the device very hot using video chat applications (Duo, Hangouts,) and if this is a hardware issue, I wonder if the extreme temperatures (85C+ at the worst) contributed.
negusp said:
r.i.p. There are modified boot.imgs floating around here on XDA, flash those and you should be able to get into Android to at least get data off (they basically disable the big A57 cluster of CPU cores). As far as a permanent fix you should get a few more months out of the phone with the big cores disabled.
Try to avoid extreme temperatures/deviations- while mine is not bootlooping I'm a generally light user- I don't need the big cluster at all, and even more I underclock my little cores.
Click to expand...
Click to collapse
it's funny you mention that
it's not the same thing, but I did have elementalx installed, i changed my governor to interactive - glassfish 1.2
i actually DISABLED big cluster on startup
i did this when i upgraded to 7.1.2
my phone bootlooped this morning when i turned it on to send a message, so the phone was definitely cool/room temp, when it did happen
I spoke to google support, they're able to replace my phone with a refurb and for me to send the current device in (even though it's out of warranty), so i dont think i'll want to try to flash that boot.img with the disabled big clusters.
Do you have a link for the boot.img file? My wife's phone started this yesterday.
duckredbeard said:
Do you have a link for the boot.img file? My wife's phone started this yesterday.
Click to expand...
Click to collapse
There's something called "search" here on XDA. Use it.
Or, simply Googling "bootloop nexus 5x xda" would yield you results.
negusp said:
There's something called "search" here on XDA. Use it.
Or, simply Googling "bootloop nexus 5x xda" would yield you results.
Click to expand...
Click to collapse
This search you speak of sometimes yields dead links and more threads where people are asking for help, often without answers.
This is a help thread, your approach to my question was without substance or tact. Learn etiquette. And use it.
duckredbeard said:
This search you speak of sometimes yields dead links and more threads where people are asking for help, often without answers.
This is a help thread, your approach to my question was without substance or tact. Learn etiquette. And use it.
Click to expand...
Click to collapse
What would help you the most would be an optometrist.
This is literally the top post in General and top of "Most Active", not to mention that it's linked in dozens of various news articles featured on Google.
retc3 said:
I am having the same issue with my Nexus 5X: I can (sometimes) get to the bootmanager. But when I try to boot recovery (which I have flashed to TWRP,) I get the "Google" boot banner image (with the unlock icon at the bottom.) This is still a bootloop, though. I can re-flash recovery with fastboot, but it still shows the "Google" banner and bootloops after that.
I regularly got the device very hot using video chat applications (Duo, Hangouts,) and if this is a hardware issue, I wonder if the extreme temperatures (85C+ at the worst) contributed.
Click to expand...
Click to collapse
Large deviations/quick deviations in temperature contribute to the bootloop (apparently a poor soldering job by Qualcomm).
There have been a couple "quick fixes" to get into recovery, including putting the phone in a freezer or attempting to reflow the CPU by putting the motherboard in an oven.