Database Users

S-OFF perhaps unneeded?

I was wondering if it would be possible to flash a ROM without an S-OFF hboot. The logic is as follows:
The NAND lock is performed by the hboot.
Flashing is performed by the recovery OS.
We can now disable the NAND lock using a kernel module regardless of the hboot.
Could the recovery OS disable the NAND lock and flash a ROM without using an S-OFF hboot?
There are a few reasons against flashing the S-OFF hboot, namely, it's less risky, and easier to revert to factory if a warranty claim needs to be made.

Simple answer NO.
Long answer, you can't flash a custom rom without a custom recovery.
You can't flash a custom recovery without and unlock hboot.
So what ur saying will not work because u will not be able to flash the recovery.
Also no risk if u follow the steps. And reverting is as easy as running pc10img
Also this needs to be move to gen thread
Sent from my T-Mobile G2 using XDA App

Technically, you can probably use dd to reflash the recovery partition instead of hboot, which would allow you to install custom ROMs because the NAND is always unlocked in recovery.
But nobody is going to do that, and there are catches: even then you still can't write to /system without Android without the hack S-OFF is best.

I agree that S-OFF is best, but there might be people who are reluctant to flash an hboot. I figured ROMs can include the kernel module that disables the lock, so they would be able to write to /system.
If it's easy to restore to factory though, I guess there isn't much point in working around the lock all the time like that. S-OFF it is then.

If I missed it, would it be possible to go S-OFF, flash a custom ROM, then go S-ON again?

ok this is a debate i had going on in dz forum. you can flash clockwork recovery via rom manager and prob dd cmd after running the wpthis.ko. you can also perm root it as we know. it has been done in dz forum.
now i agree with you. at this point you should be able to boot into recovery and flash whatever you want and have perm root. however WP will still be on when booted into andriod which can be good and bad depending on how you look at it. (noobs vs pain in ass). this leaves u 2 options. reboot to recovery for any changes, or run the wpthis.ko make changes, reboot.
that being said. heres the prob with having s-on. if you screw up your phone you have less of a chance fixing it. (currently helping someone in this position).
ot anyone know of stock rom in update.zip format?

xile6 said:
You can't flash a custom recovery without and unlock hboot.
Click to expand...
Click to collapse
That's not true......i'm proof

Would need atleast a recovery which uses test keys or simply ignores them.
With the wpthis.ko u could dd other imgs but not enough for a rom as you can not access the system while you are on it.
If you had an S-off hboot u can atleast fastboot the images without the recovery.
Right?
Sent from my T-Mobile G2 using XDA App

