• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root 605.9 quesiton

Jelly Doughnut

Jelly Doughnut

Member
Okay, so I finally get up enough nerve to root my bolt, but I am quickly finding that I am a complete and utter noob. I have a quesiton about this post.

I understand the first part, about flashing the file and downgrading (thus wiping my phone), but can I go directly to the second part and do, basically, the same thing with a different file? ...and after that will using revolutionary mess that up?
 
if im understanding the question correctly,no you cannot.

you cant flash a custom file that is 2.11.605.5,but contains the .9 radios as you are currently s-on,wich does siginiture and main version number checks. modifying the .5 file changes its signiture,and thus s-on will not let it flash.

sorry,but youll have to:
-downgrade to .5 using an official,signed RUU or PG05IMG
-run revolutionary and become s-off

then you haev 2 options:
1) if you do not install a clockwork when you run revolutionary,you can let the phone OTA to .9,or you can manually run the .9 ruu. being s-off now,you can install clockwork in hboot,then flash root files after either of those things

2)install clockwork with revolutionary,or install a different recovery in hboot. install .9 radios in hboot. flash a custom rom,or a rooted stock .9 based rom(jrocker has a nice one on this forum) in recovery :)
 
Okay, that helps a lot! I'm slowly beginning to understand.

Now, this method seems simple, but scares me a little. It's the whole "push fre3vo /data/local/tmp" thing that seems a bit out of my league.

I'm assuming that I have to have the fre3vo file in the same directory on my pc as adb right? That way adb can find it and push it to my tb?

In a way it seems too easy... 3 commands to solve a big problem.
 
i havent heard of any other methods of temp root for software that has broken zergrush. thanks for the link,ill have to download that later and check it out. for now,im off to work :(

all you do is copy/paste in a cmd window,but if youre not comfortable,its easy to downgrade as well.

if you want to wait till this evening or over the weekend,ill try it out and make up some more specific directions for this frevo temp root. :)
 
This is my first post here -- I registered just so I could say thanks for this method!! I used the link that Jelly Doughnut posted and it worked to perfection -- I'm currently rooted on 2.11.605.9, and didn't lose any data or apps in the process! It only took like 10 minutes and worked like a charm!
 
Thanks joshman229! It's good to know that it can be done that easilly! Did you find any tips for the process or is it really that straight forward?

I'll still, probably still wait for Scotty85's reply.
 
It was really straightforward -- I just ran the 3 commands (I already had adb installed, and put the fre3vo file in the same directory as adb first), and then Revolutionary ran just fine! I wouldn't blame you if you waited for scotty though, I would have but was just too intrigued
 
if you have adb set up allready,theres nothing to it. just put fre3vo into the folder with adb and fastboot/adb.

but if you want to wait,no biggie,im home and flashing the 2.11.605.9 RUU right now. in a few minutes ill put up some directions and a paste of the code box :)
 
restored 2.11.605.9 and ran zerg rush. as was expected,it failed ;)

Code: 
 =============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
 =============================================
    Brought to you by AlphaRev & unrEVOked.

Waiting for device...
Found your device: ADR6400L (mecha-1.05.0000, Android: 2.3.4, ROM version: 2.11.
605.9)

This is a beta release and requires a beta release key.
Please visit: http://revolutionary.io for more information.

Enter beta key [ serial: HT12CS012936 ]: DW5t1qMsVk8GiPEu
Beta key accepted - thank you for participating!

Zerging Root... this might take a minute or so.. Failed to get Root! :(
Press (almost) any key to exit.
if you dotn have adb set up,heres what ya do:

1)download miniadb_tbolt2.zip from here: mini-adb_tbolt2.zip
md5: ef01f616471673d3eeb71b4cac4b8118

2)set up adb:
-extract miniadb_tbolt2.zip and place the unzipped folder onto the root of your C\ drive on your PC
-open a command window. windows 7,click on start bubble,type "command" in the search box. a small black window should open up

3)download DHD Downgrade folder (from your link)

4)open the DHDDowngrade.zip file,then the folder contained inside of it. transfer Fre3vo into the tbolt2 folder with adb/fastboot.

5)in your command window: change to the tbolt2 directory by typing:
cd c:\tbolt2 (your promt should change to c:\tbolt2>)
*note that in the next few steps,anything in bold type is an adb command. you can directly copy from this window,and paste into your command window to eliminate typos.

6)enable usb debugging,plug in your phone via usb. select "charge only" mode.

7)make sure adb is seeing your phone:
adb devices (should return your serial number)

8) enter the commands from your link,one at a time,hit enter after each:

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

9)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. run revolutionary again. this time it will work really fast. i didnt have it install clockwork,but you can chose that option if you wish to use that recovery.

10)flash the superuser 3.07 files linked on revolutionarys info page

youre done :D


heres what youll see in the command window(red are my inputs,blue are just additional comments):
Code: 
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

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

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


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

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

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

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

ran revolutionary again. just for fun,heres what it looked like:

Code: 
 =============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
 =============================================
    Brought to you by AlphaRev & unrEVOked.

Waiting for device...
Found your device: ADR6400L (mecha-1.05.0000, Android: 2.3.4, ROM version: 2.11.
605.9)

This is a beta release and requires a beta release key.
Please visit: http://revolutionary.io for more information.

Enter beta key [ serial: HTxxxxxxxxx ]: DW5t1qMsVk8GiPEu
Beta key accepted - thank you for participating!

Root acquired!
Sending in Caroline...
Cleaning up...
Rebooting to fastboot...
When life gives you lemons, don't make lemonade. Make life take the lemons back!

Waiting for fastboot...
Rebooting to fastboot (Once moar...)
Success!
 
Out. Freaking. Standing. I have learned more in this thread than all others! I'll be rooting immediately! ...okay, not immediately. I have make dinner for me and my child... but almost-immediately!!


Stay tuned for results...
 
awsome. glad it worked out for ya :)

a couple root apps i cant live without:
-titanium backup(pro key is well worth the $$)
-root explorer

depends largely what you want to do with your rooted phone,as to what other apps would be good. most folks agree on wifi tether ;)
 
First thing I got was a wifi teather. Then titainium backup, then Rom manager for when I find a nice Rom. I'd like to over/underclock the cpu, but don't think It's as simple as it used to be.

Question: if I flash a new custom rom, will titianium backup restore my apps?
 
joshman299 said:
This is my first post here -- I registered just so I could say thanks for this method!! I used the link that Jelly Doughnut posted and it worked to perfection -- I'm currently rooted on 2.11.605.9, and didn't lose any data or apps in the process! It only took like 10 minutes and worked like a charm!
Click to expand...

Heartily seconded!! Jelly Doughnut for President! :D
 
You must log in or register to reply here.
Back
Top Bottom