BackTrack 5 Security Distro on Thunderbolt - Thunderbolt Android Development

BackTrack 5 Security Distro on Thunderbolt - Thunderbolt Android Development

First, if you don't know what backtrack is, or what its used for I'd recommend the Ubuntu on Thunderbolt thread found here:
http://forum.xda-developers.com/showthread.php?t=1104983
He's done a lot of great work and its more refined.
Big thanks to anantshri, he's responsible for the .img and install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installations instructions:
Update your busybox (system/xbin) to the following version for chroot
Busybox http://db.tt/S9ERQvK
thanks twistedumbrella
Click to expand...
Click to collapse
download:
Terminal emulator-- I recommend Android Terminal Emulator by Jack Palevich
VNC Viewer-- e.g. android-vnc-viewer (free)
I also recommend 'Hacker's Keyboard'
Download the following three files and extract them with 7Zip.
======== FILE DOWNLOAD LINK================
DROPBOX links Bitlied for download count track
Alternate link from personal server.
Please do not create mirror : just want to keep a count on download's
PART 1 : Download Link : http://bit.ly/p1BT5
PART 2 : Download Link : http://bit.ly/BT5p2
PART 3 : Download Link : http://bit.ly/BT5p3
bt7z.001: http://www.mediafire.com/?x9cgxzdx84vc6uj
bt7z.002: http://www.mediafire.com/?xaoidipkg1o7vgo
bt7z.003: http://www.mediafire.com/?po3nznbxgvdipur
MD5 Sum : Thanks to DooMLorD
558ecb1f0e5feb1da86526df8761e6cc bt.7z.001
247842fd0d3ebb39454f76f4704d1537 bt.7z.002
f74d2f744434a7182b13287d9f8165e7 bt.7z.003
thanks anantshri
Click to expand...
Click to collapse
Once you have all the files downloaded, extract to a folder named 'bt'. You should see the following in the folder:
bt
bt.img
installbt.sh
startbt
stopbt
Copy the bt folder to your sdcard (file size~3.25GB)
Open up your Terminal emulator on your phone and cd to /sdcard/bt
type in the following
su
sh installbt.sh
If everything installed correctly you can proceed with the following
startbt --starts the backtrack service
stopbt --stops bt
bt --gives you backtrack command line
To access the gui
type ui in the bt shell to start the vncserver
killui stops it
your vnc server default login settings are going to be as follows
Address: 127.0.0.1 or localhost
Port: 5901
Password: 12345678
Additionally, you can use a workstation vnc viewer to log into bt via adb. Type the following into adb:
adb forward tcp:5901 tcp:5901
Ensure you have started the ui in your bt shell, then start your vnc client on your workstation. Connect to 127.0.0.1:5901 (or localhost:5901) and put in the 12345678 as the password.
You need to start the bt service every time you reboot with startbt, and need to reinstall bt when you flash a new rom (sh installbt.sh).
I'll continue to update this post with confirmations of what works and things we need to fix.
Optimization/tweaks:
type 'pico ~/bin/ui' in your bt shell, then adjust the resolution to 800x480
Working/Broken:
The big glaring omission is enabling monitor mode on the wireless adapter. What we need to make this happen is a stand alone installation (dual boot with android) and wireless chipset driver support. This is very unlikely to happen, especially when it runs with a relative degree of functionality in the android VM.
There are still many things that BackTrack can do, I encourage everyone to update their apt source.list and download the pieces they found missing, as well as to utilize the tools available-- this is still a very powerful toolkit.

dude this is legit. backtrack on linux is the ****.
i used to crack people's wireless with that ****, and do penetration tests all the time.
funny thing is im sonic wall certified lol. security my ass.

Samsuck said:
dude this is legit. backtrack on linux is the ****.
i used to crack people's wireless with that ****, and do penetration tests all the time.
funny thing is im sonic wall certified lol. security my ass.
Click to expand...
Click to collapse
is that section of backtrack functional though to actually get that use out of it? OP mentioned its not 100%.

Well played. BackTrack was our "secret weapon" when I worked in the tech field. Thanks.

I will be super excited if packet injection ever works.

If anyone is having issues extracting, you only need to use 7zip on the first file. This will extract all the files you need.
Ill be making some x server tweaks and compiling a list of functioning apps/hardware, will update the op.
Right now, wifi and 3g are working for data; I still need to test bt, but it should work. Ettercap fails when scanning for hosts, as do many other apps. Still a work in progress.
Sent from my ADR6400L using XDA App

this is sweet! i got it up and running in 20 minutes including extracting the files. i tried to install a few different versions of chrome and they all said wrong architecture. Im assuming this is an ARM issue because its not emulating x86 or x64 its just running on ARM. im curious if this will cause a problem for any other software that checks the processor, i didnt have time to check

Ok so, everything worked great until after "startbt". That works but once I go to start the ui, I get "Chroot: applet not found". Anyone know what I'm doing wrong?

can someone check if wireless card can be put in promiscuous mode? aka. capturing packages intended for someone else

kr0n1c said:
Ok so, everything worked great until after "startbt". That works but once I go to start the ui, I get "Chroot: applet not found". Anyone know what I'm doing wrong?
Click to expand...
Click to collapse
Did you update busybox?

cuguy said:
can someone check if wireless card can be put in promiscuous mode? aka. capturing packages intended for someone else
Click to expand...
Click to collapse
So I don't have an exact answer for you but I tried to run Aircrack-ng&Co and all I got was command not found.

I'm looking into that today, will also post a way to vnc in via adb, will make testing much easier.
Just got married, the honeydo lists have already started.. been juggling my time.
Sent from my ADR6400L using XDA App

Ke1evraTi said:
Did you update busybox?
Click to expand...
Click to collapse
I updated Busybox but still get the same error. To update BB, all I had to do was copy busybox.txt to /system/xbin correct?

i get to the command line fine, when I type ui I get command not found

Take away the .txt and overwrite the existing busybox in xbin. The browser appended .txt when you saved it and it should not be there.
For the ui, make sure you type bt first, so that you start the bt process. You should see [email protected]# or something similar instead of the usual #
Sent from my ADR6400L using XDA App

Gr8gorilla said:
i get to the command line fine, when I type ui I get command not found
Click to expand...
Click to collapse
Also, make sure you are su when you run startbt and bt

I actually fixed it by starting the command line and using vi to edit the /usr/bin/startvnc file, changed the resolution then exported the USER=root, I then used the command startvnc and it worked fine. Ui however did not work at all.

