Database Users

[Q] Does new SPL lock us out of flashing roms?

Sorry for the probably dumb question, but I'm unclear on something.
I know that the new SPL with the OTA Froyo update is perfected. Does that mean that we can't:
A. Flash a custom recovery?
B. Install a custom rom?
C. Apply SAPPIMG if I seriously **** something up?
D. MOST IMPORTANT - nandroid back to where I am now?
I really want to try the official update with new radio but I want to be able to nandroid back to where I am now if I decide for some reason that the update irritates me. Can someone shed some light?

Well the word "perfected" refers to the ability to get unrestricted access to the nand (the storage of the device). With a perfected spl, you have no access to nand + others important instructions. Which means that you cannot flash/erase any of the fun partitions, e.g. spl, radio or recovery. Nor can you flash/erase system, boot ect...
On some non-perfected spl, you had the restriction of the above, but you could load("boot") your images and therefore easily boot a custom recovery and do whatever you wanted.
With perfected spl the option of booting an img is not there.
On some devices, like the magic, we have engineering spl, which ignores the s-off flag. S-on/s-off refers to "security" off/on. With security off you have unrestricted access to the nand.
On some other devices, you have modified spl/hboot, E.g. The Desire device.
Their hboot will simply ignore the s-off flag and give you unrestricted access on the nand + the other fun commands, e.g erase and boot.
Now you aske, Ignore the s-off flag???
Yes, the s-off flag (called "secuflag" ) is actually set in something called Radio NVRAM.
This operate in a lower level then the radio image you flash.
The non + perfected spl reads this flag and behaves accordingly.
The modified hboot + eng hboot simply ignores it.
Going back to the magic device.
As long we can get root on the system, we can flash our own custom recovery. From the custom recovery we can flash the eng spl. And wooooot... we have unrestricted access to nand.
Remember, that the spl, radio and system all are simply partitions on the nand. With root we can flash what ever we want.
The only problem can be, if the 2.2 update has a radio img that do not play nicely with the current eng spl. But will still be able to load a custom recovery wit root access... so the option to flash custom roms will always be there if we can get root on the system.
Last i checked, the android 2.2 is no problem to root using a special exploid.
So don't worry... all is good :0)
Applying a sappimg, is a feature built in all spl. You can ALWAYS flash a sappimg.zip from fastboot if you have same cid nr as the sappimg.zip and the main-version of the phone is the same or lower of what you are trying to flash!
So don't worry :0)
What is goldcard used for?
A good question. Goldcards are used to skip the CID check. E.g. my nordic magic with cid HTC-Y13 can flash the Rogers update with CID ROGER001.
But still, the main-version check still applies :0)
No more knowledge from me today... my hands hurts

mumilover said:
Well the word "perfected" refers to the ability to get unrestricted access to the nand (the storage of the device). With a perfected spl, you have no access to nand + others important instructions. Which means that you cannot flash/erase any of the fun partitions, e.g. spl, radio or recovery. Nor can you flash/erase system, boot ect...
On some non-perfected spl, you had the restriction of the above, but you could load("boot") your images and therefore easily boot a custom recovery and do whatever you wanted.
With perfected spl the option of booting an img is not there.
On some devices, like the magic, we have engineering spl, which ignores the s-off flag. S-on/s-off refers to "security" off/on. With security off you have unrestricted access to the nand.
On some other devices, you have modified spl/hboot, E.g. The Desire device.
Their hboot will simply ignore the s-off flag and give you unrestricted access on the nand + the other fun commands, e.g erase and boot.
Now you aske, Ignore the s-off flag???
Yes, the s-off flag (called "secuflag" ) is actually set in something called Radio NVRAM.
This operate in a lower level then the radio image you flash.
The non + perfected spl reads this flag and behaves accordingly.
The modified hboot + eng hboot simply ignores it.
Going back to the magic device.
As long we can get root on the system, we can flash our own custom recovery. From the custom recovery we can flash the eng spl. And wooooot... we have unrestricted access to nand.
Remember, that the spl, radio and system all are simply partitions on the nand. With root we can flash what ever we want.
The only problem can be, if the 2.2 update has a radio img that do not play nicely with the current eng spl. But will still be able to load a custom recovery wit root access... so the option to flash custom roms will always be there if we can get root on the system.
Last i checked, the android 2.2 is no problem to root using a special exploid.
So don't worry... all is good :0)
Applying a sappimg, is a feature built in all spl. You can ALWAYS flash a sappimg.zip from fastboot if you have same cid nr as the sappimg.zip and the main-version of the phone is the same or lower of what you are trying to flash!
So don't worry :0)
What is goldcard used for?
A good question. Goldcards are used to skip the CID check. E.g. my nordic magic with cid HTC-Y13 can flash the Rogers update with CID ROGER001.
But still, the main-version check still applies :0)
Click to expand...
Click to collapse
Wow, thank you very much for the prompt and extremely detailed reply! That's exactly what I needed to know.
So since it's already been verified that the superoneclick root method works on mt3g with ota 2.2, I'll be fine if I decide I'm not happy.
Cool, that's what I needed to know.
Thanks!

