[Q] Help, cannot update Sense after restoring to stock - One (M7) Q&A, Help & Troubleshooting

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.

Related

No Signal or No Touch

I'm pretty desperate right now as I'm trying to fix my phone for like 24 hours straight and searched the whole ****ing internet for a solution and my eyes are popping out any moment. My situation:
I have a HTC One from Vodafone Germany with LTE.
I rooted it with the HTCdev.com method described in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2292729
After that I put CM10.2(Android 4.3) on my phone and for the first two days it worked quite ok but since two or three days I get no signal at all. The APN settings are definitely correct. Then I decided I try to go back to stock and that's where the next problem pops up. It seems that I can't go back to stock because when I do my phone wont react to any touches at all. It seems this is a common problem when going back from 4.3 to a lower version (as the nandroid backup of vodafone stock is 4.2.2 or 4.1.2). Because I used the method mentioned above I'm stuck with HBoot 1.54 and S-On so I can't do anything about that touch problem it seems and on 4.3 I don't get any signal at all (WiFi working, just saying). Even tried Pac-Man Rom, still no signal at all. Can someone help me in any way? No one can call me or text me for two to three days now and this is a really bad situation!
Hope I did not miss anything!
anstaendig said:
I'm pretty desperate right now as I'm trying to fix my phone for like 24 hours straight and searched the whole ****ing internet for a solution and my eyes are popping out any moment. My situation:
I have a HTC One from Vodafone Germany with LTE.
I rooted it with the HTCdev.com method described in this tutorial:
http://forum.xda-developers.com/showthread.php?t=2292729
After that I put CM10.2(Android 4.3) on my phone and for the first two days it worked quite ok but since two or three days I get no signal at all. The APN settings are definitely correct. Then I decided I try to go back to stock and that's where the next problem pops up. It seems that I can't go back to stock because when I do my phone wont react to any touches at all. It seems this is a common problem when going back from 4.3 to a lower version (as the nandroid backup of vodafone stock is 4.2.2 or 4.1.2). Because I used the method mentioned above I'm stuck with HBoot 1.54 and S-On so I can't do anything about that touch problem it seems and on 4.3 I don't get any signal at all (WiFi working, just saying). Even tried Pac-Man Rom, still no signal at all. Can someone help me in any way? No one can call me or text me for two to three days now and this is a really bad situation!
Hope I did not miss anything!
Click to expand...
Click to collapse
have you tried to flash a stock RUU? http://forum.xda-developers.com/showthread.php?p=39588860
As I already mentioned... Yes I did and then the display wont recognize any touch input
Have you tried flashing the TWRP for the newer drivers and seeing if it responds?
Sent from my Nexus 10 using Tapatalk 4
It's not the recovery where the touch is not working. Recovery is working fine. As soon as i flash the stock rom and boot, i cannot type in my pin, because it wont react to touch.
anstaendig said:
It's not the recovery where the touch is not working. Recovery is working fine. As soon as i flash the stock rom and boot, i cannot type in my pin, because it wont react to touch.
Click to expand...
Click to collapse
Wut. But have you tried an RUU: a total factory reset of everything?

[Q] Various Issues - Tried different ROMs but issues remain

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

[Q] Sprint M7--Stuck on HTC logo after Sense 6 update

