yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] Grnlantern79:
This does work, but god I wish it was all ADB it was all so easy before unrevoked it didn't work the first time it gave me SU and root but no s-off then unrevoked would not run again due to new firmware. I did full downgrade to 2.2 and followed all directions ADB is so simple but unrevoked took 2 hours of just missing around to get s-off which included flashing 2.2 in hboot again starting over, running what I could run again in ADB without the gingerbreak since I was now on froyo, it was mostly just repushing the files and binary. But after all that unrevoked ran and gained root and s-off. Worst root I have ever done but people its all about making smart decisions before you do it if you make a mistake and get stuck, get help or trouble shoot but use you head before you battery pull and make sure you read before you hit anything.

If I helped you in any way please use the thank you button
[Droid Incredible General] scotty1223:
sorry you had such issue with unrevoked. usually thats the easy part ;) most folks are confused by adb and running commnads and wish it was all automated!

just a couple things that may help folks in the future:

-if you dont want to fool with unrevoked 3.22 in 3.2.4 use the "zergRoot"method in post 2. its all adb up to the downgrade. once you get to this point,you could easily roll yourself all the way back to the shipping firmware(assuming amoled screen) if you wanted,and then use an adb method(if one exists,im not that flamiliar with the inc). you dont have to go back to 2.2. i just picked that cause most folks are familiar with it,and with using unrevoked 3.32 to root/s-off it

-there have been a few complaints of unrevoked not giving s-off on 2.2. before you start,make sure "disable phone security" is checked in the file menu. if s-off still fails,but gives you root and a recovery,its worked for everyone thus far to just run the "forever" .zip in recovery,no real need to reflash the 2.2 ruu and run unrevoked multiple times.

-last and not least unrevoked is not ever going to give s-off in the 2.3.4(unless they release a new version for 2.3.4),as is uses an unsupported baseband,thats why the 2.2 downgrade is needed. folks that have no intention of backing up or returning to 2.3.4 and are fairly savy like the poster above,id strongy encourage to just use directions in post 2,its a lil quicker to not have to mess with unrevoked 3.22. its mainly included for the folks that want to make a nandroid or run tibu prior to the downgrade(plus zergRoot hadnt come out yet,when i originally put this together ;))

once your back on 2.2 you could even just use z4root to get get root access,install rom manager and clockwork,then flash the forever patch. once you can downgrade,there are alot of ways to skin the cat :D
[Droid Incredible General] chadster1976:
Worked after a few tries!

Thanks Scotty for this writeup. I thought for a minute that things wouldn't work, but a third try proved fruitful.

Here's a few tips that I can add to things.

Things failed for me at the restore 2.2 part - HBOOT would not recognize the zip file as correct.

I am on a Win XP machine... Format the sd card to fat 32 using something other than Windows - I used a little program called "fat32format.exe". Windows seems to have a problem formatting sd cards correctly, so that could have been it.

Once I made sure the sd card was formatted, I put the 2.2 zip (PB31IMG) back on the sd card and started over using the zergRush method.

If you have tried this before, you will have to remove two directories from the /data/local/tmp directory. These are sh and boomsh. Thanks to ieftm in this forum for this tidbit of info.

If your zergRush is giving you problems stating:

[-] Cannot copy boomsh.: Permission denied

Then use this method to fix as I stated in paragraph above: remove sh and boomsh

Once these directories were removed and the zergRush was completed, the downgrade commenced just as described.

Side note - Unrevoked 3.32 installed Unrevoked forever automatically onto my DInc, so there was no reason to do the additional forever installation. You may have the same results.

For anyone else that can't seem to get things working, the search is your friend. It took me a while of hacking away at things, but eventually they all turned up roses...

Good Luck! ;)
[Droid Incredible General] saosinalm:
problems install roms

I have a problen,I can't install a Rom error e: can't open/sdcard/primexl3d.zip, why?
[Droid Incredible General] chadster1976:
saosinalm:

First off, that's the wrong name for the downgrade zip according to the instructions that scotty posted above. Make sure the file is titled correctly and follow his instructions from beginning to end. I believe when mine succeeded my file title was "PB31IMG.zip" but in his instructions he leaves off the ".zip" at the end.

If there is an error in the process, you will have to start over from about step 3. You can't just start back from where you left off if you reboot the phone. Make sure you check your MD5's once you download, then you won't have to go back over that step.

I found the zergRush method easier, but I am more comfortable with adb...

