Device Reboots at Regular Intervals - Nexus 5 Q&A, Help & Troubleshooting

Hi
My device runs on AOSIP Hammerhead 2.2 ROM with Solo Gapps. Everything was fine until 2 a couple of days back my device started rebooting at regular intervals. Sometimes when I unlock the screen it reboots, or which working with some application it reboots. After suggestions from some friends I did a dirty and clean flash as well and did a fresh flashing of the ROM + Gapps. But it still ain't resolving my problem. I hope somebody could help me out here and is appreciated.
PS: I am a rookie to these concepts and terminologies.
Please help!!
Regards
Vyshak

Does it reboot with a stock ROM? s the cpu overclocked?

Related

[Q]

help please newbie in a panic installed custom rom (*updated* htc 2.1 rom) everything went fine until reboot it wont reboot seems to be trying vibrates every 30 seconds or so but nothing happening
What device model/phone do you have?
What Custom ROM did you flash?
Did you HardSPL your device prior to Flashing?
Did you alter your radio?
We can help you more if we know what we are dealing with here.

[Q] Question regarding installation of Hellfire Phoenix 2.4.2 for G2X

Hi,
I am new to this forum so hello everyone...I am having a problem installing the new Hellfire Phoenix 2.4.2 ROM for my G2X. I followed the instructions to the tee (wipe data, fix permissions, etc.) and I also have flashed my ROM before. What's happening is, I flashed my ROM and when I rebooted it is unable to get past the LG logo. It'll remain stuck on the logo for roughly 15 minutes or so and blink once in a while and eventually shut down. Not sure what's going on. Anyone have an idea how to remedy this?
Thanks
RE
DougKong said:
Hi,
I am new to this forum so hello everyone...I am having a problem installing the new Hellfire Phoenix 2.4.2 ROM for my G2X. I followed the instructions to the tee (wipe data, fix permissions, etc.) and I also have flashed my ROM before. What's happening is, I flashed my ROM and when I rebooted it is unable to get past the LG logo. It'll remain stuck on the logo for roughly 15 minutes or so and blink once in a while and eventually shut down. Not sure what's going on. Anyone have an idea how to remedy this?
Thanks
Click to expand...
Click to collapse
Hi bro. m new here too just like you. i am having the exactly same problem while rebooting after following as per instructions. no proceedings after lg logo. the phone gets hot and the battery get depleted but no HFP installed. i think we are missing some thing that we are not aware of. LETS HOPE that our seniors will help us here. AFTER ALL I AM HFP LOVER... PLZ HELP US ..

[Completed] Resurrection Remix ROM 6.8 Build running Kernel 6.2 - Bootloop Issue Zenfone 5

Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Thread closed / Duplicate

VERY Slow Boot after flashing Nethunter

