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.

[Q] Revert to stock ICS after JB OTA?

I was running ICS on my One S (S3). Installed TrickDroid v5 (JB), but there were a couple of issues with it. So I decided to go back to ICS. I just ran the 2.15 RUU. And I was back on ICS. A day later I got the JB OTA. Installed that, everything was working great, until I tried doing something stupid, and managed to wipe the entire phone.
Long story short, I got the phone working again, by putting in TrickDroid v5 again. Thing is, I want the official JB OTA. How do I do this? There aren't any RUU's for JB. I tried downloading this: http://forum.xda-developers.com/showpost.php?p=37398225&postcount=41 for my CID (J15).
I don't know how to install it though. I just put it on my sdcard, and tried to install it with TWRP. It just give me a bunch of errors. I also tried running the older ICS 2.15 RUU. It doesn't work either. Just says older hboot.
What I want to do is to revert back to stock ICS, so that I can get the JB update again? Is this possible? Or anything else I can do?
Any ideas, anyone?

firefiber said:
I was running ICS on my One S (S3). Installed TrickDroid v5 (JB), but there were a couple of issues with it. So I decided to go back to ICS. I just ran the 2.15 RUU. And I was back on ICS. A day later I got the JB OTA. Installed that, everything was working great, until I tried doing something stupid, and managed to wipe the entire phone.
Long story short, I got the phone working again, by putting in TrickDroid v5 again. Thing is, I want the official JB OTA. How do I do this? There aren't any RUU's for JB. I tried downloading this: http://forum.xda-developers.com/showpost.php?p=37398225&postcount=41 for my CID (J15).
I don't know how to install it though. I just put it on my sdcard, and tried to install it with TWRP. It just give me a bunch of errors. I also tried running the older ICS 2.15 RUU. It doesn't work either. Just says older hboot.
What I want to do is to revert back to stock ICS, so that I can get the JB update again? Is this possible? Or anything else I can do?
Any ideas, anyone?
Click to expand...
Click to collapse
In order to load an RUU from rooted device. First you have to relock your boot loader. Then all you have to do is connect the phone in fastboot usb to computer and run the RUU file on the PC.
One thing to note is that this only works if you are loading an RUU which is the same version you currently have or updated version. Can't get a previous version from one you have already. So I am guessing you have to downgrade your hboot or change your CID which is much more complicated and risky.
Sent from my One S using Xparent Skyblue Tapatalk 2

LikeaG2root said:
In order to load an RUU from rooted device. First you have to relock your boot loader. Then all you have to do is connect the phone in fastboot usb to computer and run the RUU file on the PC.
One thing to note is that this only works if you are loading an RUU which is the same version you currently have or updated version. Can't get a previous version from one you have already. So I am guessing you have to downgrade your hboot or change your CID which is much more complicated and risky.
Sent from my One S using Xparent Skyblue Tapatalk 2
Click to expand...
Click to collapse
Mate that link wasn't an executable RUU. There aren't any executable JB RUU's. It's a zip file. I don't know how to install it. I tried to flash it in TWRP, and like I said, it just gives me a bunch of errors.
So is there any way to downgrade my HBOOT? I already tried installing an older ROM (Trickdroid with ICS). And then from there, trying to update. Doesn't work. So basically, I need to downgrade my hboot. If ANYONE can tell me if there's a way to do that, that would be awesome.

firefiber said:
Mate that link wasn't an executable RUU. There aren't any executable JB RUU's. It's a zip file. I don't know how to install it. I tried to flash it in TWRP, and like I said, it just gives me a bunch of errors.
So is there any way to downgrade my HBOOT? I already tried installing an older ROM (Trickdroid with ICS). And then from there, trying to update. Doesn't work. So basically, I need to downgrade my hboot. If ANYONE can tell me if there's a way to do that, that would be awesome.
Click to expand...
Click to collapse
Its very risky and you need Ubuntu to do this...http://forum.xda-developers.com/showthread.php?p=34076562
Sent from my One S using Xparent Skyblue Tapatalk 2

Yeah I was thinking of trying that, but the thing is, it says I shouldn't try it if I took the JB OTA. Which I did. So now I'm not sure how to proceed.

firefiber said:
Yeah I was thinking of trying that, but the thing is, it says I shouldn't try it if I took the JB OTA. Which I did. So now I'm not sure how to proceed.
Click to expand...
Click to collapse
You need a 4.0.4 customrom which is based one the official release/close to stock.
Like zenRom for the S4 Version.
Maybe there is a similar one for the S3.
If you find one, do a clean install off the rom, boot full. Flash stock recovery. (You dont have to relock your bootloader, its only for RUUs)
Do a factory reset. Boot your phone and you will receive the official jb ota.
After receiving and installing the ota i recommend you to do a factory reset again.
If everything works fine, you should have a clean official jellybean Rom.
This procedure worked with the s4 Version, i can confirm it twice

How to re-flash stock JB rom with OTA (custom recovery)

Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.

Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S

JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.

Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^

I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.

orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.

Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app

tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?

bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app

[SOLVED] Need To Fuly Revert To Stock

Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
I no longer need to downgrade to get the WiFi thanks to this great post here: WiFi Fix
I hope this helps people in the future.

All roms wifi works fine for me on hboot 1.14...

Vuciz said:
Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
i regret rooting my phone.. i cant sell it because they dont want a rooted phone

Re: Need To Fuly Revert To Stock
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app

zaak00 said:
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
so let me post it the fourth time ..
http://forum.xda-developers.com/showpost.php?p=37942416&postcount=2

