So since the 2.3.3 OTA came out a few weeks ago my phone no longer randomly crashes, however im feeling the need to swap to one of the other many ROMs around here.
Did most ROMs change whatever was making the reboot bug happen? Is there a way to tell? or are they still plagued by the reboots i oh-so hated?
Note: I would get reboots everytime i used my phone for more than 15 min - it seemed to be heat related. after the OTA i have not gotten a single reboot. Hoping other roms work!~
I believe the issue is not with the rom but the LG drivers and baseband. So I believe you may have solved your problem. As far as other roms are concerned, the only way to tell which suits you best is trial/error method... Make a backup and flash away!
Update to this: I Tried Faux's ASOP ROM and to no avail, within 10 minutes I have a reboot Guess it'll be only OTA based roms for me!
Related
So I went back to stock froyo and did a complete wipe of everything, even my sd cards. then I plugged into kies mini and updated to gingerbread, and about every time my phone went into standby mode after maybe 10 minutes it would do a soft reboot. I thought it might just be a problem with the stock rom, so I rooted and got a custom kernel, and I installed many different stock based gingerbread roms, all with the same effect. then, I tried cm7 and had NO PROBLEM with the reboots. also, I have no problems on any froyo roms or any aosp based roms. thanks for any help with this
Try using the one click to stock or the updated odin packages. Follow their instructions to the letter....
http://forum.xda-developers.com/showthread.php?t=1610374
That didn't work either...
Sent from my phone
Reboots
I was running MIUI on my phone and had problems and took it to the local ATT repair shop and of course their solution was to clear out the phone and revert back to stock Gingerbread UCLB. It seemed to run well for awhile, but after about two weeks I started having random and multiple reboots too. I then odin'ed the rooted stock gingerbread (I believe posted by Entrophy) and loaded the RemICS 1.2a Rom. It seems much faster and smoother than the stock rom. We will see how it lasts. Does anyone seem to have problems with loaded Roms seeming to deteriorate after awhile? It seems like on both my Infuse and a Captivate that I have, the performance and stability seems to go bad over time...
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Try flashing a stock UCMC1 ROM and doing a factory reset after your flash finished successfully and Odin rebooted your phone.
3 things you need:
1- skyrocket windows drivers from Samsung website
2-Odin
3-stock ucmc1 tar ball.
Refer to this page:
http://forum.xda-developers.com/showthread.php?t=2228247
Good luck.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
lingowistico said:
You don't need to install a custom rom. Try updating to official jellybean with kies, if that doesn't work then try C64's advice above with either UCMC1 or UXUMA7 (uxuma7 is less bloated).
The issue you're having is odd and I haven't encountered it before..
Click to expand...
Click to collapse
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
sjbonner said:
Thanks for the suggestions, C64 and lingowistico. Upgrading to JB was going to be my next move, but I wanted to know if anybody had seen this behavior first. I don't want to mess with the phone too much in case the seller will take it back (I may be on a loser there). I'll try the official upgrade and let you know.
Custom ROM not necessary -- true, but I've been running CM on my bravo for a couple of years and can't go back to a stock ROM. I'll try the de-bloated version of the official JB release, but I'd like something I can have more control over.
Cheers...
Click to expand...
Click to collapse
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
vincom said:
when phone is doing odd things the best way to ts is a complete wipe, formatting/removing sdcards then returning to stock w/odin, but you could try the debloated rom 1st just to test it out, if its resolved then its prob not hw related, just make a backup of ur current rom if planning on returning it but since you install an official stock it should also be returnable
Click to expand...
Click to collapse
Thanks Vincom. I don't have access to a Windows machine at the moment so haven't been able to try the upgrade.
One question -- how is it possible to make a backup of the current ROM without first rooting and installing a custom recovery? I suppose that I could install the custom ROM and create a nandroid backup. Then if I needed to restore I could restore the nandroid and reinstall the stock recovery. Is there an easier way?
Apologies, I just saw that you have information on reinstalling the stock recovery on your Newb Guide.
BTW, I want to say thanks for your work on the Newb Guide. One of the things that sold me on this phone was the support that it has here. Amazing to have all of the information on installing the custom recovery, rooting, etc. all in one place.
sjbonner said:
Hi all,
I've just bought a new SII Skyrocket to replace my Motorola Bravo -- the bravo was terrible purchase and though the Skyrocket is a two year-old phone I consider this a big step up.
I bought the phone on eBay and it was advertised as new. It arrived in its original packaging with the security seal intact, so I have no reason to doubt this. The phone is running ICS (4.0.4 build IMM76D.UFCLF6).
The phone arrived yesterday and I really like it, but I've encountered a weird issue. If I reboot the phone then it is no longer able to make any sound. Any action that requires sound -- incoming calls, outgoing calls, choosing a ringtone, playing music, taking a picture -- causes the phone to freeze for a minute or more and then become very slow. Rebooting again makes no difference. The only solution I've found is to reboot into recovery and factory reset, though this may only work after several tries.
- Has anyone heard of this issue before?
- Is it likely to be fixed by upgrading to Jelly Bean (I'll install a custom ROM if I can be sure that the phone is working properly) or is this more likely a hardware issue?
Apologies if this question has been answered before. I've searched the forums here and elsewhere, but I haven't found any mentions of similar issues.
Thanks for your help!
Click to expand...
Click to collapse
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
econan1214 said:
I believe I had this kinda issue once before, it was when I flashed CM10 or something. No incoming sound, sound did not work whatsoever, but installed a different kernel solved the issue, or flashing a new different rom.
Click to expand...
Click to collapse
UPDATE:
So, I managed to upgrade to the official JB 4.1.2 this evening. Had to do it twice.
First time the boot got stuck at the AT&T logo and PC wouldn't detect the device. I followed the directions in another post http://forum.xda-developers.com/showpost.php?p=34682377&postcount=9 to repeat the upgrade and the same thing happened.
On a whim I decided to try rebooting a few times to see what would happen -- and it worked! Sort of...
I'm repeatedly rebooting the phone and sometimes it will start without problem. However, most of the time it gets stuck when the AT&T logo appears exactly where it should play the start up sound, except it freezes and the sound never plays.
I'm guessing that wiping the data before had nothing to do with fixing the problem and I was simply getting lucky on reboot.
I realize that this is a hard question without having the phone in hand -- but does this sound like a hardware issue?
Thanks again to everyone for their help.
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
theesotericone said:
Boot into recovery and factory reset from there. That should clear up the boot loop issue.
Click to expand...
Click to collapse
Just a quick note to let you know how this was resolved. I returned the phone to the seller who provided a full refund.
Thanks again to those who respondend.:highfive:
I have rooted last week when the custom ROM for Android L came out, been jumping between a few different threads so unavoidably flashing between them. At the end I started getting reboots after flashing k900's 19/11 version, and decided to flash PA 4.4.4. This did not help the issue, I was still getting reboots. As a result of really tired of custom ROMs, I flash back to stock (100%) CM11S. Been on it for about one day, and I already seen 3 reboots. They seem random from what I can find out.
I was wondering if anyone has similar issues, or knows the cause of this problem?
Possible causes:
Could flashing too many ROMs harm the device?
I also had to flash the recovery multiple times (around 8, because I wanted to get TWRP to work), could this damage the device?
I am aware that back on stock for one day is still pretty early to say it won't fix itself, but since I have had similar issues with past devices after flashing custom ROMs I kind of want to know asap so I can contact OnePlus.
I will keep this thread updated, hopefully it will help someone else even if the issue is not fixed.
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.
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.