Glad i could clarify :0)

[Resolved] PLEASE help. G2 bricked!

Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC

MobileWon said:
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
Every phone i have had from the g1, mytouch 3g, vibrant, and now g2 it never fails to amaze me how people who dont know what they are doing manage to brick their phone in under a day. PROTIP READ learn what you are doing before you go in doing it so you dont screw yourself.

If you have the hboot menu and you seem to have s-off so you can restore official htc rom or a custom rom
Sent from my HTC Vision using XDA App

Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash

Hot_Hands said:
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Click to expand...
Click to collapse
Yup, exacly what he said.. also, I don't think editing the statusbar from a stock is possible because its odexed, correct me if I am wrong though.. unless you really know what you're doing.. so now after flashing recovery, try again with a nandroid if you have yours if not with fastludeh's stock odex or deodex rom if you want to keep it stock.
Sent from my HTC Vision

You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend

Hot_Hands said:
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Click to expand...
Click to collapse
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?

MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
Nope. Just put it on your SD and flash from recovery.

MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
No, you do not need to rename it.
Sent from my HTC Vision using XDA App

MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
EDIT: Oh wait, it says SHIP S-OFF, shouldn't it say ENG S-OFF if you had the ENG boot loader? Did you even flash the new HBOOT?

KoolKidsKlub said:
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
Click to expand...
Click to collapse
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.

ianmcquinn said:
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
Click to expand...
Click to collapse
Yeah I just noticed that and edited my post about 1-2 minutes ago.

Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.

The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.

MobileWon said:
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
Click to expand...
Click to collapse
Yeah ummm you might be screwed, we assumed that you flashed the engineering HBOOT, and only with the engineering HBOOT can you use fastboot to save your self and it seems like you don't have it. I'm not sure what to do now, I think some one said that you might have to flash the stock ROM but I'm not sure how. Wait around for some other guys to help you out, they know more than me with this stuff.

Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Ok, I have the stock rom already. How do I flash a RUU? Or can you give me a link?

Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
EDIT: And if you do have to flash an RUU, could you please explain how? I would like to know how just in case I screw something up(which I probably won't because I have been on my computer searching the forum, asking for help and to double check that what I have learned is correct and what to do if something bad happens for the past week or two) and I can also use the information to help other users.

KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
That was a warning because if you had S-Off and root it would put S-On and remove root. It was an issue because for a while it was impossible to root the DZ's 1.72 RUU but this has since been worked around and doesn't apply to the G2.

Ok, guys Im not an idiot. I previously had a HD2 and had no problems...just rushing to get my phone right before I go out of town for the weekend. So, whatever I have to do to get it right.

KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
You might be right.
Ok,... So you have gone into your Hboot screen, select fastboot, then it says Fastboot on the screen yeah? Do:
fastboot devices
in cmd, do you get anything?

Downgrading from .97 to .76 bootloader, what's the trick?

I am currently s-off via UnrEVOked. I want to go from .97 to .76 to get fastboot.
Is it as simple as flashing the file from recovery?
1) Do I need to clear cache/dalvik?
2) Do I need to re-flash the ROM/radio/PRI/NV?
3) Any other implications or dangers of doing this?
I'd appreciate any info.

