Go Back   Android Forums > Android Phones > HTC Droid Incredible > Incredible - All Things Root
Incredible - All Things Root Rooting, ROMS, Overclocking, etc.

Get excited for the Samsung Galaxy S5! Find everything you need and discuss it in our Galaxy S5 Forum!

Like Tree1Likes

Closed Thread
 
LinkBack Thread Tools
Old July 9th, 2012, 12:40 AM   #1401 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by garthbartin View Post
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.

I don't suppose you have Build: 4.08.605.15 710RD? The same thing is happening to me in that unrevoked is failing to flash despite rechecking all the hashes and what not. I've read that some other people who updated to the new build have also been unsuccessful in rooting using unrevoked but I have yet to try other methods.

I've just started reading learning about rooting in general, so I have zero experience with this. Perhaps someone with a little more knowledge could chime in with a more effective way to get around this new build.

s1thl0rd is offline  
sponsored links
Old July 9th, 2012, 04:42 AM   #1402 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

Quote:
Originally Posted by s1thl0rd View Post
I don't suppose you have Build: 4.08.605.15 710RD? The same thing is happening to me in that unrevoked is failing to flash despite rechecking all the hashes and what not. I've read that some other people who updated to the new build have also been unsuccessful in rooting using unrevoked but I have yet to try other methods.

I've just started reading learning about rooting in general, so I have zero experience with this. Perhaps someone with a little more knowledge could chime in with a more effective way to get around this new build.
if your end result is simply root and s-off,i have provided other ways to skin the cat-use fre3vo for temp root in place of zerg rush,or simply use htcdev. both are pretty effective ways "to get around this new build" see the posts below.

if you just want to run unrevoked on gingerbread and run s-on root,im sorry,i cant help you there. weve had no idea why the older unrevoked happened to work on earlier builds of gingerbread,and always realized future OTAs could potentially close that door. this is why ive explored other options so when it happend users would not be stuck with s-on,no root

if you have your heart set on unrevoked,you could start downloading and trying older versions one at a time,as "efizzle" on xda did initially. maybe youll find a different version that works on this build

tho i personally would simply recomend fre3vo or htcdev. if nothing else,the htcdev method seems to be very reliable for those thus far that have used it.


see below posts for reference:

Quote:
Originally Posted by scotty85 View Post
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:

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

C:\Users\Scott>cd c:\tbolt2

c:\tbolt2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxx    device


c:\tbolt2>adb push fre3vo /data/local/tmp
956 KB/s (9796 bytes in 0.010s)

c:\tbolt2>adb shell chmod 777 /data/local/tmp/fre3vo

c:\tbolt2>adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
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>adb shell
# <-indicates that you have temp root access
Quote:
Originally Posted by scotty85 View Post
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:



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
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers.
donate to my device fund
scotty85 is offline  
Last edited by scotty85; July 9th, 2012 at 04:45 AM.
The Following User Says Thank You to scotty85 For This Useful Post:
s1thl0rd (July 9th, 2012)
Old July 9th, 2012, 09:01 AM   #1403 (permalink)
Junior Member
 
Join Date: Apr 2010
Posts: 25
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Hey all, so I tried the instructions in this thread to the best of my abilities and somehow I've ended up back with Android 2.2 and seemingly no ability to get back to a rooted 2.3.4. At one point during the process, I was able to get the HBOOT screen to show "UNLOCKED" but somehow that's been reversed and now I'm back to being LOCKED again and un-rooted. I should mention that none of the steps along the way worked perfectly for me -- unrevoked never ran smoothly and so I was doing a lot of the alternate steps along the way. The last step I ran was unrevoked forever and it failed (the "NAND flash" error message -- I didn't understand the solutions offered when I did a search for this error message). So my question is this: if I'm now back at Android 2.2, apparently un-roooted again, and LOCKED status, do I have any hope of getting my device back to 2.3.4? My only intention in doing all this was to hopefully revert back to a version of Gingerbread that existed before the last OTA update (the one within the past 1-2 weeks), which screwed up a lot of my settings and completely ate up my battery for no apparent reason. My phone was working perfectly fine before this "update". I figured rooting was the only way to get the phone back to stability until I was ready to purchase a new device. Thanks for any advice.

