Related
I just flashed [ROM] (5/25) Nils' Business ICS 4.0.3 Sense 3.6 last night for my S-OFF ReZound. Everything went beautifully and the ROM looks great. The problem I think I have is whenever an app throws up a notification my phone reboots. I first noticed it whenever I sync'd my Google account and it threw up a notification about new gmail messages. So I stopped syncing Gmail. Then it happened whenever I tried to open Twitter/Facebook or when I adjusted the ringtone volume or my alarm went off.
Does anyone have an idea why these things would cause the phone to reboot? Are there any commonalities between these functions?
Weird. Not sure about that. The only rebooting I get on the ROM is when I use my Lock Screen App instead of using the power button. From what I understand though, that is a problem with ALL the ICS versions for Rezound. I can't wait until that is fixed...I hate trying to press that little power button through the small hole in the case I use.
Did you do a full wipe and then flash? Sounds like something residual from a previous ROM. If you did wipe and flash, did you restore anything in Titanium? It clearly states in the OP for that ROM not to do that.
yea i did a full wipe and flash twice. i havent installed or used Titanium to this point.
it first started happening when i attempted to sync my google account, which was about the 3rd thing i did after installing the ROM.
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Someone for mad at me for telling them search the old firmware patch
Is suggest you do the same
If you can't find your sdcard or if your phone reboots when it makes a sound.... You need to flash the old firmware patch
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
if you're referring to the GB firmware patch, then I did do that during the ROM install process per the instructions. i can try doing that again though.
You are on gingerbread firmware correct?
I have read about the patch not working the first time so that could be the issue
Sent from my ADR6425LVW using Tapatalk 2
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
nalees said:
i did come from GB firmware, but flashed the RUU 3.14.605.5 and then flashed the GB firmware patch. after doing this and booting into the RUU, i then flashed Nil's ROM.
Click to expand...
Click to collapse
if you flashed the 3.14RUU, you shouldn't need the GB firmware patch since you are now on ICS.
I would reinstall the ROM and skip the patch.
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
nalees said:
oh ok! i will do that now.
*update 2*
rats, 5 minutes later, as i'm refreshing my twitter app, it reboots. going to see if it continues to replicate. so far it has. uninstalling and reinstalling it. /// still rebooting when i refresh twitter. weird.
Click to expand...
Click to collapse
When you went from gb and ran the ics ruu, did you run the ruu twice.? It only updates a few things the first time through. The second time it does all items on the list.
Sent from my Rezound
oh my, just read through Nil's instructions again and you're right, it does say to run it twice...
i only did the RUU once.
ok, so from here, I need to reflash the RUU one more time? and then reload Nil's ROM?
hmm, also noticed on step #10 i need to unlock the bootloader again? is this true even if i'm s-off?
I went from completely stock to S-OFF and running Nils' latest Business Sense 2 days ago. I have not had any of the problems you mentioned.
His instructions do no say to install the RUU twice. They say that it's a 2 pass affair to install it. If you went through the whole process to install it once, you don't need to do it again.
However, I agree with an earlier post. Installing a GB firmware patch after installing an ICS RUU is probably your problem. Re-doing the whole thing from Nils' instructions for "Latest Leak and Installation Instructions", and then just installing his v4.1 ROM is probably all you need to do to get straightened out.
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
nalees said:
hmm, also noticed on step #11 i need to unlock the bootloader again? is this true even if i'm s-off?
Click to expand...
Click to collapse
It says that in Step #10, I believe. And yes, you have to do that in order to install (or re-install, as the case may be) AR Recovery (Step #11).
---------- Post added at 02:10 PM ---------- Previous post was at 02:03 PM ----------
con247 said:
You absolutely need to flash the RUU twice. The 2nd time it will appear to be stuck on one of the times and flash it like 10 times but that is normal.
Click to expand...
Click to collapse
I started on Monday with a bone stock Rezound. I unlocked, rooted, and did the wire trick for S-OFF.
Then I flashed the 3.14 RUU once, unlocked again, installed AR Recovery again, and then flashed Nils' v4.1 ROM (for S-OFF).
My phone seems to be working fine. Exchange mail (I don't use Gmail), contacts, calendar and tasks. Visual Voice Mail. Notifications. Text messaging. Facebook. WiFi Tether. Google Maps. Camera. Bluetooth handsfree. Everything seems to work fine. The only thing I haven't tested yet, that I mean to, is to force it to 3G only for data and test that I can talk and surf the Web at the same time.
Since I did not flash the RUU twice, what should I be looking for to not work right?
Do not HTC unlock after s-off.
Edit: saw you did.... Basically you will have unlocked or re locked. If you wanted the bootloader to appear stock you have to s-on and do the s-off process again. Then it would say locked. Not a big deal.... Unless you are paranoid and have to do a warranty swap.
Sent from my Rezound
ericsignals said:
Do not HTC unlock after s-off.
Sent from my Rezound
Click to expand...
Click to collapse
yea, i was reading this thread and that's why i thought that...
http://forum.xda-developers.com/showthread.php?t=1620211&page=6
i'll do some more reading before i proceed.
Just tested the SVDO.
Went into Phone Info and set my phone to CDMA Auto (PRL).
Turned off WiFi.
Confirmed status bar displayed 3G.
Called up my bank and let the automated menu thing talk over speakerphone.
Ran Speedtest on phone and it worked.
Went into Phone browser, did a Google search and got results.
Turned on WiFi Tether on my phone.
Connected my TouchPad (running ICS) to phone hotspot.
Ran Speedtest on TP. Got 1934kbps down and 1945kbps up.
I'd say simultaneous voice and 3G data work just fine with Nils' ROM, too...
so i redid everything tonight the proper way and its up and running perfectly! loving it
nalees said:
so i redid everything tonight the proper way and its up and running perfectly! loving it
Click to expand...
Click to collapse
And that releives me. Have fun
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.
Hey guys! So I moonshined and got S-OFF on my phone. I first backed up my factory ROM after I wiped all the data so I would have it to go back to in the future if needed, this was done through clockwork mod. So I first tried using the NOS M7 ROM, didn't like that as the home screen seemed too Window's 8 phone like to me. I then tried the CyanogenMod 10.1, I noticed that my phone was only getting 3G data at this point. I was using my wife's new Galaxy S4 that was getting 4G as a comparison to mine. We were traveling through town so it's not a tower based issue, as her phone showed 4G.
I then tried to switch to viperDNA1.3.1 and I had all sort of issues with it. Heck this morning it would not even show me my alarm notification when it was going off to shut the phone up. I had to power it off to silence it. It even stopped showing the notification bar on the top of the screen and I couldn't even do the drag down thing to see notifications and settings.
So today at work I downloaded RageDNA to see if an optimized stock app would work for me, no change..... I even formatted my sdcard to blank it and the did an adb push to transfer the ROM.zip back to my phone.
SO.... between each app I would launch into ClockWorkMod and 1. wipe dalvik cache. 2. format system. 3. wipe data/factory reset. 4. choose the zip from the sdcard (haha like we really have a true sdcard) and wait for the install and then launch into the phone and do the basic setup to get the ROM working.
HELP!!!! (me crying) I am afraid I did something to my phone during the flashing that jacked up the radio causing 4G to be broken. Is there something else you need to know from me to help me out, please let me know!
**********UPDATE**********
I double checked all my phones settings with a coworker who also has a DNA, but still S-ON. Everything is setup the same for settings on the APN's. I even recreated a duplicate APN that used the specified "LTE" network instead of the one that was defaulted on both of ours "unspecified". No change, even rebooted.
I also restored my CWM backup I did before making any changes to my phone via switching ROM's. The only difference is the fact that their network typeshows "LTE" where my shows "eHRPD". I am going to look into seeing how to reflash the radio to see if something got corrupt.
If it comes down to it I am going to reset my phone back to S-ON and reflash everything that I can find that I can do.
*********Resolution*********
After reflashing my radio, I did not get any 4G signal any more, I know Verizon towers were down for 4G near my work so not sure if they moved over to the towers by my home as I only live 10 minutes from work. So only after being at work for about an hour my 4G signal started on it's own without anything done by me today.
So as I was on the path to trying to take it back to stock I followed the guide that Phaded posted for getting back to S-ON http://forum.xda-developers.com/showthread.php?t=2293919. I had a few issues with that, as it turns out my phone was not showing anything about being "LOCKED" after running his first set of commands. So I pressed forward after talking with Phaded on this situation. I had even flashed from my CWM recovery back to the stock recovery (also notice when running the RUU that it flashes the recovery.) I ran the RUU and then got the 158 error then had to flash the HBOOT. After that flash the phone showed "***Tampered*** & ***LOCKED***". I then proceeded to run the RUU and it completed at that point with no issues. Then the last few DOS commands for fastboot and back to Locked and S-On. I updated back from 1.15 up through 2.06. Also doing so that made me realize you have to step from 1.15 to 2.04 and finally 2.06. So far the 4G is still working. I will keep it stock for a few days to ensure no further 4G issues then I will be moonshining again!!
Just a guess, you may have to flash the boot image. If so the directions are in the install directions for Viper
RLGL said:
Just a guess, you may have to flash the boot image. If so the directions are in the install directions for Viper
Click to expand...
Click to collapse
I just tried to restore my CWM files from prior to any ROM changes. So far I have 3G data, but I tend to get 3G more so at my house than 4G, so not sure if anything will change.
I am wondering if the SIM card could have anything to do with this issue as well.... could a ROM have written to the card and caused it to not read the 4G data, or whatever is on there.
I also see that my phone's network seems to be "eHRPD" not sure if this had anything to do with it or not.
I double checked all my phones settings with a coworker who also has a DNA, but still S-ON. Everything is setup the same for settings on the APN's. I even recreated a duplicate APN that used the specified "LTE" network instead of the one that was defaulted on both of ours "unspecified". No change, even rebooted.
I also restored my CWM backup I did before making any changes to my phone via switching ROM's. The only difference is the fact that their network typeshows "LTE" where my shows "eHRPD". I am going to look into seeing how to reflash the radio to see if something got corrupt.
If it comes down to it I am going to reset my phone back to S-ON and reflash everything that I can find that I can do.
U need a new SIM card. 99% sure that's ur problem. They r free from any Verizon store. Give it a shot before u go thru the hassle of going back to s on and stock.
Sent from my HTC6435LVW using xda premium
if you download from the play store this app (its free) https://play.google.com/store/apps/...GwsMSwxLDEwOSwibmV0LmFuZGlyYy5sdGVvbmZvZmYiXQ.. open it and scroll down what does it say under set preferred network type? that screen has more crucial settings then the normal one. if you running viper in viper tweaks its the first option under misc. If you need help ill put up a pick when i get back. someones borrowing mine cause they stepped on their phone lol.
EDIT: also if you are running viper 1.3.1 you should download ind flash after the normal rom the ota update(the one that says 1.3.1 to 1.3.3.
reaverclan said:
if you download from the play store this app (its free) https://play.google.com/store/apps/...GwsMSwxLDEwOSwibmV0LmFuZGlyYy5sdGVvbmZvZmYiXQ.. open it and scroll down what does it say under set preferred network type? that screen has more crucial settings then the normal one. if you running viper in viper tweaks its the first option under misc. If you need help ill put up a pick when i get back. someones borrowing mine cause they stepped on their phone lol.
EDIT: also if you are running viper 1.3.1 you should download ind flash after the normal rom the ota update(the one that says 1.3.1 to 1.3.3.
Click to expand...
Click to collapse
Too funny that you pointed me to that app, I just found another one LTE Settings.
So I tried your app also and they had the exact same data listed. So here's the screen shots I took from my app I pointed to. My phone will connect to 4G only and only if I choose "LTE only" if I move it to something else either by changing it through the OS settings, or changing it through this app, it goes back to getting 3G service. So at least this tells me my phone isn't broken, just some setting is F***ed up somewhere.
I have tried Global and CDMA/LTE settings with it always showing 3G.
yup that's freaking weird lol swing by a VZW store and get a free sim card since yours seems like it might be messed up what happnes if you flash something like crpalmers kernel though? your boot image might just be all screwed up. his latest version is June 24th.
reaverclan said:
yup that's freaking weird lol swing by a VZW store and get a free sim card since yours seems like it might be messed up what happnes if you flash something like crpalmers kernel though? your boot image might just be all screwed up. his latest version is June 24th.
Click to expand...
Click to collapse
Yeah weird! I just used the DNA Toolkit v1.0.5, I flashed the 2.06 radio and after it rebooted and what not, I went outside (as I have bad service inside this house) and now 4G won't even connect. Not sure if it's the towers, as the one by work went out around noon today.
So as it's a kernal and not a ROM how do I do that, just the same install from zip file in CWM? Do I need any certain ROM for it? As right now I have the factory one that I backed up with CWM when I did S-OFF. (it was a blank fresh factory reset)
chayos00 said:
Yeah weird! I just used the DNA Toolkit v1.0.5, I flashed the 2.06 radio and after it rebooted and what not, I went outside (as I have bad service inside this house) and now 4G won't even connect. Not sure if it's the towers, as the one by work went out around noon today.
So as it's a kernal and not a ROM how do I do that, just the same install from zip file in CWM? Do I need any certain ROM for it? As right now I have the factory one that I backed up with CWM when I did S-OFF. (it was a blank fresh factory reset)
Click to expand...
Click to collapse
if your using viper it supports only 2.04 as a base for its radios i believe. like I said try flashing crpalmer's one this one http://d-h.st/hu7
OH also yeah your towers by you could be experiencing maintenance try driving to somewhere else id say at least a mile away.
reaverclan said:
if your using viper it supports only 2.04 as a base for its radios i believe. like I said try flashing crpalmer's one this one http://d-h.st/hu7
OH also yeah your towers by you could be experiencing maintenance try driving to somewhere else id say at least a mile away.
Click to expand...
Click to collapse
I flashed palmer's and no change. I just texted a coworker who lives about .25 miles away to see if he's getting 4G.
Again right now I'm on the factory ROM.
chayos00 said:
I flashed palmer's and no change. I just texted a coworker who lives about .25 miles away to see if he's getting 4G.
Again right now I'm on the factory ROM.
Click to expand...
Click to collapse
does the factory restore work like your cwm one i mean?
Click on Mobile Data in your settings, and make your 'preferred' network LTE/CDMA.
I had the very same error with the stock phone, and once I switched it - I started getting 4G almost everywhere.
Amer28 said:
Click on Mobile Data in your settings, and make your 'preferred' network LTE/CDMA.
Click to expand...
Click to collapse
That doesn't work, I have tried that like 30 times with no change.
reaverclan said:
does the factory restore work like your cwm one i mean?
Click to expand...
Click to collapse
I'll try the factory restore in the ROM and see what it does. (haven't setup the rom due to the lack of 4g)
chayos00 said:
I'll try the factory restore in the ROM and see what it does. (haven't setup the rom due to the lack of 4g)
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=17145857&postcount=2 found this and it seems like your towers might be experiencing something if they dropped from pure lte to this. like some equipment has failed and it has dropped to a lower communication lvl hardware wise. EDIT: when i meant factory i meant in cwm going to restore and restoring your whole backup(snapshot) of the factory rom that you made not in the rom itself.
chayos00 said:
That doesn't work, I have tried that like 30 times with no change.
Click to expand...
Click to collapse
I don't think you would notice the change instantly. You will see in a few hours, especially if you go somewhere, you will be getting 4G - or if you restart the phone.
Further, what you can do is flash the radio.
Here's the file you need to flash: https://docs.google.com/file/d/0B9yd_oFytDSzUjRpLTZhSFEwWnc/edit
That is a Verizon radio, and it works also with other providers.
Use fastboot to flash:
Code:
fastboot flash radio radio.img
Original thread of the radio: http://forum.xda-developers.com/showthread.php?t=2236633
PS: This is the original verizon radio.
reaverclan said:
http://forum.xda-developers.com/showpost.php?p=17145857&postcount=2 found this and it seems like your towers might be experiencing something if they dropped from pure lte to this. like some equipment has failed and it has dropped to a lower communication lvl hardware wise. EDIT: when i meant factory i meant in cwm going to restore and restoring your whole backup(snapshot) of the factory rom that you made not in the rom itself.
Click to expand...
Click to collapse
When I was at work, I compared a coworkers DNA and he was getting actual LTE signal. So don't think it's that with the eHRDP thing that I keep seeing. But yeah it looks like a "cheaters way" to get their CDMA hardware to work with LTE. lol
Sorry, I feel like a tard and not really following what you are talking about with the "factory" thing. If you mean in the hboot the factory restore, it takes you to the CWM recovery to do that factory restore. Plus the ROM restore seems to almost go through CWM as well, but does it automatically. I'm going to do a full wipe and set this thing back to factory settings. As when it's broke and not working, best thing to do is start fresh.
chayos00 said:
When I was at work, I compared a coworkers DNA and he was getting actual LTE signal. So don't think it's that with the eHRDP thing that I keep seeing. But yeah it looks like a "cheaters way" to get their CDMA hardware to work with LTE. lol
Sorry, I feel like a tard and not really following what you are talking about with the "factory" thing. If you mean in the hboot the factory restore, it takes you to the CWM recovery to do that factory restore. Plus the ROM restore seems to almost go through CWM as well, but does it automatically. I'm going to do a full wipe and set this thing back to factory settings. As when it's broke and not working, best thing to do is start fresh.
Click to expand...
Click to collapse
okay if you do it from hboot it wont do anything cause now cwm will stop that from running but that is the same as running factory reset in cwm, thats not what im talking about though when you first moonshined then booted cwm after getting it, did you run a backup of your factory(stock) ROM? if so it would be in sdcard/clockworkmod/backups it also would have been about 1.5-2GB's. you could also try the radio.img amer is taking about as well, that you need to flash with adb though in fastboot as he stated.
reaverclan said:
okay if you do it from hboot it wont do anything cause now cwm will stop that from running but that is the same as running factory reset in cwm, thats not what im talking about though when you first moonshined then booted cwm after getting it, did you run a backup of your factory(stock) ROM? if so it would be in sdcard/clockworkmod/backups it also would have been about 1.5-2GB's. you could also try the radio.img amer is taking about as well, that you need to flash with adb though in fastboot as he stated.
Click to expand...
Click to collapse
After I noticed my 4G issue, I restore my CWM backup. Yes the CWM backup is what I restored and I am running from right now. It's size is 1.39GB in size.
I will do the radio flash right now.