Usually you'll find answers to your problems in the according rom section as you're not the only one with it.
But as you are pretty new here:
1. You can use Linux livecd for downgrading. More here. The process isn't that easy so and you'll need to be patient and careful. (I did that couple of times on my device. The first time it was really worse also I was/am not new to Linux).
2. 1.14 means you have been on ICS only so far. So any ICS rom should work for you. If there is still trouble with wifi, search for answers in that rom section. I remember some guys editing a file for enabling/boosting wifi. As I'm not concerned by this, I have no links.
3. If you'd like to move to JB roms search for 'flashing wifi partitions' as long as you want to keep 1.14. If flashing the OTA update for JB your bootloader version will be 2.15 and the according wifi partitions will be working as well. For both, ICS and JB.
Substantially there will be no real differences for you between 1.14 and 2.15 as only with 1.06 and 1.09 you don't need to flash kernels via fastboot mode.
Hope you got the point as my answer is very short.

OTA but keep Root?

Hey im tryinna OTA update my One S its at Android Version 4.0.4 Sense 4.1 and i have an OTA ive had it for a while now. How could i update it and keep my root? Or if i install a higher version custom rom will it brick my phone?
Sent from my HTC VLE_U

Br00talBean said:
Hey im tryinna OTA update my One S its at Android Version 4.0.4 Sense 4.1 and i have an OTA ive had it for a while now. How could i update it and keep my root? Or if i install a higher version custom rom will it brick my phone?
Sent from my HTC VLE_U
Click to expand...
Click to collapse
not sure what you mean with your last sentence... but:
in my case the ota deleted my root. but I also recommend to do a factory reset after updating to 4.1 sense 4+, just to be sure that you have a clean jb rom (do titanium backups of your apps you wanna keep).
but you have to be on stock recovery if you want to apply the ota.
after your update you can root your phone again.
applying the ota wont have any effect on flashing a higher / newer custom rom.
you only have to be unlocked and on custom recovery. but you alawys have to flash the boot.img of the custom rom after flashing the custom rom zip.

NQNH said:
not sure what you mean with your last sentence... but:
in my case the ota deleted my root. but I also recommend to do a factory reset after updating to 4.1 sense 4+, just to be sure that you have a clean jb rom (do titanium backups of your apps you wanna keep).
but you have to be on stock recovery if you want to apply the ota.
after your update you can root your phone again.
applying the ota wont have any effect on flashing a higher / newer custom rom.
you only have to be unlocked and on custom recovery. but you alawys have to flash the boot.img of the custom rom after flashing the custom rom zip.
Click to expand...
Click to collapse
My bad i wasnt even payin attention to what i was typing and im still pretty much a noob at Root stuff so please bear with me lmao
Lets say i try to flash a 4.2.2. Rom even though im originally at 4.0.4. Would it brick my phone?
So would stock recovery be the stock rom i still hqve after rooting? I havent applied any custom roms at all since ive rooted
Sent from my HTC VLE_U

Br00talBean said:
My bad i wasnt even payin attention to what i was typing and im still pretty much a noob at Root stuff so please bear with me lmao
Lets say i try to flash a 4.2.2. Rom even though im originally at 4.0.4. Would it brick my phone?
So would stock recovery be the stock rom i still hqve after rooting? I havent applied any custom roms at all since ive rooted
Sent from my HTC VLE_U
Click to expand...
Click to collapse
the rom you want to flash doesnt care about your previous rom, because you wiped your previous rom.
so it really doesnt matter which rom you have before if you want to flash a new rom.
its like.. you have installed windows xp, then format your hdd and install windows 7, windows 7 doesnt take a --- about the old os
recovery and rom are two different parts.
you can stock recovery and custom rom, you can have custom recovery and custom rom, you can have stock recovery and stock rom.. blaaa

NQNH said:
the rom you want to flash doesnt care about your previous rom, because you wiped your previous rom.
so it really doesnt matter which rom you have before if you want to flash a new rom.
its like.. you have installed windows xp, then format your hdd and install windows 7, windows 7 doesnt take a --- about the old os
recovery and rom are two different parts.
you can stock recovery and custom rom, you can have custom recovery and custom rom, you can have stock recovery and stock rom.. blaaa
Click to expand...
Click to collapse
Oooh okay i get what youre saying. Soo recovery and the rom are two different things. I can upgrade to whatever gigher version i want. What about the OTA? If i upgrade to higher version custom rom will the OTA icon go away?
Sent from my HTC VLE_U

Br00talBean said:
Oooh okay i get what youre saying. Soo recovery and the rom are two different things. I can upgrade to whatever gigher version i want. What about the OTA? If i upgrade to higher version custom rom will the OTA icon go away?
Sent from my HTC VLE_U
Click to expand...
Click to collapse
after u have flashed a custom ROM, you wont get any OTA updates
Well, not from HTC anyways

Seraz007 said:
after u have flashed a custom ROM, you wont get any OTA updates
Well, not from HTC anyways
Click to expand...
Click to collapse
Oooooooh okay i get it now wow haha so custom rom updates are the OTA pretty much once its flashed on there?
Sent from my HTC VLE_U

Br00talBean said:
Oooooooh okay i get it now wow haha so custom rom updates are the OTA pretty much once its flashed on there?
Sent from my HTC VLE_U
Click to expand...
Click to collapse
well no
but u can update and then Root
That way you'll have the OTA radio and hboot and the custom ROM