If it fails to boot up after you downgrade, you'll probably have to reflash the ROM.

Noxious Ninja said:
If it fails to boot up after you downgrade, you'll probably have to reflash the ROM.
Click to expand...
Click to collapse
1) What is the likelihood of my device not booting, based on what you have seen from people's actual experience?
2) If my device boots okay, then nothing else to worry about?
3) If my device does fail to boot, will I be able to boot into recovery? Will a nandroid restore suffice?
Thank you.

Not reflash the ROM, just the kernel should suffice.

InfectedMushroom said:
Not reflash the ROM, just the kernel should suffice.
Click to expand...
Click to collapse
For my knowledge, why is flashing the kernel necessary at all? If HBoot is a different part of the phone (sort of like a bootstrap), shouldn't the OS/ROM/kernel/radio/etc. not be touched at all?
Thank you.

Snovvman-
Search for hboot in "EVO android development" section. I think Caulkin started that thread. It has the .76 hboot version with installation instructions. I would also recommend updating your recovery if you haven't already. I have AmonRA v2.2.1 with hboot .76 on my EVO. Amon's recovery has some cool features. Good luck dude.
Sent from my PC36100 using XDA App

ElectronBlue said:
Snovvman-
Search for hboot in "EVO android development" section. I think Caulkin started that thread. It has the .76 hboot version with installation instructions. I would also recommend updating your recovery if you haven't already. I have AmonRA v2.2.1 with hboot .76 on my EVO. Amon's recovery has some cool features. Good luck dude.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks. I have the files from that thread (actually on my subscribed list), I actually have all the HBoot versions at the ready. I am currently using CW 2.6.0.1 for now and I like it okay. There are even a couple of threads to help people with 2.x Hboot to go back to .76. Reading through them, they just don't exactly apply to what I'm wanting to do. I'm simply gathering some data before diving in.
Edit: I started the thread because I have read in different places where either 1) no additional flash is needed, 2) must re-flash radio/PRI/NV/etc., 3) must reflash ROM, or 4) may need to reflash kernel.
I not only want to know what one actually must do, but why...

My experience with downgrading my hboot went like this. After I applied the 76 hboot and tried to boot up, it would loop me back to the boot loader. After I went to recovery through the boot loader I flashed a new rom and got out of the boot loader loop. If you downgrade, you WILL get in that loop unless the method has changed and you will have to reflash a kernel or the whole rom.

jxr94 said:
My experience with downgrading my hboot went like this. After I applied the 76 hboot and tried to boot up, it would loop me back to the boot loader. After I went to recovery through the boot loader I flashed a new rom and got out of the boot loader loop. If you downgrade, you WILL get in that loop unless the method has changed and you will have to reflash a kernel or the whole rom.
Click to expand...
Click to collapse
Thanks. From what version did you downgrade? I presume the radio/PRI/etc. stayed intact?

There is a thread about this. Search!!
From what I can remember, the older hboot doesn't work properly with the newer nand chips, specifically those with 40000 byte erase blocks possibly present in rev 0004. Flashing an old hboot onto one of these results in a bricked evo.
http://forum.xda-developers.com/showthread.php?t=883548
ymmv

gpz1100 said:
There is a thread about this. Search!!
From what I can remember, the older hboot doesn't work properly with the newer nand chips, specifically those with 40000 byte erase blocks possibly present in rev 0004. Flashing an old hboot onto one of these results in a bricked evo.
http://forum.xda-developers.com/showthread.php?t=883548
ymmv
Click to expand...
Click to collapse
Thanks. As I indicated in a previous post in this thread, I am aware of the post you cited, as well as another. They are actually both in my subscribed list. I have the 20K partition. I started this thread because those threads describe steps to go from 2.x Hboot to .76, not .97 to .76. I have yet to see a specific case where somone went from .97 to .76. I wanted to know if going from .97 would be less problematic than from 2.x.

I went from .97 to .76 with no problems other than the expected bootloop. I just reflashed my kernel and was good to go. No need to reflash the rom.

