Database Develop

[Q] Roms do not work properly

I have 2 custom roms on my phone, cyanogen mod 7.1 stable and miui v.2.4.6.
Cyanogen has everything working except there is a wifi error, meaning i cant use wifi at all. Miui reboots by itself every few seconds, but i wanna be able to use it. What to do? These are the 2 best roms around, and none of them work!

freidchikin said:
I have 2 custom roms on my phone, cyanogen mod 7.1 stable and miui v.2.4.6.
Cyanogen has everything working except there is a wifi error, meaning i cant use wifi at all. Miui reboots by itself every few seconds, but i wanna be able to use it. What to do? These are the 2 best roms around, and none of them work!
Click to expand...
Click to collapse
We need some information about your IncS. What HBOOT version are you running? What method did you do to S-OFF and root your phone?

I'm gonna go ahead and guess. Bootloader unlocked, still on stock kernel.
Flash boot.img found in the rom zip using the fastboot flash boot boot.img command.

I think his device is S-ON with HTCdev unlock. The boot.img was not flashed.

keroro430 said:
I think his device is S-ON with HTCdev unlock. The boot.img was not flashed.
Click to expand...
Click to collapse
I recall reading this somewhere. Oh yea, the post above you

reply
My hboot version is 1.16, s-on with htc bootloader unlock. Then used clockwork mod recovery. I thought ya didnt need s-off?
And yes it still screwed up after doing boot.img (i tried it before on both roms)

Try to downgrade the hboot to 1.13 and get a revoluationary s-off.
Sent from my HTC One X using XDA

Whats the easy way to downgrade hboot? Im new to this stuff.

Check the stickies from this forum.
Sent from my HTC One X using XDA

Nonverbose said:
I'm gonna go ahead and guess. Bootloader unlocked, still on stock kernel.
Flash boot.img found in the rom zip using the fastboot flash boot boot.img command.
Click to expand...
Click to collapse
freidchikin said:
My hboot version is 1.16, s-on with htc bootloader unlock. Then used clockwork mod recovery. I thought ya didnt need s-off?
And yes it still screwed up after doing boot.img (i tried it before on both roms)
Click to expand...
Click to collapse
Ok then the quote above you was spot on. You simply need to manually flash the boot.img when you an unlocked bootloader.

freidchikin said:
My hboot version is 1.16, s-on with htc bootloader unlock. Then used clockwork mod recovery. I thought ya didnt need s-off?
And yes it still screwed up after doing boot.img (i tried it before on both roms)
Click to expand...
Click to collapse
Correct. You do not need s-off to flash a custom rom. I strongly advise against attempting to get s-off if you cannot correctly flash a rom.
You mentioned "tried doing" a boot.img. You cannot use the one in your cwm backup folder as this is not the right one. It must be from the rom you wish to install. This must be done EVERY TIME you change rom on an unlocked bootloader. You should also be wiping cache, dalvik and data.

There is no ruu available for downgrade- i checked. Are you guys sure i need s-off to run miui?

Same problem. I flashed boot.img from the right rom. I did all of those procedures and it still constantly restarts. Also wifi no work. What wrong with miui?

My two cents.. and two questions
freidchikin said:
Same problem. I flashed boot.img from the right rom. I did all of those procedures and it still constantly restarts. Also wifi no work. What wrong with miui?
Click to expand...
Click to collapse
Did you remember to do a "wipe data/factory reset" and wipe the dalwik cache before installing the ROM? Did you see any error messages right after the installation?
Does CM7 restart as well, or is it only MIUI? I remember this happening to me with Virtuous Quattro, and the download file turned out to be faulty. Check that as well.
And no, you do not need s-off to run MIUI.

yes, i did all of that. I do not think the download file is faulty, but i dont know how to check. No, only miui is the rebooting, cyanogen mod only has wifi problem

