Database Info

[Q] Whats next?

So I tried to root my phone awhile back and just ran out of time. Ive using the phone as is since but its time I finish what I started. Right now in the bootloader I have the 2 little bars on the top one saying tampered the other saying unlocked. It still says S-on(which where Im a little unsure of). I can boot into recovery without an issue from the bootloader. So i guess my question am i ready to install a custom rom or is there more i need to do before i do that?

Cbaird said:
So I tried to root my phone awhile back and just ran out of time. Ive using the phone as is since but its time I finish what I started. Right now in the bootloader I have the 2 little bars on the top one saying tampered the other saying unlocked. It still says S-on(which where Im a little unsure of). I can boot into recovery without an issue from the bootloader. So i guess my question am i ready to install a custom rom or is there more i need to do before i do that?
Click to expand...
Click to collapse
Yes, you can install an ROM you wish, but depending on hboot you may have to flash the boot.img in fastboot. There is an easy method of getting stuff in the original android development section of this phones forum, so do that and you won't have to work. Happy flashing

Original android dev section is lame. S-off your device, then flash CleanROM JB beta and ElementalX vanilla. You won't be disappointed.
Sent from my HTC One X using xda premium

S-OFF your device first this is all most noob proof just follow the instructions to the T. Then you wont have to flash the boot.img every time you flash a new rom in recovery, if you're on Hboot 1.14 and up. If you're on Hboot 2.14 I believe all 4.2 AOSP roms touch screens don't work, not sure though I know that cm10.1 doesn't for sure, but you can easily downgrade your Hboot to make it work after you've S-OFF'ed your phone or downgrade your touch panels firmware, again after your S-OFF .
S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Downgrade HBOOT: http://forum.xda-developers.com/showthread.php?t=2156686 or http://forum.xda-developers.com/showthread.php?t=2156368
Downgrade touch panel: http://forum.xda-developers.com/showthread.php?t=2159863

ECEXCURSION said:
Original android dev section is lame. S-off your device, then flash CleanROM JB beta and ElementalX vanilla. You won't be disappointed.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lame. Lol.
Its all a matter of opinion, in your opinion it is lame..
Android Dev section - anything not built from source (usually sense Roms)
Original Dev section - anything built from source (aosp based, such as cyanogenmod)
Sent from my Google Nexus 4

mirGantrophy said:
Lame. Lol.
Its all a matter of opinion, in your opinion it is lame..
Android Dev section - anything not built from source (usually sense Roms)
Original Dev section - anything built from source (aosp based, such as cyanogenmod)
Sent from my Google Nexus 4
Click to expand...
Click to collapse
Why aren't sense kernels in original development? I could be wrong but aren't they built from source

a box of kittens said:
Why aren't sense kernels in original development? I could be wrong but aren't they built from source
Click to expand...
Click to collapse
To prevent confusion
Sent from my Nexus 4 using xda app-developers app

Wubbz said:
S-OFF your device first this is all most noob proof just follow the instructions to the T. Then you wont have to flash the boot.img every time you flash a new rom in recovery, if you're on Hboot 1.14 and up. If you're on Hboot 2.14 I believe all 4.2 AOSP roms touch screens don't work, not sure though I know that cm10.1 doesn't for sure, but you can easily downgrade your Hboot to make it work after you've S-OFF'ed your phone or downgrade your touch panels firmware, again after your S-OFF .
S-OFF: http://forum.xda-developers.com/showthread.php?t=2155071
Downgrade HBOOT: http://forum.xda-developers.com/showthread.php?t=2156686 or http://forum.xda-developers.com/showthread.php?t=2156368
Downgrade touch panel: http://forum.xda-developers.com/showthread.php?t=2159863
Click to expand...
Click to collapse
I flashed a rom through recovery and had no issues with having to flash the boot.img.(but maybe that was done before and i just dont remember) I also just checked my Hboot and its at 1.11. So would you recommend i do this still or not?

Cbaird said:
I flashed a rom through recovery and had no issues with having to flash the boot.img.(but maybe that was done before and i just dont remember) I also just checked my Hboot and its at 1.11. So would you recommend i do this still or not?
Click to expand...
Click to collapse
Since your on a Hboot lower than 1.14 you shouldn't have to downgrade anything, Hboots or the touchscreen firmware, But I would still recommend doing the S-OFF still. If you do, read through the instruction before you start then give it a go. Once your device is S-OFF you can downgrade or upgrade to any Hboot or change to what ever Radio you wish and no more flashing boot.img on Hboots 1.14 and up.
TIP for S-OFF I was getting error 99 with cm10.1 so i had to backup and wipe my phone and goto Viper XL 3.2.3 and then restore my cm10.1 rom from trwp recovery, there is a post about this in the S-OFF thread it might be in the OP now not sure though.
Also if you move to a 4.2.X based rom from 4.1.X or lower you will probably need to upgrade your adb folder if you haven't made it with googles newest build

[Q] HBoot Question

Recently I rooted a friends One S just curious before I start flashing if I go from a sense rom to cyanogenmod or vice versa, Will I have to do anything with Hboot or can I switch between roms without any issues?