snovvman said:
Thanks. As I indicated in a previous post in this thread, I am aware of the post you cited, as well as another. They are actually both in my subscribed list. I have the 20K partition. I started this thread because those threads describe steps to go from 2.x Hboot to .76, not .97 to .76. I have yet to see a specific case where somone went from .97 to .76. I wanted to know if going from .97 would be less problematic than from 2.x.
Click to expand...
Click to collapse
That used to be the only method of unlocking the NAND, you are safe. If you haven't done it yet then the best way to do it is through the bootloader though.

InfectedMushroom said:
I went from .97 to .76 with no problems other than the expected bootloop. I just reflashed my kernel and was good to go. No need to reflash the rom.
Click to expand...
Click to collapse
Thank you.
xHausx said:
That used to be the only method of unlocking the NAND, you are safe. If you haven't done it yet then the best way to do it is through the bootloader though.
Click to expand...
Click to collapse
xHausx: Do you mean to do that by renaming the .76 Hboot to PCIMG36 and boot into the bootloader to let it flash?
Again, just for my education, why is this better than flashing through recovery?
Cheers.

snovvman said:
xHausx: Do you mean to do that by renaming the .76 Hboot to PCIMG36 and boot into the bootloader to let it flash?
Again, just for my education, why is this better than flashing through recovery?
Cheers.
Click to expand...
Click to collapse
You will need it packaged as a PC36IMG to work, I went ahead and attached one with it if you still need it.
As a rule of thumb flashing from the bootloader is always safer than from the recovery. Odds are if the bootloader can't flash properly your phone would already be a brick, so you know it will be good. Although with something like the bootloader the recovery may actually call on the bootloader to do the actual flashing but you never know.

xHausx said:
You will need it packaged as a PC36IMG to work, I went ahead and attached one with it if you still need it.
As a rule of thumb flashing from the bootloader is always safer than from the recovery. Odds are if the bootloader can't flash properly your phone would already be a brick, so you know it will be good. Although with something like the bootloader the recovery may actually call on the bootloader to do the actual flashing but you never know.
Click to expand...
Click to collapse
Thank you for taking the time to make and upload the zip sir.

Root no longer works

Hi
I used to have root on my HTC Magic, but I noticed that since I used System App Remover, my phone no longer has root and I experience random reboots and other times the phone just switches off. That's my fault - I should have made a backup, but for some reason I didn't at the time. Anyway. I've tried re-rooting; I've tried removing root and then re-rooting but nothing seems to work. I use Terminal Emulator to see if I have root. According to it, I don't have. However, when I use Universal Androot or some other app, it says I already have root, however, this is not the case, because when I reboot into recovery, nothing works. Whichever option I choose, the phone just reboots normally. Please help? I want to install a new Android 2.3.3 ROM :-/
Thanks in advance

Give some info about your device(from fastboot- back+power+).
What ROM you using now?

