Database Develop

[Q] HBOOT 1.16.0000, known ROMs to work?

So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
Hyun is looking for you at revolutionary irc channel.
Sent from my HTC Incredible S using Tapatalk

I know.. I have spoken to him.

jakeyo said:
I know.. I have spoken to him.
Click to expand...
Click to collapse
Any luck? still unable to flash anything?

jakeyo said:
So far I've had no luck using custom ROMs as it just stays on the htc boot screen and does not work. I can confirm that 'MiUi' does work on my phone - however it is buggy and I don't like it.
I want cyanogenod or either android revolution HD but none of these work.
I thinkit has something to do with the HBOOT being 1.16.000, and the ROM version i'm after is 2.34.981.1 (virgin or optus branded) - am with virgin though in Australia.
I have a custom bootloader/recovery whatever you call it, I wipe the cache, dalvik cache and factory wipe, before installing all ROM's. I can't update to stock ROM either because there is none for hboot 1.16.000
So right now my phone is pretty much a paper weight until I can get it working again.
I prefer custom ROM's if there is any that work, if not I atleast want the stock ROM to work for now so I can use my phone. If someone can help me through the process to get it working it would be greatly appreciated. Thanks.
Click to expand...
Click to collapse
If you go to the development section of the HTC Incredible 2 forum, attn1 has a script tool that uses the latest Revolutionary/Unreovked exploit to downgrade the ROMand HBOOT to a version that is supported by Revolutionary.
If you look at the script, it is pretty simple. You would just need to use an older Virgin Mobile RUU.zip instead of the Inc2 version. It looks like the 2.12.981.2 would be the one to try.

Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?

Doesnt matter if you need S-ON or S-OFF, as long as you get permissions to access root files.
Someone installed a custom bootloader so I can install custom ROM's, and it just works.... apparently the radios are locked though.
So, another day gone by and my phone is still not working. I can use MiUi, but I ran out of data on my 3g sim and wifi doesnt work, so now I have no internet on it.

katu2006 said:
Hang on a second, how did you S-off the Hboot 1.16?
I thought you need S-off to be able to flash a custom Rom...
How did you install Miui?
Am I missing something here?
Click to expand...
Click to collapse
I'm pretty sure no soff will cause the issues he is experiencing, though he doesn't seem to be listening

no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
Yes im a noob that has been using android since 2009..
You seem like a supreme douche.
Weren't you the one who was crying about wanting to go back to his iphone lol

jakeyo said:
no, you're all just noobs.
It was the boot.img, we swapped it with the MiUi then put back the original one, now it boots up on cyanogenmod7.1 and works completely fine.
Can access root files, can take screenshots, everything is normal.
and I have s-on.
Click to expand...
Click to collapse
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?

katu2006 said:
You're calling us noobs, but you don't even know what was done on your phone...
What's the following sentence supposed to say?
"It was the boot.img, we swapped it with the MiUi then put back the original one"
To get a custom Rom, you actually have to INSTALL it...To get the custom Rom installed, you need CWM recovery. But if you have HBoot 1.16.000, you can't have a custom recovery yet.
In less your "friend" did a downgrade of the HBoot to 1.13.000, it's unlikely that you have CWM recovery on your phone. Even so, to my knowledge HBoot 1.16.000 does a version check and won't let you downgrade it.
So, the question remains, how did you get CWM recovery on your phone?
Click to expand...
Click to collapse
This thread is awesome

no, if I hold down power down and power button I see S-ON and HBOOT 1.16.0000
He typed in commands to give it root permissions, not sure exactly as he remote controlled my computer and typed it in. Then yes, he flashes CWM onto the phone then I installed revolutionary.
Firstly, I went onto the HTC dev site (created an account) and followed the steps to unlock the bootloader. In the end, it was successful, and once it's finished it will wipe the phone (AND WILL STILL SAY s-on)
So then the bootloader is now unlocked, and he did various commands in fastboot. My guess is that he installed CWM from there and it just worked.
at first, cyanogenmod would not boot, so he copied the (boot.img that is working) from MiUi and repled it with cyanogenmod's. The phone booted up and worked. Then he put it back how it was and it now works. Strange, but something must've given it a kick.
I'll repeat myself.
HBOOT 1.16.0000
S-ON
Cyanogenmod &.1 (stable)
Full root access
Need I say more to prove it?
As far as I know, I just cannot flash radios, which actually require the S-OFF....
sorry if I come across as rude, just a long day..

