Database Develop

[Q] No Radio - and "process com.htc.htcdialer isn't responding"

I was running Android Revolution HD 52.0
My phone was unlocked, htc-off and rooted (of course)
Everything was running peachy. until..This morning, I noticed my phone didn't have reception.
I booted into recovery, and cleared cache/davlic - and let it do its thing
The phone rebooted 1/2 way through upgrading apps. then eventually rebooted all the way through.
After a few seconds - I get the "process com.htc.htcdialer isn't responding" wait / close
Waiting just brings it back - so does close - eventually.
I have no service/reception.
If i look in Mobile network settings - APN, Network mode/ network operators is disabled
Under software version - The baseband is "Unknown"
I tried updating radio - no go.
I tried updating to latest firmware 4.19.401.11
I tried updating to latest Android Revolution HD 61.1
When I stick in flight mode - it hangs - and i can't get it out of flight mode.
here's my getvar all output
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My sim card works in another phone, and i've tried a different sim card in my phone same problem
Any ideas?

Respone
wiredliving said:
I was running Android Revolution HD 52.0
My phone was unlocked, htc-off and rooted (of course)
Everything was running peachy. until..This morning, I noticed my phone didn't have reception.
I booted into recovery, and cleared cache/davlic - and let it do its thing
The phone rebooted 1/2 way through upgrading apps. then eventually rebooted all the way through.
After a few seconds - I get the "process com.htc.htcdialer isn't responding" wait / close
Waiting just brings it back - so does close - eventually.
I have no service/reception.
If i look in Mobile network settings - APN, Network mode/ network operators is disabled
Under software version - The baseband is "Unknown"
I tried updating radio - no go.
I tried updating to latest firmware 4.19.401.11
I tried updating to latest Android Revolution HD 61.1
When I stick in flight mode - it hangs - and i can't get it out of flight mode.
here's my getvar all output
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My sim card works in another phone, and i've tried a different sim card in my phone same problem
Any ideas?
Click to expand...
Click to collapse
Did you ever figure this out? I have the exact same problem...

Flash a RUU for ur phone might sort out the problem.

Slim Shady said:
Flash a RUU for ur phone might sort out the problem.
Click to expand...
Click to collapse
I have the exact same problem with my htc one I flashed RUU nothing works I really need help

any solutions / information on this?
wiredliving said:
I was running Android Revolution HD 52.0
My phone was unlocked, htc-off and rooted (of course)
Everything was running peachy. until..This morning, I noticed my phone didn't have reception.
I booted into recovery, and cleared cache/davlic - and let it do its thing
The phone rebooted 1/2 way through upgrading apps. then eventually rebooted all the way through.
After a few seconds - I get the "process com.htc.htcdialer isn't responding" wait / close
Waiting just brings it back - so does close - eventually.
I have no service/reception.
If i look in Mobile network settings - APN, Network mode/ network operators is disabled
Under software version - The baseband is "Unknown"
I tried updating radio - no go.
I tried updating to latest firmware 4.19.401.11
I tried updating to latest Android Revolution HD 61.1
When I stick in flight mode - it hangs - and i can't get it out of flight mode.
here's my getvar all output
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3861mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
My sim card works in another phone, and i've tried a different sim card in my phone same problem
Any ideas?
Click to expand...
Click to collapse
Experiencing the same error and reboot cycle.
Restored to previous backups - same error.
Tried to install latest version of ROM (Viper) - fails.
Can't find a stock recovery to use (UK on Three network via TWRP).
At a dead-end here - can anyone offer any suggestions around what to try next?
Thanks in advance...
---------- Post added at 02:15 PM ---------- Previous post was at 01:41 PM ----------
pettsvaldo said:
Experiencing the same error and reboot cycle.
Restored to previous backups - same error.
Tried to install latest version of ROM (Viper) - fails.
Can't find a stock recovery to use (UK on Three network via TWRP).
At a dead-end here - can anyone offer any suggestions around what to try next?
Thanks in advance...
Click to expand...
Click to collapse
Found this - http://forum.xda-developers.com/showthread.php?t=2758035
Bit confused (and embarrassed) by not finding it before posting.
Anyway, looks like I'm entering the arena of hardware damage, probably around the SIM tray (though looking at it, there's no obvious problem - ie, to the untrained eye!) Before I go down that route, however, could anyone point me in the direction on an appropriate stock recovery. Here's my getvar...
C:\miniadb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH35CW904925
(bootloader) imei: 354436056598731
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3834mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Thanks in advance...

