So I have Tmobile HTC One, rooted, S-off, converted to GPE.
I got the update today, ran it. I have TWRP. It installed, then the boot animation came up, and my screen stayed on but was blank for over 5 minutes. I rebooted it, same thing. I rebooted and cleared Dalvik Cache & Cache. Same thing.
It now wouldn't stay turned off. So I left it sitting while I started looking for some info, about 15 minutes later I heard noises. Saw that my phone had come all the way up. Joyous & Happy I started looking around. Found that it removed a couple of my apps. No bigger. Then I saw weird graphical glitches at the bottom of the screen.
Got worried, tried to reboot. The screen darkened, but the reboot options never came up. I forced it to reboot, it comes up fast like its supposed too. Same thing though. Weird graphical glitches, and no reboot menu.
I'm afraid I screwed it up when I cleared the cache while it was obviously still initializing the install.
First off, any ideas?
Second, can I just rerun the OTA once its posted online?
My WiFi works better now, I love the new dialer.
Hopefully you did a nandroid backup before you run the update, if so try to restore your backup and wait till someone manage to root 4.4.3.
if you didn't create a backup, I'm afraid you have to flash GPE 4.4.2 RUU pre-rooted.
critterhart said:
So I have Tmobile HTC One, rooted, S-off, converted to GPE.
I got the update today, ran it. I have TWRP. It installed, then the boot animation came up, and my screen stayed on but was blank for over 5 minutes. I rebooted it, same thing. I rebooted and cleared Dalvik Cache & Cache. Same thing.
It now wouldn't stay turned off. So I left it sitting while I started looking for some info, about 15 minutes later I heard noises. Saw that my phone had come all the way up. Joyous & Happy I started looking around. Found that it removed a couple of my apps. No bigger. Then I saw weird graphical glitches at the bottom of the screen.
Got worried, tried to reboot. The screen darkened, but the reboot options never came up. I forced it to reboot, it comes up fast like its supposed too. Same thing though. Weird graphical glitches, and no reboot menu.
I'm afraid I screwed it up when I cleared the cache while it was obviously still initializing the install.
First off, any ideas?
Second, can I just rerun the OTA once its posted online?
My WiFi works better now, I love the new dialer.
Click to expand...
Click to collapse
If you can boot into bootloader/FASTBOOT USB and run fastboot getvar all to see where you are in the install. The OTA will not run properly if you do not have the stock recovery and stock rom in place OTA will have two version numbers in the title, the first is the new version and the second is the old version this one must match for the OTA to run. If your getvar is like it was previously, then try to install a stock recovery then the OTA. If you have a backup as @aaswar states then run it first, then the stock recovery.
Related
Hey guys,
little frustrated here as i am having some issues. I have the ERIS running Gin tazz CM7, and when the phone is on, it runs flawlessly, but as soon as i reboot or turn the phone off, and turn it back on, i get a force close error message stating "com.android.phone" has stopped working, and pretty much makes the phone useless. I then have to wipe and re-flash the ROM and everything is fine again, until I reboot/turn phone off and boot back up.
I experimented a little last night, and put the phone in airplane mode and shut the phone off, rebooted, and turned it off of airplane mode when it was done booting, and i did not get that message. I thought i had found the cure. Rebooted again and got the same error message! I'm pulling my hair out, not sure what else to do. Has anyone heard of this issue, and if so is there a quick fix? FYI i used another ROM and it did the same thing, so i do not think it is the software. It is almost as if on the reboot it can't load the necessary "codes" to get the radios up and running again. Any feedback appreciated!
p.s i attached a screenshot to let you guys see what the error message looked like!
do you do full wipes of data and dalvik for every flash? The same issue hit me one time when I had not done wipes of both. I went back and wiped both, dalvik I just went ahead and wiped three times. Idk that three times matters but I wanted to make sure I was good to go and I know I had seen workshed post before about 3x wipe of dalvik. When I went back and wiped everything like that and re-flashed everything went back to normal for me.
The wipe of Data & Dalvik is a critical step. Like the poster above me, I've heard the "3 times" suggestion and I'm not sure why 1 versus 3 would make a difference. However, just to be safe, I have started wiping Data & Dalvik 5x each, each time I flash. It's most likely just overkill & paranoia, but hey, I've had no issues.
Some roms, depending on what are are upgrading from, may also require you to delete a folder from your sd card. For example, as Workshed states in his GSB v3.7 thread,
"If you're coming from a cm6 or 2.1 ROM, make sure you delete .android_secure folder on your sdcard before flashing."
http://forum.xda-developers.com/showpost.php?p=11178912&postcount=1
Hope this helps!
Having similar problems. Only wiped once, I'll try it a few times and see how that goes.
I was running Eternity version 116 for a long time, and decided i should upgrade to a more recent rev. I tried flashing v236 (and 238 and various versions in between) and all appears to go well, I get a message for successfully installing, but on first reboot, I get stuck on the splash screen. While I haven't tried many ROMs, I always wipe first. I am currently running Bamf Forever. But for whatever reason, I just can't get Eternity to load. Any suggestions? Thanks!
If you wiped data first and didn't get a bad download (if you've tried multiple versions, that would be very unlikely) then there really wouldn't be a logical reason for it not to work. All I can tell you is that it takes a long time (5 minutes maybe) to boot up the first time you flash a new ROM, I think it's because it zipaligns your apps. Hope you figure it out, if you find out what the problem was, let me know.
I've let it boot up for hours, but it never gets past the splash screen.
are you wiping data/cache/dalvik
Bigandrewgold said:
are you wiping data/cache/dalvik
Click to expand...
Click to collapse
Yes, wiping everything. I don't seem to have a problem installing other ROMs, just Eternity.
disregard. i got 216 to work. i don't know wtf was going on. but i'm happy now.
Glad you got it working. There have been some significant changes since 216 that makes it worth your time to upgrade to R238.
I figured out what the problem was. turns out all i needed to do was update CWM. now all versions flash fine. I was using a 3.0 version of CWM.
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,
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
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!