Develop Bugs

[Q] Help w/ Warranty Replacement

I have to send my phone back for a warranty replacement because it won't charge the batteries. Anyways, I'm a bit unclear as to the exact steps required to return my phone to its stock conditions.
I restored my original nandroid backup (with 2.1-update1).
This is what I want to do:
remove root
restore the stock recovery
wipe all data to factory defaults
turn S-OFF back to S-ON
Is this the correct order to do these things? Am I missing anything?
I found how to do #2 at showthread.php?t=756850 and #4 is described on the Unrevoked Forever Wiki.
I do NOT know how to do #1 or #3.

Don't forget to format the internal Phone Storage. You can do that from in Settings.
You need Clockwork to flash S-ON, so do that before restoring stock recovery.

So, if I put back on the stock recovery, will I be unrooted?

Look?
This thread could have been found by searching. The only thing it did not cover is S-ON, which can be found on the unrEVOked forever FAQ
http://forum.xda-developers.com/showthread.php?t=732497

Thanks for your reply. I did multiple searches and have been reading for the last few hours, but obviously didn't find your helpful thread.
Any recommendations on which RUU would be best? Will it also flash my radio back to 1.x?
Thanks!

...
I would take the one right above the HBOOT .79 one ... because that would be the last one with HBOOT .77. I have gotten 3 Incredibles so far (2 warranty replacements for my original) and all 3 came with HBOOT .77.
Please note, that was written long before S-OFF so figure out where in the process S-ON should go.

Thank you very much. I'm downloading the executable now.
Just wanted to make sure that this won't brick the phone since I have a newer radio. Correct?
If I read the Unrevoked Forever instructions properly, I'll need to do the S-ON before running the RUU since the RUU will replace the rooted recovery with the stock recovery. Sound right to you?
Thanks again for your help.

YMMV
While YMMV, running a RUU in the ordinary course should not brick the phone (although pulling out the battery when you lose patience might). It will either run or it wont with your radio. There are other threads to downgrade if you need to.
The double-radio-flash issue was a one time thing when unrEVOked issued a radio ****PATCH**** in their efforts. Applying the Patch to a Patched radio would brick. That has nothing to flashing two radios, although it certainly morphed into that in the hearts and minds of the flasher community.

I think I have figured this .77 .79 HBOOT thang out.
if you had .77 then got the latest 2.1 update OTA you kept .77,
BUT the latest 2.1 RUU changes the HBOOT to .79, so if you got it OTA hboot stayed, if you did RUU you have .79
I think.

[WARNING] Do not flash a new official RUU/ROM/OTA if you have root and/or S-OFF

DO NOT FLASH A NEW RUU OR OFFICIAL ROM IMAGE UNLESS YOU *REALLY* KNOW WHAT YOU ARE DOING !
Sorry for shouting, but this is very important. Thanks to the mods for making this sticky.
The latest official RUU that has been released - http://forum.xda-developers.com/showthread.php?t=870369 - has been found to break the existing methods of rooting and getting full S-OFF.
This shouldn't be a big suprise, because when HTC saw that the amazing devs on XDA had cracked the existing security, we should expect them to put something even tougher in later releases.
So flashing any later release, whether that's an official RUU or just the ROM image (PC10IMG.zip) is a very dangerous thing to do until it has been fully tested and "cleared" by the devs here. i.e. your previously rooted and S-OFF'd phone might lose root and go back to S-ON, and be unable to be rooted and S-OFF'd again.
It's of course fine if your phone came with a particular ROM release to flash that *exact same* release back onto the phone if you want to return to stock. What I'm referring to is flashing a brand new release that isn't the one that came with your phone.
It's fine to flash custom ROMs of course, because those have already been tested out. In general, it's probably best to steer very clear of new official releases, and wait till the devs have pulled them apart and put any cool new stuff into a custom ROM. Then you know it'll be safe to flash.
Currently I don't think it's entirely clear what just flashing a new *radio* on its own will do, as opposed to the entire ROM/RUU. That's still being worked on. But steer clear of even that if you're not sure what you're doing or dont' want to take any chances of losing root/S-OFF.
Thanks for reading

Thanks for the heads up.

I flashed the ROM you mentioned.
For those who want to try:
Just remember to get REAL S-OFF using gfree before flashing it.
This provide you a medicine for regret. You can get back to WWE ROM using WWE RUU and root/recover your old ROM.

What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.

