Related
Ok, so following on from the MeeGo thread, I have Ubuntu booting on the Nexus S using the same method and same kernel.
The Ubuntu image used is the HD2 Ubuntu image (v 0.3), loaded from a file on the internal memory (again, no flashing required - you can thank me later).
The touchscreen isn't yet working, but that's my kernel at fault. Will fix that with the MeeGo stuff.
If you want to try this yourself, first grab yourself a copy of Ubuntu for HD2, and take just the rootfs.ext2 file and drag it to your Nexus S (put it in a folder called 'ubuntu' - lowercase is important!).
Then use fastboot to boot the following image (or flash it to recovery partition if you're daring and know how dangerous that can be):
http://dl.dropbox.com/u/8657343/bootUbuntu.img
You will need to do one minor edit once the device is booted; you will see the screen output is very weird; ADB push the following file to /etc/X11/xorg.conf, and then reboot Ubuntu:
http://dl.dropbox.com/u/8657343/xorg.conf
If you're in any way interested, please click the thanks button! Otherwise, enjoy!
nice!
the next thing we'll need after getting the touch screen working
is to have a calling app daemon, and make sure internet works on both 3G and WiFi
nice, look same at Ubuntu Netbook Edition
What about Galaxy S?
Njcki said:
What about Galaxy S?
Click to expand...
Click to collapse
In theory the same stuff should work; I don't have a Galaxy S to test on or I'd try it. I don't know anything about the Galaxy S' bootloader, or how much the kernel would differ (I'm guessing not at all, since this is a stock Samsung kernel from the Android kernel source)
I did an article on my site http://www.android-ita.com/dev-port-di-ubuntu-sul-nexus-s/
Maybe some italian devs, will help you
Thanks for this, gonna have a play now
Why is it dangerous to flash the boot image to recovery? Isn't fastboot lower level than recovery, or have I got that wrong?
nice, thanks. trying this as soon as my wife gets off my phone.
Oh my god.. You are awesome good sir. Will give it a run when touch is up and running!
I'd love it to be run from Android....i dont want it natively, just to test it...booting for example from an android app
I would love to know if this will work on Epic 4G. I'm going to give it a shot to see what happens.
Great job
Could you give us the sources of your kernel ? Is it patched ?
Tyruiop said:
Great job
Could you give us the sources of your kernel ? Is it patched ?
Click to expand...
Click to collapse
There are no changes to the kernel at all so far. I changed the config file to enable VTs, that's it.
Ok, thank you, I'll try to build one myself
can this method be used to install android 2.3 on a phone running android 2.1,
especilly in the case when upgrading is difficult because of kernel and locked bootloader (like motorola devices) ? excuse me if it is a silly question, i'm not a coder.
would it be possible to make an app that re-boots into fastboot and runs the fastboot command. since we dont always have a comp available to run fasboot which makes this useless if your not at home, or have a laptop (in which case you dont need ubuntu on a phone)
works on Nexus One right now ?
--> ok I'm trying
It blocks on X screen of my nexus one.. before the classic bootanimation.zip
Someone have any idea about that ?
Ok, so I've got wifi working . Here is my solution. A little bit crappy but... hey... it's a start ! Also, I tried compiling the kernel with the module built in and it wont boot, and I don't know why ?
Howto get wifi :
1) Boot Ubuntu following stroughtonsmith indications
2) Download http://tyruiop.org/~tyruiop/wifi_nexuss_ubuntu.tar.bz2
3) push the vendor directory at the root. The path must remain (/vendor/firmware etc...) and the bcm4329.ko file wherever you want.
4) reboot under ubuntu
5) *optional, only if ifconfig -a doesn't show eth0* type insmod /path/to/bcm4329.ko
6) Type "ifconfig -a". An eth0 interface should appear. It's wireless. You can configure it with wpa_supplicant without a problem .
Uhm.. with Nexus One, Ubuntu blocks on X SCREEN (before the classic bootanimation).. Maybe something that I do is wrong ?
- Download HD2 Ubuntu
- mkdir ubuntu/
- put in ubuntu/ the fs on the archive I downloader
- put ubuntu/ in the SDCARD
- adb reboot bootloader
- fastboot boot bootUbuntu.img
Is it correct ?
PLEASE MAKE SURE YOU READ EACH STEP IN ITS ENTIRETY BEFORE DOING IT.
Table of Contents:
--1.0-Installing ADB
----1.1 Downloading the SDK
----1.2 Installing and Extracting the SDK
----1.3 Installing the Necessary USB Drivers
----1.4 Loading up ADB and Detecting Devices
--2.0 Installing GAPPS, The Newest Vending.APK (Market) or any APK for that matter.
----2.1 Installing the newest Vending APK (A.K.A Market Place)
----2.2 Installing the latest Google Applications (GAPPS)
--3.0 Help
Click to expand...
Click to collapse
Hey guys, I have noticed quite a few people have been having some problems with installing ADB and Google Applications on their newly loaded ROMs that don't have the GAPPS pre-installed. Well I am going to make this post to try and help some of those that are having a little bit of trouble. So please bare with me, as this is my first "Tutorial" post here at XDA. If you see any errors with this tutorial please let me know so I can make the appropriate changes ^_^
STEP ONE: Installing ADB
First thing is first, the method in which I will be showing you how to install GAPPS will be using ADB. If you don't know what Android Debug Bridge (adb) is it is simply a versatile tool lets you manage the state of your Android device. If you already know what ADB is and already have it installed feel free to skip to step 2.
-The Prerequisites for ADB-
1.1 Downloading the SDK
In order to gain access to using the ADB tool you need to first download the android SDK.
If you do NOT plan on developing any software for the AOSP you can skip to step 1.3 and download and install IOMonsters Easy ADB USB Driver installation. It contains a STRIPPED down version of the SDK which include the necessary components for using ADB. However, if you want to be on the safe side and download the whole sdk keep reading
The newest SDK can be found here:
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
1.2 Installing and Extracting the SDK
For you windows users out there after you have downloaded the SDK for windows (preferably the .EXE) you are going to want to change the installation location to "C:\android-sdk-windows" or the paths you need to enter below will be different.
Now, once you have verified that the C:\android-sdk-windows folder exists you need to run the SDK Manager.exe - If you have any trouble with the SDK Manager downloading files try clicking Settings and choose "Force https:// sources to be fetched"
1.3 Installing the Necessary USB Drivers
NOTE: If you plan on NEVER using ADB over USB you can install the WirelessADB widget Go to market, and search for ADB Wireless. Install the app and run it.
Now that you have the SDK downloaded and extracted it is time to Patch the USB Driver files. Thank GOD for IOMonsters Easy USB (DRIVER ONLY) Pack. To use this tool you will need to download it. To do so you can choose from the following links:
http://legacyschool.us.to/nookdev/nook-usb-installer.rar
http://r00tyou.com/android/tools/nook_usb_driver.zip
Click to expand...
Click to collapse
I have noticed that for some people simply executing the "install.exe" from the USB drivers folder does not work. For me I had to run the install.exe and when that was finished I ran the "DPInst64.exe" NOTE: THE ONLY REASON I RAN THE DPInst64.exe WAS BECAUSE I AM USING A 64 BIT OPERATING SYSTEM. IF YOU ARE RUNNING A 32 BIT OPERATING SYSTEM PLEASE USE "DPInst.exe"
For those of you who do NOT want to download the ENTIRE Android SDK please refer to IOMonsters thread about installing and using the Easy ADB Drivers and SDK Tool:
http://forum.xda-developers.com/showthread.php?t=910008
Click to expand...
Click to collapse
1.4 Loading up ADB and Detecting Devices
Now that you have ADB up and running, and your computer is recognizing your nook through USB (or ADBWireless) it is time to load up the ADB tool and see if we can get your computer to find your device. To do so, please make sure your device is plugged into the computer via the proper USB cable. After that you are going to need to open the command prompt. To do so, click start and run, or for windows vista and up you click start and in the search bar type "cmd" and hit enter.
Once the windows console is opened you are going to need to type:
cd C:\android-sdk-windows\platform-tools
Click to expand...
Click to collapse
(assuming you installed the android-sdk in the root of C: - If not just replace it with the path of your sdk folder)
After you have successfully changed to the platform-tools directory proceed by issuing the following command:
adb devices
Click to expand...
Click to collapse
If you see the following output you are in good shape:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[Your device is listed here]
Click to expand...
Click to collapse
If not, please make sure you have your device plugged in, and the USB Drivers are functioning. If you are still at a loss at this step, feel free to PM me and I will assist you the best I can.
2.0 Installing GAPPS, The Newest Vending.APK (Market) or any APK for that matter.
This process of installing can be used for any APK you have on your computer and you want pushed over to your device.
2.1 Installing the newest Vending APK (A.K.A Market Place)
If all you want is the market, you can download the newest market APK from my webserver.
http://www.r00tyou.com/android/tools/Vending(new).apk
Click to expand...
Click to collapse
To push it to the device simple connect the device to your computer using ADB and type the following in the console:
adb devices
adb install \path\to\the\downloaded\apk\Vending(new).apk
Click to expand...
Click to collapse
Wait for it to successfully transfer over and install.
Viola, you have the newest market APK.
2.2 Installing the latest Google Applications (GAPPS)
For those of you who want the newest GAPPS, you can download the file from the cyanogen website and push over the whole gapps bundle.
To do this, simply download the latest GAPPS from here:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version#Google_Apps
Click to expand...
Click to collapse
Again, using ADB type the following commands:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [the path to your SDK tools folder]\system system/
adb reboot
Click to expand...
Click to collapse
The console will show the progress of what apps are being transferred over and installed. Once it is done rebooting it will prompt you for logging in to your Google account to setup your device. You can simply skip this (Tapping in each corner of the screen starting from the top left going clockwise) or you can proceed with the setup process.
Hope that helps
3.0 Help
If you have encountered an error while following this tutorial PLEASE PM me and I will list some common errors/problems here and make the necessary changes to this tutorial.
Problems/Solutions:
DISCLAIMER: I AM IN NO WAY RESPONSIBLE FOR ANYTHING THAT HAPPENS AS A RESULT OF FOLLOWING THESE INSTRUCTIONS. I ASSUME THAT EVERYONE READING THIS HAS SOME SORT OF KNOWLEDGE WITH HANDLING THIS DELICATE PROCESS.
will be looking this over later.
Thank you
Your welcome Please post some feed back and anything you run into while following the steps ^_^
Reneg4d3 said:
2.2 Installing the latest Google Applications (GAPPS)
For those of you who want the newest GAPPS, you can download the file from the cyanogen website and push over the whole gapps bundle.
To do this, simply download the latest GAPPS from here:
http://wiki.cyanogenmod.com/index.ph...on#Google_Apps
Again, using ADB type the following commands:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push [the path to your SDK tools folder]\system system/
adb reboot
The console will show the progress of what apps are being transferred over and installed. Once it is done rebooting it will prompt you for logging in to your Google account to setup your device. You can simply skip this (Tapping in each corner of the screen starting from the top left going clockwise) or you can proceed with the setup process.
Hope that helps
Click to expand...
Click to collapse
WRT the installation of latest gapps, can we use (gingerbread based) CM7 gapps with (eclair based) rooted stock?
met67 said:
WRT the installation of latest gapps, can we use (gingerbread based) CM7 gapps with (eclair based) rooted stock?
Click to expand...
Click to collapse
It might be backwards compatible, that I am not sure of. However, I tried using the eclair apps on the gingerbread ROM and it put me in a boot loop. I am not sure if that was just coincidence that I just so happened to push the gapps over or not, but when I reinstalled and pushed the gingerbread gapps over I did not get put in a boot loop, the boot loop consisted of the device booting up, it hit the screen where you tap the droid, then it would flash, and the CM7 loading screen would appear. It would continue to do this until I re-flashed the device.
Excellent post. All the steps seemed pretty straight forward. I couldn't install the vendor API, but at this point I'm thinking that something is wrong with my permission set. I'll go over the list again and see what I may have missed.
If you are stuck on anything please feel free to let me know. It is also a possibility that some of the steps are incorrect as I typed them out from memory
nookie froyo emmc
i'm not familiar with adb other than the method i rooted my evo with back in august so now i'm trying it with your guide (THANKS!!!)
after failing to install every version of vending.apk i have access to with root explorer, even putting marketupdater.apk in /system/apps.
It will open for a split second and then disappear so im giving up on the root explorer method. i attempted to adb install the version you have listed (the vending.apk single) and i get INSTALL_FAILED_ALREADY_EXISTS
so i removed the vending.apk and marketupdater.apk from /system/apps and then removed vending-1.apk from data/app (dunno how it got there but i found it and removed it). i try installing with adb again, i get INSTALL_FAILED_MISSING_SHARED_LIBRARY. did i remove an important file? i am now trying to install the gapps but am unsure exactly where i should put my gapps.zip and if i should unzip it first?
the link for the gapps you gave didnt show which version to download for nook color so i grabbed the hdpi for cm6, correct?
Edit, found my problem, i was trying to install wrong market, i grabbed the market i will link below from Here and then i adb install it and it installed
hmm, keeps FC. lemme wipe and try again
Ok, it appears I didn't compensate for a small variable when writting the tutorial. IF you want to install ONLY the new vendor.apk DO NOT push the whole GAPPS bundle over, simply download the vendor.apk from my website located here:
http://www.r00tyou.com/android/tools/Vending(new).apk
And push the Vendor(new).apk over by itself after RENAMING the old vendor.apk to something like vendor.apk.old then rename Vendor(new).apk to vendor.apk and run the installation.
If you need more help, or are still having problems feel free to send me a pm or post here.
Sent from my Droid using Tapatalk
mmmm, same FC to me, i can't restore the old market, via adb or via root explorer... eclair default rom here...
Can't the new market apk just be side loaded?
C:\Users\Kris>adb install C:\users\kris\downloads\vending(new).apk
2036 KB/s (2123059 bytes in 1.018s)
pkg: /data/local/tmp/vending(new).apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
What's this about?
thereddog said:
C:\Users\Kris>adb install C:\users\kris\downloads\vending(new).apk
2036 KB/s (2123059 bytes in 1.018s)
pkg: /data/local/tmp/vending(new).apk
Failure [INSTALL_FAILED_MISSING_SHARED_LIBRARY]
What's this about?
Click to expand...
Click to collapse
Nevermind.. I just pushed gapps and got the market that way
Mariohyeah said:
mmmm, same FC to me, i can't restore the old market, via adb or via root explorer... eclair default rom here...
Click to expand...
Click to collapse
So what is the EXACT process that you are doing? And what is causing the FC? It's weird because I just retried this and I got it working :\
Does this tutorial work for DeeperBlue's HC 3.0 on microSD cards?
Hi,
Does this tutorial work if I have DeeperBlue's HC 3.0 preview v4 on a microSD card on NC? Or does it only work on internally rooted NC's? I'm encountering at the android market the error message "There are no android phones associated with this account. Please sign in with a different account". Have tried various things but not the ADB installation thing. I did download and install the android.vending_2.2.6.apk but still getting same message when trying to install something from the android market. Do I need ADB or could it be some wrong setting the "My Market Account" or "My Account"? Thanks in advance for any help!
Randy
Does this tutorial work for DeeperBlue's HC 3.0 on microSD cards?
Somehow my post repeated. Sorry.
Thank you so much for the Iomonsters! Finally after 2 days of trying it fixed my adb.
met67 said:
WRT the installation of latest gapps, can we use (gingerbread based) CM7 gapps with (eclair based) rooted stock?
Click to expand...
Click to collapse
Would like to know too as the CM7 version is not working for me on my Nook Simple Touch, will try CM6....
i root my nook touch and can't access market and have not any file managers (installed my devices);i follow steps &
i installed usb-driver but
software can't recognize device;
and this error
please help me
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[Your device is listed here]
showed nothing
Man, I just want to say, You are awesome! Nice tutorial it worked from the first time!
BACKTOP v0.00001
Click to expand...
Click to collapse
Alright, so this is a guide to finally get the backtrack 5 software running inside of webtop. It uses chroot and xterm to allow full access to the software contained within the backtrack 5 arm image.
Prerequisites:
CWM Installed:
For all version: http://forum.xda-developers.com/showthread.php?t=1138541
WebTopMOD installed:
For 2.3.4 go here: http://forum.xda-developers.com/showthread.php?t=1169457
For 1.8.3 go here: http://forum.xda-developers.com/showthread.php?t=1093790
You do not need to download the Debian disk image. Will we be using the backtrack disk image instead.
BusyBox Installed in /system/bin:
Downloaded "BusyBox Installer" from the app store.
BE SURE TO INSTALL IN /SYSTEM/BIN!
Click to expand...
Click to collapse
The Goods:
BackTop.zip:
Download and un-zip the attached files into /sdcard/bt
BackTop.zip
BackTrack 5 ARM Image:
PART 1 : Download Link : http://bit.ly/p1BT5
PART 2 : Download Link : http://bit.ly/BT5p2
PART 3 : Download Link : http://bit.ly/BT5p3
These download links are from the xperia backtrack project and where I took inspiration to get it working in webtop. After using 7z to unarchive just place bt.img in the /sdcard/bt folder. The archives other contents can be safely ignored.
Click to expand...
Click to collapse
What you should have by now:
WebTOPMOD for Atrix.
BusyBox Installed in /system/bin.
Downloaded scripts placed in the /sdcard/bt folder.
Downloaded bt.img placed in the /sdcard/bt folder.
Click to expand...
Click to collapse
Give it a go:
Step 0: Connect the phone to display/lapdock. Run webtop and wait for it to boot.
Step 1: Open LXTerminal from the dock and type "cd /sdcard/bt"
Step 2: To run BackTop type "sudo bash backtop"
You should be presented with a white xterm screen. You can now use all the utilities built into backtrack 5 with ease. You can even run the gnome desktop environment! (More on that bellow)
Click to expand...
Click to collapse
Running Gnome:
You first need to kill off all the webtop crap do this by typing the following in xterm.
"ps ax|grep awn|awk '{print $1}'|xargs kill"
"ps ax|grep panel|awk '{print $1}'|xargs kill"
Then start gnome by typing "gnome-session" in xterm.
Click to expand...
Click to collapse
Accessing sdcards:
You'll need to make two directories inside of backtrack /sdcard and /sdcard-ext to do this type:
"sudo mkdir /sdcard"
"sudo mkdir /sdcard-etc"
Once you've done this simply reboot your phone and restart BackTop.
Click to expand...
Click to collapse
Known issues:
ettercap causes network connectivity inside of webtop to fail.
If something does go terribly wrong you can always force quit backtop with the following command:
"sudo bash /sdcard/bt/forcekillbt"
Click to expand...
Click to collapse
Cool stuff, I'll definitely check this out. Moved to development.
mate I don't have webtop but as a network engineer I'm giving this a big thumbs up, super cool to have a pen testing suite in your phone!!!
reserved #10Chars
It might just be me but do your links work? Specifically the http://bit/ly ....etc. thanks
Sent from my MB860 using XDA App
edit: had a smart attck and everything is tip top...well done sir...thx!!
that is the most metal thing ever
I'd prefer it actually dual boot on my phone for hac..I mean testing on the go xD
What will this one do that the others don't?
Cheers
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
If you don't know what BackTrack is then you don't need it.
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
its a pen testing Linux suit. its essentially Linux loaded up with hacking tools meant for testing networks to prevent hacking or "penetration". hack your own network. discover the vulnerabilities. and patch them. - to put it simply
This is amazing. Thanks.
7z issue with the bt.7z
Hum... I might be doing something wrong but I am not able to uncompress the 3 volumes posted in the links... I was able to download them all but the only one who actually I can uncompress is the first one and it generate a file bt.7z that I am also unable to uncompress... I am getting the following msg when I try to 7unzip them:
"cannot open file 'x:\xx\xx\bt.7z.002' as archive"
Should I join them all into one then use 7zip?
Forget it I just found it out by myself... is using a program to join them all into one then Unzip it.
My dream come true .............. i assume that we can run kismet and metasploit framework ?!
What kernel and rom were you able to make this run well with as i am having really bad reboots after i undock the phone from the lapdock as i am running faux123 kernel and cherry crust v3.
webtop when connected to hdmi not doing anything...
I was trying to use this backtrack distro on my AT&T Atrix and I must admit that I am a kind of noob on this ... I wasn't seeing big advantage until now that we have bt to use instead of the stock version...
I have no Lapdock so I am using Ronaldo_9 CWM version to run Webtop on HDMI in my GB 2.3.4 ( 4.5.91 from Kenneth Penn ). It was working til I followed these instructions ...
Well a little bit of what I did:
1- Downloaded the WebTopMOD from Joe Ferreira v2 to install with CWM.
2- Got also BusyBox installed through the BusyBox Installer over my /system/bin
3- Downloaed (even knowing it's not needed) the Debian disk from Joe Ferreira link (to install webtopmod).
4- Downloaded the BlackTrack 5 image from the links on the first post
5- Downloaded the BackTop.zip from the first post
6- Created the /sdcard/bt folder and put only the bt.img and forcekillbt and backtop files from Backtop.zip file onto it...
7- Plugged in my HDMI cable over my tv (yes I have no lapdock)
8- The Webtop option pop's up and when I selected it.....
Nothing happened... not even an error msg or stuff... the only thing still working is EC... but webtop none.... Does anyone of you have any clue or hint of what can I do about it?
EDIT: Got it working... it was because of the broken V2 WebtopMOD so I flashed the V1 and everything went fine.... Thank you all for not helping it made me a better researcher
I think I just wet myself I've been waiting for someone to come up with this since they started the ARM archticture and ported it to the XOOM tablet
Sent from my MB860 using XDA Premium App
The built in wifi doesn't support packet injection does it?
baumerman said:
The built in wifi doesn't support packet injection does it?
Click to expand...
Click to collapse
It doesnt....
Sent from my MB860 using XDA App
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
kholk said:
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
Click to expand...
Click to collapse
That would be awesome... just amazing how u dealing with a lot of stuffs simultaneously ....... tyvm for visiting this thread its almost dead...
Doing a simple (means not a complex one) research at Google it seens that there's no much of Monitor mode for android cell phones so far... not sure why if nobody cares or if it's not possible... but u got skill enough to give the last word
Hope to hear something soon...
I wish there was more development for this, and +1 for packet injection
gzrecoil said:
I wish there was more development for this, and +1 for packet injection
Click to expand...
Click to collapse
There is monitor mode for iPhone and itouch... not sure the reason why not for android :-(
Sent from my MB860 using XDA App
So, I've been doing some Android development tutorials, as I have almost no experience in any sort of coding. I'm working in Ubuntu 11.10 with android-sdk-linux, Eclipse IDE, & java version 1.6
Things are going ok, but...
I tried to export a signed apk of my application project from Eclipse yesterday, and when I try to install it on my D3 I get this error:
HTML:
Error Parsing Package
What am I doing wrong?
thanks in advance...
lunacie said:
So, I've been doing some Android development tutorials, as I have almost no experience in any sort of coding. I'm working in Ubuntu 11.10 with android-sdk-linux, Eclipse IDE, & java version 1.6
Things are going ok, but...
I tried to export a signed apk of my application project from Eclipse yesterday, and when I try to install it on my D3 I get this error:
HTML:
Error Parsing Package
What am I doing wrong?
thanks in advance...
Click to expand...
Click to collapse
Sorry bro, I have no idea. You might get more help Android Development and Hacking or more specifically Android Software Development which is a subforum of the first link. Sorry I personally can't help you out more than that, wish I could.
If your device is recognized as a development device, you should be able to just hit the 'Run' button and it should compile your app, install it to the device and automatically launch it. Your device needs to have USB debugging turned on and you need to have the ADB driver installed (need to get it from Motorola if this is a Moto device, it won't install automatically like the rest of the storage drivers).
My Droid3 shows up as ???????? in adb. I was exporting a signed apk to install because I can't get the device to recognize. Am I missing a configuration of some kind? I'm guessing there's some kind of vendor code or something that I need for ADB to work properly with my phone?
tnx
EDIT: think I figured it out. it's the udev rules, looks like i'm on the right track....
EDIT 2: Got it! Thanks for the heads up.
Al Credits Goes TO Perceval from Hyrule
Perceval from Hyrule said:
** Currently writing this, please wait !
Hello there,
here is a new tutorial I'm sure you'll like. As usual it took me LOTS of work to get all info and make this to work, so now I share it with you and show how to run custom ROMs within Android SDK Emulator.
Please note it's mainly for XPERIA X10, but process is the same for other Android-powered devices. It will show you the process for Linux.
1. Download the latest Android SDK.
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
3. Go to the SDK folder, then in the folder Tools/. Double-click on Android and choose Run.
4. Go to Available packages, and choose to install (choose at your will !)
Android SDK Tools, revision 8
Android SDK Platform-tools, revision 1
SDK Platform Android {VERSION(S) YOU WANT} (!) You need at least one Platform. For X10, you can download 1.6, 2.1. You can also add 2.2, 2.3.
Once it's done, close the window.
5. Download Xperia X10 add-on for SDK. (?) Read the PDF add-on guide, it is helpful !
Copy the folder (from the archive) XPERIA-X10_r1 inside the folder add-ons of your Android SDK folder ({androidsdk}/add-ons/).
6. Run terminal, go to your Android SDK folder, then in tools folder, and run
Code:
./android list target
.
Note the id number of the Android you want to develop (ie for me, Android 2.3 is
Code:
id: 3 or "android-9"
). (?) You might also want to note the name ("android-X") as it might be useful later.
7. Now, create AVD (a profile for emulator). Usual command (assuming you are INSIDE the /tools/ folder !) is
Code:
android create avd -n NAMEYOUWANT -t {ID}
So, for us, it will be
Code:
./android create avd -n myx10 -t 3
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 160 (correct if I'm wrong ?)
DPad support : no (?)
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 66 (?)
Audio playback : yes
Trackball : no (?)
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 32
RAM : 280
GSM Modem : yes
(?) I recommend you to create one profile for each Android version you want to run (so : you just have to change the ID, and create same profile). If you don't, you won't be able to run custom ROMs using other versions of Android (ie your AVD profile is 2.3 and you run a 2.1 custom ROM).
9. Done ! Take your custom ROM (downloaded, compiled... In this case, files are in {YourAndroidRepoFolder}/out/target/product/generic/. It comes with about 3 files, including a file called system.img. Copy this file into the folder (hidden) .android/myx10{In fact, the name you've chosen earlier "NAMEYOUWANT"}.avd/
10. Run terminal, go to Android SDK folder/tools/ (if you didn't close your current terminal, you're already in and run this command to run emulator WITH your custom ROM :
Code:
./emulator -avd myx10{again the "NAMEYOUWANT" you've chosen before}
Wait and enjoy !
(?) First boot is long - it's NORMAL. Just like on a real device, the OS will be cached and will work faster and faster.
Click to expand...
Click to collapse
Can you please make a video tutorial? I don't have terminal i use Windows
terminal on windows
TodorSRB said:
Can you please make a video tutorial? I don't have terminal i use Windows
Click to expand...
Click to collapse
in windows 7, press the start button, type in cmd, hit enter and viola! you are in a terminal
Great tutorial but the point that confuses me is: If we're creating AVD why do we need and where/how do we used device add-on for SDK?
Thanks
LastStandingDroid said:
Al Credits Goes TO Perceval from Hyrule
Click to expand...
Click to collapse
thanks
Thanks for this tutorial! Thanks +1 for you! :good:
there is a new version of ADT out since this tutorial was written. I am able to run a virtual machine but how can I get a custom rom on it? Please help.
thanks
mrdoc151 said:
there is a new version of ADT out since this tutorial was written. I am able to run a virtual machine but how can I get a custom rom on it? Please help.
thanks
Click to expand...
Click to collapse
You need to download more than one api, it creates the directory for addons and continue from there :beer:
thanks for the tutorial
A question, ¿how to compile a rom? :S
jomigp01 said:
thanks for the tutorial
A question, ¿how to compile a rom? :S
Click to expand...
Click to collapse
A Linux environment is best, and there are a million tutorials all over xda:beer:
Slithering from the nether regions of a twisted mind and tarnished soul
jacobmacek said:
in windows 7, press the start button, type in cmd, hit enter and viola! you are in a terminal
Click to expand...
Click to collapse
That is not terminal. If you need terminal in windows download CYGWIN. http://www.redhat.com/services/custom/cygwin/
Silly post *Removed*
I want to make it to this process for one x. in addition to those for xperia Where can I find one x
I have a flashable zip of the custom rom i need to test. Is there any way i could use that here?
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
* I can't see any archive.
TodorSRB said:
Can you please make a video tutorial? I don't have terminal i use Windows
Click to expand...
Click to collapse
Download cygwin from HERE
It should help you
---------- Post added at 06:34 AM ---------- Previous post was at 06:29 AM ----------
OzoGaming said:
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
* I can't see any archive.
Click to expand...
Click to collapse
Here the archive means the flashable custom rom :laugh:
Need a windows tutorial.....
This tutorial looks like for linux......please make a windows version tutorial
Black Screen here, any suggestion?
I saw that the ramdisk.img is also needed, but I dont know how to generate it
You can use fastboot / ADB to pull ramdisk.img for the device brand model you are trying to cook for. Tutorial on youtube- I have to watch it again guy is not a natural instructor - oh well grateful for the seeds and the few Linux tutorials: I want to try setup a profile for Doogee Mix due to little support for it. Think its worthy of a few custom options. [email protected] 'LastStandingDroid" Thank U - I was looking for how to unpack stockmix.rar to fastboot flash for a restore, Can I use those same basic files to create a skeleton profile for custom rom? I'm just frankensteining
Here the archive means the flashable custom rom :laugh:
Click to expand...
Click to collapse
in my "archive" i have only md5 files no folders pls help