[TUTORIAL] How install ADB and Use Logcat! - HTC Desire X

TUTORIAL ON ADB AND LOGCAT : JDMC : Just doing my contribution.
This is part of TeamAscend, so if you are going to post this Tutorial on other forums please credit me, visit our website : I AM AWESOME!
Hello this is just to teach newbie users on how to install adb and get it working, I will also teach you how to use logcat to help devs with particular issues, okay lets get into it, I will try to be as formal and understandable is I can, I'm still a 15 year old so bare with my written language, not that its bad but we Kiwi's use weird slangs...
Setting up ADB
1. Okay first of all we need to enable Android debugging.
1a. To do so, head into Settings > development and check android debugging, If you're on CM10 + you will need to set Developer Options to "ON" then select Android Debugging.
2. Get a usb adapter and connect it to your pc and connect your device. Let it install drivers "If it's the first time.
​3. Download "SDK Tools". and install it to your desktop for now, you can move it later when you want.
4. Now create a new folder on the desktop and copy all SDK contents into it so its neat and tidy.
5. Open "SDK Manager" and un-check everything except "Android SDK Platform-Tools" and click install packages, wait till it's done then close the window, now you should be in the folder that contains the SDK Tools etc... if you see the "platform-tools" folder you're good to go.
6. Now open the "platform-tools" folder and copy the destination output at the top.
7. Now we need to set the new destination to CMD, click the start button type "cmd".
8. When it opens type "cd" obviously without the ", now hit space and click paste now your command should look something like this...
"cd C:\Users\Your PC name\Desktop\the folder that contains the sdk tools name\platform-tools" here's mine : "cd C:\Users\Lenovo\Desktop\ADB\platform-tools". Now hit enter, your target folder will change.
9. Once its done type " adb devices", make sure your phone is connected! now hit enter and it'll show your device, now you know ADB Is up and running! If doesn't show your device continue to the next step, if it does continue from step "11".
10. Download the HTC drivers and install it, plug your phone again and wait for it to install all components, if MTP fails to install just ignore it. (If your storage is on MTP), now repeat the procedure from "7" again.
11. Now lets Logcat, Now there are 2 different approaches to the logcat, I will be showing you how to do both in this tutorial. Neither one is more correct than the other, it is 100% personal preference. Feel free to try both and see where you get.
LOGCAT PROCEDURE
Doing logcat from inside the CMD window.
1. Make sure your phone is plugged in and debugging is on, now repeat procedure "7" to set target folder if it isn't already done. ie : cd _____________________________ <-- your folder destination.
2. Type "adb logcat" without the " and hit enter. It will then print a list of random writing, whether you understand or not, it doesn't matter, it's not for your use .
3. To save the logcat for devs to use, once the logcat is running, please RECREATE the bug/issue you are having. so that it logs the error into it, now to stop the logcat hit "ctrl" + "C".
4. Once this is done please RIGHT CLICK choose "Select All" then press "Enter" on your keyboard this will copy the entire log to the clipboard. You can then paste it into a .txt file to upload and show to devs.
Doing logcat to text file.
1. Now repeat procedure "7" to set target folder if it isn't already done, make sure your phone is plugged in and usb debugging mode is enabled. Once this is done we are going to type the following command "adb logcat > logcat.txt" without the ", this should initiate the logcat, it will appear as though nothing is happening, this is correct!!! So don't worry.
2. Once the logcat is running, please RECREATE the bug/issue you are having. To stop the logcat on your keyboard press "ctrl" + "C".
3. Now you've done logging, note the logcat.txt file will be located in the platform-tools folder, just open it and you will see logcat.txt, upload it for the dev and he/she will investigate.
More ADB Commands for various logcats Thanks to "Tcpaulh" from Modaco.
External adb folder, just needed thanks man : Download
1. radio logcat for Wifi issues.
adb logcat -b radio > radiolog.txt
2. kernel logs.
adb shell
su
cat /proc/kmsg > /sdcard/kmsg.txt
exit
adb pull /sdcard/kmsg.txt
3. kernel message buffer (on request).
adb shell
dmesg > /sdcard/dmesg.txt
exit
adb pull /sdcard/dmesg.txt
This was a tutorial I wrote up for my old device, users found it easier to understand then most, I cleaned this one up a bit which should be suitable for the Desire X, note, I may ask allot of question like a noob on the Q & A but HTC is so confusing.
Hopefully, users start using this so we can help out our devs, our sweet sweet devs, so they can whip u some magic.
If this helped, hit the thanks meter, no need for donations.

Related

windows 7 root NC

