I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
tannerw_2010 said:
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
Click to expand...
Click to collapse
I used to get it too. It stopped after I flashed (from hboot) the new radio, pri, and rpm, then updated ROM base to sense w/2.3.4 base. Try that, and of course, full wipe, sometimes random reboots is from dirty flashing oh yeah, and try making sure your VM heap is 42m or less in the /system/build.prop
tannerw_2010 said:
I've had the EVO3D since launch, and recently, it has been randomly rebooting at least once a day. It seems like it's getting worse and worse, as about a month or two ago (when I first got root) it was maybe 2-3 times a week. For the first month I had the phone before root (or even temp root), I only remember two specific occasions when it boot-looped until I had to do a battery pull. So i guess you can say it happened 2 times a month back from June-July.
I really love this phone but this is just getting ridiculous. I don't know what to do from here since I didn't buy the warranty. Any suggestions? I am using SupraRom (the latest AOSP version) and TWRP (1.2 or 1.3 (?))
As I typed this up, I tryed to reboot into recovery to see what version I have and it locked up again (black screen with lights on the buttons).
Click to expand...
Click to collapse
il Duce said:
I used to get it too. It stopped after I flashed (from hboot) the new radio, pri, and rpm, then updated ROM base to sense w/2.3.4 base. Try that, and of course, full wipe, sometimes random reboots is from dirty flashing
Click to expand...
Click to collapse
If the above steps don't work to clear the issue, I would suggest loading the latest stock system and kernel. If you still have random reboots on the latest stock system and kernel, it definitely sounds like it could be a possible hardware issue triggering a kernel panic causing the device to reboot.
This level of troubleshooting, determining what is causing the kernel panic and rebooting the device is beyond and most users and goes a bit deeper. Generally, on a fully stock system, this would indicate a serious programming error which should affect many users, or some type of hardware flaw in the specific device.
Random reboots are hard to prove. The best route would be to take the device back to where you purchased and/or Sprint and see if they are able to help you.
Hopefully the steps quoted above by updating the firmware and software to the most recent versions resolve the issue as it could have been a programming bug on HTC/Sprint's part.
Hope the extra information and details help!
here is the reboot fix
http://forum.xda-developers.com/showthread.php?t=1253126&page=2
download it and rename it to PG86IMG and goto bootloader problem solved
---------- Post added at 02:58 AM ---------- Previous post was at 02:07 AM ----------
follow the above link, then follow the link in the post. i would recommend installing the eniter zip package m the one that says nohboot, it has everything in it including the rpm update.
I've had 3 3D's, each running the same software at the time, only one ever did this. I personally think the freezing and reboots are more hardware related than not.
Related
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Drachen808 said:
Ok, so I need some help. I had to trade my evo in due to a problem with the front facing camera so, naturally, I have hboot 1.5. Though it is frustrating, I don't have a really big problem with taking an extra step to flash ROMS. Unfortunately, I have not been able to sucessfully flash for a while. I was on Nocturnal Xplod (1/2/12) and it was relatively stable, with only a few reboots every week. However, lately, it has gotten unstable and so I started looking for an alternative.
Every single time I flash a different ROM I get about an hour of stability, then it reboots every 5-10 minutes until the battery runs out.
I have tried the flashimg gui method, I have tried using adb to go through fastboot and flash recovery . . . I have tried with and without TiBa. I am not sure what to do. Am I missing something? I am not a flashaholic, but I do like to have the ability to take advantage of stable roms.
Click to expand...
Click to collapse
Drachen808 said:
I am using TWRP 1.03 on my phone, so I will try CWM since I just read that people are having trouble with bad flashes with TWRP. If anyone else has any other recommendations, I would be very happy to hear them.
Click to expand...
Click to collapse
A bad flash can occur but generally they aren't prevelant. The best place to look for feedback on ROMs is in that specific ROM thread. If that specific ROM isn't setup well, or has bugs, these will cause random reboots.
If you're really interested in helping out the devs, the best first step in technically troubleshooting a random reboot is to grab the /proc/last_kmsg file. This is a log of the kernel as of last boot and will indicate whether or not the kernel was involved in the random reboot. If the issue is in the kernel, will narrow down the focus. If the issue is not in the kernel, will eliminate that possibility.
Another common cause of random reboots can be poorly coded 3rd party apps. Unfortunately, depending on the number of 3rd apps installed, this process can take a while to troubleshoot as the best method is to remove all and start installing in batches waiting to see if any random reboots occur.
Hope these few suggestions and some technical information help!
Thank you Joeykrim. I will look into that, but I am fearing more and more that it may be my phone. I have tried probably every sense 3.0 rom (need wimax and camera so no 3.5) and several different kernels, and it keeps happening.
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
ferincr said:
Ok, I know some other people posted about black screen but all the other threads seem to be about it happening after a call.
Mine happens when the phone been sitting for a while with the screen off (and it's not all the times) it seems more prone to it if the screen been off for longer times.
I tried two different roms with two different kernels both have the cpu idle speed setup at 384 or more. As soon as I flash they seem to work ok but after a day or so the freaking black screen comes back. I also have pimp my rom installed with the "no black-screen after a call" tweak ticked.
I've went through the process of unrooting going all the way back to stock and start from the beginning all the way from unlocking the bootloader to S-off.
Downloaded fresh copies of the roms zip files
I don't think it's any of the apps since this does not start right away it takes a day or so after everthing been runing (but I might be wrong).
Obviously it's not the rom or the kernel since it does it with two different ones, what else is there that can be messing with my phone???
It's driving me crazy!!!!
Can it be hardware related????
I'm lost with this, and started thinking on a new phone already but I can't buy it until mid 2013 so I don't want to give up yet (actually can't).
This been working just fine up until a month ago or so, it's just now that the black screen started harrasing me.
Edit: It just happened again and since I could not get the screen up, I decided to pull the batt and when I turned the phone on again I got the vibration but the screen didn't light up during booting at all until I pressed the button few times.
Could my screen be dying?
Click to expand...
Click to collapse
have you ever considered its the tweaks your doing to your phone.. have you tried just flashing the rom and running it without doing the tweaks... not every phones hardware is identical so not all tweaks might work... ive flashed a rom recently that experienced some boot loops after doing some tweaks to the rom, and now im running that rom flawlessly without any tweaks...
---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------
you might also want to try the rom with the default kernel that comes with the phone not faux which i'm assuming your using
To be honest, no I haven't thought of that.
I just re flashed everthing, if the problem starts again I'll remove all the tweaks.
But the thing is the phone was working well and one day without changing anything it started with this. But I'll try removing the tweaks if this persist
Thanks,
Nope, it wasn't the tweaks.
Fresh flash, no tweaks and I still have to press the on button many times to get the screen to turn on
which rom are you using again?
I'm on NRG blue but I tried the Bulletproof for a while and it did it too that's why I'm thinking that is not rom related. It has to be something deeper than the rom.
Phone was working great until last month that I travelled abroad.
As soon as I got to the country I was visiting I put a local sim card and it took me a while to be able to boot, to the point that I had to restore from a backup.
Then during the time I was there I had several random reboots (like once or twice a day).
When I came back I swapped the sim again and no more reboots but after a week or so I started with this black screen problem, it was really bad to the point when sometimes I needed to pull the battery off to see if that helped and the rom got really screwed (I think sense got screwed because the screens were doing weird things). So I reflashed, it fixed all the weird things but not the black screen.
Now it's not as bad (I only need to press 3 or 4 times the button) and it's not alway, only if the screen been off for a while but my previous experiencest tells me that it will get worse in few days time...
okay i have a few suggestions.. do you do a full wipe when you flash a rom? wipe data/factory then format system then wipe cache partition's then wipe delvik cache.. and you should try going back to stock completely then trying a different rom and see.. its about testing all possibilities before coming to the conclusion your phone is damaged somehow
yes I always do a full wipe and/or the 4ext wipe and clear dalvik and cache. Not sure about the factory reset since I wasn't sure where that would take me.
you should try going back to stock completely
Click to expand...
Click to collapse
Do you mean relock, S-ON and goall the way to GB? or to ICS T-mous stock??? I did go to ICS (this one) http://d-h.st/3VD but I can do it again (I can alway use some practice with these procedures...)
I
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Ninjistix said:
you dont have to S-ON again i mean Stock ICS from your carrier.. and stock Ruu's are located in my signature if that link is one you got from there go right ahead... and try and flash back to stock, if you need instructions let me know
Click to expand...
Click to collapse
I did that yesterday and yes the ruu Iused is the same as the one listed there as most recent.
I just found an interesting discusion on the faux kernel thread about a problem, with the earlier version (which is the one I was running when the whole thing started) and that happened to me before this black screen.
This is the thread http://forum.xda-developers.com/showthread.php?t=1359951&page=232 and it's mentioned in the quote on post #2316 and ahead.
I PM'd AJ to see if he thinks this could be related since in one of his posts he said something like reverting to stock won't help (for some reason)
but overall from what i just read... the issue seems to be related to the faux kernel.. i only flashed it once but ii didnt do any tweaks,, i mostly use the stock kernel that comes with most of the rom's i flashed... here's what to try... in 4ext wipe all partitions except sd card, then wipe both sd card partitions internal and external.. toggle usb storage and flash this super wipe script in recovery.. then flash a different rom and don't flash faux.. test the rom out to see if your problem occurs again.. or flash the super wipe then place the ruu on the SD card then attempt to flash back to stock
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Double0EK said:
Try this thread and see if it will help your situation.
http://forum.xda-developers.com/showthread.php?t=2070438
Click to expand...
Click to collapse
I'll try it.
Thanks,
Tried that and didn't help, but thanks for the suggestion.
What I noticed today is that since Icouldn't get the screen on no matter how many times I pressed the darn button I pulle dhte batt out and then rebooted the phone to see if that helped and even though I got the little vibration confirmation when the phone boots up there was no white HTC splash screen or bootanimation whasoever, anyway since I could still not get the screen on I tried the same thing a few time and then once I finally managed to the the screen on I said int the bottom left corner SAFE MODE (never seen that one before). I'm running Bulletproof reloaded now.
Oh and the batt was kind of low (may be 20%).
Wow!!!! I do own a very messed up phone!!!
Today this piece of crap threw a total temper tantrum.
Would nos turn the screen on no matter what. I removed the batt and not even rebooting to the point that when I finally got it to boot it had an internal SD error. It didn't allow me to format, wipe or partition it from bootloader or recovery.
Now I'm at home so I flashed stock RUU (again) and it seems like its running one more time but I was really close to throw it over the cliff where I was Flying my RC gliders.
We'll see if I can make it last a bit longer...
so its working once again, cuz you said you flashed back the stock ruu right?
Yes,it's alive (will for how long this time). I flashed stock a couple of times , I unlocked once again, flashed 4ext, flashed JP hboot, superSU, NRG rom, supersu again (since IO wasn't sure in which order I should have done this) flash rom 2nd time, flashed Faux's v 24 (twice) and Downloaded most of the apps clean from Gplay.
I'm getting a lot of practice with this, who knows, may be one day I become good at it
its good your practicing now, but don't forget to do backups before you flash anything to your phone, this this way you'll have a stable install to restore back to incase anything goes wrong again
I been doing more tests and yesterday I run it on stock most of the day with no apparent issues, then I restored the NRG rom from a backup and still no issues so I started to think it was something I messed up flashing the JB Hboot, I moved to a bulletproof rom and decided to do another test.
I sat on the phone as to block signal and the issue came back.
Now I'll try the same with NRG, yep it seems like it's when the phone loses signal the screenwon't come back afterwards.
I'll try the same in stock rom next...
Yes, it did it in stock too but not so bad, it seems like after few attempts the screen worked againgvs. on bulletproof didn't
Ok, I found this in some other thread...
[QUOTE8. Black Screen - Phone will not wake-up
I'm accidentally find out and solved the problem of Black Screen during in-coming call (BulletProof 2.2.0). By replacing the service.jar from the previous version (BulletProof 2.1.0) with the intention to get rid of the CRT file in my system, by doing this I am also discovered that the black screen problem is gone. However, this problem can be easier solved by simply dis-able the screen-on/off animation setting instead of replacing the service.jar with the one from previous build which doesn't have CRT.
It's worth to be note that during my old days with the HTC HD2 running Nandroid I've encountering similar problem of black screen when waking up the phone and it was caused by the CRT as well. This, at least happened to me with more than 3 Rom, including the famous AmeriCanAndroid, HyperDroid and Tytung's ...
So if you are experiences Black Screen problem, please check to see if you did flashed the CRT and/or enable it? ][/QUOTE]
Can somebody tell me to how do I check this?
Thanks,
When I flashed 7/18 version of tweaked vzw remix I stated getting random shutdowns not reboots ( i pull my phone out and screen won't turn on, hold down power and it boots up fine and I have no isseus). I was getting atleast 3-4 of those a day. The new release was on its way so I wasn't worried, figured might be a bad download or kernel issue. the next release came out and I flashed it along with pbj kernel and same thing. After a few days they decreased and then hadn't had any for a week or so.
Today I went back to clean rom 3.5 and I started getting them again.
Anyone have any ideas what could be causing this? The only new app I have downloaded recently is the game dots. Neither time have I restored any data from tibu (I have been to lazy to do it)
any help is appreciated.
Have you tried going back to stock with odin and starting from scratch?
droidstyle said:
Have you tried going back to stock with odin and starting from scratch?
Click to expand...
Click to collapse
No I have not tried that. I just got the phone back in July, samsung had to replace cdma radio so it was all stock then. During the times I've had issues,there was a day I was on beans build 21 and cant remember the shut down issues happening that day. If it doesn't get better the next few days may try using Odin then rooting and unlocking it again.
Hey guys; I've been using dastin1015's ROMs for almost a year now on my Sprint Evo 3D. I definitely don't know everything (probably not even close) about using custom ROMs, but I'm not a complete noob.
That said, I screwed up. I successfully replaced my 4ext touch recovery with TWRP as dastin1015 says must be done for this ROM. I then wiped everything except my SD card and 'System' and flashed the latest ROM located here (Villuminati 12/08/13), and the "full complete" GApps package located here (4.4).
I rebooted the phone, and admired the new CM splash screen. Once the ROM loaded, I immediately got a couple of stock (system) apps (com.android.phone and ThemeManager along with some others) forceclosing repeatedly, preventing the phone from fully booting and making it very difficult for me to reboot the phone into recovery-- the messages popped up over and over again on top of the menu for reboot. I eventually did manage to get back into TWRP though.
At that point, I wiped *everything* except my SD card, and flashed the ROM and GApps again. Now I'm having the same problem, but with even more system apps force-closing, and I cannot reboot the phone or do anything else with it via the phone itself.
What do I do now? Can I fix this with ADB?
I read that using this 4.4.1 GApps might solve or prevent this problem, but it's iffy. In any case, unless someone has a better solution, that's the next thing I wanna try after managing to reboot into recovery. Do any of you think that will work?
Thank you.
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Glad to hear it dschlemmer.
The proper answer to the first part of my question (can I fix this in adb) is "of course, you idiot, just connect the phone to your pc and type "adb reboot recovery" and then wipe and re-install your old ROM or something."
However, I can't get the PC to recognize the phone, despite it having the proper drivers and having recognized it before. I think it's stuck at a phase in its boot-up that comes before the usb debugging is activated. My PC recognizes something is plugged in, based on the ding noise it makes (it's a Win 7 Pro x64 machine, and I think most of us are familiar with that ding noise), but the normal behavior of searching for and finding the drivers and then telling me the device is ready to use never occurs. Neither is there that "safely remove hardware" button in the taskbar.
So, of course, if the computer itself doesn't recognize it, adb can't either (confirmed by typing "adb devices" and it showing nothing). Is there anything I can do, or have I actually managed to completely (irreparably) brick my phone?
EDIT: The usb port is functioning, at least, as is whatever part of the circuitry or firmware controls the LED while plugged in and/or charging, because that works just like it should. It's just that I can't do anything but repeatedly cycle through the same "Unfortunately, the process com.android.phone has stopped", "Unfortunately, Themes provider has stopped", and a couple other messages that get covered up by those two, including one I briefly saw that mentioned "Settings". Haven't been able to see any of the others for long enough to identify any part of them.
EDIT2: I forgot about using the bootloader. Completely forgot. Stupid. Successfully in recovery, about to flash the same ROM with the new GApps. If it gets screwy again, I'll just remove the battery, replace it, and get into the bootloader to get into recovery.
dschlemmer318 said:
Yes that one worked for me and I used 4ext with no problems
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
electrickoolaid said:
From that version of GApps, what all did you download and use, exactly? I grabbed Standard and almost everything that didn't come included with it and flashed it all with the same ROM and the phone went into a bootloop that consisted of repeatedly verifiying apps (67 of them), throwing an error message similar to the ones I was getting before, then rebooting to do it all again.
I got a new Galaxy S4 ($50 at Best Buy with a 2-year contract renewal, woot-- Sprint wanted to charge me $200 for the same thing through them directly), so this isn't a pressing issue anymore, but I'd like to give the Evo 3D to my sister-in-law for Christmas. I ended up putting some AOKP Jelly Bean ROM on it (the zip was labeled Unofficial AOKP JB 3.5, I believe) I had sitting in the roms folder on my sd card with its own kernel next to it, and the phone appears to be functioning fine, but I'd like to a) figure out wtf the problem was/is with this ROM or GApps or whatever (something I did wrong probably) because dastin's stuff has always worked great for me before, and b) see Kit Kat in action on the phone. Either that or put it back to stock, which was, what, ICS? Did Sprint Evo's ever get an official upgrade to Jelly Bean?
In any case, and in lieu of posting in the relevant thread in the development forum since I don't have enough posts yet, here's the information about the phone at the time of this weirdness:
S-OFF
Hboot 1.40
Radio 1.09.00.0706
TWRP v2.6.3.0 recovery
NineInchNails' kernel posted in dastin1015's CM10.1-based ROM thread (Wild for the Night)
The ROM on the phone before the attempt to upgrade was dastin's latest Hood Pope version (Oct. 21st, 2013), which had been running just fine up until...
.... about 2 weeks ago, I uninstalled this Call Recorder app because I was running out of internal storage (~40 MB left) and I thought the app was causing it. Even though all the recordings seem to have been on the sd card, uninstalling it appeared to remove about 350 MB of something from the internal storage. Shortly after that (but not immediately after), every time I would end a phone call com.android.phone would force-close. I thought it was weird, but not too troublesome since it only happened after I ended a call, so it didn't affect my actual usage of the phone beyond having to tap an extra button every time I hung up the phone.
Then the other day, I noticed Villuminati was out and it was Kit Kat, so I went to install it, which failed spectacularly (as I said above, probably due to something I did or didn't do, but I'm not positive), and I posted this thread. You pretty much know the rest if you've read to this point.
Click to expand...
Click to collapse
i flashed rom then 12-6_gapps_standard_4.4.1_signed then reboot this is the link for the gapps : http://forum.xda-developers.com/showthread.php?t=2012857
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
renegadeone8 said:
Just got s-off on my DNA but installing a custom Rom makes the phone randomly freeze and reboot. Tried CM11, carbon, and a few others. The time before restarting varies wildly from 10 seconds after boot to 20-30 minutes. It seems more frequent when the screen is on or when plugged into my PC but I could just be imagining things or could be coincidence.
I have flashed and rommed many phones over the years and this one really has me stumped.
I cleared the cache and dalvik and formatted the system partition before installing the Rom and gapps. I have tried multiple roms and multiple versions of gapps as well with no luck. I have superCID of 11111111 from the original unlock process if that makes any difference. I have currently RUUd back to 3.06 for now and it seems perfectly stable on the stock Rom. Any help would be appreciated!
Click to expand...
Click to collapse
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Possibly
lemonoid said:
check my thread in the same section, mine started doing this two nights ago. I don't know why it started, my phone was fine prior to this. I did nothing to it, had been running Venom for a while, and two nights ago it started rebooting randomly and wildly. I have switched ROMs twice since then and it has not stopped. Like you said, it tends to be when the screen is on or gets plugged up. But unfortunately mine is doing it a lot on answering phone calls. I don't know if we are having same issure or what.
Click to expand...
Click to collapse
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Did all that
Jaggar345 said:
Did you use the proper recovery stated in the thread to flash the rom, have you installed any new apps recently? Does it happen when you run the phone in safemode? Have you tried Performing an RUU and the unlocking and installing a custom rom again?
Click to expand...
Click to collapse
I have done all of that stuff multiple times
I haven't installed any apps at all on it. This phone is basically brand new, I got it right when they launched. I shattered the screen like 3 days after I got it, and tucked it in a drawer. It has been sitting there ever since.
I have another piece to add to the puzzle. While it has the stock ROM installed it seems to get service and work just fine, but when I install the custom ROMS it has absolutely zero cell connectivity (though WiFi works fine.)
Going into the settings reveals that on the custom roms it shows the IMEI and MEID as Unknown, and the ICCID is listed as Unknown as well. If I try to change the network mode (to LTE/CDMA or any one of the many available options) it says com.phone has crashed.
After the RUU process I have my proper MEID and ICCID showing in the settings panel, and service returns.
Can't flash radio?
After discovering the issues with the service while on custom ROMS I wondered if the radio had something wrong with it.
I tried to manually reflash the radio via fastboot (fastboot flash radio radio.img).
I tried this both in standard fastboot as well as in the rebootRUU mode, but both times I get an error that says remote not allowed. Could my bootloader somehow still be locked? The flag in bootloader mode says "Unlocked" but I unlocked manually after obtaining s-off rather than doing it officially via HTCdev. just trying to explore all options
My phone did that at one point. I had to re-lock and RUU back to 100% stock. I then unlocked my phone with Rumrunner S-Off tool. Flashed a Sense 6 ROM and has been working fine since.
Fixed!
So this problem is fixed!! I am not 100% sure what did the trick, so I will post my solution here in case anybody else experiences a similar issue. I won't go into too much detail with these instructions as all the tools are here: http://forum.xda-developers.com/showthread.php?t=2612740
I first downgraded to the 1.15 hboot and radio. I had to rebootRUU and flash them there as it can't be done directly in fastboot as far as I know.
Do them one at a time (flash the hboot, then reboot-bootloader, then rebootRUU then flash the radio, then reboot bootloader again.)
After doing this I tried to run the RUU exe but it came up with an error that it could not update my phone, so I did the manual Alt 3.06 RUU.
This seemed to work great, restarted the phone and saw the stock rom. I then changed from superCID 11111111 back to the stock CID, relocked my bootloader went back to s-on status. At this point I ran the RUU.exe again just to make sure everything was as stock as could be.
Got that all finished, ran RumRunner again, installed CM11 and no reboot for nearly 24 hours. Pretty sure all is well!
renegadeone8 said:
I don't know if we are having the same issue it may be that we are though. I am on stock 3.06 not one reboot since I went to work this morning. Get home, install the newest twrp (it is removed in the RUU process), install cm11 snapshot m5, and the appropriate gapps. I got through setup to the point of adding my gmail and it froze and rebooted. I tried cwm recovery too but it made zero difference
TBH my screen is shattered really bad and I was going to replace it but I don't want to if I have to run stock roms forever. I was running one of the original Venom roms before s-off was possible, but then I broke the screen and switched back to my droid bionic but now I can afford the new LCD so I want to get this one running
Click to expand...
Click to collapse
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
lemonoid said:
thats kinda crazy... i was on bionic before my dna. my screen on DNA is shattered like crazy. thought about going back to bionic temporarily, instead i'm gonna replace my screen and RUU and see if it fixes my problem
Click to expand...
Click to collapse
Good news and bad news. The good news is for you!!! I think I figured out what the problem was. It seems to be an issue either with using an older radio, or an older hboot on a newer ROM. I don't know why exactly, but the RUU process was not properly updating my radios. This may be because I ran an RUU while unlocked at one point (every guide I see is very adamant about relocking before the RUU process.)
The bad news is that I ordered a new LCD for my DNA, and I ruined my phone trying to do the repairs. It is by FAR the worst phone I have ever had to work on. I have replaced LCD's in Galaxy devices, Iphones/ipod touches, laptops, TV's, and one in a smartwatch and have never hurt a thing. Got my DNA back together and it flat out wont turn on I don't know what the problem is, but something is fried. Hope you have better luck than me!