Is this happening to anybody else? My phone reboots several times a day and I cant seem to pinpoint the cause of the problem. I have tried various kernels and versions of CM7 (running latest RC now). My phone is not overclocked and is not having any heat issues. Does anybody have any ideas on how to fix the problem?
I have not had a single reboot since I put 1.5.2 on my phone. I did not wipe coming from 1.4 but I didn't have any issues on that build either. Have you tried wiping data and cache yet and reinstalling?
Sent from my ADR6400L using XDA Premium App
You mentioned it isn't overclocked, but is it undervolted by your own modding at all? Other than that only thing I can think of are the reboots people were just experiencing in general (most likely due to the handoff between LTE and CDMA).
To answer the two previous comments. First, my phone is not undervolted. Second, I have erased everything and done a fresh install several times. Thirdly, I live in Richmond VA so I don't even have LTE enabled. I just enabled it yesterday and it seemed to decrease the number of reboots today. Yesterday I have about 4-6 while today I only had one. I think that all this began when I switched to the MR2 radio.
Is there a proper way to go from an earlier radio to the current or is it like flashing anything else?
Flashing the radio is pretty much just like anything else. Go into the bootloader and have the radio .zip on SD card named correctly and that's basically it.
You flash radios from hboot.
Pull battery, hold power and vol down
courtesy of my rooted bolt
Ya, that's how I've been flashing my radios. I just don't understand why the Mr2 and 2.5 radios would cause my phone to reboot.
Not too familiar with AOSP Roms, but have you tried the official OTA radio?
courtesy of my rooted bolt
Alright, so first off I've had a few phones which I have rooted and modded to the extreme. Got a great deal on a e3d and came over.
Saw that i had hboot 1.50 and *tear*, however I followed the directions to a T and unlocked the phone, installed recovery, and threw on some well known mods.
MeanROM
CleanROM
Virus ROM
etc etc
Anyway, in all of the ROMs the camera is distorted, and when you try to use 3d it comes out greenish pixelated and crashes. When you take a 2d picture you can't see what you're pointing at, but when you click it takes a picture but well...see attachment.
Now here's what i have tried:
Re-wiped ROMs several times.
Installed Stock Kernals, and every kernel I could find.
Used the Flash app, used adb reboot-bootloader and then booted into recovery to flash roms, and most recently I re-locked the phone and used the RUU updater and Unrooted and installed stock back on phone.
STILL having same problem with camera.
So I'm asking anyone who'd like to help please, because if I can't get it working I'm taking it to sprint hopefully they'll replace it.
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
wassti said:
I would try running the RUU and see if that will get the camera going.
If it runs on stock then maybe your downloads got goofed up or somethin?
Also I think MeanROM is 2.17 base? (correct me if I'm wrong) but I think you need to update firmware on the phone for stability. The camera could be related. However I also think Virus' ROMs are 2.08, so that almost makes me think that this paragraph could be wrong.
Click to expand...
Click to collapse
Already tried unrooting and flashing RUU. Still nothing....
Edit: I tried a factory recovery and no dice.
I'm going to try re-rooting and sending the camera file to the phone. Maybe it got corrupted?
Still open to suggestions.
Nope....
Sent from my PG86100 using xda premium
Ok so camera is clearly hardware issue. I relocked and factory reset. Camera still didn't work, today I clicked camera to show a friend. I had a twenty and accidently rubbed it on the screen and magically a picture appeared but it was split. I took a picture and boom it works. I'm going to mod it again when I get home, and I'll document the results, need to find out what happened.
Sent from my PG86100 using xda premium
It's a software issue. I am going to attempt to flash the kernel again and see if I can get it to work, anyone want to give me some tips?
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
RavenFB said:
It looks like I am having precisely the same issue. My camera worked fine until today. I restored a Nand backup of my original stock yesterday, but the camera was working fine after that. It started acting up when my wife called me on Qik Video. Tried restarting the phone numerous times, no dice. Came on XDA to hunt for stock kernels, thinking maybe my kernel got borked in the restore process? I'm truly shocked at just how huge a pain in the rear this phone is in terms of modding. Seems I am constantly having problems with it.
Click to expand...
Click to collapse
Mine was actually a hardware issue, it was coincidental that the camera stopped working when I changed roms. Anyway, I have a refurbished phone on its way and hoping for hboot 1.4 I doubt it though.....
Curious to hear from the people that are still s-on and flashed the new ICS leak, how is your phone running? Are there any problems youve run into?
v36sedan said:
Curious to hear from the people that are still s-on and flashed the new ICS leak, how is your phone running? Are there any problems youve run into?
Click to expand...
Click to collapse
I tried it. Major change was an updated kernel. Reverted back to BAMF 2.1 with the previous kernel, as it didnt play well with the change. I'm just waiting for the roms to either be rebased or the OTA to be released. No radio changes only an updated hboot and a few fixes in the rom itself.
Would you run it over the gb rom the phone comes with as a daily driver?
v36sedan said:
Would you run it over the gb rom the phone comes with as a daily driver?
Click to expand...
Click to collapse
Mine loves the new radios, so yes. For most users; they have experienced issues with the radios. My suggestion; s-off before flashing either the old or new leak. That way if you do experience said issues, you will be able to rollback. Also, brings up the thought of being OTA compliant, but that shouldn't matter much as most of the devs here would hve a working rom based off the OTA shortly after.
v36sedan said:
Would you run it over the gb rom the phone comes with as a daily driver?
Click to expand...
Click to collapse
Quite honestly, I don't notice a difference one way or another. This leak was played better with my phone regarding mounting and recovery issues I had on the first ICS leak, but that is more an individual issue I had. As far as signal and reception , I think it is just the fact where I live all of the radios have been the same for me. I am in a rural area of wisconsin with just 3G, so haven't benefitted from 4g or difference in signal strength.
In my opinion, it's easier to s off than to flash the new firmware using the s on method and relocking bootloader and then upgrading then reunlocking and installing recovery and a rooted rom. Also, I've helped about the same amount of people with both. For some crazy reason even though the software seems a breeze to me, people get confused with so many steps I guess, and people who are performing s off and ask me to watch over their shoulder are having much better results than upgrading the firmware.
Every once in a while, my screen will go white when I try to connect to the internet or the play store. Back button won't work, only the home button will. Then I have to restart my phone to access the internet. This has been happening since the update. Anyone else?
Sent from my EVO using Tapatalk 2
Yes I see this also. I wounder if it is Sprint network?
I've seen this also, it seems to do this in any browser that i've thrown at it. I don't think it is the network as a web page that isn't loading due to traffic shouldn't lag the phone. When mine does it i can't even turn the screen off until its done being stuck. I was trying meanrom so i updated to the newest firmware and baseband, but i reverted back to an old nandroid of charmelon rom which is 1.13.
The nandroid didn't seem to restore the baseband nor do i think it was designed to, but long story short i'm still on the newer baseband and being that the common point between you and I is probably that, i'm going to guess there is some kind of issue in the radio thats locking up the phone.
I'm going to flash back down to the original radio and see if it changes things.
I'm on stock.
Sent from my EVO using Tapatalk 2
you're on the update, so you're on the 1.22 firmware with 1.05 something radio. I was saying that it might have had something to do with the radio.
Im stock and i have been getting this white screen after the update.
I thought it was an app i had , but i see other people having this, so i dont know what could be.
Sent from my EVO using xda app-developers app
lacrossev said:
you're on the update, so you're on the 1.22 firmware with 1.05 something radio. I was saying that it might have had something to do with the radio.
Click to expand...
Click to collapse
Is there anything that can be done about it? I'm not tech savy, so I know I won't be rooting.
Sent from my EVO using Tapatalk 2
I've just flashed back down to the older radio so i'll have to try it a few days and see if thats even the issue.
I'm not sure if theres anything to be done on a stock unit, unless maybe you're able to run an RUU of the original rom and have it restored back to the day you recieved it.
So, a few days ago, I went to unlock my phone to read a text message. Before it would even unlock, the device froze, and instantly started bootlooping. I've tried everything I can think of (flashing several different ROMs/kernels, wiping everything (including the internal data)) and nothing seems to work. Occasionally, it'll boot into the OS, and work properly–but will then randomly freeze up, and continue bootlooping. I can't seem to isolate what's causing it. I first thought it was receiving text messages, which it wasn't. Then, it seemed to do it any time there was audio (aside from startup audio (it's currently got Scott's BAMF Sense 5 on it), which now doesn't seem to be the problem. Currently, I'm thinking it might be because of the USB cable I'm using to charge it, as it started bootlooping upon being plugged in (to my computer, with debugging enabled), but it's still bootlooping even after being unplugged. I don't know what else to try, and have already lost all my personal files on the device, so I'm pretty much down to try anything. I'm S-OFF, with Eng HBOOT. Thank you in advance for any assistance you can offer.
phuckwithfire said:
So, a few days ago, I went to unlock my phone to read a text message. Before it would even unlock, the device froze, and instantly started bootlooping. I've tried everything I can think of (flashing several different ROMs/kernels, wiping everything (including the internal data)) and nothing seems to work. Occasionally, it'll boot into the OS, and work properly–but will then randomly freeze up, and continue bootlooping. I can't seem to isolate what's causing it. I first thought it was receiving text messages, which it wasn't. Then, it seemed to do it any time there was audio (aside from startup audio (it's currently got Scott's BAMF Sense 5 on it), which now doesn't seem to be the problem. Currently, I'm thinking it might be because of the USB cable I'm using to charge it, as it started bootlooping upon being plugged in (to my computer, with debugging enabled), but it's still bootlooping even after being unplugged. I don't know what else to try, and have already lost all my personal files on the device, so I'm pretty much down to try anything. I'm S-OFF, with Eng HBOOT. Thank you in advance for any assistance you can offer.
Click to expand...
Click to collapse
Flash twrp. make a nandroid. Wipe system and do factory reset. Wipe cache and dalvik. Get a rooted stock rom and install that. If that works, wipe all again(NOT DATA, only factory reset) and flash a custom rom.
123421342 said:
Flash twrp. make a nandroid. Wipe system and do factory reset. Wipe cache and dalvik. Get a rooted stock rom and install that. If that works, wipe all again(NOT DATA, only factory reset) and flash a custom rom.
Click to expand...
Click to collapse
I'm already on TWRP. I'll flash the newest version as soon as I can and give your suggestion a try. Are stock, rooted ROMs going to be in the Android Development section? Also, should I try using Zarbos' modified TWRP recovery, since it seems to be more stable with Aroma installs, or just go with the latest stock?
Thanks for the speedy reply.
After installing the latest TWRP (2.5.0.0), and following your directions (flashing 2.06 stock, rooted), it bootlooped 2 or three times, then went into the OS. It's still currently in the OS, but I don't think the issue is fixed, as it bootlooped immediately after flashing the stock ROM. I'll report back if/when it does it again.
Edit: After I unplugged the USB cable from the phone (the other end is plugged into my laptop), it immediately froze and started bootlooping again.
What's truly bizarre to me is, the first time it happened, I wasn't doing anything out of the ordinary. I hadn't flashed ANYTHING for weeks. It just started out of the blue, which leads me to believe it may be a hardware issue. It doesn't seem to feel any hotter than normal, so I don't think that's the issue (although, I could be wrong). GAH!! :'(
What kernel are you using? I had tons of bootloops with beastmode underclocked to 192. When I brought the min frequency up to 384 it stopped. I'm assuming you're not using the same kernel every time right?
Sent from my ViperDNA using Tapatalk 2
phuckwithfire said:
What's truly bizarre to me is, the first time it happened, I wasn't doing anything out of the ordinary. I hadn't flashed ANYTHING for weeks. It just started out of the blue, which leads me to believe it may be a hardware issue. It doesn't seem to feel any hotter than normal, so I don't think that's the issue (although, I could be wrong). GAH!! :'(
Click to expand...
Click to collapse
If you were on a PC, those symptoms would lead me to believe you were sitting on some faulty memory modules. The random nature of the occurrences sounds like hardware.
Sent from my DROID RAZR HD using xda premium
phuckwithfire said:
After installing the latest TWRP (2.5.0.0), and following your directions (flashing 2.06 stock, rooted), it bootlooped 2 or three times, then went into the OS. It's still currently in the OS, but I don't think the issue is fixed, as it bootlooped immediately after flashing the stock ROM. I'll report back if/when it does it again.
Edit: After I unplugged the USB cable from the phone (the other end is plugged into my laptop), it immediately froze and started bootlooping again.
Click to expand...
Click to collapse
Look on. YouTube sounds llike ur having a similar issue. Guy could get his phone to work plugged into usb but then bootloops after unplugging
Sent from my HTC6435LVW using xda premium
You mentionioned the bootlooping after unplugging the phone, maybe there's some junk in the phone's micro usb port.
And try a different usb cable, maybe one of the contacts are loose and when you unplug it from the phone it shorts something.
jamiethemorris said:
What kernel are you using? I had tons of bootloops with beastmode underclocked to 192. When I brought the min frequency up to 384 it stopped. I'm assuming you're not using the same kernel every time right?
Sent from my ViperDNA using Tapatalk 2
Click to expand...
Click to collapse
The only kernel I manually flashed during this debacle was Beastmode 4.1 (which is supposed to be stable). Aside from that, the kernels have all been automatically flashed when flashing a ROM, as I'm S-OFF.
eakeller said:
If you were on a PC, those symptoms would lead me to believe you were sitting on some faulty memory modules. The random nature of the occurrences sounds like hardware.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
Faulty memory modules in the phone, or laptop?
kaliblazin707 said:
Look on. YouTube sounds llike ur having a similar issue. Guy could get his phone to work plugged into usb but then bootloops after unplugging
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Is the video for a DNA issue, or other phone, so I know what to search for?
orangechoochoo said:
You mentionioned the bootlooping after unplugging the phone, maybe there's some junk in the phone's micro usb port.
And try a different usb cable, maybe one of the contacts are loose and when you unplug it from the phone it shorts something.
Click to expand...
Click to collapse
I've tried a different cable, so that doesn't seem to be the problem.
After flashing stock, rooted 2.06, I was only able to get into the OS once. I reflashed Scott's Sense 5 BAMF today, and I can get back into the OS, but it's hit or miss. Sometimes it'll bootloop for over an hour, sometimes it'll only do it a couple of times. I'm once again thinking it's a sound issue, though (maybe with the hardware). After I got a text with the volume all the way up, it froze, and bootlooped. When I got back in, I turned the sound off, and it stayed in the OS, until I was driving to work and wanted to listen to music. As soon as I hit play in Slacker (with an aux audio cable plugged in), it froze, and began bootlooping.
I'm leaning towards hardware issue. Perhaps you could just save yourself the trouble and see if you can warranty it with HTC. Of course, then you have the issue of trying to get a phone without the ota.
Sent from my ViperDNA using Tapatalk 2
Out of complete morbid curiosity–since Flyhalf205's CM ROM is 'mostly' working–I'm going to try flashing that.
jamiethemorris said:
I'm leaning towards hardware issue. Perhaps you could just save yourself the trouble and see if you can warranty it with HTC. Of course, then you have the issue of trying to get a phone without the ota.
Sent from my ViperDNA using Tapatalk 2
Click to expand...
Click to collapse
That's what I'm thinking, too. Although, I'm not super against getting one post-OTA, as HTC has thrown us under the bus, anyways, and released a NEW flagship device. Granted, it might not be coming to Big Red, but I'd rather sell my DNA, and get an S IV, which is guaranteed to have more devs. HTC done pissed me off by releasing the One so shortly on the heels of the DNA. Now, this (probable) hardware issue, and it's not even a year old. I'm losing more and more faith in my once-favorite OEM.
Should I try relocking the bootloader, and RUU-ing it? I guess I'll have to do that, anyways, since I'm most likely going to have to try and have it replaced under warranty... Ugh. t(-_-t)
That almost has to be hardware....on the phone.
Sent from my DROID RAZR HD using xda premium
eakeller said:
That almost has to be hardware....on the phone.
Sent from my DROID RAZR HD using xda premium
Click to expand...
Click to collapse
That's certainly seeming to be the issue. Ugh... Stupid Verizon. I don't want to have a locked phone. -_-
Did you flash a stock kernel after flashing stock rom? flash a stock 1.15 rom, flash the newest radio, and flash a stock kernel. Bootloops tend to be a kernel issue. Are you running anything that modifies the kernel(onepowerguard, kernel tuner etc)
123421342 said:
Did you flash a stock kernel after flashing stock rom? flash a stock 1.15 rom, flash the newest radio, and flash a stock kernel. Bootloops tend to be a kernel issue. Are you running anything that modifies the kernel(onepowerguard, kernel tuner etc)
Click to expand...
Click to collapse
No, I didn't. Shouldn't it have flashed the stock kernel with the stock ROM I flashed, since I'm S-OFF? Since I've formatted the device (including data), there's not much on it at all, anymore. I'm not running any tuner apps.
phuckwithfire said:
No, I didn't. Shouldn't it have flashed the stock kernel with the stock ROM I flashed, since I'm S-OFF? Since I've formatted the device (including data), there's not much on it at all, anymore. I'm not running any tuner apps.
Click to expand...
Click to collapse
Doesn't hurt to flash a custom kernel anyway try dsb read write kernel
Sent from my HTC6435LVW using xda app-developers app
DNA boot loops after unplugging usb should yield the video
Sent from my HTC6435LVW using xda premium