Gr8gorilla said:
I actually fixed it by starting the command line and using vi to edit the /usr/bin/startvnc file, changed the resolution then exported the USER=root, I then used the command startvnc and it worked fine. Ui however did not work at all.
Click to expand...
Click to collapse
Glad you got it worked out.
Additional way to connect to bt in op. Using adb should make troubleshooting much easier. Testing bt and promiscuous now
Additionally, you can use a workstation vnc viewer to log into bt via adb. Type the following into adb:
adb forward tcp:5901 tcp:5901
Ensure you have started the ui in your bt shell, then start your vnc client on your workstation. Connect to 127.0.0.1:5901 (or localhost:5901) and put in the 12345678 as the password.
Click to expand...
Click to collapse
Optimization/tweaks:
type 'pico ~/bin/ui' in your bt shell, then adjust the resolution to 800x480
Click to expand...
Click to collapse

Updated OP, we can't enable monitor mode on the wireless chipset, its running on a VM and there isn't driver support for it. This limits our ability to some extent, but there are still many useful tools in bt

this is DISGUSTING!!!
can't wait to try this out in the morning after work, MAJOR PROPS!

Related

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting!

[GUIDE] Getting ADB Setup; An Idiots' proof guide on getting ADB working for Rooting! v1.2
Hey XDAers. Getting ADB setup and working is an essential part to rooting your Android device and helps layout the foundations to better understanding the language and using it in this environment. While not going into extreme detail, this is just a quick guide or overview on the first part of rooting; Getting ADB setup and working.
** Make sure your Transformer is not currently connected to your PC yet. We will be installing device drivers first (Step 7) and modify a setting on your tablet first before connecting to your PC (Step 8).
Step 1 :
Download and install the Android SDK.
You can download the SDK from the Google Developer's website. I have linked for you the download page and a direct link to the installer (Note: the direct link may change in the future with future versions, I will try stay on top of this and change the link)
http://developer.android.com/sdk/index.html
http://dl.google.com/android/installer_r10-windows.exe
*New Version : http://dl.google.com/android/installer_r11-windows.exe
You may or may not be prompted to install the latest version of Java if you haven't done so already, install it, and you may or may not have to reboot your computer.
Step 2 :
Once the install is complete, navigate to the directory in which you installed the SDK and launch the SDK Manager executable. It may or may not ask you to download and install the Java JDK, do so if you haven't already.
*When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already*
Answer :
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead.
Thanks Crimton!
Click to expand...
Click to collapse
Step 3:
Once the SDK Manager is launched, it will look something similar to the window below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You will want to do something along the lines of update all or install all. This way it will download all the latest packages and you willhave the latest SDK tools installed.
Once that is complete, you can exit out of the SDK Manager.
Step 4:
Open up a command prompt window. You can do so by holding the WinKey+R, a run window will appear, type CMD, and hit enter.
Step 6:
Within the Command Prompt window, navigate to the Android SDK folder\platform tools folder (Command Prompt command : CD foldername\foldername\foldername\etc)
Step 7:
Now install the ASUS Sync software if you haven't loaded it previously. http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download. Just select your operating system, hit download, then install.
Why are we installing the ASUS Sync software you ask?
Well mainly because it has USB drivers that will help your PC operating system detect and display your ASUS Transformer. Without the drivers, ADB wouldn't be able to detect your device most likely!
*For other android devices, you will need similar software from that manufacture. HTC Sync for HTC devices as an example.
Click to expand...
Click to collapse
Step 8:
Enable USB Debugging on your android device / Transformer.
Go to Transformer Tablet, go to settings -> applications->Development, turn on USB Debugging.
Step 9:
Connect the USB cable from your android device / Transformer to the PC. It will begin to automatically install drivers, let it do so and complete. May ask to reboot machine.
Step 10:
Once that is done, go back to the command prompt. Run ‘ADB Devices’
You should see something like above, indicating it detected the transformer, if not, run the following ‘adb kill-server’, ‘adb start-server’, ‘adb devices’
Ok, if you are seeing something like the screenshot above then success, you have successfully gotten ADB up and working! Congratulations! That wasn't too hard now was it? You can now follow one of the root guides and follow the directions and you should be on your way to a fully rooted device. Cheers!
-------
Troubleshooting:
In the event you complete the steps above but your computer either will not recogonize the Transformer in Windows as a device, or ADB will not see it please try the following to see if this will fix it for you. You only need to try these if the above steps aren't working for you, but most people, they work fine.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html
-------
Notes:
-If you want another guide on something else, let me know, and I will see what I can do.
-Yes this has been posted a million times I know, but I thought this might help out those few people that don't feel like looking around. Plus, it has nice color illustrations. Who doesn't like picture books?
-------
Credits
Crimton for Java JDK workaround when not showing as installed
sourworm for new link to SDK installer

Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.

stuntdouble said:
Nice job. Added to ultimate thread. Probably a good idea to attach the pics in your post to the XDA forums, so they are saved in future, as a lot that are hosted on other sites die after too many people view them.
Click to expand...
Click to collapse
Will do when I get home, thanks for the tip.

Ill add this to the FAQ

One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.

I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
Glad you got it resolved, I will edit the guide and make note about java installation.

Daughain said:
One of these days I hope to get ADB set up in Ubuntu 10.10.....
HTC Vision; Rooted, Booted and Scooted.
Click to expand...
Click to collapse
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740

neilkarunatilaka said:
[GUIDE] Lazyman's installation guide to ADB on Ubuntu 10.10
http://forum.xda-developers.com/showthread.php?p=11823740#post11823740
Click to expand...
Click to collapse
at a glance, even that thread makes it look like more trouble than it is. but good info

RedMist said:
I'm not a complete noob, but I'm stuck on step 1!!
When I run the android SDK installer it tells me I don't have the java JDK installed, even though I've installed it already....
http://download.oracle.com/auth/otn-pub/java/jdk/6u25-b06/jdk-6u25-windows-i586.exe
OH! It's working now.... Never mind.
Click to expand...
Click to collapse
How did you fix it? I've been struggling with this same issue for at least a month now.

n25philly said:
How did you fix it? I've been struggling with this same issue for at least a month now.
Click to expand...
Click to collapse
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk

Crimton said:
It says that but disregard it. If you've installed it, it should be fine. When it gets to the part that says its not installed and won't let you go any further simply click back then click forward again and it should allow you to go ahead. At least that's how I remember it.
Sent from my ADR6400L using Tapatalk
Click to expand...
Click to collapse
lol, simple solutions are good. Just wish it didn't take me a month to find that one out.

Very simple and easy to follow. Thanks OP.

I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?