Talk to aftab565 he has the same hboot as you and has arhd running. Sounds like your phone was temp rooted and flashed and I would advise against letting people you don't know take remote access of your pc.

Hopefully it works for him I couldn't help.

Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Didn't take my eyes off the screen either.

jakeyo said:
Just replied to his thread.
And I know I was aware. I had full control though (could press a certain key to disconnect the connection - and only gave a temporary password) He was only typing in CMD things to do with the phone that I've heard of before
(ADB shell, fastboot recovery etc) and in the end worked well. He said my job is done and disconnect himself, so good guy
Click to expand...
Click to collapse
You gotta give props to these guys for donating their time. Every day there's more talk about h-boot 1.16.0000 so I figure if devs want to keep devin there'll be a rev released eventually.

I really appreciate the amount of work hes done, in total I recon he's spent about 6 hours trying to help me getting it to work.
Never left me by myself, he always helped me through every step and was always there if I needed help. I've now got CM7 thanks to him. If he didn't fix it, I would have a useless phone because I couldn't even put on the stock ROM because of my HBOOT im guessing (I did an OTA update to get 1.16.0000 therefore too new to download)
I think SOME of the custom roms do have support for 1.16.0000 and what you only need is the boot file from them to boot up your non-booting ROM then you're all good.

ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
2a. You don't need any existing root method to exist, there is no exploit involved in any of this, this will work irrespective of the current status of a root expoit existing or not.
2b. The phone does not have to be listed by HTC as being supproted. Any phone with a suitable hboot can be unlocked.
if this:
Code:
fastboot oem get_identifier_token
returns an identifier code then the phone can be ulocked.

globatron said:
ok, just to put some closure and sanity on this thread.
Firstly I'm probably bettery know as hyuh on #revolutionary, and it was me who was connected to his PC.
I use teamviewer to connect to people remotely, this allows anyone who doesn't like the look of *anything* I do to diconnect me...The user in front of the PC has full control of my session and I remind them to close teamviewer after we're done.
Secondly to those who think you need to be S-OFF to install a custom ROM or custom recovery, this is simply not true in the case of the 1.16 hboot. If you follow the HTC unlock procedure then you will have sufficient access to the phone to do this, it is not S-OFF just an unlock. Your phone will be in state "S-ON unlocked" This allows certain partitions on the emmc to be written to, and this sufficient for custom ROMs.
Really all that is requird is:
Code:
fastboot flash recovery <recovery.img>
then follow the normal flashing procedures.
In jakeyo's case CM7 would not boot, but MIUI would. When I say it would not boot I do not mean a boot loop here, I mean no boot period. At this point I had expected to need to rebuild a boot image for CM7 for him suspecting that HTC had done something different in the new hboot with paritions or the boot image offset.
The reason for flashing the MIUI boot image on top of CM7 was simple, to get to adb in the boot image. However seeing nothing particularly strange in the boot sequence ( other than the mismatch and resulting bootloop) I decided to reflash the CM7 boot image through fastboot.
The phone booted fully this time without issues.
It appears that the boot image simply did not flash properly from recovery the first time but I don't have a vivo to troubleshoot further.
A couple of things:
1. Don't take the OTA for 1.16 hboot if you haven't already done so.
There is currently no unofficial unlock/S-OFF
There is no RUU to fix the phone if you screw up.
There is nothing in the OTA you can't get in other ways.
2. If you're on 1.16 and want custom ROMs and aren't worried about warranty, go ahead and do unlock from HTC, but bear in mind:
There is no RUU, so you can't go back to stock
You can't flash radios
You can't superCID or similar ( but not needed since there is no RUU )
Click to expand...
Click to collapse
Get a mod to make a hboot sticky there will be floods of this crap further down the road.

[Q] Update to ICS from rooted phone