freidchikin said:
yes, i did all of that. I do not think the download file is faulty, but i dont know how to check. No, only miui is the rebooting, cyanogen mod only has wifi problem
Click to expand...
Click to collapse
I have had WiFi problems with MIUI, but not the one you describe here, and have never seen this with any of the ROMs I have had on my phone, specially Cyanogen. Have you tried flashing Virtuous Quattro or Kaijura's Ice Cream Sandwich?
And to check the downloads, use an md5 checker; there are many available on the internet for free.

Well miui keeps crashing, so i gave up on it.
I am using cyanogen stable 7.1 and everything is working fine except wifi. It wont detect any networks and sometimes it would say that the wifi or settings is not responding. Does anyone know how to fix the wifi?

Unable to put back to stock RUU (Need Original ROM HTC Incredible S)

Hello,
I have HBOOT-2.01.0001 RADIO-3822.01.08.14_M eMMC-boot and I'm running newest Cyanogenmod RC 7.2.0 RC1. Yesterday my phone was stock RUU and I went to HTCDEV.com and unlocked it. After that I flashed the recovery to Clockworkmod v.4.0.1.4 through ADB. Put the CM RC 7.2.0 RC1 .zip on the root of the SD card along with Gapps .zip file.
Then I rebooted into Clockworkmod recovery and installed the 2 .zip files and rebooted. It would not boot and was stuck on HTC logo screen. I found out that I had to separately flash the boot.img file from within the CM RC 7.2.0 RC1 .zip and then everything worked fine.
(Oh yeah, forgot to mention that I did do a backup from within the Clockworkmod before flashing the CM rom)
Ok, so I tested Cyanogenmod for a couple of hours and found out that it was a bit faster than the new stock Ice Cream Sandwich (latest update per 20 april 2012) and it had a lot of ekstra features, but the interface and layout is really low end in my opinion. I gave it a honest try and spent some time changing settings and layouts and even downloaded a couple of ADW themes. Nothing that was even near the new ICS.
Bottom line is that I really want to get back to the original stock RUU Ice Cream Sandwich and I'm unable to
Attempt 1:
I have tried to restore the backup that I made in Clockworkmod and it seems to install just fine. But when restarting it gets stuck on HTC logo Screen. So I thought, maybe this has something to do with the boot.img that has to be flashed manually. So I took out the SD card and put it in my PC using a adapter. Found the boot.img file from the backup inside the clockworkmod/Backup folder and flashed the boot.img file and I'm still stuck on HTC logo screen. It will not boot after recovering the backup no matter what I try.
Attempt 2:
After googling a lot I found the website Shipped ROMs and found my model which I believe to be VIVO (I have a HTC Incredible S from april 2011 in Norway (Europe)).
The only logical RUU i can find is: RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
Since the other 2 RUU's listed are ASIA.
I downloaded the WWE RUU and ran it. I followed the instructions to the point and got the message Error 155 after about 30 seconds right after it is finished with sending.....
Now the phone will not boot again, stuck on HTC logo screen. And so I'm running out of ideas. In other words I'm stuck here
I reflashed the same Cyanogenmod rom and at least that works again
Anybody have any suggestions in how to solve this or any info at all to direct me into the right direction? This would be much appreciated
I'm thinking maybe anybody knows where I can find a stock ROM .zip file for this phone modell that I can flash the same way i do Cyanogenmod (as described above)?
Maybe even an older version like Froyo, but then I hope it is possible to update to latest stock RUU just using the built in "search for update" function in settings.
Yours sincerely,
Mr. T. Nuis