androidtoy09 said:
What is RUU? What is it to do with ROMs? Did HTC provide a change log for newer Radio? Or does anyone know what changes are , in the latest Radio?
Just to be clear. Don’t flame me for this please. I’m still learning just like many others in here.
Click to expand...
Click to collapse
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.

steviewevie said:
We don't have a changelog, no.
RUU is ROM Update Utility. It's a program to run on Windows (.exe) which flashes your new ROM for you, and holds your hand through the process. It's possible to extract just the ROM zip file from the exe so you can flash it yourself if you want.
The thing about the RUU and stock ROMs is that they will flash pretty much *everything* on your phone. So as well as a new system partition (the main stuff for Android), you'll probably get a new hboot, new radio, new recovery. Those *might* all have increased security which is a lot more difficult to crack. So generally you should not flash it until we know it's "safe" to do so, i.e. it can be re-rooted and S-OFF'd etc.
Click to expand...
Click to collapse
Ok, thanks for clearing it up. So, RUU is pretty much similar to the method RIM uses to flash its OS on the Blackberries.

Im a little confused here.. So just to clear some things up i hope someone will answer these questions i have.
I have the software on my Desire Z that it came with (1.34.405.5), which i've rooted, S-off'ed and installed another kernel for OC porpuses. This is working fine, but lets say that i wanted to try another rom .. After some time i decide to go back to the stock software and then update to the newest software, would that be a problem? And has HTC released some newer software than the one iam using?

If you flashed back to stock, that would be fine. But if you flashed a new official update (e.g OTA), then you run the risk of installing something that you can't root/S-OFF.
It is best to steer clear of any official upgrades until they've been checked by the devs here and been given the all-clear.
Given that the phone came with certain areas write-protected, and the devs managed to crack that, we should be expecting HTC to release an even more secure update.
Yes, there is a new ROM out, at the moment for Egypt, that seems to have increased security. It would not be a suprise if HTC rolled out similar security as an OTA update for all existing ROMs. Right now there is something in that Egypt ROM (probably the hboot, at the minimum) which mean existing permanent root and S-OFF methods fail. It may be this is easily cracked again, or maybe it will take some time, who knows.
Bottom line - don't apply any official updates to your phone if it is rooted/S-OFF or you plan to root/S-OFF.
Sent from my HTC Desire Z

perm-rooted g2 stock tmobile rom s-off
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.

blitz69 said:
ok, my question is....i perm-rooted my g2 and have s-off, does this mean that i cant except the new gingerbread OTA update? ive had my fill of flashing roms with my old windows phone.. att tilt, tmobile touch pro 2, and tmobile hd2. im not looking to flash my g2 with a new rom...no offense to the chefs. love there work. but i only rooted the g2 to get rid of the bs apps that tmobile and google added to the phone. and i thought i heard that wen u root the phone tmobile cant tell wen u tether, so there for no more throttle b/s but thats not true...i must have miss read. but i would like to stay w/the stock rom and still b able to install the Gingerbread OTA. please someone provide an answer for me or point me in the right direction. thank you in advance.... sorry if the answer is already provided somewhere and i over looked it, i tend to do that a lot.
Click to expand...
Click to collapse
The trouble is, HTC/T-Mobile don't want you to root and/or S-OFF your phone, because it's a lot easier to end up bricking the phone if you don't know what you're doing. They put greatly increased security on the G2/DZ/DHD when they came out, in order to help prevent this.
Now this security has been cracked, we can expect HTC/T-Mobile to try and increase security even further (e.g. closing loopholes that let our current methods of root/S-OFF work) in future updates.
So if you accept any future OTA, you run a high risk of accepting something that will lock you out of root and S-OFF, at least temporarily, and possibly permanently (depending on how good a solution they come up with).
If you are not bothered about root/S-OFF, then that's fine of course.
This doesn't mean that you necessarily have to switch to a custom ROM to get updates though. If you stay with the stock ROM (and I'm still on a stock ROM too right now), then just do not accept the update when an OTA comes out, and keep checking these forums to see when the devs say that they can root/S-OFF with the new version. When they say it's ok then you know you can apply the update and still get root/S-OFF.
This already happened with the G2. Very soon after release, but after rooting had been achieved, there was an OTA. Most people here decided to wait until the OTA had been looked at, and sure enough there was a small adjustment needed to the rooting method. But of course this OTA was before HTC had a chance to respond to the cracking of the security, so as I said, any future updates may well require a lot more time and effort from the devs to investigate and crack again.

Ok. Thank you very much

Will this muff up my phone if I factory reset it by using the Power+Volume Down option?

Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
What do you mean with gfree?
Is my waranty broken When i execute radio s-off?
Is it possible to make it radio s-on?