blaster44 said:
Give some info about your device(from fastboot- back+power+).
What ROM you using now?
Click to expand...
Click to collapse
hboot - 1.76.0009
cpld - 12
radio - 6.35.08.29
Running FuzeBox Froyo 2.2. There's a thread of it around here, but that ROM's development was stopped a long time ago.
It happens when I reboot into recovery (haven't tried it in a while). Can't remember the combo but I can boot into Fastboot just fine. Issue comes in when I have to boot into recovery. I can see the options but when I click on them, the phone just reboots and loads the OS.

No one?

Security
Most importantly in Fastboot, do you have S-ON or S-OFF?
TheNiz said:
No one?
Click to expand...
Click to collapse

karym1969 said:
Most importantly in Fastboot, do you have S-ON or S-OFF?
Click to expand...
Click to collapse
It's always been S-ON, even when I had root...

SPL S-ON
You will not be able to flash anything as long as you have Security-ON (perfected SPL).
Thus, you need to create a goldcard with S-OFF (Engineered SPL). Check this link:
http://forum.xda-developers.com/showthread.php?t=548218
TheNiz said:
It's always been S-ON, even when I had root...
Click to expand...
Click to collapse

Let me ask the OP something real quick...
Why is it that you posted your QUESTION in the DEVELOPMENT section instead of the QUESTIONS & ANSWERS (General Q&A) section?
Rhetorical.
I'll move your QUESTION to the GENERAL Q&A section but the next thread that you create in the DEVELOPMENT section without any actual DEVELOPMENT will result in an immediate removal of your thread without warning!

karym1969 said:
You will not be able to flash anything as long as you have Security-ON (perfected SPL).
Thus, you need to create a goldcard with S-OFF (Engineered SPL). Check this link:
http://forum.xda-developers.com/showthread.php?t=548218
Click to expand...
Click to collapse
Not true. I flashed my current custom ROM and I had S-ON.

TheNiz said:
Not true. I flashed my current custom ROM and I had S-ON.
Click to expand...
Click to collapse
You flashed your current custom rom... in recovery! Not fastboot. No custom roms are flashed via fastboot. Which is why s-off isn't needed usually.

tvall said:
You flashed your current custom rom... in recovery! Not fastboot. No custom roms are flashed via fastboot. Which is why s-off isn't needed usually.
Click to expand...
Click to collapse
Yeah, I know.

Flashing
Flashing a rom is totally different than flashing a radio,spl, recovery from fastboot.
Having SPL S-ON will give you an error of "remote Fastboot not allowed".
Good Luck.
TheNiz said:
Not true. I flashed my current custom ROM and I had S-ON.
Click to expand...
Click to collapse

karym1969 said:
Flashing a rom is totally different than flashing a radio,spl, recovery from fastboot.
Having SPL S-ON will give you an error of "remote Fastboot not allowed".
Good Luck.
Click to expand...
Click to collapse
I know, but I can't flash anything due to some other error I get when I enter fastboot. It doesn't say fastboot not allowed, but it game some other message that indicated I don't have permission to do so. Even if I were to flash a new radio/SPL, that won't allow me to flash a custom ROM, since the custom recovery fails.

Can someone please help me? I've tried everything. Nothing seems to work. I've tried various recoveries and none of them work. I can't flash anything, nor do any restores

[HOW-TO] bootloader unlock 4.67.651.3 OTA

1. Unlocking bootloader via htcdev.com (selecting All Other Supported Models)
2. Flashing recovery via fastboot (./fastboot flash recovery cwm-4.0.1.4-supersonic.img)
3. Reboot recovery and flash latest su.
4. Profit.
PROOF:
Code:
[email protected] ~/evo_s-off $ ./fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
===========bla-bla-bla=============
---checking my e-mail for Unlock_code.bin---
[email protected] ~/evo_s-off $ ./fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)... OKAY
writing 'unlocktoken'... INFOunlock token check successfully
OKAY
[email protected] ~/evo_s-off $ ./fastboot flash recovery cwm-4.0.1.4-supersonic.img
sending 'recovery' (3074 KB)... OKAY
writing 'recovery'... OKAY

this is very strange. nobody interested in unlocking bootloader?

there is no official info, but works fine for me.

I'm one of the ones on the newest ota. This helps out a lot, thank you

I already have root, but I am rooting someone else's phone that has new hboot. Thanks!
Sent from my PC36100 using Tapatalk

people with unlocked bootloaders please leave comments here.

Total noob mistake.
OK i ended up updating my evo to the new 4.67.651.3 update. big mistake
I ended up stumbling across this post. (thx wardriva)
I was able to unlock the bootloader and use the ADB method mentioned in this thread to flash recovery.
after looking around I came across brad560's thread and flashed the deodex'ed rom with no problems.
so far everything is working. I also kept looking around and came across the Collection Project (thx Tommytomatoe) and flashed the hot spot hack by SOS. so far its working.
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Thx to all the DEV's.

wardriva said:
this is very strange. nobody interested in unlocking bootloader?
Click to expand...
Click to collapse
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)

coldroy said:
still looking to see if someone has found a workaround with the S-OFF or if revolutionary will support it.
Click to expand...
Click to collapse
you don't need S-OFF with unlocked bootloader. you can flash any rom you want with any kernel you wish. i just checked.

Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
what are you talking about? the latest OTA let us unlock bootloader.