this from rad131304 not me, thank you
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (www dot cygwin dot com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
1. make sure your NC is disconnected from you computer
2. make sure your SD card is mounted on your computer (readable/browsable in explorer)
3. Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
4. download nooter at http //www dot mediafire dot com/?hugt8uxcfffpdvg
5. extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
6. Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
7. Select "Disk Management" under storage
8. note the drive letter of the SD card and the disk number
9. Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
10. At the prompt, type (WOQ): "mount //./<f>: /dev/sd<c>"
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
11. press enter - there should be no output
12. at the prompt, type (WOQ): "dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>"
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
13. remove the sd card from the computer and plug it into the NC
14. power down the NC (hold power button for 15 seconds)
15. connect the NC to the computer
16. Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
17. Wait for 15 seconds after the recognition
18. power down the NC
19. remove SD card ***
20. Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
21. Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
22. save the file and close
23. find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
24. add (WOQ) "0x2080" on its own line
25. power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
26. Go To: Start > Devices and Printers
27. Right-click on Nook and select properties
28. Select the hardware tab
29. If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 38
30. Click on "Nook"
31. Select Properties
32. Click Change Settings (may require UAC elevation)
33. Click update driver
34. Select "browse for driver software on your computer"
35. Browse to the android-sdk/usb_driver folder
36. click next
37. You should be done; skip to 47 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
38. If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
39. Select Properties
40. Click Change Settings (may require UAC elevation)
41. Select the Driver Tab
42. Click Uninstall
43. Click OK
44. Disconnect NC
45. Reconnect NC
46. You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
47. Go To: start > run > cmd
48. type (WOQ): "cd <path_to_android_sdk>\tools"
49. type (WOQ): "adb.exe kill-server"
You should get something like:
* server not running *
50. type (WOQ): "adb.exe remount"
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
51. You are done configuring to sideload
From here you should be able to sideload from ADB.
by rad131304
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
I believe it was mentioned in a previous post that if you did a factory reset (power off completely, then hold power, nook button and vol up) that it would reset the Nook back to non rooted factory defaults. Can anyone else confirm this?
HeroHTC said:
Just to throw it out there...
Does this cause a PERMANENT change to the Color Nook?
Edit: thank you for posting this
Click to expand...
Click to collapse
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
believe this was done on win 64, some buttons are located in or below menu bar, some will depend on launcher.
I also wanted to mention this
http://forum.xda-developers.com/showpost.php?p=9517050&postcount=863
NOTE: I have not even opened my nook box yet, its still sealed but I am getting ready. Just waiting on an email solution.
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
RichTJ99 said:
Are these instructions for Win 7 64 or 32 bit?
BTW, how does one go back or to menu without those buttons?
Click to expand...
Click to collapse
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
The back and menu buttons are soft-buttons. The nook for some reason hides them by default in a bunch of apps.
sudermatt said:
Do you think a partitioned SD card woul dprevent this from working?
I'm pretty sure my card is partitioned....I read something in the BIG THREAD about departitioning a card.....
I can't get this to work for me and I just thought my card might be the culprit.
Thanks
Click to expand...
Click to collapse
IIRC, somebody said that in the big thread, too.
oakleyrdc said:
I cannot find the file listed in step 23. This is the only thing keeping me from root. Also when I plug my nc in, the light on the cord is amber instead of green. It tells me that adb drivers are installed. But it won't show up as a folder in my computer any more. How do I add files without removing the SD card and plugging it into my computer.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
It could be hidden (so you'll have to change the hidden files and folders setting), or installed in another user directory (like Admin).
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
I did mine on Win 64bit using winimage. Everything is working fine.
rad131304 said:
I did this on 32 bit - AFAIK, they don't support cygwin on 64 bit yet (it might run though, but YMMV).
Click to expand...
Click to collapse
XP
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
plus 1 for XP
So once your rooted, do you need to do anything special to install apk files that you download from dropbox? Is superuser ready?
i cant find the android_winusb file in the windows XP version of the android SDK. is there a different one that does the same?
EDIT: it appears the sdk is not split between versions of windows
im going to reinstall the sdk and see maybe if i accidently deleted it at some point
cabbieBot said:
If I run Windows XP, how many of these steps would change? I'm thinking it might need its own thread.
Click to expand...
Click to collapse
Very little changes; the only thing I can tell you off the top of my head is that
C:\users\<username>\.android\
Becomes
C:\documents and settings\<username>\.android\
Also, I don't know where, besides device manager, that you could locate the nook like you do in devices and printers - it may show up in my computer, also in scanners and cameras in the control panel - you can always right click a drive, select properties, select the hardware tab, select the b&n storage device, click properties, select the driver tab and uninstall from there....
HTH
EDIT: To delete the NC through device manager:
start > run > compmgmt.msc
browse to Device Manager
Expand Universal Serial Bus Controllers
Select USB Mass Storage Device (there may be multiple)
Right-Click and select "properties"
select the details tab
in the dropdown, select "Hardware Ids" - if this says "USB\VID_2080&...." then this is the NC
click ok
right Click again and select uninstall
disconnect NC from computer
reconnect NC to computer
NC re-finds all drivers, including ADB
start > run > cmd
cd <android-sdk-dir>\tools
adb.exe remount
Fixed instructions!
that's what I get for writing this crap at 1 in the AM ... I left out two INSANELY important steps at step 11.
SORRY!!!!
Windows 7 Sideload Instructions
Hope this helps some people - I tried to be very step-by-step about it.
Again, thank you Pokey9000, the guys and gals from the IRC channel, and everybody else for all of your hard work! 99.9% of this is an aggregation of what is already in this thread; some of it comes from nookdevs also.
You will need the following applications on your Windows 7 computer:
- cygwin (http://www.cygwin.com)
- Android Debug Bridge (ADB) - this comes with the android SDK
- Android USB Drivers - this comes with the android SDK
-- (WOQ) stands for without quotes, it means that I am giving you something between quotes to copy and paste.
-- if you see <some_odd_name> inside quotes or a code block, it means you MUST replace this with something from your specific OS instance (e.g. a drive letter, or something)
make sure your NC is disconnected from you computer
make sure your SD card is mounted on your computer (readable/browsable in explorer)
Install cygwin - you only need the base install AFAICT (YMMV), don't worry about the options for now.
download nooter at http://www.mediafire.com/?hugt8uxcfffpdvg
extract the contents to a folder in your cygwin install (standard install path is c:\cygwin)
Go to: Start, type in (WOQ) "compmgmt.msc" - this may require UAC elevation
Select "Disk Management" under storage
note the drive letter of the SD card and the disk number
Go To: Start > All Programs > Cygwin > Cygwin Bash Shell
At the prompt, type:
Code:
mount //./<f>: /dev/sd<c>
Where <f> is your drive letter, and
<c> is the letter you would get if you zero-indexed the disk number into the alphabet (i.e. 0 = a, 1 = b) **
press enter - there should be no output
REMOVE SD CARD FROM PC
INSERT SD CARD INTO PC
at the prompt, type:
Code:
dd if=<path_to_nooter_from_cygwin_install_folder>/nooter_sdcard_40MB.img of=/dev/sd<c>
It will sit at this for a few minutes seeming to do nothing, be patient; you should get a response eventually that looks like:
80326+0 records in
80326+0 records out
41126912 bytes (41 MB) copied, 174.525 s, 236 kB/s
Click to expand...
Click to collapse
IF THIS COMPLETES ALMOST IMMEDIATELY, YOU PROBABLY HAVE AN ERROR
remove the sd card from the computer and plug it into the NC
power down the NC (hold power button for 15 seconds)
connect the NC to the computer
Wait for a "Composite Device" to be recognized by Windows and fail to install drivers
Wait for 15 seconds after the recognition
power down the NC
remove SD card ***
Find your android_winusb.inf file - this is located in your android-sdk install directory in the usb_driver folder. (NOTE: if you installed this in the program files folder, you will need to UAC elevate your editor to edit this file)
Paste the following lines into the file below both occurrences of the line ";Moto Sholes" after the ADBInterface definitions:
Code:
;B & N Nook Color
%SingleAdbInterface% = USB_Install, USB\VID_2080&PID_0002
%CompositeAdbInterface% = USB_Install, USB\VID_2080&PID_0002&MI_01
save the file and close
find your adb_usb.ini file - it is usually located in c:\users\<username>\.android\
add (WOQ) "0x2080" on its own line
power on NC - at this point, the NC should boot normally, but ADB won't be able to recognize it
Go To: Start > Devices and Printers
Right-click on Nook and select properties
Select the hardware tab
If you have something that says "Nook" and has a yellow yield sign with a "!", then continue, if not skip to 40
Click on "Nook"
Select Properties
Click Change Settings (may require UAC elevation)
Click update driver
Select "browse for driver software on your computer"
Browse to the android-sdk/usb_driver folder
click next
You should be done; skip to 49 (I have no idea if this is correct - i pieced it together from somewhere in this as I did not get Nook to appear in the Device Functions List)
If you don't have a "Nook" Device Function, click on "USB Mass Storage Device"
Select Properties
Click Change Settings (may require UAC elevation)
Select the Driver Tab
Click Uninstall
Click OK
Disconnect NC
Reconnect NC
You should be done (this is different from my previous instructions on how to uninstall the NC USB drivers, I have not tested it so YMMV)
Go To: start > run > cmd
type:
Code:
cd <path_to_android_sdk>\tools
./adb.exe kill-server
You should get something like:
* server not running *
Click to expand...
Click to collapse
if adb.exe is not in tools (or tools does not exist), try:
Code:
cd <path_to_android_sdk>\platform-tools
./adb.exe kill-server
type:
Code:
./adb.exe remount
You should get something like:
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
Click to expand...
Click to collapse
You are done configuring to sideload
From here you should be able to sideload from ADB.
To sideload an app, simply do the following:
Code:
./adb.exe install <app_name>
Thanks Rad!
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
When you updated the SDK, did you install the USB drivers also? If you did, that file should be in whatever directory you installed the SDK in under the usb_driver subdirectory.
cabbieBot said:
im going insane, ive completely updated the SDK but i cant find this damn android_winusb file
Click to expand...
Click to collapse
I'm an idiot, I was certain the USB Drivers were installed. Done and done now, sheesh what a waste of time!
now to hunt for adb_usb which is being a pain to find too. Has anyone found adb_usb on XP?
I can see the folder C:\documents and settings\<username>\.android\ but theres two folders in there for AVD and AndroidDesktopNotifier. Maybe if someone can upload the adb_usb file I can just throw it in the folder and cross my fingers?

[TUTORIAL] Run Ubuntu 10.10 on Nexus One

Run Ubuntu 10.10 on Nexus One
--------------------------------
Background:
In June 2010, XDA zedomax got Ubuntu 9.04 running on Nexus One, tutorial is available at this thread:
http://forum.xda-developers.com/showthread.php?t=718952
I continued studying the tutorial and worked out a way to make Ubuntu 9.04 running better, smoother and cause less error, here's my post:
http://forum.xda-developers.com/showthread.php?t=815532
Recently HTC_Linux team has released version 0.3 of their Ubuntu image, compare to the original guide provided by zedomax, the v0.3 release is based on the latest Ubuntu 10.10. So I thought about making this tutorial to guide you to run Ubuntu 10.10 on your Nexus One.
--------------------------------
What benefits will you get from running Ubuntu 10.10 on Nexus One (at least):
1. Fully functional Linux terminal, with all standard Linux command line utilities
2. Fully functional desktop browser Firefox 3.6.13
3. Ability to compile and run native Linux applications
4. Bunch of graphical Internet and utility applications as shown in the screenshots
--------------------------------
Credit:
Thanks to the great XDA-developers community.
Thanks to Zedomax for providing the original tutorial of running Ubuntu on Nexus One.
Thanks to HTC_Linux team for creating the optimised Ubuntu 10.10 image file.
--------------------------------
Now the tutorial starts.
Preparation:
1. A micro SD card at least 4GB in capacity, 8GB/16GB is recommended
2. (Optional) If you're using Froyo App2SD, move all your applications which are on SD card back to Internal Storage, or you may also uninstall all applications that are on SD card. If you fail to do so, you won't be able to enter Ubuntu. However I've discovered a way that you won't need to move or uninstall apps on SD card, will discuss later.
3. Basic Linux shell knowledge
Then:
1. Get Ubuntu 10.10 from this post (file name: hd2-ubuntu_0.3.zip): http://forum.xda-developers.com/showthread.php?t=889433
2. Download attached scripts.zip
3. On your computer, make a directory on a partition that has more than 3.5GB available space, name the directory “ubuntu” (case-sensitive!)
4. Extract three scripts (b, e, u) from scripts.zip to the directory ubuntu
5. Once you finish download hd2-ubuntu_0.3.zip, extract linux/rootfs.ext2 to the directory ubuntu
6. In your ubuntu directory, rename rootfs.ext2 into ubuntu.img (case-sensitive!)
7. Now verify that you have the following files in your computer's ubuntu directory: b, e, u, ubuntu.img
8. Copy the whole ubuntu directory onto your SD card, put the SD card back to your phone
9. Power up your Nexus One
Now we have some script work:
1. Run a terminal application from your phone (e.g. Android Terminal, Better Terminal Emulator)
2. type “cd /sdcard/ubuntu” (enter)
3. type “sh u” (enter)
4. If you see “Type 'b' to boot Ubuntu”, then you're almost there!
5. Type “b” (enter)
6. If you see “[email protected]:/#” (like shown in screenshot) Congratulations! Now you're running Ubuntu 10.10 on your Nexus One!
Whenever you want to enter Ubuntu again, simply type “b” (enter) in your Android Terminal.
To properly exit from Ubuntu, you must type “exit” from Ubuntu terminal.
If your Android terminal application gets killed by Android system (i.e. you lost Ubuntu terminal), you need to go back to Android terminal, type “e” (enter), that will properly unmount Ubuntu.
Very often that you can get “loop device busy” error when exiting from Ubuntu, in that case, type “e” (enter) multiple times (it's harmless to run “e” script multiple times, don't worry). If still you get “loop device busy” error, don't worry, ignore it then.
--------------------------------
(Optional) If you would prefer working with GUI, now let's do some extra script work:
1. Install “android-vnc-viewer” from Market (freeware)
2. Enter Ubuntu terminal
3. Make sure that you have network connection (Wi-fi recommended)
4. type “apt-get update” (enter), and wait till it finishes
5. type “apt-get install tightvncserver” (enter) and answer “y” to the question
6. After installed tightvncserver, type “cd /bin” (enter)
7. Type the following commands (all are case-sensitive!):
“cat > x” (enter)
“rm -r -f /tmp” (enter)
“mkdir /tmp” (enter)
“chmod 777 /tmp” (enter)
“export USER=root” (enter)
“export XKL_XMODMAP_DISABLE=1” (enter)
“vncserver -geometry 1024x800” (enter)
(enter)
(press and hold trackball and click D on keyboard)
“chmod 777 x” (enter)
8. The above procedure makes a script named “x”, whenever you want to start GUI, you need to type “x” (enter).
Notice that the first time (only the first time) you run “x” script you'll be prompt to enter a password for VNC connection, then you'll be asked whether to create a “view-only” password, since it is not necessary, answer “n” to the question.
9. Start “android-vnc-viewer”, create a new connection with the following settings:
Nickname: (anything you like to identify the connection)
Password: the VNC connection password that you created when ran the “x”script
Address: localhost
Port: 5901
Color format: 24-bit color (4 bpp)
Click “Connect” button, and in about a minute, you'll see your Ubuntu 10.10 desktop!
10. We still need to create one final script called “s”, now go back to your Ubuntu terminal and type:
“cd /bin” (enter)
“cat > s” (enter)
“export USER=root” (enter)
“vncserver -kill :1” (enter)
“vncserver -kill :2” (enter)
“sudo reboot” (enter)
“sudo halt” (enter)
(enter)
(press and hold trackball and click “D” on keyboard)
“chmod 777 s” (enter)
11. If you have GUI running, you * MUST * type “s” (enter) to stop VNC server before you exit from Ubuntu terminal!
In case that your Android kills your Android Terminal application and you still have VNC server running, do the following steps:
a. Start Android Terminal
b. type “b” (enter) to bring back Ubuntu terminal
c. type “s” (enter) to stop VNC server
d. type “exit” (enter) to exit from Ubuntu terminal
Fail to do so you will have problem with VNC connection next time you use it.
--------------------------------
What are not working in Ubuntu:
1. Sound
2. Some applications may not run (I guess, due to Android memory management mechanism)
--------------------------------
A little trick to access SD card from your Ubuntu:
1. Install “SwiFTP” from Market (freeware)
2. Set up FTP server using SwiFTP
3. In Ubuntu, “Places → Connect to Server” then:
Service type: FTP (with login)
Server: localhost
Port: (port number specified in SwiFTP, default is 2121)
Folder: /
User Name: (user name specified in SwiFTP)
Then press “Connect” and enter your password specified in SwiFTP. Now feel free to access your phone's file system!
--------------------------------
How to bring up Ubuntu if you have applications installed on SD card using Froyo App2SD:
1. Make sure that your Android Terminal application is installed in Internal Storage
2. Put a shortcut to Android Terminal application on your home screen
3. Make sure you have got ubuntu directory and all its contents on SD card
4. Reboot your phone (stay sharp, these following steps require perfect timing!)
5. Once you enter lock screen, Immediately unlock it.
6. Enter Android Terminal and type “b” as quick as possible, do not press Enter yet!
7. Pay close attention to your notification bar, as soon as the “SD: Checking for errors” notification disappears (the little SD icon disappears), Immediately press Enter.
8. Now you should be in Ubuntu terminal, wait 1-2 minutes before you do anything else.
9. After 1-2 minutes, you may do whatever you want.
With some applications installed on SD card, you must do the procedure above to bring up Ubuntu terminal each time you reboot your phone.
--------------------------------
That's it! Thank you for reading this tutorial. Please feel free to make any comment or ask any question!
Awesome. I'll be trying this out as soon as I get a larger SD card. It would be great if you could upload a .zip with all of the scripts, downloads, etc. already placed in one folder; that would make it a lot easier.
Thx U for this Tutorial....it was really helpful...Can u fix the adobe flash thing...i know that sound will not work but just wondering if it can be installed.
yumcax said:
Awesome. I'll be trying this out as soon as I get a larger SD card. It would be great if you could upload a .zip with all of the scripts, downloads, etc. already placed in one folder; that would make it a lot easier.
Click to expand...
Click to collapse
Actually I thought about the same but here my uploading speed is 15kb/s maximum, so I'm not sure if I'm gonna upload a 600mb file...
reubenjack said:
Thx U for this Tutorial....it was really helpful...Can u fix the adobe flash thing...i know that sound will not work but just wondering if it can be installed.
Click to expand...
Click to collapse
Adobe Flash has no support for ARM architecture.. sorry, there's no way to install Adobe Flash plugin for Firefox on Ubuntu ARM.
OMG Im abt to die. Transfering the folder to my sd card takes 20 min. I really nid to get a better memory card (higher speed). SIGH..
Works nice on my N1 running MIUI 12.24..
BTW I have a question, if I wipe my phone(data,cache).. Would I need to perform any steps then?
Keshav_CoolDude said:
Works nice on my N1 running MIUI 12.24..
BTW I have a question, if I wipe my phone(data,cache).. Would I need to perform any steps then?
Click to expand...
Click to collapse
If you re-installed a rom (i.e. /system partition gets rewritten)
You'll need to execute the following commands on Android Terminal:
cd /sdcard/ubuntu
sh u
then type "b" to enter Ubuntu terminal
Happy New Year!
Hey,
In the OP you mention that some apps will not run because of the memory management? Is there a size threshold that this is start to be seen at or is it totally random on which things run/don't?
Thanks
houzuoguo said:
If you re-installed a rom (i.e. /system partition gets rewritten)
You'll need to execute the following commands on Android Terminal:
cd /sdcard/ubuntu
sh u
then type "b" to enter Ubuntu terminal
Happy New Year!
Click to expand...
Click to collapse
Okay.. Thanks for the guide..
Happy New Year..
Chopes said:
Hey,
In the OP you mention that some apps will not run because of the memory management? Is there a size threshold that this is start to be seen at or is it totally random on which things run/don't?
Thanks
Click to expand...
Click to collapse
I'm not very familiar with Linux kernel so sorry I can't give an accurate explanation
According to my observation, many applications in the Ubuntu 10.10 can successfully start (program title appears in task bar) but immediately they turn off by themselves.
And it seems to me that all those applications share a same characteristic: they're relatively bigger than others. For example, Terminal runs, Dictionary runs, Firefox runs, but Ubuntu Software Centre won't run.
So my guess is ... Android system would not allocate too much memory for an application in Ubuntu, thus they get killed before they could start.
I'll give this a one thumb up, because I got it working, got to play around a bit... it looks really nice... but I did a reboot of my phone after shutting it down properly, and now everytime I try to launch ubuntu again, I get a bunch of errors.
I've tried just about everything.... restoring to my nand backup I did before trying this, deleting the files off the sdcard and on my system relating to this, tried to set everything back up... but I still get errors and I can't get past them, even with trying "e" in the term.
FWIW, I'm on CM 6.1.1 and I do use DTa2sd with plenty of space left on all partitions. Here's a pastebin of my errors : http://pastebin.com/adCQ62iF
tehgeekguy said:
I'll give this a one thumb up, because I got it working, got to play around a bit... it looks really nice... but I did a reboot of my phone after shutting it down properly, and now everytime I try to launch ubuntu again, I get a bunch of errors.
I've tried just about everything.... restoring to my nand backup I did before trying this, deleting the files off the sdcard and on my system relating to this, tried to set everything back up... but I still get errors and I can't get past them, even with trying "e" in the term.
FWIW, I'm on CM 6.1.1 and I do use DTa2sd with plenty of space left on all partitions. Here's a pastebin of my errors : http://pastebin.com/adCQ62iF
Click to expand...
Click to collapse
Happy New Year!
Could you please go to Settings-> Application Settings-> Manage Applications-> on SD card and confirm there is no application on SD card?
Also please make sure you execute "b" after "Checking for Errors" notification disappears.
Running this distro does that mean i can use firesheep on my n1?
Awesome! What kind of battery life are you seeing using Ubuntu? Any apps in particular you've enjoyed having on your N1?
rossonza said:
Running this distro does that mean i can use firesheep on my n1?
Click to expand...
Click to collapse
According to my study Firesheep would require WinPcap to work, WinPcap is only available for Windows so unfortunately you can't use it.
Deathwish238 said:
Awesome! What kind of battery life are you seeing using Ubuntu? Any apps in particular you've enjoyed having on your N1?
Click to expand...
Click to collapse
I notice battery drains 2-3 mAh more when Ubuntu is idle, when actually using Ubuntu I notice 30-40mAh higher current draw. So actually it's not much
hey thanx houzuoguo,
working great on my n1....!!
is there any solution for the sound to run...??
I cant seem to get any of the "cat >" letters to work, it just hangs in the terminal.
houzuoguo said:
According to my study Firesheep would require WinPcap to work, WinPcap is only available for Windows so unfortunately you can't use it.
I notice battery drains 2-3 mAh more when Ubuntu is idle, when actually using Ubuntu I notice 30-40mAh higher current draw. So actually it's not much
Click to expand...
Click to collapse
Firesheep works in Ubuntu, you just have to compile it yourself.
1) Download the required dependencies:
Code:
sudo apt-get install autoconf libtool libpcap-dev libboost-all-dev libhal-dev xulrunner-1.9.2-dev
2) Install git:
Code:
sudo apt-get install git
3) Download the Firesheep source:
Code:
git clone https://github.com/codebutler/firesheep.git
4) Change to the Firesheep directory:
Code:
cd firesheep
5) Initialize it:
Code:
git submodule update --init
6) Compile it:
Code:
./autogen.sh && make
7) You'll find the file in the build directory.
hotweiss said:
Firesheep works in Ubuntu, you just have to compile it yourself.
1) Download the required dependencies:
Code:
sudo apt-get install autoconf libtool libpcap-dev libboost-all-dev libhal-dev xulrunner-1.9.2-dev
2) Install git:
Code:
sudo apt-get install git
3) Download the Firesheep source:
Code:
git clone https://github.com/codebutler/firesheep.git
4) Change to the Firesheep directory:
Code:
cd firesheep
5) Initialize it:
Code:
git submodule update --init
6) Compile it:
Code:
./autogen.sh && make
7) You'll find the file in the build directory.
Click to expand...
Click to collapse
Not to threadjack or anything of the sort but:
Does the above method work on getting firesheep installed on a n1 running ubuntu or is this just the way to install it assuming your running on normal hardware?
Second question, what is the resulting file?
Thanks,
Which terminal application are you using, and did you type the "cat >" on screen keyboard or copy&paste?

