i have a htc touch diamond and i tried to put the xdandroid the new one and i downloaded all the files needed then i put the files in a folder that i created (andboot) and all the required files there and i alos copied the diam500 from (start up conf) to the (andboot) folder next when i went to the ((haret)) file to execute the proses and i clicked it and then i have a weird window the says:
launch a script file.default path is the same where the executable lives.
and there is this box that have (( default.txt )) run
and then
start waiting for connection on port 9999
when you connect,you'll get a remote hardware examination tool.
listen for network connection (in a box)
(another box)
found machine generic msm7xxxa
that all in that window
and when i press (((run))) a small error window pops the says : cannot open script file /internal storage/andboot/default.txt
please help me if you can because i really want the to see the xdandroind and thanks any way so sorry for any trouble.
I'm having exactly the same problem. It runs fine on the first run but once I reboot the phone and run it again it just keeps asking for default.txt. I tried specifying startup.txt but it won't work either (it's a zero-length file anyway). This is happening with both the current builds.
So i've got the SDK installed, and i THink i ahve ADB installed correctly (i can run commands and get results evn though i have no idea what to do with them)
But i dont know how to get a screen cap of wht is on my Tablet...is there an app i should be using?or is this not somethingi need to do via ADB?
Darkeyce said:
So i've got the SDK installed, and i THink i ahve ADB installed correctly (i can run commands and get results evn though i have no idea what to do with them)
But i dont know how to get a screen cap of wht is on my Tablet...is there an app i should be using?or is this not somethingi need to do via ADB?
Click to expand...
Click to collapse
You use DDMS to take screenshots. Take a look in your tools folder in the SDK. There should be a file there named ddms.bat... If not it may be in platform-tools. I usually just copy everything in platform-tools to the tools folder anyway.
To take a screenshot make sure you can talk to your tablet. So do a ADB devices from a command line pointed at your tools folder. It should come back and tell you it found your tablet. Then just run ddms.bat and it will open up a window. You need to select your tablet from the list. It will normally be the top line if you only have one device connected. Then from the menu up top select Device, and then screen capture.
Sprdtyf350 said:
You use DDMS to take screenshots. Take a look in your tools folder in the SDK. There should be a file there named ddms.bat... If not it may be in platform-tools. I usually just copy everything in platform-tools to the tools folder anyway.
To take a screenshot make sure you can talk to your tablet. So do a ADB devices from a command line pointed at your tools folder. It should come back and tell you it found your tablet. Then just run ddms.bat and it will open up a window. You need to select your tablet from the list. It will normally be the top line if you only have one device connected. Then from the menu up top select Device, and then screen capture.
Click to expand...
Click to collapse
Oh, That's just SWEET!
Thanks for the assist
It looks like we may have some users that are new to rooting or to Android all together.
I posted these instructions in the perm root thread, but I figured putting them in their own thread would make it easier to find.
This is meant as a basic pre-cursor to following BCNice's perm root instructions.
I've added a link to TrueBlue_Drew's adb/fastboot guide here
If you use the method that I outline below just download his zip and extract the files to your desktop. Then move the fastboot file into your AndroidSDK\platform-tools sub directory. Thanks to Drew for putting together a great guide!
You will need fastboot installed to install BCNice20's recovery.img.
Make sure you have HTC Sync installed on your computer HTCSync
First download the SDK here
Make sure to dowload the installer_r09-windows.exe
Now install the SDK when prompted for the install path paste C:\AndroidSDK over the default path
Once you have installed it open it from the start menu
Select install packages
The main one we are concerned with is "Platform Tools"
Go to the start menu and right click on My Computer in XP Computer in Windows 7.
Select properties, then select advanced/advanced system settings in Windows 7, then environment variables, now go to the lower box (system variables) and select path then edit.
Paste the following as your path C:\AndroidSDK\platform-tools then select o.k.
Make sure you have temp root via Visionary or Z4.
On your phone go to Settings, Applications, Development, and make sure USB Debugging is checked.
Now connect your phone to your computer and leave the connection type as "charge only"
On your computer select Start, then run, type in CMD
Once in the Command Prompt enter
Code:
cd C:\AndroidSDK\platform-tools
The next line should pop up C:\AndroidSDK\platform-tools>
Now test adb by typing in
Code:
adb
If adb runs you are ready to start!
Type
Code:
adb shell
Then type
Code:
su
Allow Superuser on your phone
You are now in and ready to follow BCNice's directions
Here's some adb stuff that I found from the evo days that has linux, mac, and windows adb and some of the files it needs. I flashed the evo with it so it should work for the shift too. I used an all in one for the epic to root mine in windows. I just extracted the zip and ran adb inside it. I could have included that or instead but there were a lot more files in there pertaining to recovery, root exploits, and images of things I didn't know if they could safely be removed and still work or not. I used the mac version of the file in this package instead of running back and forth from win to mac. I purposely keep the win partition off the internet. Yeah, vmware works but sometimes it doesn't and I didn't want to risk anything when flashing a phone.
As usual, use at your own risk. It worked for me in the past so I don't see any reason why it won't work now. Make note of the adb program naming schemes because they aren't just "adb". I uploaded this because it was very useful to me in the past and I've always failed or got lost when trying to set up sdk per google's instructions. It's very stripped down so don't expect it to be as fully functional as the sdk would be.
If you want to do it the way I did then head over to the epic section and get the all in one root and recovery in the dev section, unzip it, then use the adb.exe inside. Don't use any bat files or scripts in there, you might brick the phone.
As a Win7 64bit user, I had the additional steps of downloading and installing HTC Sync so that Win7 would install the proper drivers for my phone before I could use adb shell to access my shift.
JigSawMan said:
As a Win7 64bit user, I had the additional steps of downloading and installing HTC Sync so that Win7 would install the proper drivers for my phone before I could use adb shell to access my shift.
Click to expand...
Click to collapse
Yes, of course, how could I forget that? You definitely need drivers for windows.
Anybody care to link me to a good guide for Linux mint/Ubuntu 64 bit?
I've done it on 32, but I can't find good resources for 64.
I used adbwireless and it worked first shot!
Time to work on some roms...;-)
Sent from my PG06100 using XDA App
So is there like a video review or a picture review of this. I am trying to do the steps, but the process is different from your steps. I have tried this on xp and windows 7
When I get to this step
"On your computer select Start, then run, type in CMD
Once in the Command Prompt enter cd C:\AndroidSDK\platform-tools
The next line should pop up C:\AndroidSDK\platform-tools>
Now test adb by typing in adb"
It tells me "The system cannot find the path specified"
Can anyone help me.
all of my drivers are installed for my phone.
koolkid09 said:
When I get to this step
"On your computer select Start, then run, type in CMD
Once in the Command Prompt enter cd C:\AndroidSDK\platform-tools
The next line should pop up C:\AndroidSDK\platform-tools>
Now test adb by typing in adb"
It tells me "The system cannot find the path specified"
Can anyone help me.
all of my drivers are installed for my phone.
Click to expand...
Click to collapse
You need to locate the SDK and rename it. It should be on your C drive in the program files folder and the android sub folder.
Once you have located the folder I believe is named android-sdk-windows right click on it and rename it to AndroidSDK.
Then open up a new window in My Computer on Windows XP or Computer on Windows 7.
Open the C drive and then drag the renamed AndroidSDK file over to the root of the C drive.(not in any folder)
BrandoKC said:
You need to locate the SDK and rename it. It should be on your C drive in the program files folder and the android sub folder.
Once you have located the folder I believe is named android-sdk-windows right click on it and rename it to AndroidSDK.
Then open up a new window in My Computer on Windows XP or Computer on Windows 7.
Open the C drive and then drag the renamed AndroidSDK file over to the root of the C drive.(not in any folder)
Click to expand...
Click to collapse
Ok. I deleted everything and I am going to try over.
OK.. When I'm first trying to install it do I install it to C:\Program Files (x86)\Android\android-sdk-windows. That is the defualt place it wants me to install it to. (I am on Windows 7)
I've updated the original post with some more specific instructions for Windows 7.
I had to reboot my computer before I could move the SDK to the C drive and rename it.
The first time I entered the command prompt adb wouldn't work, but I closed it out and the second time it worked flawlessly.
Ok thanks BrandoKc. Coming from windows mobile it would of tooken me a while to figure this adb stuff I out. I have a question??? I just finished rooting... if I hard reset does this break the root???
Sent from my PG06100 using XDA App
koolkid09 said:
OK.. When I'm first trying to install it do I install it to C:\Program Files (x86)\Android\android-sdk-windows. That is the defualt place it wants me to install it to. (I am on Windows 7)
Click to expand...
Click to collapse
That will work! Once installed there and updated rename it to AndroidSDK and move it to the root of the C drive. You may need to reboot your computer before it allows you to edit the folder.
alanherrera59 said:
Ok thanks BrandoKc. Coming from windows mobile it would of tooken me a while to figure this adb stuff I out. I have a question??? I just finished rooting... if I hard reset does this break the root???
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
By hard reset I assume you mean factory reset. It may but you can re root if it does.
I'm glad to have helped. I know when I rooted my Hero I nearly shatted a bricked Hero.
UGH! Now my SDK manager is not working. It pops up then goes away and I can keep it up. This is happening on this step "Once you have installed it open it from the start menu". I'm probably going to wait until the morning or somebody makes a video on how to do this because I'm getting frustrated.
Koolkid come to the IRC so we can help you
BrandoKC said:
Koolkid come to the IRC so we can help you
Click to expand...
Click to collapse
I sent you a PM.
BrandoKC said:
By hard reset I assume you mean factory reset. It may but you can re root if it does.
I'm glad to have helped. I know when I rooted my Hero I nearly shatted a bricked Hero.
Click to expand...
Click to collapse
Lol. As from my language... You can tell I come from windows mobile, in those forums we refered a factory reset as a hard reset and a soft reset as a battery pull
Sent from my PG06100 using XDA App
alanherrera59 said:
Lol. As from my language... You can tell I come from windows mobile, in those forums we refered a factory reset as a hard reset and a soft reset as a battery pull
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
Once we have a recovery you will definitely be able to wipe/hard reset/factory reset without losing root.
I would imagine at this point you should be able to without losing root also.
Left WinMo when the G1 came out and haven't looked back. Enjoy Android!
I downloaded the Android SDK on the website and the drivers from MotoDev and placed them on my desktop. I ran the drivers and they installed fine. I unzipped the SDK, created a new folder in my C: drive called AndroidSDK and placed the unzipped folder in that folder.
I opened Command Prompt and entered:
cd C:\AndroidSDK\android-sdk-windows\tools
then entered:
fastboot oem unlock
and got this error:
This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this issue.
I then went into the SDK and read the readme where it says that adb was moved. It says it was moved to platforms. When I open the folder there is nothing in there.
try the path that ends with "platform-tools" instead
Sent from my Xoom using XDA Premium App
Ok I figured it out. I clicked on something and it brought up a repo. I download the missing platform-tools.
I ran the commands again and I'm still getting the errors. Should I copy everything from platform-tools into the tools directory?
gqstatus0685 said:
I tried that also. I forgot to add that in my first post. There is nothing inside that folder. Am I missing adb? Is there a way to download it and drop it into that folder? I'm lost on this.
Thanks.
Click to expand...
Click to collapse
Did you open the SDK Manager and make sure all your packages are updated?
gnackattack said:
Did you open the SDK Manager and make sure all your packages are updated?
Click to expand...
Click to collapse
I did do that but cancelled after it installed the platform-tools. Should I let it download everything? It looked like it was going to take a long ass time.
**** I ended up downloading all the updates for 3.1 and entered the commands again. This time it was able to cd into the platform-tools but I can't enter the command fastboot oem unlock because I get error:
"fastboot" is not recognized as an internal or external command, operable program or batch file
Just my luck...
fastboot is in the "tools" folder, not the "platform-tools" folder.
gnackattack said:
fastboot is in the "tools" folder, not the "platform-tools" folder.
Click to expand...
Click to collapse
Ok I changed CD but now it's telling me it can't find a file that's located in platform-tools. Should I copy all the files from platform-tools and move them into the tools folder?
*********************************************************
Ok. I moved the file and it worked. My Xoom is unlocking. I have the worst luck when I borrow someone else's laptop.
Copy any files it tells you it can't find. I haven't encountered that issue myself, but that's the solution I've seen others recommend.
I'd like to thank Gnac and the other people who helped me achieve root with the issues I was having.
Anyway I have an SD card in my Xoom and I don't think it's working like it should. I downloaded a file manager, loaded a .zip on there of a theme I want to install but when I boot into recovery it's not there.
I've verified it's in the SDcard with the file manager and it's in .zip format. I'd prefer to flash it instead of adb'ing it because I keep all my .zip organized in folders on my SD card. Before inserting the SD card in the Xoom I did wipe it.
I'm rooted 3.1 and I have Busybox installed. I'm running:
[email protected] #2
Any ideas how I can get the files to be seen in recovery?
I've been trying to fix this for the last 48 hours, and it is driving me insane. There are a few other threads on xda about this, but they didn't fix my problem.
My SDK Manager.exe flashes a cmd screen and closes in less than a second.
After much searching, I finally managed to get my SDK Manager to open after adjusting android.bat, and running android.bat as administrator.
But, SDK Manager.exe was not able to find android.bat so I copied it into the android-sdk folder.
SDK Manager.exe is now able to find android.bat, but it is still briefly flashing cmd and then closing.
My PATH variable has my jdk java.exe directory as the first entry, and I have restarted and reinstalled several times.
What is causing this? Why am I able to open the manager from android.bat, but not from the executable?
I am trying to configure Eclipse to use the SDK Manager, but obviously I cannot because the executable refuses to open.
Eclipse is also telling me that adb.exe is missing, and upon checking platforms I have confirmed this. I assume adb.exe will be installed from the SDK Manager?
Thanks in advance for the help.
Edit: After thinking about it, I think the issue may be with the permissions of android.bat. It must be run as administrator in order to work, otherwise if opened regularly it will say "Access is denied".
Is it possible to change this? Looking in the properties of android.bat, I have adjusted my account to have full control. This has not affected the issue, though.