I would suggest re-reading the instructions and following closely - he walks you through things really well.
[Droid Incredible General] epescina:
I have one question....

Why root a phone? I had my phone rooted and honestly it was a complete waste of time. NONE of the Roms I downloaded ever worked properly, the apps never worked, and it was nothing but trouble for me. My phone always "force close" my apps too. No offense to the developers I just didn't see a benefit.

Am I wrong?
[Droid Incredible General] chadster1976:
epescina:

That's really best answered differently depending on the type of person you are. If you like to play around and experiment with things or like learning how things work, maybe this works for you. Some people do it to get a custom look that no one else has, some do it to try and get better performance out of their phone that may have been bloated with apps out of the factory, and others are learning about developing apps and programming with it. Every person is different. Maybe it's just not for you, but others on this board can't live without it. To each his (her) own...
[Droid Incredible General] scotty1223:
what are you trying to do exactly? no part of this guide requires you to flash a rom. so if youre tryingto root,be more specific what youre having trouble with, and if this is just a general question about flashing roms,you might do some research and/or post a new thread where more people will see it :)
[Droid Incredible General] scotty1223:
i personally have the opposite experience. while there are a couple minor issues with the rom that i run,i feel my phone is faster and more pleasureable after root. i love htc phones,but hate htc sense,so i root mainly root so i can run AOSP based firmware.

but as was said,to each his(her) own :)
[Droid Incredible General] epescina:
I too hate the HTC Sense and wish I could change the overall layout of my phone. When I did load a new ROM that changed the layout it always seemed to be screwed up for one reason or another.

For example the lastest rom (Cyanogen) I absolutely loved but it didn't have market and I never could find out how to load it!
[Droid Incredible General] kjy2010:
Couple of quick questions (which might appear silly):

"place the PB31IMG of 2.2 on the root of your sd card. rename PB31IMG"

#1) What do we rename "PB31IMG.zip" to? The directions simply state to rename it.

#2) Move it to the root of the external sdcard or internal sdcard?

tia, and I hope these questions weren't too ridiculous. ;)
[Droid Incredible General] cmlusco:
It should be named PB31IMG.zip

It all depends how you rename it, if you use your pc it may not show the.zip extension if you have "show extensions" turned off. So on your pc it may just say PB31IMG even though it is really a zip. Sometimes when extensions are off people end up naming it PB31IMG.zip.zip wich will not work. It is best to have your pc show extensions you can do that by going to controll pannel / folder options / view tab uncheck hide extensions for known file types.
[Droid Incredible General] kjy2010:
wow lol ok, that just seems common sense, but I guess you never know who your audience is ;)

Which sdcard should the file be on?
[Droid Incredible General] cmlusco:
It should be on the removable sd not the internal storage if thats what you were asking.
[Droid Incredible General] kjy2010:
thanks again, just making certain. going for my third try now! ;)

---------- Post added at 01:20 PM ---------- Previous post was at 01:14 PM ----------

I'm getting an unmatched number on zergRush

"md5sums zergRush again,output stuff, then this number: 795275fb9c41ebd5b9fe7ab19108c52b"

I get "4bf71b766a9603fa7db98e71e3f3b470"

??:confused:

It states:

"*all those numbers must match exactly. if they do then you can procede."

What do you do if they don't match?

Sorry for the n00b questions, been dealing with nothing but HC since June. ;)
[Droid Incredible General] cmlusco:
I would try redownloading and then check it again. If its still wrong i would contact the op scotty and ask him, as he is the one who provided the original md5.
[Droid Incredible General] kjy2010:
thanks, d/l it three times already what a PITA ;)
[Droid Incredible General] cmlusco:
I get a md5 of

3cf8a3fbceb667121d91f4ef1a66684c

for the zergrush file in the zip and.

12c52b97e75e73595b325c03610b3380

for the zip it self, different than both of your guys.

Edit. I believe that the zergrush file has been updated since this post to include more phones so that is probably why the md5 is different.
[Droid Incredible General] cmlusco:
What is the current status of your phone?

s-on / off (on im assuming)?

stock or cwm recovery (stock im assuming)?

hboot version?

radio version?

can you boot to the os?
[Droid Incredible General] Pappy Drewitt:
S-on

stock recovery

hboot 1.02.0000

radio 2.15.00.07.28

The phone boots up and works completely normally right now
[Droid Incredible General] normanx:
Did you notice the first guy's radio was 07.07 and this guy has 07.28 with the same hboot? That is interesting to say the least.
[Droid Incredible General] scotty1223:
do you have the locked 1.02.0000 hboot? if so try unvevoked 3.22. check out this thread