Yes,warranty is broken,but with the new gfree method
you can go back to S-ON:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

ericjosepi said:
Will this muff up my phone if I factory reset it by using the Power+Volume Down option?
Click to expand...
Click to collapse
If you do a factory reset then I think you'll lose root, but you can get it back again easily enough. The issue for this thread is flashing new updated stuff from HTC etc.

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
You might still need that backup, e.g. if you don't know what your old CID was and you want to un-do that bit too. I would keep it.
Sorry I don't think I understand your last question though, or why you say the uberroot method (I'm personally not keen on that name, it's just the usual method using Visionary/rage with gfree, not a new method) doesn't work.

Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
If you are only interested in permanent root you only need radio S-OFF and then it is sufficient to use
# ./gfree -s off
instead of
# ./gfree -f
in the following commands.
And gfree can now also be used to set radio S-ON by using the "-s on" option and to change the CID back to the original value be using i.e. "-c T-MOB010" if you want or have to go back.
Click to expand...
Click to collapse
But for CID (you mean SuperCid right?) I need the backup?
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

Thanks for the advice, I will stick myself with the current rom for a while

Ganii said:
Ok,so I can go back to S-ON with gfree commands from here:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
But for CID (you mean SuperCid right?) I need the backup?
Click to expand...
Click to collapse
Yes, I mean to go from your SuperCID back to your regular CID. You might not know what your original CID was.
And with the last question which you don`t understand,I mean
with flashing the HTC RUU 1.34.405.5 I don`t go back to S-ON
and original CID whether I use UBERROT method or this from here:
(Rooting the Vision (G2/DZ) and DHD)
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
Yes, if you flash a stock ROM then it won't affect your S-OFF and CID status (or SIM unlock). These are stored in your radio configuration partition, and not in any of the partitions which are overwritten by the ROM flash.

[Q] Undo old permaroot & S-OFF from pre-gfree, or update to new S-OFF?

Hi guys,
I've been reading through the forums over the past two days but I have to admit it's hard to find what I am looking for now that the G2 forum and the DZ forum are merged, and the search isn't getting me anywhere for this one.
I have Bell Canada Desire Z permarooted and S-OFF'd, with CWMod. I did this before the newer gfree method and from what I can gather this can lead me to some kind of endless loop if I try to flash back to the a Bell RUU or other RUUs for that matter. It also worries me that I can't try new radios, etc.
I am getting very poor battery life compared to others so I want to have my phone replaced. I have an extended warranty from FutureShop so I probably don't even need to reset the phone to stock again (they swap on the spot) but I would like to anyway. It will also allow me to test the battery again with the stock ROM.
So, how do I go about flashing back to the Bell ROM and turning S-ON, and unrooting? Keeping in mind that I used the pre-gfree method. I believe it was Visionary R12 and gtab's guide.
Also as the title implies, I was wondering if it's possible to use the new (better) S-OFF even if I am already S-OFF'd the old way?
Any help is appreciated!

You can use gfree and achieve "real" S-OFF without having to unroot.
Just run it. Worst that'll happen is it fails if you happen to be on a kernel it doesn't like. If this happens, no harm is done, just a reboot.

Just run gfree from where you are, as the previous poster said.
That will put you in a much safer position, where you can get stuck in that boot loop that you can if you've only got the eng hboot.
Then you can flash whichever ROM you want. Then you can undo gfree if you want via its new options (see the Wiki).
Regarding your point about the merger, IMHO this issue isn't anything to do with the DZ specifically, and lots of users are posting about similar stuff with their G2s. It's all the same

Thanks guys,
I've done gfree (which is MUCH easier than the thread and wiki make it look - they need to simplify the text, it's overwhelming to look at given how simple the procedure is) and flashed the Bell RUU.
Now I am just about to root, and use gfree to undo the S-OFF I guess?
Will let you know how that turns out. Thanks again!

Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!

