Develop Bugs

Rooting with Visonary 14 killed me phone

I didnt think this was possible but I think I bricked my phone by using Visionary and permroot.
I clicked on the permroot, the icon went on, rebooted and got stuck at the HTC green screen.
After pulling the battery;
I tried doing a factory reset, nothing.
I tried a stock image of tmobile, nothing (at least I think I did this right)
ADB doesnt recognize the device in windows
I have only seen a red triangle and exclamation point after trying several posts suggestions.
I'm stuck on what to do, and have a replacement coming, but not soon enough.
Can I do anything with this? Like get the original Tmobile image back on? If so, how? I'm not the brightest bulb when it comes to this, as the g1 was so much easier. A bit of instructions would be great.
Thank you!

People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.

You didn't read the post which said you should not try to install the stock rom?
fastludeh22 said:
Ok mods, I know this normally isn't the place, but I think this is very important as I'm seeing more and more semi bricks, some of which are not recoverable without HTC signing keys!
So I ask you mods, please don't lock this, if anything it really needs to be a sticky!
That being said, if you are s-off, do NOT flash the signed offical PC10IMG.zip. if you don't have the correct rom on there when you do, as per the unroot thread you will get stuck.
Let me give u an example of what I've been seeing and why its happening so everyone understands. Example: you perm root/s-off your phone. You decide to do some rom playing. You end up boot looping and can't fully boot into android. So u say hey, ill reload pc10 and start over, WRONG.
What happens is s-off does no checks, sigs, version number etc. So when you load it up it starts to flash. Hboot(s-on) is first, then recovery, then radio. Thing is it has to reboot to do radio, so it reboots, at this point your s-on so it does a version check. "Main is older" then it quits before ever touching the system.img or boot.img. at this point you are locked. You have s-on, stock recovery, and can't boot android. Long story short, your screwed.
Now depending on the rom/kernel u had/have installed you may have adb access. At this point you have a small chance of recovering, which is better then some. I just spent the last 5 hours working with someone on a fix and think we got it, but the bat has died and will have to pick back up tomo. If this works or not, I also have one more idea we can try. I will update OP with any fixes we find.
*If your system was bootable when you started this, it may still boot. but you will be s-on, stock recovery, and still on whatever rom you were running. at this point you will have to hex edit to downgrade, or wpthis.ko if there is one for your kernel to get back to s-off.
*ive seen some people saying. i did it, it worked for me, but don't add any supporting info. this is bad for people new to android cause it makes them feel they will be ok. the only way this can work is if you have a version installed as old or older then the official img, or if you take hboot out of the update which then makes it no longer the official update. but my question is why are you flashing this? if you want to fully unroot, then follow the unroot guide. if you just want to go back to stock w/root, grab one of the stock w/root roms.
Long story short, do your rom flashing from recovery. Stay out of hboot unless you are following proven instructions to a T, or being walked though be a "pro". I hope this helps save some people!
* if you just read all this going DAMN, i already did that, then go here:
http://forum.xda-developers.com/showthread.php?t=842495
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App

@ddgarcia05 - that should be ok if he wasn't at S-OFF with the eng hboot though, which I don't believe that Visionary applies.

ibemad1 said:
People have been warned about visionary's high chance of bricking over and over again and that they should just use the rage method but they can't seem to get it.
Also: you do realize that the nand lock was to prevent this exact thing: people bricking their phones then returning them hoping to get them replaced. If it doesn't get replaced then you full well deserve it for not reading the countless posts about people bricking their phones using visionary.
First off: are you s-off?
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I checked and it said S-On and this was in recovery

ddgarcia05 said:
You didn't read the post which said you should not try to install the stock rom?
Sent from my HTC Vision using XDA App
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
ADB doesnt recognize the device in windows and this was also in recovery

Anyone? Bueller?

cwis said:
ADB doesnt recognize the device in windows and this was also in recovery
Click to expand...
Click to collapse
Check out the adb guide at http://forum.xda-developers.com/showthread.php?t=865685
If you install the HTC Sync software, as mentioned in that guide, that should give you the drivers that you need.

