Since I've rooted I obviously don't get new hboots, but the newest Viper is 3.20 base while I think I'm only on 3.18. Are there any downloadable hboots for HTC__023?
noodlesfordaddy said:
Since I've rooted I obviously don't get new hboots, but the newest Viper is 3.20 base while I think I'm only on 3.18. Are there any downloadable hboots for HTC__023?
Click to expand...
Click to collapse
To flash a ROM with a 3.20 base, you don't need to have the 3.20 firware...
I have the same CID as well HTC__023...
I have tried ARHD 21 and it works perfectly... however not much of a sense fan since I started using AOKP
What is the newest 023 firmware anyway though?
noodlesfordaddy said:
What is the newest 023 firmware anyway though?
Click to expand...
Click to collapse
I'm on 3.17.728.1...
I using a custom rom so OTA is out of question. I had updated everything (2 months ago) and at that time 3.17 was the latest... No idea whether OTAs have been pushed out afterwards.
Related
witch one is the latest + rootable rom? because im on 1.34.405.5 CL273326 is 1.72 because im not reciving OTA updates and need to flash a RUU form this thread http://forum.xda-developers.com/showthread.php?t=971109 to update so what ones is the latest and rootable?
scottmahoney said:
witch one is the latest + rootable rom? because im on 1.34.405.5 CL273326 is 1.72 because im not reciving OTA updates and need to flash a RUU form this thread http://forum.xda-developers.com/showthread.php?t=971109 to update so what ones is the latest and rootable?
Click to expand...
Click to collapse
If you want the easy and safest way to root, use v.1.34 instead of 1.72. Dont receive OTA if you want to root your device.
ahh ok great as my device seems to be stuck on 1.34 lol
scottmahoney said:
ahh ok great as my device seems to be stuck on 1.34 lol
Click to expand...
Click to collapse
If you see my sig below, I have tested the newer stock ROM (1.84).
I didn't feel or see any different from 1.34
That was the reason why I decided to downgrade and root it
The Virtuous custom ROM is version 1.85 and pre-rooted. Its mostly stock with a few extra features added and some optimizations. You should check it out, if you want a more up date, but close to stock ROM.
http://forum.xda-developers.com/showthread.php?t=837042
Hi everyone...I recently got a hold of a one X with CID ORANG001. Hboot 1.12 i think....i did my fair amount of googling but i am still unsure,are there any alternate roms available other than the stock orange one?i realized that it hasn't a 4.1.1 cid compatible firmware yet but can the stock rom be changed and how?
Thanks in advance...
Karolix21 said:
Hi everyone...I recently got a hold of a one X with CID ORANG001. Hboot 1.12 i think....i did my fair amount of googling but i am still unsure,are there any alternate roms available other than the stock orange one?i realized that it hasn't a 4.1.1 cid compatible firmware yet but can the stock rom be changed and how?
Thanks in advance...
Click to expand...
Click to collapse
Pretty much all ICS ROMs will work, which means the older versions of the ROMs located in Development section. Also, all CM10, AOSP, AOKP ROMs will work on older hboots. First you need to unlock the bootloader of your device. You can look around for more instructions.
Every ics + aosp+aokp+cm bassed roms
Sent from my Phone :-\
In order to get 4.1.1 update orange has to officially release it correct...?Does anyone have any news about when can we alter the CID and use international roms?
Karolix21 said:
In order to get 4.1.1 update orange has to officially release it correct...?Does anyone have any news about when can we alter the CID and use international roms?
Click to expand...
Click to collapse
Correct.
For changing cid we need s-off which doesn't seem to be achieved any time soon.
Sent from my HTC One X
Hello,
Since i don't have 10 posts yet and can't post this in the original thread i'm asking it here.
I'm using the Domination CM10 ROM and i'm on hboot version 0.94.
Should i upgrade to another version or is it wise to stay?
And if i should upgrade, what are the best steps to take?
I know how to flash roms and boot, however i'm not sure how to upgrade hboot.
Thanks
Stay. Support for JB HBoots is sketchy until the JB kernel source code is released.
BenPope said:
Stay. Support for JB HBoots is sketchy until the JB kernel source code is released.
Click to expand...
Click to collapse
+1, Yes don't update, updating will cause nothing but harm for a non-sense rom.
Hi there,
lately there have been OTA updates for CID HTC__023 and TELNZ001 which brought a new base (3.17) and some troubles (touch not responding) when using old (3.14) based custom roms.
The OTA brought a hboot update including an update to the touchscreen controller and therefore it only works correctly when using the corresponding 3.17 base kernel.
As slowly various CIDs are getting OTA updates to new base with new touchscreen controller firmware, these devices will have touchscreen issues on 3.14 based roms. But this kernel will help those people out.
adamnz had the initial idea in the thread linked above to try the 3.17 kernel on a 3.14 rom, so I followed up and created a flashable zip with all neccessary modules for those who are stuck with stock HTC ROM atm.
As I am running sense based RD-MIUI, I created a MIUI compatible boot.img, too which incorporates some ramdisk tweaks as init.d-support (busybox run-parts), volume-wake-deep-sleep-fix and run shelld service to prevent MiuiHome FCs.
03.02.2013: Base 3.17.781.2 (CID TELNZ001)
Grab the flashable zip from here: endeavoru_base_3.17.781.2_kernel.zip
Thx to adamnz for providing the OTA file and yumcimil for a full nandroid backup. :highfive:
Base 3.17.728.1 (CID HTC__023)
Grab the flashable zip from here: endeavoru_base_3.17.728.1_kernel.zip
Infos on different boot images
boot.img is the fully untouched 3.17 stock kernel while boot_miui.img has some tweaks as described above.
As the tweaks in boot_miui.img should have no drawbacks when used with non-miui-rom (and users reported that the stock one does not work but the miui one does),
boot_miui.img is the prefered kernel even when not running MIUI (if you do not want to repack).
Repacking
As JB sense roms around use the HTC stock kernel, which ramdisk is quite the same compared to this kernel, you can easily repack this kernel with the one from your favourite ROM. Please use the boot.img for this instead of boot_miui.img and do not forget to flash the zip file with the modules. This way you get all the rom-specific features and tweaks the rom chef included in his ramdisk.
Installation
Make a nandroid before, flash zip from recovery, flash boot.img from within the zip via fastboot, wipe cache and reboot.
Re: [KERNEL][Base 3.17.728.1] HTC JB Stock & MIUI
Thanks for this!
Sent from my One X running Blade v4.6.0. At a mere 240 MB, with tons of AROMA Mods and tweaks, this, is what you want.
Confirmed working with ViperX 3.3.2 using boot_miui.img, on HTC__023.
Touch works
cheers
Working with insert coin 15.1.1 with vid HTC_001!!
fantastic!
Works very well with Blade v4.6.0 (de-sensed) on HTC__023. Battery drain is less than 0.5% per hour in deep sleep.
[KERNEL][Base 3.17.728.1] HTC JB Stock & MIUI
marcosorano said:
Working with insert coin 15.1.1 with vid HTC_001!!
Click to expand...
Click to collapse
Yeah, this kernel works with all CIDs, but there are no real improvements. At least I did not notice any.
But for those with CID 023 and latest OTA update (3.17) this kernel allows them to use 3.14 based roms again. :good:
@all
Thanks for trying this one out and reporting back. Really much appreciated.
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
nevermore6990 said:
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
Click to expand...
Click to collapse
You would need to unlock your bootloader via htcdev, flash custom recovery and then flash the kernel zip in recovery and the kernel image in bootloader with fastboot.
nevermore6990 said:
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
Click to expand...
Click to collapse
What CID do you have?
The offical 3.17 base update only rolled out for CID HTC_023 atm. As this update brought something new to the touchscreen controller, this 3.17 kernel is needed to run 3.14 based roms.
If you have a CID different from HTC_023 (OR did not yet installed the official 3.17 OTA), running this kernel will not change anything regarding to your problem. But of course you can try, it will not cause any harm. Just follow the instructions in OP.
EDIT: Just overread the STOCK in your post. Need to grab a cup of coffee.
But gffmac is right: Just need to mention that unlocking the bootloader will wipe your /data-Partition (userdata).
nevermore6990 said:
hi, i have touchscreen problems. part of my touchscreen not working. but im on 3.14.720 stock rom. and i didn't get the update yet. i want to try this flashable zip. what should i do? does the update fix touchscreen problems?
Click to expand...
Click to collapse
It's unlikely to fix a touchscreen problem that was present on a stock rom especially if you haven't unlocked it previously. You maybe have a hardware problem with it
JohnnyInBriz said:
It's unlikely to fix a touchscreen problem that was present on a stock rom especially if you haven't unlocked it previously. You maybe have a hardware problem with it
Click to expand...
Click to collapse
Absolutely... Did not even think about that...
REALLY need to grab a cup of coffee. Now! :silly:
hi man!
can i use this kernel on my HOX?
ROM:Nocturnal JellySense+ v5.0 (3.14)
CID: HTC_044
thanks for reply
mrberni said:
Yeah, this kernel works with all CIDs, but there are no real improvements. At least I did not notice any.
But for those with CID 023 and latest OTA update (3.17) this kernel allows them to use 3.14 based roms again. :good:
@all
Thanks for trying this one out and reporting back. Really much appreciated.
Click to expand...
Click to collapse
With the stock kerneli ave some touchscreen problem when connected to usb now with your kernel it's solved
omer_hyltz said:
hi man!
can i use this kernel on my HOX?
ROM:Nocturnal JellySense+ v5.0 (3.14)
CID: HTC_044
thanks for reply
Click to expand...
Click to collapse
This kernel should work with every jb sense based rom.
marcosorano said:
With the stock kerneli ave some touchscreen problem when connected to usb now with your kernel it's solved
Click to expand...
Click to collapse
Really glad to hear that it helped you out. :highfive:
can this be worked on h boot unsupported version too or its just for the people who are already updated their h boot ??
Nani2000 said:
can this be worked on h boot unsupported version too or its just for the people who are already updated their h boot ??
Click to expand...
Click to collapse
Of course you need a jb compatible hboot the run this kernel.
Working fine on Venom ViperX JB 3.3.2
CID: H3G__001
HBOOT: 1.39
What's battery life using this on Viper like compared to Skydragon?
I was hoping to upgrade my firmware(3.32.531.2) to the newest version(4.16.401.10). My baseline nand back up is the original htc tmobile 4.4.4 rom after it was boot loader unlocked, rooted, and s-offed, but nothing else.
If I upgrade to the latest and greatest firmware will that rom still run, or can that only work with android 5.x?
Basically I wanted to upgrade the firmware, make sure that all works, then move to a 5.x rom. I've tested a few 5.x roms and they worked with the older firmware, but I was curious if people knew if it worked the other way?
Thanks!
Device:
Tmo 4.4.4 m8
current firmware 3.32.531.2
Mostly stock - unlocked bootloader, rooted, and s-offed. Still on original htc image
Sartan4455 said:
I was hoping to upgrade my firmware(3.32.531.2) to the newest version(4.16.401.10). My baseline nand back up is the original htc tmobile 4.4.4 rom after it was boot loader unlocked, rooted, and s-offed, but nothing else.
If I upgrade to the latest and greatest firmware will that rom still run, or can that only work with android 5.x?
Basically I wanted to upgrade the firmware, make sure that all works, then move to a 5.x rom. I've tested a few 5.x roms and they worked with the older firmware, but I was curious if people knew if it worked the other way?
Thanks!
Device:
Tmo 4.4.4 m8
current firmware 3.32.531.2
Mostly stock - unlocked bootloader, rooted, and s-offed. Still on original htc image
Click to expand...
Click to collapse
It does work the other way, better than old firmware and new ROM. With old FW and a newer ROM, you will possibly have data connection issues, particularly WiFi.
xunholyx said:
It does work the other way, better than old firmware and new ROM. With old FW and a newer ROM, you will possibly have data connection issues, particularly WiFi.
Click to expand...
Click to collapse
So to be clear: old firmware and new rom works(and I've tried it) but may have issues(I had lte issues but was fine with wifi) but also new firmware old rom shouldn't cause real issues(aka unbootable)? When I was doing this with my old htc sensation sometimes that wasn't the case(but this was back in the good old gingerbread days). New rom(ics) and old firmware was bad news.
If something goes wrong, I want to be able to roll back to my working nand back up of 4.4.4, but if the firmware doesn't allow it, I could have some serious issues.
Sartan4455 said:
So to be clear: old firmware and new rom works(and I've tried it) but may have issues(I had lte issues but was fine with wifi) but also new firmware old rom shouldn't cause real issues(aka unbootable)? When I was doing this with my old htc sensation sometimes that wasn't the case(but this was back in the good old gingerbread days). New rom(ics) and old firmware was bad news.
If something goes wrong, I want to be able to roll back to my working nand back up of 4.4.4, but if the firmware doesn't allow it, I could have some serious issues.
Click to expand...
Click to collapse
Yeah, don't worry. I had 4.16.401.10 on a 4.4.4 ROM for a month or more.
xunholyx said:
Yeah, don't worry. I had 4.16.401.10 on a 4.4.4 ROM for a month or more.
Click to expand...
Click to collapse
Great That's what I wanted to know! I had to wait months to s-off..(sunshine 3.x+) after having free reign with my sensation. I'm just so excited!
Nice to know.
And what about Xposed? If i don't get wrong, it doesn't work on Lollipop because Lollipop is ART-based.
So it should not be any way related to firmware, meaning that I could have the latest firmware (able to support a Lollipop ROM), a Kitkat based ROM AND working Xposed.
Could it be?
xunholyx said:
Yeah, don't worry. I had 4.16.401.10 on a 4.4.4 ROM for a month or more.
Click to expand...
Click to collapse
It worked just fine. Rocking 4.16.401.10 and skydragon 4.2.5 for now! Much thanks!
sbiricuda said:
Nice to know.
And what about Xposed? If i don't get wrong, it doesn't work on Lollipop because Lollipop is ART-based.
So it should not be any way related to firmware, meaning that I could have the latest firmware (able to support a Lollipop ROM), a Kitkat based ROM AND working Xposed.
Could it be?
Click to expand...
Click to collapse
I don't use Xposed, but I believe it will work fine with new firmware as long as you are still on a 4.4.4 base. Xposed modifies /system which is part of the ROM.
Sartan4455 said:
It worked just fine. Rocking 4.16.401.10 and skydragon 4.2.5 for now! Much thanks!
Click to expand...
Click to collapse
How's it going on so far? Still fine?
sbiricuda said:
How's it going on so far? Still fine?
Click to expand...
Click to collapse
Oh yah. Going great. I've settled on LeeDroid as my daily driver, but want a gpe/aosp version that works better in the end. CM12, Blisspop, skydragon(and I've tried others) have all had an issue or two for me that pulled me back to leedroid's. I've not wanted to make the switch to full GPE conversion yet, but maybe one day...