randy_c said:
I download Asus sync for window 7 64bits but when I run asus, it doesn't detect my device and of course ADB devices didn't show up any device. Something I missed? Please?
Click to expand...
Click to collapse
Sorry to hear that. Off the top of my head, I'm not sure what could be causing this. But here are a couple things you can try. And please let us know what happens next.
Try uninstalling the ASUS Sync software, and reloading it.
After reinstalling the ASUS Sync software, restart your PC
Make sure your Transformer tablet is in USB Debugging Mode, and connect the USB Cable
You should see a Win7 prompt that says installing drivers. If you do not, try connecting to a different USB port, I've had to do this once on an older PC of mine.
In ADB be sure to kill server and start server and then see if you can see the device
Now, if you are still not seeing it installing drivers, or its not showing up as a device on My Computer, or ADB is still not seeing it, try download and install these ASUS Windows USB Drivers, these may do the trick : http://hotfile.com/dl/118226479/2f89b99/ASUS_Android_USB_drivers_for_Windows.zip.html

I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!

andrew53517 said:
I have a few questions. This is the first real time I'm using ADB.
So I have tried everything you listed above and I can get it to sync on occasion, but I cannot get it to read my device in the command prompt. I type this "D:\android-sdk-windows\tools>adb devices" and it says "The device is not ready." Why is it not finding it even with it syncing at that moment?
Also, do you type "D:\android-sdk-windows\tools>" every time you run something? If so, is there a way to get that to show up beforehand every time instead of having to type it? Thanks again for your help!
Click to expand...
Click to collapse
1) First thing you can try is the famous 'adb kill-server' 'adb start-server' commands and see if that will get it going. Also 'adb usb' will restart the daemon listening on USB, so maybe that could make it usable. If not, make sure the ASUS Sync app is not running, and perhaps see if there are any running services/apps on your Transformer that could be causing the conflict. Download System Panel Lite from Market and tell it to end all apps, then try again (make sure USB Debugging is enabled)
If you tried all of that, and still no dice, make sure no USB Drives or Memory Cards are connected, then connect the Transformer (w/ USB Debugging), go to Device Manager, uninstall the USB drivers for the device if you can find it or it may show up as a USB Mass Storage device under USB Controllers, then disconnect the Transformer, reconnect the Transformer, it should reinstall the drivers for the Transformer since you already have ASUS Sync installed, then retry.
If again still no dice, try using the ASUS USB Windows Drivers and going to Device Manager and updating the drivers with those you downloaded (download the correct ones for your particular operating system, and then try again.
Now, if this still doesn't work, let me know, and I'll try think of something else. Maybe someone else has had this issue and come up with a workaround or solution, but I'm drawing a blank currently. I'll sleep on it and see if I can think of anything else
2) You don't have to type that up all the time. What you can do is navigate the platform tools folder (or whatever folder has the adb files), then if on Win 7, hold shift and right click on the folder (Platform Tools for example), and you will see an Open Command Prompt here. Hit that, and it will already be in that root folder. But in general, in a command prompt window, once you have navigate to the specified folder, you will be in that folder, so you will only need to type ADB 'command' if that makes sense.
[/LIST]

I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.

andrew53517 said:
I think I might have figured it out, if this is it. So I downloaded the drivers but I don't think they ever installed. Don't laugh lol, how do you install them? There isn't a .exe file or anything to install them.. I just see files and notes. Do I put it somewhere or what do I do with the 3 files and readme file?
I think that might fix my problem...I hope.. Thanks again for your help. Much appreciated!
EDIT: I think I got the drivers and it still can't find it. :/ I think I'm going to take a break on rooting for a few. ADB is a pain! lol. I might just wait for an easier method or just not root it. We'll see. Thanks again.
Click to expand...
Click to collapse
If you get a chance, try this on a Windows XP or Windows 7 machine that you haven't connected the Transformer too yet, and follow the guide exactly, and I'm pretty sure it will work without a problem I'm just thinking something has happened when it loaded up the drivers for you initially and that is why you are having the issues, or some background process on either Windows or the Transformer is making the device seem "busy", thus giving you the not ready error, as this process has worked for many many other users.

I was just thinking about it. Maybe I can try that on my downstairs computer. Ill give it a shot Sunday night and see how it goes...ill let you know...

[GUIDE] Noob's Guide to setting up ADB

How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!

I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.

Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?

Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!

I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.

ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES

Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked

Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.

bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.

+1 for sticky

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.

Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.

I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App

allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.

Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App

bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.

sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.

bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse

Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App

[GUIDE] Running Debian Linux on Xperia X8 (chroot)