This looks bad. Being that you're new. this can be very bad.
You have three choices:
1: study each thread about Bricking G2.
2:find a more experienced person to help you unbrick your phone.
3:find a very strong magnet and place it on your phone leave it there for an hour and bring it back.

How do I get S-Off

I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App

Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.

ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.

What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?

KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z

steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside

I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z

steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...

schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App

Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul

Can't s-off alpharev

Hi guys I'm trying to s-off using alpharev ISO disc...it goes through the process then after rebooting stage 3 I get 4 lines that say unary operator expected ... I shut down pc and phone boots as usual...
I'm running rxmix s v1.1

maybe change to stock ROM and try s-off again

Yes like the post above switch to a ROOTED stock froyo rom worked for me, the reason your getting errors is because the rom you are running has probably got data2whatever, data++ ect... this affects the alpha rev process.

Ditto above. Alpharev doesn't work on a2sd or similar ROMs... Look back a couple pages and you'll see I started a thread with the same issue. I'm on IC GB a2sd+...
Once pc is repaired, I plan to load stock Telstra RUU and try again, then re-root...

bailz2506 said:
Hi guys I'm trying to s-off using alpharev ISO disc...it goes through the process then after rebooting stage 3 I get 4 lines that say unary operator expected ... I shut down pc and phone boots as usual...
I'm running rxmix s v1.1
Click to expand...
Click to collapse
First, you better use USB stick instead of a disc, it is faster a more reliable.
Secondly, you won't be able to get s-off unless you flash either stock rom or AOSP rom ( oxygen worked for me without any problems).

mikeraul said:
First, you better use USB stick instead of a disc, it is faster a more reliable.
Secondly, you won't be able to get s-off unless you flash either stock rom or AOSP rom ( oxygen worked for me without any problems).
Click to expand...
Click to collapse
+1, I s-off my phone with oxygen running on it.

ThaNx everyone for the help will try it that way and let you all no if it worked
Sent from my HTC Desire using XDA App

thanks everyone for the help it worked fine now i have fully rooted and s-offed htc desire...now to get back into the flashing fun.
When the moderator reads this i have no problems if this thread is deleted thanks again

bailz2506 said:
thanks everyone for the help it worked fine now i have fully rooted and s-offed htc desire...now to get back into the flashing fun.
When the moderator reads this i have no problems if this thread is deleted thanks again
Click to expand...
Click to collapse
Happy to hear

Hi folks. Writing this without any hope that someone is online at the moment.
I'm currently using alpharev to flash HBOOT on my htc desire. It has stucked on step 3 with two lines on phone's screen:
Aplharev SPLBOOT version 2.0
...
Normal NAND detected. Non-PVT4
and keeps hanging like that nearly an hour already.
The phone is rooted, with Clockworkmod recovery and InserCoin 2.0.1 DATA2EXT ROM installed.
Did anybody have the same behaviour while flashing HBOOT?
Should I be patient and wait for some miracle to happen?
thanks in advance.

Are you S-Off already??

use the new S-OFF utility. It's a lot quicker and easier. Just make sure you uninstall HTC Sync, or at least make sure it isn't running.

777ace said:
Are you S-Off already??
Click to expand...
Click to collapse
no...
just saw here an advice to wait for a long term and the to pull out the battery and reboot.
did as he said.
device is rebooting in fastboot mode...
will try to restore previous ROM from recovery mode...

n0vice said:
no...
just saw here an advice to wait for a long term and the to pull out the battery and reboot.
did as he said.
device is rebooting in fastboot mode...
will try to restore previous ROM from recovery mode...
Click to expand...
Click to collapse
try it with the new utility.. it should work for you..

finally I've restored my previous ROM (and sh*tted a pile of bricks during this hour).
HBOOT screen says that my device is still S-ON. strange... maybe that's because of 'DATA2EXT' ROM onboard.
bortak said:
use the new "...revolutionary.io/" S-OFF utility. It's a lot quicker and easier. Just make sure you uninstall HTC Sync, or at least make sure it isn't running.
Click to expand...
Click to collapse
thanks. I'll try it when my hands will stop shaking