tnuis said:
Hello,
I have HBOOT-2.01.0001 RADIO-3822.01.08.14_M eMMC-boot and I'm running newest Cyanogenmod RC 7.2.0 RC1. Yesterday my phone was stock RUU and I went to HTCDEV.com and unlocked it. After that I flashed the recovery to Clockworkmod v.4.0.1.4 through ADB. Put the CM RC 7.2.0 RC1 .zip on the root of the SD card along with Gapps .zip file.
Then I rebooted into Clockworkmod recovery and installed the 2 .zip files and rebooted. It would not boot and was stuck on HTC logo screen. I found out that I had to separately flash the boot.img file from within the CM RC 7.2.0 RC1 .zip and then everything worked fine.
(Oh yeah, forgot to mention that I did do a backup from within the Clockworkmod before flashing the CM rom)
Ok, so I tested Cyanogenmod for a couple of hours and found out that it was a bit faster than the new stock Ice Cream Sandwich (latest update per 20 april 2012) and it had a lot of ekstra features, but the interface and layout is really low end in my opinion. I gave it a honest try and spent some time changing settings and layouts and even downloaded a couple of ADW themes. Nothing that was even near the new ICS.
Bottom line is that I really want to get back to the original stock RUU Ice Cream Sandwich and I'm unable to
Attempt 1:
I have tried to restore the backup that I made in Clockworkmod and it seems to install just fine. But when restarting it gets stuck on HTC logo Screen. So I thought, maybe this has something to do with the boot.img that has to be flashed manually. So I took out the SD card and put it in my PC using a adapter. Found the boot.img file from the backup inside the clockworkmod/Backup folder and flashed the boot.img file and I'm still stuck on HTC logo screen. It will not boot after recovering the backup no matter what I try.
Attempt 2:
After googling a lot I found the website Shipped ROMs and found my model which I believe to be VIVO (I have a HTC Incredible S from april 2011 in Norway (Europe)).
The only logical RUU i can find is: RUU_Vivo_Gingerbread_S_HTC_WWE_2.30.405.1_Radio_20 .2808.30.085AU_3805.06.03.03_M_release_199308_sign ed.exe
Since the other 2 RUU's listed are ASIA.
I downloaded the WWE RUU and ran it. I followed the instructions to the point and got the message Error 155 after about 30 seconds right after it is finished with sending.....
Now the phone will not boot again, stuck on HTC logo screen. And so I'm running out of ideas. In other words I'm stuck here
I reflashed the same Cyanogenmod rom and at least that works again
Anybody have any suggestions in how to solve this or any info at all to direct me into the right direction? This would be much appreciated
I'm thinking maybe anybody knows where I can find a stock ROM .zip file for this phone modell that I can flash the same way i do Cyanogenmod (as described above)?
Maybe even an older version like Froyo, but then I hope it is possible to update to latest stock RUU just using the built in "search for update" function in settings.
Yours sincerely,
Mr. T. Nuis
Click to expand...
Click to collapse
You can only run and use a RUU successfully when you relock your bootloader. That is what the error 155 is telling out.
In the Development section there is a stock, rooted ICS ROM based on the WWE RUU as well as a couple of custom ICS ROMs based on the stock ICS. You can flash these in CWM like you did CM 7.2

Dude follow nonverbose downgrade technique .... I've gone through same problem...he will help u and he is the best
Smal suggestion ,if u want to upgrade to stock ics 4.0.3 or 4.0.4 its waste of time u will definetly go back to custom roms believe me...
Sent from my HTC Incredible S using xda app-developers app

kalyanroxx said:
if u want to upgrade to stock ics 4.0.3 or 4.0.4 its waste of time u will definetly go back to custom roms believe me...
Click to expand...
Click to collapse
lol everyone has different preferences

tpbklake said:
You can only run and use a RUU successfully when you relock your bootloader. That is what the error 155 is telling out.
In the Development section there is a stock, rooted ICS ROM based on the WWE RUU as well as a couple of custom ICS ROMs based on the stock ICS. You can flash these in CWM like you did CM 7.2
Click to expand...
Click to collapse
Ok thanx Do you have a direct link though? I´m unable to find this......

kalyanroxx said:
Dude follow nonverbose downgrade technique .... I've gone through same problem...he will help u and he is the best
Smal suggestion ,if u want to upgrade to stock ics 4.0.3 or 4.0.4 its waste of time u will definetly go back to custom roms believe me...
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
Thanx man, could you also provide me with a direct link? I´m unable to find this. I don´t get it. Whenever using the "Search All Forums" all this other stuff comes up. I must be searching wrong....

