yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] fuzzynco:
Wondering about mismatched kernels and /system?

wouldn't mismatched (2.2 vs 2.3) kernel's cause it fail. It seems to be working

right, with the cwr 5.0.2.0 that reflash stored there. Would I do better to

fastboot boot the recovery, system restore then reboot to the restored system?

Where can I find the s-off patch (the recovery flashable)? The website

only offers reflash 3.32

Would the fastboot boot thing work for an AmonRa style restore on Rezound

with its unlocked hboot & s-on status? So as not to need to separately restore

the images that restore can't restore running from the recovery partition?
[Droid Incredible General] scotty1223:
you are better off just becoming s-off ;) once you are s-off,you can use the unlockedhtcdev hboot along with it,as it does offer the fastboot boot and fastboot flash. i use it with all my devices that a real eng hboot is not available for.

the forever patch is linked in the OP,sir. but here ya go again: http://unrevoked.com/rootwiki/doku.php/public/forever :)

yes it would. this is exactly what i do on my rezound. i generally dont even bother keeping a permantly installed recovery on it. im perfectly ok with hooking my phone to the computer to launch recovery. :)
[Droid Incredible General] fuzzynco:
Where do I get the hboot that supports the added functions of fastboot?

ok - i got the s-off patch now.

Where do I get the hboot version that supports

fastboot boot? I have hboot 0.92 on Inc1.

I'll redo the downgrade to 2.2 again and attempt

the standalone s-off.zip patch. I'm concerned about

my current state (hboot locked + s-on) and the

restore from CWM recovery 5.0.2.0 that reflash

put there, may not have properly restored the

restricted partitions. The 2.3.4 os boots fine and

seems to be running, but from what I read, it

shouldn't have restored boot, system and recovery

partitions.

I was left with a rooted but s-on/locked system

The 0.92 hboot doesn't appear to support the

new fastboot commands or adb commands related

to htcdev.com lock / unlock functions.

I think I'm supposed to run

zergRush to root 2.3.4

then push the flash_image

to /data/local (the /sdcard files are already there)

cd /data/local

chmod 0755 flash_image

./flash_image misc /sdcard/mtd0.img

reboot bootloader to run the 2.2 PB31IMG.zip

that should be 2.2 stock

(rerun zergRush to temp root)

adb shell rm /sdcard/PB31IMG.zip

adb reboot bootloader

get fastboot USB

fastboot flash recovery 5.0.2.0-cwm-recovery.img

adb reboot recovery

then flash the s-off.zip from recovery?

after reboot to bootloader I should have s-off, right?
[Droid Incredible General] fuzzynco:
restating for clearity (to convince myself I understand)

OK - I think I got it

my most recent experience was with Rezound

which is unlocked/s-on but came with the

hboot that supported the fastboot commands.

Previously, with the Inc1, when it was on froyo,

I only had to run reflash and that did everything

to make it rooted / custom recovery / s-off and

then I could use custom ROMs.

As I understood it, Gingerbread fixed the exploit

that was used to get s-off, so you have to restore

froyo and then the patch to get s-off ?

I have a rooted Gingerbread nandroid to restore

once I get s-off. I found the RUU to upgrade

hboot for support of unlock commands.

PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe

Is this supposed to only update hboot?

It seems the simplest approach is to downgrade again.

then rerun unrevoked to root, install recovery 5.0.2.0

and get s-off. If s-off doesn't 'stick', then separately

run the forever patch. if that works, restore the GB

nandroid which should then restore everything to a

rooted gingerbread 2.3.4 with hboot 0.92 s-off and

the custom rom that was on the old phone.

Is that right?
[Droid Incredible General] scotty1223:
QUOTE=fuzzynco

OK - I think I got it

my most recent experience was with Rezound

which is unlocked/s-on but came with the

hboot that supported the fastboot commands.

Previously, with the Inc1, when it was on froyo,

I only had to run reflash and that did everything

to make it rooted / custom recovery / s-off and

then I could use custom ROMs.

As I understood it, Gingerbread fixed the exploit

that was used to get s-off, so you have to restore

froyo and then the patch to get s-off ? gingerbread only fixed the "rage in the cage" exploit that unrevoked,and may other "one clicks" were using to gain temp root access. as i said above,the exploit to turn the s off is dependent on the froyo and eclair basebands(radios),not so much in the software.

unrevoked 3.22 is special,somehow,as its the only version that works on 2.3.4 to gain root access. no one knows why. it cannot turn s-off becasue of the gingerbread radio.

