I was wondering, im on viperXL rom and was curious to know if i have to flash a boot.img when using AOKP
Sent from from the forrest moon of Endor
if you are s-on then yes if s-off depends if the dev has scripting in his rom to flash the boot.img then you dont. just fastboot flash the boot .img to be safe it took longer to make this post than to flash it
If you are not s-off I recommend you do so. It is simple to do and well worth it.
Sent from my HTC One X using xda premium
Flash gui should work then right? (My computer is down)
Sent from from the forrest moon of Endor
it should
Related
Hey guys. Noob question and all but i've only had this phone on a custom rom for an hour.
Is the boot.img image compatible with any ROM? As in does each one need a different boot.img file or could i just keep one copy?
Thanks.
Huzi.
If you're unlocked through htcdev then you'll need to flash boot image each time you flash a new ROM, some roms may well work with others boot image, but I wouldn't recommend it.
Each ROM well need its own boot image, which you'll have to extract from ROM and flash separately
Swyped from my Desire S using XDA Premium
ben_pyett said:
If you're unlocked through htcdev then you'll need to flash boot image each time you flash a new ROM, some roms may well work with others boot image, but I wouldn't recommend it.
Each ROM well need its own boot image, which you'll have to extract from ROM and flash separately
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
So if I use say unrevoked and revolutionary I won't have to keep flashing the boot.img file through adb?
Sent from my HTC Desire Saga using XDA
True, they would give you true s off in which case you don't need to bother with separately flashing boot image, but whether you can use that method depends on which version of hboot your device has
Swyped from my Desire S using XDA Premium
ben_pyett said:
True, they would give you true s off in which case you don't need to bother with separately flashing boot image, but whether you can use that method depends on which version of hboot your device has
Swyped from my Desire S using XDA Premium
Click to expand...
Click to collapse
Well I have hboot version 2.00.0002 which I just found out does not support revolutionary. I need to downgrade to 0.98 first. Thanks for clarifying that.
Sent from my HTC Desire Saga using XDA
What am I able to do with those in terms of roms and kernels?
doesn't matter for ROMs, but kernels and radios can't be flashed through recovery on that hboot.
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
To save you from doing that, you can downgrade your hboot and then RUU downgrade to 1.85 so you can flash a radio. Go to the eMMC JET tool in the android dev forum if you want to downgrade your hboot.
Sent from my One X using xda app-developers app
Myrder said:
Cid just means you're rooted. Your hboot means you can flash kernels and ROMs with an extra step. You'll have to fastboot flash the boot.img then install the .zip from twrp.
Click to expand...
Click to collapse
I've had a good amount of luck with Aroma installers taking care of the boot.img flashing for me. Between CleanRom and BeastKernel, I only had to flash the zips from twrp.
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
The easiest thing to do would be to s-off. Then you can flash whatever you want.
Sent from my HTC One X using xda premium
You shouldn't need to update your hboot to run cm10 but I'd be lying if I said I hadn't encountered people with phones that wouldn't boot cm10 unless they updated to the 2.14 HBOOT.
Bear in mind on the 1.14 hboot, you need to extract the boot.img from the rom and flash it using fastboot before most roms will boot. If it still doesn't boot or you don't like the idea of flashing boot.img separately every time you flash a rom then yes I would agree to S-OFF and use the 3.18 ruu.
Sent from my One X using xda app-developers app
ratsack said:
Instead of creating a new thread, I thought I'd just bump this one.
Anyway, just bought a used AT&T HTC One XL and it has CID: 11111111 and S-ON. I need to update my HBOOT so I can run CM10. I just want to know what exact firmware/HBOOT to use so I can use the phone.
Thanks in advance!
Click to expand...
Click to collapse
Thank you for not creating a new thread. Let everyone else said, it would be wise to do s off while you are this far.
Sent from my Carbon-ize Evita using xda-developers app
I think it is my old HBoot as it's doing the same thing my wife's HTC One X did the other day when I tried to put CM10 on it. Updating HBoot fixed that.
I can't boot into Android as it isn't working. Is there a way to S-Off (that's easy) where I don't need to boot into Android? All I really want is to update HBoot and I'll be happy.
---------- Post added at 01:44 AM ---------- Previous post was at 12:48 AM ----------
Well, I think the issue was I that I wasn't using the correct recovery to flash the CM10 & GApps. Was using the recovery for a One X, not XL. Put the correct recovery on and now I'm typing this message on my phone. Yay!
Thanks for the help peoples! Now to find out how to remove the red text on start-up!
Sent from my One X using Tapatalk 2
Do i need to flash the boot.img from the kernel from fastboot before installing the kernel from recovery? Or if this is completely wrong and im crazy, could someone correct me
Many thanks!
Depends on your Hboot. I'd downgrade it if yours is 1.14 or higher
Sent from my One X using xda premium
Hi All,
I am fairly new to all this, I have read countless posts and done everything I can but I am stuck.
I have a HBOOT 2.14 currently with S-ON.
I have installed TWRP in recovery but no custom mods work due to the HBOOT version.
SuperCID is 111111111 and is already set.
I want to be able to S-OFF my device so i can downgrade the HBOOT and use the custom roms.
I ran through the facepalm S-OFF procedure, it all runs correctly, although upon reboot it still says S-ON.
Does anyone know why this would be? Is there something I am missing?
I am doing this some the TWRP recovery mode as that is the only place I can access adb commands currently.
There is no working ROM currently installed, CM 10.1 is installed although it can't be used because the touchscreen doesn't work.
Any information people can provide me to get all this working would be of great help.
Happy to donate/pay someone to help me via teamviewer or whatever.
Thanks,
Tabmowtez
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Venomtester said:
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
v2.4.4.0
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Venomtester said:
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Really? I haven't seen this said anywhere? Do you have any references to the procedures or the TP firmware?
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Venomtester said:
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes that's the one I posted, it still requires S-OFF.
It seems all the fixes need S-OFF and that is the one thing I can't seem to get working as there is no ROM installed so I can't use supersu?
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Venomtester said:
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I will download ViperX3.4.0.zip and use the boot.img to flash it from adb and see how it goes.
I have tried AOSP and CM Roms and all have had the same issue of the TP not working though.
I'll see how this goes.
Just to confirm, it seems all ROMS based off of the 3.17 kernel and higher work with S-ON.
I have the HatkaXL-evita-v4.2.5_Sense5Elements ROM working after I did the following steps:
Place boot.img in sdk platform tools folder
Boot phone into fastboot usb
open your command prompt from the sdk files folder. (shift+right click-select open command window)
type: fastboot erase cache
type: fastboot flash boot boot.img
type: fastboot erase cache (just to be safe)
On phone select bootloader, then recovery.
Once TWRP loads (I'm using 2.4.4.0) go to wipe and select factory reset then wipe system and both caches
Then install the rom and go through setup
once setup is complete, UNCHECK restart now so it leaves the rom and goes back to TWRP.
Click on clear cache/davlik and then click reboot
Settings application keeps on crashing so I am going to try the aokp_evita_jb-mr1_build-4 ROM now after a backup.
I still have issues getting adb to recognise the device once the ROM is booted but that's a separate issue for now...
Are you sure your getting error 92 and not 99 when you flash the zip for s-off cause if your getting 99 you need to fastboot write your cid then reboot and try again
Sent from my One X using Xparent Green Tapatalk 2
I'm definitely getting the error 92. My CID is already a SuperCID so would I have to do that again?
I have the ViperX ROM running now so I am happy, would still like to S-OFF though so I can try CM etc. after a hboot downgrade.
Sent from my HTC One X using xda app-developers app
When I did the s-off to my One XL, the error 92 is normal and I just followed the steps in this thread and it worked fine
http://forum.xda-developers.com/showthread.php?t=2155071
That is the same thread I follow, I will try again now that I have a working ROM and see how it goes.
Sent from my HTC One X using xda app-developers app
All good, I successfully S-OFF'd my device and downgraded my hboot to 1.09. Hopefully this means I can put any mod on now without flashing from fastboot first and having the touchscreen work!
Sent from my HTC One X using xda app-developers app
Hello all. I got my One S from a guy that didn't want it anymore. It came rooted and flashed with CM10.1. I've gone into fastboot and it says I'm unlocked, s-off, and on hboot 1.14. My question is if this means that to change ROMs all I do is wipe/clear and flash. Or do I have to flash GUI or boot.img every time. I use to have a LG P509, but this seems to be much more complex than that device's flashing.
Thanks
Sent from my One S using xda app-developers app
kkevin94 said:
Hello all. I got my One S from a guy that didn't want it anymore. It came rooted and flashed with CM10.1. I've gone into fastboot and it says I'm unlocked, s-off, and on hboot 1.14. My question is if this means that to change ROMs all I do is wipe/clear and flash. Or do I have to flash GUI or boot.img every time. I use to have a LG P509, but this seems to be much more complex than that device's flashing.
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Yeah all you have to do is wipe and then flash.
S-on means your security is on and HTC semi locks your boot loader so you need to flash the boot.IMG via fastboot or the GUI to bypass htcs stupid bootloader limitations, being as the ville/one s now has s-off (as your phone is) you don't need to flash the boot.IMG after flashing the rom. I hope this helps you understand a little more.
Sent from my One S using xda premium