If you want to install stock RUU again, you need to relock the bootloader as some one already pointed out..
To relock the bootloader, enter your phone's bootloader, connect your phone to your computer --> enter fastboot in your bootloader --> fastboot menu should show fastboot usb once the usb is connected --> open command prompt/terminal on your computer --> type fastboot devices. if your phone is recognized, it should show the device serial number.
Then type fastboot oem lock...your phone's bootloader should be relocked...then install the RUU
Sometimes, you need to format the data and system partition for the RUU to work properly. You need to do this before relocking the bootloader through a custom recovery (i find this easy instead of using ADB). This is not mandatory. I ran into some problem once and formatting data and system partitions worked..But, as I said, it happened only once and it is not mandatory to do this every time you relock your bootloader.
Please correct me if I am wrong...
edit :
you can find Stock RUUs in the following link...select your device and carrier
h_t_t_p://www.htcdev.com/devcenter/downloads
pls remove underscores (i cannot post links as i am new here)

tnuis said:
Ok thanx Do you have a direct link though? I´m unable to find this......
Click to expand...
Click to collapse
Just check my signature for a link.

pavankumarpingali said:
If you want to install stock RUU again, you need to relock the bootloader as some one already pointed out..
To relock the bootloader, enter your phone's bootloader, connect your phone to your computer --> enter fastboot in your bootloader --> fastboot menu should show fastboot usb once the usb is connected --> open command prompt/terminal on your computer --> type fastboot devices. if your phone is recognized, it should show the device serial number.
Then type fastboot oem lock...your phone's bootloader should be relocked...then install the RUU
Sometimes, you need to format the data and system partition for the RUU to work properly. You need to do this before relocking the bootloader through a custom recovery (i find this easy instead of using ADB). This is not mandatory. I ran into some problem once and formatting data and system partitions worked..But, as I said, it happened only once and it is not mandatory to do this every time you relock your bootloader.
Please correct me if I am wrong...
edit :
you can find Stock RUUs in the following link...select your device and carrier
h_t_t_p://www.htcdev.com/devcenter/downloads
pls remove underscores (i cannot post links as i am new here)
Click to expand...
Click to collapse
Will it be installed same way as other ROms are flashed and does it have sence aswell ?? like the original which was factory installed

jaspreet13 said:
Will it be installed same way as other ROms are flashed and does it have sence aswell ?? like the original which was factory installed
Click to expand...
Click to collapse
No, a RUU is a Windows PC App that you run on your PC and then follow the instructions to attach your phone via the USB cable when prompted.
It will install a stock Sense ROM to your IncS. The only version on HTCDEV.com is the final ICS 4.0.4 ROM with Sense 3.6.

tpbklake said:
No, a RUU is a Windows PC App that you run on your PC and then follow the instructions to attach your phone via the USB cable when prompted.
It will install a stock Sense ROM to your IncS. The only version on HTCDEV.com is the final ICS 4.0.4 ROM with Sense 3.6.
Click to expand...
Click to collapse
and the one in your signature line, is that the same rom though the version seems different ?

jaspreet13 said:
and the one in your signature line, is that the same rom though the version seems different ?
Click to expand...
Click to collapse
The one in my signature is built from the 4.14.405.1 RUU and is a fully rooted version of this stock ROM.
You can flash it on an unlocked bootloader from recovery just like you would for other custom ROMs.
Since you have an unlocked bootloader, you would have to manually flash the boot.img file contained in the ROM's zip file just like other custom ROMs.

tpbklake said:
The one in my signature is built from the 4.14.405.1 RUU and is a fully rooted version of this stock ROM.
You can flash it on an unlocked bootloader from recovery just like you would for other custom ROMs.
Since you have an unlocked bootloader, you would have to manually flash the boot.img file contained in the ROM's zip file just like other custom ROMs.
Click to expand...
Click to collapse
and does it has same sense features, lock menu and widgets like original one,,.. coz i find flashing rom easier than installing RUUs, i had downloaded the stock from Dev website it doesnt have any executable file in it...