I have my HTC Vivid rooted and on HoliRaider v1.6. I really wanted to use the rom Rum Float Beta, which is ics. I tried to find the steps for updating to this but i get kinda confused... If anyone could help me that would be great!

Taken from a similar thread...........
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....

The thing that is getting me is how I have to Lock the bootloader again. Do I just lock it through the htc unlock tool? How do I " run PH39IMG install"? After, do i follow the same steps that i did before to root my phone?

To relock bootloader:
fastboot oem lock
To Unlock bootloader:
fastboot flash unlocktoken Unlock_code.bin
The PH39IMG file needs to be on the root of your SD card. Boot into hboot and it will automatically find the the PH39IMG file and update. I hope this helps. Like you said it's almost exact same steps you did to root assuming you didn't use the supertool or one click method.

Kent Melton said:
The thing that is getting me is how I have to Lock the bootloader again. Do I just lock it through the htc unlock tool? How do I " run PH39IMG install"? After, do i follow the same steps that i did before to root my phone?
Click to expand...
Click to collapse
Fastboot OEM lock. This is done from the fastboot screen. This is covered in the superguide and mentioned several times throughout these forums.
Sent from my SGH-I777

strose after putting the ruu on a stock vivid, which boot.img file are you going to look for and recovery img file? this is where i get a little confused?
strose09 said:
Taken from a similar thread...........
the RUU or the methods that thecubed and i have laid out will get you the necessary HBOOT/RADIO/etc that you will need to flash a custom ICS rom
either method will get you the same thing....an updated HBOOT and ICS
if you run the bootloader unlock tool from htcdev, YOU WILL LOSE ALL YOUR SETTINGS! it will wipe the device like its brand new......do NOT include this in your dreams of getting backups prior to flashing a custom rom....
please just read through the posts and understand what is going on.
in order for ICS to happen on your vivid you need the new HBOOT, Radio, and various other components that the RUU/PH39IMG contain
there are 3 different roads you can follow to get there, the EASIEST being just run the RUU (WHICH WILL ALSO WIPE SETTINGS!), afterwards, reboot to bootloader, unlock bootloader, reboot to fastboot, fastboot flash the boot.img and the recovery.img of your choice on (limited on boot.img's at the moment, better use the one from the rom), reboot to recovery and flash the rom
the other methods imply you understand somewhat how the process works.
relock bootloader (if unlocked), run PH39IMG install, unlock bootloader, fastboot flash recovery and boot.img, reboot to recovery and flash rom.....
if you wrap your head around HOW it works, its all really simple....so the first step is understanding HOW it works, not blindly following some tutorial or walkthrough.
please try to LEARN and UNDERSTAND what it is you are doing....
Click to expand...
Click to collapse

I got the recovery I needed following this:
http://forum.xda-developers.com/showpost.php?p=23238449&postcount=9

alright so after i get the two files that i need i just follow the instructions above starting with locking bootloader?
strose09 said:
I got the recovery I needed following this:
http://forum.xda-developers.com/showpost.php?p=23238449&postcount=9
Click to expand...
Click to collapse

Before you start are you savvy with fastboot commands? I'm confident you can do this but just read read read. I'll answer your questions as best as I can. I"m not a dev or anything but I was able to do this following the steps created by PG and Thecubed.

i've tip toed around with it. Back when i had my evo 4g. I'm pretty familiar with the commands and stuff. i think i got a pretty good idea with the superguide also. after the getting the img file on and cwm i'm decent at the whole flash thing. If i can just get past that point i think im good.
strose09 said:
Before you start are you savvy with fastboot commands? I'm confident you can do this but just read read read. I'll answer your questions as best as I can. I"m not a dev or anything but I was able to do this following the steps created by PG and Thecubed.
Click to expand...
Click to collapse

Yes keep the superguide thread open as well. It's a great resource to have while you are doing this. The steps are nearly the same just have to update the HBOOT first. Good luck! I look forward to seeing you post having a successful install.

So I just got my replacement vivid..still locked and everything..how do I update with the ruu?
Sent from my HTC PH39100 using xda premium

Connect phone to pc, open .exe and run it.
Sent from my HTC PH39100 using XDA

Thank u got it going and thank god cuz now pg it seems has left the building...
Sent from my HTC PH39100 using xda premium

If we flash the RUU, do we need to relock the bootloader first or just run the RUU? Running stock rooted
EDIT: Nvm I found my answer. Still unable to find the RUU. Anyone have a mirror to the RUU?

Apatche69 said:
If we flash the RUU, do we need to relock the bootloader first or just run the RUU? Running stock rooted
EDIT: Nvm I found my answer. Still unable to find the RUU. Anyone have a mirror to the RUU?
Click to expand...
Click to collapse
Here you go

Thank you very much. I'll look forward to ICS.

flash recovery: signature verify fail

I am trying to install Amon_RA recovery on my N1.
I followed the instructions from the Full Update Guide (wiki.cyanogenmod) and from XDA (recovery RA-passion-v2.2.1 by Amon-RA who does an outstanding dev).
Checked md5sum of recovery-RA-passion-v2.2.1.img : matched
Checked md5sum of recovery-RA-passion-v2.2.1-CM.img: matched
The phone is unlocked. I use fastboot to flash the recovery. I get “Signature verify fail”.
I made a thorough search and I did not find an explanation and an answer other than for rooted phone.
I do not want to root.
I tried disabling the anti virus program. I reset the phone. I checked the installation of SDK. I checked the Environment Variables in “Advanced settings” on Widows Vista and Win7. I even checked my sanity.
I would appreciate any guidance to solve this issue.
Nexus One unlocked
S-ON HBOOT-0.35.0017 RADIO-5.08.00.04
GB 2.3.6 Kernel 2.6.35.7-59465-g42bad32 Build # GRK39F
Device recognised under ADB and Fastboot. Recovery put in android-sdk-windows/platform-tools.

hi, sorry if my english isn't perfect, but i want to try to help u.
If with the command fastboot devices you get a report the fastboot.jpg in attachments you'r ok.
Unlock the bootloader, command prompt do this: fastboot oem unlock
and accept the question on the mobile phone.
now you have phone unloocked so no free assistance if you broke.
Procede to next step, flash the recovery download rar from attachments and then in the fastboot do this: fastboot flash recovery recovery-RA-passion-v2.2.1.img if you get problem repost.
teh in the bootloader go to bootloader (power button) and then recovery (power button) phone will reboot in recovery mode.
If you have problem post another time and forgive my bad english =)