You won't be able to alter HBoot without S-Off...
I am not sure how the new Utility that bortak linked to works, but I know that the "old" alpharev will not S-Off if you are using A2SD/D2SD/D2EXT type ROMs. You will need to flash stock RUU (do not use latest GB update RUU!!!), or one of the AOSP ROMs, such as Oxygen, before proceeding.
Once you have S-Off, you can go back and re-root, then upgrade your HBoot etc.

777ace said:
You won't be able to alter HBoot without S-Off...
I am not sure how the new Utility that bortak linked to works, but I know that the "old" alpharev will not S-Off if you are using A2SD/D2SD/D2EXT type ROMs. You will need to flash stock RUU (do not use latest GB update RUU!!!), or one of the AOSP ROMs, such as Oxygen, before proceeding.
Once you have S-Off, you can go back and re-root, then upgrade your HBoot etc.
Click to expand...
Click to collapse
thanks. I'll follow your advice.
I'm still wondering, why TUT-makers didn't mention this A2SD/D2SD/D2EXT ROMs inconsistency.
I think this should be written in large letters on the first line for noobs like me

Lol, you're right on that!!
If you look on alpharev site, it is mentioned in the text, but VERY small!
Requirements:
The only requirement right now is that the ROM you're running is rooted.
As techniques such as 'data2ext' have been popping up, these might disturb our finely-tuned flashing process.
Please revert to a rooted stock ROM if possible. Your /data partition is used for temporary storage of important files.
Click to expand...
Click to collapse
I missed it the first time also, had lots of dramas, and finally spotted that note after many frustrating hours. It should have been written in bright red, 72 cap at the top of screen!!

You need to use an a2sd Rom like lee Droid 2.5.
Alpha rev state this at start of web page using data2sd can cause problems.
Flash lee Droid 2.5 and try it again, you should be fine
Kind regards
John
Sent from my HTC Desire using XDA Premium App

It is being said on Alpharev website under "requirements".
Though I agree it should be said in tutorials too.
n0vice said:
thanks. I'll follow your advice.
I'm still wondering, why TUT-makers didn't mention this A2SD/D2SD/D2EXT ROMs inconsistency.
I think this should be written in large letters on the first line for noobs like me
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App

simi brick?

I have hw 003 hboot 2.10. I can enter hboot but not recovery. during normal boot phone just shows evo boot screen and boot loops. same thing when I try to enter recovery. I was s-off but after trying some methods in other brick threads I ended up with s-on.
I was using miui 2.2.3 when I turned it rebooted into recovery to make a nand and that is when the loops started. I have tried several ruu's with no luck on getting it to boot. was going to try the lastest ruu but not sure if I should.
I am flashed for cricket so there is not the option of bricking and returning to sprint for a replacement.
Edit: was not using twrp. Ar 2.3 was my recovery. As stated earlier I tried several ruu's in pc36img.zip.

If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.

sitlet said:
If you can get to hboot you are not bricked. Have you tried using a pc36img of a stock rom in the hboot? This should boot you to a stock rom, thus allowing you to re-root and get your recovery back.
Click to expand...
Click to collapse
You can be bricked and still get in hboot Twrp2.0 did it to a few phones, the partitions end up screwed up and you can boot to hboot but no recovery or system not sure which partition gets borked but I think its the misc partition
We are legion, for we are many

Where is Captain_Throwback to save the day and another evo once again

Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?

stevovanburen said:
Oh I am sure Captain will save the day soon as he always does.
That does not sound like fun man, sometimes the evos get crazy and there is nothing you can do about it. Did you do anything different before you had this issue? flash any files, adjust any system settings or mess with the hardware in anyway?
Click to expand...
Click to collapse
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App