jaspreet13 said:
and does it has same sense features, lock menu and widgets like original one,,.. coz i find flashing rom easier than installing RUUs, i had downloaded the stock from Dev website it doesnt have any executable file in it...
Click to expand...
Click to collapse
Yes, it has full stock Sense 3.6.
As for the download, sounds like you may have downloaded the kernel source and not the RUU.

tpbklake said:
Yes, it has full stock Sense 3.6.
As for the download, sounds like you may have downloaded the kernel source and not the RUU.
Click to expand...
Click to collapse
I'll then go for the one you have on your signature and have an upgraded version aswell,
so its same way i install other roms by flashing boot img manually
thanks buddy

HELP - phone wiped and no rom - how do I flash?

Hi,
I've got S-OFF's phone with bootloader unlocked.
I've had the phone months and been using various custom roms and firmwares.
I'd tried the latest 3.17 rom but the radio was rubbish and decided to go back to 2.24.401.8 based rom.
I flashed the unmodified 2.24.401.1 firmware (inc HBOOT, radio etc.)
This went fine, but it's wiped my phone and now I have no ROMs on the phone to be able to flash them.
How do I get my phone back up and running???
please help

Had that once,too. Try to upload the rom with adb or a toolkit
Sent from my HTC One using XDA Premium 4 mobile app

Either fastboot a ruu, run a ruu.exe, or you have to adb sideload a rom in twrp
Sent from my HTC One using Tapatalk 2

danlat1415 said:
Hi,
I've got S-OFF's phone with bootloader unlocked.
I've had the phone months and been using various custom roms and firmwares.
I'd tried the latest 3.17 rom but the radio was rubbish and decided to go back to 2.24.401.8 based rom.
I flashed the unmodified 2.24.401.1 firmware (inc HBOOT, radio etc.)
This went fine, but it's wiped my phone and now I have no ROMs on the phone to be able to flash them.
How do I get my phone back up and running???
please help
Click to expand...
Click to collapse
Follow this procedure:
You need to relock your bootloader and flash a RUU.zip which is the stock 4.1.2.