First of all please notice, that this is not my own development project, it is just a port of the guide for HTC G1 from http://pdaclub.pl/forum/htc-dream/%28how-to%29-instalacja-debiana-%28na-g1%29/ for Xperia X8.
Please be aware, that this solution has been only tested with one Xperia X8 device running Floyo 0.30 (thanks to Racht for this great ROM !). I cannot guarantee that it will work on every other custom ROM as well as on the stock Xperia X8 ROM's.
Please also notice, that instructions in this tutorial in some cases can brick Your phone. I'm not responsible for any damage to the software or hardware caused by this tutorial. You can follow the instructions from this guide but only at Your own responsibility!
Please also notice, that I'm not an Android Developer. I'm just a user with some knowledge about Unix, so don't blame me if this tutorial won't work for You. You can post Your problems and we'll try to solve it together.
OK, I think that's all for the intro .
TABLE OF CONTENTS:
1) The purpose of this guide
2) Requirements
3) Things to prepare
4) Installation
5) Some known bugs
6) Some little tips
1) The purpose of this guide.
This guide reffers to the newbie users who want to run Debian Linux on their Xperia X8. Step by step I'll try to explain how to run Debian simultaneously (at the same time) with Android. To gain that we'll use a program/command chroot (http://en.wikipedia.org/wiki/Chroot) which will allow us to Run Debian in Android as something similiar to "virtual machine" on PC.
You may ask why to run Debian on Android device ?
There are several answers to that question:
a. For testing...
b. ...developing applications in for e.g. C/C++ for ARM platform and try to run them on Android OS.
c. Installing Linux applications (like web servers, WiFi cracking software) and test what is working and what isn't.
d. For fun
For those who are asking what Debian actually is - please refer to the page http://en.wikipedia.org/wiki/Debian.
2) Requirements.
Before continuing check if You and Your device meet the following requirements:
a. ROOTED Xperia X8 device (I recomend to have Floyo 0.30 by Racht ROM installed, because it was tested on this ROM. I don't know if it'll work on different ROM's.)
b. At least 800MB space free on Your SD Card
c. Access to PC computer
d. Basic knowledge about Windows command line and Linux shell
e. About 1 hour of free time to set up everything
3) Things to prepare.
a. Download one of the following packages:
http://rapidshare.com/files/327504536/debian750.rar
Click to expand...
Click to collapse
or
http://rapidshare.com/files/327491605/debian1.5.rar
Click to expand...
Click to collapse
These are the packages containing Debian drives image as well as all other files needed to install Debian on Android. The only difference is that the first one is 750MB and the second is 1,5GB. The second one is for bigger SD Cards, you'll get more free space in Your "virtual machine" after running it.
b. ADB Shell (can be found in Android SDK in folder platform-tools\ - http://developer.android.com/sdk/index.html)
c. SSHDroid from Market (only if You're planning to connect to Your Debian via SSH)
d. PuTTY for Windows (only if You're planning to connect to Your Debian via SSH - http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)
e. ConnectBot or Terminal Emulator from Market (it's a good terminal application)
The bold items are necessary.
4) Installation.
PERFORM A FULL SYSTEM BACKUP USING XRECOVERY BEFORE PROCEEDING ANY FURTHER !
Now the best part !
There are several ways to install Debian:
1) Some are using Terminal Emulator application (preinstalled in Floyo 0.30)
2) Others are connecting with phone via SSH
3) But some are using adb shell command from Android SDK and that's the way we'll do this, because I know there are some differences between using adb shell and other ways. I tested it with adb and it is working so I think it is the right choice.
First, unpack the *.rar file of Your choice (debian750.rar or debian1.5.rar) to Your hard disk on a PC.
Replace file bootdeb which can be found in Debian folder after unpacking the archive with the one from bootdeb.zip file attached to this post. You need to do this, because the bootdeb file which is in the archive won't let You boot Debian correctly. It'll only cause Xperia X8 to restart after few seconds since execution. The file in bootdeb.zip has been corrected by me and it allows to boot Debian without any (known ) bugs.
Copy the Debian folder from the archive directly to the SD Card (also known as a root directory of Your SD Card). You should have the following directory tree on Your SD Card visible in Xperia X8:
/sdcard/Debian/bootdeb
/sdcard/Debian/debian.img
/sdcard/Debian/installer.sh
etc...
Click to expand...
Click to collapse
Enable USB Debugging in Xperia X8. To do this go to Settings->Applications->For programmers and check USB Debigging.
Connect Your phone via USB and don't mount the SD Card (just like You want to charge the phone via USB).
On Your PC click Start->Run, type cmd and cd to the directory where You installed Android SDK, then cd to platform-tools and execute command adb shell. After execution You should see a # symbol in the command line window like on a below screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now execute the following commands in ADB ahell on PC:
su
cd /
sh /sdcard/Debian/installer.sh
Click to expand...
Click to collapse
And You shoul get something like this:
VERSION 2.1
Custom Debian Bootloader is now installed! Quick huh?
etc...
Click to expand...
Click to collapse
And it's done ! Debian Linux has been installed.
Type in ADB Shell command
exit
Click to expand...
Click to collapse
As many times (I guess 3) until command line window disappears. Disconnect Your phone from PC and unplug the USB cable.
Now let's try to run Debian - on Xperia X8 run ConnectBot or Terminal Emulator and type:
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
Remember to allow the terminal application to run as a superuser.
After a while You should see a screen similar to the below screen shot:
I removed the lines (blured section) which You won't see after first boot. I have them, because I installed Apache Web Server and it is starting at the logon .
As You can see we are logged into Debian Linux !
Now, execute the following command:
/scripts/onetime.sh
Click to expand...
Click to collapse
It's necessary only after first logon. It'll let You to set up root password (only for Debian, not for Android) and do some more stuff (actually I didn't even check what this script is doing - forgive me).
And it's done... Now You are on Your own with Debian installed ! Go, play around, because it is a fully functional operating system for Your demand .
What about the performance ?
My Debian is still working since one day in the background (minimize the Terminal Emulator window after logging in) and I haven't suffer any problems with the low performance yet. I even set up an icewm window manager and VNC Server to be able to log in to my machine via VNC client and see the desktop and it isn't too laggy . But that's only a stupid future. The most power we get because of the access to Linux Shell (the command line which let us to use Linux applications on our Xperia X8).
4) Some known bugs.
For Your own safety read this short section.
1) Better don't try to unmount the SD Card from Xperia X8 (for e.g. when mounting the phone to the PC) when Debian is running. I didn't try this yet, but the bootdeb script is creating something called loop device in the Android system which should be properly unmounted. If this device will wanish due to some user activity the phone may not boot correctly any more.
2) When You finish playing with Debian always use the exit command to safely unmount the loop filesystem. After exit Your phone needs to be rebooted, better don't try to override this setting.
3) If somehow You will loose connection with Debian in Terminal Emulator You always can run:
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
And log in again. You'll just receive several errors on the boot screen, because the script will try to mount already mounted file system.
5) Some little tips.
1) After first logon execute the following commands:
cd /etc/apt
nano sources.list
Click to expand...
Click to collapse
And in the opened text editor add these lines (do not overwrite the file contents):
deb http://ftp.debian.org/debian lenny main contrib non-free
deb-src http://ftp.debian.org/debian lenny main contrib non-free
Click to expand...
Click to collapse
After this execute the command:
apt-get update
Click to expand...
Click to collapse
It will update Your applications repository available for Debian.
2) Running Apache Web Server:
Execute command:
apt-get install apache2
Click to expand...
Click to collapse
To install Apache Web Server. When the installer asks You if You want to proceed with the installation type Y.
After installation run command:
/etc/init.d/apache start
Click to expand...
Click to collapse
And then You can try to connect to Your phone on port 80 using HTTP browser and see if there's a message It works! .
3) Uploading files to Your Debian "virtual machine":
Install SSHDroid from Android Market.
Download program WinSCP and connect to Your device on port 22 using root as a user name and admin as a password.
After connection open location /data/local/mnt and You'll see Your Debian file system.
I think that's all for now.
I hope this guide will help "newbie" users to run Debian on their phones.
If You have any more questions or problems please let me know.
Regards,
Chris.

you should post this on development!

At the moment it's a little fiddling. Start phone -> connect bot -> su -> sh /sdcard/Debian/bootdeb -> from there I should be able automat anything
How can I use some kind of autostart?
Why I lose connection in ConnectBot when I disable mobile internet connection? Doesn't make sense to me. Mobile internet has nothing do do with local shell, or?
kingsize623 said:
you should post this on development!
Click to expand...
Click to collapse
He should. This is GREAT!

hello,
if i typ
su
sh /sdcard/Debian/bootdeb
and then come some text
and my phone does reboot.
what am i doing wrong?

