Root [How To] Root 2.3.4/downgrade and Get S-off

[zepolyar]

Ok Thank you!

 

[funkpod]

question, i heard that verizon is sending out another OTA, over the air update for the Incredible.

Will that take away our root? do i definitely need to do this s-off in order to keep my root?

 

[sdrawkcab25]

question, i heard that verizon is sending out another OTA, over the air update for the Incredible.

Will that take away our root? do i definitely need to do this s-off in order to keep my root?

You won't be able to install the update if you are rooted(it will fail due to the custom recovery). Though, I'm sure it will be integrated into a stock rom that you can install.

 

[dhgilbert]

Hey everyone, I'm Doug... first time poster. AWESOME write up, Scotty.

Spoiler

I had a dinc previously to the one that's currently sitting in front of me... and when I think back to when I rooted the original one, I don't recall it being such a hassle (plug in the phone, run unrevoked, done). Maybe I'm just losing it in my old age.

Anyways... following this guide, I downloaded the modified USB drivers for windows and all of the extras that I'll be needing... however, when I go to update the Android 1.0 device with the modified drivers, I get an error message stating that the drivers ARE there but they cannot be installed because the hash file cannot be found in the catalog.

It should be noted that I am running the Win8 Consumer Preview. 64bit. However, I don't think that this is the cause of the problem.

Any advice?

Disregard. My problem does appear to be stemming from the fact I'm on Win8.
The drivers installed flawlessly on my Win7 machine.

Either way, thanks again Scotty for getting me through this!

 

[mtrott]

awsome! makes me happy its working for everybody without much issue.

i think later today,ill add to the second post a method that uses the new zergRush tool linked above,for the folks that dont care about a backup,or for some reason(like me) the old unrevoked wouldnt worked. i think the zergRush should work for everyone.

I am having trouble getting the zergrush tool from xda keep getting explorer cant display website requires me to login??

 

[MoebusNet]

Now that I've upgraded to a 4G phone to save my unlimited data & hotspot, my old Incredible is available to experiment with root (always too cowardly before). I use the Incredible on WiFi-only.

I'm running Ubuntu 12.04 64-bit, but all of the instructions I've read seem to be Windows-centric. I am definitely not any kind of Ubuntu expert, but I can follow directions and cut-and-paste in Terminal.

Do you have any recommendations for where I can find clear directions to root my Gingerbread Incredible using Ubuntu?

TIA

 

[scotty85]

I am having trouble getting the zergrush tool from xda keep getting explorer cant display website requires me to login??

the newest zergrush tool is included in the mini-adb_inc download in the OP. along with the newest clockwork.

Now that I've upgraded to a 4G phone to save my unlimited data & hotspot, my old Incredible is available to experiment with root (always too cowardly before). I use the Incredible on WiFi-only.

I'm running Ubuntu 12.04 64-bit, but all of the instructions I've read seem to be Windows-centric. I am definitely not any kind of Ubuntu expert, but I can follow directions and cut-and-paste in Terminal.

Do you have any recommendations for where I can find clear directions to root my Gingerbread Incredible using Ubuntu?

TIA

sorry,there is no specific guide that i know of. there are several generic writeups on getting adb working on ubuntu,and then a little bit of research on wether or not any commands need modded.

only prollem is that youll then be stuck with zergrush or htcdev,if that matters,as i do not believe we have a linux version of unrevoked 3.22

you could try sending this guy a message,looks like he used ubuntu. he may have some advice for you for getting it working: http://androidforums.com/incredible...2-3-4-downgrade-get-s-off-14.html#post3693785

 

[Pb_shutr]

Only if you want s-off (an unlocked bootloader). Which gives you the ability to change radios, hboots, downgrade system images, and modify system files while booted(like the build.prop).

If you just want root access, then you don't have to downgrade, but it is well worth the extra effort to downgrade and get s-off.

Unrevoked forever states the following about radio baseband versions and mine is not listed. Does this mean unrevoked forever will not work on my phone, and I am dead in the water? mine is 2.15.10.12.20.
Thanks
Supported Devices

At this time, the following devices are supported.

• HTC Droid Incredible, running radio baseband versions:
  • 1.00.03.04.06
  • 2.05.00.06.11
  • 2.07.00.07.16
  • 2.15.00.07.28
  • 2.15.00.09.01

 