[Q] ruu leak help

my phone was not rooted and i wanted the new gb official build so i installed it and now i want t go back to froyo how do you do this on a mac
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Google came up with this
I looked FOREVER for these instructions. While I didn't write them, they definitely worked for me:
- Download the Android SDK for Macintosh at: Android SDK | Android Developers
- Extract it
- Download Fastboot for OSX (If not included with SDK)
- Extract fastboot and place it in your /tools folder.
- Open up a terminal window
- type: pico .bash_profile (this will create a .bash_profile)
- type the following in the new screen: export PATH=$
{PATH}:<sdkfolder>/tools
- Hit CNTRL + X
- Hit Y (for yes to save)
- It will return you to the terminal screen… type: exit
- Restart terminal.
- Then you can use your adb commands like you would on a PC. To test this, plug your device in (make sure its in debugging mode), then type "adb devices" in the new terminal window. It should show up with a number. This means you are good to go.
blueis300 said:
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Click to expand...
Click to collapse
A better statement is he can run things like you would on linux, because osx has a bash terminal built in. Type "terminal" into finder. Sadly, most osx people have no clue that exists, which is sad because it's not a hackjob like cmd.exe.
ok i got all the way to the last step and the terminal window keeps saying: -bash: adb: command not found and -bash: sdkfolder: No such file or directory
blueis300 said:
Even though its a Mac cant you run things in a Dos like mode with c:\ prompt?
Google came up with this
I looked FOREVER for these instructions. While I didn't write them, they definitely worked for me:
- Download the Android SDK for Macintosh at: Android SDK | Android Developers
- Extract it
- Download Fastboot for OSX (If not included with SDK)
- Extract fastboot and place it in your /tools folder.
- Open up a terminal window
- type: pico .bash_profile (this will create a .bash_profile)
- type the following in the new screen: export PATH=$
{PATH}:<sdkfolder>/tools
- Hit CNTRL + X
- Hit Y (for yes to save)
- It will return you to the terminal screen… type: exit
- Restart terminal.
- Then you can use your adb commands like you would on a PC. To test this, plug your device in (make sure its in debugging mode), then type "adb devices" in the new terminal window. It should show up with a number. This means you are good to go.
Click to expand...
Click to collapse
ok i got all the way to the last step and the terminal window keeps saying: -bash: adb: command not found and -bash: sdkfolder: No such file or directory