Greetings.
I recently attempted to install Sprint's OTA update for the stock ROM on my phone. However, I had TWRP installed, so the update could not complete. I installed the stock recovery, but the update failed, stating that it could not find one of the .apk files. After that, the phone boots to the lock screen, but displays nothing but a green HTC logo on a white screen when I try to unlock the phone, repeatedly displaying "Unfortunately, Qualcomm Enhanced Location Services has stopped." After about 2 minutes on this screen, the phone reboots, with no user input.
I have no usable Nandroid backup (lost the password), and don't know what to do to make my phone usable again.
Any help you can provide would be greatly appreciated.
P.S. One other peculiarity I noticed, when researching my issue, is that "fastboot getvar version-main" does not return a value. This doesn't seem normal to me. Could something have gone wrong with a firmware update as part of the OTA?
FlynnLives said:
Greetings.
I recently attempted to install Sprint's OTA update for the stock ROM on my phone. However, I had TWRP installed, so the update could not complete. I installed the stock recovery, but the update failed, stating that it could not find one of the .apk files. After that, the phone boots to the lock screen, but displays nothing but a green HTC logo on a white screen when I try to unlock the phone, repeatedly displaying "Unfortunately, Qualcomm Enhanced Location Services has stopped." After about 2 minutes on this screen, the phone reboots, with no user input.
I have no usable Nandroid backup (lost the password), and don't know what to do to make my phone usable again.
Any help you can provide would be greatly appreciated.
P.S. One other peculiarity I noticed, when researching my issue, is that "fastboot getvar version-main" does not return a value. This doesn't seem normal to me. Could something have gone wrong with a firmware update as part of the OTA?
Click to expand...
Click to collapse
I'd say download a custom rom for temporary use like cm or pa and find the stock sense 6 rom for your phone and flash when you find it.
sent from a stock AT&T Galaxy S III LTE
Jakeuten said:
I'd say download a custom rom for temporary use like cm or pa and find the stock sense 6 rom for your phone and flash when you find it.
sent from a stock AT&T Galaxy S III LTE
Click to expand...
Click to collapse
I just downloaded and installed CyanogenMod, but now the baseband version and IMEI are both "unknown", so I can't connect to the cell network. fastboot getvar all still shows the proper IMEI, however.
I was able to find a Sense 6 ROM and flash it, and that worked. Thanks.

[Q] Sprint HTC One not booting past lockscreen. Is it totally irreparable?

I have a Sprint HTC One which is having serious issues. It will boot to the lockscreen but when I unlock the screen all it shows is the HTC logo on white background, then a little while later it will reboot. I have done an RUU flash yet it is still the same. I have flashed the stock 5.05.651.2 ROM yet the phone remains in the same condition. Please can anyone help?
Thanks in advance for any help.
OK. There's some improvement. I flashed CM11 Nightly with GAPPS and it booted. However it says Baseband Unknown and restarts randomly. I have flashed 1.01.20.0904_2_5.05.651.2_radio.zip from TWRP recovery but still same issue. Can anyone help here please, maybe some other way I can flash the radio? Perhaps the baseband has been the issue all along. I really need help with this; at my wit's end...
Thanks all.
Update: I ran the new 5.0.2 RUU and it boots fine and phone works ok, but still no baseband/IMEI/MEID. I have flashed a radio in recovery but still same issue; no baseband/IMEI/MEID. Any help? Anyone?

[Q] Rom Load but is basically unusable then it reboots.

Hi Guys. I have searched the forum but havent found anything that applies to my problem. I have the HTC One M7 sprint version. I have been trying to sim unlock it but the phone came on an android version higher than 4.3. This is one of a batch of 4 so at this point I cant even remember the original os. My problem is that I need to be on an android os lower than 4.3 to unlock. I have been following the tutorial here: http://forum.xda-developers.com/showthread.php?t=2586704 .Only roms at kitkat or higher are stable enough to use and not even all the kitkat ones are stable.
The issue:
The phone boots and the rom loads but I am unable to do anything with it. The lockscreen shows as normal but anytime I unlock the screen I get a white screen with HTC in green letters. On some roms I am able to access the settings menu but that is it. It just stays like that forever. On some roms it will stay on but most reboot in roughly 2-3 minutes. Most of the roms that are stable go into a handsfree activation loop where I cant get past that screen. I read a tutorial about deleting the htc setup apk but that works only some of the time and then the roms are mostly unstable.
My phone is S-Off and I have attempted to downgrade to stock 4.1.2 using the official ruu.. The process was successful but the stock os is unstable. Reboots every 2-3 minutes. I have flashed the firmware separately and then run the ruu. I have run the ruu on its own. I have done factory reset with both stock and custom recoveries after running the ruu.
I have tried pretty much every sprint rom I have come across and still no love. I've been at this for nearly a month and my HTC Rom folder is about 25gb if a list is needed I am willing to provide it but I really just want to be on stock 4.1.2 or a sense rom lower than 4.3 for the purpose of unlocking the gsm sim. I have been told that the issue could be hardware but then I have roms that run without issues except that the phone isnt unlockable in that state.

Categories

Resources