So I've had root (stock Froyo) on my TB for a month or 2 now and really like being able to take off the bloatware and maintain consistent backups with TI and pull back a recovery with ROM Manager.
Over the past 2 weeks or so the damn OTA has been forcing its way into my phone, literally!!!
Every so often I would open my phone and it would be in process of DL a Firmware update. I'd pull the battery and restart and give me a server failure error and I was able to continue wihtout error.
All other times it would give indication that Verizon was trying to do something and I would reject it. It would disappear for a few days and reappear with the same 3 selections. I would always reject.
Then one day, as mentioned previously, I noticed my phone was in process of DLing a firmware update.
I thought I caught it in time, but then it kept happening.
I guess yesterday was the last straw VZW had with me rejecting their update and it was forced on. I was then stuck in a boot loop. It would start up and run some processes, get past the SD connection and then hang for a minute then return to a shutdown.
After this I decided to run the Deodexed 1.70 update and the Radio update.
Sat down last night and started messing with it.
Ran the Deodexed through HBOOT and nothing really happened. Did not process as I would expect or had seen when I set up ROOT originally.
So I then ran the radio through HBOOT and this one ran as expecxted asking me for the next step to run the install.
Seemed to work fine and the phone rebooted without a problem, that is until I saw my phone had 'No Service' on the lock screen and the little [x] next to the reception bars.
I tried running both files again through ROM Manager and received the same result.
What I noticed is the following;
Yeah I switched my Tom's and I had no data connection. This is what I did.
Step 1. ##778
step 2. Password 000000 ( six 0's)
Step 3. Tap on edit mode
Step 4. Go to modem settings and scroll to Rev.A (I was on eHRPD so I switched to Enable or whatever the first option is. If your oh enable switch it to eHRPD I did this setting when I didn't have connection a looong time ago)
Sounds like you successfully flashed an MR2 radio but you are still on MR1 (1.13.605.7 indicated by your screencaps) thus no service.
Assuming your recovery still works, flash the 1.70.605.0 rom via recovery.
bloated: http://forum.xda-developers.com/showthread.php?t=1160374
debloated: http://forum.xda-developers.com/showthread.php?t=1161251
If your recovery doesn't work, reflash it then flash the rom.
As you see in the screencaps, you should see 1.70.605.0 under build and software.
The OP's issue is a common one. Rejecting updates is a sorry way to retain root.
First, the 1.13 RUU that was flashed after rooting via ADB was NOT intended to be retained as the long-term solution. Please take a look at this radio link. As you'll see, RUU 1.13 is OLD. I believe many are under the impression this is the firmware that was on their device pre-root, and it likely wasn't. Most started with RUU 1.66 or 1.68. By running that post-root RUU, you're running firmware that is significantly older and less efficient than just about anything out there. And it WILL continue to attempt an auto-update until you fix that situation.
If you like your stock ROM, flash the RUU 1.68 rooted ROM but keep your radios. An even better idea would be to flash the RUU 1.70 ROM and radios since they are the most stable and efficient Froyo releases out. Of course, flashing a real custom ROM would be the best solution, but I know some people like bone stock or have some irrational paranoia about custom ROMs.
Check the Access Point name
Someone else had a similar problem. He realized he had no Access Point Name assigned. (Menu/Settings/Wireless & networks/Mobile networks/Access Point Name)
He wasn't able to reset it from the menu/reset option on the APN page, but was able to add a new APN with VZWINTERNET as the Internet name with the same settings as the non-working APN. Once he had the new APN enabled, he had data access.
brenick said:
Someone else had a similar problem. He realized he had no Access Point Name assigned. (Menu/Settings/Wireless & networks/Mobile networks/Access Point Name)
He wasn't able to reset it from the menu/reset option on the APN page, but was able to add a new APN with VZWINTERNET as the Internet name with the same settings as the non-working APN. Once he had the new APN enabled, he had data access.
Click to expand...
Click to collapse
Not this case since from the pics, the OP never actually flashed a rom that would work with his radio anyway as I mentioned above.
I have two rezounds, just got the second one. I forgot to restore the stock recovery before doing the OTA, but it seems to have installed OK. However, when I go into Software Information screen, the PRI Version is older than the one on my first Rezound. Everything else is the same on both phones. Did the update fully install? Thanks!
Edit: Wifi isn't working...definitely think something may have went wrong.
Not all phones are on the same PRI. Mine did not change with the OTA, I'm still on an earlier version than some people. I've seen three different versions posted.
As to the wifi... try flashing the 2.x stock kernel from the OTA and see if that fixes it. You're still on stock ROM?
I wonder if different PRI could account for the variable battery drain people seem to be having?
Thanks guys. Wifi is working now and everything looks OK.
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?
I've tried searching google/xda/everything but I haven't turned anything up.
Have had my phone rooted and rommed for a few months without issue. Decided today to try out the kit kat. followed the wiki and updated the radios & the hboot. Flashed the rom & gapps. Booted right up. Except it won't make or receive calls. Under phone info it has 000-000-3891 listed as the phone # - which isn't mine, obviously. Like I said in the title, IMEI is correct, etc. When I try to make a call it says I can call collect press 1, blah blah blah, then something about pushing 411 to win a walmart giftcard??
Do not know what to do. Any advice?
Flash a sense rom(not sense 5) then dial ##72786# and that will put your phone through hands free . and that will hopefully get your phone number back
Sent from my SPH-L710 using Tapatalk
34896549
jessiedrm said:
I've tried searching google/xda/everything but I haven't turned anything up.
Have had my phone rooted and rommed for a few months without issue. Decided today to try out the kit kat. followed the wiki and updated the radios & the hboot. Flashed the rom & gapps. Booted right up. Except it won't make or receive calls. Under phone info it has 000-000-3891 listed as the phone # - which isn't mine, obviously. Like I said in the title, IMEI is correct, etc. When I try to make a call it says I can call collect press 1, blah blah blah, then something about pushing 411 to win a walmart giftcard??
Do not know what to do. Any advice?
Click to expand...
Click to collapse
UPDATE: After a lot of random googles, I ended up on a couple different XDA threads with people having similar issues with other phones. SO Here's how I fixed it:
Downloaded Mean Bean Rom (it's Sense based - none of the other 'stock' roms that I downloaded would go past bootloop). Booted into MeanBean, updated the PRL and all other updates in that same settings menu (I think there was also a firmware). Then, booted into recovery, factory reset, reinstalled the rom I had the issue with & gapps. Booted into the fresh new room without issue. Running great today!
Hope this helps if anybody else encounters this!
first off i would like to say sorry if there is a thread out there discussing this. I have looked all over and didn't find what i was looking for. well i htc dev unlocked my phone and flashed recovery, root etc. when i finished i flashed a gsm rom i believe and ever since i can't make/receive calls and no text. i still have data and sprint said it shows my device as being activated. I'm at a loss please help.
thanks in advance if someone can shed some light
snugglepirate said:
first off i would like to say sorry if there is a thread out there discussing this. I have looked all over and didn't find what i was looking for. well i htc dev unlocked my phone and flashed recovery, root etc. when i finished i flashed a gsm rom i believe and ever since i can't make/receive calls and no text. i still have data and sprint said it shows my device as being activated. I'm at a loss please help.
thanks in advance if someone can shed some light
Click to expand...
Click to collapse
you need to just RUU. If you are unsure how to do this some simple searching will give you all you need but it is quite easy. Assuming you have the sprint variant just RUU The latest version.
OMJ has a wonderful RUU/Firmware/Stock Rom thread under android dev. You will find the latetst RUU there in fact its like the first one at the start of the thread: Make sure you show your thanks to him for it all
http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
As always.. please please read the instructions before doing any of this. If you use the windows RUU make sure you are running windows (duh) and have the latest HTC drivers installed on your machine first by install htc sync manager ( you can remove the sync manager program afterwards and leave the drivers installed if you want) http://www.htc.com/us/software/htc-sync-manager/
PS- it would also help a ton if you gave a bit more info such as what rom you flashed and if you flashed GSM firmware. Depending on the ROM you flashed you might just need to flash the latest firmware. Just to be safe and cover all bases just RUU.
I have already ran the RUU i know at least 6 times and it still didn't work. even goes though the whole activating handset deal. Still no actual cell service.
i flashed Android Revolution HD 14.0 once i was able too. doesn't specifically state that it's GSM but no one really said anything about it working on sprint.
i flashed the firmware via OMJ post about 3 times. all of them full, modified, and radio only. no change in the issue
when i go into the phone identity i have a LTE imsi number but my number and CDMA imsi number are all 0's idk if thats an issue. i also tried to manually reprogram it but when i enter##******# to get to MDN menu nothing happens.
thanks for the quick reply
snugglepirate said:
I have already ran the RUU i know at least 6 times and it still didn't work. even goes though the whole activating handset deal. Still no actual cell service.
i flashed Android Revolution HD 14.0 once i was able too. doesn't specifically state that it's GSM but no one really said anything about it working on sprint.
i flashed the firmware via OMJ post about 3 times. all of them full, modified, and radio only. no change in the issue
when i go into the phone identity i have a LTE imsi number but my number and CDMA imsi number are all 0's idk if thats an issue. i also tried to manually reprogram it but when i enter##******# to get to MDN menu nothing happens.
thanks for the quick reply
Click to expand...
Click to collapse
##786#, menu, reset, let it activate that should fix your phone identity stuff. I had same prob after flashing candyrom. This worked for me.
thank you sooo much. it fixed my problem like a dream.