Ganii said:
Ok,there is a new gfree method to get root and S-Off.
And gfree can now also be used to set radio S-ON.
But what about the backup "part7backup-1291675121.bin"
which gfree created at my sdcard?
No longer needed?
And with the new root and S-Off method,is it now possible to
to flash stock RUU 1.34.405.5 to get all original?
Because with old UBERROOT method this doesn`t work!
Click to expand...
Click to collapse
I'd keep that backup file as it is a dump of your original partition 7 before gfree mods it. You can dd i back and put everything back to how it was, if you ever need to. Do you need to keep it on the phone? No.. store it somewhere on your PC.
With the old "fake" S-OFF you would get stuck if you flashed a stock rom because it would overwrite the engineering HBOOT which was the only thing making your phone think it had S-OFF. With gfree method, you have real S-OFF, so this should be fine.
See http://forum.xda-developers.com/showthread.php?t=838484 for details.
tl;dr You should be fine.

Hm,little bit confused!
The backup I need to get original original partition 7
but not to get S-On.
To get S-On I can use the new gfree method,it`s now
possible with this!
I did the old UBERROOT method with real S-Off!
P.S.I read here about this:
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2

Not 100% sure I understand the question...but:
You don't need that backup file. If you delete it nothing bad will happen. Paranoid people (like me) would copy it to a safe place, but there's no real need.
You can flash whatever roms you like, including stock ones, as long as you have real, radio (gfree) S-OFF.

Hi guys, thanks for the help! I got it all settled, it was easy.
As I mentioned above, I used gfree to do a true S-OFF, which was easy.
Then I ran Bell's RUU and it worked without any issues. I assume the RUU install also flashes the HTC recovery back to the phone, I didn't check but it must..
A little summary for anyone who needs help in the future..
If you rooted/S-OFF'd using a method older than the current rage/gfree method (the one in the wiki) then you need to redo the S-OFF using gfree.
Steps:
Use gfree -f to S-OFF again
Run the stock RUU file on your pc (you need HTC sync installed for this)
Temproot (first part of the wiki guide) the stock ROM
Use gfree -s on to S-ON your phone
Reboot, and everything should appear like stock (aside from still being sim-unlocked).

Were u sucessful in returning your phone to htc after u did the above?

I didn't have to return it to htc, just to future shop, and it was fine.
Sent from my GT-I9000 using XDA App

[Q] Should I Upgrade SPL?

Hello all.
I rooted my G2 using the gfree method and all went well(I have S-Off). It was much easier then the process for my G1.
Current setup
HBOOT-0.82.0000
RADIO 26.03.02.26_M
Cyanogenmod 6.1.1
So my question is should I bother to update my bootloader? A friend of mine with a similar setup said I should upgrade but what additional functionality would I get? Anyway I hope this does not seem like a stupid question.

The Eng HBoot gives you fastboot capabilities. That's about it. If you don't really use fastboot, then there is no reason to flash it.

Thank you for the reply but Im confused.
When I go into the boot loader it says fastboot and it shows up if I do 'fastboot devices' from the command prompt. I thought that meant I have fastboot capabilities? Or am I misunderstanding something?

If you have the stock bootloader, you don't have privileges like "fastboot flash" capabilities. It will show up with "fastboot device" because you have the phone in fastboot. It's like in adb, doing "adb devices" will show it up, even if you don't have superuser privileges.
Hope that clears things up a bit.

Ok now I understand. Thank you for your patience.
Looking back on the root instruction on the cyanogen site now I see the section referring to replacing the bootloader.
Now I hear alot about flashing the wrong radio and bootloader versions. How do I know for sure the file on the cyanogen site (0.76.2000) is the correct one?

That's the one that I have on my G2

Side note. I was looking at the wiki on XDA and it has the Eng HBoot for the G2 listed as 0.84.2000 and the DZ HBoot as 0.76.2000 that are hyperlinked to download.
Correct me if I'm wrong, but aren't those two supposed to be switched? My G2 has 0.76.2000, which is what I used when I first achieved perma root using the rage method before gfree. This is also listed on the CM wiki. I am by no means an expert, but I thought the two HBoot's were not interchangeable between the two devices.
Anyone care to chime in on this to share some light? I would hate to start a thread for this question of mine to be answered.

Yes I noticed the same thing. XDA has 84.2000 and CM has 76.2000. Relevent links posted below.
http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
tazz, what radio version do you have? Id like to update my radio as well, hopefully it will clear up some issues.

My radio version is the one dumped from the RUU_Vision_Hutch_AUS_1.85.861.3_Radio_12.28h.60.14 0f_26.06.02.27_M_release.
It's found in this thread http://forum.xda-developers.com/showthread.php?t=959488
The instructions to flash with fastboot are there, as well as an update.zip, so you should have no problems there.

Regarding the engineering hboot;
The ONLY known brick was made by scotty2 by playing with hboot commands that are only available in the engineering hboot. In other words, it allows you more freedom to control the device, but at the expense of potentially REALLY f-ing it up if you mess with things that you don't understand.
With a radio s-off phone, you can save the phone from literally anything, even without the engineering hboot. As a matter of safety, the engineering hboot is *not required*. In terms of convenience, it is nice, as long as you don't go playing with things you don't understand.