[meep570]

Hi, I'm having a really tough time getting anything to work at this point.
My droid incredible had been replaced due to a defective charging port within the phone

The phone I have now uses 2.3.4

but the build number is newer than most people are posting on this thread.

I'm using 4.08.605.15

It doesn't seem to be syncing up to the unrevoked 3.21 or 3.22 at all

I'd really appreciate some guidance on where to go with this one

 

[sdrawkcab25]

Unrevoked forever states the following about radio baseband versions and mine is not listed. Does this mean unrevoked forever will not work on my phone, and I am dead in the water? mine is 2.15.10.12.20.
Thanks
Supported Devices

At this time, the following devices are supported.

• HTC Droid Incredible, running radio baseband versions:
  • 1.00.03.04.06
  • 2.05.00.06.11
  • 2.07.00.07.16
  • 2.15.00.07.28
  • 2.15.00.09.01

Correct, you need to downgrade your phone to 2.2 to get s-off.

 

[BABLESON]

Ok, I am TOTALLY confused here. I tried the first steps of even getting unrevoked to work and it said "unable to flash custom recovery image". I don't have HTC Sync on my computer. I just got 2 weeks ago an OTA update on my stock Incredible running 2.3.4 build number 4.08.605.15 710RD and radio 2.15.10.12.20

Do i have to downgrade before doing anything else?

 

[scotty85]

Hi, I'm having a really tough time getting anything to work at this point.
My droid incredible had been replaced due to a defective charging port within the phone

The phone I have now uses 2.3.4

but the build number is newer than most people are posting on this thread.

I'm using 4.08.605.15

It doesn't seem to be syncing up to the unrevoked 3.21 or 3.22 at all

I'd really appreciate some guidance on where to go with this one

Ok, I am TOTALLY confused here. I tried the first steps of even getting unrevoked to work and it said "unable to flash custom recovery image". I don't have HTC Sync on my computer. I just got 2 weeks ago an OTA update on my stock Incredible running 2.3.4 build number 4.08.605.15 710RD and radio 2.15.10.12.20

Do i have to downgrade before doing anything else?

you guys can try gaining temp root with zergrush(method in post 2),or with the htc supertool (htc supertool )

using the supertool to prep,then perm root may let you install rom manager,then clockwork if your main desire is to make a backup. with permanent root from htc supertool,you should be able to download and run titanium,also,wich will make resetting up easier.

or you can use the other thread to use htcdev unlock.

 

[meep570]

I tried the zergrush route
everything seemed to go smooth but superuser doesn't show up
and I still haven't got anything to unlock

 

[Hollowpint]

Hey everyone,

I have spent the last 2 days trying to get both of these methods working to no avail, and I have scoured the internet trying to find solutions to my problems.

I noticed that a lot of people who having been rooting their phones do not have the pink text at the top of their HBOOT that says "*** LOCKED ***", so I went out and found the htcdev location where I could download the software to unlock it. After hours fighting with that application giving me the 107 errror "no usb cord attached" I finally was able to downgrade my HBOOT to 1.02 (which I believe was needed for this).

So here is where I am at, and the questions I have.

1. At the top of my HBOOT it now says "*** LOCKED (oow) ***" which is what it changed to after using the htcdev tool. Is this where it should be? Or do I need to do something to fully unlock this first before proceeding to get root.

2. Trying to use unrevoked is either giving me "can not get root, firmware may be to new", or it is just sitting there saying "Waiting for reboot..."

3. Trying to use zergRush is giving me "[-] Hellions with BLUE flames !"

Baseband version: 2.15.10.12.20
Android version: 2.3.4
HBOOT version: 1.02

Thanks for any help!!!

 

[Hollowpint]

Hey everyone,

I have spent the last 2 days trying to get both of these methods working to no avail, and I have scoured the internet trying to find solutions to my problems.

I noticed that a lot of people who having been rooting their phones do not have the pink text at the top of their HBOOT that says "*** LOCKED ***", so I went out and found the htcdev location where I could download the software to unlock it. After hours fighting with that application giving me the 107 errror "no usb cord attached" I finally was able to downgrade my HBOOT to 1.02 (which I believe was needed for this).

So here is where I am at, and the questions I have.