Thanks for your suggestions.
I managed to sort it by flashing CWM recovery, going in it and doing a full wipe (the firmware change seemed to have messed up the data on phone rathan than wipe it.
Then I use adb push ROM.zip /sdcard/ROM.zip (naming my custom Rom ROM.zip)
I was then able to load the Rom in CWM and get the phone running.

I've seen a lot of people resorting to a RUU lately. It seems like every time someone has trouble, that's the answer they get. RUU's are usually a last effort to fix a phone. In most situations there's an easier fix. ( like adb push )
Sent from my HTC One using XDA Premium 4 mobile app

Touch Panel Firmware

Hey guys, I have noticed many people trying to return to 4.1 roms after flashing the new firmware from the 4.3 update and then their touchscreens not work. As a result, many people have had to resort to running the 1.29.651.10 RUU in order to get a working touchscreen again.
In order to help alleviate this problem, I went ahead and pulled the touch panel img from the 1.29.651.10 decrypted RUU. This way, people can just downgrade their touch panel firmware instead of having to downgrade everything with the RUU.
It should be noted that that I am posting the touch panel img from the 1.29.651.10 RUU because the touch panel img was not included in the 1.31.651.2 OTA.
EDIT:
I decided to use this thread to keep the different touch panel firmwares in one location just in case anyone needs them for whatever reason it may be, so here are the zips:
1.29.651.10
3.04.651.2
3.05.651.5
So to flash this you need to be S-OFF and just rename the zip to "firmware" then boot into fastboot and run the following commands:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot

Thanks for posting this, This is just the Touch Panel, Correct ?

DNarsingh said:
Hey guys, I have noticed many people trying to return to 4.1 roms after flashing the new firmware from the 4.3 update and then their touchscreens not work. As a result, many people have had to resort to running the 1.29.651.10 RUU in order to get a working touchscreen again.
In order to help alleviate this problem, I went ahead and pulled the touch panel img from the 1.29.651.10 decrypted RUU. This way, people can just downgrade their touch panel firmware instead of having to downgrade everything with the RUU.
It should be noted that that I am posting the touch panel img from the 1.29.651.10 RUU because the touch panel img was not included in the 1.31.651.2 OTA.
So to flash this, just rename the zip to "firmware" and then boot into fastboot and run the following commands:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
Thanks, it save me alot !

drlzanej said:
Thanks for posting this, This is just the Touch Panel, Correct ?
Click to expand...
Click to collapse
Yup, just the touch panel img

DNarsingh said:
Yup, just the touch panel img
Click to expand...
Click to collapse
Thanks again, not that Im thinking of going back to 4.1\4.2, Im really liking 4.3, but good to have on hand just in case. :good:

drlzanej said:
Thanks again, not that Im thinking of going back to 4.1\4.2, Im really liking 4.3, but good to have on hand just in case. :good:
Click to expand...
Click to collapse
Yea, same here. I posted it for a few people last night, so I figured why not make a thread just in case anyone else needs it. Either way I don't think I will be downgrading from 4.3 anytime soon.

I really appreciate you pulling and creating a zip. It was driving me crazy not to be able to use my otg cable. Flashed your zip and rolled back to twrp 2.5.0.0.
Thanks again
Sent from my HTCONE using XDA Premium 4 mobile app

sweet! i was hoping someone would post this.. same thing happend with the evo 4g LTE.. thanks so much! so if im on the new firmware 3.04 base and im on a new base rooted rom.. what do i have to do to go back?? flash this old touch pannel zip.. then flash old 1.31 rom? is there anyway u could post just the new touch pannel zip also.. so we can have the old and new just in case dont i have to flash the old 1.31 firmware also if i want to flash a 1.31 rom?? i want to go back to tranquil rom which is 1.31 base.. is there an 1.31 firmware file for s-off people to flash? well hope i did it rite!! lol i flashed the old TP file.. then flash twrp 2.5.0.0 then 1.31 rom then 1,31 firmware for s-off people.. everything seem to be good so far!! thanks so much im back to where i want to be.. now ill sleep better tonite..

CWM Recovery 6.0.4.3 Touch. work perfect with the OTA 4.3 update

works fine with the latest twrp also..

Is it possible to flash the whole firmware (radio, modem, etc) without flashing a RUU? I'd like to downgrade my firmware, but don't want to relock bootloader and download all the ruu. Can you upload the full old firmware(without hboot)? Can I just flash it with fastboot without needing the whole RUU? Thanks

elvisypi said:
Is it possible to flash the whole firmware (radio, modem, etc) without flashing a RUU? I'd like to downgrade my firmware, but don't want to relock bootloader and download all the ruu. Can you upload the full old firmware(without hboot)? Can I just flash it with fastboot without needing the whole RUU? Thanks
Click to expand...
Click to collapse
Give me a bit, I will try to have it up later today.
EDIT: Actually, if you use my zip to downgrade your touch panel firmware, you can just go here to get the firmware from the 1.31.651.2 update instead of downgrading all the way to 1.29.651.10:
http://forum.xda-developers.com/showthread.php?t=2368907

Everything is workfine
Thank's dude ,you're rock
Sent from my HTCONE using Tapatalk 2

I flashed the updated firmware and lost my touch screen. I am S-off, but I can not get my phone to reboot. I hold the power button and the VOL+/- buttons and it counts down 3 seconds until reboot but holds at 1 second and the back and home button are flashing. How do I fix my phone?
Thanks

HuDuVuDu said:
I flashed the updated firmware and lost my touch screen. I am S-off, but I can not get my phone to reboot. I hold the power button and the VOL+/- buttons and it counts down 3 seconds until reboot but holds at 1 second and the back and home button are flashing. How do I fix my phone?
Thanks
Click to expand...
Click to collapse
If you flash a 4.3 rom, you will have touch again.
As for getting into recovery, do you have adb set up? If not, use this:
http://forum.xda-developers.com/showthread.php?t=1698471
EDIT: and when I say 4.3 rom, I mean a 4.3 Sense rom, I'm not sure about an AOSP rom.

DNarsingh said:
If you flash a 4.3 rom, you will have touch again.
As for getting into recovery, do you have adb set up? If not, use this:
http://forum.xda-developers.com/showthread.php?t=1698471
Click to expand...
Click to collapse
4.3 aosp too??

DNarsingh said:
If you flash a 4.3 rom, you will have touch again.
As for getting into recovery, do you have adb set up? If not, use this:
http://forum.xda-developers.com/showthread.php?t=1698471
Click to expand...
Click to collapse
I do have ADB setup on my mac. Duh. "ADB reboot"
Thanks for kicking me in the head and waking me up.

Aldo101t said:
4.3 aosp too??
Click to expand...
Click to collapse
Actually, I'm not sure about that.
HuDuVuDu said:
I do have ADB setup on my mac. Duh. "ADB reboot"
Thanks for kicking me in the head and waking me up.
Click to expand...
Click to collapse
Haha, no problem.

Back up and running. Thanks for the kick.
Sent from my HTCONE using Tapatalk 4

Can someone tell me :
I'm in stock 4.3 and want to go to stock 4.2
So I need to flash the 4.2 and than flash this file to make the touch screen back to work?
Because after I flashed the 4.2 the touch screen stop working .

Viper Rom clusterF

I have an older version of Viper ROM on my HTC One M8 Sprint...
I've been having dropped calls like mad and I see that there is a new version of Viper.
BUT - there is some sort of issue with the firmware and so I have to somehow flash a stock ROM and do OTA - oh goodie!!
Heck man.. I love tinkering with my phone. But I have now spent HOURS AND HOURS trying to figure this out!
I am NOT s-off and I have tried numerous ways to get s-off - not going to happen.
I was successful upgrading TWRP to 2.8. BUT, the version-main of my OS is blank so I have no idea what OS I have.
Can anyone please tell me the easiest way to remedy this? I'll donate, give you beer money, whatevs!! I am just sick of trying to figure this out.
I think I just need to find the correct stock ROM and flash it right? PLEASE HELP!

No a Rom flash won't fix your issue, well unless it's stock and the previous version then you updated the software but for all that there's this thing called a ruu which stands for Rom update utility. So what you need to do is ruu to the latest 4.4.4 and from there reunlock boot loader with HTC unlock then push a recovery image via fastboot and then flash the viper Rom Sprint kernel via fastboot then go to recovery and install the Rom. Or you can just take 25 bucks and buy s-off and make your life easier with just flashing the firmware.

Sinistertensai said:
No a Rom flash won't fix your issue, well unless it's stock and the previous version then you updated the software but for all that there's this thing called a ruu which stands for Rom update utility. So what you need to do is ruu to the latest 4.4.4 and from there reunlock boot loader with HTC unlock then push a recovery image via fastboot and then flash the viper Rom Sprint kernel via fastboot then go to recovery and install the Rom. Or you can just take 25 bucks and buy s-off and make your life easier with just flashing the firmware.
Click to expand...
Click to collapse
Thanks - already tried the $25 s-off fix and it said I need to flash a stock rom or nearer stock rom. Believe me, I would gladly give $25 to get my phone to where it needs to be.

markinsf said:
Thanks - already tried the $25 s-off fix and it said I need to flash a stock rom or nearer stock rom. Believe me, I would gladly give $25 to get my phone to where it needs to be.
Click to expand...
Click to collapse
Try doing it again but fastboot flash a stock kernel (boot.img) you can get that in the firmware zip provided in development.

Run RUU then try s-off