again,if you are running rooted gingerbread,still with a froyo baseband, then you should be able to simply flash the patch. if you absolutely needed froyo software,you could simply flash a froyo rooted rom. theres no need to go thru the process downgrade and run the froyo ruu again. again,this is assuming you to be on a froyo baseband after downgrading once allready,and not having upgraded the baseband due to being s-on.

if you are indeed back on gingerbread,with the gingerbread radio,then yes,you will have to go thru the process to downgrade to froyo again,run unrevoked again to get a recovery,and flash the patch if unrevoked fails to turn s-off.

I have a rooted Gingerbread nandroid to restore

once I get s-off. I found the RUU to upgrade

hboot for support of unlock commands.

PB3120000_Incredible_C_hboot_1.02.0000_4.08.605.2.exe

Is this supposed to only update hboot? that is correct.it updates .92 to the 1.02.0000 locked hboot.

It seems the simplest approach is to downgrade again.

then rerun unrevoked to root, install recovery 5.0.2.0

and get s-off. If s-off doesn't 'stick', then separately

run the forever patch. if that works, restore the GB

nandroid which should then restore everything to a

rooted gingerbread 2.3.4 with hboot 0.92 s-off and

the custom rom that was on the old phone.

Is that right?

well,sort of. ;) see above... if youre still on a froyo baseband,you dont need to downgrade again.

otherwise,yes... if youre on a GB baseband:

1)dongrade to froyo

2)run unrevoked 3.32

3)if 3.32 fails to s-off,then flash the patch seperately.

once you have achieved s-off: you can restore a backup wich will restore boot,system,and data. you can install the 2.3.4 radio only, as a PB31IMG,or you can run the whole GB ruu. if you want the htcdev 1.02.0000 hboot,you can easily install and unlock it at this time.

the important thing to remember is that restoring a nandroid in clockwork is not restoring hboot,radio,or any other firmware
[Droid Incredible General] fuzzynco:
How to associate radio numbers with thier OSes

ok so I need to find out what radio is on the phone.

Where can find a mapping between baseband radio numbers

and OS version (froyo or gingerbread)?

http://wiki.cyanogenmod.com/wiki/HTC_Incredible:_Support_Downloads

has a list of radio PB31IMG.zip files but doesn't say which are

froyo and which are gingerbread. :confused:

HTC Incredible Radios

1.00.00.02.09

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

2.15.00.11.19

2.15.10.05.06
[Droid Incredible General] scotty1223:
again,i think you are making this more complicated than it needs to be.

1)did you downgrade to froyo?

if yes:

2)did you run a GB ruu?

if no: then youre still on a froyo radio :D

1.00.00.02.09

1.00.03.04.06

2.05.00.06.11<-eclair

2.07.00.07.16

2.15.00.07.28<-froyo

2.15.00.09.01<-evo radio

2.15.00.11.19<-evo radio

2.15.10.05.06

2.15.10.07.07<-gingerbread

those in blue are the official radios listed here: http://pvillecomp.com/?page_id=18

you could also just flash the patch and see what happens.. the worse thing that will happen is it wont work. ;)
[Droid Incredible General] fuzzynco:
[Solved] Just running the patch worked

I'm on hboot 0.92 s-off with the froyo baseband.

As you had said, the radio from the downgrade

stayed, when I restored the cwm 5.0.2.0 nandroid

backup of the 2.3.4 system.

Should I update the radio to the gingerbread baseband?
[Droid Incredible General] scotty1223:
if you are s-off now,then i prolly would. :)
[Droid Incredible General] Shano56:
Thanks guys. I finally took a shot and got it rooted. (s-on for now. but not for long because i love custom roms :D)

Thanks again for your kind and simple help and not giving some smart ass answer like some ppl do :p
[Droid Incredible General] Shano56:
Tried going on with the rest of the guide to get s-off and I receive error Main version is older when trying to downgrade. help anyone? Im wondering if my ICS rom has anything to do with it

./flash_image misc /sdcard/mtd0.img returns segmentation error
[Droid Incredible General] tiny4579:
Try going back to gingerbread. That should allow you to run it.
[Droid Incredible General] scotty1223:
your ics rom does not change your main version,and shouldnt really be a factor.

the error youre getting means you didnt do something correctly with the adb commands,and the misc image didnt get rewritten with a lower main version number,to allow the "upgrade"(downgrade to froyo)

you need to start again with the adb steps,and provide a copy/paste of everything in the cmd window if it fails again.
[Droid Incredible General] Shano56:
my steps: format sd card to FAT32. place place PB31IMG.zip sd:/PB31IMG.zip

