Related
THIS IS STRICTLY A GUIDE TO PRE-PARE YOU ON HOW TO SET-UP ANDROID SDK AND ADB DEVICES(DRIVERS), IF YOU ALREADY HAVE THAT SET-UP YOU CAN SKIP TO EUGENE'S POST ON HOW TO ROOT MYTOUCH SLIDE.
Last Updated:6/29/2010 at 11:36PM
Any other issues to deal with the actual process to root your mytouch slide should be directed toward his thread. Thank you for reading.
Okay so after about 4 hours of reading and asking questions I finally got my device rooted. My biggest problem doing this was that the guide in this forum was basically showing you how to root the phone if you had previous experience with androids and android SDK which I did not.
Note: If you have SDK installed already on your pc please delete your SDK folder and start from scratch for best results with my guide.
1. download Android SDK.(You will not have to use Android SDK physically but you will need it installed on your pc to root your phone) Save it to your PC where you can find it.
2.Extact the .zip file, do not rename just yet for the sake of my guide you also may delete the .zip file of it to keep clean.
3a. Move android-sdk-windows* out of the android-sdk_r06-windows folder onto the root of your C:/ drive.
*=the name of the folder may be different if you use a different operating system but since I do not own the other systems I cannot really tell you what the folders name.
3b.Now that you have the folder in the correct place you can rename the folder from "SDK-Anroid-Windows" to something easier such as "SDK" "Android" or something else which you will remember has to do with SDK.
This next part is not required, if you do not feel comfortable doing this, then don't, there is other ways around this.
3c.You also have the option to change your the path of your directory on your system. To do this, follow the instrustion here on step 2.( I would like to thank fermunky for his input)
My directory was pointed to the C:/Program files so I switched it to C:/android/tools , for those who do not know what this does it simply makes it so you do not have to change directory in step 7 (CD), you will only have to open your command prompt and then your ready to enter "ADB devices" .
4.Install the correct ADB drivers from pdanet . Select the proper download based on your OS if you do not know what bit you are using click start, right click computer, click properties, the system type will show you the proper file to download. and save it to your computer where you can find it.
5.Start the installation process for the ABD drivers, Follow the on-screen directions to install the drivers ( make sure your phone is not plugged into the pc at this time)
6.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools**
**=your file directory might be different than this, it depends what you renamed your folder
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.***
***=If it is correctly connected you will see a device listed and under attached it should say device.
After you have this all set up you are ready to root your phone via the guide from Eugene.****Remember you need to add the contents from his root.zip file into the tools of your SDK folder in order to root your phone.
****=Eugene's guide has changed since I wrote this but you still are ready to follow his steps. I plan on rooting someones slide soon based off his steps and will edit here if I need to add anything)
Thanks for reading.
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
the other guide mentions to create a new variable such as:
For Variable Name type: adb
For Variable Value type: C:\android-sdk-windows\tools
Click to expand...
Click to collapse
so would i follow this? or list that directory under the already-enabled PATH variable?
Yeah just use the existing PATH variable, and only need the path, no need to include variable names.
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
For the uninitiated, and yes it's common sense
When I was using Windows (as I'm using Ubuntu now), and reading all the adb guides, for ease of use and to prevent people from getting confused, they name the sdk as "android-sdk-windows", which is fine for a newcomer (it's the same for Ubuntu except the "windows" part and the slash direction \ vs. /). However, you can name it whatever you want. You just need to make sure to have the same name in your path. For example, I'm lazy and my typing skills aren't that great. I don't want to type 19 characters (yes, I counted). So I just named it simply "android". 7 characters from 19. Its way more efficient for me. I've contemplated naming it "andy" or something to shorten it further. But, again, you don't even need to name it anything android related. You can choose to name it r2d2 (see what I did there?) if you want! Just my 2 cents. Thanks!
Yeah I could of renamed it something different but I didn't think about that til after it was written, I will fix it as soon as I am on an actual pc. I will also include how to do it via mac and ubuanta(sorry if I miss spelled)
kingofyo1 said:
I think this is a very valuable how-to for the noobs out there and im going to pass this up the chain to get sticky'd. I also posted this in the slide bible. Good job, OP
Click to expand...
Click to collapse
Thanks kingofyo. Glad I could give back to this forum after all it has done for me. And if I find any other helpful tips to help make rooting easier I'll be sure to include it.
Sent from my T-Mobile myTouch 3G Slide using XDA App
fermunky said:
One thing I did that makes a lot of this a whole lot easier, is to add the directory to your Tools folder to your system's PATH variable, as explained in Step 2 here: http://developer.android.com/sdk/installing.html
What this allows you to do is run the commands with Tools (ADB, fastboot etc) from anywhere within the command prompt, without having to cd to your c:\android-sdk-windows\tools folder. This way, you can put any other update files, into any directory you want.
For example, let say i have update.zip directly on the C drive. I can simply go to command prompt, and just type "cd" and get to the root of the C drive, and then can just run "adb push update.zip /sd/card/". No need to store everything into the tools folder.
Click to expand...
Click to collapse
I will leave that as an option for others to pick if they want to do that, as some might not want to change their directory to follow that path.
oo, this cleared up a few things for me! thanks!
eff0rtless said:
oo, this cleared up a few things for me! thanks!
Click to expand...
Click to collapse
ah what pat of seattle do you live in? I live up in mukilteo.
rlacsamana1989 said:
7.Check to see if you did this correctly, plug in your phone and open your comand prompt on your computer and type:
cd C:\android\tools (your file directory might be different than this, it depends what you renamed your folder)
then type:
adb devices ( this will now show all the devices connected to an adb devices)
Check to see if your device is listed and connected properly.
Click to expand...
Click to collapse
when typing in 'adb devices', i get this message:
Code:
adb server is out of date. killing...
* daemon started successfully *
however, it does continue to list my device as attached.
the full message is:
Code:
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HTxxxxxxxx device
*the x's do represent a valid serial number
-------------------------------------------------------
is this a problem? and will i run into any problems trying to successfully root?
note: i have done a search on this and the results returned as the program DroidExplorer being the culprit, however, i do not have that program installed.
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
rlacsamana1989 said:
Do you have the most updated Android SDK? And try searching that topic on google and see if you can find people with the same issue.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
poetik517 said:
I believe so. I actually installed of the available packages as per the initial guides instructions. If I needed to uninstall & reinstall the sdk, how would I do that?
As yes I have done a thorough search. I mentioned the results in my original comment.
Click to expand...
Click to collapse
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
cdt82002 said:
Ok so I just got my slide and want root. Im coming from a rooted g1 which has a completely different root process and so I have no experience with sdk and adb sadly. Im running windows 7 and I have followed this guide step-by-step but every time I get to the point where I type "loop" in eugenes guide it says it does not recognize the command... I saw somewhere sdk components are not supported by windows 7. Is this true? And is there a way around it? I also saw somewhere that it could be that I dont have my enviroment variables set correctly. Im not sure by what it means to add the full path to the tools\ directory to the Path variable value. When I double click Path default displays:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
Where do I add it?
My tools directory is set in the root of my C drive as
C:\SDK\tools (most people typed android, renamed mine to just SDK, seemed faster)
This is what im trying to figure out at this point. Sorry if it very noobish.. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Okay my guide is to set you up to root, you need to download slideroot.zip from eugene's how to guide. It will download a folder so you need to save it somewhere you will find it. Once you have it saved extract the files and the files within that folder you need to put in the tools of the sdk directory. Do not just drop the folder as that would change the directory even more to another folder. A file in that folder is what actually makes the loop feature work and there are other things you will need from that folder to root.
And to this. %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QuickTime\QTSystem\
you just need to delete "Program Files (x86)\QuickTime\QTSystem\"
and then replace it with your directory to your C:/
rlacsamana1989 said:
You should be able to just delete the folder it downloaded. and make sure you empty your trash. I will look at what the issues can be. and let you know if I find anything. I'm pretty good at that
Edit: Have you seen this post? I'd start from the first thing they say which is going to task manager and ending adb.exe and if that doesn't work go to the next thing they stated to do. If none of those work come back and I will try and figure it out.
Click to expand...
Click to collapse
a successful uninstall & reinstall of the sdk worked for me. i no longer get the 'adb server is out of date' message when trying to list devices.
when reinstalling all of the packages in sdk, i did note this message:
Code:
'Downloading Usb Driver package, revision 3
Installing Usb Driver package, revision 3
Installed Usb Driver package, revision 3
Updated ADB to support the USB devices declared in the SDK add-ons.
'adb kill-server' succeeded.
ADB: * daemon not running. starting it now *
ADB: * daemon started successfully *
'adb start-server' succeeded.
but its a good thing =]
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
poetik517 said:
another note:
when i have sdk all setup, HTC Sync no longer seems to work or recognize my device as connected, even after ending adb.exe in my task manager.
Click to expand...
Click to collapse
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
usbdeview
rlacsamana1989 said:
Have you tried re-installing the pdanet drivers again. And make sure you aren't clicking the box that pops up on the bottom of the screen. And if that doesn't work I know there is a program I have installed on my pc that let's me delete drivers I just can't remember the program so ill post it once I get home from work.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
I think the program you're trying to remember may be "usbdeview"? This program allows you to disconnect or uninstall drivers.
Since i'm bored, i wanted to experiment with ADB, i know what it is, and what happens on it.
I've never used it, but i want to start
i just downloaded android SDK
idk what else to do, i searched ADB on the windows search thing, but i get 3 results, 1 is from something else, and another when i try to open says adbwinapi.dll is missing from your computer. try reinstalling the program to fix this problem.
i can't find adb on the folder i downloaded, whats wrong?
can someone tell/link me to a step-by-step instruction?
Sorry nobody got back to you sooner.
ADB is usually hidden in the android-sdk-windows\platform-tools folder.
I'm not sure which file you extracted yours to, but I extracted mine to C:Android so my path in cmd looks like C:Android\android-sdk-windows\platform-tools>
Once in there type adb and hit enter for a list of commands. Connect your phone and type adb devices to see if it can find it etc.
Good luck. You can really F stuff up with adb.
Not sure where else there are tuts but I learned from the ADB for dummies tut in the G1 development section (when I had my G1).
I would link but I'm on my phone and can't figure out how/if it can can be done w/ the app. Just go to the informative links sticky. Theres lots of basic android info there. Some translates to vibrant some doesn't. But good reading nonetheless.
Good luck
XDA Mobile
Can use terminal emulator to run adb commands.
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
I would take the time to learn ADB or wait until a one click is out. Learning ADB while rooting your phone could easily break it.
what os are you using?
svalle713 said:
I need help rooting my Tb , does anyone have a video or direct me to one that can help! I don't know how to use ADB!
Click to expand...
Click to collapse
Honestly just take the time to read the procedure, other help topics on these forums, and take your time when actually going through the procedure.
I had never used ADB either or rooted an android phone for that matter, and I gotta say, rooting the TBolt was cake.
I just took my time with it ensuring I typed in the commands properly.
But if you need a video, here you go: http://www.droid-life.com/2011/03/22/video-rooting-the-htc-thunderbolt/
what drivers do we need for the process, are they only the htc sync drivers? where can these be found?
Android SDK should be extracted/installed straight onto the C:\ directory to make it easy. Open the android-sdk folder and in it is a program sdkmanager.exe, open that and you can reject all of the downloads but scroll down and install one called the "google usb driver package" which may be necessary, I'm not sure (you should also have the htc sync drivers installed)
The contents from the "exploit.zip" should be extracted into the folder "platform-tools" within the android-sdk folder. Plug in your phone to the usb and open the command prompt. To get started open the command prompt (like a dos prompt) and get the prompt into the folder 'platform-tools' and type "adb devices" then hit enter. If your phone is connected and you have "usb debugging" enabled on your phone from the settings, your phone should appear and you can begin the instructions from jcase
Heres the deal. I have a MAC with a newly installed hard drive. On my old hard drive I had everything setup with SDK and Adb but that was when I had an HTC Hero. My problem is this: When in terminal my damn computer keeps prompting me for a password but it doesnt allow me to type anything except control C which aborts the program. It never was like that with the old hard drive.
2. Ive dl SDK for MAC unzipped it and saved it to my desktop and my hard drive.
3. When I click on tools it says "adb_has_moved.txt"
4. It says the adb tool has moved to platform-tools/ and if you dont see this directory in your SDK, launch the SDK and AVD manager and install "android SDK Platform-tools and also update my path environment variable to include the platform-tools/ directory, so I can execute adb from any location. What the heck does this mean and how do I fix it. Also how do I know if SDK is installed correctly.
5. I DL some version of eclipse that was recommended from SDK but I dont know how to use that either.
6. I have tried all the root methods shown here in XDA except the on with the Dock since I dont have a dock.
7. Also ADB does not recognize my device and my debug is selected. I cannot get it to find my device.
8. One last question when some instructions say unzipped and move the root exploit to /data/tmp/ is that the file labeled under sdcard/data or is it the one inside the Android Folder listed as "data"
Please anyone help if possible.
let me try that
Stupid question but How do I launch SDK?
laraiza said:
Stupid question but How do I launch SDK?
Click to expand...
Click to collapse
Make sure your phone has USB Debugging Mode enabled. Otherwise, adb will not recognize your device.
Check this thread: http://forum.xda-developers.com/showthread.php?t=879701
However, you will have to modify for MAC.
In my opinion the easiest way to root the Photon is still using the dock method. Otherwise, try the One Click Root method (Torpedo) as mentioned above. Then you don't have to worry about issuing all the commands.
I got it done I got it done. What I did was borrow my daughters windows netbook and the one click method worked on the first try. Thanks to all who replied. I will definitely hit your thanks buttons.
Sent from my MB855 using XDA App
im sorry.. my tool was a one click i dint think i needed to give it instructions.. especially teh part of how to run it on your computer... just fyi.. when invoking sudo (to do things as admin/root) on your computer. you are asked to enter in your password.. as a privacy/security feature it will NOT display any characters.. ergo it looks blank...
as you arent teh first one to run into this issue ill add instructions for mac users ( i know anyone running linux can figure out how to run a bash script, and windows users have a bat file after installing 209387249087 drivers... but they still figure it out ;P)
Like me I'm sure many of you were very surprised to log in today, as most have been doing everyday for the past month or so to find that not one, but two methods for obtaining s-off on the DNA were released within minutes of each other. First Revone and then, coincidentally enough, Moonshine was released minutes later. Somebody didn't want somebody else stealing their thunder I'm guessing. I'm just kidding...I'm sure both sides worked extremely hard on their respective methods and deserve mad props for the time spent on this and for waving a middle finger in the face of Verizon. Having said that I have tried both methods and have been unsuccessful so far at each one. I have to pose my questions here because I'm a new member and the development threads are off limits to me.
I tried the Revone Method first and like many were saying in the actual thread, my phone kept auto rebooting after the ./revone.dna -P step. I tried everything I could think of including all of the suggestions from the other users who finally got it to work by trying different things. Has anyone figured out what is causing the auto reboot? There has to be something specific causing this. One thing I have noticed with my phone is that USB Debugging has been very unreliable as of late. It turns itself off and on at random times and a lot of times the box is checked to enable it but it's not on. I don't know if this is playing a role in the process not working for me. I got the "success" message after every step several times but never actually achieved s-off.
I finally gave up on Revone to try Moonshine. I really didn't want to have to fo this route since I don't know a thing about Linux. I decided to go the boot from flash drive route so I downloaded 32 bit Ubuntu 13.04 iso and used universal USB installer to put it on my drive. I am using an external hard drive that is already formatted to fat32. I did NOT format the drive because I didn't think I had to since it was already fat32. Universal USB Installer was successful in putting Ubuntu on the external drive. I then went into my bios and changed the boot sequence to boot from the external drive first but when I rebooted it just loaded up Windows like normal. What am I doing wrong here? I'm running Windows 7 64bit but it was my understanding that this should not be a problem. Do I have to format and/or partition the external hard drive even though it is already fat32 before putting Ubuntu on it?
I'm dying to get one of these methods working but I'm currently stuck. Any newbies like me that can't post in the Development forums have any ideas as to what is going wrong here or would anyone else like to chime in with their own issues? Thanks in advance. I'm sure I'll get there eventually. :good:
Follow this guide for using an external USB device.
Modify the boot sequence like you were doing before, hopefully you'll get in to Ubuntu.
You say you don't have Linux experience, so I'll simplify the process for you:
Once at the desktop, press Control + Shift + T. This will open the Terminal, which is basically the Linux version of Windows' cmd.exe. Once inside, open up Mozilla Firefox (included) by using the side bar, the icon should be there. Download the version of Moonshine for the DNA, and then switch back to the terminal.
Type in these commands:
cd /home/Downloads
tar -zxf moonshine_dlx_2.06.605.1.tgz
sudo ./distiller
Click to expand...
Click to collapse
And then let Moonshine do its thing.
Modify the boot sequence like you were doing before said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
Oh and one other thing I forgot to mention regarding the revone method...the directory \data\local\temp did not exist on my device prior to me creating it when I pushed the revone.dna to my phone. Should I have had that directory on my phone already?
Sent from my HTC6435LVW using xda premium
I am in a similar boat. I am trying to use revone as I can't get ahold of linux. I downloaded the sdk and revone, moved adb to my C: with the revone file. Everything goes smoothly until i reach the -P step. Every single time it reboots after saying success. If I try to run the -s 0 -u command after that I get failed to map memory, success, revone failed = -1. If I try the -P command again, I get the same message with error code 2. If I try to reboot the bootloader, I get error device not found. I've been at this for hours, and Jerry from Android central even walked me through it, everything ended up successful ans when the bootloader rebooted, it was still locked and s on. Help please?
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Gorilla* said:
I dont even know what command to type into CMD for Revone. how do i push the file I have revone on my desktop downloaded and SDK installed..
Next step is?
Click to expand...
Click to collapse
I moved adb and its two counterparts in a folder named ADB_WIN, in my C: drive. From there, I typed cmd.exe in the search bar, it opened the command box. I typed in adb push revone.dna /data/local/tmp/ ENTER adb shell ENTER cd /data/local/tmp ENTER chmod 755 revone.dna ENTER ./revone.dna -P and that's where my error started coming in. You can try this, not sure if this right, but if its not, hopefully someone will correct me.
Krispenwah said:
Thank you for the response. I saw in the instructions it says to put the moonshine file in the ~Downloads directory. How do I do that? Also, I think I am going to try the disc method instead. Does it matter if its a cd or dvd? And I never did ask if the version of Ubuntu I had downloaded was compatible with this method. I downloaded Ubuntu 13.04 32bit for use on Windows 7 64bit. Will I have any problems? Thanks again!!
Click to expand...
Click to collapse
32 bit should work fine. You need a DVD because a CD is too small. ~/Downloads directory is just the current user's downloads folder. So most likely it would get downloaded to there anyway.
Sent from my DNA using Tapatalk 2
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
michaelrager said:
"1. Download revone (above) and push it to your device: adb push revone.dna /data/local/tmp/"
How is this done? I have no idea how to push to the DNA. Anybody help? Thanks
Click to expand...
Click to collapse
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
That's the command you use, adb push. Use it in a terminal. So..assuming windows use explorer to go yo where you downloaded the files and have revone.dna then hold shift and right click, choose open prompt here then type
adb push revone.dna /data/local/tmp
If it complains about command not found for adb add the adb.exe and its libraries to the same folder then try again.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
michaelrager said:
Thanks for the quick response. I don't have that option when i shift and right click, I only have "open with" Any Ideas?
Click to expand...
Click to collapse
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
pio_masaki said:
Hold shift while you right click, can't be on a file, just someplace in the explorer, no folders, etc clicked on, someplace blank.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
michaelrager said:
Got it. I misunderstood what you meant thanks! However, I am getting that error.
I got the error 'adb' is not recognized as an internal or external command, operable program or batch file. Can you elaborate on what to fix? Thanks Again!
Click to expand...
Click to collapse
add adb.exe to your command, instead of just adb
Gorilla* said:
add adb.exe to your command, instead of just adb
Click to expand...
Click to collapse
Thanks, but the same type of error came up.
michaelrager said:
Thanks, but the same type of error came up.
Click to expand...
Click to collapse
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Krispenwah said:
Put revone.dna in the same folder that has fastboot and adb then try
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
michaelrager said:
That worked I got daemon started successfully. Then it says error: device not found
I am in debugging mode.
Any help is much obliged. Thanks!
Click to expand...
Click to collapse
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Krispenwah said:
Try 'adb devices' and see if it recognizes your phone. Do you have usb debugging enabled? If so toggle it off and then back on while the phone is plugged in then wait about 10-15 seconds and try 'adb devices' again to see if its recognized now
Click to expand...
Click to collapse
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
michaelrager said:
Got it!
* daemon started successfully *
3372 KB/s (645920 bytes in 0.187s)
Is it all set so I can move on to the next step?
Click to expand...
Click to collapse
Yeah looks like the file pushed successfully. Now u do "adb shell" then "cd data/local/tmp" then "chmod 755 revone.dna" ....and so forth. Make sure ur adding the extension ".dna" to revone (revone.dna) each time u type it. If u just put revone it won't work ull just get an error