[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.

Help Please...

i posted this here cause no one answers my Q&A posts, but here's the story - i was running CM7 on my phone and i was having problems with my phone and decided to restore to stock and unroot via PD15IMG.zip, but i didnt know how to undo gfree cause grankin's instructions are all over the place. so the PD15IMG.zip did it's thing but it says update failed and reboot. so i reboot and the phone goes to the android recovery, not the CWM recovery. what do i do to get back on track, cause its not bricked if i can go to the bootloader and recovery, right? im stuck

This may or may not be the issue, but what recovery version are you running?

TeeJay3800 said:
This may or may not be the issue, but what recovery version are you running?
Click to expand...
Click to collapse
well, it WAS CWM 3.0.0.6 but now it's the stock android recovery, i think i might try installin CWM by adb since s is still off...

I2IEAILiiTY said:
well, it WAS CWM 3.0.0.6 but now it's the stock android recovery, i think i might try installin CWM by adb since s is still off...
Click to expand...
Click to collapse
You can use ADB or even fastboot if you have the engineering SPL. Once you have a good recovery installed, it's just a matter of wiping everything and flashing a stable ROM. If CM7 didn't work well for you but you want Gingerbread and the plain Android look, try RoyalGinger.

TeeJay3800 said:
You can use ADB or even fastboot if you have the engineering SPL. Once you have a good recovery installed, it's just a matter of wiping everything and flashing a stable ROM. If CM7 didn't work well for you but you want Gingerbread and the plain Android look, try RoyalGinger.
Click to expand...
Click to collapse
i decided to reroot cause all roms i installed, even after clean wipes, would lag and be unresponsive at times. and what's SPL? i'm kinda new to the android game, but iphones and ipods are a different story...

I2IEAILiiTY said:
i decided to reroot cause all roms i installed, even after clean wipes, would lag and be unresponsive at times. and what's SPL? i'm kinda new to the android game, but iphones and ipods are a different story...
Click to expand...
Click to collapse
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.

TeeJay3800 said:
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
Click to expand...
Click to collapse
Or too much of a load for the CPU settings if he has it Under or over clocked... or a bad kernel (aka not one fauxs ;D )
Sent from my HTC Glacier using XDA Premium App

TeeJay3800 said:
The SPL is often referred to as "hboot" or "bootloader". It sounds like you're having enough trouble as it is, so I wouldn't worry about that. If you still have S-OFF, then you're still rooted. I honestly don't think that un-rooting and the re-rooting will solve your problems. It's possible your previous recovery was corrupt, that's why everything you flashed was slow (although apps and setups can also cause that). I would flash CWM 3.0.0.6 via ADB and then try another ROM.
Click to expand...
Click to collapse
how do i get adb to work in bootloader? cause it obviously wont in the android recovery

Nicgraner said:
Or too much of a load for the CPU settings if he has it Under or over clocked... or a bad kernel (aka not one fauxs ;D )
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
i've used faux's and grankin's...it's still bad

I2IEAILiiTY said:
how do i get adb to work in bootloader? cause it obviously wont in the android recovery
Click to expand...
Click to collapse
just kidding, i figured it out...
but when i try to use the method on unlockr.com (not sure if everyone does it this way) i cant navigate to adb via the command terminal

See here for instructions on setting up ADB. You can't use ADB while in your bootloader, that's what fastboot is for. ADB is done with the phone fully booted.

I2IEAILiiTY said:
just kidding, i figured it out...
but when i try to use the method on unlockr.com (not sure if everyone does it this way) i cant navigate to adb via the command terminal
Click to expand...
Click to collapse
alright, the problem right now is, i've figured out how to use usb on my f***ed up phone, but the drivers won't install, and adb is still being a pain in the arse.

I2IEAILiiTY said:
alright, the problem right now is, i've figured out how to use usb on my f***ed up phone, but the drivers won't install, and adb is still being a pain in the arse.
Click to expand...
Click to collapse
That doesn't tell me much. Do you get an error when running "htcdrivers.exe" during the setup procedure?

TeeJay3800 said:
That doesn't tell me much. Do you get an error when running "htcdrivers.exe" during the setup procedure?
Click to expand...
Click to collapse
lol, just kidding. i didn't see your post til i said that. alright, so do i type fastboot devices or whatever from the command menu and then install CWM?

I2IEAILiiTY said:
lol, just kidding. i didn't see your post til i said that. alright, so do i type fastboot devices or whatever from the command menu and then install CWM?
Click to expand...
Click to collapse
It is that simple, but only if you have the engineering SPL/hboot/bootloader. Towards the bottom of this post is instructions for flashing that.

TeeJay3800 said:
It is that simple, but only if you have the engineering SPL/hboot/bootloader. Towards the bottom of this post is instructions for flashing that.
Click to expand...
Click to collapse
yea...i didn't take the risk of flashing that when i rooted my phone...will i still be able to flash this recovery img?

I2IEAILiiTY said:
yea...i didn't take the risk of flashing that when i rooted my phone...will i still be able to flash this recovery img?
Click to expand...
Click to collapse
Yes, in fact fastboot is the safest way to flash things like recoveries. Once the SPL is installed, boot the phone normally, connect ADB, enter "reboot bootloader", once the phone has booted into the SPL enter "fastboot flash recovery recovery.img" and press enter. Just remember to have the IMG file in the ADB folder of your computer.

TeeJay3800 said:
Yes, in fact fastboot is the safest way to flash things like recoveries. Once the SPL is installed, boot the phone normally, connect ADB, enter "reboot bootloader", once the phone has booted into the SPL enter "fastboot flash recovery recovery.img" and press enter. Just remember to have the IMG file in the ADB folder of your computer.
Click to expand...
Click to collapse
so, in order to complete this, do i need the engineering hboot?

Only to do it via fastboot (the safest way). You can also do it from the terminal emulator while the phone is booted normally.

TeeJay3800 said:
Only to do it via fastboot (the safest way). You can also do it from the terminal emulator while the phone is booted normally.
Click to expand...
Click to collapse
my phone is still stuck in the boots and recoveries is the problem. i don't have the engineering hboot and when i try to flash the recovery.img it says writing recovery...failed

DEsire Z/G2 added to official bootloader unlock program

Didn't see this in General so thought it would be worth adding, especially since there have been many threads lately with new users wanting to root their phone and then getting scared of the guides.
Now there is also the option to go the official way to unlock the bootloader.
http://htcdev.com/bootloader/

noob here with a question... rooting is the same as unlocked bootloader??

coldsun15 said:
noob here with a question... rooting is the same as unlocked bootloader??
Click to expand...
Click to collapse
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.

thomas_wlc said:
Not quite. It can probably explained more accurately but the gist of it is this:
An unlocked bootloader is what allows you to flash custom roms to your phone.
Root access simply grants you the rights to mess with your phones rom whichever way you want.
Click to expand...
Click to collapse
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?

coldsun15 said:
so, basically whats this means is, now i dont need to root and s-off and stuff to be able to put CM7 (for example)?
Click to expand...
Click to collapse
I thinks that's pretty much it, once you have unlocked your bootloader you'll be able to flash any custom rom you like. Though it'll probably a bit tricky on the first go since you don't have a custom recovery yet, so I believe you'd have to flash some pc10img.
Still it's commonly to believed to be the better choice to stick with the more exhausting solutions posted around here, since HTC will register your phone if you use their tool. At least for the time being they claim that by using their way, your warranty will be void.

I've unlocked my desire z through the htcdev.com website.
Bootloader is unlocked, S-on..
But I can't get a rom installed, it gave me an error while trying to update from the recovery mode (apply update zip) using a stock rom with root.
Akward..
So now I've unlocked my bootloader, but still can't change my rom..
Anyone know how to do it after you've unlocked the bootloader?

flash custom recovery first, from there flash the rom

if you're s-on, bootloader is still locked....

artov said:
flash custom recovery first, from there flash the rom
Click to expand...
Click to collapse
I'm working on it
Gaining temp root using this guide worked.
http://forum.xda-developers.com/showthread.php?t=1178912
But when I press start clockwordmod, it says that my phone is not rooted..
While I press "flashcockwork" clockword mod recovery, I get an error.
än error occurred while attempting to run privileged commands!
I'm doing something wrong..
pretty annoying

I get unlock my bootloader today, and YES there is S-ON, but on the top is written in hboot menu big letters UNLOCKED (How you thinks, htcdev joke?).
I've installed clockworkmod using fastboot:
Code:
fastboot flash recovery clockwork_mod_for_vision.img
Then put off battery and turn on phone with volume down + power, I pressed 'recovery' menu option. Clockworkmod runs correctly. Then tried last stable CyanogenMod 7.1.0, flash was done without errors, I wiped out what's need (cache, data). Next I tried run phone, but freezes at splash (green htc letters on white background).
I tried also miui mod, but Ive got only MIUI splash screen nothing else.
Then I restored my htc from backup (done before flashing using clockworkmod) and Im still on the stock htc android 2.3.3.
Regards,
Mariusz
p.s Sorry for my poor english.

how can I install CM7 or other roms after unlocking the bootloader
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.

pentie said:
1. boot to fastboot mode, flash a custom recovery (recommand ClockWorkMod), power down the phone.
2. put your downloaded update_cm7.xxx.zip into sdcard, boot phone into recovery
3. choose in the recovery, first "wipe data", then "install update from sdcard", choose the zip file you just put in.
4. choose "reboot system"
that's all to go.
Click to expand...
Click to collapse
I did it, but CM7 doesnt boot.

rskainth82 said:
Hi,
I also unlocked using the official method of unlocking the bootloader. How can I get root and install CM7 now? Even to install clockwordmod its asking me root the phone.
Can someone help me out here?
Thanks...
RSK
Click to expand...
Click to collapse
flak999 said:
I did it, but CM7 doesnt boot.
Click to expand...
Click to collapse
Booting problem is mostly kernel related, do you have logcat output? (run "adb logcat" and boot the phone)
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
EDIT:
That was a EVO3D with UNLOCKED HBOOT, I believe you're having the same situation, try my method or may others make out a better perfect solution ? (not my own phone, I just helped with its owner, no time to dig the details)
Click to expand...
Click to collapse
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!

flak999 said:
Thanks men thats worked for me. First flash the boot.img from CM7.0.1 then run recovery and run update_cm7.0.1.zip. After reboot everything run corectly.
Once more thanks!
Click to expand...
Click to collapse
now I confirmed the UNBLOCKED HBOOT somehow blocks the CWM to flash boot.img
My Phone have a S-OFF HBOOT and i was considering flash it to the UNLOCK the last night, now it seems not worth the try ~

pentie said:
I encountered with the situation (w. another phone) that the recovery can't flush the boot partition during the recovery installation, I have to extract the boot.img file from the zip and flash it manually in the fastboot mode (fastboot flash boot boot.img)
Click to expand...
Click to collapse
My friend has an officially unlocked Desire Z as well and I gave him these instructions to try it out, he has the same boot problem (stuck at splash screen). Maybe this information should either be stickied or added to a faq until there is a real solution to the problem (unlike this workaround), updated cwm or something like that.
Anyway thanks for sharing this information.

HTC bootloader unlock tool is quite restrictive. It still leaves you S-ON, so you won't be able to flash a new hboot or radios.
I recommend avoiding it and using the current well-proven methods from the XDA Wiki.
Sent from my Desire Z running CM7.

Its working now...
Steps I followed:
1. flash recovery using fastboot
2. Do a nandroid backup using recovery
3. flash boot.img using fastboot
4. reboot into recovery
5. wipe data/cache
5. install update for CM7, and gapps
Also make sure before doing any of these steps you have copied CM7 and gapps update onto sdcard.
Thanks everyone for helping out.

I am experimenting with this myself and I don't seem to be having the same issues flashing a boot.img from an update.zip in ClockworkMod recovery with the official HTC unlocked bootloader that others are having. Maybe it is the version of the recovery that is the issue? Which version is everyone trying to use? I am using the 3.xxxx version that is linked from the wiki. I have had other problems with the 5.xxx version and tend to stick with the older version for that reason anyways.