Hi, I am using Ubuntu Lucid Lynx (10.04) and having got my Nexus one yesterday from a grey market (I live in Thailand so that's the only easy way). It was supposed to be factory new but I found it was loaded with the amon_RA-1.5.9 stack, and a cyanogen 2.1 android version. I felt like I had to upgrade all this.
Thanks to this forum, here is the way to update to froyo and update to amon_RA 1.7.0 on Ubuntu amd64 (versions lower than 10.04 should be similar):
Download Froyo
I used this /showthread.php?t=686631 XDA Post (sorry, I am new and can't post links.... or dunno how to do for inside xda links)
Update Froyo
I followed the tutorial:
- rename the file 'update-nexusone-FRF50-signed.zip' to 'update.zip' (make sure no quote and no '.zip.zip' issue occurs, but if you are on Linux 64 bits I trust you know what you're doing so far)
- copy to the sdcard root folder (use the nexus one USB cable then slide the top panel on the screen where it shows the USB symbol, then select the option to mount the SD card as storage, or use a sdcard reader/writer )
- disconnect USB if connected, have the sd card in the phone, reboot on bootloader: hold the trackball while power on.
- Select recovery
- flash from sdcard and follow instructions.
Note: search this forum for more details on this part
Build 'fastboot'
- I actually created an Ubuntu 10.04 amd64 in VirtualBox in order to have an uncorrupted environment. I just ran the standard updates after installation
- Download from 'source DOT android DOT com/source/download.html' source. Follow EXACTLY what they say on the Linux for 64 bits EXCEPT that now you can use Java 6 (if you spend time adding the JAUNTY multiverse repository and install sun-1.5.0-jre the SDK build will fail immediately telling you to use Java 1.6.0...)
- after you run the 'make' command, wait for a while.... depending on your RAM/CPU, then open another terminal and check if the 'fastboot' binary is already built (<repo>/out/host/linux-x86/bin/fastboot). If so, you can CTRL+C the build (except if you really want it)
- copy fastboot to a location in your PATH
- create a file (as root or 'sudo' it) /etc/udev/rules.d/51-android.rules:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="18d1", ATTRS{idProduct}=="xxxx", MODE="0666", OWNER="username"
SUBSYSTEM=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="yyyy", MODE="0666", OWNER="username"
where:
xxxx: is the value returned by the command 'lsusb | grep 18d1', after the '18d1:xxxx' when the phone is turned on in normal mode
yyyy: is the value returned by the command 'lsusb | grep 0bb4', after the '0bb4:yyyy' when the phone is turned on in fastboot/bootloader mode
username: is your login name
- save the file
- run 'sudo service udev restart'
- restart the phone in fastboot (hold the trackball while turning on the phone)
- run 'fastboot devices' and it should show something like:
HTxCxxxxxxxxx fastboot
Click to expand...
Click to collapse
Update amon_RA
- Now you just follow showthread.php?t=611829 from amon_RA himself
I attach my 'fastboot' version if you prefer the shortcut. Do it at your own risk, I provide no guaranty. It worked on my machine, that's all.
im running the same thing as u. i just downloaded the sdk and it came with fastboot.
samir5421 said:
im running the same thing as u. i just downloaded the sdk and it came with fastboot.
Click to expand...
Click to collapse
From the developer.android.com/sdk/index.html page, 'fastboot' isn't in the 'android-sdk_r06-linux_86.tgz'
What package did you download and from where?
Thanks a lot man, now I can fasboot with my ubuntu 64!!!!
Thanks for the file, fastboot was removed from last Android SDK (r08).
Related
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
joshw0000 said:
I recently rooted my Eris and I'm unable to flash a custom recovery because I can't get the USB drivers to update with those found in the SDK files. When I try to update the drivers Windows tells me that I have the most up to date drivers installed. It's because of this I cannot see my phone in the command prompt and can't get the custom recovery to work.
Has anyone tried putting the recovery files on their SD and using a terminal emulator?
Any ideas on updating the USB drivers?
If I flashed a custom Rom (as risky as that is without a recovery) could I then use nandroid or some other recovery? Or would I still need to use SDK?
Click to expand...
Click to collapse
download htc sync that should fix ur problem , it did for me
Yes HTC sync updated mine as soon as your phone is acknowledged by HTC sync it should update your usb drivers
FYI HTC sync did NOT work for me on Windows 7. I had to do some pretty annoying stuff to stop windows from installing the regular drivers automatically. If HTC sync doesn't work I can try to help.
If HTC Sync doesn't help, try the following steps.
1. Unplug your Eris from the PC
2. Open Device Manager and delete the Android device
3. Reboot your PC
4. Once in Windows, connect your Eris
5. The drivers should load automatically, if not point it to the SDK drivers folder
Good luck!
Any more ideas
First I tried downloading HTC Sync on my laptop (running Vista) and that didn't do it. Then I deleted the drivers and tried to manually download them back with the ones in the USB folder of SDK and still it wouldn't work.
So I started over and downloaded SDK and Java to my pc (Windows 7) and tried to update the drivers with the ones found in SDK and it wouldn't let me. So I deleted the drivers, unplugged my phone, and plugged it back up. Before I could attempt to direct it to download the intended USB drivers, Windows 7 had already updated with the drivers of it's choice. I can't win for losing.
If you don't mind using one of those "Live" Linux CDs, you could install the recovery using fastboot.
No need to install anything on the PC, and no drivers are needed for Linux, no SDK, no Java, no adb; just make sure to run fastboot as root.
The downloads of fastboot and the Amon_RA recovery are small, so they will easily fit in /tmp.
bftb0
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
When you have your phone plugges in do you have it set to "charge" or "sync"? I know all the how to's say yo have it set to charge only but the inly way my computer ever finds my phone is if it us set to sync.
-------------------------------------
Sent via the XDA Tapatalk App
I set it to charge. I was finally able to install the correct driver. I selected a Google driver from the list it gave me (which my computer did not like) then went back and updated the drivers with those found in the tools usb folder of SDK. IT FINALLY LET ME!
Now I have a new problem. I'm using the command prompt and trying to create a custom recovery. I set it to the tools directory in SDK (where the flash and recovery images are) and I'm entering the commands exactly like the "how to" instructions have them. I keep getting "adb: not found" errors.
Can anyone tell me what I'm doing wrong?
joshw0000 said:
I've never used Linux but I'm willing to try. Please tell me more. Are there "how tos" for this?
Click to expand...
Click to collapse
Well, in the long run it is probably a good idea to resolve the driver install problems you are having on your PC, because it is very useful to have "adb" around, even if you are already rooted and have the ROM of your choice installed.
But, if you would like to do this, here's an outline below. Note that the point of the "Live" CDs is that you are not installing Linux on your machine, you are just booting it directly from the CD - the OS and hard drive on your PC are untouched.
1) Download an ".iso" file from your favorite Linux distro [ 3 ] for their "live" CD. (BIG download, usually 600+ MB)
2) Burn the .iso file to a CD as a bootable CD. (Most decent CD/DVD burner programs know what an .ISO file is, but might refer to them as a disk image).
3) Boot your PC off it! (You might need to hit a key on your PC right after you power it on to go into a boot menu, or the BIOS setup to change the boot order so your PC will try to boot from the CD/DVD before it tries the hard drive).
4) Copy the fastboot [ 1 ] executable for Linux and the Amon_RA recovery image [ 2 ] to /tmp "somehow" - you could just download it using the Linux browser if your network come up automatically (wired ethernet), or you could put them onto a USB key beforehand, and plug that in after Linux has booted; it should mount automatically.
5) Then, open up a terminal window and become root. (Type either "su" or "sudo /bin/bash" - depends on the Linux distro)
6) Attach your (well-charged) phone to the phone via USB, and power it up in fastboot mode (Send+End simultaneously)
cd /tmp
chmod 755 fastboot
md5sum recovery.img (check file sig)
./fastboot devices (check to see you are connected)
./fastboot flash recovery recovery.img
Obviously, if you need to look something up on the internet, it is useful to be networked, so you can use a web browser. The Linux boot will try to autoconfigure network interfaces automatically, but this is going to be most straightforward with a wired connection (Ethernet). Alternatively, if you have another PC or laptop nearby, you could use that.
Good luck.
Edits:
[ 1 ] Find Linux version of fastboot from HTC midway down this page - md5sum 9851bb6ad29cd4b60c9ba9d011ba9efd
[ 2 ] Amon_RA's recovery is located on this XDA page - md5sum e3932991f097993602af3c7a4b61a4f8
[ 3 ] Ubuntu's Current (x32) CD for v10.04 this page
NOTE: This CD is both a "Live" CD and an Install CD. You DO NOT WANT TO INSTALL ANYTHING; you are using the "Live" CD function - see the "show me how" link under Item #3 ("Try It!") on the above linked page
[ 4 ] Various OpenSuSe 11.2 Live CDs
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
joshw0000 said:
Thanks for the info. I was able to get my drivers installed and run a nandroid recovery. Then I think I bricked my phone:
I just ran a nandroid backup for my Eris which was at stock 2.1 w/ root. I first partitioned the sd to swap - 3072 MB, ext2 swap 3072 MB, and fat32 - remainder. Realizing this was stupid, I went back and changed the partition to swap - 0, ext2 - 512 MB, fat32 - remainder 7680 MB or 7.5 GB. I moved ext2 to ext3 and booted the phone. All my sd was cleared so I copied everything back on (I saved all sd contents to my computer prior to this). I went back to recovery and flashed Eris Lightning 3.02. Everything went successful and when it rebooted, I saw the droid guys, then the "quietly brilliant", then "Verizon" screens. It then began running the "quietly brilliant" and "verizon" screens over and over. I pulled the battery and powered up again but it's still running those two screens over and over. I booted into recovery and attached my phone to the computer. I opened command prompt, entered " sd C:\android-sdk-windows\tools" and then entered "adb devices". It reads "List of devices attached" but there are none. I attempted to add the driver back to my device but when I go to device manager and click "update driver" and point it to the tools directory in SDK, it says that "Windows could not find driver software for your device".
If I can't communicate with my phone via usb and it wont boot, how can I get it to recover?
Any suggestions would help, I'm scratching my head here. I really don't want to have to buy another phone.
Click to expand...
Click to collapse
First, relax and take a deep breath; everything's going to be fine.
In the recovery main menu, there is an Item called something like "MS-USB toggle" or something like that. It does not use the adb driver, it uses a standard "Mass Storage Device" USB driver already on the PC. The purpose of this function is to make the SD Card mount on the PC when the Amon_RA recovery is running.
Try that - it should work.
Then, download a conservative ROM such as Ivanmmj's Official 1.0 alpha, or Jcase's "Plain Jane", and copy it to your SD card.
After you have done that, make sure to check the MD5 sum of that .zip file on the SD card. (You should be doing this already).
Then, cleanly dismount the USB drive from the PC with the "Safely Remove Hardware" thingamabob, and toggle "off" the MS-USB toggle on the phone. Return to the main menu, wipe /data, and then flash the "conservative" ROM.
Then boot the conservative ROM just to verify everything is OK.
Next, Backup anything from the SD card that you don't already have (this step might be optional), and boot into recovery, and unpartition your SD card so that the only thing that is there is the VFAT partition.
For the moment, I'll give you some advice: f*ck A2SD. You need to gain some familarity with how the various versions of a2sd work before you start using it..
Very likely you were just stuck in a boot loop created by the re-partitioning you performed after initial configuration of a ROM that uses a2sd. Frankly, it is easy to create conditions for this, especially if you switch between ROMs that use different versions of a2sd, and/or don't understand that certain versions are not correctly backed up with Nandroid at the moment (e.g CLB).
bftb0
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
Go in to the start menu of your computer or laptop right click on computer and go down to properties and open it up look to the right and you will see something that says advanced system settings click that and it will open up another window for system properties.. Okay look at the bottom of that small window you will see something that says environmental variables, click that. Now you want to scroll through the system variables and find the one that says "path" you want to change that to you ";C:\android-sdk-windows\tools" and save it.. That is where your adb file or app is in your sdk tools folder, so when you open up a command prompt type in adb devices it may say something about killing daemon starting successful.. Don't worry just type it in again you should get your phones serial number thats when you know your good and you can start talking to your phone.. You can try a simple command like adb reboot and it will reboot your phone.. All else fails and you do this and your phone is responding but you can get anything to run in the command prompt type with 1 space cd then another space and then copy and paste "C:\android-sdk-windows\tools" that.. So it will look something like this
cd C:\android-sdk-windows\tools.. That should def do the trick.. Or absolute worst case scenario and you want to make it real easy and not have the fun of doing all the hard but fun work just use the "all in one root script" it will root your phone and it will also install "amon RA recoveryv1.6.2"... Hope this helps you out. LoL I know its long but yo dude I went through the same hell and I finally got everything where I want it!!!!!! Also make sure your HBOOT is under 1.49, if you have 1.49 you cant root... For example 1.46 your good...
If you want to install Debian, just follow this step:
1. Download this : megaupload.com/?d=EV1SOKWJ
In the debian folder you should change the installer.sh and bootdeb files by this one
Download them:
installer.sh : mediafire.com/file/6j99zi0g1lu4oxq/ashu11x_installer.rar
Bootdeb : mediafire.com/file/osshm94mo1qhd65/ashu11x_bootdeb.rar
2. After that, copy the debian folder unzipped to the root of your sd-card
3. Than open Terminal and type:
Code:
su
cd /sdcard/debian
sh installer.sh
bootdeb
cd /scripts/onetime.sh
sh onetime.sh
That's it!
Credits:
ashu11x
An other way to install it
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
Download Linux Installer here:
uk.androlib.com/android.application.com-galoula-linuxinstall-tFjz.aspx
Install it
Press "Menu" button and choose "Setup".
The configuration apper, the defaults settings work without touch anithing : Debian Leny into a 500M loop file named "Linux.loop" in th sdcard. for lunch this Linux, the script name is "linuxboot".
Detailled functions :
- Install into LOOP file
Check to box if you want use an loop file, a loop file, is a virtual disk, same as image of hard drive. The loop file can be in any directory. I recomand to put this loop file into sdcard with an extension ".loop".
- Server
Name or IP of download server. If this option is empty, the default server is used. To install ubuntu, leave emtpy.
- Distribution type
Type of distibutions, actualy, Debian or Ubuntu.
- Distribution version
Version in type distribution. Warning ! Please check your version with a real type ! Debian can be Lenny or Squeeze, but no Dapper or Jaunty ! This two end, is Ubuntu version !
- Script to lunch Linux
The command to lunch Linux. you can choose own command to lunch. It permit to install Lenny into file Lenny.loop with script name bootLenny and install. after that install debian squeez or Ubuntu Jaunty into a partition of your SD card, and use an JauntyBoot to lunch jaunty. You have two Linux distributions on the same phone !
- Install into (loop)
Enter full path for the filename used as loop. I recommend to /sdcard/myfile.loop
- File size
The size of file allowed for loop. The size is alocated directly, no possible to change or have an dynamic size !
Click to expand...
Click to collapse
The full site with pictures
android.galoula.com/en/LinuxInstall/
where is the /scripts/onetime.sh
http://forum.xda-developers.com/showthread.php?t=1129803
http://forum.xda-developers.com/showthread.php?t=996746
http://forum.xda-developers.com/showthread.php?t=954807
ccownu said:
I'm back:
Ok galoula create a universal way to install Deban AND UBUNTU
So,
The full site with pictures
android.galoula.com/en/LinuxInstall/
Click to expand...
Click to collapse
on My P500 that one sucks, it worked on 2 gb not on 8 gb, but as told its an rc
Or just do this: ← How to Build CHROOT ARM Ubuntu Images for Android! (UBUNTU ONLY) SHALL WORK ON DEBIAN I THINK!
How to Install Busybox on your Android! →
How to Install Ubuntu on Android!
Posted on February 1, 2011 by admin
For those of you who want to install Ubuntu on your Android smartphone or tablet device, here’s our universal guide on how to do it. (This guide is based off my original guide at NexusOneHacks.net)
*Note – This guide should work on most “rooted” Android smartphones/tablets with no further modification.
We will be running Ubuntu “chrooted” under Android OS, which just means that we will be running a “virtual” Ubuntu OS that runs on top of the Android OS. Your Android OS will work fully (e.g. your phone will keep working normally) while the Ubuntu runs on top of it.
First of all, you should have your Android device “rooted” because you need root access to run Ubuntu off your Android.
Second, your Android OS must support loop devices. Most newer Android smartphones/tablets come with this support so we can mount our Ubuntu image as a loop device. If not, you will either have to build your own kernel with support for loop devices or you can try an aftermarket ROM for your phone as most aftermarket ROMs come with support for it.
For example, G2 Phone and Nexus One both come with loop device support so there’s no need for us to compile a new kernel for it but for others, you may have to.
How do you know this? Just try installing Ubuntu and if it doesn’t boot, your Android device needs a kernel with loop device support. Otherwise you are fine.
How to Install Ubuntu on Android! (Windows)
First, download the following Ubuntu.zip file (from a preferred mirror), unzip and copy over the whole ubuntu directory to the SD card of your Android smartphone/tablet device:
Download ubuntu.zip http://downloadandroidroms.com/files/get/Nhi9EJWSw7/ubuntu.zip
(Turn USB storage ON then copy over the Ubuntu folder to the root directory of your SD card.)
(What it looks like after copied over to the SD Card)
1) Again, make sure you have your Android smartphone/tablet “rooted”!
2) You must have Android SDK installed or have access to adb.exe.
3) Make sure your Android phone/tablet is in debugging mode. Go to Settings->Applications->Development and make sure USB Debugging is checked ON.
4) Connect your Android device to your computer via USB cable and set the USB mode to “Just Charge”.
5) Your Android device should be recognized as “ADB Device” under Device Manager. If not, install appropriate drivers.
For all HTC Android smartphones/tablets (such as G2 Phone, Nexus One), you can download Windows drivers here:
HTC Windows 64-bit driver download – Click Here to Download Driver
HTC Windows 32-bit driver download – Click Here to Download Driver
6) Open up a command prompt by typing “cmd” under Start->Search programs and files.
7) Browse to your SDK directory where you installed the Android SDK:
8) Then go into platform-tools directory:
9) Type “adb devices” to double-check your Android device is recognized.
In this example, I used an HTC G2 Phone, which shows up at “HT09SR204261″. This is fine. However, if you get an empty device, that means you didn’t install the drivers for your phone/tablet correctly. (Go back to #5)
10) Type “adb shell” to enter the Android shell.
Then type “su” to enter super user mode, then type “cd /sdcard” and “cd ubuntu” to enter the ubuntu directory in your SD card of your Android device.
11) Next, type “sh ubuntu.sh” to run the script which will basically get your Ubuntu image ready to run on your Android smartphone/tablet.
If you get error messages, don’t worry and keep going.
12) Type “bootubuntu” to enter Ubuntu. (Next time you enter Ubuntu, you just need to type “bootubuntu” from your /sdcard/ubuntu directory, no need to run ubuntu.sh again.
If you got “[email protected]” at this point, congratulations! This means your Android OS comes with loop device support and Ubuntu is now running “chrooted” on top of your Android OS!!!
However, if you failed at this point, your Android OS probably doesn’t support loop devices, try installing another ROM or compiling your own kernel with loop device support.
How to Install Programs on your Ubuntu!
Once you’ve got Ubuntu running on your Android device, it’s time to install some Ubuntu packages(or programs).
Type “apt-get update” to update, this is the first thing you will need to do before installing any new programs.
How to Install OpenSSH-server on your Android Ubuntu!
Type “apt-get install openssh-server” to install OpenSSH-server. What is OpenSSH-server? If you want to connect to your Android Ubuntu via an IP address (and SSH into it), you will want to do this.
How to Install TightVNCServer on your Android Ubuntu!
If you want to access the GUI of your Android Ubuntu, you can install TightVNCServer, which allows you to access the Android Ubuntu via Android VNC app on your Android smartphone/tablet or even access it remotely from your desktop computer.
Type “apt-get install tightvncserver” to install.
How to Fix Language Issues
Above is after I connected to my Android Ubuntu via SSH2. Well, for some reason my default language switched to German. To fix that, just type “export LANG=en_US.UTF-8″:
How to Install LXDE!(optional)
Next, we will install LXDE (Lightweight X11 Desktop Environment). Although we can use Ubuntu’s default GNOME (and trust me I love that), LXDE takes up less memory so our GUI access will be faster.
If you like GNOME, you can skip this step though.
Type “apt-get install lxde”
Next, let’s setup xstartup file so that when TightVNCServer is started, the LXDE runs instead of GNOME:
Type “cat > /root/.vnc/xstartup”
Then type:
cat > /root/.vnc/xstartup
#!/bin/sh
xrdb $HOME/.Xresources
xsetroot -solid grey
icewm &
lxsession
Then hit Ctrl+D twice and enter to save the file.
How to Start TightVNCServer!
Next, let’s start the TightVNCServer and connect to it from our Android phone and my Windows 7 desktop:
Type “export USER=root” and “vncserver -geometry 1024×800″.
Here, you can change the resolution settings 1024×800 to the resolution of your liking.
Now your TightVNCServer is ready to accept any incoming connections from your phone or computer. Just point to the correct IP address and use port number 5901 to connect.
On your Android smartphone, just download the free app “Android-VNC-Viewer” and set the IP address to “127.0.0.1″ and port number 5901 to connect.
And you should be able to get into your Ubuntu like this:
You can also use desktop software like TightVNC Viewer and connect to your phone.
Do “ifconfig” to find out what your IP address is in your Android Ubuntu.
In this example, mine was connected to “192.168.1.131″.
Then connect to “192.168.1.131:5901″ on your TightVNC Viewer:
Here’s LXDE running on my desktop off my G2 Phone’s Ubuntu:
Troubleshooting
Ubuntu not running?
Try typing “cp” under Android shell and if you get an error message, it means you need to install Busybox. Install Busybox and try again.
Final Thoughts
As said in the video, there will be a lot of improvements in the speed of Android devices in the near future. This year, there will be a slew of dual-core 1Ghz processor-equipped Android devices being introduced. Which just means our Android Ubuntu will run faster and faster.
I've been sitting on my 4.5.91 update for a month or two now, out of sheer laziness/I have no idea what I'm doing. I'm currently running Android 2.2.2, update 4.1.83, and GingerBlur 3.1. I have a recovery image, yet when I try to boot into Fastboot, nothing happens and holding the up volume button only locks me into a "Starting RSD protocol support" screen. I'm a little lost,and my Android-savvy roommate is as well. Any help would be appreciated!
-My roommate has reviewed my post and says I should mention I'm trying to push a ROM through Fastboot, but my PC won't recognize my phone.
download and extract
Android-sdk-windows
to the c:\ on the pc
then go to android-sdk-(yourpc) folder open it and run the installer
choose the first 2 packages check tools
and platform tools then unckeck 4.0
and all the rest (it should do it but you might need to uncheck manually)
then install 2 packages ok,
inportant note below!
go to:
start,
computer right click and choose properties /advanced /enviromental varialbles
second wimdow scroll down to PATH
highlight it scroll all the way to the far right and type C:\android-sdk-yourpc\platform-toolsC:\android-sdk-yourpc\tools
reboot pc and go to start/run type"adb
enter; you should get a big list of options
plug your phone into pc Dont mount sdcard to pc just plug it in
adb devices
# attached devices
output will read a device secific code
and time it took
there is a video refrence for indepth investigation
http://m.youtube.com/#/watch?desktop_uri=/watch?v=oaNM-lt_aHw&v=oaNM-lt_aHw&gl=US
to "change directory you will need to type
into command promt cd android-sdk-windows\platform-tools
for windows pc for linix and mac (sellit and by a windows
I am having a hard time un-rooting my phone back to stock to return to at&t. I have followed this instruction:
http://forum.xda-developers.com/showthread.php?t=1634087
But when I get to this part I am totally lost.
" Issue the following adb command. I SUGGEST YOU COPY AND PASTE IT, IF YOU TYPE IT WRONG YOU WILL HARD BRICK YOUR PHONE.
command: " adb shell dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 "
I am not sure I installed ADB correctly following this instruction:
http://jaxov.com/2010/10/set-up-adb-on-windows-7-vista-xp-for-android-phones/
and this:
http://developer.android.com/sdk/installing/bundle.html
I can't afford to brick my phone and if I get caught by my wife.... OOOOO the horror.
Here's what I have,
1. the adb bundle in a folder here -C:\Android Development\
2. android Development contains - a. eclipse folder, b. sdk folder, c. a workspace folder for eclipse projects I added
3. I have the drivers for my phone installed (I think - Kies works)
4. I have the Recovery image on my sd card. (my external card won't mount)
5. Debugging enabled
6. SDK manager has been run and updated
I think I need to do some thing with the environment variables but I'm not sure what.
the instructions said:
"Navigate to My Computer (Icon)->Properties (Link)->Advanced System Settings (Link)->Advanced (Tab)->Environment Variables (Button)->System variables (Section)->Path (Variable)-> Edit (Button)-> Variable value. Enter the following value as shown in the screenshot.
C:\android-sdk-windows\tools "but my path is not the same. I didn't want to mess up my computer so I created a new variable named android path and added C:\Android Development\sdk\tools.
when I open the cmd line, the instructions here ( http://jaxov.com/2010/10/set-up-adb-on-windows-7-vista-xp-for-android-phones/ ) show the folder as C:\android-sdk-windows>adb devices and I have C;\Useres|Momma Bear (Yes it's her computer)
What do I do Next? Pleas help a noob Google let me down for hours.
Thanks to all who look and help. and +10 to all the devs and who ever gives me a working solution.
Just use dos commands to change to the directory with adb.exe , then run adb, then type " devices" and it should report your phone as android device. If not, PC did not correctly install driver. If yes, copy paste command.
But honestly, just return to stock, then delete superuser app. How will they check?
I am working on trying to root my Alcatel A50 (nice little phone I picked up on the cheap). In order to install SuperSU to get root access, I need to install a bootloader. By the looks of it, I should be able to make a working bootloader if I have the boot.img file. In order to extract boot.img from the phone, I need root access... a bit of a catch22...
I have so far managed to unlock the bootloader and download an official MBN file via the official Alcatel Windows updater. If I can figure out how to extract boot.img from this MBN file, then I may be able to get around the above3 catch 22.
From this MBN file (3.4 GB in size), I have managed to extract a bunch of apps (see my journal in the hidden section below for details of how I did that). However, part way through the extractor chokes and quits. Based on the size differential of what I am able to extract vs the overall size of the MBN file, I am sure that there is more lurking inside of this file beyond what was extracted - such as the desired boot.img.
What I have gleaned so far in my reading suggests that these MBN files are, in fact, a sort of executable binary file. To that end, I am wondering if anybody has had any luck disassembling these files/fully extracting their contents.
In case it helps (either for my query or some future endeavor in a related vein), here is what I have documented of my quest thus far (follow the directions/links/downloads at your own risk):
https://web.archive.org/web/2017070...bile.com:80/global-en/support/smartsuite/list
Enable OEM Unlock: http://techbeasts.com/how-to-enable-oem-unlock-on-android-nougat/
Install ADB and Fastboot. Go here: https://developer.android.com/studio/releases/platform-tools scroll down to the Downloads section and click on “SDK Platform-Tools for Windows” - it should be a 4-5 MB download. Unzip the files and navigate to the folder via CMD.exe.
As Alcatel seems to have merged with another company, it would appear that links to useful software, drivers etc have all been broken in the midst of their overhaul. I must say I was unimpressed with the limited information/downloads available from their present sites (even checking many of their international sites). At any rate, I managed to find a link to the Alcatel Smart Suite (https://web.archive.org/web/2017070...bile.com:80/global-en/support/smartsuite/list) via Archive.org. I simply selected the newest one and – behold – it downloaded.
Download Smart Suite → Install and load application. Plug in phone to install Alcatel ADB Driver. Reboot Windows
I did run into an issue when running “adb devices” after launching the Smart Suite where it was saying:
adb server version (31) doesn't match this client (40); killing...
could not read ok from ADB Server
* failed to start daemon
error: cannot connect to daemon
I found someone else had a similar issue (https://stackoverflow.com/questions...rsion-31-doesnt-match-this-client-36#38447003). As per the link, I closed Smart Suite and ran the following terminal commands:
adb kill-server
adb start-server
And that seemed to resolve the issue.
You will want to reboot the phone into fastboot mode with this command:
adb reboot bootloader
And verify that you have connectivity by running:
fastboot devices
Then type in this command:
fastboot oem unlock
Your phone will display some text prompting you to unlock the bootloader. Mine says:
Unlock bootloader?
If you unlock the bootloader, you will be able to install custom operating system software on this phone.
A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly.
To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from our phone (a “factory data reset”).
Press the UP/Down buttons to select Yes or No.
Yes: (Volume Up): Unlock (may void warranty)
No: (Volume Down): Do not unlock bootloader.
To continue, Press the Volume Up button on the phone.
Another site suggested I also run: fastboot flashing unlock. I am not sure if that is necessary, but I ran it for good measure. The procedure is the same as above.
Once it finishes, press and hold the power button to power the phone off. Then power it back up. Once it is finished erasing, set up the phone again, enable developer mode and USB debugging.
Next, we will need to obtain root access. To do this, we will install SUPERSU. Unfortunately, at the time of this writing, the official website only gives us XML files when trying to download the files. I did track down an unofficial mirror, though am not 100% sure of its veracity. Download the latest version (the zip file) and use ADB to push it to the phone (adb push filename.zip /sdcard/) and then use the onboard file manager to move it to your external SD card. Then reboot into recovery mode (adb reboot recovery).
Getting Original Firmware
http://www.alcatel-mobile.com/cari/support/softwareUpgrade/list
Download Mobile_Upgrade_S_Gotu2_v5.2.1_Setup.exe
• Install
• Shutdown Phone
• Load software & select 5085O
• Plug in Phone to initiate the downloaded
• (?Unplug phone) and wait for download to complete
• Go into C:\Mobile Upgrade S Gotu2 v5.2.1\download and grab the big file.
Extract Zip → Get MBM File
Either using CYGWIN or running it on Linux directly, execute the following perl script (as per this thread discussion - https://forum.xda-developers.com/an...p-4s-help-rooting-installing-t3514186/page9):
cat system.mbn | perl -pe 's/(\xFF{5}\x00{4}\xFF{54})[^\xFF]{10}(\xFF{16})/\1\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\2
/g' | perl -pe 's/(\xFF{32})\xA8\xCF\x56\xCF\xFA\x43\x09\x9F\x79(\xFF{32})/\1\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\2/g' > system.img
On Linux, install simg2img. Use this utility to convert the system.img to system.img.raw (cannot recall where I saw this tidbit)
Mount system.img.raw (mount system.img.raw /mnt/tmp)
sudo cp -R * /home/Downloads/temp/