Hello All,
I'm a relative newbie and have an issue with my HTC One (M7UL). I've had the phone about a year and it's unlocked (still with S-ON). I've changed the ROM loads of times but now I've got a problem. I think the problem started recently when I couldn't get the OTA updates with Cyanogen to install. I formatted the phone via TWRP, something I've done loads of times and generally do before installing a new ROM. I've tried to sideload several suitable ROM's (CM11, CM10, ARHD etc.), but they all fail. I've never had a problem before. The most recent failure has caused me give up.
I've taken a screenshot following the most recent failure (attached).
Any help would be greatly apperciated.
Many thanks.
Related
Hello everyone !
I've rooted my SFR Legend, and since i've flashed the 3st rom, i've randomly this message "The process com.android.phone has stopped unexpectedly" and i need to enter my PIN, at this time i've never wiped, and i decided to wipe data/cache/dalvik-cache, flash radio and flash rom and the problem disappeared. But since i installed another rom (now i redo these steps in the same order every flash , wipe, flash radio and flash rom) the problem came back. I think Froyo must solve this problem and i've wait, now froyo is here and i've already the problem. I've tried to format SD and flash, i've tried to unroot but CID incorrect. I've wiped a time with clockworld mod and another time with r4-legend-root.
I need help please i don't find any solution
Edit: SOLVED , Andromax cause the problem
no answers? i didn't found any solutions
since you have the phone rooted, why don't you just install whitesnakedk's Froyo modified Vodafone ROM? I got tired of waiting for HTC to release one so I went ahead and used his and i feel like I just took it in to the shop and got it souped up, I love it! Everything feels like it's working better. So give that a try and see if the phone app keeps failing.
I think is a problem due to the radio update (included in 2.03), i think many files enter in conflicts between residues (if any) of the original radio and the new version. But wipe doesn't fix this
Earlier today i went to flash a newer version of the viper rom. I have done this quite a few times and know the whole process of flashing a rom so i don't feel i am a n00b. So after the rom flashed it was stuck in bootloader and the recovery was gone. I got a recovery back on it and restored what i had saved prior to this. Now i keep getting this error process com.htc.htcdialer isnt responding and the phone does just keeps restarting after about a minute or so. I have looked around quite a bit for a fix but cant seem to come across one and hope someone here can point me in the right direction. And i also noticed it wont seem my sim card either. I did the unlock and was using T-mobile with no probs until i tried to flash that rom....Thanks for any help
I'm having the same issue with my Sprint htc one
Edde3d said:
Earlier today i went to flash a newer version of the viper rom. I have done this quite a few times and know the whole process of flashing a rom so i don't feel i am a n00b. So after the rom flashed it was stuck in bootloader and the recovery was gone. I got a recovery back on it and restored what i had saved prior to this. Now i keep getting this error process com.htc.htcdialer isnt responding and the phone does just keeps restarting after about a minute or so. I have looked around quite a bit for a fix but cant seem to come across one and hope someone here can point me in the right direction. And i also noticed it wont seem my sim card either. I did the unlock and was using T-mobile with no probs until i tried to flash that rom....Thanks for any help
Click to expand...
Click to collapse
I'm currently running ViperOne 5.7.0 I tried updating to 5.8.0 and even 6.0.0. Neither would work. Kept getting the same results as you. And, same as you, I tried looking at a lot of different places for solutions, unfortunately I can't find any.
UPDATE: I found out that the culprit was twrp 2.7.0.0 so I flashed twrp 2.7.0.4b and it allowed me to flash ViperOne 6.0.0
Try flashing the latest radio.
Hi guys,
this is gonna be a long story, but I'm at end of my wits.
So my phone (HTC One M7_UL Vodafone DE) got water damaged (it was submerged in water for at least a minute). I tested it again last weekend and it seemed to work in terms of hardware. I managed to test the speakers, the charge jack, the headphones jack, wifi, gsm, both cameras, etc. it all seems to work fine, and it's not about that anyways. I kept getting a "com.htc.htcdialer" issue, saying the process had unexpectedly crashed and then a few minutes later the phone would reboot. I tried finding out what this error was and how to fix it but I couldnt find anything. Also its weird that I got a software error.
So I unlocked the bootloader (via htcdev.com), flashed the latest recovery (I tried both cwm and twrp), which was also fine. I managed to install the latest Android Revolutions HD (53.0) and thats where the problems started again: I would get to the lock screen but as soon as I would swipe up to unlock it I would the white screen with the HTC letters on it. I tried wiiping all the cache and partitions i could find and reinstalled that rom, but the problem remained the same. Tried a different recovery (twrp) repeated all the steps and still no more luck than before.
So I decided to give a different rom a try and just flashed the latest stable cyanogenmod rom on it, and that boots fine, but eventually without error message reboots as well.
Then I tried flashing the latest viper rom, but there I have the same issue as at the beginning, that I get as far as the lock screen and then it just wont let me unlock it.
And that's where Im at the end of my wits. I cant imagine its a hardware related issue, but i might be wrong.
Ideally I would love to get my hands on a nandroid backup to restore the phone to stock, a stock rom ruu, but I cant find any of those either.
I'd really appreciate your help.
Let me know if you need specific details of installations, versions, decide numbers, etc
OK, I haven't seen this specific problem elsewhere though I've searched a lot, so I hope someone can help me...
I want to restore my intl HTC One M7 to stock Sense. I'm not S-Off because of H-BOOT 1.57 but I've restored it with the Stock Guru Reset ROM. At first everything fine, and the phone completes a minor update with no problems. However, when the update for 4.4.2 comes, the phone cannot start after the update is installed. It boots up, then the screen turns pink for a while. Then the HTC screen with the Beats logo af the bottom comes up, but the colors are distorted - and then the phone stalls. Only option is to flash a new custom recovery and ROM. The phone is the M8 build of Cyanogenmod with no problems whatsoever, so there doesn't seem to be any problems with the phone as such - but, I can't get Sense to work.
The same thing happens every time, no matter which ROM or recovery I'm coming from. Does anyone have any idea what's causing this?
Thanks in advance.
Hey guys, I've encountered a thorny problem on my wife's N910T3, and am running out of ideas about what this could be... so, could really use some help.
Some background: The phone's been working fine for over a year of ownership, mostly on the stock ROM, which gets pretty laggy at times. A few weeks ago I installed a custom ROM (the Acapolypse-X N7 port) to improve performance, and for the past few weeks it's been working perfectly fine on the custom ROM no problem.
Today, when my wife went to check Twitter, the phone crashed and started bootlooping. I had seen a similar issue on my Note 3 before (which turned out to be a specific issue with the kernel I was using), so I figured I would just go into recovery, flash a different kernel or at worst, do a clean install of the ROM.
That's when things started getting weird: The phone would crash while INSIDE recovery during ROM installation (I've never seen a phone crash inside recovery before...) After failing to successfully flash a ROM or, even in cases when it succeeds, fails to boot, I decided to do a full flash back to the latest unmodified stock ROM (since I couldn't find an ODIN-flashable image to download, I used Samsung Kies for this - typically this resolves any kind of left over from previous installations).
On the first attempt, it succeeded - the phone booted into the stock ROM and I was able to start customizing settings. Figuring the issue has been resolved, I went ahead and attempted to root by flashing TWRP through ODIN, and that's when the phone went back to rapidly bootlooping again (it reboots every 2 seconds, I can't even get into recovery when this is occuring). The only way I can return to Recovery is by flashing it again in ODIN (typically this trick will only work once; upon rebooting the phone after that it is prone to start bootlooping again).
Based on the symptoms I suspected the NAND going bad. However, I receive no emmc read/write errors during flashing - all write operations in ODIN results in success and my friend even ran a full storage check via ADB and this phone just doesn't seem to have any bad sectors (I almost wish it were since that would resolve the mystery).
Anyone have any ideas what may be the problem? I have a decent amount of experience installing custom roms on my phones and troubleshooting installation issues, but I've never seen anything like this (crashing/bootlooping directly inside recovery).
I'm sure there are several possibilities that could be software related. However, I've had this issue on a couple of my older phones and it just turned out that the power button was sticking. Just had to pull the phone apart and clean it.
If nothing else seems to work for you, it wouldn't hurt to check this.
PS: I have 4 boys who like to play on the devices with sticky fingers.