To cut a long story short, it seems the HBOOT on my Sensation is the latest one and is not compatible with Revolutionary, doesn't even get upto the point where it's meant to generate the beta key, just says HBOOT isn't supported.
Short of jamming wires into my phone, it seems I can't get S-OFF on the current HBOOT, but I have got the official HTC Dev bootloader unlock working fine and my phone is currently rooted on the stock ICS ROM.
However I want to install CM9 on my phone. AFAIK, with the official HTC bootloader unlock my kernel and radio cannot be changed but everything else can.
So can I install CM9 successfully using CWM if I have the official bootloader unlock or will it only work with S-OFF? I guess the real question is will CM9 on the Sensation work with the default kernel, radio, and firmware?
Thanks!
NVM, finally found a good guide to flash custom ROMs and with custom kernels with S-ON if you are HTC bootloader unlocked, will use this for CM9 and see how it goes
did you find that after doing this it messed up your wifi, cuz near the end it says there's a possibility?
Been using it for a day and WiFi works perfectly.
The WiFi will only be a problem if the kernel doesn't flash, but in the case of CM9 it needs a custom kernel to even boot anyway, the Sense kernel won't work. So if CM9 boots it'll work
Also 4EXT has been updated since that thread was written and when you install the 4EXT recovery it now asks you if your device is S-ON, if you hit yes it'll turn the SmartFlash thing on automatically. What that does is flash the kernel separately before you exit the recovery to reboot back into Android and in my case it worked fine
Only catch is that you can only install ROMs for your current firmware. I have 3.32 so I can pretty much install any ICS ROM, but I can't install a GB ROM and I might not be able to install a Jellybean ROM, for example. But I'll cross that bridge when I come to it
I had this too, and I found out that I could flash only ROMs, where kernel is ready made .img file inside the zip. To do this, I needed to install the ROM (it installed into /system, but the kernel couldn't be installed due to protection), reboot into fastboot, and flash the extracted kernel img with ADB from the PC (as ADB was only way to flash kernel).
If there was a custom installer where I could configure the kernel (set CPU speed etc)., that would mean that the kernel image is assembled during installation, and it is not readily available in ROM. In that case, I was f***ed .
Most ROMs have the standard boot.img file in the .zip though, and you can check it by just extracting the files and taking a look
The 4EXT process basically does the same as you did but automatically, it's just as much effort as flashing a ROM normally
I see one problem with that your are using cwm as the recovery and that simply will not work because you can't flash kernels because your s on but there's light at the end of the tunnel but you must be rooted to do this you Will need to install 4ext custom recovery why because it will allow you to flash kernels with smart flash enabled and you can't do that with cwm
Sent from my Sensation Z710e using xda premium
Related
i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.
Hello Everyone, I am hoping someone can tell me what to do to fix this, I have been searchng and reading and trying things I have found online all day, but without luck. I dont think Im savvy enough to know what is actually wrong.
My Phone :
Australian Telstra HTC Sensation running ICS (OTA update)
here is my problem :
Wifi will not turn on, comes up status of error.
I flashed CWM + supersu v0.89 onto my phone to give myself root access so that I can use the gesture control application and also to get access to the \data\data\ folder for the Dead Trigger hack. this worked without issue.
I noticed that I was having major issues with multi-touch after putting ICS on my phone. I read that this is a known issue with ICS on sensations, and that a custom rom would be my best bet to fix.
I had read alot about cyanegen (or however you spell it) mods on androidpolice, so i decided to give that one a go.
Being a noob, I didnt know my sensation cannot be S-off'd (due to Hboot 1.27) and when I flashed the rom onto my phone, it would not boot passed the boot animation. (I followed the instructions on their site and did a backup with CWM as well as wiping the phone).
Looking into the no-booting issue, I found out that my phone is not S-off'd and is the reason the flash did not work, something about not being able to replace the boot.img and custom kernel.
So I found a stock kernel rom (ARHD 6.6.7) and flashed that onto my phone. this one boots, but the wifi will not turn on.
I decided stuff it, and used CWM to restore my backup, now my phone is back to how it was before I started all this flashing, accept that the WIFI will not turn on at all!
please can someone help me? I have no idea how to fix this, I thought using the recover option in CWM would put my phone back to how it was at the beginning, and with the exception of the wifi issue it did. all my apps and customizations came back.
How can fix my WIFI issue?
I have a Telstra Sensation too & i've never had any wifi problems with custom ROMs.
Did you superwipe between flashing ROMs? & Did you flash a different kernel?
Hi, I tried running superwipe which is on the ARHD 6.6.7 thread, however it got a "status 1" error message, so I used the wipe data and cache options available in CWM (which was the steps listed in the cyanagen mod install)
I also tried flashing SebastianFM's custom kernel, but that gave a "status 7" error message. Is this what buggerd my phone?
Thankyou for the fast reply!
the sole reason for everything is recovery
(ARHD says 4EXT custom recovery is mandatory ..yet you are still using CWM)
now first change the recovery to 4EXT
how and all the bleow guide explains (when you are not SOFF ..but SON and have htc-dev unlocked bootloader ..you have to flash roms ..little bit differentely ..traditional way wont work)
FLASHING ROMS WITH SON
FOLLOW the guide to the letter
i got wifi issues when using faux kernel.. no problem with sebastian's
Thankyou so much for that. That solved my issues completely, I was able to flash Cyanogen onto my phone and it boots, wifi works too!
Can you tell me, can I use 4EXT to flash Sebastians custom kernel even though I am S-ON?
templargfx said:
Thankyou so much for that. That solved my issues completely, I was able to flash Cyanogen onto my phone and it boots, wifi works too!
Can you tell me, can I use 4EXT to flash Sebastians custom kernel even though I am S-ON?
Click to expand...
Click to collapse
First do the step 5 in the guide that I've mentioned (permanent enabling of smartflash)
Then forget about smart flash and flash any kernel
Alternatively if you didn't make smart flash permanent yet (which I highly recommend you to do)
You can enable smart flash just before flashing kernel and can flash any kernel
Sent from my pyramid.. Through blazing fast sonic waves
I am HTCDev unlocked and I am runnin ViperS 1.41 is there anyway to flash Faux kernel? I tried the Viper-application and it didn't work.
I remember something with Hboot but I don't know where to get the kernel img.
If you are already using ViperS rom you should be able to flash Faux kernel from your recovery. Just download the kernel you want to flash, place it on your sd card, go to 4ext recovery (make sure smartflash is on) and just flash it. I assume (correct me if I'm wrong) along with "smartflash", the faux kernel will flash the boot.img automatically. Ohh and before you do anything make nandroid backup, so if it is not working then you will be able to restore your rom!
Well it didn't work and I can't restore from backups nor install new roms, it just bootloops all the time, I have tried to format all partitions (except sd card) with 4EXT tried with and without smartflash.. sigh.
A fresh start could help. If you are htcdev unlocked, s-on, 4ext recovery installed and you follow THIS guide, you will be able to install roms. If it doesn't boot up after you enabled smartflash in 4ext then do step "extra1" from that guide
Well in the HBoot it says that I am unlocked, but it's worth giving a try, I am pretty sure that you know better than I do,
I redid everything; First HTCDev unlock, flash recovery and then try to flash a new rom. It didn't work so now I will try to do a RUU.
Just enable smartflash and flash the kernel that will do for you
Now as you are SON you should always make sure that smartflash is enabled all the time..whatever you are flashing
Sent from my HTC Sensation using xda premium
Not to be offensive or anythign, but it's kinda hard to flash a kernel when I am stock in a bootloop. I'm downloading the RUU right now and I hope that it fixes it.
I have tried flashing, wiping, smartflashing etc. on Bruce's and ViperS (both 1.35 and 1.41) and also flash from backups. Everything have just bootlooped.
I don't get what you mean on "hard to flash a kernel when I am stock in a bootloop". You don't need to power up your rom to flash a kernel. You go into recovery, enable smartflash, choose the zip file from the sd card and that's it. Also try another kernel and see if that works. I recommend Overclocked Kernel v1.5.2 by SebastianFM as well. I am using that on stock sense rom and it works very well. If you flash a rom and you follow everything word by word in the thread was linked to you then it must work. If you still have issues, then try to post in that thread and someone will help you there.
No I don't need a rom to flash a kernel, but I need to be able to flash a rom, and apparently something went wrong (I don't know what). If you read my prior posts you'd understand what I mean. I couldn't flash any roms (and both ViperS and Bruce have a built into the rom kernel), so I were forced to get a RUU (The XE RUU is hard to find) and do everything from the very start (not just do step one).
Blackzter said:
No I don't need a rom to flash a kernel, but I need to be able to flash a rom, and apparently something went wrong (I don't know what). If you read my prior posts you'd understand what I mean. I couldn't flash any roms (and both ViperS and Bruce have a built into the rom kernel), so I were forced to get a RUU (The XE RUU is hard to find) and do everything from the very start (not just do step one).
Click to expand...
Click to collapse
did you try also to flash the boot.img of the rom manually?
Blackzter said:
No I don't need a rom to flash a kernel, but I need to be able to flash a rom, and apparently something went wrong (I don't know what). If you read my prior posts you'd understand what I mean. I couldn't flash any roms (and both ViperS and Bruce have a built into the rom kernel), so I were forced to get a RUU (The XE RUU is hard to find) and do everything from the very start (not just do step one).
Click to expand...
Click to collapse
You got me wrong mate. Under do step "extra1" I mean do step EXTRA1. There is a step called Extra1 in the thread I linked before. That explains how to flash boot.img manually.
Hello, recently i've just rooted my htc one s, s4. I stalled for a bit and had the 4.0.4 update already, so currently I have root access with the stock firmware. I'm looking through the rom list and the viper One s room caught my eye. So my question is, are there any prerequisite requirements before i flash this rom. Sorry for such a ridiculous question, but i havn't flashed a rom since the G1 and I remember having to flash certain kernels for certain roms. I still haven't messed with the kernel yet so that's stock too.
_________________________________________________________
My One S is s4 t-mobile, TWRP recovery, obtained root access with the All in One Toolkit v3.0 by hasoon2000. firmware is stock update 4.0.4 and everything else is just stock. so all i did was root
Just follow the instructions in the Viper Thread.
Since you have it rooted (and I assume a working recovery) you should already have all tools needed (fastboot etc).
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
rugmankc said:
On the Working Recovery, I would recommend installing TWRP. Best recovery atm for rom flashing. Get it thru the Goo Manager App on PlayStore. Just open Goo Manager then open Menu and tap on Install OpenScript Recovery.
Read OP pages carefully and scan the threads of the rom you want to flash. Depending on your hboot version, you may have to fastboot boot.img right after flashing rom. If at or above .13. Or, get Flash Image GUI from PlayStore and it will do it for you.
On CM roms there are some other quirks with radio etc, so some pre-study would be advised as well as nandroiding and backing up sdcard first. Put both backups on PC for extra safety.
Good Luck--
Click to expand...
Click to collapse
Thanks! i went ahead and flashed viper rom and after reading a bit i noticed that i had hboot .14 so it broke my wifi . I'm still currently searching info and came across that i need linux to downgrade, which i don't have . do you know any other method? or roms beside trickdroid 7 that support the hboot version and allow wifi?
On .14 the items I mentioned will apply on all roms
Not sure on wifi, i use mostly cm roms atm
Im on Hboot .14, and wifi works fine for me on viperS
there is a wifi partition zip floating around for wifi issues. didn't pay much attn to it as i have no issues--maybe a search, or someone will post it
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.