Hi guys hope you are having a nice sunday.
I am facing a quite annoying issue after flashing Nethunter on my Oneplus One: every time I boot the phone, the device gets stuck for about 6/7 minutes on the 1+ logo, then the animation appears for few seconds before it finally boots.
I have had this issue with stock CM12.1+Nethunter 3 for OPO CM12.1, and now I am having it with a CM13 nightly + a custom Nethunter that works on CM13. In both cases the device boots up in seconds until flashing nethunter.
I did try to reflash once again (just in case) and I still have the same problem.
Scenario:
Wipe the whole device
Flash CM13 (or 12.1)
Flash Gapps
Reboot and configure android
Reboot again to test boot speed - it boots up super fast
Go to recovery again and flash Nethunter
Wipe dalvik+cache
Reboot
From now on it takes 6/7 minutes to boot
Liveboot Log (only appears during kali animation though, not sue it's logging what happens during the kernel logo):
txt log file > drive.google.com/file/d/0B7y82quVQHh6elliMmFXdUJFSjQ/view?usp=sharing
virus check > virustotal.com/it/url/60a0f8536b0053f104a5d8dcf06a8cc27f89736d0fd915572b75790e12cad031/analysis/1456660030/
Tried with many versions of TWRP (from 2.6 to 3.0.1), nothing. Also, when I boot into recovery, I see the recovery logo for about 5 minutes before I can actually get into the recovery.
I hope someone has got an idea about how to fix this, as you can understand it's very frustrating having a phone that takes half of a big bang theory episode to boot.
Let me know if I can provide more info about my device!
Thanks a lot.
pLx_ said:
Hi guys hope you are having a nice sunday.
I am facing a quite annoying issue after flashing Nethunter on my Oneplus One: every time I boot the phone, the device gets stuck for about 6/7 minutes on the 1+ logo, then the animation appears for few seconds before it finally boots.
I have had this issue with stock CM12.1+Nethunter 3 for OPO CM12.1, and now I am having it with a CM13 nightly + a custom Nethunter that works on CM13. In both cases the device boots up in seconds until flashing nethunter.
I did try to reflash once again (just in case) and I still have the same problem.
Scenario:
Wipe the whole device
Flash CM13 (or 12.1)
Flash Gapps
Reboot and configure android
Reboot again to test boot speed - it boots up super fast
Go to recovery again and flash Nethunter
Wipe dalvik+cache
Reboot
From now on it takes 6/7 minutes to boot
Liveboot Log (only appears during kali animation though, not sue it's logging what happens during the kernel logo):
txt log file > drive.google.com/file/d/0B7y82quVQHh6elliMmFXdUJFSjQ/view?usp=sharing
virus check > virustotal.com/it/url/60a0f8536b0053f104a5d8dcf06a8cc27f89736d0fd915572b75790e12cad031/analysis/1456660030/
Tried with many versions of TWRP (from 2.6 to 3.0.1), nothing. Also, when I boot into recovery, I see the recovery logo for about 5 minutes before I can actually get into the recovery.
I hope someone has got an idea about how to fix this, as you can understand it's very frustrating having a phone that takes half of a big bang theory episode to boot.
Let me know if I can provide more info about my device!
Thanks a lot.
Click to expand...
Click to collapse
My 2013 nexus 7 hangs on the google logo for about 5 minutes as well so I guess it's normal :/
What are the main purposes of NetHunter? It seems like it's some kind of counter offensive security tool or some network backdoor discovery tool. I've never heard of this before.
@noahvt it is not normal, I have tried to reproduce the same situation on a friend of mine's device which is exactly the same as mine, same baseband, same kernel, same nightly rom, same file for Nethunter, an exact copy of my phone. His phone boots in seconds.. It's not normal, especially when boot to recovery it shouldnt hang for 5 minutes on the recovery logo.
-
@SirSoviet
https://www.offensive-security.com/kali-linux-nethunter-download/
Nethunter is basically a Kali Linux port for Android, which allows you to pentest your network. A bit of googling will give you more info about it.
pLx_ said:
@noahvt it is not normal, I have tried to reproduce the same situation on a friend of mine's device which is exactly the same as mine, same baseband, same kernel, same nightly rom, same file for Nethunter, an exact copy of my phone. His phone boots in seconds.. It's not normal, especially when boot to recovery it shouldnt hang for 5 minutes on the recovery logo.
-
@SirSoviet
https://www.offensive-security.com/kali-linux-nethunter-download/
Nethunter is basically a Kali Linux port for Android, which allows you to pentest your network. A bit of googling will give you more info about it.
Click to expand...
Click to collapse
Just built my own version of it and it boots slow as well on my one+ so don't know what's wrong :/
I have the same issues also, the main OS feels pretty unstable (had it freeze on me twice and had to hard reboot it), gonna try a different base maybe Calkulin's or a previous CM 12.1 build.
nfusion77 said:
I have the same issues also, the main OS feels pretty unstable (had it freeze on me twice and had to hard reboot it), gonna try a different base maybe Calkulin's or a previous CM 12.1 build.
Click to expand...
Click to collapse
I wish you good luck, though I've tried both CM12.1 and CM13 and unfortunately had the same issue. Hope it will do the trick for you!
hello pLx_, i got same trouble, but i install patch "kernel-nethunter-flocm-marshmallow-3.1.0" from "https://idlekernel [dot] com/nethunter/nightly/" (flocm, not flo!) and its works fine.
hope it will help you.

XT1033 : ROM Bootup gets hangs every time

Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files

Categories

Resources