HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
dorianshehu said:
HI Guys,
i have a HTC one S which after restore the touch didnt work anymore.
I tried with ROMs and other flash but no success, Also ordered a new display and still the same.
Please help what to check.
Thanks
BR
Click to expand...
Click to collapse
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
es0tericcha0s said:
Was the restore from an older update? If so, this would explain it. HTCs are particular about having the same firmware version needed with the rom update otherwise there will be issues with touch, signal, and a couple other things. I would try and run a full RUU from the PC. This should resolve it, if it is software based.
Click to expand...
Click to collapse
Thanks es0tericcha0s,
i did restore from the same firmware just after doing a factory reset. Because of the big file size of the restore the process stopped in the middle ( the phone was hot in fact ) and after reboot no touch working. Even after changed the screen still the same.
I did a full RUU.exe but no success and now after doing a lot of things on it, the phone does not mount /sdcard when in CWM recovery mode.
I dont know what to try any more first to fix the mount of sdcard and then try something else.
Please advice .
Thanks
BR
That's not good. Sounds like when the phone got hot and failed to restore that something might have happened to the motherboard. I seem to remember that some HTCs of that generation had touchscreen issues due to something shorting out, but can't seem to find the thread anymore. Sorry. Might be time to save for an upgrade. At least something that gets LTE...
Related
Recently I updated my 'non-rooted' HTC Hero (Orange) to 2.73.61.66 from my previous version (2.73.61.5). I got this ROM from the Orange site.
The problem I am facing is that once I restart it and slide down the lock screen, it just shows me the HTC logo. It's very frustrating, however, I can receive phone calls and SMS (for SMS, I can just see the preview in the lock screen). After fiddling around with it a bit, once I move the slider to get in the home screen (which is just the HTC logo), I press HOME button for a while and it brings up my Recent Applications (which is empty). After this if I press the call button, it even gives me access to the dialer screen and I can make calls. But alas, so far I have found no way to get to the main GUI, it keeps on showing only the HTC logo!
So far I re-installed the new and previous firmware a couple of times each, but the problem remains. I have also tried a hard reset and a memory clear and that has also not helped.
Just want to point out here that when I first got the Hero I updated to the .5 version in exactly the same manner and it worked just fine (now when I run the ROM Update Utility and take it back to that same version, I face the same issue).
I will highly appreciate any help in this regard as you can imagine how frustrating this is - I love my Hero!
full wipe, reflash, boot w/o sdcard, logcat...
kendong2 said:
full wipe, reflash, boot w/o sdcard, logcat...
Click to expand...
Click to collapse
Thanks for trying to help kendong2, as I'm pretty desperate here. I would further appreciate it if you could just elaborate on those terms a little more.
I'm not sure what you mean by 'full wipe' and 'logcat'.
Also, my phone is not rooted. I looked up logcat and it seems I need to run ADB for it. I'm a total newbie on this but from what I understood; my phone needs to be rooted to run ADB (would be glad to be corrected here).
consider your users manual and find out how to "restore factory settings". i believe there is a button combination you can press to do this. all your settings will be lost afterwards.
logcat needs adb, although no root AFAIK. but i am not sure if you can use it on a stock rom at all.
kendong2 said:
consider your users manual and find out how to "restore factory settings". i believe there is a button combination you can press to do this. all your settings will be lost afterwards.
logcat needs adb, although no root AFAIK. but i am not sure if you can use it on a stock rom at all.
Click to expand...
Click to collapse
Thanks again. Did the Restore Factory Settings, flashed it and booted without the SD card but still facing the same problem. I'm checking if there is a way to get that logcat somehow.
you flashed it via ruu? or what?
kendong2 said:
you flashed it via ruu? or what?
Click to expand...
Click to collapse
That's right, I used the RUU and it completed successfully (as it has been doing all the times I have flashed it lately), but with the same results. Is there any other way to flash it?
I've also had no luck to get ADB/logcat running either.
you can flash roms through a custom recovery image. but if you don't have any luck by flashing an ruu update the custom recovery probably won't help either. thought about returning the hero for a refund? sounds like a defective device to me...
Returning it would be a major hassle as I live in Kuwait and got it sent to me from the UK through some 3rd party supplier.
I'm also not so sure about the device being defective because when I first did the upgrade to the .5 version (back in Sept 2009, when I got the phone), it worked like a charm. So I'm not sure what went wrong between then and now, when I made the latest .66 update a few days ago.
It's weird, I can make calls, send/receive SMS, but I just can't get to the main home-screen GUI. Keep seeing that HTC logo!
Thanks for trying though.
i'd say try some other roms, but for that you need to install the custom recovery image, and for that you need to create a goldcard and downgrade, so it's kind of a hassle as well... good luck with what ever you go for.
PLEASE.
I have found lots of threads on this topic and nothing is working for me.
-I unlocked bootloader.
-Flashed Android revolution ROM
>WiFi stopped working..A device doesn't even show up to try and select just a blank menu (should be several routers showing)
-I have since tried using CyogenMod menu to do factory wipe/cache wipe then installed a new rom
- I have tried installing JmzStockATTOneDeodex, and RageOneV.1.1.0 after doing factory wipe/cache wipe
- I then found "RUU_Puccini_LTE_Rogers_WWE_1.26.631.4_Radio_1.05.550I.09v2_30.68.550I.12_release_219377_signed"
but this file doesnt seem to open at all it is a exe... and now .......I now am starting to lose my mind
PLEASEEEE HELP!
I am on Rogers LTE Network, HTC One, Canada.
I would really like to be able to flash the RageOne and have wifi work, PLEASE!!!!
millarrjm said:
please.
I have found lots of threads on this topic and nothing is working for me.
-i unlocked bootloader.
-flashed android revolution rom
>wifi stopped working..a device doesn't even show up to try and select just a blank menu (should be several routers showing)
-i have since tried using cyogenmod menu to do factory wipe/cache wipe then installed a new rom
- i have tried installing jmzstockattonedeodex, and rageonev.1.1.0 after doing factory wipe/cache wipe
- i then found "ruu_puccini_lte_rogers_wwe_1.26.631.4_radio_1.05.550i.09v2_30.68.550i.12_release_219377_signed"
but this file doesnt seem to open at all it is a exe... And now .......i now am starting to lose my mind
pleaseeee help!
I am on rogers lte network, htc one, canada.
I would really like to be able to flash the rageone and have wifi work, please!!!!
Click to expand...
Click to collapse
****. Now my ****ing internet wont work either **** me.
Please i need help asap!!! Someone pleaseeeeeeee
i cant believe i even tried this **** with my new device
i just want to go back to factory rogers setting for canada when my wifi and internet would work **** **** **** ****f uck :"(
Calm down. You found the solution yourself. That exe file is the ruu. Relock the bootloader put the phone in fast boot. Then run the program on your computer
gunnyman said:
Calm down. You found the solution yourself. That exe file is the ruu. Relock the bootloader put the phone in fast boot. Then run the program on your computer
Click to expand...
Click to collapse
So it didn't work..Also it said I have version 1.29.631.4 and this is 1.26.631.4 .. wouldn't I want the newer one? I never used a rom exe like this.. only flashed different rom zips from here.. the 3 available.
Also I am not posistive I MIGHT have used a "flash kernal" on one of the rom zips the android revolution one the very first time I installed it...
using "One_M7_All-In-One_Kit_v1.0" that is available here on at&t htc one part of forum. Then I kept reading and flashed it using recovery mode... and the rom worked well everything was fine except wifi... then today I flashed the others like I explained before trying to fix wifi and now the internet won't work as well. but the rest of the phone functions as it should and my carrier network works fine i can txt / call .
I follow your steps and it said this when I ran the exe..
ERROR[132]:SIGNATURE ERROR
The ROM Update Utility cannot update your android phone.
Please get the correct ROM update utility and try again.
--- Sorry this is kind of long, I just want to explain best for anyone reading this including yourself to understand what idiot things I did to bring myself to this conclusion, I am new to the community and a android noob
I have the same problem too,my HTC One wifi keep saying turning on and then error after root, i tried using the wifi tether app but its not working, any one can help please?
I've re-read your OP and you don't have the correct RUU for your device. You have an M7 not a Puccini, anyway like the At&T model a RUU for rogers doesn't exist yet.
As for fixing your wifi, your best hope is to restore your nandroid backup (I hope you made one) or find a Nandroid for your device. I know there's a thread over on the International forums with Nandroids in it, maybe find it there or make a request there.
Hello guys
I tried like everything to fix my HTC One X +. IT was stuck in airplane mode, then i started resetting it and stuff, and a while later, i found myself deleting chache, system, data and internal memory. I know it was stupid, but how do i fix it? I'm not a computer genious, but I tried so many guides on here and none of the seem to work.
Can someone please help me out here? I can give additional info if needed.
Thank you very much
Die you try to push a Rom into your phone via ADB sideload?
jizang said:
Die you try to push a Rom into your phone via ADB sideload?
Click to expand...
Click to collapse
Yes, but I'm having trouble finding a rom that will work, the roms i've tried so far didn't work out for me, chameleon, insertcoin,...
buudeluu said:
Yes, but I'm having trouble finding a rom that will work, the roms i've tried so far didn't work out for me, chameleon, insertcoin,...
Click to expand...
Click to collapse
Is your phone AT&T/Telus or International?
Kujo-ou812a said:
Is your phone AT&T/Telus or International?
Click to expand...
Click to collapse
It"s international, my CID is E11 if that helps. And btw, i keep getting this 'MD5 files missing' error i can't seem to resolve.
buudeluu said:
It"s international, my CID is E11 if that helps. And btw, i keep getting this 'MD5 files missing' error i can't seem to resolve.
Click to expand...
Click to collapse
Also, I don't know if my phone is rooted or not, since i can't check it in any way because i don't have a OS instaled. Please someone help me out, I'm feeling pretty lost out here.
I have had a similar issue with my HOX+ in the past, I wiped a little too much and had trouble getting any ROM to work.
After having tried a lot of ROMs without success, I tried flashing MIUI, and somehow this worked. After I had flashed MIUI, and ran it for a while, I could switch back to other ROMs without problems.
I don't know what exactly caused and resolved the issue, but somehow it worked, so you may wanna give that a try. Make sure you also always flash the right kernel for the ROM you are flashing.
Before doing any of this, though, I recommend checking if your recovery is up to date. If it is not, or if you are unsure, you should flash Lloir's latest CWM, which prevents you from wiping too much too easily.
Hello,
I have an old HTC Hero (GSM) with a very old VillainROM on it, I haven't touched the phone for years. I now wanted to update with this ICS ROM (or potentially another one), however, I was unsure where to start, e.g. update my bootloader or whatever.
I tried copying the linked ROMs zipfile to the SD card, booting into my loader, wipe everything, and then "Install from zip". However, that fails while verifying the zip package.
I then also tried the newest official CM7 nightly for the hero, and that didn't produce above verify error.
Should I update my bootloader or something, or is just the ROM I tried broken? (for other people in that thread it seems to work).
What recovery do you use (CWM, AmonRA)?
Maybe you should try a newer one from here:
http://forum.xda-developers.com/showthread.php?t=1797626
derproblembaer said:
What recovery do you use (CWM, AmonRA)?
Maybe you should try a newer one from here:
http://forum.xda-developers.com/showthread.php?t=1797626
Click to expand...
Click to collapse
@derproblembaer Thanks for getting back to me! Just to close this, the phone wasn't really usable anymore, the touch was not working or acting weird on half the screen.
Elador said:
@derproblembaer Thanks for getting back to me! Just to close this, the phone wasn't really usable anymore, the touch was not working or acting weird on half the screen.
Click to expand...
Click to collapse
Yes exactly, why in the world does this happen? My friends HTC hero also, most of the times the bottom half of the phone does not work (touch). Thought a ROM problem so Flashed different ROM's and still the problem remains. He bought a new phone but he still has it, we could still try and see if we can do anything about that phone.
What can we use it for?
driverless said:
Yes exactly, why in the world does this happen? My friends HTC hero also, most of the times the bottom half of the phone does not work (touch). Thought a ROM problem so Flashed different ROM's and still the problem remains. He bought a new phone but he still has it, we could still try and see if we can do anything about that phone.
What can we use it for?
Click to expand...
Click to collapse
That's interesting! I assumed it was because I haven't been cleaning the screen for years and it was sticky etc., and even after proper cleaning it didn't work anymore. So I thought it was me and I should've taken more care And also, I mean it's really old.
However, maybe it's a Hero problem after all. And after thinking about it, it's not that old - it's from summer 2009 which makes is 5 years old. Hmm.
I had the same problem few years ago... two times with the same phone.
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
TwinShadow said:
Currently, I'm using TWRP 3.2.1-0 and I managed to get it to flash a ROM only once so far. I've already done some searching on what this error means which apparently just says that it fails checking for the proper make/model of the device so that it won't flash something its not suppose to. Except, I have a ROM for the device...
When I first flashed, I had no choice but to do a factory reset which is really a given anyway. But now... its another story. Trying to flash a an updated LineageOS ROM for instance to the latest nightly for instance, will always result in an Error 7. I don't really want to do a factory reset again if I can help it though, even though I do have two points of backup just in case... Not sure if anyone else is having issues about this or not, but figured I'd point it out for now.
Click to expand...
Click to collapse
Downgrade to twrp 3.1.1-0 and try again...
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
TwinShadow said:
No dice. Actually this was the second time I tried doing it like that. Doesn't matter which recovery I use be it 3.1.1, or 3.2.1. Both results in the same error regardless. Its like TWRP downgraded after it hit v3 because never once had I ever encountered a problem when I used it back on 2.8.7 (or 2.8.6, I can't recall back when Moto X (ghost) was my main device).
Click to expand...
Click to collapse
What is your exact model - what's written on the box and what is the model shown in Settings on your stock firmware (if you remember).
I have a sneaking suspicion that it may not be the exactly same device as ours - E5823, creating a conflict somewhere between Firmware/Recovery. Generally, it should get the device data from prop files but you never know I guess...
Here is what you can try: Install latest firmware for E5823 from XperiFirm in Flashtool and wipe everything. If you don't wipe old files are still going to stay! Also, make a backup of all your stuff so you don't lose it. There are guides how to do it here and what things to not wipe in any case.
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
The last 2 nightlys don't work properly!! I have clean installed, wiped everything and gone back to stock and tried and tried again and again!! 20180318 is the one that is true!! Try flashing that build!!
TwinShadow said:
The device model is indeed a E5823. This has been reported as such in the official firmware as well.
Currently I don't have any of the official firmware files, and I would like to avoid having to set up my phone again if I can help it; even with a nandroid of my current install handy... Its simply just a pain to get all that done.
Click to expand...
Click to collapse
The thing is some partitions get updated only in that way - like baseband for example. Ensuring everything is the latest version and on a clean slate will remove the chance of weird bugs that nobody knows about or can help you with.
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
TwinShadow said:
Well, here's the irony. I reflashed your TWRP again, twice for that matter.. (I've had random cases where fastboot won't flash it the first time even though it said it did) and all of a sudden it started working. Android never ceases to amaze me when things want to work, and when things don't...
Click to expand...
Click to collapse
Lol. I have never had that :d and that is from years and years of use and multiple Sony devices...
My guess is a bad flash. That happens rly rarely but maybe u have a bad PC or cable that makes an unreliable connection...
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
TwinShadow said:
Same thing happened on my old Moto X (2013) on my last system and the new tower I built. For some reason its something to do with fastboot for me, I really don't know. Either that, or its just Windows trying to fight me every which way it possibly can before something wants to work. Its a daily thing I have to deal with, no idea why. Must be my disdain for Windows perhaps..
Click to expand...
Click to collapse
You might wanna ensure you have the latest fastboot drivers installed under 'Disable driver verification' mode.