Database Info

[Q] Phone screen unresponsive after flashing cm10

Hi guys. I have just recently bought this phone. This is my first HTC phone, ive always used samsung phones and wanted to try out the HTC. I managed to unlock the bootloader, root the phone and install twrp. My phone was bone stock so I downloaded the latest nightly for CM10 and gapps. Now for samsungs i didnt have to extract the boot.img and flash that via fastboot. so thinking the flashing process would be the same i flashed cm10, gapps and rebooted. And like clockwork the phone went into a boot loop. I found this little blurb in this thread http://forum.xda-developers.com/showthread.php?t=1957193
"5) Once your phone is in bootloader mode, type the following command fastboot flash boot boot.img ( If command prompt is closed then open command prompt in the folder where boot.img, adb, fastboot are present . For example: C:\android-sdk\platform-tools - Same folder used in step 3)
5) Then run the following command adb reboot recovery
6) Your phone is in TWRP recovery
7) Select mount from recovery ( See mount - image in the attachments for example)
8) Copy the ROM.zip which you downloaded earlier to the SD card ( For example cm-10-20121012-NIGHTLY-evita.zip) ( Not the extracted folder but the actual zip file which you downloaded)
4) Copy the gapps into sd card ( you need to download gapps if you using CM10 or ASOP roms )
5) Unmount, then select Wipe and select Factory reset ( it is recommended to do a factory reset before flashing the new ROM. ) (See wipe, wipe1 images below )
6) Select Install in recovery and flash the ROM.zip
7) You need flash gapps if you flashing CM10 or ASOP ROMS
so i re did the process. flashed boot img through fastboot, rebooted to recovery, flashed the rom that was already on the sd card, flashed the gapps package and rebooted phone. and i did do a factory reset when installing the rom. the phone rebooted, but this is where im stuck. the phone boots to the setup screen where you basically select the language. SCREEN is unresponsive, its not letting me click on start, its not registering my touch anywhere on the screen. I was thinking maybe it was the kernel so i made sure i was using the right kernel. i tried the whole process a few times but it didnt work. same problem. fone boots but doesnt register the touch. i even tried booting with flashing the gapps. so basically im stuck at the first screen. i had done a nandroid back up before and tried flashing that but that doesnt work either i guess because of the same reason.
Any help would be appreciated?
Thank you so much in advance

what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.

codeprimate said:
There is an issue with the 2.14 hboot
Click to expand...
Click to collapse
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.

twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
So in your opinion what is the solution i can try? Im not able to boot my phone so i cant really transfer any ROM zips to my phone. I have to use the bootloader or recovery to somehow get my phone back into workin order and then go from there. Thank you for your response

codeprimate said:
what hboot version do you have? There is an issue with the 2.14 hboot as HTC modified the firmware so the touchscreen drivers don't work for the older ICS or AOSP roms. If you have the 2.14 hboot, you'll need a JB sense ROM (like jokers or viperXL 3.1, or maybe Newts), check the forums themselves to see if they are compatible with the 2.14 hboot if you have it.\
If you don't have the newest hboot, maybe check the md5sum of the one you downloaded in case it is corrupted? If not try reflashing it, or flashing a different ROM and report back with results.
Good luck.
Click to expand...
Click to collapse
So i checked in the bootloader screen and i do have 2.14 hboot. so as the other person said i can downgrade my hboot using JET? and If im not mistaken you said that 2.14 may not be the latest hboot. If not where can i get the latest hboot. The other thing was since im not able to transfer any files to the phone.

Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense

marijuana king said:
Like twisted said you're going to have to flash a sense jb Rom right now go try viper.... Until the others update touch drivers to accommodate you people you have to use jb sense
Click to expand...
Click to collapse
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.

anandsamuel said:
ok so i downloaded jokers rom, and i was reading this link http://forum.xda-developers.com/showpost.php?p=32794132&postcount=7 to put the rom on my sd card. this link says they are using cwm recovery but i have read in many places that twrp should be used because it is officially supported for our devices. when i boot into recovery and try mount usb storage it doesnt show up on my computer as a flash drive. i have checked the drivers. im going to uninstall them and reinstall them, reboot my lappy and see if it recognizes the device. if you have any suggestions please throw them at me. at this time im looking for any straw that i can get to keep afloat.
Click to expand...
Click to collapse
you should be able to flash that from TWRP instead of CWM without any dramas. if you can't see the device from your pc while it is booted into TWRP you can use "adb push C:\somepath\somefile /sdcard" to copy it onto your sdcard (you'll need the right version of the drivers and adb in your path). If you can't find the drivers or figure out anything let us know.
twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
You are right, it isn't the bootloader, it was the firmware upgrade pushed out alongside it, but it is a lot easier to check your hboot version from the bootloader than it is to check what software/firmware version you have, as the OP didn't list his software version, and had since blown it away with a new ROM, it seemed easier to check the firmware compatibility via the hboot version. I know strictly speaking the hboot isn't responsible for the touchscreen drivers, but they got the point quite quickly.