You weren't using twrp2.0 were u? If you were more than likely SOL that's one of the main reasons twrp for the evo is no longer supported even tho it works great on other devices like the kindle fire and 3vo I use it on the KF which I have running cm9 which I just got running on the evo as well now I gotta get my kernel fixed for this thing, have you tried reflashing your recovery? Or using adb to push a boot.img
Sent from my PC36100 using xda premium

evo4gnoob said:
Where is Captain_Throwback to save the day and another evo once again
Click to expand...
Click to collapse
I know. Captain has become the shaman of the Evo. He needs a special title, like Honorary Genius, or something.
sent from AOKP heaven

You guys flatter me .
I don't have any experience with MIUI, though. It's the one ROM I've never tried, but if it's an AOSP ROM, then the bootloop of death is always a possibility.
We haven't had any success rescuing anyone in that scenario, unfortunately. Flashing the ENG HBOOT will allow you to run fastboot commands, though, so that's probably the first step if you want to flash stuff through fastboot.
If you can't get adb working, then there probably isn't much hope. Since you ended up S-ON, and now without a custom recovery, I don't think there's much you can do. Perhaps others with a similar issue can chime in, but as far as I know, there's no current solution. The only way I'd know for sure is having the phone in my hands personally, but I doubt that's a possibility. I haven't personally experienced this bootloop thing, but it sounds scary .

jlmancuso said:
No i had been running miui for a few days and was getting prepared for the next update by doing a nand. I rebooted to recovery with the reboot option in the rom. Then bang boot loop city here i am. Just tried the newest ruu pc36img.zip and still nothing. Going to get it unlocked later and see if I can reflash .img files through fastboot.
Sent from my M865 using XDA App
Click to expand...
Click to collapse
Ok so I have unlocked the bootloader from the htcdevelopers site and i can now use fastboot commands and have tried flashing the recovery. I see it load and write to the phone only thing is that it makes no difference. I still just get the boot loop.

Hate to say it, my friend, but I think it's the end of the road for that phone

HipKat said:
Hate to say it, my friend, but I think it's the end of the road for that phone
Click to expand...
Click to collapse
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.

jlmancuso said:
maybe but i will keep trying till the phone catches fire in my hands. I dont know the meaning of "quit". I read last night in a xda thread about a possible fix by this guy and some people said it would just brick the phone and others say it works. only thing is i have been unable to find that thread again. it had a link to some evo.docx file.
Click to expand...
Click to collapse
I assume you're referring to this thread: http://forum.xda-developers.com/showthread.php?t=1480630
Have fun trying! Many have tried, and I think only 1 ever succeeded.

thanks captain.

capn, thanks for the link! I've had that README_EVO.docx file on my SD for god-knows-how-long and have always wondered where in the hell I got it lol (and 'why').
@jlmancuso
Good luck, but condolences as well. My $ says, if Cap'n can't fix it, it likely can't be fixed (on Evo). Seems that guy has explored every RUU, Hboot, recovery, NV, Radio, kernel etc. He could probably BUILD an Evo, HW and SW lol.
sent from AOKP heaven

Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??

fatalfury said:
Captain throwback just the person i want to see lol i have a evo with 2.18 hboot
with s-on the phone keeps boot looping wrote the wrong nv to the phone now its boot looping also used the latest ruu top no avail still boot loops now is there a way i can repair the nv please help me with your guiding light and also this phone is not rooted or no roms its all stock also says in purple at the top ***LOCKED (00w) *** what ever that means ??
Click to expand...
Click to collapse
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
EDIT: This is the thread - you'll probably want to read the whole thing, and if you have issues, maybe you can PM the guy that got it working.
The potential problem I see for you is that you're S-ON and bootloader is locked. You're probably going to have to unlock your device with HTCDev.com before you can make any headway. How were you able to write NV items to the phone? Don't you have to be S-OFF to do that?

Captain_Throwback said:
I think someone else was able to fix this problem . . . there's a thread around here somewhere. I'll try and find it.
Click to expand...
Click to collapse
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?

evo4gnoob said:
i remember you had them downgrade to the ENG hboot and they were able to use fastboot to change the NV ?
Click to expand...
Click to collapse
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.

