Related
This thread is about installing Android natively on your Vogue so it completely replaces Windows Mobile.
[size +1]Important: This thread is now out of date, if you want to flash Android, use the new "norootfs" NBHs.[/size]
There are 2 installation methods:
If you are already running android from your sd card then use method 2, if you want a fresh install of android 1.5 from a windows machine use method 1.
For both methods, you must have a HardSPL installed, if you have flashed a custom wince rom before then you will, otherwise read one of the other threads on XDA about how to do this.
Method 1:
------------------------------------------------------------------
download the following:
http://www.mediafire.com/?zldjhfnkzk2
Unzip it and follow the instructions in README-ANDROID.txt.
All you have to do is copy the androidinstall.tar file to your sd card and run ROMUpdateUtility.exe on your PC.
Now Donate:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Method 2:
------------------------------------------------------------------
Check here for NBH files containing a linux kernel and initrd to allow you to flash android to your vogue and wipe windows completely.
http://it029000.massey.ac.nz/vogue/files/?C=M;O=D
The ROMs are dated and there are three versions.
They are identical except the resolution; 240x320, 320x428 and 320x480.
You will also need a new rootfs:
http://it029000.massey.ac.nz/vogue/files/rootfs.zip
This rom will copy your rootfs, system and data to nand (the internal storage of the phone) so you will only be running from nand. To do this, make sure you have a working setup (using system.sqsh and data.img without partitions) and install the new rootfs. Make sure it still works.
Make sure you have a carrier rom to go back to. Android currently doesn't let you change any of the radio parameters so you would have to flash back to a carrier rom to re-provision your phone.
Now create 3 empty files in the root of your sd card called:
rootfstonand
systemfstonand
datafstonand
These must be all lower case with no extensions and they will be deleted once each fs has been copied.
Now flash the rom corresponding to your resolution and wait.
There are 3 ways to flash a rom.
1. Use ROMUpdateUtility under windows (this may not work on these roms, i haven't tried it). Rename the nbh file to RUU_signed.nbh.
2. Use HTCFlasher under Linux, this is what I have been doing and although a bit quirky, it does work. A binary that fixes a few things with HTCFlasher is on the website.
3. Rename the nbh file to VOGUIMG.NBH, put it on an SD card and boot the phone while holding down the power and camera keys.
When it starts, it should be running from nand. The tmp and cache dirs are still mounted from sd, so you do need the sd card in there but it's not really used much.
If something goes wrong or you haven't copied the correct files, press volume up while it is booting (after the two vibrates preferably). It will display a message saying that its in recovery mode. You should be able to plug the phone into a computer and the sd card will appear as a usb drive. You can also connect using adb.
There are a few limitations, rootfs must be less than 13M, system must be less than about 90M and data must be less than about 128M. This means unless you use a very stripped down system with apps2sd, hero probably won't work.
I've put a linux adb binary on the files page that fixes the annoying history 'feature' too.
Remember, this will completely wipe windows mobile and all your data from the phone. Run android from SD first to make sure you like it and don't want to be able to easily go back to windows mobile.
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Woot!
Doing this now =)
dzo said:
I've spent a lot of time on this so I would like people to donate if they use it.
This is my paypal:
https://www.paypal.com/cgi-bin/webs...bn=PP-DonationsBF:btn_donate_SM.gif:NonHosted
Click to expand...
Click to collapse
I'm paypaling 5 bucks right now.... and I dont have a Vogue, I have a kaiser, but hey, $5 is long overdue for all the work you've done for the kernel... if NAND support hits the kaiser, I'll probably throw another $5-10 your way.
*paypaled - I normally dont do this kind of stuff, but its the holiday season, the MSM Android project has made SO much progress cause of DZO, if everyone just donated $5-10, it would at least be a nice gesture for all the work he's done*
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
If I understand correctly, theres "NO" build in here, you play with builds in your DS, and when you are ready and like one..you just use that system.sqsh data.img rootfs (provided) and..the nbh, all in the root of the sd card. And it will flash the nand with your files! So..thats it!
Nice one dzo, hoping for you to get to kaiser
Hey Martin, I can't even use these flashable images, but if it weren't for you I wouldn't even be running Android via haret, plus you've answered so many of my questions and I've never donated. So, since you're actually now, I'll donate $10.
flashing from windows
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
gswarriorfan said:
I just registered to say thanks for all the hard work! I'll paypal you some cash once I get it up and running! I have a couple questions...
First, what works and doesn't work with this version? Bluetooth, tethering, nav?
Second, what version of android is this?
Click to expand...
Click to collapse
nothing that hasnt already worked works there is no change...
dj13241 said:
After flashing android using this method, can you still force the phone into the bootloader? I am assuming this is how you would flash back to windows.
Click to expand...
Click to collapse
yea camera + power + reset hole
Shidell said:
Thank you, dzo. This is incredible work!
Now that you've gotten this far, can you answer some questions for those of us considering making the switch to Android:
What is/is not working in this build?
What version of Android is this?
What are the advantages of running one resolution over another?
Will we require new drivers to sync to our PCs when running Android instead of WinMo? Are they available for all OSes? (XP, Vista, 7, OSX, Linux)
How can we return to WinMo if necessary?
What's next in your development goals? With any ideas, can you give any sort of time frame on what we can expect and maybe when?
Click to expand...
Click to collapse
i can answer a few
1 nothing that wasnt already working this isnt a build!!!, this is a way for VOGUE users to be able to put a working build "data.img and system.sqsh" they already have working on their phone and to be able to get rid of android
2 this isnt a build
3 320x240 shows more on screen 320x428 and 320x480 show more on screen but it is a little blurry
4 you will require adb drivers located on http://code.google.com/p/vogue-android and as far as i know they work on vista 32 and win 7 32 bit and there are different ones also located at vogue-android for win 7 64b
there are adb drivers for linux in the android SDK located here http://developer.android.com/sdk/1.6_r1/index.html make sure you download 1.6r1 though! 1.5r3 doesnt work for our devices in linux
5 just reflash any wm rom (that works with vogue of course)
mrkite38 said:
Can someone try flashing from windows, then use mtty and run
Code:
set 16 0
task 3
I had to do that to get my test phone out of bootloader last night even after flashing from Linux. But it's up and running 'the new old fashioned way' now.
Click to expand...
Click to collapse
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Ahhh ok I get it now. I'll still donate when I get it up and running. Thanks!
OMFG!!!! dzo you are something else!!!
I just got my Vogue a few weeks back and I am surprised on how well Android runs on this thing (I have a Raphael as well, but no comparison to this)
Having a flashable rom to a WM device... unbelievable...
Kudos for your work man!!!!
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
you could also use the bootloader cmd prompt in htc flasher and do:
Code:
set 16 0
ResetDevice
Click to expand...
Click to collapse
I tried that and it came back in bootloader with 'RUUNBH' in the upper right corner. Then I added the task3 and it booted normally. Who knows, maybe I did something else funny.
I used htcflasher on my newly-reloaded ubuntu laptop, but I wasn't able to get it to work under windows. So I thought that maybe flashing from windows was ok, but it just needed a kick through mtty to get going.
What do those two bootloader commands do? Not that it really matters since dzo says the newest version should work from windows anyway...
egzthunder1 said:
I guess the question on a lot of people's minds right now is this... how do you go back to WM?
Click to expand...
Click to collapse
Boot back to bootloader and flash it! Did that myself last night.
Also, how do we make a smaller data.img? I keep getting 256MB versions.
scizzle said:
Does this have lcd density set? Because eclair is density 120, but looks better in 320x428 with 160 density. If not, is there a way to set density after flashing?
Click to expand...
Click to collapse
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Thanks you so much dzo. i got this working, now im going through all my android files on my computer to find a build that i like, and wanna keep as my main build, but one thing, does the data really have to be less than 128mb? because almost all my android builds are alot bigger which is annoying.
but other than that it worked like a charm. thanks so much.
p.s. once i get some $$ (the 15th of december [my payday]) and find a permanent build i'll send some donations for you hard work.
dzo said:
There's no density set on the kernel cmd line, I'd have to make another nbh for that.
However, since system can now be made r/w you should be able to edit /system/default.prop to change density.
Do:
adb remount
adb pull /system/default.prop .
edit the file and change ro.sf.lcd_density
adb push default.prop /system/
reboot
Click to expand...
Click to collapse
Legend! Thank you. I will try it as soon as I can figure out the data.img haha.
scizzle said:
Also, how do we make a smaller data.img? I keep getting 256MB versions.
Click to expand...
Click to collapse
jamezelle said:
i used the following commands to make a new data img
Code:
dd if=/dev/zero of=~/data.img bs=1048576 count=128
mke2fs -F ~/data.img
to make a blank 128 mb data.img file in my home folder
Click to expand...
Click to collapse
- I can now confirm that flashing the nbh with the ruu works from Windows.
- dzo, I have a panel type 3 us sprint vogue. everything booted up fine, the buttons work, but the touchscreen isn't. Will post logcat / dmesg in a bit.
edit: uploaded zip w/ logcat and dmesg
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.
HI,
I've had success installing my other android devices on my windows 7 x64 computer, have even used my (ADB) Nook Colour on a windows 7 32Bit laptop fine.
Problem: Android Composite ADB Driver wont install/ isn't found, Device is Auto Nootered on 1.1 using rooted stock firmware.
Tried:
I have the .android folder in my user profile dir with the device ID in it
Followed various wikis and guides (that worked for the 32Bit version)
Watched the driver load/unload in device manager as I tick 'Development Mode (enable ADB)'
Tried various driver packs from here and googles latest offering, still only matches up with Android ADB Driver not the Composite (wont even show me the composite one)
Wireless ADB works and is disabled, worried about installing CWM using wireless for some reason USB feels safer to me
Thinks I noticed:
Hardware ID is listed as USB\VID_2080&PID_0002 which matchs up with %SingleAdbInterface% in the ini file for the driver, composite aka %CompositeAdbInterface% has &MI_01 on the end. Not sure if that means its not getting the right hardware ID from the device when ADB/ Development mode is enabled of if having the wrong driver loaded on it shows up the wrong Hardware ID.
Things I havent tried, enabling ADB on the Nook using sqlite3 method, but if it works on another coputer didn't think it would be a good idea.
Plan:
Install CWM, flash CM7 or similar to device.
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
ouldsmobile said:
I had the same issues with Windows 7 64-bit and never got it working. Worked fine on my WinXP laptop at work though. If you find a solution I would be happy to hear it, but to be honest I have found I haven't really needed ADB much if at all.
Click to expand...
Click to collapse
Same here!
This one is weird...
I'm on win7x64 and I *have* got adb to work at times. When I was first rooting my new NC (1.1.0), I fiddled with it and I had it running over usb fine. But now, when I plug in the usb and I either get that the device is unrecognized or it goes into usb sync mode. Haven't quite figured that out...
But, ultimately, I just use adb wireless for any adb stuff, although it's "not recommended". It's worked perfect for me all along.
Check this link
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
loupnook said:
http://forum.xda-developers.com/showthread.php?t=987409
i posted it a few days ago. If it works for you please recommend for being pushed up and add to the linked post that it worked.
Click to expand...
Click to collapse
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
UR Welcome and USB Automount?
NewZJ said:
OMFG dood!!!!! it fixed mine, my win 7 x64 i could not get to stop installing the drivers, i tried every trick the internet has and it would always reinstall the drivers instantly, i added the stuff to my .ini file and i disconnected and reconnected nook and BAM!!! adb devices showed it, and adb shell worked, and now its reconnecting every time!!!
now to get that darn usb auto mount to stop permanently
Click to expand...
Click to collapse
Glad to help. What do you mean USB Auto Mount? I kind of thought that should happen?
My goal for getting adb working was to get su, which i got here http://forum.xda-developers.com/showthread.php?t=953110 with a bit of trouble but seems to work, so that i could drag items from my pc onto HC. I'm using http://forum.xda-developers.com/showthread.php?t=952456 to mount the media directory. I now seem to have su installed and the USM app is working. i only see my BN media directory from my pc now (yay) but i can't browse that directory from my nook HC (boo). So i can't share files between eggclair and HC. I'm a noob to nook and newbe to linux, so i'm assuming it is a permissions issue but don't have enough knowledge on how to change them yet.
I've installed DropBox but it keeps asking for an SD card, which isn't a big issue, just i haven't found the time to go buy one. Is there a way to use db without an SD card?
unfortunately no, db requires external storage. if you opened the apk to recode its default directory maybe but im not sure its possible
usb auto mount I can disable in nook tools but its a persistant system that defaults every reboot, I dont like to see it popup while using the nook when I plug it in just one of many peeves
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
GateheaD said:
Things I noticed:
In the Driver ini it states &MI_01 means composite driver is installed.
Under Hardware ID I only get :
USB\VID_2080&PID_0002&REV_0216
USB\VID_2080&PID_0002
This leads me to believe that even though the box is ticked on my nootered Nook that its not really enabling ADB on the device (then maybe it would show &MI_01 as needed?)
Going to flash a new firmware.... maybe Froyo and see if it comes up right after that.
Click to expand...
Click to collapse
I thought that as well and flashed back to the EC 1.0.1, sideloaded 1.1 update and repartitioned, used cw to add HC back and all that, and still had the same issue. Came down to the ini file not having a NookColor section.
Did you check the link http://forum.xda-developers.com/showthread.php?t=987409
I'm no stranger to drivers, I could force it to use the driver by changing the ini files but it still wouldn't appear in ADB Devices.
Flashed Nooky FroYo and now the device driver states the hardware ID has the missing '&MI_01' which means the composite driver works out of the box.
I used IOMonsters Easy USB installer and it seems to have installed the drivers for Windows 7 64Bit Fine
After running the install .exe I also had to execute the Inst64.exe
I've spent some (much) time this week with trying to get ubuntu running on the optimus 2x. I have succeeded to boot and get the wifi, X11 and the touch screen sort-of working.
The ramdisk is completely replaced with a busybox executable, some symlinks to it and a shell script that mounts the necessary stuff (/dev/block/mmcblk1p2 as ext3), changes root directory and calls /sbin/init.
USING THE FOLLOWING WILL VOID ANY WARRANTY YOU MIGHT HAVE LEFT AND MIGHT ALSO BRICK YOUR PHONE!
Seriously, don't do this if you don't wish to risk the data on your phone.
I will be providing some demo images for people who don't have a build environment up and running. These images will not work particularly well, don't get your hopes up .
If you want to have a big linux installation (more than 3 GB) you can flash the images to the second partition on your external sd (obviously you have to create this yourself first). You can use the following boot image (which assumes that linux is on /dev/block/mmcblk1p2 with ext3:
https://ha.xxor.net/o2x/boot-20110813.img
I have also targzipped the modifications to the file system that were required to get stuff going here:
https://ha.xxor.net/o2x/o2x-20110813.tar.gz
This should be extracted directly to the root file system.
The kernel source code is up at https://github.com/ergoen/LG-Optimus-2x-linux-kernel
Things that have been done to get this to "work":
1. Boot partition
Apart from grabbing the busybox stuff from some nexus one boot image (I'm sorry whoever fixed it, I don't remember where I got it from ) the boot command line had to be modified a bit, changing stuff from the default usually ends up in a phone that won't boot, but I discovered that it's possible to append new arguments to the default ones. So the following have been appended:
console=tty0 root=/dev/mmcblk1p2 init=/sbin/init
The console=tty0 makes sure that you see stuff on the screen while ubuntu get's running. The last two are not necessary to boot, but ubuntu seem to like (need?) them (or at least the init=/sbin/init), since otherwise you never get to the login prompt on the screen.
2. The Ubuntu installation
To make it possible to communicate with the phone at all adbd was put into the /sbin/ folder and a symlink was created /system/ -> /. Also the "/sbin/adbd recovery &" command was added to rc.local to make it autostart.
2.1. Modules and wifi
We need the /lib/modules/2.6.32.9 directory. Most files inside that were generated using the "depmod" command, the exception is wireless.ko which was taken from android, the firmware and nvram files needed for the wifi chip to work were placed in the /lib/firmware/wl/ folder. To make the wifi module autoload with the proper firmware "wireless" was added to /etc/modules and the file /etc/modprobe.d/wireless.conf was created with the contents describing the location of the firmware and nvram.
To make the wifi autoconnect on boot the /etc/network/interfaces file was modified with the following contents:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
(To make the wifi autoconnect to your wireless you need to run the command "wpa_passphrase networkname networkpassword > /etc/wpa_supplicant.conf using adb or chroot)
2.2. X11
Getting X up by running xinit produces a simple black screen on the phone. At first I thought the problem was that the refresh rate was set to 106 Hz, indeed changing it with xrandr and pushing a new mode got me a visible xterm on Kubuntu 11.04:
https://ha.xxor.net/o2x/xterm.jpg.
On Ubuntu 10.10 it even gave me a nice colored gdm screen:
https://ha.xxor.net/o2x/gdm.jpg
But the image I got there was static and wasn't being updated. Turns out the reason the screen was black earlier with the 106 Hz rate and the reason why the screen is now just showing an image is that the framebuffer device doesn't update the screen like it should..
By modifying the kernel source to redraw the screen every 50 ms (~20 Hz) it's possible to get a scren that works. This is an ugly hack in the tegra-fb driver though, so I'm open for suggestions on how to solve it in a better way!
2.3. Touchscreen
By default the only thing the touchscreen does is force the mouse up in the left corner, I think this is due to some multitouch thing. Some more kernel hacking (basically half-disabling multitouch) makes the touchscreen work.
Pictures:
https://ha.xxor.net/o2x/SAM_0671.jpg
https://ha.xxor.net/o2x/SAM_0672.jpg
Video:
http://vimeo.com/27662093
Thans to RaYmAn and lilstevie on #tegralinux for all their help this far!
3. Misc
(K)Ubuntu 11.04 uses a new version of libc which crashes with the current nvidia kernel (2.6.32.9) on this hardware (http://developer.nvidia.com/tegra/forum/errata-657451-tls-bit-20-cp15-c13-3), so I'm going back to Ubuntu 10.10 until someone ports a newer kernel to the Optimus 2x or this problem can be solved in another way.
edit 1: Ubuntu 10.10 with much more working X11 noted in section 2.2.1.
edit 2: X11 working even more, touchscreen works aswell!
edit 3: Landscape mode works with both X11 and the touchscreen now, getting ready for alpha 1!
Current status:
Working:
- adb (best way of controlling device currently)
- X11 (only framebuffer with hardcoded refresh rate of ~20Hz)
- landscape mode fixed! =D
- touchscreen (probably only single touch)
- wifi (only when running things from console, ubuntus network manager does not recognize it)
Not working:
- Basically everything else
Alpha 1:
EDIT: Seems that multiupload has screwed up and this link was going to some crap, anyway this is not relevant anymore
Username 'ubuntu', password 'ubuntuxda'. Don't use this if you don't know how to restore the boot partition! (Or else you won't be able to boot back into android!)
Experiments:
Tried disabling the CONFIG_TEGRA_ERRATA_657451 switch in the kernel to make newer linux versions boot. This might be a bad idea in the long run, but this far things are working better than with the switch enabled..
I tried Ubuntu via chroot method posted in other thread, but I'm a noob.. Can you please explain what is different about your ubuntu?? Does it boot without Android and doesn't need VNC stuff?
Yes, it boots instead of android when turning on the phone, but it doesn't work completely, so I mostly put it up here so that people could help test and fix/hack things.
You rock! Unfortunately I'm no dev, so can't help but hopefully others will, so we'll get a fully working linux on our phone, and maybe later even meego. Is there btw drivers for the gpu? Because hdmi, with usb host ofc, would be really useful!
Anyway, good job, really!
This looks great ergoen! I'm no dev either but I can't wait until it's available to everyone, I would love to have Ubuntu running on my O2x.
Best of luck!
gpu drivers are closed source, and the ones released by nvidia require a newer kernel (2.6.38), so thats not really possible yet.
Newer kernel will be necessary anyway though, since the crashes I'm getting seems to be due to a bug in tegra which gets worked around in 2.6.36. I'm not skilled enough to perform that port though. I will of course give it a try, but most likely I'll go for some older version of ubuntu and/or perhaps meego instead.
Håller med tidigare poster. Would be awesome with native Ubuntu and Meego on the phone... keep up the good work, can't wait to follow this development.
Sent from my Optimus 2X using XDA Premium App
ergoen said:
... I realized that it tried to run the screen at [email protected], which is hmm, wrong . So setting up a script at /etc/xprofile, which makes sure the refresh rate is 60Hz...
Click to expand...
Click to collapse
What would happen if you changed this to 72Hz instead? I saw that info when I was browsing System Information in some app. Im not a dev At. All. But tell me what you think it's probably a stupid question
Sent from my Optimus 2X using XDA Premium App
I can give it a try later, not that it would make any difference .
edit: 72 Hz also seems to work, cool, that's higher refresh rate than my computer screen...
ergoen said:
I've spent some (much) time this week with trying to get ubuntu running on the optimus 2x. I have succeeded to boot and get the wifi working, also X sort-of works (software fb). I have only slightly modified the kernel (built with CONFIG_SIGNALFD=y so that Meego wont complain in a related attempt to get that os booting). The ramdisk is completely replaced with a busybox executable, some symlinks to it and a shell script that mounts the necessary stuff (/dev/block/mmcblk1p2 as ext3), changes root directory and calls /sbin/init.
USING THE FOLLOWING WILL VOID ANY WARRANTY YOU MIGHT HAVE LEFT AND MIGHT ALSO BRICK YOUR PHONE!
Seriously, don't do this if you don't wish to risk the data on your phone.
I will not provide a complete root file system for two reasons:
1. It's pretty easy to make yourself, grab the omap3 kubuntu mobile image from the kubuntu site, or use rootstock from an ubuntu installation to build one yourself.
2. My upload sucks, and putting several hundred MB onto the interwebz would hurt me.
However, I have placed an image of my boot partition here (assumes you've got ubuntu on the second partition of the external memory card formatted with ext3):
https://ha.xxor.net/o2x/boot.img
I have also targzipeed the modifications to the file system that were required to get stuff going here:
https://ha.xxor.net/o2x/o2x.tar.gz
This should be extracted directly to the root file system you aquired earlier.
Things that have been done to get this to "work":
1. Boot partition
Apart from grabbing the busybox stuff from some nexus one boot image (I'm sorry whoever fixed it, I don't remember where I got it from ) the boot command line had to be modified a bit, changing stuff from the default usually ends up in a phone that won't boot, but I discovered that it's possible to append new arguments to the default ones. So the following have been appended:
console=tty0 root=/dev/mmcblk1p2 init=/sbin/init
The console=tty0 makes sure that you see stuff on the screen while ubuntu get's running. The last two are not necessary to boot, but ubuntu seem to like (need?) them (or at least the init=/sbin/init), since otherwise you never get to the login prompt on the screen.
2. The Ubuntu installation
To make it possible to communicate with the phone at all adbd was put into the /sbin/ folder and a symlink was created /system/ -> /. Also the "/sbin/adbdb recovery &" command was added to rc.local to make it autostart.
2.1. Modules and wifi
We need the /lib/modules/2.6.32.9 directory. Most files inside that were generated using the "depmod" command, the exception is wireless.ko which was taken from android, the firmware and nvram files needed for the wifi chip to work were placed in the /lib/firmware/wl/ folder. To make the wifi module autoload with the proper firmware "wireless" was added to /etc/modules and the file /etc/modprobe.d/wireless.conf was created with the contents describing the location of the firmware and nvram.
To make the wifi autoconnect on boot the /etc/network/interfaces file was modified with the following contents:
auto wlan0
iface wlan0 inet dhcp
wpa-driver wext
wpa-conf /etc/wpa_supplicant.conf
(To make the wifi autoconnect to your wireless you need to run the command "wpa_passphrase networkname networkpassword > /etc/wpa_supplicant.conf using adb or chroot)
2.2. X11
Getting X up by running xinit produces a simple black screen on the phone. After some troubleshooting and voodoo magic I realized that it tried to run the screen at [email protected], which is hmm, wrong . So setting up a script at /etc/xprofile, which makes sure the refresh rate is 60Hz, and running it after xinit gets you a xterm!!!
https://ha.xxor.net/o2x/xterm.jpg
Telling /etc/X11/xinit/xinitrc to run it makes sure that it gets set up properly by the startx script, unfortunately startx doesn't go through for me on kubuntu because of some weird error caused by a hardware problem in tegra: (http://developer.nvidia.com/tegra/forum/errata-657451-tls-bit-20-cp15-c13-3).
Unfortunately this (probably) means that either we'll have to stay with old versions of libc or get a newer kernel (2.6.36 contains fix). Old libc seems backwards, but porting a new kernel requires a bit more skill than I possess.
2.2.1. Ubuntu 10.10
Grabbed the image ubuntu-netbook-10.10-preinstalled-netbook-armel+omap.img.gz from http://cdimage.ubuntu.com/ubuntu-netbook/ports/releases/maverick/release/ . After first unpacking the tgz, then unpacking the raw disk image to partition images (with 7zip on windows) and then flashing the 1.img file to the second partition on my sdcard I managed to run a much more bug free ubuntu than before.
Ubuntu 10.10 (Maverick) uses an older version of som libraries that don't crash with the old o2x kernel.
This has lead to the following:
https://ha.xxor.net/o2x/gdm.jpg
Obviously touch screen isn't working properly (pressing it puts the pointer into the upper left corner :S) so can't get further than this currently.
3. Misc
avahi-daemon and cups seems to be crashing all the time and restarting, so removing them (apt-get purge if ubuntu/kubuntu) will make the boot much cleaner. Also I get lots of alignment trap kind of errors that shouldn't be there for different kinds of services, (due to tegra bug mentioned earlier).
edit 1: Ubuntu 10.10 with much more working X11 noted in section 2.2.1
Click to expand...
Click to collapse
Its good you got it to work.Saves me some work.I was gonna begin this project my self after the 19th when my exams end.Maybe i could help you.
ergoen said:
I can give it a try later, not that it would make any difference .
edit: 72 Hz also seems to work, cool, that's higher refresh rate than my computer screen...
Click to expand...
Click to collapse
Most computer screens usually support atleast 72hz also, it's just that it only works with d-sub, and sometimes only at a lower resolution.. It's possible to make special drivers to some screens to enable higher refresh rate through dvi also.
Anyway, it's good the screen on the phone refreshes at 72hz instead of 60 for android, but in linux I really don't see the benefit.. Doesn't hurt to have though. Btw, if we would stay on this kernel, can we use the drivers from android then? Shouldn't gpu also work? Or are the drivers limited and don't allow xorg for example? Sorry if it's stupid question, don't have that much knowledge how android works yet.
Update: X11 and touchscreen work on Ubuntu 10.10 Maverick with new kernel (just a few hacks )!
manasgirdhar: sure! Lot's of things to do new kernel is needed for anything newer than ubuntu 10.10, and even here things like sound etc (cpu scaling maybe too) don't work.
kruppin: actually i removed the xorg.conf now, the phone thinks its running at 106 Hz and it works. Unfortunately in practice it goes at more like 20 Hz because of the hack I made to enable the fbdev output in the kernel. Android doesn't use X11, so those drivers wont be of any use. (I will post the kernel modifications to github soon)
edit: kernel source up on https://github.com/ergoen/LG-Optimus-2x-linux-kernel
A List of Things working at 2nd Post would be nice.
So anybody could fast see Updates,...
Edit:
Have you tried some "cleaner" Linux like Debian?
Alpha 1 is up in the second post for anyone who wants to test it (don't ^^).
I have not tried debian no, I thought ubuntu would be the easiest to google errors and bugs for .
You are great! i was hopin' for this since I have mine. You should try to make usb(otg) work to get some devices going i will try to test it soon
That's amazing We have to test USB OTG function. If it works by default, I'll try this right now
It is possible to make a dual-boot: ubuntu and android?
I don't think usb otg works since I am basically using the android version of the kernel, I also won't be able to try since I don't have a cable... (will buy one sooner or later).
Dual boot probably works if you flash the boot.img onto the recovery partition instead of the boot partition (/dev/block/mmcblk0p7 instead of /dev/block/mmcblk0p5). I have not tried this though. That way regular booting would give android and booting while holding volume down would give ubuntu, only problem with this is that cwm will be gone and the only way to fix broken things would be to flash with nvflash.
well it is not a major deal if have cifs avail needs kernel support as well. Benee mentioned (might) some otg support, mayb u could ask.
also, you might give E17 a try, it is butter-fast, and has a touch module for keyboard (letter zooming.!..) LINK
this can be compiled on a lot of hw, and gives good response with fbdev non-accel drivers also.
and most linux apps work on it fine. ofc until we have 2d/3d accel and might try compiz/fusion as well
LINK
Great job ergoen!
I've worked on exactly the same some weeks ago but i never accomplished it. because i stuck creating a working ramdisk. Which toolchain do you use?
MfG
Since we got a x86 cpu i want to use ubuntu on it, as im from germany i still dont have my I but has anybody tried linux on android?
Adam Outler mentioned something that this would not work...
Btw can somebody tell me what the kernel version is..?
Sorry mods for (possibly) posting in the wrong section :/
//Robert
Sent from my LG-P500 using xda premium
Robbilie said:
Since we got a x86 cpu i want to use ubuntu on it, as im from germany i still dont have my I but has anybody tried linux on android?
Adam Outler mentioned something that this would not work...
Btw can somebody tell me what the kernel version is..?
Sorry mods for (possibly) posting in the wrong section :/
//Robert
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
Kernel version is 3.0.8.
If you can install linux distros on the backend of rooted ARM devices it should make sense we could do the same....maybe
Ubuntu on a RAZR I ? Linux x86 apps + windows apps with wine without even recompile? I think this devece needs some love. It can be the next HTC HD2 for shure.
I dont understand the htc comparison
But i have your ideas about no need to recompile and wine in mind too...
But i understand adam because linux for android is compiled for arm achitecture so a usual desktop image would make more sense...
Why is the kernel version so low?!
Sent from my LG-P500 using xda premium
What we need to do
I have a friend with this device, after rooting he reports there is no chroot command from terminal. If so we must:
Compile busybox (with more extensions) for x86 and install it alongside root (or after root)
Make a mountable image from an ubuntu clean install and mount it (probably also needs busybox)
chroot into this mounted image
run a vnc X server on a framebuffer
vnc from android
This is how it is done on other android devices, will attempt to compile and try these instructions out this weekend when I meet him but booting native ubuntu is a much better idea (even better if we can make it receive calls ).
And for what Windows on 4,3 inches display? It dont have hdmi.
Odoslané z GT-P7300 cez Tapatalk 2
The micro usb is acting like hdmi with adapter...
Sent from my LG-P500 using xda premium
Go look up the HTC HD2. It can run Windows Phone 7 and Android dual-booted (with Linux from SDCard), and was originally the last, albeit most powerful, Windows Mobile 6 phone ever made.
Even though it is four years old, there is a massive and vibrant dev community behind it, making it reach the front page of XDA forums.
However, even the venerable HD2 is getting old, with 1GHz processor and half a gig of RAM that was top-of-the-line years ago, and people have looked in vain for some kind of successor. Hopefully, the Razr I, with an unlockable bootloader and Intel processor, will be the one. But that remains for us to do.
pablocrossa said:
I have a friend with this device, after rooting he reports there is no chroot command from terminal. If so we must:
Compile busybox (with more extensions) for x86 and install it alongside root (or after root)
Make a mountable image from an ubuntu clean install and mount it (probably also needs busybox)
chroot into this mounted image
run a vnc X server on a framebuffer
vnc from android
This is how it is done on other android devices, will attempt to compile and try these instructions out this weekend when I meet him but booting native ubuntu is a much better idea (even better if we can make it receive calls ).
Click to expand...
Click to collapse
So I tried this out and there is a chroot-compatible busybox after rooting ("busybox chroot" needs to be called as opposed to "chroot" as there is no properly made link), so anyone with this phone can try (using a PC) install Ubuntu without the grub bootloader using manual partitioning on a single ext3 (I am not sure if ICS supports ext4) partition on a microsd, put into your phone, use a root terminal, mount it, mount the adequate dev, dev/pts, proc and sys partitions and chroot right in. You then might want to install a VNC server in Ubuntu to be able to create a VNC X session in a framebuffer and a VNC client on the android side to VNC into localhost (127.0.0.1), but that should work, I didn't have time to try it this weekend If someone gets stuck post and let us see what happens I cannot wait to see if wine can run desktop Spotify with sound, excited a little hehe.
EDIT: So to make this more understandable you must:
Install Ubuntu (using your computer) to a MicroSD, specifying partitions manually and choosing only a single ext3. Right before clicking install there is a button with something along the lines of "Advanced options", disable the install the bootloader (grub) option.
Insert the MicroSD into the phone and open a root terminal
I don't use Android, maybe it automounts in /media/sdcard or /sdcard, if not you will have to find the device and partition name (probably /dev/mmcblk0p1 or /dev/sdb1) and issue "mount /dev/DEVICEPARTITION /media/sdcard"
mount -t proc proc /media/sdcard/proc
mount -o bind /dev/ /media/sdcard/dev/
mount -t devpts devpts /media/sdcard/dev/pts
busybox chroot /media/sdcard /bin/bash
Now a shell from Ubuntu should open. apt-get update && apt-get install vncserver (maybe the DNS settings must be set in /etc/resolv.conf, not yet sure)
vncserver (or start vncserver, something along those lines)
Now from Android install a VNC viewer and vnc into 127.0.0.1 (or localhost)
That should do it, again if you get stuck post here
i had htc hd2, the most amazing phone in the world. I wanna buy the rarz i for the x86 processor in it. But cpu power without community and developers is nothing :|
Sorry for my bad english.
Yesterday we tried something:
We used dd to put an arch linux image on a micro sd card...
Though my laptop wasnt even able to boot from any sd card, this should work on our phone...
but how to make it boot from the sd card? xD
btw you might have noticed, this will make only linux boot, not android, we dont chroot, may somebody build a simple ubuntu img for complete linux installer?
//Robert
so right now i am trying to chroot into an img file, mounting it and then chrooting it but all i get is:
chroot: can't execute '/system/bin/sh': No such file or directory
whats wrong?
Robbilie said:
The micro usb is acting like hdmi with adapter...
Click to expand...
Click to collapse
Razr i MHL capable???
as far as i know, sadly not no
Ok so finally I got Ubuntu Quetzal running with chroot, still some problems (missing randr extension in vnc) but ill get over this
Hey,
great work. :good:
Good to see there are people with the same ideas. I´ve searched a lot for this thread.
I will also try to get this device for the same reasons when it´s cheaper. Has anybody tried to get Plasma Active or Tizen to run?
I think Active should now be possible through kubuntu Active?
Cheers!
Hi all
At first you can try a application from play store called Linux installer
https://play.google.com/store/apps/details?id=com.zpwebsites.linuxonandroid
Otherwise you can wait some weeks for an nexus 7 Ubuntu port witch looks really interesting.
http://forum.xda-developers.com/showthread.php?t=1957561
Ahhh maybe have a look at the andrinux project here at xda
[/COLOR]Here's the andrinux link
http://forum.xda-developers.com/showthread.php?t=1387105
Sent from my sweet little Blackbox
Robbilie said:
Ok so finally I got Ubuntu Quetzal running with chroot, still some problems (missing randr extension in vnc) but ill get over this
Click to expand...
Click to collapse
thanks for your post on preparing an arch image (I don't have permision to post in devel forum, maybe because I'm a newbie ), It worked well for me although I had to adjust some things such as path and pts mount
I now have a gcc toolchain and a latex distrib on my phone I had never used arch, found it very good
I've also tried some window managers ... the one I find best for the moment is enlightenment in the touchscreen mode, awesome works great as well.
I would also suggest to use Hacker's keyboard instead of stock android, it is a complete keyboard, very usefull when dealing with terminals ... as for VNC viewer, one should recompile android-vnc-viewer with the patches given in Issues 238 and 239 (can't post links either), it's a lot better
I've had a lot of fun, thanks
First, Complete Linux Installer doesnt work because its images are compiled for arm not x86 (i tried )
Secondly, I did a tutorial here http://forum.xda-developers.com/showthread.php?t=1966984
the nexus 7 stuff is interesting and we consider making flashable fastboot for the razr i since we dont have cwm or such you know
i am talking to jordan keyes who recently owned a nexus 7 who probably will try out the ubu stuff and i might get some system info
but i would really prefer a dual boot, capable of booting from sd...
I came across this site today:
http://www.pvsm.ru/wine/10369
translated here
I don't know if this could possibly help you any further but I thought that I might as well post it.