I updated in a hurry to and wanted to SBF back, didn't find a very useful linux guide. I'm running Ubuntu 10.10
Files you will need:
1. sbf_flash
2. Full SBF 2.3.340
Guide:
1. Created a folder and place the files inside.
2. Make sure the sbf is unzipped into the folder.
3. Open a Terminal and change to the directory to your folder
4. Type chmod +x sbf_flash
5. Type sudo ./sbf_flash name of sbf file
6. Type in your password
7. Let it run until is shows "waiting for phone"
8. Restart the phone ( Make sure it's plugged into your PC )
9. Enjoy.
Hope it helps!
Thanks for the guide bro. This will be helpful down the road
this is one reason why i love ubuntu sbf'ing is so easy no drivers no programs
Thank you for this post. Messed up my x but was able to get it back up and runnning
Stuck. Mind adding Windows instructions?
mrkite38 said:
Stuck. Mind adding Windows instructions?
Click to expand...
Click to collapse
This is for folks on "Linux" to my understanding.
Such as a Windows based PC with a Linux partition with Ubuntu as a OS.
This maybe a good time to checkout Linux if you haven't already.
I'm aware of what Linux is. If the op has the ability to include windows instructions also, it would be convenient since the thread is already stickied.
AWESOME. Much easier...
Downloading files to do this now. One question..is this going back to stock or can I flash my back-up by doing this?
Sent from my DROIDX using XDA Premium App
Got most of this to work. When it tells me to reboot phone into bootloader..I can not access it. Can not get past the "triangle".
Sent from my DROIDX using XDA Premium App
sooo these instructions are reaaalllyy vague. for instance how do i get to the directory where my folder is? do i have the phone plugged in this whole time, or only when it shows "waiting for phone?" please make this noob useable. because i can't tell this right from wrong.
so i think i got to where i'm supposed to be..
[email protected]:~/Documents$ cd sbf/
[email protected]:~/Documents/sbf$ chmod +x sbf_flash
[email protected]:~/Documents/sbf$ sudo .sbf_flash VRZ_MB810_2.3.34_1FF_01
[sudo] password for derique:
i named the file i put the sbf_flash and the actual sbf file into "sbf"
so assuming that what i've done so far is correct, it won't let me type my password.. it actually won't let me type anything at all.
i got to [waiting for phone] but i didn't type in the "sudo" part of the command.
now i get to the part where it says waiting for phone.. so do i plug in when it's on, in the bootloader, or what?
when i plug in while it's in the bootloader i get this:
>> waiting for phone: FAILED: Could not claim usb interface
(Are you root?)
[email protected]:~/Documents/sbf$
but i don't think i'm rooted. i unrooted many times via z4root. so what else can i do guys? i need help
DeriquedeCoux said:
sooo these instructions are reaaalllyy vague. for instance how do i get to the directory where my folder is? do i have the phone plugged in this whole time, or only when it shows "waiting for phone?" please make this noob useable. because i can't tell this right from wrong.
so i think i got to where i'm supposed to be..
[email protected]:~/Documents$ cd sbf/
[email protected]:~/Documents/sbf$ chmod +x sbf_flash
[email protected]:~/Documents/sbf$ sudo .sbf_flash VRZ_MB810_2.3.34_1FF_01
[sudo] password for derique:
i named the file i put the sbf_flash and the actual sbf file into "sbf"
so assuming that what i've done so far is correct, it won't let me type my password.. it actually won't let me type anything at all.
i got to [waiting for phone] but i didn't type in the "sudo" part of the command.
now i get to the part where it says waiting for phone.. so do i plug in when it's on, in the bootloader, or what?
when i plug in while it's in the bootloader i get this:
>> waiting for phone: FAILED: Could not claim usb interface
(Are you root?)
[email protected]:~/Documents/sbf$
but i don't think i'm rooted. i unrooted many times via z4root. so what else can i do guys? i need help
Click to expand...
Click to collapse
It's asking if you ran the program as root, meaning you SHOULD use sudo. When it prompts for your password, just type it in and press enter. It doesn't show any placeholder characters.
Very vague instructions. I don't know what to do at all. Would like a bit more step by step in regards to what I enter in terminal.
double post.
SBF Ubuntu
Question, is it possible to SBF back to an older Bootloader? Thanks-AT
So, with this method i will be able to downgrade from OTA .596 to .340 ? Or can someone point out how can i get the .596 rooted and be able to install apex 2.0 RC. any help will be appreciated .
Yes, you can downgrade from the GB OTA to froyo with this.
Thank you.
Sent from my DROIDX using XDA App
Linux CD method
For those of you that are not very up on linux, the link below guides you into making a linux CD that you can insert into your windows laptop and contains all the programs you need to sbf your droid x back to froyo. You can then root it and upgrade to GB rooted using the 2 file method. It's almost idiot proof and the instructions are pretty good. If you can burn an ISO file onto a cd or usb drive and get your computer to boot from it then you should be able to sbf in about 10 minutes.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
nukeruss said:
For those of you that are not very up on linux, the link below guides you into making a linux CD that you can insert into your windows laptop and contains all the programs you need to sbf your droid x back to froyo. You can then root it and upgrade to GB rooted using the 2 file method. It's almost idiot proof and the instructions are pretty good. If you can burn an ISO file onto a cd or usb drive and get your computer to boot from it then you should be able to sbf in about 10 minutes.
http://www.droidxforums.com/forum/d...-solution-your-windows-rsd-lite-problems.html
Click to expand...
Click to collapse
I can vouch for this CD method. I used it to sbf from GB OTA back to Froyo. It is pretty idiot proof. It will even coach you on how to get to the bootloader screen. Just one hint: eject the CD before shutting down. It will boot back to linux when you start up again.
Related
I don't feel like reformatting it to make it look good. You can find my post at AllDroid.org or by following this link http://alldroid.org/Default.aspx?tabid=40&g=posts&t=554 let me know if this helped you out. If you follow it to a tee you should have no problems at all.
This is what the link that they OP posted says.
This is a walk-through of how to root your Droid X using the Birdman's method. This walk-though is based off of Rainabba's walk-though but I am going to go into a little bit more detail on some sections to make it more understandable for newer people to rooting.
Before starting this walk-through make sure you do not have any Server Applications running on your computer. This includes stuff like PDAnet's or Some Bluetooth server apps. I noticed that PDAnet will close the adb.exe so you can't do anything. It has also come to my attention that bit-torrent and U-torrent applications may interfere with this process shut those down to.
First you will need to download 3 files, just put these files onto your desktop.
Download the DroidXRoot_v2.zip file from http://alldroid.org/default.aspx?g=posts&t=493
Download the ADBDriver_v3_Google.zip from http://alldroid.org/Defa...40&g=posts&t=495
Download the correct SDK for your OS (Operating System) from http://developer.android.com/sdk/index.html
Now that you have all 3 files downloaded and put onto your desktop its time to do stuff with them.
Extract the DroidXRoot_v2.zip to drive "c:" and just name it "DroidXRoot" so it will look like "c:/DroidXRoot"
Extract the SDK folder into your "DroidXRoot" it doesn't matter what the name of this folder is I used the preset name. This should not look like "c:/DroidXRoot/android-sdk-windows"
Open the "android-sdk-windows" folder and then open the "Tools" folder. From here copy ALL of the files from this folder.
Back out of the "Tools" folder and then out of the "android-sdk-windows" folder. You should now be in "c:/DroidXRoot" Paste those files in here.
Right now Bookmark this page, doing the ADB driver install requires a reboot. This way you can find this post instantly.
Time to install the ADB drivers. For these instructions go to http://alldroid.org/Defa...40&g=posts&t=495 and follow the instructions.
Assuming that the installation went through with no problems, its time to move on.
(Where you see the "Run" at type the command in the quotes ("") but with out the quotes. You should also be able to just copy and past whats inside the quotes if your lazy)
Go to the phone it should still be plugged in from doing the ADB driver install if not plug it in now.
Go to your phone: Home, Menu Button, Settings, Applications, Development: Make sure the "USB debugging" option is enabled/checked.
Hit your Home Button and pull down the Status Bar and click on USB connection: Make sure its set to PC MODE.
Open a command prompt (On Windows 7 and Vista: Start, then type cmd, Right click the cmd and make sure you run as admin. Linix just open the terminal and make sure your running Root through it. If you don't know how to get that good terminal root.)
Ok now that you have your command prompt open Run "cd c:\DroidXRoot"
Run "adb devices" you should see your device listed with a whole bunch of numbers. If you get the message "No devices found" you didn't copy and past the files correct from the tools folder to the "DroidXRoot" folder or you didn't install the driver right from the previous post. If you get the message "adb is not recognized as an internal or external command" you may still have a server file running, make sure there all exited since you rebooted while installing the "adb" drivers. Well if you see your device your doing great keep moving.
Run "adb push Superuser.apk /sdcard/Superuser.apk"
Run "adb push su /sdcard/su"
Run "adb push busybox /sdcard/busybox"
Run "adb push exploid /sqlite_stmt_journals/exploid" If you have any problems with the pushing as in getting the "access denied" response then you did not start in an admin or root and need to restart...
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
Where doing great if you didn't have any problems. From here pick up your phone, and navigate to a screen where you can turn on/off your WiFi with a widget, turn your WiFi on. You will need to turn it off then back on instantly after the following command.
Run "./exploid" turn your Wifi off then turn it back on. Now follow the directions on your command prompt. When that completes you will be back at a shell prompt.
Run "rootshell" You will be prompted for a password enter "secretlol" and press Enter. You are now root but you still have more to do. (You will know that you are in root because your prompt will be a "#" instead of "$")
Run "cp /sdcard/Superuser.apk /system/app/Superuser.apk"
Run "cp /sdcard/su /system/bin/su"
Run "cp /sdcard/busybox /system/bin/busybox"
Run "chmod 4755 /system/bin/su"
Run "chmod 4755 /system/bin/busybox"
Run "rm /system/bin/rootshell"
Run "exit" to drop from root to a non-root user, you will still be logged into the phone.
Run "exit" again to drop back from your phone to your computer command prompt, you should be at "c:\DroidXRoot"
Now you need to confirm that you have established Root:
Run "adb shell"
Run "su" you should now see the "#" sign which indicates you are root)
WATCH YOUR DROID X SCREEN SO YOU CAN ALLOW SUPERUSER ROOT ACCESS!!!
Credits
Sebastian Kramer for this blog post - http://c-skills.blogspot...07/android-trickery.html
Birdman - for editing Sebastians work for the droidx
[mbm] - for answering birdmans many questions while root was tried (and failed xD)
Rainabba - for the original post located at http://alldroid.org/default.aspx?g=posts&t=493
The blog list
Birdman - @mrweeeedbirdman - http://stevenbird.info
Rainabba - @rainabba - http://rainabba.blogspot.com
Videos
Evidence of root: http://tiny.cc/DroidXRootProof
Video tutorial for root: http://tiny.cc/How2RootDroidXVideo
As is always the case with this sort of activity, you do this completely at your own risk. AllDroid, Rainabba, Birdman, and myself take NO responsibility for the outcome.
Edited 7/27/10
Added the section about shutting down the Bit-torrent and U-torrent applications - Thanks sanzy for finding that out.
Fixed a typo in line 21 - Thanks kdkinc fo noticing that.
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
ksidirt said:
Alright. Thank you very much.
I'm new to the DroidX. I'm trying to root my friend's phone.
Before updating to the OTA 2. 2 does the DroidX need to be "S-Off" as we Incredible users call it?
Or does this process cover that?
Thank you again.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
MrDanger said:
Simply put... S-Off does not work for anything other than HTC phones. So your Motorola Droid X will not need S-Off because it's not an option.
As of right now.. the leaked 2.2 is rootable but I don't know if the OTA that Verizon release for the DX will block the root or not.
To be safe, if you really want froyo now... use the leak, I have no problems with it, or you can wait until the OTA is released and confirmed rootable.
Your choice...To each his own
Click to expand...
Click to collapse
Awesome. Thank you.
I ended up using the following:
http://alldroid.org/default.aspx?g=posts&t=553
Worked first try.
If you're going to update to 2.2, you will need to run some additional commands prior to the update via adb or Root Explorer.
I've not had any issues with 2.2 - and I upgraded the day I got my X. No complaints here.
I'm also not really concerned with getting the official OTA -- chances are it (or a version of the update that is compatible with the leaked 2.2) will be found in the wild before long.
First off let me say this is 1000000% easier than RSD Lite in my opinion.
If you like this guide just give me a little thanks
You will need a few things downloaded.
The sbf: Download In this folder you are really only going to need the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file. You can delete the second one.
The sbf_flash file: Download
Once you download both put them in your home folder(user name folder) open terminal and type these things step by step
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Now your phone should start flashing. Let it do its stuff and it should reboot in about 20-30 minutes.
Hope it helped!
BTW this works if you are bricked
Thanks for the info. I've been wondering this; now I don't have to set up a windows VM when things go south. I usually find most things easier in Linux (once you get used to Linux).
Sent from my DROID2 using XDA App
A note to people who try and do the SBF. Wipe your data and cache in recovery if you have a boot loop after flashing. I have verified this method works, but I had to wipe my data and cache afterwards to get past an infinite boot loop.
Maybe someone can help me out. I've installed Ubuntu (first time user), and I have followed the directions up to the terminal part.
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
When I try these commands, here is what I get:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
bash: sudo./sbf_flash: No such file or directory
Also tried:
sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
sudo: unable to execute ./sbf_flash: No such file or directory
It shows up in the username folder (David), but for some reason I get no such file.
If someone can point out what I'm doing wrong, that would be great. Thanks.
draya1986 said:
Maybe someone can help me out. I've installed Ubuntu (first time user), and I have followed the directions up to the terminal part.
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
When I try these commands, here is what I get:
[email protected]:~$ chmod +x sbf_flash
[email protected]:~$ sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
bash: sudo./sbf_flash: No such file or directory
Also tried:
sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_ SECURE.sbf
sudo: unable to execute ./sbf_flash: No such file or directory
It shows up in the username folder (David), but for some reason I get no such file.
If someone can point out what I'm doing wrong, that would be great. Thanks.
Click to expand...
Click to collapse
Put a space between sudo and ./sbf_flash. It is not one command.
Sent from my DROID2 using Tapatalk
this forum is so awsome thank to all the people that post and help !
Matt4542 said:
First off let me say this is 1000000% easier than RSD Lite in my opinion.
If you like this guide just give me a little thanks
You will need a few things downloaded.
The sbf: Download In this folder you are really only going to need the DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf file. You can delete the second one.
The sbf_flash file: Download
Once you download both put them in your home folder(user name folder) open terminal and type these things step by step
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Now your phone should start flashing. Let it do its stuff and it should reboot in about 20-30 minutes.
Hope it helped!
BTW this works if you are bricked
Click to expand...
Click to collapse
How does this work if you are bricked? I am stuck at getting to the M logo on boot and can only get to Android Recovery Console. I can't turn off the phone after i plug in the USB and hitting up arrow i've never seen before. Also, the phone when at the recovery console isn't recognized as anything; even in windows
EDIT: Hmm, i was not using bootloader mode sorry, trying again!
Link is broken for sbf_flash.
Sent from my DROID2 using XDA App
zibrah3ed said:
Link is broken for sbf_flash.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
Ya, I noticed that too. Pretty easy to find it searching on google though and I think its not specific to model of phone. I found a link to it here:
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Motorola_Droid
patchm00 said:
Ya, I noticed that too. Pretty easy to find it searching on google though and I think its not specific to model of phone. I found a link to it here:
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Motorola_Droid
Click to expand...
Click to collapse
Thanks I wasn't sure if it was specific to this phone or not. I had found another copy using the google.
patchm00 said:
How does this work if you are bricked? I am stuck at getting to the M logo on boot and can only get to Android Recovery Console. I can't turn off the phone after i plug in the USB and hitting up arrow i've never seen before. Also, the phone when at the recovery console isn't recognized as anything; even in windows
EDIT: Hmm, i was not using bootloader mode sorry, trying again!
Click to expand...
Click to collapse
I WAS using the bootloader, and RSD lite says the "Failed flashing process. Phone [0000]: Phone is not compatible with multi-interface super-file. [0x703B]; phone connected." I have no idea on what to do now.
Sent from my DROID2 using XDA App
I followed the steps and now I am stuck in bootloader.... The process seems to have been completed, but when I turn on phone it directly goes into bootloader.
It shows the following.....
Bootloader
D2,35
Err:A5,70,70,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
Which sbf did you use and did you get the OTA update (2.3.2)?
Might I interest you in this threadit has the same instructions with more explanation just ignore the stuff about the livecd because you already have linux.
duongtran said:
I followed the steps and now I am stuck in bootloader.... The process seems to have been completed, but when I turn on phone it directly goes into bootloader.
It shows the following.....
Bootloader
D2,35
Err:A5,70,70,1F
MEM_MAP Blank
Service Req'd
Battery OK
OK to Program
Connect USB
Data Cable
Click to expand...
Click to collapse
Boot into recovery by holding x and power, then press the search key at the android. Wipe data and cache, then reboot.
I figured it out! Thanks for info newk8600. I was using the sbf found in this thread, but I needed the newer sbf(2.3.20) because I somehow got the OTA update. I have no clue how I got it because I never updated my phone in over 3 weeks. The last time I updated my phone was Fission beta or alpha. But either way thanks developers for everything you guys saved my expensive paperweight.
Matt4542 said:
First off let me say this is 1000000% easier than RSD Lite in my opinion.
If you like this guide just give me a little thanks
You will need a few things downloaded.
....
Once you download both put them in your home folder(user name folder) open terminal and type these things step by step
Plug your phone in via USB now and turn it off and press up on the keyboard to go into the bootloader.
1. "chmod +x sbf_flash"
2. "sudo ./sbf_flash DROID2_X6_2.2.20_SHADOW_BP_C_01.09.05P_P2_USERBLD_SECURE.sbf
Now your phone should start flashing. Let it do its stuff and it should reboot in about 20-30 minutes.
Hope it helped!
BTW this works if you are bricked
Click to expand...
Click to collapse
Thanks! But can you tell me it this will also work on the motorola milestone ? (other SBF file ofcourse!) because I tried updating to 2.2 but RSD lite wasn't able to find my phone or something.
Maybe someone else has an idea what the cause would be for it not to function as it should ?
I bet it would work for the milestone also with the correct .SBF file. Just make sure you use the same syntax with the correct filename: sudo ./sbf_flash [sbf_file_name] (make sure the file doesn't have spaces or it won't find the right file).
I wrote a small script.
DOSBF (kind of like DORoot and DOOverclock). You just got to give it permissions and run it, and yeah.
www.kimete.com/download.html
Awesome! Sounds easy.
Sent from my DROID2 using XDA App
newk8600 said:
Awesome! Sounds easy.
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It is actually! Super easy!
Ive just ordered a desire z and have been reading a bit on the uber root method.....
What i want to know is can I use a file manager to install the visinary.apk and then the terminal emulator from the phone to run all the adb commands?
Reason i ask is cos A) ADB freaks me out....just the install instructions make my head spin and B) i havent got any space on my even if i wanted to install it....
Im aware that you need to install the gscript to /data/local but can this be done just by dropping it into the relevant place rather than pushing it using ADB?
and assuming I can?
Which bits of the commands do i run ? looking at the following.....
adb push gfree /data/local
adb shell
su
cd /data/local
chmod 777 gfree
./gfree
sync
do i just pick this up from the point of SU?
oh and errr if ive completely got the wrong end of the stick then please say.....id sooner look stupid than have a £420 brick
cheers peeps
Yes, if you want you can copy the gfree program to your SD card via some other method, and then pick up the instructions from the su onwards.
An alternative is to run the "rage" method of rooting, but if you don't like adb (it's a lot easier than it might look) then maybe that's not for you.
steviewevie said:
Yes, if you want you can copy the gfree program to your SD card via some other method, and then pick up the instructions from the su onwards.
An alternative is to run the "rage" method of rooting, but if you don't like adb (it's a lot easier than it might look) then maybe that's not for you.
Click to expand...
Click to collapse
TBH its not the ADB commands that i struggle with its the setup of ADB itself.....ADB, SDK, HBOOT drivers, issues with windows 7 etc....
Im happy running the commands and sort of understand what im asking my phone to do so if i can get by without ADB i will try
Thanks for clarifying though
rtorbs said:
TBH its not the ADB commands that i struggle with its the setup of ADB itself.....ADB, SDK, HBOOT drivers, issues with windows 7 etc....
Im happy running the commands and sort of understand what im asking my phone to do so if i can get by without ADB i will try
Thanks for clarifying though
Click to expand...
Click to collapse
I suggest you to read the Easy root / flashing tutorial and FAQ post located at android development subforum
And regarding ADB, if you daownload qpop's "uber root" package, everything required is inside the zip, even ADB is inside
i used gtrab's guide...
super easy and no adb necessary.
http://forum.xda-developers.com/showthread.php?t=835777
bradleymor said:
i used gtrab's guide...
super easy and no adb necessary.
http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
Things evolve quicky, problem with this guide is hBoot step was very risky, and it was sort of a "false" S-OFF
The newer method is easyer, safer, and doesn't require manually flashing hBoot
The guide has been reestructurated accordingly
gtrab said:
I suggest you to read the Easy root / flashing tutorial and FAQ post located at android development subforum
And regarding ADB, if you daownload qpop's "uber root" package, everything required is inside the zip, even ADB is inside
Click to expand...
Click to collapse
I've already read them pal, that's why im here...I was just clarifying that I could use the terminal emulator rather than adb.....I'm pretty sure what i need to do now so its cool
Cheers peeps
Sent from my HTC Hero using XDA App
rtorbs said:
I've already read them pal, that's why im here...I was just clarifying that I could use the terminal emulator rather than adb.....I'm pretty sure what i need to do now so its cool
Cheers peeps
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
The reason the guide is all ADB is that its much easier to get right with adb...seriously there's no install needed, just open up a command prompt in windows seven (or use the packaged cmd.bat from my zip) and follow instructions. No install needed, no complexities, no messing around with a very limited terminal clone.
But yea, as long as you get the gfree file onto your phone it should be ok
qpop said:
The reason the guide is all ADB is that its much easier to get right with adb...seriously there's no install needed, just open up a command prompt in windows seven (or use the packaged cmd.bat from my zip) and follow instructions. No install needed, no complexities, no messing around with a very limited terminal clone.
But yea, as long as you get the gfree file onto your phone it should be ok
Click to expand...
Click to collapse
Ok cool....sounds a bit more promising....will give it a bash....at least I know I now have a plan b with the term emulator if I have problms
Cheers
Sent from my HTC Hero using XDA App
As someone who had never even heard of ADB and is on his first Android phone..believe me when I tell you that all these different instructions and methods made my head spin! What I ended up doing was (can't remember which "method" it was called) just downloading the VISIONary program onto my SD card, and then running it right from the phone to achieve my ROOT. Once I was rooted, I used the UBERROOT method for S-OFF. I simply downloaded the ADB program (and whatever else it was that came with it)..let it go thru it's updates and made sure the computer recognized my phone (by making sure drivers were installed). Plug your phone into the computer..open up the gfree program you downloaded...and inside there is two main programs..and exe and the cmd. I ran the exe, then simply opened up the cmd program..entered the necessary commands..and viola! It really was simple once I finished it.
I read many thread but didn't find clear answer for this question.
I have a vodafone htc legend with froyo updated trought ota
I would, root it and install HTC rooted rom.
any body can help with the steps and tools need it?
thanks a lot
follow this http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
it is not rooting, it is downgrade, what's not same
rolks said:
it is not rooting, it is downgrade, what's not same
Click to expand...
Click to collapse
he have official froyo... then he must downgrade first or what??
FIRST HAVE TO DOWNGRADE
follow this http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
Click to expand...
Click to collapse
THEN U CAN ROOT
http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
Great!
If I undertood right...
First downgrade (this is something we could not avoid) then root.
Let me try!
Ill back!
Thanks
MontseCat said:
Great!
If I undertood right...
First downgrade (this is something we could not avoid) then root.
Let me try!
Ill back!
Thanks
Click to expand...
Click to collapse
i followed these steps and now i have rooted legend with BlaYo ROM B 0.2...
GOOD LUCK
I tried yesterday and having some troubles with Android sdk, doesn't work I don't know if any trouble with its installation.
Need to read carefully the instalation process and try again.
The only issue is find time for ths... its chrismas so, some familiar meetings
I'll back!
Oh!
I tried once again with not succes.
when running "crackin"...
starts with...
"Copying tools"
"adb" is not recogniced as command internal or external
program or file executable...
And remainds with same message for serveral lines till finish!!
Nothing happens.
I installed the android sdk package and added the hack4legend-v5.zip contenst on android-sdk-windows\tootls folder
Obviously I am doing something wrong but I am not able to locate where the problem or mistake is!!
any idea?
thanks
I downgraded my Legend from the OTA 2.2.
Now the ROM version is 1.31 which should be correct, but the HBOOT version still is 1.00, which is according to this guide (http://forum.xda-developers.com/showthread.php?t=746454 ) the wrong one, it should be 0.43.... any ideas on this one?
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
nae64 said:
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
Click to expand...
Click to collapse
Sorry I don't follow you at all.
I currently have my legend working with HTC Sync, witout problems, so don't undesrtand, shall I remove an reinstal it after installed android sdk to?? or..
thanks
No, that was just my problem at first when I had to move to a Windows PC for the downgrade, adb requires HTC Sync. So you should be fine.
But now that I read your problem again, my solution would not even fit I guess your tools directory does not contain the adb.exe. But the directory platform-tools in the android-sdk folder does. I just copied over the contents of the hack zip to platform-tools and did it from there... what ever, now I am having the problem i described above...
nae64 said:
I downgraded my Legend from the OTA 2.2.
Now the ROM version is 1.31 which should be correct, but the HBOOT version still is 1.00, which is according to this guide (http://forum.xda-developers.com/showthread.php?t=746454 ) the wrong one, it should be 0.43.... any ideas on this one?
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
Click to expand...
Click to collapse
Hmm my HBOOT version is 1.01
Sent from my HTC Legend using XDA App
Okay, thank you very much, root completed successfully even with HBOOT v1.00
nae64 said:
... But the directory platform-tools in the android-sdk folder does. I just copied over the contents of the hack zip to platform-tools and did it from there... what ever, now I am having the problem i described above...
Click to expand...
Click to collapse
I done as you said and succed,
Now the problem is
CR--rw----
So fails
the message at the end is xxxx permision denied.
I don't konw how to put an image of the scren. sorry
what whall I do now?
MontseCat said:
I done as you said and succed,
Now the problem is
CR--rw----
So fails
the message at the end is xxxx permision denied.
I don't konw how to put an image of the scren. sorry
what whall I do now?
Click to expand...
Click to collapse
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.
janarp said:
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.
Click to expand...
Click to collapse
Ok I Istalled the Visionary and temorary root,
I don't know how to connect via 'adb' and do su...
so, just stoped here and waiting next instruction. Sorry work as neel!!
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
janarp said:
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
Click to expand...
Click to collapse
even with this guide I didn't succed!!!
What I done is just temporary root with visionary then run again the adb but remains the same,
sorry I don't see where lost!!
In the following I will assume a Windows-PC:
1. Restart your phone to start from scratch, make sure 'TempRoot on boot' (or sth along this line...) is NOT checked
2. Run the crackin.bat, which you put (along with all other files in that download) into the directory containing the adb.exe (which is, at least for me, the platform-tools directory)
3. when it fails (it will), TempRoot using VISIONary, leaving everything unchecked (no System Read Write, even if that seems like a good idea)
4. on your PC, go to a Terminal (Windowsbutton + R, enter 'cmd' without quotes, press enter) , navigate to the folder crackin.whatever is in using the cd command like in my following example, but with the correct, full path
Example: 'cd "C:\\Programm Files\Android\andorid-sdk\platform-tools"' (again, without the single quotes (preserve doublequotes))
5. in that same Terminal Window, enter 'adb shell' (again, without quotes). The prompt should change to a dollar sign. Then enter 'su' (you know, without quotes...), and when the prompt changes to a '#', the TempRoot was successful and we can resume. Make sure to leave that Terminal open, you can use it again when rooting.
6. On a Windos System (32bit preferred) run the RUU.something.exe and follow these steps.
7. follow the main rooting guide, in which you will have to open a Terminal Window in the directory you unzipped. This is done with the same method I described above (opening cmd, 'cd' command)
I hope this makes it more clear =)
Edit: btw, this is a full guide, feel free to pick out the stuff you need, because I really did not understand what your problem was =) as a rooting guide I used this: http://forum.xda-developers.com/showthread.php?t=746454
MontseCat said:
even with this guide I didn't succed!!!
What I done is just temporary root with visionary then run again the adb but remains the same,
sorry I don't see where lost!!
Click to expand...
Click to collapse
i belive u have same folder names like me...
first i connect my phone with pc then i open command (start and type cmd)
Code:
cd C:\android-sdk-windows-1.1_r1\tools
then
Code:
adb shell
and then
Code:
su
and then follow nae64 post
point 6 and 7
hello
i just see how to root KF and it's so hard !!
i don't know how to use ADB
This seems pretty helpful in figuring out adb
http://forum.xda-developers.com/showthread.php?t=502010
When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.
http://rootkindlefire.com
Watch the YouTube video or do the step by step method. You do need to download Android SDK and install an USB driver as well. Took maybe 15 minutes all together
Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)
I just did it following this guys video. Quality is great and so are the instructions.
Shows:
-how to install adb
-how to edit the appropriate files
-how to root KF with superoneclick
http://www.youtube.com/watch?v=f409qNgpzSA&feature=related
mewshi said:
When I rooted mine a few days ago, I had spent the night before trying to do it on Windows. Two computers, and none of the files that were supposed to exist did, even thought I had followed the directions up to that point.
Oddly enough, the Linux/Mac tutorial on the forums here works incredibly well and is incredibly easy. If you can use Linux (even a LiveCD or USB drive install) that is probably going to be the easiest method.
Click to expand...
Click to collapse
I'll second this. It's extremely simple and straight forward. Much simpler than the Windows method if you're at all comfortable with the command line. And as the OP said you don't even need Linux installed you can use a live CD.
Sent from my HTC Flyer P512 using Tapatalk
sum182 said:
Once you get to the point to make the .android folder in your users folder (if you dont have sdk installed), you have to use the command prompt (cmd) or else you will get the "You mus type a file name" error. The command is " mkdir .android ". just make sure you do it in the proper directory (cmd should show C:\Users\*yourusername*)
Click to expand...
Click to collapse
This is what I had to do basically.
I created a folder android, and wouldnt let me name it .android
So in command prompt i renamed it, then I put an empty txt file, renamed it to the necessary ini, pasted that line they tell you and it worked first try.