edit: just noticed the above posts. the 1.02.0000 hboot is persistant. we downgraded all the way to eclair(should have been to .79 hboot) and the 1.02 refused to let itself be overwritten :eek:

check out the thread i linked for more info. the end result was he was able to get us-off with 3.22 on froyo with 1.02.0000
[Droid Incredible General] mynymyl:
I still am not getting superuser when I run either unrevoked 3.22 or trying zergrush through superoneclick. SOC did tell me I had root after declining to install busybox the second time around, but then again no su~ is it possible it is rooted just not installing the su.apk file?

I don't have the phone with me tonight but I will get the specifics on it and post them. I am sure the phone was S -on, 2.3.4 gb...
[Droid Incredible General] scotty1223:
to my knowledge super one click will not work on 2.3.4. you prolly can use the htc supertool,it does give you root via zergrush,but will not install a custom recovery.

after running unrevoked 3.22,are you left with clockwork recovery?
[Droid Incredible General] Pappy Drewitt:
I just got it rooted. I had forgotten that a while ago when I tried to root, I did the htcdev unlocker. So, all I had to do was roll back to 2.2, unlock the bootloader again, then run unrevoked with the clockwork img you provided. Im s-on right now but I still got cm7 flashed so, I might look into getting s-off this weekend.

Thanks guys
[Droid Incredible General] normanx:
Very cool.
[Droid Incredible General] BluesHawk:
Thanks for the great guide Scotty. I'm rooted and S-off :)
[Droid Incredible General] normanx:
Sounds good.
[Droid Incredible General] joot:
This guide have help me achieved root, gain s-OFF. Thank you very much Scotty...
[Droid Incredible General] izgil82:
adb device does not recognize my phone. What to do?

UPDATE:

It didn't work on my Windows 7 laptop but it worked flawlessly on my brother's Windows Vista desktop PC. It took me many hours to come to a decision to try another computer cuz it was simply not working on my laptop, lol. But I did it. Thank a lot for this thread!

So it looks like in order to root GB and gain S-OFF, you need to root GB first, then do command prompt things and only then the 2.2 zip file can be flashed in hboot giving the stock Froyo Rom. Then, you root it and use the unrevoked-forever zip file to flash it in recovery (at least I had to do so cuz reflash package didn't disable the security on my phone for some reason).

Thank you so much once again!
[Droid Incredible General] scotty1223:
so from the above post,i assume the issues in your PMs are no longer issues. glad you got them figured out :)
[Droid Incredible General] HSadler93:
I just downgraded to 2.2, I used the zergRush method.

I can't get root in 2.2 though, I used unrevoked 3.22 and set a custom recovery to CWM 5.0.2.0 but it says "failed to get root, is your firmware too new?".

It says i'm on Baseband version 2.15.00.07.28, Software Number 3.26.605.1

I've also tried SuperOneClick v2.3.3.0 and no luck there either.

INCREDIBLEC XC SHIP S-ON

HBoot-0.92.0000
[Droid Incredible General] cmlusco:
Keep trying unrevoked, sometimes it takes 3 or 4 tries before it works.
[Droid Incredible General] HSadler93:
Should I continue using CWM 5.0.2.0?

Would unchecking Disable Security and using the .zip later change anything?

UPDATE: I just unchecked Disable Security after Unrevoked (Still using CWM 5.0.2.0) failed 3 times total, I achieved root and installed recovery. Just flashed the Unrevoked Forever Zip for S-Off, and now i'm running CM7.

Thanks for all the help guys!!!
[Droid Incredible General] cmlusco:
Glad to hear you got it.
[Droid Incredible General] Kian0926:
i keep on receiving /flash_image: not found