kingsize623 said:
hello,
if i typ
su
sh /sdcard/Debian/bootdeb
and then come some text
and my phone does reboot.
what am i doing wrong?
Click to expand...
Click to collapse
I also had this problem. But try using ConnectBot - this is known for me to work.

kingsize623 said:
hello,
if i typ
su
sh /sdcard/Debian/bootdeb
and then come some text
and my phone does reboot.
what am i doing wrong?
Click to expand...
Click to collapse
Hi kingsize623!
As I said at the begining this script is highly ROM-dependent. It can run on some ROM's, but on the others there will be many problems.
I suggest You to edit file /sdcard/Debian/bootdeb in some text editor (I suggest Notepad++), locate the line:
busybox mount -o loop,noatime $kit/debian.img $mnt
Click to expand...
Click to collapse
(it should be line 47), and change it to:
mount -o loop,noatime $kit/debian.img $mnt
Click to expand...
Click to collapse
This should help. If it won't, there can be a lack of some module in Android on Your device which will prevent the script from running (no loop support for e.g.).
If You'll face some further problems let me know.

bagers said:
I also had this problem. But try using ConnectBot - this is known for me to work.
Click to expand...
Click to collapse
i've treid
and make a printscr
http://imageshack.us/photo/my-images/233/screenshot1315842466117.png/
http://imageshack.us/photo/my-images/18/screenshot1315842470958.png/

bagers said:
At the moment it's a little fiddling. Start phone -> connect bot -> su -> sh /sdcard/Debian/bootdeb -> from there I should be able automat anything
How can I use some kind of autostart?
Why I lose connection in ConnectBot when I disable mobile internet connection? Doesn't make sense to me. Mobile internet has nothing do do with local shell, or?
He should. This is GREAT!
Click to expand...
Click to collapse
Hi bagers!
Thanks for the comments on this post !
First of all, You're right, maybe I should post it on Dev section, but I didn't use XDA-DEVELOPERS much in the past, so I was afraid I may get kicked because of such information from "newbie user" in Dev section. This section (in my understanding) is for Android guru's, and I'm not one of them .
As for the autostart: the only thing You can automate in my opinion is the part where You type:
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
The only thing You need to do is to write a simple script which will look like the following:
su
cd /sdcard/Debian/
sh bootdeb
Click to expand...
Click to collapse
or
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
Name it for e.g. startdeb and place it in /system/bin for e.g. (I think bash will look for files in this directory by default, but I'm not sure about that).
Now, everytime when You'll try to run Debian, just open ConnectBot and type startdeb - this should automatically make You su and execute the startup script.
As for the dissconnections issue:
As far as I can see this problem exists on Floyo 0.30 as well. I'm not yet sure why it acts like that.

kingsize623 said:
i've treid
and make a printscr
http://imageshack.us/photo/my-images/233/screenshot1315842466117.png/
http://imageshack.us/photo/my-images/18/screenshot1315842470958.png/
Click to expand...
Click to collapse
As I wrote in previous post - try modyfying the startup script.
You also should have Busybox installed (if You don't have it download it from Market).

I installed also sshdroid and connected to the phone from Windows 7 using Putty. But, when I disconnect putty, then I will also see this "Rebooting device to ensure clean takedown.".
Ehrm, I just wanted to disconnect putty, not to shut down debian. Another bug?
Can you disable all this "Rebooting device to ensure clean takedown.", it's really disturbing.
krzysiek_grucha said:
As for the autostart: the only thing You can automate in my opinion is the part where You type:
The only thing You need to do is to write a simple script which will look like the following:
or
Name it for e.g. startdeb and place it in /system/bin for e.g. (I think bash will look for files in this directory by default, but I'm not sure about that).
Now, everytime when You'll try to run Debian, just open ConnectBot and type startdeb - this should automatically make You su and execute the startup script.
Click to expand...
Click to collapse
Okay, I done that and something really strange happened.
I made a files called "sd" in /system/bin with content:
su
sh /sdcard/Debian/bootdeb
Like you said.... But when I type sd in ConnectBot then, debian will start, and then the phone will restart...
But, when I type su and sh /sdcard/Debian/bootdeb, manually in ConnectBot, then debian will start with no error. Strange, huh? Any idea? Bug?
krzysiek_grucha said:
As for the dissconnections issue:
As far as I can see this problem exists on Floyo 0.30 as well. I'm not yet sure why it acts like that.
Click to expand...
Click to collapse
Please add it to the bug list. Maybe later someone will have an insight.

bagers said:
I installed also sshdroid and connected to the phone from Windows 7 using Putty. But, when I disconnect putty, then I will also see this "Rebooting device to ensure clean takedown.".
Ehrm, I just wanted to disconnect putty, not to shut down debian. Another bug?
Can you disable all this "Rebooting device to ensure clean takedown.", it's really disturbing.
Okay, I done that and something really strange happened.
I made a files called "sd" in /system/bin with content:
su
sh /sdcard/Debian/bootdeb
Like you said.... But when I type sd in ConnectBot then, debian will start, and then the phone will restart...
But, when I type su and sh /sdcard/Debian/bootdeb, manually in ConnectBot, then debian will start with no error. Strange, huh? Any idea? Bug?
Please add it to the bug list. Maybe later someone will have an insight.
Click to expand...
Click to collapse
Hi again !
There are lots of bugs as I can see . But... If You're connecting from Putty don't be surprised that the phone is rebooting after closing Putty window. It works like that:
1)You're running the sh /sdcard/debian/bootdeb from Putty - Putty is the only terminal for the script.
2)When You dissconnect suddenly the only terminal which was preventing the bootdeb script from running wanishes so the script continues working (so it's jumping to reboot section). That's not a bug, it was written to work like that.
I don't suggest You to disable the rebooting - it helps You to have a clean unmount. If You override this, strange things may happen when You'll boot for the next time, but it is not sure for 100% - check it for Yourself .
As for the not working script file - I thought that su command won't work in the script. That's why the bootdeb script doesn't already have it included.
If You want to know about some more bugs:
Don't try to set up OpenSSH on Debian - it won't work.
Don't run FTP server like proftpd or vsftp - port 21 is forwarded correctly, but port 20 is not, and that's why FTP is not working.
There are many bugs, but if You'll follow simple rules You won't have any problem with using Debian.

Can you think of some workarround in order to use Windows+Putty+Disconnect+Nophonereboot?
I really like to use that phone now as a server, because the power consumption is very very little (compared to a PC server). All time connected to charger (~3,5 W) would only coast me around 5 or 10 Eur per year. l So I plan to run Debian on the phone at all times and from time to time to administer my "server" using Putty and WinSCP.
But of course, at some time I'll have to quit Putty (and WinSCP)...
The problem is, that SSHDroid runs "outside" of Debian. The ssh would need to run "inside" Debian. You already told me not to try OpenSSH. Do you know any alternative to OpenSSH or an alternative protocol? Connect and remote administer by anything else, vnc server maybe (vnc for console?), but not ssh.

bagers said:
Can you think of some workarround in order to use Windows+Putty+Disconnect+Nophonereboot?
I really like to use that phone now as a server, because the power consumption is very very little (compared to a PC server). All time connected to charger (~3,5 W) would only coast me around 5 or 10 Eur per year. l So I plan to run Debian on the phone at all times and from time to time to administer my "server" using Putty and WinSCP.
But of course, at some time I'll have to quit Putty (and WinSCP)...
The problem is, that SSHDroid runs "outside" of Debian. The ssh would need to run "inside" Debian. You already told me not to try OpenSSH. Do you know any alternative to OpenSSH or an alternative protocol? Connect and remote administer by anything else, vnc server maybe (vnc for console?), but not ssh.
Click to expand...
Click to collapse
The workarround is very simple. As You said SSHDroid works on the "outside", but I'm telling You that it can work in the "inside" of Android as well. I tried to use X8 as a web server so this solution has been tested.
1) Run SSHDroid
2) Connect using ConnectBot to [email protected] and run:
su
sh /sdcard/Debian/bootdeb
Click to expand...
Click to collapse
You'll have Debian on the phone already started.
3) Connect to Your phone via Putty with Debian started in ConnectBot and type:
chroot /data/local/mnt /bin/bash
Click to expand...
Click to collapse
It will connect to the virtual Debian on Your phone and will let You to administer it, but on the second side it won't even touch bootdeb script which is annoying You so much, so the phone won't restart after logging off from Putty, because the "main" session will be still held by ConnectBot on the phone.
The only thing You need to remember is to safely kill Debian when You'll want to restart the phone using exit command in ConnectBot (which will cause the phone to restart as usual).
As I know, You'll very soon tell me, that there's a bug - don't let the Android device to go to "sleep" (turn off the screen), because the performance of the "server" will get very low because of lower CPU speed in sleep mode.
Hope it'll help