[Q] Sony Tablet S ADB support

Has anybody got a Sony Tablet S being recognised by adb?
It seems to be blocked :-(
And yes, I have done all the usual enable USB debugging etc...
I can not use it for development :-(
---------- Post added at 12:56 PM ---------- Previous post was at 12:06 PM ----------
Managed to sort it myself
you need to cd to your .android folder (on a mac, this is ~/.android) and then type
echo 0x054c > adb_usb.ini
Where 0x054c is the vendor id for Sony (I got that by looking at the attached evices in the 'About this mac' preferences)
Now adb sees the device - woohoo
would this apply if i just wanted to use it to transfer music and such? I am not incredibly savy with coding but i tried to enable debugging and all that. I am justnot sure whats the problem.
No, the Android File Transfer program still works without this
Good to know it can be used to dev on. Anyone have any information on how to send data out using the IR blaster, I dont think there is support for it in the native android libraries from what I can see?
The following procedure has confirmed that ubuntu 11.04.
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Kaz Taguchi said:
The following procedure has confirmed that ubuntu 11.04.
1. Enable debug mode for sony tablet S
2. Add line /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="054c", MODE="0666", GROUP="plugdev"
3. Change file mode
sudo chmod a+r /etc/udev/rules.d/51-android.rules
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
5. adb kill-server ; sudo adb start-server
6. finish!
Click to expand...
Click to collapse
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Found a way on Windows!
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Bojanglez said:
I don't seem to have that file
I had done all the other steps in order to mount the tablet and copy files over (which works great).
Does anyone have issues with Sony's Music player failing to update the database? Music appears in the native Music app correctly but nothing in the Sony one
Click to expand...
Click to collapse
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file.
Works lime a charm now.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
CaptainJack87 said:
With the help of the vendor ID from above and the following article on generic Tegra Tablets, was able to get it to show up on Windows!
(Copied from addictivetips)
1.You must have Android SDK installed before you can proceed. If you don’t have it already, proceed to our guide on what is ADB and how to install it. Make sure you download the Google USB Driver Package as well.
2.Open the google-usb_driver folder that you will find inside your Android SDK folder.
3.Open the android_winusb.inf file in notepad or any text editor to edit it.
4.Add these lines under [Google.NTx86] or [Google.NTamd64] depending on whether you are using 32 bit or 64 bit Windows. If unsure, it is safe to add these under both these sections. ;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
Don’t edit or replace any other text that is already there; just add these new lines and save the file.
5.Open a command prompt window and enter this command: echo 0x054C >> "%USERPROFILE%\.android\adb_usb.ini"
Note: this is where you have to use 0x054C instead of what is at the link, otherwise it wont work
Now your Android SDK drivers are configured to support any Nvidia Tegra based tablet. To be able to use ADB and other SDK tools with your device, you can proceed as follows:
1.On your tablet, go to Menu > Settings > Applications > Development and enable ‘USB Debugging’.
2.Connect your tablet to your PC via USB. You will get a notification that some drivers were not installed, which is OK for now.
3.Right-click ‘Computer’ and click ‘Manage’. Identify your device from the list, right-click it and click ‘Update Driver Software..’.
4.Choose to browse your computer for driver software and then select to pick from a list device drivers on your computer.
5.Choose to view all devices and click ‘Have Disk…’.
6.Browse to the google-usb_driver folder inside your Android SDK folder and select the android_winusb.inf file.
7.If you get any warnings prompts telling you that the driver might not be compatible, just choose to continue installing.
8.Once the drivers have been installed, you should be able to use ADB with your device.
9.To confirm that your device is recognized, launch a Command Prompt window and enter these commands: adb kill-server
adb start-server
adb devices
Also, using BRKs Transformer's instructions found a way to boot Tablet S into recovery: has reboot, update from ZIP and factory reset options
a) Hold down power and volume UP button
b) when SONY logo appears, release power button but keep pressing volume UP button
c) should load into recovery
This also gives us the MTP device driver, which I have been unable in finding/installing
No luck so far with Automated rooting tools, working hard to crack this awesome tablet!
Click to expand...
Click to collapse
Done loading packages.
Preparing to install archives
Downloading Google USB Driver package, revision 4
File not found: C:\Program Files (x86)\Android\android-sdk\temp\usb_driver_r04-windows.zip (Access is denied)
Done. Nothing was installed.
I tried downloading and installing
(Can't post links)Download: Android USB Drivers - Original (Firmware 1.0)
But when I try to install the drivers for the tablet through device manager it says:
The folder you specified doesn't contain compatible software... ...Windows for x64-based systems.
Apparently this driver is only for x86. But after googling "download Google USB Driver Package" that's all I can find.
Got it...
At least I was able to "enable it" through the USB port,
thanks to this exercise in frustration.
Alas no root screen cap still didn't work.
It flashes wildly and does nothing.
Anyone happen to know the proper command line in system variables for win 7 for adb should be?
I haven't used adb in forever, and I think alot of peoples issues with adb is in the fact they cannot use it outside of the android/android-sdk/platform-tools directory. As in you can just type adb shell, adb start-server, adb kill-server from the root dir. I had it set up before, but with a new comp now, and I forgot what it was before.
whats going wrong
i cant seem to get the device driver on my adb at all. no matter what i do i cant get the usb driver sorted. this is where i get stuck"
Please add 0x54c into .android/adb_usb.ini file under HOME directory by using following command from command prompt.
echo 0x54c >> %HOMEPATH%\.android\adb_usb.ini
home directory???? every time i try this from home directory i get nothing.
this is my problem.... i dont have this file or entry. what is the entry?????? o notpad doc??,
adb_usb.ini file was missing the 0x54c entry! <<< what is this. a screen shot goes a loooong way.
Adb was simple with my x10 and sgs2 but man this is giving me the ****s.
can someone please post a few simple screenshots of what directory is supposed to be where please?
---------- Post added at 08:39 AM ---------- Previous post was at 08:21 AM ----------
what does this mean?
Thanks Kaz Taguchi !!
Couldn't connect to my Sony..
It made me crazy..!
I was just forgotten the:
4. Add line idVendor to ~/.android/adb_usb.ini
0x054C
So i created the file:
touch ~/.android/adb_usb.ini
and echoed the line into the file
?????????
I've created an automated ADB driver installer for the Sony tablets.
No more messy, time-consuming SDK install.
http://forum.xda-developers.com/showthread.php?t=1488822
Official Sony instructions
Looks like Sony has posted official instructions for setting up ADB with the Tablet S:
esupport.sony.com/US/perl/support-info.pl?info_id=878
After following their instructions I still had to go to Device Manager, choose to Update the driver for my tablet, and point it to the SDK/usb_driver folder. After that it works great.
debug
Hey guys i have installed the android sdk and the sony s drivers from the official site as dreadengineer posted. but after run the adb devices command i was unable to saw my device.
After that i tried the automated installations that BluechipJ posted, but the result was the same i cannot see the devices neither on eclipse or adb devices command.
i want to debug my application on this device but i could not access it. Can someone help me.
I have a windows 7 x64 OS. i'm able to debug on htc phone and also on the super slower emulator

How To Guide Remove Microsoft Bloat

In the spirit of removing stubborn pre-installed APKs from freshly unpacked Android devices, I would like to share the apps I removed using adb and the commands used to do so.
I personally do not use Office or Bing so these were my primary targets, but I also removed OneDrive, OneNote, Outlook and Edge as well.
This is step-by-step for Windows users:
1. Download platform-tools from https://dl.google.com/android/repository/platform-tools-latest-windows.zip
2. Extract to C:\ (or a place of your choosing)
3. Open a command prompt from your start menu by typing "cmd" in your Windows search bar.
4. You should see something like: C:\Users\YourUsername_>
5. Type "cd C:\platform-tools" and press Return/Enter
6. You should now see C:\platform-tools>
7. Plug in your device with a USB cable and ensure you have turned Developer Options on your device (search Google for how to do this if unsure)
8. Type "adb shell" and you should get an Unauthorized message in the command prompt window followed by a pop-up on your device asking if you trust the computer you are connected to.
9. Select the option to trust the computer you are connected to.
10. Type adb shell again and hit Enter/Return and you should see a unique alpha-numeric device ID show in the command prompt now.
11. Begin uninstalling the packages you wish to no longer be stuck on your Surface Duo 2 with the command below.
12. Repeat the command below for each package/app you wish to uninstall.
pm uninstall --user 0 <package name from the list below goes here>
(Below are the packages I have personally removed line by line and still have stable experience on the device. Most are evident in the package name of what was removed. I will update the list as I remove more.)
com.microsoft.amp.apps.bingnews
com.microsoft.office.officelens
com.microsoft.skydrive
com.microsoft.amp.apps.bingnews.overlay.duo2
com.microsoft.office.onenote
com.microsoft.bing
com.microsoft.office.outlook
com.microsoft.office.officehubrow
com.microsoft.surface.office.outlook.overlay.duo2
com.microsoft.surface.tips
com.microsoft.bing.overlay.duo2
com.microsoft.surface.onedrive.overlay.duo2
com.microsoft.teams
com.microsoft.todos
com.microsoft.emmx (Edge Browser)
com.microsoft.windowsintune.companyportal
Hi. Somewhat cautious of doing anything that bricks my Duo 2 - I use many of the Microsoft apps, so I'm more interested in removing the Google suite of apps. Does the above approach work for Google apps too?

Categories

Resources