eject sd card

turn off phone

insert sd card

boot phone normally

file browser on phone confirms its not .zip.zip or anything

plug in phone open cmd

C:\miniadb_inc>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT******** device

C:\miniadb_inc>md5sums mtd0.img

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\miniadb_inc\]
mtd0.img 34307be744275f1db1dd16af04c37839

C:\miniadb_inc>md5sums flash_image

MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\miniadb_inc\]
flash_image 0098a7dd6600b55fac34fc6645be5d7a

C:\miniadb_inc>adb push flash_image /data/local/
failed to copy 'flash_image' to '/data/local//flash_image': Permission denied

C:\miniadb_inc>adb root
restarting adbd as root

C:\miniadb_inc>adb push flash_image /data/local/
1237 KB/s (76044 bytes in 0.060s)

C:\miniadb_inc>adb push mtd0.img /sdcard/
1225 KB/s (655360 bytes in 0.522s)

C:\miniadb_inc>adb shell
root@android:/ # cd /data/local
cd /data/local
root@android:/data/local # chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
root@android:/data/local # cd /data/local
cd /data/local
root@android:/data/local # ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
Segmentation fault
139|root@android:/data/local # exit
exit

C:\miniadb_inc>adb reboot bootloader

C:\miniadb_inc>

press power once once exits to bootloader

after some loading i get

Main Version is older!
Update Fail!
Do you want to reboot device?
[Droid Incredible General] tiny4579:
Actually that flash_image command does depend on the os version. The flash_image binary that works on gingerbread will not work on ics. The flash_image packed with a more recent rom manager might.
[Droid Incredible General] Shano56:
so what do you suggest? should I install a gingerbread rom? or is there a flash_image that will work with ICS?
[Droid Incredible General] tiny4579:
Either works. If you don't want to flash a new ROM try:

cd /data/data/com.koushikdutta.rommanager/files instead of the cd /data/local line. And then continue the instructions with the ./flash_image.

Otherwise flashing a gb rom should work.
[Droid Incredible General] Shano56:
so do i do

cd /data/data/com.koushikdutta.rommanager/
chmod 0755 /data/local/flash_image

cd /data/data/com.koushikdutta.rommanager/
./flash_image misc /sdcard/mtd0.img

or

cd /data/data/com.koushikdutta.rommanager/
chmod 0755 /data/local/flash_image

cd /data/local
./flash_image misc /sdcard/mtd0.img

or what?
[Droid Incredible General] tiny4579:
Just:

cd /data/data/com.koushikdutta.rommanager/files

./flash_image misc /sdcard/mtd0.img
[Droid Incredible General] Shano56:
i get

C:\miniadb_inc>adb shell
root@android:/ # cd /data/local
cd /data/local
root@android:/data/local # chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
root@android:/data/local # cd /data/data/com.koushikdutta.rommanager/
cd /data/data/com.koushikdutta.rommanager/
root@android:/data/data/com.koushikdutta.rommanager # ./flash_image misc /sdcard
/mtd0.img
e misc /sdcard/mtd0.img <
/system/bin/sh: ./flash_image: not found
127|root@android:/data/data/com.koushikdutta.rommanager #
[Droid Incredible General] tiny4579:
Sorry, I didn't do a great job trying to send this from work but it should be:

cd /data/data/com.koushikdutta.rommanager/files/
./flash_image misc /sdcard/mtd0.img

You were missing the files at the end of the long command beginning with cd. Very important as it would not be able to find a flash_image file in the directory you specified:

/data/data/com.koushikdutta.rommanager/

Let me know how that goes for you.
[Droid Incredible General] Shano56:
much better. thank you sir. worked like a charm. we'll see if i have s-off in about 2 minutes :)

i supposed i could have looked into /data/data/com.koushikdutta.rommanager/ to see what adb was looking for myself, but i didn't think of it :p

EDIT:

now i have a problem. booted into froyo just fine, however i run unrevoked 3.32 and it says cannot root is system to new

im left without a recovery image so i cant run unrevoked-forever.zip

should i retry unrevoked 3.32 ? any idea why it did not work at first try
[Droid Incredible General] cmlusco:
Sometimes it takes a couple tries. You could try .22 shouldnt matter either way. If your on froyo with the froyo radio, it will eventually go thru.
[Droid Incredible General] scotty1223:
good call,sir,i hadnt thot of that :cool:

try it a second time,alot of times it need run twice.
[Droid Incredible General] Shano56:
tried again and just used default recovery (version 2 instead of version 5) and it worked. now I have

INCREDIBLEC XD SHIP S-OFF