gunner1937 said:
I am trying to install Amon_RA recovery on my N1.
I followed the instructions from the Full Update Guide (wiki.cyanogenmod) and from XDA (recovery RA-passion-v2.2.1 by Amon-RA who does an outstanding dev).
Checked md5sum of recovery-RA-passion-v2.2.1.img : matched
Checked md5sum of recovery-RA-passion-v2.2.1-CM.img: matched
The phone is unlocked. I use fastboot to flash the recovery. I get “Signature verify fail”.
I made a thorough search and I did not find an explanation and an answer other than for rooted phone.
I do not want to root.
I tried disabling the anti virus program. I reset the phone. I checked the installation of SDK. I checked the Environment Variables in “Advanced settings” on Widows Vista and Win7. I even checked my sanity.
I would appreciate any guidance to solve this issue.
Nexus One unlocked
S-ON HBOOT-0.35.0017 RADIO-5.08.00.04
GB 2.3.6 Kernel 2.6.35.7-59465-g42bad32 Build # GRK39F
Device recognised under ADB and Fastboot. Recovery put in android-sdk-windows/platform-tools.
Click to expand...
Click to collapse
You said "I do not want root" so why do you want to install custom recovery? The purpose of installing custom ROM or recovery is to gain root access but you don't want to root your phone so don't flash custom ROM or recovery. And you should post in Q&A not both places.

Molto grazie.Your English is far better than my Italian.
As I said the phone is unlocked and, yes, I get fastboot (if not I could not go to the point where I am, I believe)
Forza italia ma nontroppo against Russia

Yes, you're right, but i'm agree with Taodan, why you should have to flash recovery if you don't want root ? it isn't very useful XD maybe you want root in order to backup a stock rom, but if you want a stock rom of android 2.3.4 i can upload one for you XD anbd thanks for say my engolish isn't bad and yes Forza Italia XD but I want to get live in the UK or USA !!!

