I'm on Paranoid Android 5.1 and latest TWRP and sometimes I have to do a battery pull when I reboot the phone because it's unresponsive. This happens on every AOSP rom and I was wondering what causes it, the rom or TWRP?
It would be the rom
Sent from my iPhone using Tapatalk
I'm on stock and this happens to me so its not the ROM I want to blame it on twrp though
Happens every time with me. I'm on Lam Hoang 2.2 (stock-based). Happened on Cloudy, as well. I feel like it happened on Euphoria (AOSP), too, but not as much. Incredibly annoying.
I'm experiencing the same problem. Both with Blisspop and Stock. After reinstalling the stock boatloader it fixed the problem therefore its twrp. Anyone have any idea's of a solution?
Bump for an old thread. Has anyone figured this out? I'm almost tempted to just go back to stock bootloader because of this issue on my Verizon LG G3 (VS985)
Related
Hey so when I update my phone from a nightly from August to a nightly in September I keep on getting random force reboots. I managed to flash to the experimental M1 nightly and i'm stable there, but anything past that and I get force reboots (my phone randomly shuts off).
Any help would be greatly appreciated! Thanks!
Are you sure it is due to CM? I have the same issue with the stock Rom rooted.
Well it only happens on any nightly past the experimental M1.
Have you tried a clean flash? Or have you just been doing dirty flashes over and over?
Yeah, I tried a full wipe then install last night.. didn't get a force reboot for about an hour but then after that it went back to "normal" and happened like every five minutes.
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
kevin2005 said:
Thank God i made my back before I installed cm10 i had and still have the same issue, so i went back to stock+root if anyone know the fix post it thanks
Click to expand...
Click to collapse
Same here I had tested e different rom and mostly reliable I found was DarthStaker v7. But looks like samsung did something with the new s3 hardware because before my phone replacement my first s3 was smooth as a butter with any rom but now is a pita toget it shorted out with new rom. Stock+root works way better that any rom.
Sent from my SGH-T999 using xda premium
OK, so the wife and I both have VZW S3s, rooted and running AOKP JB Milestone 1. I have had zero issues with my phone, and she didn't have any for like 3 months. Now all of a sudden she keeps getting random reboots that take her into a bootloop. The only way she can get her phone up and running again is to do a complete wipe, and flash AOKP and GAPPS again. Has anyone else seen this? What could be causing this and how do I fix it? Thanks for all the help!
Have you undervolted her phone? If you did then it probably bootloops because it was undervolted to much.
spears1977 said:
OK, so the wife and I both have VZW S3s, rooted and running AOKP JB Milestone 1. I have had zero issues with my phone, and she didn't have any for like 3 months. Now all of a sudden she keeps getting random reboots that take her into a bootloop. The only way she can get her phone up and running again is to do a complete wipe, and flash AOKP and GAPPS again. Has anyone else seen this? What could be causing this and how do I fix it? Thanks for all the help!
Click to expand...
Click to collapse
Seems like you have corruption in /system. If you want trouble free, don't use AOKP rom, use something like CleanRom instead! AOKP does have weird issue from time to time.
Alrighty, this is one of the weirdest things I've had happen with a phone since I started doing this on the original Droid. Lately I've been using Jellybeans Rom, its been great and my longest running ROM so far, but like a lot of people here I have to try out new stuff quite often just to try it. Well anymore I cant seem to try much else, I wanted to run the newest Liquid Smooth 2.3 ROM that just hit and it wont work at all really, before I redid the whole phone every time I flashed LS 2.3 I couldnt even hit the start button when the ROM first installed, when I did it wouldnt do anything and then the screen would go black and I would have to hard reset or battery pull. Next boot up seemed to go fine, got my gmail up and running and titanium downloaded and then after that, hitting settings options would lock up the phone in just about any app I had, never even got around to trying to restore anything with titanium.
Re-flashed LS 2.3 three or four times and nothing changed, tried fixing permissions, fully wiping, etc. didnt matter. So naturally I figured it was simply the ROM on my phone (mind you LS 2.2 worked fine before) so I went and decided I would try out Avatar ROM, CM based with MIUI themes, this ROM did pretty much the same thing. No idea why...
Next I figured something maybe was wrong with my phone so I went back to the drawing board and started from factory with ODIN, I redid my ROM with stock/root, unlocked the boot loader again and redid custom recovery and all the same thing with LS 2.3 happened all over again, Stock ROM worked great for the bit of time I used it before I tried to reflash LS 2.3 again, Now I'm back running Jellybeans v.15 and it runs perfectly fine as well.
I really have no idea what the problem is, both of those ROMs I've tried are CM based original development, so I'm wondering if its something in there thats causing an issue over the TW ROMs I've used. I've used other TW ROMs with decent success, but I've had some issues with those too that you wouldnt think should happen but it wasnt anything worth noting, just like Jellybeans the best, but even some of those would give me slow down problems and occasional lock ups when Jellybeans doesnt.
Anyone have any clue as to what could be causing this? I used to be able to run non TW roms just fine and its only been in the past month that this has started happening that I've noticed, I've had the phone since January and have been flashing away this whole time and now I cant seem to try out any more ROMs without having major issues......ugh
Your situation is a very random situation but I have something similar happened to me involving TW ROMs in that some of them froze on me. I had to flash the stock ROM.
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Vidfreek said:
Bump, anyone having any kind of similar problems?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you've only had these issues in the last month, it could be attributed to the Linux 3.4 kernel that every AOSP rom has moved to. I wouldn't let that stop you though. Are you downloading these rom zips over WiFi or mobile data? Were your downloads taking awhile as well? I know either GOO or AFH was having server issues recently which may have coincided with your downloads. I'd suggest using WiFi if you aren't already and trying again?
Sent from my SCH-I535 using xda app-developers app
Yeah its only been fairly recent and all roms I've tried have been updated since the very end of april, if my phone has major problems with that linux kernal am I going to be able to flash anything again? Everything I downloaded was over wifi but I can try all the downloads again but I'm thinking that won't fix anything, just weird stuff
Sent from my SCH-I535 using xda premium
So...I have had a captivate and SGS3 and have never had so much trouble with a phone. This infuse is frustrating and complicated to work with. I have blue CWM which was acquired by using Entropy's guide and the other numerous helpful tips out there. I had rootbox running which would eventually start FC'ing and acting dumb. I wiped everything the other day and flashed unofficial CM 10.2, it worked perfect then random reboots to stuck at samsung then cyanogen mod then back again. Sometimes it would randomly reboot in CWM, which has never happened to me on other phone. I feel like going back to stock and back again is the only answer, but it seems like a lot of work and I already did that and it was fine.
So, all you guys that understand whats going on behind that scenes, what do you think the issue is?
UPDATE: I found a video that may link this behavior to a hardware issue caused by poor design by Samsung having too many contacts that can get gunked up and causing issues.
Might be a problem with the version of the Gapps you're using. Consider changing and even going back to older versions. I found v 12/12 signed very stable on cm10.1.
If still stuck, consider Odin back to stock in download mode and flash cm9 and cm10.2 again!
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Update:
Tried Elemental X, the phone reboots randomly now... And also just googled problem with Nexus 5... it seems like 5.0 and 5.0.1 have TONS of random reboot issues...? Goddamn it Google...
Do any of you have a stable ROM (stock or custom) that doesn't have random reboot issues?
Elementalx
codenamezero said:
I clicked on the Kernel tab, and tried the franco.Kernel, and simply get stuck in bootloop, I look at the tags and it seems like most of the kernels only support the old KitKat..?
In addition, it seems the kernel scenes is a bit haywire now with AOSP/CAF...?
Could someone gimme one or two kernel suggestion that works with rooted OOB 5.0.1? I am just trying to quickly fix my sister's N5 here... she got nothing but nightmare after upgrading from 4.4.4 to 5.0, constant reboot, crash, battery drain... so i just now wiped the whole thing and flashed a fresh 5.0.1
Any help/suggestion on kernel would be appreciated. <3
Click to expand...
Click to collapse
i use franco kernel 70 with stock rooted 5.0.1 with no issues. but i don't see any differences between stock and franco. neither performance nor battery life.
This Nexus 5 is just getting worst... it random reboots now.
codenamezero said:
This Nexus 5 is just getting worst... it random reboots now.
Click to expand...
Click to collapse
Sorry to hear that. Could it possibly be a hardware issue since you say it's happening to you across all software? Corrupted storage media could cause random reboots such as that.
I'm not seeing any myself, though I do reboot the phone about once a week just as a precautionary measure with L's RAM management.
Was having this issue with Stock and Custom ROMS ended up going back to KITKAT and no problems. Hopefully they will have this fixed with 5.1 that will be released soon.
Stock one is allways the best choise. You must be aware, that the stock one is build by a lot of good developers and custom ones are made by individual enthusiasts. There is nothing wrong with that, but the pure logic here speaks by itself.
Used a lot of different roms
ordered my nexus on release day, used quite a few different roms and i've never had a random reboot.