Database Users

HTC Shift and Android... is there a way?

Hi to everyone,
I'd like to buy this device, now it's street priced at 500 euro but before I do that, I would like know if there's any way to get it into the Android platform.
As far as I read nobody speaked about that and for that I opened this thread.
What do you know about?
Cheers,

If you are thinking of trying Android like what have been tried on other devices (i.e. via SD card loading) there lies the first essential problem. There is no SD card on mobile side. Crack this and you probably can start on the Android issue.

http://forum.xda-developers.com/showthread.php?t=440036

sev7en said:
Hi to everyone,
I'd like to buy this device, now it's street priced at 500 euro but before I do that, I would like know if there's any way to get it into the Android platform.
As far as I read nobody speaked about that and for that I opened this thread.
What do you know about?
Cheers,
Click to expand...
Click to collapse
Hi. I use a translator from Russian into English so that not worry.
I did so.
Download the Android x86 with http://android-x86.googlecode.com/files/eeepc-20090820.iso.
Install an image through unetbootion on USB stick. Start. Start the installation on the hard disk. Formatted for ext2. Rebooted. Yes, with the appearance of the boot to choose the first row, press the "e" (for her editing) and another "e". Append the following line to vga = 788. Press Enter. Then click "b" to boot. When you boot, you will need to press the button and select the video mode, I chose 8. And voila.
Camera works. Better than eeepc900. (It also tried to) the rest did not try it, they say you can start the WIFI, but I'm not good at Linux.
Maybe someone will try harder to establish all the drivers?

nice finding! but everyone is still wanting to replace windows mobile with android or other linux.

propsan said:
Hi. I use a translator from Russian into English so that not worry.
I did so.
Download the Android x86 with http://android-x86.googlecode.com/files/eeepc-20090820.iso.
Install an image through unetbootion on USB stick. Start. Start the installation on the hard disk. Formatted for ext2. Rebooted. Yes, with the appearance of the boot to choose the first row, press the "e" (for her editing) and another "e". Append the following line to vga = 788. Press Enter. Then click "b" to boot. When you boot, you will need to press the button and select the video mode, I chose 8. And voila.
Camera works. Better than eeepc900. (It also tried to) the rest did not try it, they say you can start the WIFI, but I'm not good at Linux.
Maybe someone will try harder to establish all the drivers?
Click to expand...
Click to collapse
This seems to be an installation on the PC side of the Shift. I think the poster knows how to install full linux on the PC side. He is interested in Android on the snapvue side.