taodan said:
You said "I do not want root" so why do you want to install custom recovery? The purpose of installing custom ROM or recovery is to gain root access but you don't want to root your phone so don't flash custom ROM or recovery. And you should post in Q&A not both places.
Click to expand...
Click to collapse
I owe you an apology for not knowing that I have to justify the purpose of my question.
I was naive enough to consider that flashing a recovery was obviously to help install a Cyanogen ROM. My naivete even brought me to believe that installing a Recovery without flashing a ROM will bring me back to the stock recovery.
Going further I should have added "for the moment" to my decision of not rooting.
And my final answer, regarding the wrong thread, is that I tried to edit my post in order to move to the right thread when I discovered my mistake.
Thank you for your reply. It will help me re-check my sanity.
That said are you ready to offer me a solution which could be posted on the other thread?

Ivan93tm said:
Yes, you're right, but i'm agree with Taodan, why you should have to flash recovery if you don't want root ? it isn't very useful XD maybe you want root in order to backup a stock rom, but if you want a stock rom of android 2.3.4 i can upload one for you XD anbd thanks for say my engolish isn't bad and yes Forza Italia XD but I want to get live in the UK or USA !!!
Click to expand...
Click to collapse
My main concern is not to root or not to root.
Re-read my post and you will discover that my question specifically asks for a solution regarding a flash recovery.
Anyway, I do appreciate your contribution. Prego

this belong to help Q&A thread not dev thread...

P00r said:
this belong to help Q&A thread not dev thread...
Click to expand...
Click to collapse
Please, read Post# 6 and the last sentence of the 1st paragraph. It should make you happy

[Q]S-OFF

Two simple questions: When do I need S-OFF and when do I know?
I want to test some of the custom roms on xda, and I have unlocked the bootloader, flashed cwm and are rooted.
Sent from my HTC One using xda app-developers app

You don't need S OFF to use ROMS. So long as you have CWM you can flash any ROM. But you have to flash the Boot.IMG separately as well.
E.g.
- Download your ROM
- Double click on the ZIP and take the Boot.IMG out. Just get a copy of it. Doesn't matter if it's still in the ZIP. You just need a copy of it.
- Flash the ROM
- Go back in Fastboot and flash the Boot.IMG
- To do that put the IMG in your Fastboot folder or any folder than recognises ADB (Fastboot mode)
- Open CMD and navigate to the Fastboot folder in which the boot.img is too
- Type with CMD : Fastboot flash boot boot.img
- It should say complete or OK
- Restart phone and enjoy
S OFF is mainly just for users who can't be bothered to do that. And to find out if you have S OFF you go in Fastboot mode and it will say up top if it is or not (S-ON)
Sent from my Sony Xperia Z using XDA Premium HD

But why not just get s off and flash roms normally? What's the reason for not get s off?
Sent from my HTC One using xda app-developers app

VistaX said:
But why not just get s off and flash roms normally? What's the reason for not get s off?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
you don't need S-off unless you want to change your phone's CID or downgrade the HBoot
if you don't know what these things are you don't need it.
You also don't need it to flash a kernel like the 2nd post suggested.

I've flashed about 10 different roms and not had to that with any of them. Just flash the zip in recovery. I'm new to android a few months so maybe things have changed recently?
S-off is if you want change bootloaders, cid, etc. Once you have s-off it's easy to brick your device if you're not careful. It's not needed for flashing roms though.
Sent from my HTC One using xda premium

Ah, then I'm gonna skip S-OFF. I've flashed many roms with mye SGS3 and LGO2X, but I think maybe HTC is a little more tricky to handle.

VistaX said:
Ah, then I'm gonna skip S-OFF. I've flashed many roms with mye SGS3 and LGO2X, but I think maybe HTC is a little moretricky to handle.
Click to expand...
Click to collapse
Yes they are definitely!

So for the "common flasher" it's not necessary to be S-ON?

VistaX said:
So for the "common flasher" it's not necessary to be S-ON?
Click to expand...
Click to collapse
If all you plan to do is use custom ROMs then there's no need to be S-OFF. All you'll really need is unlocked bootloader and custom recovery (TWRP or CWM).