Captain_Throwback said:
Yup. I updated my post above with the thread, but that guy was S-OFF, so it was actually possible. Not much you can do with S-ON and locked bootloader.
Click to expand...
Click to collapse
use HTC dev to unlock then use your guide to downgrade then root with revolutionary then downgrade hboot ?

Install recovery without S-OFF?

I was wondering if it was possible to install e.g. CWM or 4ext Recovery without actually S-OFF'ing the Desire?

AFAIK impossible

Even with htc-dev unlock?

Unrevoked can do it, though you'll be stuck on a really old cwm. So better just s-off and install 4ext after.
Gesendet von meinem HTC Desire

I dont know what are you thinking about. Having S-ON is like a pain in the *** tbh.
By doing S-OFF you only gain - this removes every limit HTC imposed on your phone. I know this takes some risk, but if you done this, you will get more control over phone and it will be more secure as you will be able to use your favourite recovery as well as fastboot.
I'm not worried anymore until i have S-OFF'ed my phone. Flashed hboot, radio, recovery, boot partitions many times via fastboot and once it even saved my phone as i couldnt boot into android and i was using broken recovery. Due to S-OFF i could flash new recovery, then copy to sd and flash new android via it.

why do people reply when they don't know or can't help??
Yes you can.
Run unrevoked, in options select custom recovery, then you can use 4ext, amon ra etc. clockwork is fine but a bit usb brick prone. It'll flash the recovery in the process. To be honest you may as well soff.
4ext is the best really.

backfromthestorm said:
why do people reply when they don't know or can't help??
Yes you can.
Run unrevoked, in options select custom recovery, then you can use 4ext, amon ra etc. clockwork is fine but a bit usb brick prone. It'll flash the recovery in the process. To be honest you may as well soff.
4ext is the best really.
Click to expand...
Click to collapse
Thank God... finally one who knows

It might be me who has misunderstood, but isn't it correct that with s-on, it is always possible to recover a brick, while with s-off, in some cases it would be impossible?

numb92 said:
It might be me who has misunderstood, but isn't it correct that with s-on, it is always possible to recover a brick, while with s-off, in some cases it would be impossible?
Click to expand...
Click to collapse
When you screw up your phone for some reason, having s-off is more of an advantage in getting it fixed...
via xda app

kotag82 said:
Thank God... finally one who knows
Click to expand...
Click to collapse
Actually thank research, xda, me, maybe even Alan Turing, but thanking a non existent celestial dictator is a wasted thank you. ;-)

Okay, so I now have CWM with S-ON, if I decided I would like S-OFF at a later point, how would I go about doing this?

alpharev. google that.

don't know why you are all so eager for S-OFF.
i use CWM, sandvolds ICS and a 2GB ext4 partition - all with S-ON and i have not a single reason to complain.
until now i have not experienced an error due to S-ON.
it might have some advantages, but for me it's fine that way.
just wanted to let you know it's very possible.

BU7CH4 said:
don't know why you are all so eager for S-OFF.
i use CWM, sandvolds ICS and a 2GB ext4 partition - all with S-ON and i have not a single reason to complain.
until now i have not experienced an error due to S-ON.
it might have some advantages, but for me it's fine that way.
just wanted to let you know it's very possible.
Click to expand...
Click to collapse
Until you have to flash an ruu that's not for your cid because the correct one isn't available.. Or get an lcd brick, or want to change hboot, etc etc.. being s-off can mean the difference between a phone and a paper weight.
Hence why devs spend so much time and energy seeking exploits to enable it on just about every HTC.

yeah, sure. it has its advantages, but points you just mentioned don't apply to me.
i'm planning to stick with this rom i currently use. it runs perfect in every way.
so i thought like "never change a running system".
i know, that quote is very inappropriate here at xda
but i'm just kind of afraid that i will only make things worse, when i s-off now.
all i've been tryin to say is that s-off is not absolutely neccessary.

Then you will not realize the potential that your phone holds. Being S-OFF is not aBsolutely necessary for the people who don't wish to know their phone.