Tazz. Thank you for the info. but should I upgrade the SPL before that installing that radio?

If you want to upgrade the radio through fastboot then yeah, you need to upgrade the spl first.
Otherwise, you can just update the radio through the update.zip in bootloader the pc10img.zip way, then you can do the spl upgrade.
Its really a personal preference.
Sent from my thumbs

tazz9690 said:
Side note. I was looking at the wiki on XDA and it has the Eng HBoot for the G2 listed as 0.84.2000 and the DZ HBoot as 0.76.2000 that are hyperlinked to download.
Correct me if I'm wrong, but aren't those two supposed to be switched? My G2 has 0.76.2000, which is what I used when I first achieved perma root using the rage method before gfree. This is also listed on the CM wiki. I am by no means an expert, but I thought the two HBoot's were not interchangeable between the two devices.
Anyone care to chime in on this to share some light? I would hate to start a thread for this question of mine to be answered.
Click to expand...
Click to collapse
santaclaws said:
Yes I noticed the same thing. XDA has 84.2000 and CM has 76.2000.
Click to expand...
Click to collapse
You were right I updated the XDA Wiki to reflect the correct info on the ENG. Hboot for the G2 which is 0.76.2000 and the DZ which is 0.84.2000. Good Catch.

joemm said:
You were right I updated the XDA Wiki to reflect the correct info on the ENG. Hboot for the G2 which is 0.76.2000 and the DZ which is 0.84.2000. Good Catch.
Click to expand...
Click to collapse
You're a good man joemm. Thanks for fixing things.

I went ahead and upgraded to the Eng hboot. No Brick. Yay!
tazz. occasionally my phone loses data connectivity. i can still make phone calls but no data. i notice if i kill the radio process internet works after the signal comes back. do you think an update to my radio would help this issue?

Yeah it could help it. I upgraded my radio and I get better data reception now than I did with the older radio version that I had.
I had the same problem, where I would have to reboot the phone to regain data. It still happens once in a blue moon, but not like it did before.

At least I am not the only one having that issue. Its a bit annoying.
The only "solution" I found was to make a simple gscript to kill all radio processes. Its quicker then a reboot. Not sure if killing the radio process has any negative effect but the phone seems fine after.
I just leave the shortcut on the desktop and use it whenever I need it.

dhkr234 said:
Regarding the engineering hboot;
The ONLY known brick was made by scotty2 by playing with hboot commands that are only available in the engineering hboot. In other words, it allows you more freedom to control the device, but at the expense of potentially REALLY f-ing it up if you mess with things that you don't understand.
With a radio s-off phone, you can save the phone from literally anything, even without the engineering hboot. As a matter of safety, the engineering hboot is *not required*. In terms of convenience, it is nice, as long as you don't go playing with things you don't understand.
Click to expand...
Click to collapse
Thanks for the info here, I had been searching this forum for at least 2 days now, looking for information on the eng-hboot and was it needed or not.
Being new to all this, could this eng-hboot vs hboot be on the wiki somewhere? My thoughts are that once I got my phone rooted and backed up I was trying to figure out what the next step was before flashing any ROM. I really don't want to mess up my phone.

From what I gather the main thing with the eng hboot is that it lets you do the fastboot commands.
and apparently it has other stuff that can also brick your phone lol

[Q] S-OFF... Again

Hi all.
I have a rooted wildfire with a custom ROM on HBOOT 0.80. As I'd like to S-OFF it, I searched for info, and at first it looked like I had to RUU it (with goldcard and all), and then use Revolutionary to do the trick.
Then I found this thread. Inside the file linked there there seem to be the correct HBOOT I need (1.01, same one as in the RUU) and a clear explanation of how to upload it, and I thought maybe it could be possible to just flash the HBOOT alone, without the rest, and then S-OFF the phone. In theory, this would cut the necessary steps quite a lot and allow S-OFF keeping the phone as it is.
The questions are, has anyone tried this procedure? If I do try and something goes wrong, will a nandroid restore of my previous setup also restore the old HBOOT, thus making the phone usable again?
Thanks!
Veon11

You can't use that method. Fastboot needs S-OFF by Revolutionary originally.

3xeno said:
You can't use that method. Fastboot needs S-OFF by Revolutionary originally.
Click to expand...
Click to collapse
It DID looked too easy...
Thanks for the quick answer.