this appears on cmd and i dont know what to do now:(

i estracted miniadb under c drive together with the other files including recovery-clockworld-5.0.2.0-inc

pls help:(
[Droid Incredible General] izgil82:
You don't need recovery-clockworld-5.0.2.0-inc for now.

Here's what you need to do (considering that your sd card is formatted as FAT32). Do exactly as I say.

1. Make sure you install unrevoked modified usb drivers according to the instructions on the unrevoked website.

2. Use unrevoked 3.22 to root GB.

At this point, you should have a rooted GB with S-On. Now, you need to flash stock Froyo. Here's how;

3. Place the 2.2 zip file in the root of your sd card (make sure to rename it to PB31IMG, though).

4. Place the mini-adb_inc folder (the one taken out of the zip file with the same title) into the root of your C drive

5. Connect the phone with the computer in Charge Only mode with Debugging enabled.

6. Open up command prompt window

7. Type this in exactly as you see below:

cd..

cd.. (yes, the second time)

cd mini-adb_inc

adb devices (now, for some reason at this point my comp wouldn't see the attached phone, so I had to use my bro's comp, as I mentioned above. If that's the case with you, try another computer)

md5sums mtd0.img

md5sums flash_image

adb push flash_image /data/local/

adb push mtd0.img /sdcard/

adb shell (from the original post; "your prompt should change to a #. if it changes to a $,then type su. Note that your phone may pop up a message asking you to allow permissions the first time you do this. if it does check "always" and touch "allow" on the superuser request on the phone screen.")

cd /data/local

chmod 0755 /data/local/flash_image

cd /data/local

./flash_image misc /sdcard/mtd0.img

exit

adb reboot bootloader

Your phone will now reboot to bootloader (hboot) and flash the 2.2 zip file which is Froyo. Don't do anything at this point. After it does its thing and the phone gets to the main screen, go to settings ->about phone to make sure that it says 2.2 there. It will be unrooted (this is why you need to downgrade from a rooted GB to the stock Froyo). Now, enable the usb connection as Disk Drive and remove the 2.2 zip file from the root of your sd card (cuz you'll return to hboot after that and you don't want it to waste your time scanning the file again).

Once you do so, disconnect the phone and open the unrevoked reflash package. In the file menu choose to add a custom recovery image, that's when recovery-clockworld-5.0.2.0-inc comes in. The package would root your phone, take s-off, and flash the new recovery. Once you add the image file to the reflash package, make sure that "Disable security on the phone" is enabled. Connect your phone back as a charge only with usb debugging enabled. The package would detect it and do it's thing.

Now, just like in my case it might not take the s-off for some reason (but it WILL root and apply the new recovery). In this case, go to the original post in this thread and follow the link where there's unrevoked-forever zip file that you flash in recovery. It's an alternative way to gain s-off.

You can now flash custom Roms.
[Droid Incredible General] mynymyl:
...Sorry this took so long for a response. The answer was no unfortunately. It would not install the cwm recovery either. I have the phone once again so I'm back at it tonight.

So finally posting what came of all this...making sure the correct 2.2 file was renamed to PB31IMG.zip worked through hboot and unrevoked 3.22 worked succesfully afterward to install root and cwm 5.0.2 ...

Flashing roms with ease now!

Thanks again @Scotty1223 for the guide and keeping the answers coming and also thanks to normanx for helping out some of us in the thread!
[Droid Incredible General] justjoe88:
my browser doesnt show a thank u button so THANK YOU!!!!!!!!!!!!
[Droid Incredible General] Shano56:
I keep getting failed to get root is firmware too new

I downloaded hboot drivers, unrevoked 3.32. I tried custom recovery, recovery that came with the program, and tried unchecking turn off device security. anything I missed?

I'm on latest firmware 4.08.605.2..

oh and running from win xp
[Droid Incredible General] scotty1223:
you are getting the error,as your firmware is too new. 3.32 does NOT work with gingerbread,you need to gain temporary or permanent root and downgrade to froyo so you can run unrevoked 3.32.

run unrevoked 3.22 on gingerbread,as described in the OP.

if for some reason you cannot get it to work(it has for most folks) then you can procede with the zerg rush directions in the 2nd post.

another option might be to use the htc supertool to gain root,then follow the steps to downgrade
[Droid Incredible General] SlimSnoopOS:
You need unrevoked 3.22 NOT 3.32. Did you download unrevoked from the OP?
[Droid Incredible General] Shano56:
I was doing this late last night, I didn't realize I had to use 3.22 specifically. Thanks guys, I'll try it out again.
[Droid Incredible General] SlimSnoopOS:
Hope that works out better for you. I almost never do any rom/root changes at night. I don't like troubleshooting in the late hours.
[Droid Incredible General] Shano56:
Yeah me too, but once I start something, I don't like to stop until it's done :p but I was also working on troubleshooting an app on one of my consoles at the same time so I was distracted
[Droid Incredible General] fuzzynco:
I want to be sure of steps

I have an Assurian refurb with hboot 0.92 & GB 2.3.4

When I tried to run unrevoked 3.22 it reported

that the firmware was too new.

I have the SDK installed along with the proper Win7 driver set

for Incredible 1. fastboot.exe (and .DLLs) and adb.exe

(and DLLs) are in the windows path.

Both fastboot and adb (in their various modes) see the device fine.

Do I push the 3 files (2 to /data/local, 1 to /sdcard) then

adb shell change the perms to 0755 for the flash program

run it, then reboot to hboot and let it run the PB31IMG.zip

to do the downgrade?

If I understand right, that should leave me with a Inc1 like it was originally

distributed with froyo and the right other matching partitions for unrevoked

to 'fix'.

Will unrevoked need its own cwm 2.x to run its scripts or can I tell it

use the cwm 5.0.2.0 img for recovery (to avoid having to fastboot

flash it separately)? :confused:

My intent is to have cwm 5.0.2.0 recovery and restore an nandroid

backup from the device that failed, (which also was s-off, 0.92,

and rooted 2.3.4).

For the old device, can I use this 2.2 image and s-on flash to return it to factory

so I return it to Assurian? I can access it (old device) from adb and fastboot

so I can push the image / script for 2.2 and s-on.

Thanks

Followup:

I needed to use zergRush to get root for prep

then I did the flash_image with its img file

and then rebooted to bootloader to run the 2.2

install. After rebooting to 2.2 I reran the reflash

and it complained I needed rom manager installed.

so I'm doing that to the 2.2 system so its there for the

recovery script to use. I didn't remember reflash requiring

rom manager ??

It seemed to complete, but hboot still says s-on.

I was able to restore my gb 2.3.4 nandroid backup

with cwm 5.0.2.0, which surprised me. i thought with

s-on and locked one couldn't restore boot, recovery

and system? Its rooted but s-on.

Anyway, it seems to be working, and the old phone

restored to stock froyo 2.2 for return.
[Droid Incredible General] scotty1223:
QUOTE=fuzzynco

I have an Assurian refurb with hboot 0.92 & GB 2.3.4

When I tried to run unrevoked 3.22 it reported

that the firmware was too new. try running it a second or 3rd time,in a row.

I have the SDK installed along with the proper Win7 driver set

for Incredible 1. fastboot.exe (and .DLLs) and adb.exe

(and DLLs) are in the windows path.

Both fastboot and adb (in their various modes) see the device fine.

Do I push the 3 files (2 to /data/local, 1 to /sdcard) then

adb shell change the perms to 0755 for the flash program

run it, then reboot to hboot and let it run the PB31IMG.zip

to do the downgrade? yes,but youll need temp root. either from unrevoked 3.22,zergRush,htc supertool,or even htcdev

If I understand right, that should leave me with a Inc1 like it was originally

distributed with froyo and the right other matching partitions for unrevoked

to 'fix'. correct

Will unrevoked need its own cwm 2.x to run its scripts or can I tell it

use the cwm 5.0.2.0 img for recovery (to avoid having to fastboot

flash it separately)? :confused: point it to 5.0.2.0,especially if you have an slcd inc now. youll get an error after unrevoked runs,but this is normal. it doesnt affect anything.

My intent is to have cwm 5.0.2.0 recovery and restore an nandroid

backup from the device that failed, (which also was s-off, 0.92,

and rooted 2.3.4).

For the old device, can I use this 2.2 image and s-on flash to return it to factory

so I return it to Assurian? I can access it (old device) from adb and fastboot

so I can push the image / script for 2.2 and s-on. yes. tho you dont really need to if its an assurion claim. they dont care,as long as youve paid the premiums and deductible.

Thanks

Followup:

I needed to use zergRush to get root for prep

then I did the flash_image with its img file

and then rebooted to bootloader to run the 2.2

install. After rebooting to 2.2 I reran the reflash

and it complained I needed rom manager installed.

so I'm doing that to the 2.2 system so its there for the

recovery script to use. I didn't remember reflash requiring

rom manager ?? this is the error i spoke of above. its normal.

It seemed to complete, but hboot still says s-on.

I was able to restore my gb 2.3.4 nandroid backup

with cwm 5.0.2.0, which surprised me. i thought with

s-on and locked one couldn't restore boot, recovery

and system? Its rooted but s-on. s-on doesnt really matter. you should be able to flash and restore with an s-on device just fine. if youre on froyo,wwith the froyo baseband,all you need to do is flash the s-off forever patch.

Anyway, it seems to be working, and the old phone

restored to stock froyo 2.2 for return.