Temporary fix / workaround
Hi guys
I've been struggeling with this for DAYS now where I've tried different solutions like going back to stock RUU, flashing different radios and ROMs.
Today I just flashed Onedroid Beta 21 ROM (get it here http://forum.xda-developers.com/showthread.php?t=2522530) along with baseband 4A.23.3263.28_10.38r.1157.04L
Don't ask me why I choose the specific combo... but it works! I sometimes get the "process com.phone has stopped working" error but it resets in a few seconds and the phone catches reception right away. So I can now do phone calls, send text messages and use 3G/LTE.
The phone still restarts but now it's very rare.
My specs:
OneDroid BETA 21
M7UL
CID: Y_13
S-Off
Unlocked
Rooted

androglezz said:
Hi guys
I've been struggeling with this for DAYS now where I've tried different solutions like going back to stock RUU, flashing different radios and ROMs.
Today I just flashed Onedroid Beta 21 ROM (get it here http://forum.xda-developers.com/showthread.php?t=2522530) along with baseband 4A.23.3263.28_10.38r.1157.04L
Don't ask me why I choose the specific combo... but it works! I sometimes get the "process com.phone has stopped working" error but it resets in a few seconds and the phone catches reception right away. So I can now do phone calls, send text messages and use 3G/LTE.
The phone still restarts but now it's very rare.
My specs:
OneDroid BETA 21
M7UL
CID: Y_13
S-Off
Unlocked
Rooted
Click to expand...
Click to collapse
Hey man, thanks for the tip, just wanted to know where do i get the baseband as you mentioned?

[Q][HELP] Issues after installing custom ROM

Hi everyone, could use some help with my One M7.
EDIT: Okay, i got passed the initial problem! I had to go into recovery and mount /system and everything. I can get into the phone again, however it's continuing to reboot every 2 minutes without warning.
After updating to the stock 4.4.2 my phone became more or less un-usable (no network, constant rebooting, dialer crashing at startup) so I unlocked my phone, installed TWRP and attempted to install a custom 4.3 ROM however it got stuck in a bootloop and corrupted my TWRP.
I can't use TWRP because none of the versions work, they all send me into a bootloop so I'm using ClockWork Mod.
After much frustration I managed to adb push a stock rom onto my phone and install that through CWM. After installing the new ROM i wiped system cache, dalvik cache and wiped all data, all good so far. I rebooted the phone and it started initializing the Android OS and shows me the lock screen. At this point I'm over the moon! However I go to unlock the phone and I'm greeted by the white HTC splash screen. Unfortunately this is as far as I've gotten. The phone just constantly reboots itself every 2 minutes and gets to the same point.
Does anybody know of any workarounds?
Much appreciated, you'll make my week if you can help me.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---------------------------
(bootloader) imei: --------------------------
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4288mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

[Q] USB works in power off, fastboot, recovery but not in OS

When booted into an OS, I can't do anything over USB, i.e. adb, mtp or charging. However I am able to use adb and charge while in recovery (TWRP 2.8.0.2), I can use fastboot and I can charge when the phone is powered off. This leads me to believe it's not a hardware issue. Seems to be ROM independent as well. There are a bunch of other threads similar to this, but no one seems to have found a solution.
I noticed the problem a couple days after I got S-off and Super-CID (i followed these instructions) and flashed the firmware to 6.06.401.1 and ROM to pac_m7-lp-Official-20150504.
I tried to revert so i flashed firmware 3.10.502.2 and ROM aokp_m7att_unofficial_2013-06-27, same problem.
I tried going back to stock with RUU M7_UL_JB43_50_Cingular_3.10.502.2, same problem.
I also tried some battery calibration thing a few times where you hold power, volume up and volume down for 2 minutes, but it never had any effect.
That is where I am now and I have no idea if there's anything I can do. I probably never should have messed around with firmware. Now I just want a phone that charges while turned on again.
In case it helps here is my getvar:
Code:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.19.3263.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.10.502.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3886mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-82f5c3b9b3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Same problem here...any news on how to resolve this?
Thanks.

[Q] HTC ONE (M7) 802w - Help with getting phone to boot?

Hi guys!
Here's the deal. I got a brand new M7 Dual Sim edition from an official reseller's store here in Prague, the Czech Republic (Central Europe). I went home and did the dumbest thing possible. I tried to flash Android Revolution. I had no idea that the M7 and the M7 Dual Sim editions were totally different and that a ROM for one version did not have to be compatible with the other. Such an idiot! So since then (for 2 months now) I've been trying to get the phone back to it's original state with no luck. I can boot into recovery (TWRP or CWM) and bootloader so I have access to fastboot, thankfully. I have tried everything possible hence the reason why I'm writing here and bugging people who have much more important things to do. So let me apologize in advance for wasting everyone's time if this has already been solved once. It's just that every guide I come across explaining anything regarding this phone has impossible prerequisites for a phone that cannot boot into the system normally - like changing the CID, having the phone S-OFF or having an older HBOOT version which I've tried to change several times unsuccessfully.
Here's some info on my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: U3.15.3509.12
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.402.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4158mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
And a screenshot is attached from the Bootloader.

How to disable this "Autonavi" Dialog

This is driving me crazy. This particular HTC M7WLS is popping up this dialog "Allow Autonavi location service to collect anonymous location data ...." every now and then even though I have the location disabled in Settings. I do not want to enable location. How can I get rid of this?
The phone is rooted with S-OFF but bootloader is still locked and the current firmware is still on 4.4.2. Here are more phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 2.03.30.0428
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FXXXXXXXXXXX
(bootloader) imei: 99XXXXXXXXXXXX
(bootloader) meid: 99XXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4126mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks!

tech_girl said:
This is driving me crazy. This particular HTC M7WLS is popping up this dialog "Allow Autonavi location service to collect anonymous location data ...." every now and then even though I have the location disabled in Settings. I do not want to enable location. How can I get rid of this?
The phone is rooted with S-OFF but bootloader is still locked and the current firmware is still on 4.4.2. Here are more phone info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 2.03.30.0428
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FXXXXXXXXXXX
(bootloader) imei: 99XXXXXXXXXXXX
(bootloader) meid: 99XXXXXXXXXXXX
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4126mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks!
Click to expand...
Click to collapse
From my cursory research into Autonavi, it seems like some sort of Chinese bloatware (the company Autonavi was purchased by Alibaba). Did you install any apps just before you started getting the notices? That's definitely not a normal, built-in app.

No...I noticed this right after I put in a sim card. Before that I was installing apps on wifi.

tech_girl said:
No...I noticed this right after I put in a sim card. Before that I was installing apps on wifi.
Click to expand...
Click to collapse
Hmm, I really can't find anything about Autonavi. If you are running a custom ROM, maybe the app was put on there by the developer. If you are just running a stock ROM, then I don't know. Some options:
1. If you are rooted, use an app like Titanium Backup Pro or ROM Toolbox Pro to freeze the app. It may be listed under a system app.
2. Since you are s-off, you could install a different ROM or even run the RUU to get back to complete stock. That should take care of the issue.

coal686 said:
Hmm, I really can't find anything about Autonavi. If you are running a custom ROM, maybe the app was put on there by the developer. If you are just running a stock ROM, then I don't know. Some options:
1. If you are rooted, use an app like Titanium Backup Pro or ROM Toolbox Pro to freeze the app. It may be listed under a system app.
2. Since you are s-off, you could install a different ROM or even run the RUU to get back to complete stock. That should take care of the issue.
Click to expand...
Click to collapse
I couldnt find any process pertaining to this autonavi app. So I decide to factory reset and it seems to have fixed the issue.
Yes I want to install a different ROM especially since stock Sense ROM seems to be draining quite a bit of battery. Im thinking of flashing to LP. But I'm reading up on the different variants of HTC M7, and I have other questions now. But its for another thread.