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.
Related
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!
I have combed these threads as hard as possible but still can't find a clear answer/fix.
I had a custom rom installed a while back, and it started freezing and not coming out of sleep mode. It has done this with asus official rom as well. Is there a specific process to wiping and installing the correct rom so this won't be an issue. It was running fine for at least 2 months before it started doing this and I can't seem to reverse this. I don't care if i have a custom rom or official, i just want my transformer to be used again!
thanks!
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:
OK, so last weekend I managed to get my HTC One X (Evita) rooted, but not S-OFF. I made it once successfully through the entire Facepalm process, but the phone remained S-ON for some unknown reason. It was said to me that I may try to flash a custom ROM and then try again, so I flashed to the most recent CleanROM. Since that time, I've had great problems getting my cell service to stay active, and all further attempts to use the Facepalm/S-OFF method have proven useless because I simply can not ever under any circumstance get past the dreaded "device not found" from the command prompt. I should further note that I read about a LOT of people needing to add a few layers of tape to their SIM in order for their service to stay on with this particular phone...so I've already successfully done this and it did not resolve my dropped service issue.
At this point, I don't know which direction to go. Could the ROM be why my service is dropping? I've not done any sort of "radio" update on this phone yet...can that be an issue? I see RUU's listed on the index thread...would flashing to one of those help? If so, is the procedure same as flashing a custom ROM? And how in the world can I get passed the "device not found" error so that maybe, someday, possibly, I can have my S-OFF?
Any help would be greatly appreciated...
OK, so I've done a couple MORE hours of reading, and I've learned this:
1. The signal drops (as well as the occasional reboots which I didn't mention earlier) are consistent with people whose kernel or radio need to be updated to something that appropriately matches the ROM they're running.
2. I'm not imagining things...rooting/updating THIS particular HTC phone is indeed trickier than the other 3 I've rooted in the past...in the sense that following the directions won't always yield you the same results as the next guy. I'm seeing this sentiment in forum posts (even from ROM developers/etc.) quite a bit today, so, if nothing else, I know I haven't lost my mind lol.
So anyways, it seems as though I need to figure out which "kernel" to flash. I've not flashed ANY kernels on this phone so far, and it came stock running Android 4.0. I ultimately want to be running the latest stable version of Android with Sense on this phone. It appeared the answer for me would be the latest CleanROM, which is 4.2.2. and Sense 5. It's been running on my phone for almost a week now and I like it, except for the signal dropping/rebooting.
I don't know if I've added ANY info that will help someone give me good advice, but....anyone?
...and even MORE reading led me to the xda thread for the latest CleanROM, which is littered with folks having the exact same problem as me.
So yeah, I was here thinking all these problems were brought on by me just not "getting it"...but it just so happens that the first ROM I flashed had these issues for folks with not-so-current radios.
I've got several threads pulled up now that will supposedly get me fixed up, but I can't flash a kernel without S-OFF, so I'm back trying to figure out how to get past this stupid "device not found" issue.
Flash a different ROM to get s-off, Android 4.0 or 4.1 will be best. Once you have s-off you can either upgrade to the 2.15 firmware or flash the Beastmode kernel, either of these methods will stop the signal loss issues you've experienced on Cleanrom. Also, please search before posting, the signal loss issue is plastered all over the Cleanrom thread, you can't read more than two or three pages without seeing it mentioned along with the fix.
Sent from my Evita
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.