PS: I should mention that, despite being fearless and a good instruction-follower, I'm not inherently familiar with the shortcuts or methods used in these instructions. So answers such as "just run HBOOT and flash a new image" are totally confusing to me -- layman's language would be much appreciated!
ronchito is offline  
Old July 9th, 2012, 10:04 AM   #1404 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

I would follow directions in the root/downgrade s off with HTC dev thread. I'm assuming you still have your original unlock token.

Since your on.froyo,start at step 5
scotty85 is offline  
Old July 9th, 2012, 10:10 AM   #1405 (permalink)
Junior Member
 
Join Date: Apr 2010
Posts: 25
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Thanks scotty. I have my original Unlock_code.bin file if that will be sufficient?
ronchito is offline  
Old July 9th, 2012, 10:13 AM   #1406 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

Yup! That's it!

If you have ?s post them in that thread. I'm currently at work,but will try and help if you need it
scotty85 is offline  
Old July 9th, 2012, 10:13 AM   #1407 (permalink)
Junior Member
 
Join Date: Apr 2010
Posts: 25
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 1 Time in 1 Post
Default

Quote:
Originally Posted by scotty85 View Post
Yup! That's it!

If you have ?s post them in that thread. I'm currently at work,but will try and help if you need it
OK cool thanks man! Will give it a shot tonight.
ronchito is offline  
Old July 9th, 2012, 06:50 PM   #1408 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 2
 
Device(s):
Carrier: Not Provided

Thanks: 1
Thanked 0 Times in 0 Posts
Default

So I took Scotty85's advice and tried the fre3vo approach. This is what I got out of it.

Code:
C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb devices
List of devices attached
HTxxxxxxxxxx    device


C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb push fre3vo /data/local/t
mp
613 KB/s (9796 bytes in 0.015s)

C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb shell chmod 777 /data/loc
al/tmp/fre3vo

C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb shell /data/local/tmp/fre
3vo -debug -start F0000000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.

C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb shell
$
I ran the cmd prompt as administrator if that means anything, but I guess it's time to try the htcdev method. Again, this is a Dinc with build 4.08.605.15 of Gingerbread.
s1thl0rd is offline  
Old July 10th, 2012, 06:45 PM   #1409 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

Quote:
Originally Posted by s1thl0rd View Post
So I took Scotty85's advice and tried the fre3vo approach. This is what I got out of it.

Code:
C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb devices
List of devices attached
HTxxxxxxxxxx    device


C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb push fre3vo /data/local/t
mp
613 KB/s (9796 bytes in 0.015s)

C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb shell chmod 777 /data/loc
al/tmp/fre3vo

C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb shell /data/local/tmp/fre
3vo -debug -start F0000000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
This device either does not support the fre3vo exploit, or this
account lacks permission to access the required devices.
An error has occured.

C:\Users\Anthony\Desktop\DHDDowngrade\DHDDowngrade>adb shell
$
I ran the cmd prompt as administrator if that means anything, but I guess it's time to try the htcdev method. Again, this is a Dinc with build 4.08.605.15 of Gingerbread.
ahhh it may be that fre3vo does not support mtd devices. it always slips my mind that the original incredible is NOT an emmc device,like most everything else i mess with

holler if you have questions on htcdev.
scotty85 is offline  
Old July 14th, 2012, 01:49 PM   #1410 (permalink)
New Member
 
COTorrey's Avatar
 
Join Date: Jun 2012
Location: Colorado
Posts: 4
 
Device(s): 1st Gen Incredible Nexus 7
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 1 Post
Thumbs up

hey everyone, totally new to this.

I tried running unrevoked3 on my Droid inc but i'm getting the "Error: failed to get root, Is your firmware too new?"