You can switch between roms , regardless of your Hboot. If you're on a higher Hboot after 1.09 I think then you have to fasboot flash the boot.IMG or use flash image GUI, even if you're restoring to a previous ROM. Doesn't matter if its cyanogenmod or a stock sense ROM. If you don't want to flash the boot.IMG then you can S-OFF http://forum.xda-developers.com/showthread.php?t=2155135
Sent from my Nexus 4 using xda app-developers app

Thanks, thats what I needed to know.

I got a question regarding this topic:
My brother's One S is still on HBoot 1.09 and currently running an ICS ROM.
If he want to install a JB ROM, does he need to change his HBoot or anything else?
Because with my One X, I had to upgrade HBoot to be able to install newer ROMs.

Yes, Hboot update is required to install JB
Sent from my HTC One X using xda app-developers app

zakvoline said:
Yes, Hboot update is required to install JB
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thank you, is there an easier way than going back to stock and updating via OTA?

don't get hboot's and boot images mixed up
you can flash jb or ics or whatever on .09 and most likely will not have to flash boot images separate. that usually occurs on .13 or higher
i have .06 and flash everything including radios
obviously can't change hboots without s-oo

[Q] HBOOT 2.15 killing me...

*** WHAT MY PROBLEM IS***
PLEASE can someone confirm any AOSP ROM that works with 2.15 HBOOT?
***WHAT I KNOW***
( i know the CM 10.2 thread says that RUU 3.18 which will make the hboot 2.14 but since 2.15 is latest i assume it should support)
(i also know that [HBOOT 2.15 is essential for SENSE 5 4.2.2 to run,i believe that's the only reason people go for 2.15)
***WHAT I HAVE TRIED***
NOW from what i have tried is that the 1st stable cm 10 release doesn't work with 2.15 (obviously too old build) my screen also became responsive(i believe that because of touch panel firmware) then with the latest stable release of cm 10.1 it specified that it needs hboot 2.14 and hence couldn't flash.
with PAC 4.3 it does gets installed but screen is unresponsive and infinite bootloops!:silly:
***WILL THIS WORK***
so now if i RUU 3.18 i will have to unlock boot loader and root it (M SOFF SUPER CID) which i m not really ready to do!
now there are methods that can help u downgrade/upgrade your firmware , can i do that?
also will using torched kernel help in me in any way?
***WHY DO I WANT AOSP***
Viper XL 4.2.2 best ROM ever hats off but the thing is i dont know why but i have Signal issues i tried flashing the recommended RADIO version.
since the vendor had already RUUd my device that was meant from some ASIAN region and already came with SENSE 5 and i dint mess up with it in any way still i had signal issues (which are unpredictable) i found by GSAM BATTERY monitor that around 30 to 40% of my battery is consumed by RADIO.
also the best signal is around -81db
i also had some issues with camera!
and then there is the numerous options i can have with AOSP.
****LASTLY CAN ANYONE HELP****
:angel:

Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.

I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL

954wrecker said:
He makes it hard to understand but he is S-ON so he is screwed at this point
Sent from my HTC One XL
Click to expand...
Click to collapse
no no no i am SOFF i know for sure!!!

exad said:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
Click to expand...
Click to collapse
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?

954wrecker said:
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
Click to expand...
Click to collapse
LOL u are right thanks!
its just that m kinda paranoid cause every day in the Help and Troubleshooting section there is some thread dats says BRICKED so always to be on the safer side!

Sonone said:
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
Click to expand...
Click to collapse
yes

exad said:
yes
Click to expand...
Click to collapse
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?

Sonone said:
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Click to expand...
Click to collapse
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.

exad said:
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
Click to expand...
Click to collapse
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.

redpoint73 said:
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
Click to expand...
Click to collapse
as always thank you...
since u recoomend thats the safest way i will try out that.
have to download the RUU 3.18!!!
*waiting*

[Q] Problems with Viper Rom

Hello,
i'm having a lot of trouble with the viper made rom ( http://forum.xda-developers.com/showthread.php?t=2667758). I'm new here, so i cannot post it there.
My problems began when i try to install the updates. I have installed the original rom version 3.0.0. i get the OTA message, but when i try to install it in recovery, the phone can't mount the sd card, and the installation doesn't continu. I tried to do it manually (using the download link i found in one of the posts) and that seemed to work.
Then i got another OTA notification, to upgrade to version 3.1.0, but when i tried to boot after the installation, i couldn't enter my sim pincode, and when i reboot, the phone keeps looping. I have to install the original rom twice (once with and one time without wiping) before the ROM boots normally.
What am i doing wrong?
i'm on Hboot 1.25 and radio:1.15.50.05.29
I'm S-on (RL)

It seems that viper made a fll rom, with the updates included.

Wrong Hboot?
Martin_Weterholt said:
Hello,
What am i doing wrong?
i'm on Hboot 1.25 and radio:1.15.50.05.29
I'm S-on (RL)
Click to expand...
Click to collapse
I'm not sure but i think it starts with your Hboot, maybe one of the older members can verify, but according to the rom it requires Hboot version 2.15 or 2.16.
I am in the process of updating my Hboot by downloading and flashing the RUU as well as achieving S-OFF status

fidodaj said:
I'm not sure but i think it starts with your Hboot, maybe one of the older members can verify, but according to the rom it requires Hboot version 2.15 or 2.16.
I am in the process of updating my Hboot by downloading and flashing the RUU as well as achieving S-OFF status
Click to expand...
Click to collapse
You need to update hboot first
2.15 is most compatible i suppose

LS.xD said:
You need to update hboot first
2.15 is most compatible i suppose
Click to expand...
Click to collapse
Question. Is there a way for me to upgrade the hboot without the ruu wiping everything? Or will I just have to make a backup. I plan to go s-off before upgrading the hboot.

fidodaj said:
Question. Is there a way for me to upgrade the hboot without the ruu wiping everything? Or will I just have to make a backup. I plan to go s-off before upgrading the hboot.
Click to expand...
Click to collapse
If you're S-OFF ist possible I think

No, you don't need to update the hboot. I am on 1.06 and Viper works fine...in fact any ROM works fine for me but that's another story. The updated firmware (2.13 or 2.15) is required only for Android 4.4.x KitKat due to a check present in the updater-script. There's no such check nor requirement for previous Android versions and Viper 3.x is based on Android 4.2.2
The problems first could come from not being S-Off...this makes impossible to flash the kernel from recovery so any OTA that has a kernel is not flashed properly. I remember that 3.1.0 has also a full ROM ZIP, maybe is good if you flash that one from recovery and flash the kernel after that in fastboot. Also it could matter the recovery you're using, I would recommend latest TWRP
Sent from nowhere over the air..

Rapier said:
No, you don't need to update the hboot. I am on 1.06 and Viper works fine...in fact any ROM works fine for me but that's another story. The updated firmware (2.13 or 2.15) is required only for Android 4.4.x KitKat due to a check present in the updater-script. There's no such check nor requirement for previous Android versions and Viper 3.x is based on Android 4.2.2
..
Click to expand...
Click to collapse
In the viper rom forum post it says ROM firmware required hboot 2.15/2.16.. Am I to j just ignore tha? Or is it that it is only required that hboot (2.15/2.16) if you are s-on and s-off can do whatever you like? Lol

You need hboot 2.16 for Radio 1.20
And to Flash hboot 2.16 you will need S-OFF
Sent from my loved HTC One S using (most time buggy) Tapatalk

LS.xD said:
You need hboot 2.16 for Radio 1.20
And to Flash hboot 2.16 you will need S-OFF
Sent from my loved HTC One S using (most time buggy) Tapatalk
Click to expand...
Click to collapse
Actually I'm on hboot 2.15 with Radio 1.20.XX
I know this doesn't help... just saying..
To contribute smth. To get the most out of the Viper 3 Rom, everyone should upgrade their Radio to 1.20.XX. And this is actually why you need to S-OFF.

Hboot

Hey guys I've looked around and I just can't seem to find what I'm looking for, does the hboot version matter? I am on 1.14, but the phone is still s-on , I would like to flash 4.4 roms but I wanted to know if I should ruu to the newer hboot and start from there.
Thanks
Sent from my HTC One S using xda app-developers app

Silentwidow said:
Hey guys I've looked around and I just can't seem to find what I'm looking for, does the hboot version matter? I am on 1.14, but the phone is still s-on , I would like to flash 4.4 roms but I wanted to know if I should ruu to the newer hboot and start from there.
Thanks
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Most of roms are usable on 2.15 hboot and lower (which comes with last ruu), so why not give it a try with your actual hboot ?
I would say you to update your hboot but since it wipes sdcard it's quite annoying
What you can do is make a backup and then try the rom you want, if you notice any issue, restore your backup or update through latest ruu.
For some reasons you'll probably need to manually update the radio to 1.20 or 1.35 (I don't recommend this last one since I had random reboots with it), but you need to s-off. I you do, I advise you to use rumrunner.

benJX said:
Most of roms are usable on 2.15 hboot and lower (which comes with last ruu), so why not give it a try with your actual hboot ?
I would say you to update your hboot but since it wipes sdcard it's quite annoying
What you can do is make a backup and then try the rom you want, if you notice any issue, restore your backup or update through latest ruu.
For some reasons you'll probably need to manually update the radio to 1.20 or 1.35 (I don't recommend this last one since I had random reboots with it), but you need to s-off. I you do, I advise you to use rumrunner.
Click to expand...
Click to collapse
If he's on 1.14 he can't flash a KK ROM unless he's not modifying the updater-script in the ROM zip. The check there gives an error if someone tries to flash a KK ROM on a hboot other than 2.13.0000, 2.13.4444 or 2.15.0000

Rapier said:
If he's on 1.14 he can't flash a KK ROM unless he's not modifying the updater-script in the ROM zip. The check there gives an error if someone tries to flash a KK ROM on a hboot other than 2.13.0000, 2.13.4444 or 2.15.0000
Click to expand...
Click to collapse
Yes on Vanir AOSP I had to do this to make it flashable on 2.16 (btw thx for your guide )
Sent from my ElementalXed One S