Hi there! I´ve got some issues with my gnex lately: I clean installed PA 3.99. Every went well for a couple of Days, including turning on and turning off the phone.The one strange thing happend. I installed an app, baammm, first reboot. Hm. Phone came up quickly, then baamm, second reboot. From then things went downhill... Stuck at Google-Logo. Had to pull Battery. Factory reset.
Now, everytime I boot the phone it is stuck at the Google-Logo. I have to install the ROM again and then it boots up. One time. I flashed the latest bootloader, which did not help.
Any ideas?
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
astarman said:
ive got this problem as well. probably worse.
ive got the latest nightly of carbon installed.
however once i reboot it is stuck at the google logo!!!!
im not sure if i need the latest bootloader or if im missing soemthing!
i came from a 4.2.2 rom .
Click to expand...
Click to collapse
Yeah, pretty bad. At the weekend maybe I'll try to flash stock factory image. Hope that helps. But I've seen some things here at the forum. I'm slightly scared...
Sent from my Galaxy Nexus using xda app-developers app
Related
Today when i got home i turned on Wifi and suddenly my phone went into a boot loop.. It doesnt get past the "Google" logo at the beginning and just keeps rebooting every 5 seconds.. I have tried doing a hardreset restoring to factory settings but that didnt work.. It is rooted.
Can anyone help me fix this?:/
What Rom/Kernel are you on? Can you get it into download mode? Have you tried restoring a Nandroid? Have you tried a fresh install?
I had the CM9 3/29 nightly running. Had the phone in desktop mode all night. This morning it started rebooting after coming to the home screen, and then situation is getting worse, it reboots after every boot. I had a good CM9 nandroid back up, restored and still doing the same thing.
CM9 nightly, no separate kernel, just some tweaks and was @1350 under performance.
Can there be some hardware damage?
Help please!!
---------- Post added at 09:54 AM ---------- Previous post was at 09:51 AM ----------
Phyxius said:
Today when i got home i turned on Wifi and suddenly my phone went into a boot loop.. It doesnt get past the "Google" logo at the beginning and just keeps rebooting every 5 seconds.. I have tried doing a hardreset restoring to factory settings but that didnt work.. It is rooted.
Can anyone help me fix this?:/
Click to expand...
Click to collapse
Was your phone continuously on, and got hot by any chance?
Don't run performance governor. Also just do a full wipe system and data and flash a known stable CM9 build. That should get you up and running.
Sdobron said:
Don't run performance governor. Also just do a full wipe system and data and flash a known stable CM9 build. That should get you up and running.
Click to expand...
Click to collapse
Done, no go there. One thing I am noticing is a "pop" sound just before it reboots
This happened to me 2 months ago. The way I fixed it was by putting it into download mode and flashing 4.0.1 YAKJU via the ODIN file found on the Samsung German website. Phone has been good ever since. *knock on wood*
EDIT: BTW, after that, I updated to 4.0.2 OTA normally, and since then, I've been manually updating because I rooted my phone.
Sent from my Galaxy Nexus using XDA App
wiki_warren said:
This happened to me 2 months ago. The way I fixed it was by putting it into download mode and flashing 4.0.1 YAKJU via the ODIN file found on the Samsung German website. Phone has been good ever since. *knock on wood*
EDIT: BTW, after that, I updated to 4.0.2 OTA normally, and since then, I've been manually updating because I rooted my phone.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Yes thats the only way to do it.
Installed the rootkit 5.6 and downloaded the 4.0.4 into the corresponding folder.
Sure wiped my phone completely, but I don't have a $600 paper weight.
Thanks all!
Search did not give any results i guess. Finally got the nexus up and running again / was on CM10 and had neglected to wipe data when flashing the 4.2.2 factory image. It was pretty weird, I think. The phone had sat on the 'X' screen time after time, minutes not counted.. I had at first vol up/ vol down / power and had gotten a red exclamation for some reason. Eventually got into fastboot, I had used the toolkit by mskip / reflashed the 4.2.2 image , made sure to clear data and all works fine. When flashing a custom rom it sticks on the google unlocked screen. Why? What is the problem? How does this fix itself or going about it to get it fixed? ....... Again, if this is a stupid question and you have easily found the answer by all means pass along the right keyword. If this is not a stupid question, you don't think, and are cool about helping me out, by all means, please do so.
Edit . I had flashed stock then custom rom on another device with only the usual, i guess, load time. The best advice search forums gave me was , just wait'.
http://forum.xda-developers.com/showthread.php?p=38127432
Flashed cm-10.1-20130217-NIGHTLY and got stuck on the "Google" logo on reboot. Booted to recovery and installed the Feb 16 build and all is good. Hopefully the next nightly works well.
From the CM thread.
Hello.
Try to flash the 2013.02.17 nightly AND some 4.2.2 kernel.
I tried with LeanKernel 6.0exp1 and it works
There are reports with working flashed 2013.02.17 with Franco's Kernel latest too.
vfmmeo said:
hello.
Try to flash the 2013.02.17 nightly and some 4.2.2 kernel.
I tried with leankernel 6.0exp1 and it works
there are reports with working flashed 2013.02.17 with franco's kernel latest too.
Click to expand...
Click to collapse
perfect work.
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
JonnyZaggi said:
Hey the Problem is the following:
3-5 random reboots every day
restarts during every phonecall after 1-3 Minutes
freezes when in standby, cant turn back on -> need to take battery out
often slow, especially when switching apps. or when typing
I have tried stock 4.3, CM10.2 recently and before that CM10.1 for a while.
I already send it in but they only said my battery is broken.
Is it possible that all my problems come from this?
I rather think my flash memory is broken? What you think?
Click to expand...
Click to collapse
Since yesterday I am facing the same problems you are describing. At first I thought it was a bad flash or something like that. Clean installed various 4.3 costum roms and it's always the same.
Right now I will look deeper into it since the phone is unusable in that condition.
If I find a solution I will comment.
Best regards
Edit: Okay, works again flawlessly. I simply flashed an nightly from carbon-rom and the lags were gone. Hope it helps. What exactly caused the lag I don't know. For now I am staying on 4.2.2 Carbon as it is my favourite rom anyway and I will wait till there are stable 4.3 from carbon.
Are you sure it's the phone and not an app?
chrisinsocalif said:
Are you sure it's the phone and not an app?
Click to expand...
Click to collapse
Not pretty sure, but it still occured after countless factory resets, wipe cache, wipe dalvic cache and wipe system via TWRP.
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
chrisinsocalif said:
Have you tried a clean install without installing apps to see if you get a reboot to eliminate an app as a possible cause?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yes I did. I only flashed for example newest PA and their PA Gapps.
So far I resolved it by "downgrading" to a 4.2.2 nightly from carbon. The lags are completly gone. I will stay and wait till carbon has stable 4.3.
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Zepius said:
why dont people try stock when they are having problems? going from 1 custom rom to the next does not prove it is the phone.
please fastboot flash the stock rom and do not restore any apps/data other than say your google acct
Click to expand...
Click to collapse
Already did that.
I am having the same/similar problems with my GNex too. Specifically bullets [1-3] from the original post. I am running unmodified yakjuux and have tried with just my google account with no other apps and the same problem exists.
Mine makes a noticeable "click" sound with a vibration followed by a reboot.
It usually happens during calls and after it boots the phone call log shows no record of the incoming/outgoing call that just happened. Its like a blue screen of death for android!
I have sent the phone back to Samsung's warranty service 4 separate times and each time they reported no trouble found in the completion report. They just factory reset or put an older version of jelly bean back on the phone and send it back to me with some notes of PRL updates and other nonsense to make it seem like they did something to fix it.
Does anyone have any suggestions (logs, adb, etc) how I can help prove to Samsung/service absolute that the phone is a lemon (other than trying to video tape the phone hoping it reboots - because that is the last resort)?
I already escalated to executive customer service and they refused an exchange because the completion reports show no trouble found :crying:
Thx!
well... I also have this problem.
First happened when I flash Cm10.2 nightly (don't remember which one).
Then I flash PA, or whatever... Looks like the random reboot relating to notifications? It's usually happened when whatsapp notification coming in, but not always.
But a few weeks ago I flashed stock ROM rooted (via TWRP, not fastboot).
The problems solved. No random reboots anymore. Then today I tried latest CM10.2, and it happened again... Wonder why... Looks like it's a very rare problems.
Interesting to see someone having the same problem...
Now I want to flash stock ROM via fastboot to check if it'll fix.
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
lonestrider said:
Btw, I can flash directly to CM 10.2 from 10.1, can't I? Or I should flash 4.3 via fastboot first?
Click to expand...
Click to collapse
I believe CM offers an upgrade option somewhere in the system settings. Unless you want to wipe your phone and flash directly to 10.2 in which case I do not think you need to flash stock 4.3 first. Maybe just do a reset within 10.1 before you flash CM10.2 via whatever recovery (clockwork etc) you are using but even that may be unnecessary.
My 1 year warranty expires this month so if I can't manage to get something out of Samsung I am going to play around with flashing stock 4.3 as you suggested. I have tried converting yakjuux to yakju in the past but still saw the problem then which made me revert back to yakjuux so I could send the phone back for service).
Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??
Go in twrp and make factory reset
just tried that, didnt work
Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.
yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.
cant even adb whilst its booting.. getting waiting for device.
What version of twrp are you using?
2.8.6.1
philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.
I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.
Hello everyone. Since the Title has character limit im gonna have to explain myself here better.
Ive had my HTC One M8 for 4 years now. Pretty much since it came out in 2013. I installed ARHD back in 2014 and its been working just fine ever since. A couple of months ago i decided to go back to 45.0. Everything went smooth and everything works just fine.
But a week ago the phone decided to just go woopdido and it wouldnt open up any apps in Playstore although i could still see them. So i tried to restart it and when i did it got stuck at the HTC Logo. I tried to restart it a few times but it kept getting stuck. I was super confused due to the reason that i havent really done anything with my phone besides since the day i installed ARHD 45.0. I got desperate so i reinstalled it but this time with 53.1 and that went fine too except for one fishy thing and that was that i remember before when installing ARHD, when it got 30% it wouldnt take 2-3 minutes for it to finally start installing the ROM. It would take a couple of seconds for it to start right away and be done.
After installing 53.1 phone worked just as fine except for the fact that it was slower than it has ever been before. Which was also weird. Either way. After a couple of hours of it working, setting up every app i needed i restarted it and again it was stuck at the HTC Logo. Welp i guess..
So after that crap i went back to 45.0 again. It went good and all except it keeps getting stuck at 30% for a while but whatever. Going back to 45.0 though didnt help. Keeps repeating the same crap after a while. After a restart when having the phone doing nothing for hours gets it stuck at HTC Logo again. I literally cannot do anything with it atm and i have no clue how to go further from here as i have not had this before.
The HTC One M8 is rooted. S-Off everything you really need. The current TWRP version i have is 3.1.1.0.
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
redpoint73 said:
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
Click to expand...
Click to collapse
It was released in 2014? Welp why did i think it was 2013? Either way.
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right. The firmware is fine and all for the current version i have. It was for 53.1 too.
And out of the blue it just got stuck on the HTC Logo. I tried something and it was updating the SuperSU which actually was the reason why it got stuck on the HTC Logo. I installed 2.79 and now it boots just fine and the phone is back on speed again. Apparently 2.82 has issues which is the version i assume it tried to update to through both TWRP and Playstore.
sp3tan said:
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right .
Click to expand...
Click to collapse
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
redpoint73 said:
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
Click to expand...
Click to collapse
Yeah it does. I also forgot to mention that my microphone went to sh*t also. But its not because of this event. Although after this last reinstall i did the microphone picks up my voice better than it did before it went crap. But people cant still hear me when they call me