Update: so I was able to get my phone working I had to reinstall drivers on my computer restart the computer and then I was able to actually view my phone on my computer through TWRP and I transferred the ROM on to my phone and rebooted back into the bootloader flashed via boot image then went back to recovery and flash the ROM and everything is good to go now thank you all for your help this is an amazing phone
Sent from my HTC One XL using xda app-developers app

twistedddx said:
I hate that people are so hell bent on that this is a "2.14 hboot" issue.
2.14 hboot was just one of the many firmware updates pushed with 3.17 ROM's. I have not seen any knowledged person yet claim that the issue is actually in 2.14 hboot.
I believe if you revert your hboot with JET to 1.09 which you can do, the Touchscreen still does not work with incompatible kernels.
Which to me makes it pretty clear the issue is not in the hboot update at all but instead in one of the other updates.
Click to expand...
Click to collapse
Because it's the easiest way to identify that they are running the new firmware?

Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app

h8rift said:
Yes. HTC went off and made some firmware updates to the touchscreen firmware.
We can't do anything about it until kernel source for the jellybean update is released.
Basically, if you took the new hboot EVER(since it updates the touchscreen firmware), that means you cant use AOSP Roms until we get source and can fix it in CM.
Aokp, pa, jellybam, kingkang, etc. All of those Roms use our kernel and device trees as a base. Once we get source and fix, they will update and everyone will be back in business.
The guys at TWRP were able to make recovery work because they just used the prebuilt stock kernel. On AOSP...we need source.
Sorry guys. Pester and scream at HTC to release JB source and that is the only way to help with this. Sorry to all of those that are affected....just know we are waiting impatiently as you are.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
lol, I've tried arguing with HTC's "support" for the source code, they are either extremely thick or deliberately obtuse. They kept telling me how to check if my carrier has released jellybean. I kept telling them that they are required under the GPL to release the source for the kernel along with any binaries.
I think the only way they'll release them in a timely fashion is if we get organised in a class action suit for violation of the GPL. It is for HTC's point blank refusal to meet it's legal requirement in a timely fashion that I refuse to ever buy another HTC device. I'll use this one for the term of my contract and then jump ship to a manufacturer that doesn't treat the open source community with contempt.