sniveri said:
nice finding! but everyone is still wanting to replace windows mobile with android or other linux.
Click to expand...
Click to collapse
It would be great. I saw somewhere on the internet post installation Androida place for WM. If turn out otpishus. While hardly on the side of wm memory only 50 mb (if I'm not mistaken) and for Androida need more.

Yep and we don`t even have bootable kernel yet, unless Neutron83 has founded out something, as he was working with this. There is another topic about this..

Boot non-native Android ROM from within Android?

Hello everybody.
Does anybody know if it's possible to boot a custom/experimental Android build from the removable SD card instead of the internal ROM memory?
I'm thinking, in particular, of Haret, which can be used to boot Android from within Windows Mobile.
Is there something like Haret, that can boot Android from within Android?
That would be useful to test experimental builds without jailbreaking/rooting/flashing the original ROM of the device, and especially useful for those very new devices that cannot be rooted yet.
Any help greatly appreciated, thanks in advance!

I'm sorry to break it to you, but absolutely nothing of that nature exists for Android :-( You'd just have to make a nandroid backup before you flash incase you want to go back to your previous ROM.

That's so bad
I hope this will be of inspiration for someone to develop.
Thanks anyway Adriank

+1 to that idea i think it would be gr8 to try out roms without flashing
if we can do it on win mo with heret surely is possible to do it with android

well, isn't it possible to just use fastboot to boot a specific system.img? i guess it is possible, since someone in our debian thread made a bootable image for fastboot and we were able to simply run ubuntu netboot using fastboot

the_fish said:
well, isn't it possible to just use fastboot to boot a specific system.img? i guess it is possible, since someone in our debian thread made a bootable image for fastboot and we were able to simply run ubuntu netboot using fastboot
Click to expand...
Click to collapse
theres plenty of live cd's for linux init thats the same principle

HTC Dream/G1 Dual/Tri Boot

Hi I am currently running debian on my phone using the method outlines here
http://www.myhangoutonline.com/2009/11/22/install-linux-on-your-g1/
Ive gotta say it quite slow and the method of installation is strange.
Here is a video of someone dual booting NATIVE debian on a G1. Read descrip in video for more info.
http://www.youtube.com/watch?v=tX1BOGl8Fnw
I would really want an option where you boot into recovery (Holding Home) and there is a menu where you can choose to boot into a normal recovery (Amon_Ra's) and the other options would let you choose between what OS you want to boot into like Gnome,OpenMoko,Debian. A normal boot would take you back to android.
Speeking of OpenMoko
there is a tut here
http://wiki.openmoko.org/wiki/OpenMoko_on_HTC-Dream
and i was wonderin weather anyone had tried this because it seems very interesting and would make it possible to bood gnome,debian etc
any opinions are highly appreciated
let me know what you think.

i dunno if im allowed to but bump

donut = 1.6 right?

yes
cupcake = 1.5
donut = 1.6
eclair = 2.0/2.1

Hi!
I've got OpenMoko dual-booting natively on my G1.
When I first looked into the problem, I saw that:
1) OpenMoko option involved boot flashing that would disable booting into Android.
2) Debian option had no ready-to-use rootfs. You had to bring on the usbnet and install debian packages through netinstall. But Debian was able to dual boot, thanks to FukTheRegister's excellent recovery image.
I surely needed something in the middle
I had contacted the OpenMoko port developer, leviathan (a nice guy btw). He's doing some great job of hacking the forked Android kernel to work on HTC Dream together with some other guys. He told me that he was continuing his work on OpenMoko for HTC Dream and that made me want to try it instead of Debian. By the way, FukTheRegister's Debian and Ubuntu ports are based on leviathan's OpenMoko kernel.
What I did to install and dual-boot OpenMoko was:
1) I partitioned my microSD card into three partitions: FAT, ext3, ext3
2) I extracted the OpenMoko rootfs to the third partition (ext3)
3) I made myself a recovery image that would consist of the most recent OpenMoko kernel from gitorious AND FukTheRegister's ramdisk (I just glued them together and threw away some modules to make it fit into 5Mb - maximum for recovery partition images)
4) I copied the recent kernel modules to /lib/modules/ on the 3rd partition of the sd card
5) I copied my recovery image to the sd card and flashed it with flash_image recovery /sdcard/openmoko-recovery-partition3.img right on the phone (under root).
After that I was able to boot OpenMoko with holding HOME + END during the bootup or Android (holding nothing).
See http://vaskas.ru/om-g1/ for all the relevant files.
If you want to try it yourself:
- repeat stage 1) after me
- take the openmoko-rootfs-20091128.tar.gz and repeat stage 2) after me
- copy the openmoko-modules-20100128.tar.gz to /lib/modules/ on the 3rd partition and extract it there
- take the openmoko-recovery-partition3.img and repeat stage 5) after me
P.S. I am not 100% sure that it's going to work for you, because I experimented a lot. It's pretty likely to work though.

hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?

vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
p.s this is sooooooo sick with open moko the possibilities are endless aswell as for people who prefer they can turn openmoko into debian and some time in the future android
so future = openmoko installed instead of android and then being able to boot debian/android or stay in openmoko environment.
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work

olvap377 said:
vaskas thx so much for the huge leap forward ecept im a little confused. so when i hold home + power using ur method it will boot into openmoko, butif i boot normally it wouild go into android, but what if i wanted to boot into normal recovery like amon_ra's?
Click to expand...
Click to collapse
No, normal recovery won't be there, since my image replaces it. As far as I know, it's the only way to dual-boot now. If you wish to use your normal recovery image (amon_ra's or cyanogen's), just flash it with flash_image recovery my.img. When you're done with it, flash it back to openmoko's.
olvap377 said:
if i boot into android normally and then run quickboot app and select recovery will it boot opoenmoko or amon_ra's recovery. also with your method does keeping apps on the first ext3 still work? while the second ext3 is for openmoko?
also when making second ext3 partition what size should i make it?
Click to expand...
Click to collapse
I haven't tried quickboot yet.
Yes, Apps2SD still works perfectly with the first of ext3 partitions. I suggest that you make the second one at least 700Mb in size. I've got 500Mb taken by OpenMoko, for instance.
olvap377 said:
also if it's not to much trouble vaskas can u please make a vid and put on you tube or here thx in advance andthx for ur hard work
Click to expand...
Click to collapse
Well, you shouldn't really thank me since I only built a recovery image It's the kernel and ramdisk hackers who rock.
I'll make a vid when I have some free time, but I really suggest that you try it yourself

scheich said:
hi again vaskas!
thx for work. Tried your setup, it worked for me.
Now it would be nice to have a recovery with an option to boot the second ext3.
Openmoko on Dream ----> nice!
Seems to get a usb connection:
http://wiki.openmoko.org/wiki/Usb_networking
Is a ssh/dropbear server already running on boot?
Click to expand...
Click to collapse
FukTheRegister's ramdisk has such an option. I can try to make such a recovery if you need it.
Yes, dropbear is started automatically.

I'd love to see a solid and stable distro that would provide all the things that Android doesn't have, with:
- A compact desktop environment, supposedly e17 or LXDE
- Midori or Google Chrome
- Pidgin
- Sylpheed or Claws for GPG-secured e-mail
- MPlayer or VLC
- FBReader
- evince
- AbiWord
- Gnumeric
- Conky
- Gpodder for podcasts
- Some music player like Sonata
- Cron, sshd, gcc, scripting languages like Python and Ruby
- Zhone for making calls, texting, storing the address book
See, I'm not advocating touch-oriented software. I think we still need touch-capable apps for calling, texting and the address book. The others can be easily manipulated with the trackball and keyboard on G1.
That's what we should aim for IMHO: http://wiki.openmoko.org/wiki/Image:Debian_lxde_zhone.png
OpenMoko project has all this stuff. And that's really awesome. The question is if such an OS should be based on Angstrom (like OpenMoko SHR) or Debian (see http://wiki.openmoko.org/wiki/Debian). My preference is Debian since I'm a long-time Debian/Ubuntu user.

i prefer debian too and i will try this when i get home

i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance

lolmensch said:
i'm sorry for my really dumb question.
but how can i copy something from windows (7) to a ext2 partition?
and if you are creating those partitions, do both ext2 have to be primary or
one primary and one secondary?
thx in advance
Click to expand...
Click to collapse
They both have to be primary. I also recommend you to upgrade them to ext3 which is more stable thanks to journaling.
As far as I know, it's not possible to write to extX partitions from Windows. You can copy the files you need to the FAT partition and move them within the phone using Astro or other file manager.
You can mount the second ext3 partition from Terminal Emulator in Android like this:
$ su
# cd /sdcard
# mkdir SD2
# mount /dev/block/mmcblk0p3 /sdcard/SD2
Then it will be accessible from Astro in /sdcard/SD2.

i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?

Have also a swap as the fourth partition.. That doesn't matter, I think. Its only important, that the second ext3 is the third partition.
Heres my partition table:
fdisk -l /dev/mmcblk0
Code:
Disk /dev/mmcblk0: 1977 MB, 1977614336 bytes
255 heads, 63 sectors/track, 240 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000ac1bc
Device Boot Start End Blocks Id System
/dev/mmcblk0p1 1 64 514048+ b W95 FAT32
/dev/mmcblk0p2 65 131 538177+ 83 Linux
/dev/mmcblk0p3 132 223 738990 83 Linux
/dev/mmcblk0p4 224 240 136552+ 82 Linux swap / Solaris

olvap377 said:
i followed all the steps correctly but it just gets stuch at boot screen if i try to boot into recovery
any advice
maybe this has something to do with the fact that i have ebi1 phone?
pls help i really want this
EDIT:
wow im dumb i figured it out if u look at my sig ull see the way my partitions are setup
i followed all ur steps except each time i changed instructions from p3 to p4 becasue i also have a linux swap so when i installed this recovery it tried to boot from part3 which is my swap and obviously didn;t work
so vaskas can u please for everyone who has a linux swap release another recovery except that boots from part4?
Click to expand...
Click to collapse
Ok, try http://vaskas.ru/om-g1/openmoko-recovery-partition4.img - it should work.
I'll try to make a multiple-choice one soon.

thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice

olvap377 said:
thx alot il try when i get home from school
EDIT: still dosent work just freezes at boot screen
plzzzz help any advice
Click to expand...
Click to collapse
Do you mean you're stuck into the "G1" screen? If so, it's a recovery/kernel problem, not really connected with partitioning and stuff. I'm not sure if this openmoko kernel supports EBI1/32A, may be it's the problem

Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?

olvap377 said:
Well I have a dream which is 32b but with ebi1 radio I think this is the problem because amon_ra has a special recovery just for rogers dreams meaning something is different between them
If u could compare amon's rogers to normal recovery and find the differences could u chabge yours to make the latest part 4 file ebi1 compatible?
Click to expand...
Click to collapse
Frankly speaking, I don't think I'm going to have much time for this Since my radio is different, I won't be able to test it properly too.
Actually, I hope that more people join the thread so that we'll be able to solve much more problems together. I wonder where the guys from "Installing Debian on G1" are gone, I saw 2-3 people really interested in native Linux there.
Can you still rename the thread? If so, what do you think about appending something like " - Native OpenMoko and Debian" to it?
EDIT: compared Amon_Ra's recoveries in hex editor, they seem quite different

Dual Boot,Splitting Partitions

Can you dual boot or any other way to have 2 different roms installed at the same time,so i can switch back and forth?Like windows either at boot or logging in and out of 2 different desktops.
Maybe find a way to split the partitions.Any suggestions would be great.

Duel= 2 roms fighting. Make it dual. Thought it was funny, no malice intended.

lol - duel - dual...
It would be interesting if that was possible. There would have to be another program in there to act as the buffer between both OS's though - that would take control of the start-up, hold on a page that has both options and then would boot the option you want.
Not sure if that's possible since some files are right on the root and in order to have an OS work it can't have files in the same directory - they would just overwrite each other.
But, I too, have wondered if it would ever happen. Be a great way to test new ROM's if you didn't always have to overwrite the existing ROM but rather, you could place a new ROM in a special directory and then run it from that - or partition the internal memory with the new partition available to boot from and store.

partition the internal memory with the new partition available to boot from and store.
Click to expand...
Click to collapse
Thats exactly what i was thinking,partition the system os,i rebuild computers and a little system modding in windows,but this is a linux based os,so it would be a little odd for me.I'm gonna look into this a little more.

You may try to contact the guys who developed boot manager. www.init2winitapps.com they have a listing of supported devices and a request form. Works on the thunderbolt 5 slots for 5 roms, I'm unsure how difficult it would be to add support for the iconia.
Sent from my A500 using XDA Premium App

ibsk8 said:
You may try to contact the guys who developed boot manager. www.init2winitapps.com they have a listing of supported devices and a request form. Works on the thunderbolt 5 slots for 5 roms, I'm unsure how difficult it would be to add support for the iconia.
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
Thanks,i submitted the idea,lets see if they will run with it,hopefully they will find interest.

Hello Diabblo,
Any update on that?
I think the idea of dual boot (or 5al boot) is just fantastic!
I have beside my iconia a501 a poor old zt180s and it can triple boot on android, ubuntu and WinCE!
Best,
Inji.

inji75 said:
Hello Diabblo,
Any update on that?
I think the idea of dual boot (or 5al boot) is just fantastic!
I have beside my iconia a501 a poor old zt180s and it can triple boot on android, ubuntu and WinCE!
Best,
Inji.
Click to expand...
Click to collapse
Im guessing that device has a open non encrypted boot loader. The Iconia was encrypted at birth with the 3.2 push they tightened security even more from whqt I have read.So this is likely never happening unless acer changes ttjere boot loader policy.not likely to happen.
hope this helps you understand more of this issue.

I'm dual-booting my A500 right now with ICS and Ubuntu. The method for dual-booting is a replacement recovery.img which contains a Linux kernel and acts as a bootloader for Linux. Ubuntu itself runs from a rootfs.img on the internal storage (there's also recovery.img's available to run from external SD too). If I want to run Android, I just boot my tab normally. When I wanna run Ubuntu, I hold vol+ as I'm turning it on to force the modded recovery to load. It's a pretty cool setup more info in this thread: http://forum.xda-developers.com/showthread.php?t=1158260

Dear Erica Renee and Bloodflame,
Thanks a lot for your answers. Ok, I got it with the encrypted bootloader.
Will try the method described by Bloodflame.
Actually, since I got these tablets my main use of them is flashing new ROMs... I don't really have the use of new ROMs but I think it's so exciting!
Cheers,
Inji.

I don't believe the encryption is the problem.
The current boot loader is available unencrypted in update packages if anyone want to have a look at it.
Replacing the boot loader on the device is done as part of a down grade procedure described elsewhere on this forum.
So unless I'm missing something, the problem is more likely time and interest. Someone need to care enough about it and have the time to make some other boot loader work. Or patch Acer's. Either way it is likely to require quite a bit of time and patience.

So let me see if I have this correct. Acer's hardware bios code is 'locked down' enough to keep the average code manipulator out? A custom boot loader needs to be dev'd that can communicate correctly to be able to handle Android recovery and a linux/android boot screen etc. ? Could someone elaborate more blatantly if I am incorrect...

? Windows 10 on a WinBook TW800

I have a WinBook TW800 from Micro Center. I wanted to load Windows 10 on it, has anyone on here done this? Maybe you can give me tips\pointers on how to go about doing this; is the update method better or would a clean install be the ideal way? Thanks for your help in advanced.

Well I got my answer today while trying to do it via the update way. I got an error that my tablet wasn't able to upgrade because the OS is compressed something about Boot WIM. SMH.

sinister1 said:
Well I got my answer today while trying to do it via the update way. I got an error that my tablet wasn't able to upgrade because the OS is compressed something about Boot WIM. SMH.
Click to expand...
Click to collapse
I can help you install it, in fact, I can make a guide. I have the TW801 and everything is working properly.

TravisAntonio said:
I can help you install it, in fact, I can make a guide. I have the TW801 and everything is working properly.
Click to expand...
Click to collapse
Cool, I will appreciate it. Thanks.

Any luck on getting a guide posted

Sorry for taking ages, I totally forgot about this.
http://forum.xda-developers.com/windows-10/general/guide-install-windows-10-tw800-801-t3069958

is it for free?

Issues
I'm having issues too. I don't think the 800 has enough space to do the install. The 801 seems like a better option due to the 16gb of storage, vs the 8gb on the 800.

TravisAntonio said:
Sorry for taking ages, I totally forgot about this.
http://forum.xda-developers.com/windows-10/general/guide-install-windows-10-tw800-801-t3069958
Click to expand...
Click to collapse
I will try it this some time this week. Thanks.

No luck
Apparently I can't because the memory is full so I basically can't do anything with this POS. I can't back it up or restore it or add anything to it, it actually runs out of disk space when uninstalling stuff.

I successfully installed Windows 10 on my TW-801 I first installed internally (internal installation failed) and then installed again via the sdcard (so you have to burn the win image to the sdcard for the second install in addition to doing the download for the first install). The second time Windows 10 was activated. I am also running Ubuntu with VMWare on a virtual machine on this tablet. Windows 10 is alot better than 8.1 on this tablet. I think even though the internal installation fails it saves the Windows 10 activation code and the second install works because it is not a download and is directly from the cd or in this case the sd. Also, during the first download (that fails) two files are created on the c drive that I copied to the sdcard that I had already burned the win image on it - I don't know if that did anything or not.