Root DETAILED Leak Root Tutorial

Ok thanks, I have a reply going there.

frankly, i'm not sure why every one is attempting the engineering bootloader. i didnt need it for anything

v941726 said:

frankly, i'm not sure why every one is attempting the engineering bootloader. i didnt need it for anything

Click to expand...

Because we still had the 1.49.0000 s=on locked bootloader following the root process.

I was running white widow fine with 1.47 s-on,

Now I don't know what is going on. Phone doesn't even show up in adb anymore.

Well it shows up if I let the original root rom boot up. Let me see now.

Ya it doesn't show up when in fastboot. For some reason fastboot gets permission denied.

xliderider said:

Because we still had the 1.49.0000 s=on locked bootloader following the root process.

Click to expand...

so do i. i have root and am clocked at 787MHz

wasnt the bootloader s-on an old problem, with the old root methods?

I ran these instructions again and it installed the recovery from adb

It is installing white widow again..

But i still do not know why I cannot use fastboot. Maybe it is my mac somehow?

forgot to mention that i also have wifi tether too. i guess i used a combination of methods. i would have to upload my tools directory. then you guys could do it in 5 minutes. 227mb. but thats trial and error stuff that could probably cut down to 10mb.

yeah. already got it down to 25mb. had roms in there just in case. and most was sdk stuff that is not needed after you install the sdk.

got it down to 18 mb..just need to run a few batch files mostly for root, overclock, and wi-fi tether will post the link shortly. again, there are lots of credits to go to people but i put lots together from xda and here

here is my tools folder: http://www.multiupload.com/ALL7IOLX2M this folder has all the files you need already in it. except the engineering bootloader stuff. it also includes wi-fi tethering. you just need your drivers. i'm sure by now you have them installed. this is for windows only!

assuming you have sdk installed and your android drivers installed: 1st. just place the file in your c drive and unzip it there. such as right click and left click "extract to tools\. this will place a directory called tools in the root of c drive. open the folder. you can rename it whatever you like.

right click on a blank space in this NEW folder and left click "run command from here". drag 1.bat to the cmd window and press enter. this will push tether, busy box, and superuser to your card. you will get an error with the update file..here. all we want is tether anyway. i should have edited the bat file but im getting ready for my dinc.

at this point copy all your zip files to the root of your card(i.e. rom, the update file you already have, engtools, overclock kernel)..no need to rename your files to update.zip. recovery will see them as they are named


now run runindos.bat from the cmd window. it will give you instructions and reboot your phone.
IF YOU ARE GOING TO INSTALL A ROM THEN READ ALL THE REST BEFORE DOING EACH STEP
now, apply your zip files one at a time. no need to reboot your phone after each, unless you want to. do all 3 and let each finish. now. reboot your phone.

IF YOUR GOING TO INSTALL A ROM FORGET EVERYTHING.. JUST KIDDING! depending on your rom and its features you will just need your rom zip. most likely it will give you what you want.

again: by the time you have got this far in this thread im assuming you are pretty much in place with sdk and everything else (but sdk stuff is already in the folder anyway). but the files are there and its a matter of running a few batch files. im sure you even have the zip files you want and/or need on your zip card already too

v941726 said:

frankly, i'm not sure why every one is attempting the engineering bootloader. i didnt need it for anything

Click to expand...

xliderider said:

Because we still had the 1.49.0000 s=on locked bootloader following the root process.

Click to expand...

v941726 said:

so do i. i have root and am clocked at 787MHz

wasnt the bootloader s-on an old problem, with the old root methods?

Click to expand...

Well now I have 1.49.2000 s=off for bootloader. Just need to get Amon Ra recovery back, where my nandroid backup is. I guess I need to use the hack4.zip from adb when I get back home to the computer to get root back and hopefully recovery as well.

For some reason i have hit a snag at Step 7

List of devices attached
???????????? no permissions

Is what comes up when i type in ./adb devices



I'm using Ubuntu. Any ideas why it can't find my phone?

surgeon0214 said:

Is this in the root tutorial or in the boot-loader tutorial. Technically speaking the boot-loader change is just a plan b if for some reason somthing happens to your phone (un-rooted somehow). But you can still root with the same method as before so I see no need to change the bootloader.

Click to expand...

Root tutorial.

yep

It probably has to do with the phone driver. I'll have to try on my windows PC later.

OK well the reboot didn't work.
I also went through and tried this
http://esausilva.com/2010/05/13/setting-up-adbusb-drivers-for-android-devices-in-linux-ubuntu/
Still nothing

Yeah i do. Sucks i'll have to start back over again. But hopefully it won't cause as many problems.
Thanks for your help.

Michaelrk said:

For some reason i have hit a snag at Step 7

List of devices attached
???????????? no permissions

Is what comes up when i type in ./adb devices



I'm using Ubuntu. Any ideas why it can't find my phone?

Click to expand...

No permissions is an issue with the driver for the phone under ubuntu.

In a terminal type

sudo pico /etc/udev/rules.d/51-android.rules

that will start a file named 51-android.rules in the correct location

in that file copy and paste

SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", SYSFS{idProduct}=="0c02", MODE="0666", OWNER="yourusername"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", SYSFS{idProduct}=="0c01", MODE="0666", OWNER="yourusername"

and change the "yourusername" part with your user name

restart udev with

sudo /etc/init.d/udev restart

unplug the phone and plug it back in. try step 7 again