So, I was running NeoMax 2.0 for the most part without any problems. I swapped batteries like normal and then the phone started bootlooping, never leaving the HTC screen. I put the regular battery back in and still had the same problems. I had been planning to switch rooms soon anyways, so I decided to flash Neo's AOKP. That ran fine except for that I had no wifi and data would mostly stay on 3G. I tried to do a nand restore to the last working version of NeoMax and the bootlooping continued. I tried to flash the latest ruu and that also had me bootlooping. Going back to AOKP worked just fine but again, no good data connection. Any ideas aside from getting a new phone?
aftafoya said:
So, I was running NeoMax 2.0 for the most part without any problems. I swapped batteries like normal and then the phone started bootlooping, never leaving the HTC screen. I put the regular battery back in and still had the same problems. I had been planning to switch rooms soon anyways, so I decided to flash Neo's AOKP. That ran fine except for that I had no wifi and data would mostly stay on 3G. I tried to do a nand restore to the last working version of NeoMax and the bootlooping continued. I tried to flash the latest ruu and that also had me bootlooping. Going back to AOKP worked just fine but again, no good data connection. Any ideas aside from getting a new phone?
Click to expand...
Click to collapse
going to need some information from you:
are you s-on or off?
what firmware are you on?
what hboot are you on?
question can be answered by turning off the phone. boot the phone up but hold vol- and power. type all the information in the top left corner
synisterwolf said:
going to need some information from you:
are you s-on or off?
what firmware are you on?
what hboot are you on?
question can be answered by turning off the phone. boot the phone up but hold vol- and power. type all the information in the top left corner
Click to expand...
Click to collapse
Current:
S-OFF
Kernel: Snuzzo's Funky v1.3
Rom: Neo's AOKP v1.5 Linaro
Radio: 2.22.10.0801, 2.22.10.0803
HBOOT: 2.27
I am s-off with hboot ver 2.27. The last RUU I flashed was 4.03.605.2 from micromod's thread here. I believe that I used version 1.2. I followed his instructions first flashing the firmware, then recovery, then the ota global plus. This was the same firmware that I was originally on before I left NeoMax2.0. It kept bootlooping so I flashed Neo's AOKP again. Both his AOKP and AOSP work just fine besides the data problem. I also flashed snuzzo's funky kernel v1.3 and it didn't help. So currently I'm stuck in AOKP/AOSP with only 3g data speeds. Should I try flashing an older RUU?
once my phone charges up, i'm going to flash the stock 3.14 ruu. i'll check back and let you know if it worked.
it's a no go. flashed the 3.14 ruu from shippedrom.com and kept boot looping. sometimes it would get to the 2nd htc splash screen but it wouldn't actually get to the rom. fresh out of idea's, could use your magic synister!
hmm sounds like what happened to me i found a thread where they said that when running the .2 global ruu you need to flash it twice in a row ( i did battery pulled when it was ready to reboot then went back into boot loader) and do a factory reset all from the boot loader before you install recovery and then boot rom they say it helps with data problems worked for me anyway
forey79 said:
hmm sounds like what happened to me i found a thread where they said that when running the .2 global ruu you need to flash it twice in a row ( i did battery pulled when it was ready to reboot then went back into boot loader) and do a factory reset all from the boot loader before you install recovery and then boot rom they say it helps with data problems worked for me anyway
Click to expand...
Click to collapse
Thanks for the reply, I'll try it out tonight. I'm thinking that maybe I will try to flash the global that originally came with my phone. I can't remember the exact one, but I think it was the gb version just before ics came out. I'll post an update with the results.
hmm looks like you have the right radios and hboot or anyway its the same as i have but it still wouldn't hurt to start over the only reason i say something is because i skipped the factory reset in boot loader and i had data problems im not the smartest android on the block here...lol so i try not to tell people stuff that i dont know about that well just what worked for me
And flash Neo's CM9 RAGE rom (aka funky symbol rom).
AOKP has issues where you can lose 4G by going into network settings, CM9 apparently does not. Also, make sure your network mode is set to the one that supports several different data modes, even if you don't get them. Trying to use the one that just says CDMA/LTE prevents 4G signal.
And just FYI, you can run neomax 2 on top of the global firmware, you just can't use it as a true global phone since it is an older rom.
Sent from my Rezound using Tapatalk 2
Related
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?
***Pre warning***
Turning your phone s-off gives you a chance of bricking your phone. I am not responsible if you try these steps and have problems. Also you will loose all your data as you will be wiping your phone multiple times. Make sure to backup all your data (I used Titanium backup) OK?! :good:
I had done a ton of research trying to fix the GPS on my HTC Jewel and never found a solution that worked. Issue was the GPS would not lock. I was originally running MeanRom, then JellyBam, and finally switched to CM10.1 nightly builds, all with no GPS. Last night though I finally fixed it and wanted to post this for anyone else having this problem.
Prior to last night here is how my phone was setup:
S-On
Hboot 1.19
Radio 1.12.11.0890
CM10.1 20130224
I saw that HTC released a new update, and started digging on how to update when on a custom ROM. I realized that I needed to go s-off which I had tried last year with LazyPanda, but it failed.
Last night I was able to go S-Off following directions from FacePalm: http://forum.xda-developers.com/showthread.php?t=2163013
It was a lot easier than DirtyRacoon and I'm running Win7x64 which DirtyRacoon says is not supported by them.
Once I was s-off I downloaded the latest Radio 1.12.11.1210 from: http://themikmik.com/showthread.php?13192-RADIOS-RECOVERY-FLASHABLE-Jewel-Radio-Collection
I confirmed that the radio upgraded successfully and rebooted. I was then prompted to activate my phone, and when I tried to activate it gave me the error that I was not authorized! With some help from the FacePalm IRC channel I was pointed to having to flash stock to be able to re-activate and then flash again back to your custom ROM.
I downloaded and flashed with Stock_Rooted_Deodexed_2.13.651.1 found here http://themikmik.com/showthread.php?14585-ROM-Kernel-2-13-651-1-Stock-Rooted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Booted and re-activated, and confirmed GPS working! Then I re-flashed with CM10.1 20130228 and GPS was still working!
I hope this helps others as I have seen a lot of forums with people complaining about the HTC Jewel GPS and saying it's faulty hardware, unfixable, or their fixes are all in app software related.
Thanks!
One thing that I would like to add is if you go stock, do NOT turn off your GPS after you get a lock. I usually have GPS turned off to save battery, but it was the reason why the new ROMs couldn't get a signal.
So to recap
1. Go back to stock
2. Get any old signal even for just a second
3. Immediately flash your new ROM without turning off GPS
4. Enjoy
This indeed works.
I don't like Sense-Based ROMs, so the first thing I did after getting my Jewel was S-Off, and I'm running AOKP. The GPS was driving me crazy, and I couldn't figure out how to get it working.
I updated my radio, flashed a sense-based ROM, locked GPS, then reverted back to AOKP, and it works flawlessly!
This method works!
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
The way I fixed the problem before was to flash back to sense, clear maps data and flash back to CM10.1. Voilà
I use waze
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
The only reason you have to go back to stock is to re-activate your phone.
xlxcrossing said:
Is this really a fix? You described how to s-off and go back to a stock Rom. Are you saying that custom roms don't lock fast enough, if so I've experienced this too. I don't see how going back to stock then flashing a custom Rom would fix that.
Click to expand...
Click to collapse
pbedard said:
I use waze
Click to expand...
Click to collapse
So do I, but before I did this waze just searched for GPS signal.
So tonight I've run into an issue that confounds me. I am a veteran flasher of roms and kernals and never have I found myself so stuck.
I did the following:
1. I applied Facepalm S-Off to my phone earlier and it worked fine, data still worked.
2. I later went to flash Beastmode. I was running Cubed and forgot to reset to stock before flashing.
3. My phone wouldn't boot. So I flashed back Cubed with Fastboot, and the phone boots.
The issue is that now I have no radio. I see the Verizon Wireless on the lockscreen and there are bars on the top bar, however whenever I try to make a call, it says call ended unexpectedly (paraphrase) and whenever I send a text it says SMS Problems. I have wifi, but I need my phone to work as a phone! It also says "Preparing SIM" every few minutes. Any ideas what could be wrong here?
I am currently on NOS N7 with the included Beastmode Kernel.
Thank you in advance for helping me out! I'm a little lost here.
I really hate to bump things, but I need a phone that is... well a phone. If anyone can help that would be great. I am going to have to go to Verizon if not. I have reset everything including unlock flags to stock in preparation of that sad reality.
flash a stock rom and different kernel
azhockey said:
So tonight I've run into an issue that confounds me. I am a veteran flasher of roms and kernals and never have I found myself so stuck.
I did the following:
1. I applied Facepalm S-Off to my phone earlier and it worked fine, data still worked.
2. I later went to flash Beastmode. I was running Cubed and forgot to reset to stock before flashing.
3. My phone wouldn't boot. So I flashed back Cubed with Fastboot, and the phone boots.
The issue is that now I have no radio. I see the Verizon Wireless on the lockscreen and there are bars on the top bar, however whenever I try to make a call, it says call ended unexpectedly (paraphrase) and whenever I send a text it says SMS Problems. I have wifi, but I need my phone to work as a phone! It also says "Preparing SIM" every few minutes. Any ideas what could be wrong here?
I am currently on NOS N7 with the included Beastmode Kernel.
Thank you in advance for helping me out! I'm a little lost here.
Click to expand...
Click to collapse
I'm having exactly Dane issue after flashing beastmode 4.3, how did you fix it?
Sent from my HTC6435LVW using xda app-developers app
motumbo said:
I'm having exactly Dane issue after flashing beastmode 4.3, how did you fix it?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Return to lock using "fastboot oem lock"
Download HTC DROID DNA’s RUU.exe, this is a stock firmware by HTC, which contain radio, systems and bootloader.
make sure that your phone is being detected by your computer. then reboot it into bootloader. When you see Fastboot USB in the middle section run the ruu.exe on your computer.
This should repair bootloader and radios.
dragonstalker said:
Return to lock using "fastboot oem lock"
Download HTC DROID DNA’s RUU.exe, this is a stock firmware by HTC, which contain radio, systems and bootloader.
make sure that your phone is being detected by your computer. then reboot it into bootloader. When you see Fastboot USB in the middle section run the ruu.exe on your computer.
This should repair bootloader and radios.
Click to expand...
Click to collapse
Thanks for your answer. I've tried return to stock with success and now my phone is in full stock state but it keeps showing preparing sim card every two or three minutes exactly as it was before. When I switch the phone to 2g the problem is gone, I bought this phone online and I'm a gsm user so I own the most expensive 2g phone in market.
Phone was perfectly working in all roms and almost every kernel, the problem came up just when I flashed beastmod 4.3 kernel then I went into bootloops and I flashed stock kernel and it booted since that I've been with this issue. I'm gonna try different sim cards because I don't believe this is a software issue anymore.
So this might be a bit convoluted, but here it goes. I was on the OTA path until last week when I decided to flash some kit kat roms. As my title states, I am rooted with s-off, I've flashed several kitkat based sense roms, BSC, Viper, santod, etc...after doing so I lost 4g and 5ghz wifi. When i flash a new rom I will have 4g for several moments but it always drops, additionally I can not see my 5ghz wifi network with wifi set to auto or 5ghz only. I did already have the new radios installed from the recent OTA's, but I thought I would try to see if flashing the firmware santod posted would help. I flashed that through fastboot and it said it installed, although I did not get the same messages that santod mentioned in his post. So I reflashed the stock rooted rom that santod uploaded (santod is a lifesaver by the way), that rom restored 5ghz wifi, but the same issue with 4g. Now, I am having problems with adb and fastboot recognizing my device. I am in it deep here and would greatly appreciate any advice.
Thanks in advance!
Update
micahl88 said:
So this might be a bit convoluted, but here it goes. I was on the OTA path until last week when I decided to flash some kit kat roms. As my title states, I am rooted with s-off, I've flashed several kitkat based sense roms, BSC, Viper, santod, etc...after doing so I lost 4g and 5ghz wifi. When i flash a new rom I will have 4g for several moments but it always drops, additionally I can not see my 5ghz wifi network with wifi set to auto or 5ghz only. I did already have the new radios installed from the recent OTA's, but I thought I would try to see if flashing the firmware santod posted would help. I flashed that through fastboot and it said it installed, although I did not get the same messages that santod mentioned in his post. So I reflashed the stock rooted rom that santod uploaded (santod is a lifesaver by the way), that rom restored 5ghz wifi, but the same issue with 4g. Now, I am having problems with adb and fastboot recognizing my device. I am in it deep here and would greatly appreciate any advice.
Thanks in advance!
Click to expand...
Click to collapse
So, I finally got adb/fastboot to work after about three hours of work including a variety of manually installing adb interface drivers/htc drivers and other misc work. After completing that, I flashed the firmware that santod has uploaded to hopefully resolve 4g issues, but still no 4g :crying: .I have my network settings set to cdma/lte of course...I would love any help.
Thanks
Had the same problem. After flashing the stock rom, you have to flash the stock recovery then proceed to do a factory reset. Make sure to back up all your data first cuz you'll lose it all. That seemed to do the trick for me. Also had problems with texting on kitkat, would get message failed after sending 1 text. Lemme know if that ffixes it.
yesitsneuner said:
Had the same problem. After flashing the stock rom, you have to flash the stock recovery then proceed to do a factory reset. Make sure to back up all your data first cuz you'll lose it all. That seemed to do the trick for me. Also had problems with texting on kitkat, would get message failed after sending 1 text. Lemme know if that ffixes it.
Click to expand...
Click to collapse
I have sent a stock recovery from [Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU] by .torrented on xda, but when I go to boot into the recovery it just reboots to the normal start up...
micahl88 said:
I have sent a stock recovery from [Latest OTA: 3.06.605.4] [Collection] HTC Droid DNA Firmware [Radio] [hboot] [RUU] by .torrented on xda, but when I go to boot into the recovery it just reboots to the normal start up...
Click to expand...
Click to collapse
Go to setting >power (battery) clear fastboot mark.
restart phone asap turn off hold volumen rocker down to enter to stock recovery
do a factory reset*
I'm sure you've seen this by now, but 5Ghz wifi isn't quite working on any kitkat roms. Santo's making progress but hopefully we'll have a stock kitkat kernel, modules, and source soon.
zandarillis said:
I'm sure you've seen this by now, but 5Ghz wifi isn't quite working on any kitkat roms. Santo's making progress but hopefully we'll have a stock kitkat kernel, modules, and source soon.
Click to expand...
Click to collapse
Oh, I actually did not. Thanks for clarifying that for me, I will just keep checking back for rom patches.
Thanks.
finanandroid said:
Go to setting >power (battery) clear fastboot mark.
restart phone asap turn off hold volumen rocker down to enter to stock recovery
do a factory reset*
Click to expand...
Click to collapse
Ok, I followed those instructions, unchecked fastboot, reboot into hboot then selected recovery, the phone goes to the white HTC loading screen that shows "Entering Recovery" on the top for several seconds then just begins a normal boot. I then used adb commands to enter recovery but it did the same thing. I also tried to factory reset from the typical android feature in settings...
Side note, can you explain what happened? I was already on the latest firmware and radio before flashing the rom.
Many continued thanks for the help.
micahl88 said:
Ok, I followed those instructions, unchecked fastboot, reboot into hboot then selected recovery, the phone goes to the white HTC loading screen that shows "Entering Recovery" on the top for several seconds then just begins a normal boot. I then used adb commands to enter recovery but it did the same thing. I also tried to factory reset from the typical android feature in settings...
Side note, can you explain what happened? I was already on the latest firmware and radio before flashing the rom.
Many continued thanks for the help.
Click to expand...
Click to collapse
Ok, I reflashed a recovery from a different source and finally got stock recovery to run then factory reset and then MAGIC 4G reappeared. Thanks. Now, what caused this to happen? Should I not reflash another rom? 4g is more important to me than other roms...
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!