Hello all, I have read the other forums and this problem remains unanswered.
After installing ANY compatible ROM.. in this case for me it is marvelc roms, when starting up, the touchscreen doesn't work at all, as far as I could tell, for all installations, the volume and lock button works.
Also, I found that after installing modified stock roms, then [advanced] restoring only the "boot" from my recovery, the touchscreen works but at the cost that the WiFi is unoperational.
I hope this helped a few people who wanted to at least get the touchscreen working on CUSTOM STOCK ROMS. Otherwise all the help will be greatly appreciated.
Same Problem with Marvel
I have the same problem with Marvel (GSM Version) Wildfire S.
My device is S-OFF & I'm using CWM Recovery which downloaded directly from ROM Manager.
When installed two different Custom ROMs (ICS) I ended with unresponsive touchscreen.
Currently I'm using the Stock ROM (Glade that I made Backup before flashing Custom ROM).
Maybe this problem is Recovery Version related .
I will try replacing it then reinstall Custom ROM.
If you have progressed with this issue than please post update.
Thanks
Help needed with Unresponsive Touch Screen
As posted before I have the same issue of not responding touch screen with HTC Wildfire S 2012 after flashing Custom ROMs.
Up to now I have done the following:
1. Installed ICS & JB Custom ROMs (one from each) - Flashing passed successfully but touch screen is unresponsive.
2. Replaced my CWM 5.0.2.8 Recovery with TWRP 2.3.3.0 Touch Recovery - Touch Screen not responding under Recovery as well.
3. Reinstalled CWM 5.0.2.8 & installed cm7.2 custom ROM - Touch Screen not responding.
4. Backup of cm7.2 at Recovery mode than I checked the size of boot.img file - file size was the same as at a backup of the original (stock)
ROM which means that the boot.img file was not flashed.
5. At this point I thought that I found the problem so I extracted cm7.2 ROM file & attempt to flash it at ADB but it failed because Bootloader
is locked.
6. Unlocked bootloader then flashed cm7.2 boot.img - Touch screen still not responding.
If I'm going back to stock ROM touch screen works fine.
Can someone please help with this issue ?
I would like to understand if it's a HW or SW issue (seams to me like a SW issue) & how to overcome it.
Related
Hello, i have a big/little problem with TWRP, i have the bootloader unlocked and installed twrp for a few months but kept the stock rom. Today i received a notification abount an update, so i flashed the stock recovery, instaled the update and then flashed TWRP back removed the usb and entered recovery, it shows the screen with instal,backup, etc but it has no response. Tried to flash it again, tried to flash an older version but nothing. The update was from 3.14.401.1 to 3.18.401.1. I installed then CWM and it works but i want the twrp back because my backup is made with twrp,Any ideas? please help
I guess its a problem with the base. Guys who are on the 3.17 base also have this problem with TWRP. afaik it has something to do with the touch driver that is based on the 3.14 base.....
Correct me if I'm wrong
And a TWRP backup can't be restored with CWM. Thats a problem,hope it will be fixed, i would like to know that i can restore my backup when i want. No known alternatives? You are probably right, because the lock button works and no response from the touch
Try this one
http://db.tt/pMxLQp44
Its an older one that needed an update because of the 3.16 base !
It works, thaks a loot. Can i restore my backup with this oine? or the version doesent count if it's still twrp
Should be no problem !
Thanks again
Hello...
I tried to install Android Revolution HD rom. After all phone stuck at Htc screen and doesn't boot.
Here are the info about phone ;
Hboot :1.72.0000
baseband :5.1204.163U2.31
version : 4.17.118.3
cidnum: T-MOB009
What i did? ;
I follewed the instructions, unlocked the bootloader,
flashed latest TWRP but touchscreen didn't work
than flashed latest cwm also touchscreen didn't work
so i flashed philz recovery 5, it worked.
I installed android revolution hd, and than flashed boot.img file with fastboot, but the screen stuck
than i downloaded maximus hd and installed without any problem but still the screen stuck..
I don't know what to do. I didn't do a nandroid backup and i can't open my phone..
I really need your helps so much.
In the philz recovery, did you perform a full wipe BEFORE installing the rom ? If not it's a must otherwise you mess up 2 roms together !
Thanks for your response.. Finally i found what is wrong. I installed a new recovery TWRP v2.7.0.0
So this one worked with touchscreen and i installed Maximus Hd Rom.. Phone booted ...
Many Thanks to '' kantry123 '' who helped me so much in that.
I wish you all the best..
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help
I have been using Cyanogenmod 11 version along with CWM recovery for some time. Recently I installed a theme which crapped on my wifi settings (simple but irritating problem) which I couldn't fix it any which way. Long story short, I tried to install a new boot.img and ended up "soft bricking" my phone. I feel terrible on doing so, since honestly I loved the mods!!
Since the recovery I already had (CWM) wasn't helping me, I tried to flash a new recovery (TWRP) into the phone. After flashing (which worked), when I went to recovery mode, the touch screen nor the volume buttons were working in TWRP. Got frustrated and I tried to flash the old CWM recovery and it keeps giving me this error:
"writing recovery...
<bootloader> Formatting partition SOS done
Failed: <remote:err = 0xa>"
So, Things that are working in my phone are: Fastboot
Things that aren't working in my phone are: adb, not able to flash the recovery with fastboot, boot of course isn't happening..
Ideally I am planning to flash a new recovery and somehow copy a new boot.img and flash the same. Please help. If you feel this problem has already been discussed, you could just pass me on there.
PS: I have already tried solving this by looking at replies from many such forums...
Got it fixed!!
Somehow got PhilZ recovery installed and from then on, it was easy sailing!! I realized that the img should be less than 8MB. Not sure why but it is, what it is. :victory:
hello I'm french I own a HTC Desire 816
I have a problem with my touch screen that works very very badly (he responds poorly).
I do not know if it is a software problem or if I have to change my entire screen
I would like to install a new custom rom or re install the original ROM with the original recovery ..
the problem is that no recovery is working.
TWRP Recovery V2.7.0.1
I can not kick start recovery, when I run it makes me backlight black picture but no recovery
the same for the / ClockWorkMod 6.0.4.7
same with stock recovery
2.8.0.1 TWRP custom recovery this one started but impossible to swipe to unlock.
can you help me