S-off allows you to change your phone's firmware regardless of what carrier you have or model ID. So you can get the most recent firmware even if your carrier hasn't pushed out an OTA. That matters to some people but not all.
It also allows you to flash a custom hboot to remove the red text on your splash screen. This is wholly an OCD thing--there's no good reason to do it otherwise.
S-off essentially means you're taking full responsibility for your phone and can't rely on HTC's security checks to prevent bricks.

Verizon Htc one, rom reboots every few minutes.

Hello guys Im having a problem with my vzw htc one and I know its my fault, I basically soft bricked the phone however it loads into currently installed rom (I had 3 and only one that would load) I have but reboots every few minutes with no access to the internal memory. I was trying to install Google play edition 4.4 kitkat however I forgot the radios are different for our phones and I installed the incorrect radio so now I am stuck only with the bootloader and CWM recovery but I cannot flash any files through fastboot because its apparently still locked (im getting the remote not allowed error) My phones is S off and rooted (I used rumrunner) . I have tried to mount usb storage in recovery with no luck and I have tried to flash a new rom and radio through boot loader but its locked and htc dev wont let you unlock our phones so im kinda stuck
If anyone has a solution to my problem I would really appreciate it I use my phone for a lot of stuff while deployed here in Afghanistan I use Roshan prepaid sim card works well.Thanks for any help and have a great day !

armyguy1989 said:
Hello guys Im having a problem with my vzw htc one and I know its my fault, I basically soft bricked the phone however it loads into currently installed rom (I had 3 and only one that would load) I have but reboots every few minutes with no access to the internal memory. I was trying to install Google play edition 4.4 kitkat however I forgot the radios are different for our phones and I installed the incorrect radio so now I am stuck only with the bootloader and CWM recovery but I cannot flash any files through fastboot because its apparently still locked (im getting the remote not allowed error) My phones is S off and rooted (I used rumrunner) . I have tried to mount usb storage in recovery with no luck and I have tried to flash a new rom and radio through boot loader but its locked and htc dev wont let you unlock our phones so im kinda stuck
If anyone has a solution to my problem I would really appreciate it I use my phone for a lot of stuff while deployed here in Afghanistan I use Roshan prepaid sim card works well.Thanks for any help and have a great day !
Click to expand...
Click to collapse
instructions to unlock are here ...you use revone (on hboot 1.44)
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
Correction Below for hboot 1.54 use this >> http://forum.xda-developers.com/showthread.php?t=2470340
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader

clsA said:
instructions to unlock are here ...you use revone
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Thank you so much clsA I will do this when I get off work im on a government computer, thanks again !

clsA said:
instructions to unlock are here ...you use revone
http://forum.xda-developers.com/showthread.php?t=2314582&nocache=1
I also suggest update to TWRP if you want to flash the modern kit kat roms
http://techerrata.com/browse/twrp2/m7vzw
fastboot flash recovery openrecovery-twrp.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
So revone will unlock my hboot ? Im already s-off but my problem is its saying it doesnt support hboot 1.54 and thats what I have

armyguy1989 said:
So revone will unlock my hboot ? Im already s-off but my problem is its saying it doesnt support hboot 1.54 and thats what I have
Click to expand...
Click to collapse
I think some functions like unlock still work. if not you'll have to flash a firmware to get back to 1.44 hboot
sorry try here >> http://forum.xda-developers.com/showthread.php?t=2470340

147
clsA said:
I think some functions like unlock still work. if not you'll have to flash a firmware to get back to 1.44 hboot
sorry try here >> http://forum.xda-developers.com/showthread.php?t=2470340
Click to expand...
Click to collapse
Im using my buddies laptop and 3g hotspot at work I just installed twrp it works fine I have the correct radio to load on my phone is there i way i can flash this new correct radio without unlocking the hboot ? Everything is erased but i still have carbon rom running so if i get the correct radio again i can just use the phone normally and install the rom using the computer. if that doesnt work can i use adb sideload or something in twrp recovery ? i tried to mount usb in twrp but still no go.

