View Single Post
Old July 9th, 2012, 04:42 AM   #1402 (permalink)
scotty85
AF Addict
Thread Author (OP)
 
scotty85's Avatar
 
Join Date: Jul 2010
Posts: 11,014
 
Device(s):
Carrier: Not Provided

Thanks: 7,893
Thanked 7,228 Times in 4,485 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 online now  
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)