wardriva said:
what are you talking about? the latest OTA let us unlock bootloader.
Click to expand...
Click to collapse
my fault, apologies reading to fast and totally thinking rooting instead unlocking??lol!

hmmm. From the little bit I had read on Evo 3d forum, I thought that even with unlocked bootloader, s-on means no flashing of kernels? Or maybe it's different on 3d cuz it uses EMMC ? Does a custom kernel remain after reboot?
Would love clarification from anyone who knows better than I. Thanks.
Also, this comes just in time for evos EOL status lol. Coincidence ?
Sent from my PC36100 using xda premium

Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?

To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Why is my security still on (S-On) after I have unlocked my bootloader?
Your device is shipped with Security on (S-ON) to protect your system software configuration (such as the bootloader, radio, boot, recovery, system and others). After you have unlocked the bootloader, however, you will have lifted the restrictions on boot, recovery and system. This means you can customize boot, recovery and system images on your phone as you desire. You can easily see that you have successfully unlocked the bootloader by looking at the top of the screen when entering the bootloader screen. Security is left on to protect things like the radio, and SIM lock.
Click to expand...
Click to collapse

shortydoggg said:
Can you still write to the system or uninstall bloatware with the unlocked bootloader (which is still S-ON)?
Click to expand...
Click to collapse
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.

shortydoggg said:
Just curious about the new bootloader, because based on past bootloaders I've had,
If you are rooted, but still S-ON, you can delete any bloatware (system apps) that you want, but after rebooting the phone it all returns. Why, because there is a backup of how your partitions were on the phone that cannot all be flashed unless you are S-OFF. When you're S-ON, any changes you made to the original partitions, (especially recovery and system if system is done inside the operating system) will be voided the next time you reboot the phone. That is also why you would need to connect your phone to your computer every time you needed to flash a custom ROM (if this is still the case with the new bootloader), because the backup (stock Recovery) is always restored on reboot.
You can change the system partition outside of the operating system by recovery, however; which is the reason why you can still flash custom ROMs (if the new bootloader behaves the same as the older ones).
I'm just curious if anyone with the new (unlocked) bootloader with S-ON can confirm this.
Click to expand...
Click to collapse
S-ON + Locked means that all partitions(other than data / sdcard) are write protected. The only way to write to the partitions is with an official OTA or RUU signed by HTC. The reason why "deleted" items return after reboot is because the deletion never actually occurred on the partition itself. It was temporary because the write was blocked by the security.
S-ON + Unlocked means that HTC removed the write protection from: boot, recovery, and system.
For HTC's official FAQ see my post immediately before yours.

illogos said:
To answer some people's questions unlocking with the HTC tool allows you to write to boot(kernel), recovery, and system. This means you can flash custom recovery and ROMs to your hearts content. You will still require official HTC signed updates to change: bootloader, radio, nv, pri, wimax, etc because technically you are still S-ON.
Here is the FAQ from HTC on unlocking the bootloader: http://htcdev.com/bootloader/faq
Click to expand...
Click to collapse
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done

.Elite_The_King. said:
Or get a stock(4.67-Android 2.3.5) ROM that has -Signature Verification disabled which will allow you to update the radios and such.
Is how it use to be done
Click to expand...
Click to collapse
thanks Cap. but I was not rooted before OTA. and after OTA there is no other way to root or flash custom ROM.

WIP Guide for achieving S-OFF after unlocking Bootloader with HTCDev.com
[GUIDE][WIP] How to achieve S-OFF after unlocking 2.18 HBOOT with HTCDev.com - No More Watermark! )
Still working on the details, but a shell of the instructions is there .

Tekn010933 said:
It's not that, it's the rooted version and stock de-odex/odex are already on the forum. Just waiting for the full rls of the RUU, rule of thumb from a great one(haus) "never update OVER THE AIR"(OTA)
Click to expand...
Click to collapse
DISCLAIMER: I'm a noob in this root world.....and enjoying the freedom to use my phone as I choose.
With that said, if you do not recommend updating OTA, then how would a person do such? I'm asking for my friends who are run stock on their phones.