krzysiek_grucha said:
As I wrote in previous post - try modyfying the startup script.
You also should have Busybox installed (if You don't have it download it from Market).
Click to expand...
Click to collapse
I've treid it twice and i've bricked my phone twice
And now i can't instal gingerdx (i was on gingerdx)
So is there any way to deinstal the whole debian.
And trey it argain on froyo(i've learnt something!)

kingsize623 said:
I've treid it twice and i've bricked my phone twice
And now i can't instal gingerdx (i was on gingerdx)
So is there any way to deinstal the whole debian.
And trey it argain on froyo(i've learnt something!)
Click to expand...
Click to collapse
Hi !
I guess there's some problem with GingerDX.
To Deinstall Debian You just need to delete the Debian folder from /sdcard/ . Nothing has been installed into /system/.

krzysiek_grucha said:
Hi !
I guess there's some problem with GingerDX.
To Deinstall Debian You just need to delete the Debian folder from /sdcard/ . Nothing has been installed into /system/.
Click to expand...
Click to collapse
And You shoul get something like this:
VERSION 2. Custom Debian Bootloader is now installed!
Quick huh? etc... And it's done.
Click to expand...
Click to collapse
He instals a custom boatloader right?
Mayby it doesn't work with gingerdx becouse he restarts after the gingerdx logo but before the cyanogen mod 7 logo, i don't know how to name it
Btw, sorry for my bad english

kingsize623 said:
He instals a custom boatloader right?
Mayby it doesn't work with gingerdx becouse he restarts after the gingerdx logo but before the cyanogen mod 7 logo, i don't know how to name it
Btw, sorry for my bad english
Click to expand...
Click to collapse
No - if I am not completely wrong - the real bootloader of the x8 will not be changed in any way.
The debian bootloader is only needed to start debian inside android.
kingsize623 said:
I've treid it twice and i've bricked my phone twice
And now i can't instal gingerdx (i was on gingerdx)
So is there any way to deinstal the whole debian.
And trey it argain on froyo(i've learnt something!)
Click to expand...
Click to collapse
Don't panic, as long as you did not mess with the bootloader, you can always rescue your device.
I also bricked my device once, could not even get to xrecovery. Read this post.
http://forum.xda-developers.com/showpost.php?p=13341271&postcount=2
No worry, with PC Companion and repair (you'll loose all data) you will be able to recover your phone.

My phone has GPRS and WiFi enabeld at the same time.
Is it possible to tell the a few selected debian processes "use only GPRS, no WiFi"?

bagers said:
No - if I am not completely wrong - the real bootloader of the x8 will not be changed in any way.
The debian bootloader is only needed to start debian inside android.
Don't panic, as long as you did not mess with the bootloader, you can always rescue your device.
I also bricked my device once, could not even get to xrecovery. Read this post.
http://forum.xda-developers.com/showpost.php?p=13341271&postcount=2
No worry, with PC Companion and repair (you'll loose all data) you will be able to recover your phone.
Click to expand...
Click to collapse
so you can't HARD brick your device?
o, and thanx for your help

kingsize623 said:
so you can't HARD brick your device?
Click to expand...
Click to collapse
I also asked that myself....
http://forum.xda-developers.com/showthread.php?t=1239274
Afaik - from my knowledge from reading and searching the forums alot - a permanent (must send to se to repair) brick is only possible if you want to use the new cracked bootloader and mess up something.

[GUIDE] How to install Universal Naked Drivers

I have seen many questions asking how to install universal naked drivers. Last week I received (loan) a windows computer and had the same issues. I decided to provide the info to help others.
Note: These drivers do work properly for the TF300T even though they may not state that exactly. Also if your tablet identifies as a TF201 it will still work properly.
Note: If you are on windows 8 and having problems please see the bottom of this post #1 for help! This info was provided by prototype7 please give him a thanks.
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process if we are to succeed.
Here are the choices I had to use to change my drivers and a link to the drivers.
windows-start - in search type device manager and return
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
right click on the entry you wish to change the driver for
Update Driver Software
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says drivers not signed; install anyway
Windows 8
Note: The following info was kindly provided by prototype7. Please give him a thanks.
Originally Posted by prototype7
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!

Re: How to install Universal Naked Drivers
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.

And this thread is now stickied
MD

philos64 said:
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
Click to expand...
Click to collapse
Thanks for the kind words. I have wanted to post this for sometime but didn't have windows to prove the method.

Moscow Desire said:
And this thread is now stickied
MD
Click to expand...
Click to collapse
Thank you!
I just hope it can help some others getting their drivers installed and working.

Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.

Manox7 said:
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Click to expand...
Click to collapse
Thanks!
I don't know why some tablets require the tablet designation and others don't. For that reason we suggest everyone use them. It is a code assigned by google that designates the manufacture of the unit. On linux we have to declare them to avoid a permissions error but we don't have to add drivers.
I'm glad you got everything sorted.

I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.

prototype7 said:
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.

tobdaryl said:
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
Click to expand...
Click to collapse
Go ahead, it would make it easier to see. Glad I could help.

prototype7 said:
Go ahead, it would make it easier to see. Glad I could help.
Click to expand...
Click to collapse
Thanks again, I'll put in the first post for others.

Windows for x64
tobdaryl said:
Thanks again, I'll put in the first post for others.
Click to expand...
Click to collapse
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time

nathanielhall929 said:
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
Click to expand...
Click to collapse
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.

file selected still not working
tobdaryl said:
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
Click to expand...
Click to collapse
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information

nathanielhall929 said:
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
Click to expand...
Click to collapse
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.

Still nothing
tobdaryl said:
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Click to expand...
Click to collapse
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.

nathanielhall929 said:
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
Click to expand...
Click to collapse
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.

how do I start ADB?
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe

nathanielhall929 said:
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
Click to expand...
Click to collapse
Check the thread you wished me to help with as I think I have already posted the resolution there.

tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
Thanks for ur great job
I have tf300t with replaced logicboard. -it was bricked
My os win8 64bit
I tried universal naked driver ..but no way
is their any reasons with the last bricked in this case...??
Sorry for the poor english

Lightpack on the Shield Console ~ Possible?

I'm getting a Shield Console soon and while searching for accesories; stumbled upon this amazing Kickstarter backed Ambilight clone - Lightpack. Tho it's mentioned on their website that (Rooted) Android is supported out of the box, it's been more of an hit or miss on functionality. And it seems to be working without a hitch on an OUYA, which is also an Android Box. Does anyone else have this Lightpack setup with their Shield Console? Has anyone got the Prismatik App to function or even screen capture on their Shield? Is it worth rooting the Shield for this Lightpack?

If you are using Kodi and looking for a AmbiLight I can recommend Hyperion
It's working perfect.. (Kodi only and no root)
And have led's connected to a RaspPi running Hyperion Daemon... No cables to my Shield.. connects with wifi

I have this exact setup and the screen capture does not function.
Very dissapointed. Lightpacks android support died when the OUYA did.

If you don't mind having to connect to a raspberry pi, Hyperion might work with Lightpack..
(I don't have this and have never used one, this is just a guess)
I did some searching and I think u can run Lightpack with a raspberry pi and have your shield connect with hyperion...
...one page I found.. (google Lightpack Hyperion)
http://www.creativenightly.com/2014/07/setting-up-hyperion-on-a-raspberry-pi-for-use-with-lightpack/

NisseDILLIGAF said:
If you are using Kodi and looking for a AmbiLight I can recommend Hyperion
It's working perfect.. (Kodi only and no root) And have led's connected to a RaspPi running Hyperion Daemon... No cables to my Shield.. connects with wifi
Click to expand...
Click to collapse
Thank you for this! Might eventually try it out when I get a moment. Never played with a RaspPi before you see.
NisseDILLIGAF said:
If you don't mind having to connect to a raspberry pi, Hyperion might work with Lightpack..
(I don't have this and have never used one, this is just a guess)
I did some searching and I think u can run Lightpack with a raspberry pi and have your shield connect with hyperion...
...one page I found.. (google Lightpack Hyperion)
http://www.creativenightly.com/2014/07/setting-up-hyperion-on-a-raspberry-pi-for-use-with-lightpack/
Click to expand...
Click to collapse
Thank you for this too The magic behind lightpack was that, you could connect it to your android device; run an app and you're set. Nothing more to fiddle around with. If things don't work, then your path is the one I take.

Hi, plz what version of Kodi you are using on Nvidia Shield TV? I tryed on my Kodi build from 29-12-2015 (Jarvis 16.0 BETA5) and there this dosnt works.
Thanks for your advantage...

has anyone tried this?
https://www.youtube.com/watch?v=3otxXST1d50

I think for this you needs have rooted android device...

NisseDILLIGAF said:
And have led's connected to a RaspPi running Hyperion Daemon... No cables to my Shield.. connects with wifi
Click to expand...
Click to collapse
Sir, can u please explain this further? especially the part where u mention that ur Shield connects via Wifi! So u don't have to use a grabber and hdmi splitter which u connect to ur RaspPi?

chieco said:
Sir, can u please explain this further? especially the part where u mention that ur Shield connects via Wifi! So u don't have to use a grabber and hdmi splitter which u connect to ur RaspPi?
Click to expand...
Click to collapse
Hi, its simple easy and i will try explain you what to do.
1) At first you needs instal some whrere hyperion server (install it from terminal command and copy to right directory config file), you can use Openelec or Raspbian. I tested on my Pi2 both system and for me its more faster Raspbian. After thats you hahe your owner Hyperion server who is conected to LED and power supply.
2) At second you needs hyperion client, you will open your KODI (for now its works only 15.2) and install via zip archiv special addon. Then you will open your addon hyperion and and replace IP adres by IP adrres of your Hyperion server and just klick add and activate. After thats you will have your Ambilight systém.
If you will needs more advantage i can help you wit this... i just made it yesterday any my wife and kids love it...

riddleace said:
Hi, its simple easy and i will try explain you what to do.
1) At first you needs instal some whrere hyperion server (install it from terminal command and copy to right directory config file), you can use Openelec or Raspbian. I tested on my Pi2 both system and for me its more faster Raspbian. After thats you hahe your owner Hyperion server who is conected to LED and power supply.
2) At second you needs hyperion client, you will open your KODI (for now its works only 15.2) and install via zip archiv special addon. Then you will open your addon hyperion and and replace IP adres by IP adrres of your Hyperion server and just klick add and activate. After thats you will have your Ambilight systém.
If you will needs more advantage i can help you wit this... i just made it yesterday any my wife and kids love it...
Click to expand...
Click to collapse
Wow that sounds awesome! I would love it if you could show me a tutorial or give me a good link to a forum thread where this is discussed. But I assume it will only work for kodi and not Netflix/YouTube,

chieco said:
Wow that sounds awesome! I would love it if you could show me a tutorial or give me a good link to a forum thread where this is discussed. But I assume it will only work for kodi and not Netflix/YouTube,
Click to expand...
Click to collapse
Yes its will work only in KODI, but in KODI you can install more plugin and i think Youtube there are already works, i tested yesterday when i watching video trailers. And here is tutorial on Netflix : https://addons.tvaddons.ag/show/script.program.androidnetflix/ so this will works too. I will makes to day some tutorial from the star to end with all the steps.

install hyperion on PI1/2
Hi this works for me…
Install Hyperion system
From https://www.raspberrypi.org/downloads/raspbian/ plz download Raspbian Jessie image and instar it on your SD card via program „Win32 Disk Imager“. When you will be done take your installed card to your PI and switch on power, linux Raspbian will take IP addres from your DHPC server. Then open Putty program and in host you will add IP addres your PI (you can see it at your router on section DHCP host) and open it in SSH mode. Login is „pi“ and password „raspberry“. When you will be loged to raspbian you must write this command:
1 )sudo raspi-config
And click enter, you will see configurate menu and there you will click on first option „Expand Filesystem“ and on option eight „Advanced Option“ and there you will click ok A6 and choice SPI and enable it.
For now you are ready to instar Hyperion…
In command line write this 4 command:
1)sudo apt-get update
2)wget -N raw.github.com/tvdzwan/hyperion/master/bin/install_hyperion.sh
3)chmod +x install_hyperion.sh
4)sudo ./install_hyperion.sh
after this install web aplikation for hyperon:
1)sudo apt-get install nginx php5-fpm
2)sudo nano /etc/nginx/sites-enabled/default (this will edit web configutation and there you will remove all line and add only this:
server {
listen 8888;
root /home/pi/www;
index index.php index.html index.htm;
location ~ \.php$ {
fastcgi_pass unix:/var/run/php5-fpm.sock;
fastcgi_index index.php;
include fastcgi_params;
}
}
Ok, next command will be :
1)git clone https://github.com/poljvd/hyperion-webapp.git /home/pi/www
then
2)sudo nano /etc/nginx/fastcgi_params
add this config this line on end:
fastcgi_param SCRIPT_FILENAME $request_filename;
After all make in command line this 2 command
1)sudo service nginx restart
2)sudo service php5-fpm restart
Now you can open your Hyperion server from your web pages :
http://ip-raspberrypis:8888
Configuring Hyperion
Things are starting to get colorful now.
To assign the correct color values to the LEDs , you have to inform Hyperion about the layout of your ambilight- system.
Thanks to the configuration tool this is very easy to do.
Download the most current version from the developers site:
Download: https://raw.github.com/tvdzwan/hypercon/master/deploy/HyperCon.jar
You may get a security message when downloading. Just ignore and download the file.
Info: n case you cant open the HyperCon.jar , you need to install Java on your computer.
Count your LEDs!
I counted my LEDs as shown in the following picture. After that I entered the values in the Hyperion config tool.
For some example setup you used this following settings in the config tool.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hardware-settings
Here you can set values like how many leds exist on each side, where the first led is, etc. I explained the settings in the screenshot.
Make sure that the LED count in the bottom right corner is correct, otherwise some LED’s won’t light up later.
Process-settings
Here you can set brightness, color intensity, color transition and other finetuning. More on this later.
I tried to explain everything as good as I could in the following screenshot:
External-settings
Here you just need the last 2 entries.
It’s important to change the path for “Effect Engine” to the shown value on the screenshot.
Create config- file
After you’ve done with config, just click on “Create Hyperion Configuration” in the bottom left corner” and save the created hyperion.config.json in the “/opt/hyperion/config” folder on your Pi.
Install program WinSCP and add your PI1/2 addres to this file manager
Move your hyperion created config hyperion.config.json to “/opt/hyperion/config”
Now just reboot you raspberry so it can load the config file.
and this is all... for now
Now just reboot you raspberry so it can load the config file.
Install Hyperion addon in KODI by this manual..:
http://raspberry-at-home.com/control-lightberry-from-kodixbmc-htpc-over-network/
And this is manual for install LED on your TV
http://awesomepi.com/diy-breath-taking-ambilight-for-your-own-tv-raspberry-pi-2-tutorial-part-1/
and you will be done, but br aware on 1m ws2801 you will needs 8W power supply (this is max use on 1m led in strip), so in 5m you will needs min. 40W but i think optimum will be 50W because of power efectivnes on power supply like in PC.