armyguy1989 said:
Im using my buddies laptop and 3g hotspot at work I just installed twrp it works fine I have the correct radio to load on my phone it has a boot img is there i way i can flash this new correct radio and a new rom without unlocking the hboot ? like using adb sideload or in twrp recovery ? i tried to mouunt usb in twrp but still no go.
Click to expand...
Click to collapse
you can download any flashable radio and replace the radio.img in the zip with yours and flash it in twrp.
here's one of mine >> http://www.androidfilehost.com/?fid=23501681358550122
Edit: and did you look at scotty's lock / unlock page ?
Also the Carbon rom could be part of your problem
try a normal Sense Rom - like http://forum.xda-developers.com/showthread.php?t=2693502
or
here>> http://forum.xda-developers.com/showthread.php?t=2485319

clsA said:
you can download any flashable radio and replace the radio.img in the zip with yours and flash it in twrp.
here's one of mine >> http://www.androidfilehost.com/?fid=23501681358550122
Edit: and did you look at scotty's lock / unlock page ?
Also the Carbon rom could be part of your problem
try a normal Sense Rom - like http://forum.xda-developers.com/showthread.php?t=2693502
or
here>> http://forum.xda-developers.com/showthread.php?t=2485319
Click to expand...
Click to collapse
I did see that and cool I will use yours. I guess I will try to unlock it in case this happens again but ill probably never mess with the radio again lol.
i wasnt using the carbon rom anymore i had 2 more roms on my sd card and when i flashed the incorrect radio the other two wouldnt even work. thescreen was black when it loaded. carbon rom is the only one that would load but it just reboots every few minutes i tried to copy the files on the sd card before it rebooted but wouldnt work
just out of curiousity how would i flash that with the bootloader locked. i really want to know incase something ever happens again. im still learning alot of this stuff lol
Im going to unlock the hboot real quick and see if that works. you should private message me your paypal im going to buy you dinner for all your help

btw this my current radio 4T.21.3218.21 im guessing it doesnt work with verizon htc one lol.

Never mind I found the donate button !

armyguy1989 said:
Never mind I found the donate button !
Click to expand...
Click to collapse
This is the newest Verizon radio
http://forum.xda-developers.com/devdb/project/dl/?id=6511
and in my dropbox as well >> https://www.dropbox.com/s/0yq7d3xnrni9hm3/Flashable-m7vzw_4.10.605.3_1.13.41.0421_Radio.zip
Thanks for the Dinner and Drink

clsA said:
This is the newest Verizon radio
http://forum.xda-developers.com/devdb/project/dl/?id=6511
and in my dropbox as well >> https://www.dropbox.com/s/0yq7d3xnrni9hm3/Flashable-m7vzw_4.10.605.3_1.13.41.0421_Radio.zip
Thanks for the Dinner and Drink
Click to expand...
Click to collapse
Well i feel like a dumbass right now unless its just a crazy stroke of luck. i had my usb plugged in to the ss 3.0 and when reading the instructions to setup up the adb it said to make sure you not using a 3.0 usb. so i switched and when i rebooted carbon rom becase it says i need usb debugging on but when i rebboted my internal sd popped up and i tried to move the files and it worked and then reboot lol. i went into recovery and flashed google play rom and its working however my Afghanistan roshan simcard isnt working now i set it back to global but no go. what radio should i flash now if yours works fine with verizon ill just use yours. which one should I use ?

armyguy1989 said:
Well i feel like a dumbass right now unless its just a crazy stroke of luck. i had my usb plugged in to the ss 3.0 and when reading the instructions to setup up the adb it said to make sure you not using a 3.0 usb. so i switched and when i rebooted carbon rom becase it says i need usb debugging on but when i rebboted my internal sd popped up and i tried to move the files and it worked and then reboot lol. i went into recovery and flashed google play rom and its working however my Afghanistan roshan simcard isnt working now i set it back to global but no go. what radio should i flash now if yours works fine with verizon ill just use yours. which one should I use ?
Click to expand...
Click to collapse
Did you set the APN setting on the new Rom ?
Setting/mobile data/access point name
Stick with the newest Verizon radio I posted above

No I havent done that yet i just installed your radio ill try that now.