I don't mean to hijack this thread, but I'm facing a related issue.
I had rooted and unlocked my bootloader, hadn't yet installed any custom ROM. So today, without thinking, I install the OTA 4.1.1 update. Now of course I lost root, but even worse, when I boot in TWRP, my touchscreen is also unresponsive. I have the hboot 2.14.
I tried flashing TWRP again, but the same deal happens: the touchscreen won't register anything.
When you said that TWRP were able to make the recovery work, was this after the recent firmware update? Do I need a more recent version of TWRP (I'm using 2.3.3.1)?
I asked about this in the TWRP thread, but this seems closely related so I posted again here.
Edit- All is well, goo manager was installing 2.3.3.0 for some reason.

Flashing roms results in constant fail

Ive have this phone for a while now and although ive run into a failed zip file before it has never been this consistent. im s-off, and ruu to 3.18 in case anyone is wondering. as of lately, flashing any rom is resulting in a fail error 7 from twrp. i thought maybe it was because im using twrp 2.3.1.0 so i tried updating it and it is still happening. it has nothing to do with having md5 or signature verification checked/unchecked. tried it both ways. im starting to wonder if my zip card is corrupted, although the roms that i had downloaded before this started happening all still work correctly. any that i download now, do not flash at all. anyone know wth is going on ?

dalvarez0312 said:
Ive have this phone for a while now and although ive run into a failed zip file before it has never been this consistent. im s-off, and ruu to 3.18 in case anyone is wondering. as of lately, flashing any rom is resulting in a fail error 7 from twrp. i thought maybe it was because im using twrp 2.3.1.0 so i tried updating it and it is still happening. it has nothing to do with having md5 or signature verification checked/unchecked. tried it both ways. im starting to wonder if my zip card is corrupted, although the roms that i had downloaded before this started happening all still work correctly. any that i download now, do not flash at all. anyone know wth is going on ?
Click to expand...
Click to collapse
I just happened to be updating a guide and noticed this post.
download twrp 2.3.3.1 Check the file md5
Fastboot flash recovery recoveryfilename.img
fastboot erase cache
reboot to recovery
Download rom, check md5.
Flash rom (leave both md5 and sig verif unchecked)
You can format the SD card before doing all this if you like. Typically a corrupt SD card won't mount/work at all.

exad said:
I just happened to be updating a guide and noticed this post.
download twrp 2.3.3.1 Check the file md5
Fastboot flash recovery recoveryfilename.img
fastboot erase cache
reboot to recovery
Download rom, check md5.
Flash rom (leave both md5 and sig verif unchecked)
You can format the SD card before doing all this if you like. Typically a corrupt SD card won't mount/work at all.
Click to expand...
Click to collapse
with any version of twrp besides 2.3.1.0, the sd will not mount via recovery but will still mount when i turn on the phone and mount it.
tried 2.3.3.1 again just now, still no dice. checked md5, nope still not flashing even though md5 checked out fine. im leaning towards a corrupt sd card, even though it mounts fine through 2.3.1.0 twrp and through android. it cant be a coincidence that not a single rom im downloading will flash, not pacman, not latest cm nightly, not carbon rom. even though a week ago eveything flashed fine, and all the roms i had previously downloaded still flash fine. ill format sd card just to make sure but if you have any other ideas pls lmk.

dalvarez0312 said:
with any version of twrp besides 2.3.1.0, the sd will not mount via recovery but will still mount when i turn on the phone and mount it.
tried 2.3.3.1 again just now, still no dice. checked md5, nope still not flashing even though md5 checked out fine. im leaning towards a corrupt sd card, even though it mounts fine through 2.3.1.0 twrp and through android. it cant be a coincidence that not a single rom im downloading will flash, not pacman, not latest cm nightly, not carbon rom. even though a week ago eveything flashed fine, and all the roms i had previously downloaded still flash fine. ill format sd card just to make sure but if you have any other ideas pls lmk.
Click to expand...
Click to collapse
http://forums.team-nocturnal.com/fo...ountable-internal-storage-on-the-htc-one-x-xl

exad said:
http://forums.team-nocturnal.com/fo...ountable-internal-storage-on-the-htc-one-x-xl
Click to expand...
Click to collapse
i did that, the latest nightly still wont flash. i downloaded several roms to serve as control for my little flashing experiment and heres what i found:
aokp flashes fine
slimbean flashes fine
latest cm nightly fails
latest pacman nightly fails
latest carbon rom nightly fails
carbon rom 1.7 (6/10 release) flashes perfectly
so...the only common factor i see here is that only the latest nightlys will fail to flash.

exad said:
http://forums.team-nocturnal.com/fo...ountable-internal-storage-on-the-htc-one-x-xl
Click to expand...
Click to collapse
dalvarez0312 said:
i did that, the latest nightly still wont flash. i downloaded several roms to serve as control for my little flashing experiment and heres what i found:
aokp flashes fine
slimbean flashes fine
latest cm nightly fails
latest pacman nightly fails
latest carbon rom nightly fails
carbon rom 1.7 (6/10 release) flashes perfectly
so...the only common factor i see here is that only the latest nightlys will fail to flash.
Click to expand...
Click to collapse
problem was solved by redoing the 3.18 ruu, not sure if it was the ruu or the fact that this time i didnt downgrade touchpanel firmware. either way it worked, for anyone that experiences a similar problem. mods you can change this to solved. thanks.

dalvarez0312 said:
problem was solved by redoing the 3.18 ruu, not sure if it was the ruu or the fact that this time i didnt downgrade touchpanel firmware. either way it worked, for anyone that experiences a similar problem. mods you can change this to solved. thanks.
Click to expand...
Click to collapse
Touchpanel firmware would only make the touchscreen not work. Roms would still flash and boot just fine. I know from experience.

flash of nightly Carbon Rom fails using TWRP zip install
Flash of Carbon KK nightly d2lte ROM fails on VZW (SCH-535) Samsung III using TWRP zip install function. I have tried two nightlies (July 4 and July 13) Any suggestions? Does CWM have a better success at processing the zip file contents? I have been using Carbon R 1.8. Is that the last stable release under Android JB 4.2.2 for VZW Galaxy S3?

paul1701 said:
Flash of Carbon KK nightly d2lte ROM fails on VZW (SCH-535) Samsung III using TWRP zip install function. I have tried two nightlies (July 4 and July 13) Any suggestions? Does CWM have a better success at processing the zip file contents? I have been using Carbon R 1.8. Is that the last stable release under Android JB 4.2.2 for VZW Galaxy S3?
Click to expand...
Click to collapse
You're in the wrong forum, you need to ask in your own device forum, that way people that actually have your device can assist you properly.
Sent from my Evita

wrong forum?
Thank you - I know this may be wrong forum but as I am not an active participant I cannot post to developer forums - quite annoying
timmaaa said:
You're in the wrong forum, you need to ask in your own device forum, that way people that actually have your device can assist you properly.
Sent from my Evita
Click to expand...
Click to collapse
---------- Post added at 10:31 AM ---------- Previous post was at 10:12 AM ----------
I reposted to the vzw samsung S3 general forum - thank you
paul1701 said:
Thank you - I know this may be wrong forum but as I am not an active participant I cannot post to developer forums - quite annoying
Click to expand...
Click to collapse

[Q] Unresponsive touchscreen after CM flash

Gentlemen and ladies, firstly I would like to apologize if this is a repost. I did scour the internets as well as ran some searches on xda to locate anything similar to my prediciment and found nothing.
THE ISSUE:
Specs:
HTC ONE X Evita
HBOOT - 2.14.0000
Rooted
SuperCID
Bootloader Unlocked
S-off
I unlocked bootloader, rooted, established s-off and then decided to try and flash CM10 using TWRP. Everything looked awesome until I got to the welcome page to initialize setup and to my dismay I noticed that my touchscreen does not function. I have downloaded the package at http://forum.xda-developers.com/showthread.php?t=2159863
and seeing as how I cannot enable USB debugging I mounted my USB storage via TWRP to my computer and threw the .zip on the phone. I then tried to use TWRP to install the package however it failed out:
Finished running boot script.
Installing '/sdcard/Download/downgrade_tp.zip' ...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/Download/downgrade_tp.zip'
Updating partition details...
I have reached a standstill and no longer have any ideas as to resolve this issue. Thank you for your time and consideration in this matter.

You can't flash the touchscreen downgrade through recovery, it must be flashed via fastboot, it states that clearly in the instructions. Anyway, you've flashed quite an old build of cm10 (it's Android 4.1), the current nightlies don't require you to downgrade your ts firmware so I would suggest flashing one of those instead. You can find cm10.1 and cm10.2 threads in our Original Android Development section here. Just flash one of those through recovery and you'll have no problems, plus you'll be on a more recent version of Android (4.2/4.3).
In future, don't deviate from the instructions you're given in a thread, that can lead to bricking your phone. Trying things that you don't really know about is a really bad idea.
Sent from my Evita

timmaaa said:
You can't flash the touchscreen downgrade through recovery, it must be flashed via fastboot, it states that clearly in the instructions. Anyway, you've flashed quite an old build of cm10 (it's Android 4.1), the current nightlies don't require you to downgrade your ts firmware so I would suggest flashing one of those instead. You can find cm10.1 and cm10.2 threads in our Original Android Development section here. Just flash one of those through recovery and you'll have no problems, plus you'll be on a more recent version of Android (4.2/4.3).
In future, don't deviate from the instructions you're given in a thread, that can lead to bricking your phone. Trying things that you don't really know about is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
Ok, as soon as I get an unsecured internet connection I'll give that a shot. I'll post updates as progress is made. Thank you Timmaaa, I appreciate it.

No problems.
Sent from my Evita

[Q] Bricked?

I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!

qabi said:
I unlocked and installed the CWM recovery. The ROM manager confirmed this was installed.
Following the guide at teamadroid.com for the twistedkat 4.4.2 ROM.
I flashed a new boot.img (from the twistedkat ROM).
Now I just see the "Only for internal use" red letters, and cannot invoke the CWM recovery for installing the ROM.
Any help would be appreciated on how to install the ROM or get back to stock.
EDIT: I progressed from this situation by re-flashing the CWM recovery, even though this emitted an error indicating that the file could not be validated or such. After this I can enter the CWM recovery.
Thanks!
Click to expand...
Click to collapse
Do you have Ville (S4) or Ville C2 (S3) model?
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery --> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/ville/philz_touch_6.19.3-ville.zip
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
PLS check if you have S3 or S4

LS.xD said:
The recovery provided by rom manager does NOT support Android 4.4.2 KItKat roms !!!
Click to expand...
Click to collapse
Thanks for your suggestion.
Actually I don't know. I think only one HTC One S was ever in my market (Denmark).
In the meantime I succeeded installing the TwistedKat ROM and have it running now.
Does anybody know of a tutorial for resetting to stock ROM? (Just in case I want to revert).
-qabi

Unable to enter clockwork recovery?
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!

qabi said:
I installed clockwork recovery and actually managed to install TwistedKat (what seems to be an old version).
But I am unable to enter the clockwork recovery in order to reflash to another ROM. Choosing RECOVERY from HBOOT just shows the warning screen and then halts the phone.
I have been reding through a ton of threads mentioning similar symptoms, but with no solution found.
Any help would really be appreciated!
Click to expand...
Click to collapse
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???

808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
Which recovery do you use? Are you S-OFF // SuperCID // HBOOT 2.15??

808phone said:
I get this as well. Try it twice. For me the second time always boots up into CWM.
Can you tell me what you did to get rid of the red letters/HTC??? Did you flash boot.img again???
Click to expand...
Click to collapse
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...

Rapier said:
The "red letters" have nothing to do with kernel. To get rid of them you must be S-Off and flash a moded hboot/firmware. There is one in the firmware thread that has the red warning removed.
@qabi: don't use CWM. Flash latest TWRP 2.7, you should be able to flash any ROM with it except the ones for 2.16 hboot
Sent from nowhere over the air...
Click to expand...
Click to collapse
Rapier, can you explain this? A while back I loaded TWRP (S-ON) then loaded one of the CM series (either 11 or 10, can't remember). Then after I flashed boot.img, I was stuck in boot loop with HTC/red letters.
The reason I was asking what he did was I never did get to stop the boot loop myself. I paid to get it fixed, but I would like to know what I should have done to fix the boot loop after flashing the boot.img and having the problem. Seems like a lot of people get this so, so would be nice to know.
I was basically following everything listed on a web page and everything was working. Unlocked boot loader, SuperSU, TWRP etc... the last thing I did was flash the boot.img and then the problems occurred.
As far as the double try for CWM, I am S-OFF, 2.15 and I noticed it happens every now and then. I don't have this issue with TWRP at all.

It is hard to say why, apparently you did all right. What I can think off is a bad download or a bad flash or you could have used a wrong TWRP version. Also that ROM you have tried could have issues. It is very hard to know why without some logs that shows what went wrong
Sent from nowhere over the air...

LS.xD said:
If you have S4 ( I suppose due to te fact you installed TwistedKat) install this recovery -->
Click to expand...
Click to collapse
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!

qabi said:
After much mucking about I flashed the "philz" recovery. That helped alot - I can now enter recovery every time. So apparently the original CWM recovery has problems on the HTC one S.
Thanks for your suggestions guys!
Click to expand...
Click to collapse
I think so. I am running the latest CWM and never had problems before this.

Cannot Flash Any Rom Besides CM11 (set_perm: some changes failed)

Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock (credit for the RUU goes to dottat), installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"

RealROGWaffle said:
Hey guys, just looking for some help with this. For the record, I was using TWRP 2.8. Last night I tried to install NuSenseSIX from the development forum, only to have this error: set_perm: some changes failed. Thinking it was just a problem with the download, I downloaded a second copy, checked the MD5 (which was the same), flashed it, same error. I then tried flashing DigitalHigh's GPE Rom, but the same error had came up. I RUU'd the phone back to stock, installed TWRP, flashed:failed. Flashed CWM, Rom flash:failed (every Rom I mentioned before failed to flash). Everything had the same error, although CWM reported it as Error 7. The only Rom that installs successfully and boots is CM11, I have no clue as to why. I'm stuck, I don't know what to do. Any help would be greatly appreciated.
EDIT: Only the CM11 M10 Snapshot will flash, I just tried to flash the latest nightly (10/5/14) and it gave me "assert failed: run program("/system/bin/makelinks.sh") == 0"
Click to expand...
Click to collapse
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.

dottat said:
Try doing another ruu. Then boot to hboot and chose factory reset. Make sure you do not flash twrp before doing the factory reset.
Click to expand...
Click to collapse
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.

RealROGWaffle said:
Hey dottat! Sorry I forgot to give you credit for the ruu. I'll give that a shot after work tomorrow. Thanks for the reply. By the way, what does flashing TWRP before doing the factory reset do? I flashed mine without even doing that.
Click to expand...
Click to collapse
Factory reset using stock recovery can fix things twrp sometimes can't.

dottat said:
Factory reset using stock recovery can fix things twrp sometimes can't.
Click to expand...
Click to collapse
Alright, thanks. As I said, I'll try it tomorrow. I'll report back with new info.

By the way, what's the difference between the old ruu you made and the new one? I flashed the old one and I want to know if that might be why it didn't fix my issue.

Well... same issue after doing what you said. I'm honestly really sad right now.

RealROGWaffle said:
Well... same issue after doing what you said. I'm honestly really sad right now.
Click to expand...
Click to collapse
I have one more thing I'm going to pm you to try.