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
Related
I have two Samsung Fascinates. Both were wiped clean and Odin flashed with DJ01. I followed all the steps to install SC 2.92 Voodoo. One of the phones works fine. The other phone occasionally stops responding in the middle of the screen.
I went ahead and flashed it back to stock and it doesn't seem to have this problem. I have gone from SC to Stock 2-3 times now, and after a few minutes of use it keeps doing this. Is anyone else experiencing anything similar?
Which odin package did you use to return to stock?
There are a few of us on here who have screen response issues. It's even worse when the phone is charging. No known solution. I think it's a problem that carried over from the i9000 which our current kernel is from. I was going to pull the thread for you but the search function is down.
Some work arounds:
Reboot. It will work for awhile repeat as needed
Don't root...
Try my guide, if it doesn't work still.
http://forum.xda-developers.com/showthread.php?t=1001064
Let me know by posting in guide.
Your guide is what I did twice. It appears that this is a known issue with only certain phones. I also noticed that the display is brighter on the fully functional super clean fascinate.
I went ahead and flashed it to stock took it to the Verizon store showed the person that it wasn't as bright at max settings, they said it looks like a manufacturer defect they will send me another phone and just to mail back the one I have.
I also have 2 FC n other one had that so b4 flashin di01 I flashed eb01 stock rom then flashed di01. Now its working flawlessly
Sent from my SC2.9.2Voodoo/EC10 kernel/Nitro Ultra Honeycomb v3.1 using XDA Premium
I am one of the unlucky ones too. I don't think its kernel related. It does it on the OEM mesmerize kernel too (ec10). I think the only real solution is to wait for our OEM update and if it still does it take it in for an exchange.
Very frustrating! !
Sent from my SCH-I500 using XDA App
I had this problem, but once I wiped data, cache, dalvik, and flashed the newest SC 2.9.2, it went away.
a newbe i am wondering what is the differences between eb01 and di01????
newbe here what is the difference between eb01 and di01???
I haven't had a problem since flashing the jt's new kernel. Not yet anyways
Sent from my SCH-I500 using XDA App
mrtonee said:
newbe here what is the difference between eb01 and di01???
Click to expand...
Click to collapse
EB01 is a 2.2 froyo release (not official)
D101 is an early 2.1 eclair release (oem)
thank you...........
Switched the phone out problem gone
that'll do it..
How did you go about exchanging your phone? Did they make you replicate the problem?
Sent from my SCH-I500 using XDA App
I told them that it does it sometimes and it's completely random. I showed them the phone they made sure it wasn't rooted.... and then they said...ok, we'll mail you a new phone just send yours back
Shinebox said:
I told them that it does it sometimes and it's completely random. I showed them the phone they made sure it wasn't rooted.... and then they said...ok, we'll mail you a new phone just send yours back
Click to expand...
Click to collapse
Just spoke with a VERY nice man at VZW tech support. I explained my problem (leaving out a few particulars of course). He had me boot it in safe mode and wants me to run it that way till Monday. Hmmm, yeah. . .that is not going to happen. He said he will call back at 3:00pm Monday and see if my problem went away. I plan on telling him that it made no difference. Am I being unethical?
I would suggest Gizmo Droid's fix for CWM. I flashed through ODIN and checked Repartition like he said. I followed all of his instructions and my phone no longer gives me a headache. Since doing so, I do experience lag, but I no longer need to lock and unlock my phone to make it work.
Update: Downloaded official froyo and had same screen responsiveness issues. Called Verizon and they are sending me a replacement!!
I've been having pretty good success with Imanut's 100mV voodoo kernal with cpu clocked to 800mhz. However, the screen is still unresponsive when the charger is plugged in
Sent from my SCH-I500 using XDA App
So I have gotten a 3d 2 weeks ago as a replacement through asurion for my broken evo 4g and like most people on xda it is only natural to root it and slap on a rom the second you get your hands on it. I checked the hboot and to my hearts content it was 1.4, and easy as cake to root since I was coming from evo 4g. The dilemma is that I have tried several roms and everyone I have loaded would give me random reboots and eventually it would just keep rebooting as soon it loads to the home screen. Realizing maybe if I just loaded it back to stock it would help. The random reboots have cut down but I still get it and it's really frustrating. I have checked the battery and it is not loose, and at this point I don't know what to do. I realize that if I go to the sprint store I have to be able to show them the problem. I am also worried that they will update my hboot to 1.5 and claim that I didn't update system software and just send me on my way. Anyone experiencing the same symptoms as mine? Should I just bring it in to sprint to see if I can get a new one?
Thank you
Sent from my PG86100 using Tapatalk
They will update it I suggest you use a format all zip and flash a haus stock rooted ROM or run a ruu hour that works the got me that way updated my phone cause it was over heating
Sent from my PG86100 using Tapatalk
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Yeah I loaded the RUU on it and turned S-off back on. Just sucks because when it doesn't random reboot or bootloop it works great.
Sad Panda said:
Without more information it would be hard to diagnose it without playing around with the device. It also sounds like it could be the kernel, or overclock settings causing instability because of the voltage either being too low, too high, or heat related. Do you have a custom kernel? If you are, is the device also being overclocked?
The first thing I would do is stop overclocking if you do have a custom kernel. If that doesn't fix it, change the kernel. Remember, some ROMs install their own kernel and you may not even be aware of that. While our devices run the same hardware design there are two possible differences between our device compared to another's. That would be flaws and differences caused by the manufacturing process, and different revision numbers. So while one device runs kernel A @ frequency B very well, another device may have problems and run kernel X @ Y frequency better.
So that could be the issue, and using those diagnostic steps you could easily determine that is the issue, or not.
Click to expand...
Click to collapse
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Is your battery loose?
I thought I had this problem at first too but I just popped a business card behind the battery and Viola no random reboots
Sent from my PG86100 using xda premium
bakarus said:
I am currently running everything stock, reverted back with RUU and turned back S-on, and it still does it, although less frequently. Before I reverted back to stock, I did use android revolutionary 1.1.1 and on boot up it would run unstable. I then applied his stock clock zip, and it seemed to allleviate the problem at first but would again random reboot. After decided to try InfectedRom which worked great but after a day it would just reboot and eventually just bootloop. Unlucky with both decided to try MIUI and ran great for a few days and kept it on the stock kernel, but again the issues have returned. I have properly wiped the phone each time before applying any ROMs and followed the directions with everyone of them. Before trying another new ROMs I would also battery pull each time it bootlooped to see if it was just a fluke, but it would always come back. I am interested in to see what revision it is, how would I check that?
Thanks again for all the advice!
Click to expand...
Click to collapse
Not a problem at all, that is what the community is all about. Free exchange of information, open source advancement of the platform and technology. Everyone gives a little, and takes a little.
I know there is a dialer code that works to give you that information without the need to install any application, or the need for root access, but after lots of research I was unable to find which one would give that info. However, there is a very useful app that you might want to have anyway. It is called "elixir 2", available on the market for free. Once installed, information > click"processor" > more information > processor: (mine says: ....rev. 2 (v71))
Let us know what yours says [for curiosity sake] please
Quick note, if you replaced the phone through asurion and try to replace it doesn't sprint, don't they refer you back to asurion?
Sent from my PG86100 using xda premium
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
kpsingh said:
I would take it to see and request them not to update it they wont ask why not don't worry...
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I requested then not to and they still did the update
Sent from my PG86100 using Tapatalk
So just an update, I finally decided to bring it in store today with it rooted and s-off. I was just so sick and tired of it randomly rebooting I just walked into the Sprint store. Technician brought it in, updated the hboot 1.5 =*(. I checked bootloader, and of course I see the locked in capital letters, but I am still s-off. Does that mean I can still load TWRP and root it? Or do I have to follow the HTC method to root it? Thanks for all the help guys!
If it still says s-off, i believe you are good! but that sounds odd, because otherwise we should all be able to update are hboot after rooting? If anyone knows about this...but anyway...
It was not the hboot upgrade but the firmware upgrade that you needed. You did not have to take it to sprint to do that, they have the firmware update without hboot flooting around the dev threads. 2.3.4 and above roms require the new firmware or you'll get the problems you had. No that you have the firmware a lot of the more cutting edge roms still get reboots with most advanced kernels, you have to watch your rom kernel combo, or stick with the stock kernel.
As for flashing, if you really are s-off still, then you can flash anything you want just like on the ol 4g Let us know. Lucky bastard, have fun
[edit] Found this a few threads down:
"I did what you did, had 1.40 and flashed the wrong update, got 1.50 LOCKED with S-off. You can still flash ROMs and Kernels with no issues. I just had to reload TWRP recovery. Then I flashed the 1.40 Bootloader and all was well.
You can grab 1.40 and flash from here: http://forum.xda-developers.com/show...eng+bootloader
***To others reading this...do not flash this, unless you are S-OFF with 1.50 hboot***
You do not need to UNLOCK using the htcdev method. Just flash the 1.40 hboot and you will be fine."
So reinstall twrp, flash 1.40, and have 1.40 s-off and flash the good way
Yep just flashed old hboot 1.3 and merrily rooted, so far so good running cleanrom 2.9 and taking sad panda's advice trying to figure out if it's app related. I am suspecting that it is groove ip running in the background. So far just installed cleanrom and added tapatalk and SwiftKey
Sent from my PG86100 using Tapatalk
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.....
I know there are several posting about Vibrants shutting down on its own even when it is fully charged, but, most of the posting are about rooted phones. I am experiencing the same problem but with a stock Vibrant upgraded to 2.2 Froyo. Is there a fix for this problem? I just experienced this problem twice today already and I'm hoping stock Vibrant owners might have a solution.
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
cashmundy said:
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
Click to expand...
Click to collapse
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
dustinkh said:
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
I have put my phone back to JFD via Odin quite a few times, let alone resets, so I wouldn't expect much from that. There will apparently never be a stock ICS for the Vibrant. If the underlying problem is indeed fixed in ICS, the OP may want to make the leap to a good rom at some point.
My GF's phone was on stock 2.2 Froyo and shutdown incidentally, it actually just cut power, black screen suddently. Tried two battery and did the same, reflash to VJI6 and JFD and didn't help at all, but after flashing to Bionix 1.3.1 somehow the problem is gone, weird though
Spontaneous halts and reboots indicate a bug in the kernel or drivers. I don't know what bionic uses. ICS kernels are from the 3.x series of Linux, and are incompatible with older roms. Changing ketnel amd/or radio driver might be a way of attacking the problem short of changing roms. I've changed radios with CM7 but still get the halt/reboots.
A spontaneous shutdowm could also be cause by the battery making bad contact.. try smacking or dropping the phone and see if it happens
sent from the xda app on my android smartphone.
I had CodeFire on my DNA for about a month. All was running well. I just installed whatever was current around 2/23 and never installed a nightly update. Last week, I started having problems texting. I thought the ROM was going belly up on me. So I flashed SlimKat. I still cannot text without cycling Airplane Mode in between each. Alternatively, I can wait about an hour to sent a subsequent test message after a successful one.
I just re-flashed the latest radio hoping that would fix it. I'm at a loss. Do I need to call VZW and have them do something on their end?
mdphoenix said:
I had CodeFire on my DNA for about a month. All was running well. I just installed whatever was current around 2/23 and never installed a nightly update. Last week, I started having problems texting. I thought the ROM was going belly up on me. So I flashed SlimKat. I still cannot text without cycling Airplane Mode in between each. Alternatively, I can wait about an hour to sent a subsequent test message after a successful one.
I just re-flashed the latest radio hoping that would fix it. I'm at a loss. Do I need to call VZW and have them do something on their end?
Click to expand...
Click to collapse
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
mdphoenix said:
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
Click to expand...
Click to collapse
The kit kat roms are ported. There are several issues with them that cannot be "fixed" until the source code is released. If the phone does not respond to any commands including trying to boot.... leave it on a factory charger for 24 hours. Then try to work with it
mdphoenix said:
Nothing? Just flashed another ROM. Phone is dead. Am I beating a dead horse with this question? Someone point me in the right direction then, please. Everything I've read states that the SMS issues are related to showing double texts. I can't find this exact problem.
My phone is useless to me now.
Click to expand...
Click to collapse
What do you mean by "phone is dead"? Completely non responsive or no signal. I've been on cfx since I ported it over with no issues besides the random signal drop here and there. But that's maybe a few times per week and happens to me on all ROMs. What do you wipe when flashing a new ROM? Have you tried a RUU?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
What do you mean by "phone is dead"? Completely non responsive or no signal. I've been on cfx since I ported it over with no issues besides the random signal drop here and there. But that's maybe a few times per week and happens to me on all ROMs. What do you wipe when flashing a new ROM? Have you tried a RUU?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Dead as in Roaming again. My apologies for the exaggeration. I'm a bit frustrated here. I cannot seem to win with this thing. I hated my Thunderbolt at the end, but at least it worked. RUU brings back mobile data and texting. I've tried CM 10.2 several times. Each time, it gets stuck in roaming. I cannot change the NV setting. Changing it, then checking it again and it's right back. I've tried flashing with the SIM in. With it out. I've cycled Airplane mode a few times. Rebooted. Installed GApps. Rebooted. Cycled Airplane mode. I'm missing something. Apparently.
I just want a phone without Sense or the Verizon crap. CFX was awesome until this texting issue.
mdphoenix said:
Dead as in Roaming again. My apologies for the exaggeration. I'm a bit frustrated here. I cannot seem to win with this thing. I hated my Thunderbolt at the end, but at least it worked. RUU brings back mobile data and texting. I've tried CM 10.2 several times. Each time, it gets stuck in roaming. I cannot change the NV setting. Changing it, then checking it again and it's right back. I've tried flashing with the SIM in. With it out. I've cycled Airplane mode a few times. Rebooted. Installed GApps. Rebooted. Cycled Airplane mode. I'm missing something. Apparently.
I just want a phone without Sense or the Verizon crap. CFX was awesome until this texting issue.
Click to expand...
Click to collapse
EDIT: Just installed the latest CFX and AGAIN I have the god blessed SMS issue. I can't sent sequential texts. I have to turn on Airplane mode after each one before sending the next.
mdphoenix said:
EDIT: Just installed the latest CFX and AGAIN I have the god blessed SMS issue. I can't sent sequential texts. I have to turn on Airplane mode after each one before sending the next.
Click to expand...
Click to collapse
omfg. I just installed a stock Odexed, Rooted 3.06.605.4. SMS works but now I'm stuck in 3G. Is there a ROM out there that works so I can use my phone for work and play or should I Just suck it up and put it back to a full stock OTA ROM?
mdphoenix said:
omfg. I just installed a stock Odexed, Rooted 3.06.605.4. SMS works but now I'm stuck in 3G. Is there a ROM out there that works so I can use my phone for work and play or should I Just suck it up and put it back to a full stock OTA ROM?
Click to expand...
Click to collapse
Have you considered hardware issues? If it was a ROM issue it wouldn't be a one person issue. Or provide a log of what's happening when you send SMS. You're just not giving us much to go by, except what's not working. Are you doing full wipes between flashing roms, or just cache or factory resets?
Sent from my HTC6435LVW using xda app-developers app
danjull said:
Have you considered hardware issues? If it was a ROM issue it wouldn't be a one person issue. Or provide a log of what's happening when you send SMS. You're just not giving us much to go by, except what's not working. Are you doing full wipes between flashing roms, or just cache or factory resets?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Full Wipes between flashes.
I've had this phone for about two months. I initially had issues flashing CM and being stuck in roaming. No CM ROM I attempt to flash will work. They always end up stuck in roaming. I think the problem is that I can't switch from NV. When I change it, it always goes right back. Not sure what's up there.
I just flashed ★ ☆ [ROM/RADIO][4.2.2] Stock 3.06.605.4 | Rooted | Odex-Deodex | Sense5 And now SMS works, but I'm stuck in 3G.
I hadn't considered hardware only because with each ROM, the previously broken feature works, but then something new pops up.
With one, I can text, but am in 3G. With another, I've got 4G but can't text without cycling Airplane mode.
I sincerely apologies for coming off as a d!ck. I've nothing to contribute to the community but my bug reports and money. It's frustrating to see how quickly some phones are abandoned, though.
I've always been thankful for everyone's help and tried to offer bug reports and donations where applicable.
I just want my phone to work, with a plain vanilla OS and tethering. I don't need Sense. I don't need fancy mods. Just a phone that works.
Please accept my apology, and thanks again for the help.
mdphoenix said:
Full Wipes between flashes.
I've had this phone for about two months. I initially had issues flashing CM and being stuck in roaming. No CM ROM I attempt to flash will work. They always end up stuck in roaming. I think the problem is that I can't switch from NV. When I change it, it always goes right back. Not sure what's up there.
I just flashed ★ ☆ [ROM/RADIO][4.2.2] Stock 3.06.605.4 | Rooted | Odex-Deodex | Sense5 And now SMS works, but I'm stuck in 3G.
I hadn't considered hardware only because with each ROM, the previously broken feature works, but then something new pops up.
With one, I can text, but am in 3G. With another, I've got 4G but can't text without cycling Airplane mode.
I sincerely apologies for coming off as a d!ck. I've nothing to contribute to the community but my bug reports and money. It's frustrating to see how quickly some phones are abandoned, though.
I've always been thankful for everyone's help and tried to offer bug reports and donations where applicable.
I just want my phone to work, with a plain vanilla OS and tethering. I don't need Sense. I don't need fancy mods. Just a phone that works.
Please accept my apology, and thanks again for the help.
Click to expand...
Click to collapse
Verizon is sending me another phone. Stay tuned.
mdphoenix said:
Verizon is sending me another phone. Stay tuned.
Click to expand...
Click to collapse
Have you considered the fact that the recovery itself is causing your issues? I would give TWRP a try to see if there are differences. TWRP is a must to flash KitKat roms and the version used is critical.
RLGL said:
Have you considered the fact that the recovery itself is causing your issues? I would give TWRP a try to see if there are differences. TWRP is a must to flash KitKat roms and the version used is critical.
Click to expand...
Click to collapse
Nope. I didn't consider that. Because most of my problems were with CM 10.2.1. Which is JB, correct?
That being said, I've tried both CW and TWRP to no avail. After being stuck in 3G for two days across multiple ROMs, I'm convinced the hardware went belly-up.
New SIM?
HTC DNA
LG Optimus G
mdphoenix said:
Nope. I didn't consider that. Because most of my problems were with CM 10.2.1. Which is JB, correct?
That being said, I've tried both CW and TWRP to no avail. After being stuck in 3G for two days across multiple ROMs, I'm convinced the hardware went belly-up.
Click to expand...
Click to collapse
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
RLGL said:
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
Click to expand...
Click to collapse
I did lots of searching before asking. I try to do my due diligence before bothering you all.
The replacement phone did not resolve the problem. The replacement SIM did.
Now on to bigger and better things. Thanks for putting up with me.
And now I can't text without cycling Airplane mode again.
Sent from my HTC6435LVW using Tapatalk
RLGL said:
Santod has a process to recover the unit from the conditions you describe. It is fairly simple and doesn't appear to require much time.
I don't have time to search for it at the moment.
Click to expand...
Click to collapse
Are you certain it was Santod? He's only got 19 posts on this board and I don't see anything directly related to the SMS problem I'm having.
mdphoenix said:
Are you certain it was Santod? He's only got 19 posts on this board and I don't see anything directly related to the SMS problem I'm having.
Click to expand...
Click to collapse
Yes it is on This page
RLGL said:
Yes it is on This page
Click to expand...
Click to collapse
Since my last update, I've received a new DNA, and a new SIM card.
Check out the last few posts here: http://forum.xda-developers.com/showthread.php?p=51465109
This is bizarre. Either I'm doing something wrong, or... I don't know. SMS works on a stock ROM but not on a custom ROM, with a new phone, with a new SIM.
I think you are doing something wrong.
RUU the latest firmware, factory reset, wipe data, cache, and system, install a ROM and DO NOT restore anything.
I think youre not completely wiping and/or are restoring things.