Related
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.
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?
okay so last night i was flashing Roms trying them out to see witch one would be my daily driver
but the problems happened when i flashed MIUI. Then I flashed newts one xxx and i had the roaming triangle on my signal bar
now when ever i try to use my phone it says no service and the 4G is pretty slow
I already went to settings > mobile network > and the setting in there and still no luck
im s on
HTC unlocked
any help thanks
is ur radio up2date ?
did u flash the ruu of global rom ?
No i havent how would i go about doing that
what is your hboot?
Option1:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Option2:
Go into mobile network settings and change to Global Mode. If already on global. Change to CDMA/LTE auto
EDIT
I posted in the wrong thread
Thank you all for your help
Flyhalf205 I flashed the recovery and factory reset and that worked. Thanks a lot
Flyhalf205 said:
Flash the stock recovery. Then try a factory reset inside of HBOOT.
Link to stock recovery: http://goo.im/devs/Flyhalf205/Rezound/Recovery/stock_recovery_signed.img
Click to expand...
Click to collapse
It's many months since Flyhalf's post, but I wanted to report that after getting a replacement unit, I also ran S-OFF and htc dev unlock and pushed the radios forward to the latest and found that I could no longer make or receive calls, send or receive texts, although data/4G/wifi and BT were all functioning nominally. Tech support couldn't solve it; a new SIM card couldn't change things, and when I finally rolled all the way back to the last GB RUU, and FINALLY did a factory reset WITHIN HBOOT that cleared the problem. I then let the handset download the OTA's one by one to bring it up to speed.
I'm putting this here because I didn't find anything else for "no phone service" or "lost cell service" and was about to open a new thread in troubleshooting when I found this thread, followed Flyhalf's advice and I am now fully operational again. Hppefully someone else doing a similar search will see this post.
hgoldner said:
It's many months since Flyhalf's post, but I wanted to report that after getting a replacement unit, I also ran S-OFF and htc dev unlock and pushed the radios forward to the latest and found that I could no longer make or receive calls, send or receive texts, although data/4G/wifi and BT were all functioning nominally. Tech support couldn't solve it; a new SIM card couldn't change things, and when I finally rolled all the way back to the last GB RUU, and FINALLY did a factory reset WITHIN HBOOT that cleared the problem. I then let the handset download the OTA's one by one to bring it up to speed.
I'm putting this here because I didn't find anything else for "no phone service" or "lost cell service" and was about to open a new thread in troubleshooting when I found this thread, followed Flyhalf's advice and I am now fully operational again. Hppefully someone else doing a similar search will see this post.
Click to expand...
Click to collapse
I wanted to 2nd this post with a small addition. After S-offing my rezound and flashing the latest CarbonRom, I ended up losing 4G. I mistakenly though it was related to gaining s-off and performing a full factory restore and update. I was left with a phone that did everything but receive 4G signal. I had reliable 3G data and could make/receive calls/SMS/MMS. I only lost 4G data. After finding this post, thank you hgoldner for talking it up, I flashed the ICS RUU and then performed a factory reset. I probably could have just flashed the stock recovery but the Goo.im servers appear to be acting up and I couldn't download it from Flyhalf's link above. For those of you with signal issues following a custom ROM flash, I'd definitely suggest giving this a try.
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!
Hello all.
New poster here, been coming here for some time though for the loads of great information and generally helpful people.
I'm having an issue with my Honor 5x, and I seem to be the only one i can find on this forum having this issue.
The issue that I am having is that I lose the ability to connect to the cellular networks (I am actually running dual-sim) when I load a custom ROM after the first reboot.. The first time this happened, it even lost the IMEI numbers (WTF). I restored from the backup I made, and tried again. I got the same result, after the first reboot, it can no longer find the cellular networks, and when i try to search for network providers, it gives me an error simply saying "Error searching for networks." Restore backup again, flash resurrection rom to see if maybe CM13 is just being stupid with my phone, got no signal right off the bat, and could not find networks.
At this point, I restored the stock recovery, and let it recover my phone to stock, which is where I am at the moment, since it works. Also noteworthy, that every time I restored from backup, the phone had no problems at all connecting to the cellular networks. as well, it never had an issue through all of this with connecting to WiFi.
Relevant Information:
Phone Model: KIW-L24
Build Number: KIW-L24C567B331
Emui Version: 4.0
Android Version: 6.01
Kernel Version: 3.10.49-g472a5b3
Location: United states
Carriers: Cricket, MetroPCS
Bootloader is unlocked
I have not restored root access
I have Flashed TWRP and made a full backup (again)
I'm getting the feeling that it is due to to something that I have forgotten, but I can't seem to think of anything.
Help?
So close, but no cigar.
Still having issues, here's what Ive done so far:
Restored phone completely to stock, leaving only an unlocked bootloader.
Loaded the latest version of TWRP
Re-Rooted the phone
Made a complete backup of the phone, with no partitions left unchecked, in case of a catastrophic failure
Used TWRP to wipe Dalvik/ART, Cache, System, & Data
Loaded the latest CM13 nightly build
Loaded GApps pico version (I don't use many of the Google apps, so I prefer to download the ones that I want)
Wiped Dalvik/ART
Rebooted Phone
At this point, the phone went about its first boot business, loading stuff in the background, optimizing apps for the first use.
I skipped almost all of the first-time setup stuff, no sense in setting it all up if it didn't work this time as well, but connected to WiFi, selected the primary SIM, and activated data on that SIM. This is all normal from my other attempts as well.
Rebooted the phone, when it came back up, I had signal on my phone, and it successfully sent and received messages.
Added my Google account, rebooted again, not getting signal. checked network operator settings, and I get the message stating "Error searching for networks" for both SIM cards.
Removed Google account, changed SElinux settings to permissive, soft reboot, no change.
In the past, I did try wiping Dalvik/ART & cache once this happened, but the only thing that changed is that it caused the process com.android.phone to crash on me repeatedly.
Currently digging around on the net some more to see if maybe there's something that I missed.
Try 1 Sim? Its some bug with dual sim i guess
I will try that when I get a chance, I am currently trying to restore the phone back to stock again after another failed attempt.
Also noteworthy, I had it completely lose the sim cards on me after a restore to the working stock backup that i made earlier in the day yesterday, I had to completely revert to stock (Restore stock recovery, let it rest the phone to stock) then the SIM cards started working again.
This is starting to get rather frustrating.
I'll keep you updated, as I've kinda decided to make this a log of sorts of my experience with this.
Hellspawn119 said:
I will try that when I get a chance, I am currently trying to restore the phone back to stock again after another failed attempt.
Also noteworthy, I had it completely lose the sim cards on me after a restore to the working stock backup that i made earlier in the day yesterday, I had to completely revert to stock (Restore stock recovery, let it rest the phone to stock) then the SIM cards started working again.
This is starting to get rather frustrating.
I'll keep you updated, as I've kinda decided to make this a log of sorts of my experience with this.
Click to expand...
Click to collapse
Did u fixed it? im having the same issue, although i dont have a backup.....
Tried updating to stock marshmallow first before installing CM?
stanley08 said:
Tried updating to stock marshmallow first before installing CM?
Click to expand...
Click to collapse
I tried that, see my thread http://forum.xda-developers.com/honor-5x/help/network-help-t3445510
i dont really know what to do, could the problem be MODEM.img???
Im having the exact same Issue, All roms loose the SIM card so I loose all signal and basically everything... a restart sometimes helps it, tried installing different ROMS, going back to STOCk 5.0.1 or 6.0.1 nothing Helps... NO clue what to do.
Same issue here. Happens on every Rom.
EDIT: Using KIW-L21 (UK)
Unlocked, single sim.
Maybe the it has something to do with modem.img