its android 2.3.4
4.08.605.2

I'm working on a Mac

thanks so much in advance. I really really appreciate it.
COTorrey is offline  
sponsored links
Old July 14th, 2012, 02:47 PM   #1411 (permalink)
Senior Member
 
Join Date: Aug 2010
Location: PA
Gender: Male
Posts: 5,540
 
Device(s): Rooted Samsung Galaxy Nexus, Rooted HTC Incredible, Stock 4G Motorola Droid Xyboard 10.1 (32GB)
Carrier: Verizon

Thanks: 470
Thanked 1,957 Times in 1,327 Posts
Default

Quote:
Originally Posted by COTorrey View Post
hey everyone, totally new to this.

I tried running unrevoked3 on my Droid inc but i'm getting the "Error: failed to get root, Is your firmware too new?"

its android 2.3.4
4.08.605.2

I'm working on a Mac

thanks so much in advance. I really really appreciate it.

The first post has directions for a Mac or check out the htcdev method stickied at the top of the forum.
sdrawkcab25 is offline  
The Following User Says Thank You to sdrawkcab25 For This Useful Post:
scotty85 (July 14th, 2012)
Old July 14th, 2012, 03:09 PM   #1412 (permalink)
New Member
 
COTorrey's Avatar
 
Join Date: Jun 2012
Location: Colorado
Posts: 4
 
Device(s): 1st Gen Incredible Nexus 7
Carrier: Not Provided

Thanks: 0
Thanked 2 Times in 1 Post
Default

Quote:
Originally Posted by sdrawkcab25 View Post
The first post has directions for a Mac or check out the htcdev method stickied at the top of the forum.
yeah the mac way seems like a haslte, might just do it later, found a guy on craigslist thatll root android phones for $20

im just lazy :-/
COTorrey is offline  
Old July 15th, 2012, 07:50 PM   #1413 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

So the question was "do I need to downgrade my baseband v. 2.15.10.12.20. to run Unrevoked and get S-off?".

Quote:
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
And the reply was
Quote:
Originally Posted by sdrawkcab25 View Post
Correct, you need to downgrade your phone to 2.2 to get s-off.
So this means that downgrading your phone to 2.2 also downgrades your baseband?

Please pardon my n00b confusion.

Basically I followed this [HOW TO] Fix the "Low on space" problem (in plain English) and now have root with 2.3.4, but want to carry on to also have S-off.