1. At the top of my HBOOT it now says "*** LOCKED (oow) ***" which is what it changed to after using the htcdev tool. Is this where it should be? Or do I need to do something to fully unlock this first before proceeding to get root.

2. Trying to use unrevoked is either giving me "can not get root, firmware may be to new", or it is just sitting there saying "Waiting for reboot..."

3. Trying to use zergRush is giving me "[-] Hellions with BLUE flames !"

Baseband version: 2.15.10.12.20
Android version: 2.3.4
HBOOT version: 1.02

Thanks for any help!!!

Okay I was able to successfully unlock my phone using the instructions found in the htcsupertool. Now I am back to working on trying to get root with the instructions here or there.

 

[scotty85]

Okay I was able to successfully unlock my phone using the instructions found in the htcsupertool. Now I am back to working on trying to get root with the instructions here or there.

since youre unlocked,simply use the other sticky thread: http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html

i am starting to think it may be one of the most reliable means of achieving root and s-off,as both unrevoked programs seem a little "finicky" it worked very smoothly on my junk spare inc,on wich unrevoked 3.22 or 3.31 would not run.

just post on that thread if you have further questions

 

[scotty85]

Hey everyone,

I have spent the last 2 days trying to get both of these methods working to no avail, and I have scoured the internet trying to find solutions to my problems.

I noticed that a lot of people who having been rooting their phones do not have the pink text at the top of their HBOOT that says "*** LOCKED ***", so I went out and found the htcdev location where I could download the software to unlock it. After hours fighting with that application giving me the 107 errror "no usb cord attached" I finally was able to downgrade my HBOOT to 1.02 (which I believe was needed for this).

So here is where I am at, and the questions I have.

1. At the top of my HBOOT it now says "*** LOCKED (oow) ***" which is what it changed to after using the htcdev tool. Is this where it should be? Or do I need to do something to fully unlock this first before proceeding to get root.

2. Trying to use unrevoked is either giving me "can not get root, firmware may be to new", or it is just sitting there saying "Waiting for reboot..."

3. Trying to use zergRush is giving me "[-] Hellions with BLUE flames !"

Baseband version: 2.15.10.12.20
Android version: 2.3.4
HBOOT version: 1.02

Thanks for any help!!!

unfortunaltely,unrevoked can be finicky,and seems to have issue with some phones.

also unfortunately,hellions with blue flames indicate at some point an OTA patched the exploit zergrush used.

for those that dont want to use htcdev,you can try fre3vo. its worked on the thunderbolt,desire hd/inspire,and merge to get temp root.

i will try and get a more detailed guide up in one of the first posts,but in a nutshell:
downloload dhd downgrade folder

open the DHDDowngrade.zip file,then the folder contained inside of it. transfer "Fre3vo" into the mini-adb_inc folder with adb/fastboot.(ignore the rest of the files in DHDDowngrade,fre3vo is the only one you need)

run it with these commands in cmd,on a booted phone:

adb push fre3vo /data/local/tmp

adb shell chmod 777 /data/local/tmp/fre3vo

adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF

make sure it worked. when you see "exploiting device" then your command prompt again:
adb shell (if your prompt changes to a # youre good to go)

this is actually being run on a thunderbolt,but fre3vos use looks basically like this on all devices,with excpetion of the software version where the exploit region is:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Scott>[COLOR="Red"]cd c:\tbolt2[/COLOR]

c:\tbolt2>[COLOR="Red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxx    device


c:\tbolt2>[COLOR="red"]adb push fre3vo /data/local/tmp[/COLOR]
956 KB/s (9796 bytes in 0.010s)

c:\tbolt2>[COLOR="red"]adb shell chmod 777 /data/local/tmp/fre3vo[/COLOR]

c:\tbolt2>[COLOR="red"]adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF[/COLOR]
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
  id: msmfb
  smem_start: 802160640
  smem_len: 3145728
  type: 0
  type_aux: 0
  visual: 2
  xpanstep: 0
  ypanstep: 1
  line_length: 1920
  mmio_start: 0
  accel: 0
fb_var_screeninfo:
  xres: 480
  yres: 800
  xres_virtual: 480
  yres_virtual: 1600
  xoffset: 0
  yoffset: 0
  bits_per_pixel: 32
  activate: 16
  height: 94
  width: 56
  rotate: 0
  grayscale: 0
  nonstd: 0
  accel_flags: 0
  pixclock: 0
  left_margin: 0
  right_margin: 0
  upper_margin: 0
  lower_margin: 0
  hsync_len: 0
  vsync_len: 0
  sync: 0
  vmode: 0
Buffer offset:      00000000
Buffer size:        8192
Scanning region f0000000...
Scanning region f00f0000...
Scanning region f01e0000...
Scanning region f02d0000...
Scanning region f03c0000...
Scanning region f04b0000...
Scanning region f05a0000...
Scanning region f0690000...
Scanning region f0780000...
Scanning region f0870000...
Scanning region f0960000...
Scanning region f0a50000...
Scanning region f0b40000...
Scanning region f0c30000...
Scanning region f0d20000...
Scanning region f0e10000...
Scanning region f0f00000...
Scanning region f0ff0000...
Scanning region f10e0000...
Scanning region f11d0000...
Scanning region f12c0000...
Scanning region f13b0000...
Scanning region f14a0000...
Scanning region f1590000...
Scanning region f1680000...
Scanning region f1770000...
Scanning region f1860000...
Scanning region f1950000...
Scanning region f1a40000...
Scanning region f1b30000...
Scanning region f1c20000...
Scanning region f1d10000...
Scanning region f1e00000...
Scanning region f1ef0000...
Scanning region f1fe0000...
Scanning region f20d0000...
Scanning region f21c0000...
Scanning region f22b0000...
Scanning region f23a0000...
Scanning region f2490000...
Scanning region f2580000...
Scanning region f2670000...
Scanning region f2760000...
Scanning region f2850000...
Scanning region f2940000...
Scanning region f2a30000...
Scanning region f2b20000...
Scanning region f2c10000...
Scanning region f2d00000...
Scanning region f2df0000...
Scanning region f2ee0000...
Scanning region f2fd0000...
Scanning region f30c0000...
Scanning region f31b0000...
Scanning region f32a0000...
Scanning region f3390000...
Scanning region f3480000...
Scanning region f3570000...
Scanning region f3660000...
Scanning region f3750000...
Scanning region f3840000...
Scanning region f3930000...
Scanning region f3a20000...
Scanning region f3b10000...
Scanning region f3c00000...
Scanning region f3cf0000...
Scanning region f3de0000...
Scanning region f3ed0000...
Scanning region f3fc0000...
Scanning region f40b0000...
Scanning region f41a0000...
Scanning region f4290000...
Scanning region f4380000...
Scanning region f4470000...
Scanning region f4560000...
Scanning region f4650000...
Scanning region f4740000...
Scanning region f4830000...
Scanning region f4920000...
Scanning region f4a10000...
Scanning region f4b00000...
Scanning region f4bf0000...
Scanning region f4ce0000...
Scanning region f4dd0000...
Scanning region f4ec0000...
Scanning region f4fb0000...
Scanning region f50a0000...
Scanning region f5190000...
Scanning region f5280000...
Scanning region f5370000...
Scanning region f5460000...
Scanning region f5550000...
Scanning region f5640000...
Scanning region f5730000...
Scanning region f5820000...
Scanning region f5910000...
Scanning region f5a00000...
Scanning region f5af0000...
Scanning region f5be0000...
Scanning region f5cd0000...
Scanning region f5dc0000...
Scanning region f5eb0000...
Scanning region f5fa0000...
Scanning region f6090000...
Scanning region f6180000...
Scanning region f6270000...
Scanning region f6360000...
Scanning region f6450000...
Scanning region f6540000...
Scanning region f6630000...
Scanning region f6720000...
Scanning region f6810000...
Scanning region f6900000...
Scanning region f69f0000...
Scanning region f6ae0000...
Scanning region f6bd0000...
Scanning region f6cc0000...
Scanning region f6db0000...
Scanning region f6ea0000...
Scanning region f6f90000...
Scanning region f7080000...
Scanning region f7170000...
Scanning region f7260000...
Scanning region f7350000...
Scanning region f7440000...
Scanning region f7530000...
Scanning region f7620000...
Scanning region f7710000...
Scanning region f7800000...
Scanning region f78f0000...
Scanning region f79e0000...
Scanning region f7ad0000...
Scanning region f7bc0000...
Scanning region f7cb0000...
Scanning region f7da0000...
Scanning region f7e90000...
Scanning region f7f80000...
Scanning region f8070000...
Scanning region f8160000...
Scanning region f8250000...
Scanning region f8340000...
Scanning region f8430000...
Scanning region f8520000...
Scanning region f8610000...
Scanning region f8700000...
Scanning region f87f0000...
Scanning region f88e0000...
Scanning region f89d0000...
Scanning region f8ac0000...
Scanning region f8bb0000...
Scanning region f8ca0000...
Scanning region f8d90000...
Scanning region f8e80000...
Scanning region f8f70000...
Scanning region f9060000...
Scanning region f9150000...
Scanning region f9240000...
Scanning region f9330000...
Scanning region f9420000...
Scanning region f9510000...
Scanning region f9600000...
Scanning region f96f0000...
Scanning region f97e0000...
Scanning region f98d0000...
Scanning region f99c0000...
Scanning region f9ab0000...
Scanning region f9ba0000...
Scanning region f9c90000...
Scanning region f9d80000...
Scanning region f9e70000...
Scanning region f9f60000...
Potential exploit area found at address f9fd6200:e00.
Exploiting device...

c:\tbolt2>[COLOR="red"]adb shell[/COLOR]
# [COLOR="Blue"]<-indicates that you have temp root access[/COLOR]

 

[Hollowpint]

since youre unlocked,simply use the other sticky thread: http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html

i am starting to think it may be one of the most reliable means of achieving root and s-off,as both unrevoked programs seem a little "finicky" it worked very smoothly on my junk spare inc,on wich unrevoked 3.22 or 3.31 would not run.

just post on that thread if you have further questions

It worked!!! Thank you sooo much scotty, your a good man. I am not rooted with s-off!

One more thing though, can you spell out what s-off gives me, and what unlocking gave me just so I know the difference. I have seen explanations on them but I have never really understood what exactly they unlock.

 

[scotty85]

htcdev does not allow writing of boot from recovery,so seperate kernel flashes are neccessary. you only have access to boot/system/recovery so you cannot change radios or hboots and you cannot backtrack to older firmware.

s-off allows access to ALL partitions,and allows the boot image to be written from recovery. you can change radios,hboots,and flash older ruus if you wish. it allows more options to recovery a soft bricked phone.

in short, s-off is better.

with it comes greater responsibility. make sure you double and triple check md5s of any file that contains a radio or hboot,as a bad flash of those can leave you with a permanently bricked device

 

[garthbartin]

So everything was working perfectly and I checked all my MD5 hashes and they matched up correctly, but when I run unrevoked (after installing the proper drivers etc.) it goes through a couple reboots and then tells me that it failed to flash memory. I checked to see that htc sync wasn't installed etc. etc. and tried again. Same message. I switched to my dad's new computer which wouldn't have any programs conflicting with the process. Same error message. I tried it several times each time fiddling with things such as turning off Windows autoplay. Still no luck.

I searched this thread for advice and I simply saw the suggestion to switch computers. I can't seem to figure out the zergrush method, I can't find a download for the zergrush program and when I do it's a .c file that doesn't have the correct md5 hash, I feel like I'm doing something wrong. Can you help me with this?

Also, I haven't a decent computer knowledge, however I'm completely new to rooting phones so I am unfamiliar with all the jargon. My eventual goal is to install a WP7 rom onto my Droid Incredible.

 

[MrNoun]

So everything was working perfectly and I checked all my MD5 hashes and they matched up correctly, but when I run unrevoked (after installing the proper drivers etc.) it goes through a couple reboots and then tells me that it failed to flash memory. I checked to see that htc sync wasn't installed etc. etc. and tried again. Same message. I switched to my dad's new computer which wouldn't have any programs conflicting with the process. Same error message. I tried it several times each time fiddling with things such as turning off Windows autoplay. Still no luck.

I had the same problem, with the same specs as Hollowpoint (new phone replacement). After pulling my hair out changing computers, etc., and not being able to use either method 1 or 2, I ran the htcdev method and it worked flawlessly. Thanks Scotty for all of your time and patience!

 

[sdrawkcab25]

So everything was working perfectly and I checked all my MD5 hashes and they matched up correctly, but when I run unrevoked (after installing the proper drivers etc.) it goes through a couple reboots and then tells me that it failed to flash memory. I checked to see that htc sync wasn't installed etc. etc. and tried again. Same message. I switched to my dad's new computer which wouldn't have any programs conflicting with the process. Same error message. I tried it several times each time fiddling with things such as turning off Windows autoplay. Still no luck.

I searched this thread for advice and I simply saw the suggestion to switch computers. I can't seem to figure out the zergrush method, I can't find a download for the zergrush program and when I do it's a .c file that doesn't have the correct md5 hash, I feel like I'm doing something wrong. Can you help me with this?

Also, I haven't a decent computer knowledge, however I'm completely new to rooting phones so I am unfamiliar with all the jargon. My eventual goal is to install a WP7 rom onto my Droid Incredible.

Use this method instead:
http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html

 

[scotty85]

So everything was working perfectly and I checked all my MD5 hashes and they matched up correctly, but when I run unrevoked (after installing the proper drivers etc.) it goes through a couple reboots and then tells me that it failed to flash memory. I checked to see that htc sync wasn't installed etc. etc. and tried again. Same message. I switched to my dad's new computer which wouldn't have any programs conflicting with the process. Same error message. I tried it several times each time fiddling with things such as turning off Windows autoplay. Still no luck.

I searched this thread for advice and I simply saw the suggestion to switch computers. I can't seem to figure out the zergrush method, I can't find a download for the zergrush program and when I do it's a .c file that doesn't have the correct md5 hash, I feel like I'm doing something wrong. Can you help me with this?

Also, I haven't a decent computer knowledge, however I'm completely new to rooting phones so I am unfamiliar with all the jargon. My eventual goal is to install a WP7 rom onto my Droid Incredible.

im not sure i should continue to help you after knowing you want to run a wp7 rom instead of a beautiful android rom



all kidding aside,have you checked to see if unrevoked was able to install clockwork recovery? power the phone off,boot to hboot via vol down+power,and then select recovery from the hboot screen. does it take you to clockwork,or to a red triangle,!,and pic of a phone?

if you get clockwork,you can easily flash superuser 3.0.7 with clockwork,and be rooted. as ive said many times in the thread,the main reason to use unrevoked over another method is to get clockwork recovery installed.rooting is easy once you have a custom recovery.

if you dont have clockwork,and want to try the zergrush method,check the "download these files" step of the OP,and notice that the latest zergrush is included in the mirror. however it appears that at some point an OTA has patched the zergrush exploit(wich may also be why some are having trouble with unrevoked 3.21) so it may or may not work,dep on the state of your phone. if you do get the "hellions with blue flames" message above,you can try fre3vo to get temp root,im pretty sure it will work. directions are a couple posts up,youll just substitute the zergrush commands in post 2 for the fre3vo commands above.

wich brings us to:

Use this method instead:
http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html

im starting to change my mind about htcdev,in that it may actually be the most reliable way to root and downgrade,as its using htcs own unlock method. so far it has worked fine for the few that have used it,and went without a hitch even on my junk spare inc.

the disadvantages are:
-it may void all or parts of your warranty. while if the rooting is successful,all visual signs of htcdev can be removed(i.e. the relocked 1.02.0000 bootloader),the identigier token does contain bits of info uniquie to your phone,and could be kept on file at htc,and as such a warrantly claim could be denied because of it. while personally feel such a scenario is unlikely(htc has better things to do than search each phone it gets back for signs of being rooted),it may be possible and i accept no liabilitys. most incredibles are prolly old enuff that there is no mfg warranty left,anyway.

-it will wipe your data,it will wipe your data,it will wipe your data. did mention it will wipe your data? performing the bootloader unlock will perform a factory reset at the same time. no way around it,currently. at least none that is easy,that i know of.

just holler if you have further questions on any of the methods

 

[garthbartin]

Wooh it worked! However I'm not exactly sure what "it" was. I followed the HTC dev instructions and finished it with s-off and everything. Now I'm wondering, what's the best way to be able to dual boot Windows Phone 7 and my phones default ui?

 

[scotty85]

the original incredible does not have a ton of memory or ram,and i dont know of a good way to truly "dual boot" any 2 roms. you can easily swap back and forth by restoring nandroids if you want to switch back and forth between them. its fairly quick aND Painless,tho i might suggest using amon recovery if youre going to be doing alot of flashing/backing up/restoring.

have you actually found windows 7 roms for the incredible?if so i wouldnt mind seeing some links