HBOOT-0.92.0000

RADIO-2.15.00.07.28

is it recommend to update hboot or radio to anything?
[Droid Incredible General] tiny4579:
I would upgrade clockworkmod back to 5. You can use rom manager for that. No need to upgrade hboot. In fact I wouldn't. The radio is fine but if you look around different people have different radio versions that seem to worn better for them. You don't need to change radios when flashing rooms tho. Also good job on the tricky s-off.
[Droid Incredible General] Shano56:
yeah i updated in rom manager. thanks again for the help, i'll keep my radio as is

i can now remove /system/apps with s-off.. could not with s-on. interesting
[Droid Incredible General] zounduser:
Im getting mainver error as well? Im trying to root friends dinc...... This is ridiculous, my tbolt, and rezound were easy as hell! Any thoughts guys? He has the 1.2 00000000 hboot, and he is on the stock gingerbread rom. We do have cwmr and su permissions.

Sent from my s-off rooted htc rezound using Xparent ics blue tapatalk 2
[Droid Incredible General] cmlusco:
Follow this guide http://xdaforums.com/showthread.php?t=1506258, start at step 28. The bootloader must be unlocked first, but since its rooted i assume it is.
[Droid Incredible General] dpwhitty11:
Here's my situation.

HBOOT .92, s-on, 07.07 radio, CWM 5.0.2.0. Unrooted.

Somehow, don't remember how (did this ages ago), got myself running CM7 nightly.

Phone was originally on the 2.3.4 update.

Now, I can't do a damn thing.

Can't re-root.

Can't get s-off.

Can't run a RUU.

Can't anything.... Besides flash kernels?

This guide doesn't help, I get stuck at step 2... It runs up until it enters CWM, and then it spits this out:

And I can't continue on. Root fails, step 3 fails, etc.

Copy of recovery-log:

http://pastebin.com/cKB6j4Di
[Droid Incredible General] scotty1223:
if you have recovery thats the important thing.

check app drawer for superuser. if its there run a couple root apps. after they fail clear data in superuser as instructed in first post.

if superuser is truly not there,relax. just flash it in recovery: http://downloads.androidsu.com/superuser/Superuser-3.0.7-efgh-signed.zip

now you have root access and can continue with step 3.

the error you get when runing unrevoked about rom manager is irrelevant,ignore it.
[Droid Incredible General] dpwhitty11:
It was there, just not working.

The flashable su worked. I'll continue with the rest tomorrow. Thanks.
[Droid Incredible General] scotty1223:
You're welcome. It's all downhill from here :)
[Droid Incredible General] dpwhitty11:
On this step

getting:
[Droid Incredible General] kordon:
I was having an issue with clockworkmod on my SLCD. I was able to fix it, but didn't see it specifically spelled out when I was searching the thread, so here was the issue and the solution just in case another newb like me happens to come along...

Basically I downloaded unrevoked 3.32 and the clockworkmod 5.0.2.0 but when I ran unrevoked it didn't work. I saw that it said to do it using 3.22, so I downloaded that and ran it. This time it worked, I had root, all was good.

Except that the 2nd time I ran unrevoked I forgot to have it use clockwork 5.0.2.0 and so when I booted into recovery I just saw a black screen with white bars on the side and nothing else. I would have to pull the battery to be able to boot again. With a little bit of research I discovered I could flash the latest version of clockwork using Rom Manager. I did it, rebooted to recovery, still had the same screen. Tried it again, making sure it was saying it was flashing 5.0.2.0 and it still didn't work.

What finally worked and got clockworkmod updated was to re-run unrevoked 3.22 and to select File > Custom Recovery, and then select the clockworkmod file I downloaded just like the first page describes. and to follow the rest of the directions on running unrevoked.

Once unrevoked finished I was loaded in clockwork and everything was looking great. I was even able to make a backup of the system.

And thats what i've got so far! I hope this helps out any newbs that have an old incredible and are wanting to do fun things to it, too!

now I go boldly onto the next steps from the OP :-)

p.s. thanks for making this guide, it's been a giant help!
[Droid Incredible General] Bonkurei:
i have a question,

on step 2, if after this step i make a nandroid and after all the step is complete, is it save to restore the nandroid (official 2.3.4) that i make before? will it make s-off and root disappear?

thank you very much in advance
[Droid Incredible General] scotty1223:
s-off will remain until you purposely remove it,so you are perectly safe in restoring your backup. i would make efforts to restore the radio as well,to the newest GB version.

