Guest _melchett Posted February 23, 2011 Report Posted February 23, 2011 I know there is a sticky but i didn't want to sully that post with something as purile as this request. Anyway i have no working touchscreen at all - not a software fault but rather a broken screen. I also now get force closes when i try to make a phonecall, enter the market or Gmail and try to play music- this is a new fault that i want to investigate as i still use the phone as musiv player. I can only rely on nandroid backups because when flashing a new rom it asks you to 'touch the google-guy' (not verbatim what is said) which i can't do. Therefore i cannot type adb logcat in the terminal emulator. This means the only option to use the SDK. So far i've: 1) Downloaded the Java developer kit that the SDK required 2) Downloaded the Android SDK and the first two options. a) Android SDK Tools, reversion 10 :huh: Android SDK Platform-tools, revision 3 I can find adb when going through C:\Windows etc. WHen i try opening in that it opens, flashes text and closes. When i open command prompt and type in adb logcat it says waiting for device - but displays nothing. So i'm sure there is something very basic but i can't find instructions anywhere (the sticky ones aren't particularly extensive!)
Guest AntonioPT Posted February 23, 2011 Report Posted February 23, 2011 I know there is a sticky but i didn't want to sully that post with something as purile as this request. Anyway i have no working touchscreen at all - not a software fault but rather a broken screen. I also now get force closes when i try to make a phonecall, enter the market or Gmail and try to play music- this is a new fault that i want to investigate as i still use the phone as musiv player. I can only rely on nandroid backups because when flashing a new rom it asks you to 'touch the google-guy' (not verbatim what is said) which i can't do. Therefore i cannot type adb logcat in the terminal emulator. This means the only option to use the SDK. So far i've: 1) Downloaded the Java developer kit that the SDK required 2) Downloaded the Android SDK and the first two options. a) Android SDK Tools, reversion 10 :) Android SDK Platform-tools, revision 3 I can find adb when going through C:\Windows etc. WHen i try opening in that it opens, flashes text and closes. When i open command prompt and type in adb logcat it says waiting for device - but displays nothing. So i'm sure there is something very basic but i can't find instructions anywhere (the sticky ones aren't particularly extensive!) I also can't get the Android SDK working on Windows. Fortunately for me, Linux (Ubuntu) is my main system and I don't have any type of problems here :huh: I recommend you to install Ubuntu on your computer to do your android developing/hacking. Just download the android sdk from google, install platform-tools and run adb. BTW, can't you "touch the google guy" with the trackball?
Guest Boony123 Posted February 24, 2011 Report Posted February 24, 2011 u dont need the sdk to use adb, just download a recovery img zip that has fastboot and adb inside and use that or if you really want to use the sdk then try download a linix vmbox see if that helps.
Guest _melchett Posted March 28, 2011 Report Posted March 28, 2011 Finally got round to getting this working. I'm not entirely sure how to get a full logcat, so this is just the initial part (still has a nice few errors). http://pastebin.com/kPNpJwmY Any advice would be greatly apprechiated...i miss my pulse!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now