Please confirm, I basically need to:
  • downgrade to 2.2 (what's the easiest way, considering I have root and Clockwork installed?)
  • Run current version of Unrevoked(?)
  • re-upgrade to 2.3.4 (restore the backup of my current ROM?)

Forgive my asking; I usually am the guy telling people to RTFM but I haven't been able to find my particular situation addressed.

I presently have baseband 2.15.10.07.07 on 2.3.4, and as soon as I fixed the space issue it started bugging me to update to 4.08.605.15.

Thanks.
tadc is offline  
Old July 15th, 2012, 08:34 PM   #1414 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

Quote:
Originally Posted by tadc View Post
So the question was "do I need to downgrade my baseband v. 2.15.10.12.20. to run Unrevoked and get S-off?".

...

And the reply was

...
So this means that downgrading your phone to 2.2 also downgrades your baseband?
in this particular case,yes. the entire froyo RUU is run,so all partitions,inlcuding the baseband,are downgraded.
Please pardon my n00b confusion.

Basically I followed this [HOW TO] Fix the "Low on space" problem (in plain English) and now have root with 2.3.4, but want to carry on to also have S-off.

Please confirm, I basically need to:
  • downgrade to 2.2 (what's the easiest way, considering I have root and Clockwork installed?)
    just start at step 4 of the original post 4)downgradewith adb
  • Run current version of Unrevoked(?)
    once youre on stock froyo,you should be able to simply run unrevoked 3.32(or whatever the most current one is)
  • re-upgrade to 2.3.4 (restore the backup of my current ROM?)
    simply restore it,after youve rooted 2.2 and installed recovery. i would also recomend upgrading your baseband back to GB also,after youre s-off

Forgive my asking; I usually am the guy telling people to RTFM but I haven't been able to find my particular situation addressed.
it has been addressed several times in this thread. trust me

I presently have baseband 2.15.10.07.07 on 2.3.4, and as soon as I fixed the space issue it started bugging me to update to 4.08.605.15.

Thanks.
youre welcome
scotty85 is offline  
The Following User Says Thank You to scotty85 For This Useful Post:
tadc (July 25th, 2012)
Old July 16th, 2012, 03:56 PM   #1415 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by scotty85 View Post
youre welcome
Thanks for the service you do to the community in answering a continuous stream of noob questions. Unfortunately this is a common issue with crowd-sourced projects such as this (and dd-wrt is another good example) - the internet is awash with outdated/superseded/questionable information, so even for the technically-inclined it's hard to be sure you're doing it right unless you ask for confirmation (or learn the hard way!).

One last Q:
Quote:
i would also recomend upgrading your baseband back to GB also,after youre s-off
How does one backup/restore ones baseband?

Thanks!
tadc is offline  
Old July 16th, 2012, 04:32 PM   #1416 (permalink)
Senior Member
 
Join Date: Aug 2010
Location: PA
Gender: Male
Posts: 5,540
 
Device(s): Rooted Samsung Galaxy Nexus, Rooted HTC Incredible, Stock 4G Motorola Droid Xyboard 10.1 (32GB)
Carrier: Verizon

Thanks: 470
Thanked 1,957 Times in 1,327 Posts
Default

Quote:
Originally Posted by tadc View Post
Thanks for the service you do to the community in answering a continuous stream of noob questions. Unfortunately this is a common issue with crowd-sourced projects such as this (and dd-wrt is another good example) - the internet is awash with outdated/superseded/questionable information, so even for the technically-inclined it's hard to be sure you're doing it right unless you ask for confirmation (or learn the hard way!).

One last Q:

How does one backup/restore ones baseband?

Thanks!
All compatible basebands can be found here:
PvilleComp's | Droid Incredible Resource Site

They are installed in hboot by naming them to PB31IMG.zip
sdrawkcab25 is offline  
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
scotty85 (July 16th, 2012), tadc (July 25th, 2012)
Old July 24th, 2012, 01:17 AM   #1417 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 4
 
Device(s):
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Quote:
Originally Posted by sdrawkcab25 View Post
All compatible basebands can be found here:
PvilleComp's | Droid Incredible Resource Site

They are installed in hboot by naming them to PB31IMG.zip
Thanks guys... all done and worked like a charm. Or rather would have worked like a charm if were better at following instructions.

Only thing I really wasted time on was the whole internal-vs-external storage issue. I kept copying stuff onto internal storage and then wondered why it didn't find the zip file... of course in my defense this computer has an unreasonable number of drives attached so the extra volume wasn't immediately obvious.

Last question (promise), can I now install the update that Verizon has been prompting me about for weeks? Or is there some way to make it stop bugging me about it?

Thanks!
tadc is offline  
Old July 24th, 2012, 05:26 AM   #1418 (permalink)
Senior Member
 
Join Date: Aug 2010
Location: PA
Gender: Male
Posts: 5,540
 
Device(s): Rooted Samsung Galaxy Nexus, Rooted HTC Incredible, Stock 4G Motorola Droid Xyboard 10.1 (32GB)
Carrier: Verizon

Thanks: 470
Thanked 1,957 Times in 1,327 Posts
Default

Quote:
Originally Posted by tadc View Post
Thanks guys... all done and worked like a charm. Or rather would have worked like a charm if were better at following instructions.

Only thing I really wasted time on was the whole internal-vs-external storage issue. I kept copying stuff onto internal storage and then wondered why it didn't find the zip file... of course in my defense this computer has an unreasonable number of drives attached so the extra volume wasn't immediately obvious.

Last question (promise), can I now install the update that Verizon has been prompting me about for weeks? Or is there some way to make it stop bugging me about it?

Thanks!
You would install this rom if you want the phone to stop nagging you.
[ROM] Stock rooted OTA 4.08.605.15 - 06-27-2012 - xda-developers
sdrawkcab25 is offline  
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
scotty85 (July 24th, 2012), tadc (July 25th, 2012)
Old July 27th, 2012, 01:00 AM   #1419 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 6
 
Device(s): HTC Incredible 1
Carrier: Not Provided

Thanks: 2
Thanked 1 Time in 1 Post
Default

Removed
Robrooter is offline  
Last edited by Robrooter; July 27th, 2012 at 01:14 AM. Reason: wrong thread
Old July 29th, 2012, 09:18 AM   #1420 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 8
 
Device(s): Motorola Droid 4
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

New member here and I'm sure you guys get this a lot, but me being an idiot I upgraded from 2.2 to 2.3.4. I've followed Scotty's guide to try and downgrade however I'm getting an error message in unrevoked.



Failed to flash recovery image.




I see Scotty posted another guide that if unrevoked 3.22 didn't work for whatever reason to use that guide. The speedbump I've run into is that I wasn't able to download the zergRush tool from xda or the mini-adb_inc image file. The link for the mini-adb forwards to some BS Hollywood VS Internet site.

Perhaps there's something I'm missing or maybe I'm ******ed?? I haven't tried doing a factory reset on the phone as of yet. This phone was a replacement because I lost mine last week.

Any help/feedback would be greatly appreciated.

Thanks.
AlphaZulu is offline  
sponsored links
Old July 29th, 2012, 01:19 PM   #1421 (permalink)
Senior Member
 
Join Date: Aug 2010
Location: PA
Gender: Male
Posts: 5,540
 
Device(s): Rooted Samsung Galaxy Nexus, Rooted HTC Incredible, Stock 4G Motorola Droid Xyboard 10.1 (32GB)
Carrier: Verizon

Thanks: 470
Thanked 1,957 Times in 1,327 Posts
Default

Quote:
Originally Posted by AlphaZulu View Post
New member here and I'm sure you guys get this a lot, but me being an idiot I upgraded from 2.2 to 2.3.4. I've followed Scotty's guide to try and downgrade however I'm getting an error message in unrevoked.



Failed to flash recovery image.




I see Scotty posted another guide that if unrevoked 3.22 didn't work for whatever reason to use that guide. The speedbump I've run into is that I wasn't able to download the zergRush tool from xda or the mini-adb_inc image file. The link for the mini-adb forwards to some BS Hollywood VS Internet site.

Perhaps there's something I'm missing or maybe I'm ******ed?? I haven't tried doing a factory reset on the phone as of yet. This phone was a replacement because I lost mine last week.

Any help/feedback would be greatly appreciated.

Thanks.

We don't recommend using the method in his thread anymore.

Use this method instead:
http://androidforums.com/incredible-all-things-root/531353-how-unlock-downgrade-achieve-s-off-htcdev.html
sdrawkcab25 is offline  
The Following 2 Users Say Thank You to sdrawkcab25 For This Useful Post:
AlphaZulu (July 29th, 2012), scotty85 (July 29th, 2012)
Old July 29th, 2012, 05:24 PM   #1422 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

zerg rush is included in the mini-adb_inc download,but as sdraw has said,this thread is now outdated. as the OP states, unrevoked has become unreliable,and the zerg rush method is now broken with recent updates.

the htcdev thread is your best bet.
scotty85 is offline  
The Following User Says Thank You to scotty85 For This Useful Post:
AlphaZulu (July 29th, 2012)
Old July 29th, 2012, 08:43 PM   #1423 (permalink)
New Member
 
Join Date: Jul 2012
Posts: 8
 
Device(s): Motorola Droid 4
Carrier: Not Provided

Thanks: 3
Thanked 0 Times in 0 Posts
Default

Ah! Okay, thanks a lot. That thread looks way more laborious but I'll take a crack at it when I have a chance.

Thanks again.
AlphaZulu is offline  
Old July 30th, 2012, 04:45 AM   #1424 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

it looks like alot of commands,but the important ones are exactly the same(the ones rewriting the misc image),and there are some extra commands to run the downgrade software from fastboot,in hopes of eliminating the prollems folks were having running PB31IMG from the sd card(seems like at least 1/4 of the questions in this thread are "PB31IMG wont flash!")

it also looks like alot of steps,but most steps are short,and it goes pretty quickly. considering all the different issues folks have had with unrevoked,it should be alot less painless!

just holler if you have questions
scotty85 is offline  
Old October 27th, 2012, 07:26 PM   #1425 (permalink)
New Member
 
Join Date: Oct 2012
Posts: 1
 
Device(s):
Carrier: Not Provided

Thanks: 0
Thanked 0 Times in 0 Posts
Default

[QUOTE=scotty85;3308718]this is for folks who for whatever reason,unrevoked 3.22 does not work to get them root access.

-at the promt in your command window:

cd c:\mini-adb_inc this should change your command promt to "mini-adb_inc",indicating youre using that directory.
adb devices this should output your phones serial number,indicating its recognized

md5sums mtd0.img it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839

md5sums flash_image again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a

md5sums zergRush again,output stuff, then this number:4a32187446c284c2b975845f3ab9ffc4

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

I have already done the downgrade and my md5sums for the zergRush is 03903c2e387f4c6a3907e6dc08dba118

Due to the updates done to zergRush would this md5sums work?

Please disregard I just saw the post about zergrush becoming unrelyable.
2CCW is offline  
Last edited by 2CCW; October 27th, 2012 at 07:57 PM. Reason: Update
Old October 27th, 2012, 09:18 PM   #1426 (permalink)
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 10,650
 
Device(s):
Carrier: Not Provided

Thanks: 7,184
Thanked 6,786 Times in 4,268 Posts
Default

[QUOTE=2CCW;5135955]
Quote:
Originally Posted by scotty85 View Post
this is for folks who for whatever reason,unrevoked 3.22 does not work to get them root access.

-at the promt in your command window:

cd c:\mini-adb_inc this should change your command promt to "mini-adb_inc",indicating youre using that directory.
adb devices this should output your phones serial number,indicating its recognized

md5sums mtd0.img it should output a few things.at the end you should see this number 34307be744275f1db1dd16af04c37839

md5sums flash_image again,it will output some things,then you should see this number: 0098a7dd6600b55fac34fc6645be5d7a

md5sums zergRush again,output stuff, then this number:4a32187446c284c2b975845f3ab9ffc4

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

I have already done the downgrade and my md5sums for the zergRush is 03903c2e387f4c6a3907e6dc08dba118

Due to the updates done to zergRush would this md5sums work?

Please disregard I just saw the post about zergrush becoming unrelyable.
if you have allready down the downgrade,you should be able to root with unrevoked 3.32.

if you havent downgraded,and are on 4.08.605.15,then htcdev is prolly the best method to gain root access to downgrade and get s off
scotty85 is offline  
Closed Thread
Tags
2.3.4, gingerbread, root


Go Back   Android Forums > Android Phones > HTC Droid Incredible > Incredible - All Things Root
Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


LinkBacks (?)
LinkBack to this Thread: http://androidforums.com/incredible-all-things-root/427344-how-root-2-3-4-downgrade-get-s-off.html
Posted By For Type Date
YouTube - Droid Incredible 2.3.4 Root [WORKS!!!!!] S-OFF IF This thread Refback April 9th, 2012 11:24 PM
root 2.3.4,downgrade,and regain s-off - RootzWiki - Page 2 This thread Refback February 17th, 2012 08:51 AM
root 2.3.4,downgrade,and s-off - Page 16 - xda-developers This thread Refback February 11th, 2012 01:06 PM


All times are GMT -5. The time now is 04:57 PM.
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.