im sure there are lots of nice roms based on the latest GB,may want to consider installing one of them so you wont have any of the issues you had with your stock GB rom :)
[Droid Incredible General] Bonkurei:
thank for the answer bro, right now im already halfway, just finished step 3 and now charging the phone to 100% and ready to start step 4, wish me luck :D

Edit:

Successfully downgrade to 2.2, gain S-Off and Root

thank you very much scotty1223 for this awesome guide
[Droid Incredible General] citysoundman:
custom ROM question

Hi everyone,

I'm on gingerbread 2.3.4 and I just completed the 750MB data/data MOD to fix my 'low memory' error. The one from this thread.http://xdaforums.com/showthread.php?t=1488351

So now my phone is rooted with Clockwork Recovery 5.0.2.0.

Just checking about something:

1. If I want to flash a custom ROM will I need to downgrade to froyo first? I know this is what everyone says is necessary. But now that I am already rooted I don't know if that would make it possible to flash a custom ROM without downgrading to froyo.

2. If I do flash a custom ROM will I lose this 750 mb data/data MOD? This is the most important question! For me the 'low memory' problem was SO bad I was having to wipe my app caches every day just to get my Gmail! So I do not want to take a chance of having it recur. Honestly I don't know exactly what files the custom ROM replaces/modifies. I read that some people with custom ROMs were still getting the 'low memory' error - so I'm thinking that they do not have this this 750 mb data/data MOD.
[Droid Incredible General] Bonkurei:
hi,

1. no u do not have to downgrade to froyo just to instal / flash a custom rom. a process downgrade to froyo is to get S-Off.

2. idk about this one, but i never have any problem like this in a custom rom's.

if you read this guide, u already halfway to S-Off, so why dont you take a little tour and get S-Off in ur device, its worth the time to get it :D.

but then again if u just want to install a custom room u dont need to get S-Off or downgrade to froyo.
[Droid Incredible General] rickatnight11:
Some roms have it, some don't. It's not particularly difficult to reapply.
[Droid Incredible General] cmlusco:
2. A lot of roms have the ext4 mod built in. If you flash one that dosent you will need to redo the mod. However it will be way easier to do because your already rooted and s-off.
[Droid Incredible General] citysoundman:
Likely I will go s-off eventually. I'm just gonna wait take a break from rooting now - it's such a nice day outside! Thanks again for your replies :good:

---------- Post added at 11:49 AM ---------- Previous post was at 11:47 AM ----------

Yes I can see now that it would be pretty easy to re-apply the Mod - thank you!

---------- Post added at 11:52 AM ---------- Previous post was at 11:49 AM ----------

thanks cmlusco
[Droid Incredible General] rmkilc:
When I run unrevoked 3.22 on my Incredible running Android 2.3.4, I get "failed to flash recovery" after it does its reboot. I have tried uninstalling the usb drivers, and reinstalling, I have tried running unrevoked as administrator (windows 7). What am I doing wrong? I should also mention I successfully did this on the same computer to my bros Incredible running Android 2.3.4 a couple months ago.
[Droid Incredible General] scotty1223:
unrevoked 3.22 has always been finicky,working fine for some users,not so much for others.recent updates seem to have made it even more so,to the point that i have declared this guide outdated(tho i forgot to do that here).

i have been recomending using htcdev to root,downgrade,and flash unrevoked forever. while it does wipe your data,and technically void your warranty,it has at least proven to be reliable. i doubt many incredible 1s have any factory warranty left anyway ;)

here is the htcdev thread on AF: http://androidforums.com/incredible...ow-unlock-downgrade-achieve-s-off-htcdev.html

i believe it is here as well,i will have to see if i can dig it up.and update the original post.
[Droid Incredible General] rmkilc:
Thanks for the info. Am I understanding correctly that you can achieve root without using unrevoked, but in order to flash a custom rom, you need s-off, which requires unrevoked?
[Droid Incredible General] scotty1223:
no. you are rooting,downgrading,then acieving s-off,just like in this thread,with exception you are using htcdev to install a recovery and gain root access in both GB(to rewrite misc image) and froyo(to install forever s-off patch).

end result is the same(s-off). just a slightly different patch to get there.
[Droid Incredible General] rcracerguy:
I still haven't been able to get S-off. tried the unrevolked forever zip and wouldn't install it. What can I do?
[Droid Incredible General] cmlusco:
What do you mean wouldnt install it? Did it give an error? Did it not even start to flash, or start and error?
[Droid Incredible General] rcracerguy:
yes got an error
[Droid Incredible General] normanx:
You have to be a lot more specific then that.... during what process did you get the error?