https://drive.google.com/file/d/0B_iPX_d720-pSnBpQjRVWFhSSmc/view?usp=sharing
test video

In new version of KODI 16 and alfa 17 build, just disabled Mediacore (Surface) in hardware acceleration.

riddleace said:
In new version of KODI 16 and alfa 17 build, just disabled Mediacore (Surface) in hardware acceleration.
Click to expand...
Click to collapse
Brilliant walk-through - much appreciated
Does this mean that we can only choose between Ambilight or Hardware acceleration though?
If that is the case what needs to change to make the two compatible?
Thanks!

zenji2016 said:
Brilliant walk-through - much appreciated
Does this mean that we can only choose between Ambilight or Hardware acceleration though?
If that is the case what needs to change to make the two compatible?
Thanks!
Click to expand...
Click to collapse
I thinks its bug in KODI, they needs more time for reserch it, but with this disabling hadware accelaration you will got bether video quality image.

riddleace said:
Hi, its simple easy and i will try explain you what to do.
1) At first you needs instal some whrere hyperion server (install it from terminal command and copy to right directory config file), you can use Openelec or Raspbian. I tested on my Pi2 both system and for me its more faster Raspbian. After thats you hahe your owner Hyperion server who is conected to LED and power supply.
2) At second you needs hyperion client, you will open your KODI (for now its works only 15.2) and install via zip archiv special addon. Then you will open your addon hyperion and and replace IP adres by IP adrres of your Hyperion server and just klick add and activate. After thats you will have your Ambilight systém.
If you will needs more advantage i can help you wit this... i just made it yesterday any my wife and kids love it...
Click to expand...
Click to collapse
Did you mean this add on? I set up my ambilight clone and would love to use it with the shield.

I think i use this addon from here: https://github.com/brindosch/script.service.hyperionBETA but if you will wait i will upload this addon some where when i will be at home from work.

riddleace said:
I think i use this addon from here: https://github.com/brindosch/script.service.hyperionBETA but if you will wait i will upload this addon some where when i will be at home from work.
Click to expand...
Click to collapse
Thanks buddy got it to work in the meantime. I wonder what's the difference between the one i mentioned u urs... one says master the other beta. very happy that it works with the shield. got concerned for a minute after reading the thread and and you mentioning it only works on 15.2 didn't know if u mean that for the server or client.... any way thanks again. one last question do u know a good way to calibrate the colors? mine are really wrong...

Database Users

welcome