Related
Hi there,
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.
1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.
After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.
Which IP to use to connect with OPAL I still must investigate.
Well ip connectivity now works:
ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>
Notas:/# ifconfig usb0 up 192.168.2.200 netmask 255.255.255.0
Listik:/usr/src/linux-2.6.27/Documentation# ping 192.168.2.202
PING 192.168.2.202 (192.168.2.202) 56(84) bytes of data.
64 bytes from 192.168.2.202: icmp_seq=1 ttl=64 time=2.95 ms
64 bytes from 192.168.2.202: icmp_seq=2 ttl=64 time=1.72 ms
And how to do it:
prolong "set CMDLINE" line with
ip=192.168.2.202:192.168.2.200:192.168.2.200pal:usb0
But in this image there doesn't seem to be any telnet/ssh server running. I will try cook image with ssh server support later
Download error
Were not able to re-upload
404 file not found error!!
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/
and open latest gizard-<date>.tar.bz2
or that I suppose.
The latest link should be http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20090703.tar.bz2
does this mean any chance of android working? anyone tried?
Hey,
I'm a new Opal user and I'm interested in getting *nix running on my device. I still haven't had the chance to mess around with this stuff but I'm excited to see this thread.
I was looking into the possibility of running Android on the Opal and it seems the closest thing is this thread bout running it on the Herald (it uses the same processor as the Opal).
I don't any experience in Linux porting so I thought I'd share this, in case anyone else is interested. And at the same time, I'll try to see if I can get something working based on what has been/is being done for other devices.
Sorry for the long post.
Hey Folks,
Any progress on getting Android on Opal? I am eagerly waiting to load one.
Kindly let me know, if this version of Linux when loaded, gives the UI.
Cheers'
Vijay
cijoml said:
Hi there
I got Linux to boot at OPAL via linwizard project. Here are steps needed to get it work.
1) download image from:
http://tinderbox.x86.dev.gentoo.org/embedded/linwizard/gizard-20080602.tar.bz2
2) copy content of file to the microSD card
3) edit default txt and replace init=/linuxrc with init=/bin/sh
4) run haret and let it boot.
After a while you'll get to shell. No graphics.
Now you can attach microusb cable and connect it with your linux laptop (I recommend ubuntu)
and you will get usb0 interfece to start up.
Which IP to use to connect with OPAL I still must investigate.
Click to expand...
Click to collapse
Android can boot on Opal
I have some good news, Android can boot on the Opal. This is just a proof of concept as it's missing tons of drivers and is completely useless.
Touchscreen and all keys except for the volume control (and obviously the reset button) are not working. So you basically can't do anything when you run it.
What I tried is the same as what's written in this thread about running Android on Gene. They're using the build made for the Herald/Wing (just as I was proposing in my last post) with customized initramfs and kernel.
You'll find all the necessary details in that thread. However, there's a newer build than the one mentioned there it's wing-linux-0.4pre2.cab. And the suitable kernel for that build is supposed to be the pre2 posted in this post but it didn't work on my Opal so I tried the older Gene kernel and it worked. The main difference between the two is bluetooth support, and that's obviously is of no use for us.
This doesn't effect the Windows rom, nor does it requires any special partitioning. Still it's best to have everything backed up before launching it, just in case.
This is the official site for the wing/herald build:
http://wing-linux.sf.net/
This thread on their forums about the Gene port will probably be of use to us:
http://sourceforge.net/apps/phpbb/wing-linux/viewtopic.php?f=4&t=4
I'm reading about the next steps but as I said before, I don't have any previous experience or knowledge about this type of things. If someone can give me hand, I would be more than grateful. At any rate, once I have better understanding of the concept I'll contact the people behind the Wing and the Gene ports.
P.S: If you do try to run this, keep in mind that this will take lots of time, specially for the first launch. And when you get an error saying something like "android sh: can't access tty" just ignore it and keep waiting. After a while you'll have a flashing "android" on the screen, and after some more waiting you'll reach the main screen.
Is this just THE BEGINNING
Sooper Stuff..!! So is this just THE BEGINNING??
How do we port the drivers and other required information in the build?
Cheers'
Vijay
www.msigeek.com
A Lil' help
I'm going through the Gene port thread here and on the Wing-linux sourceforge forums but I'm still a bit overwhelmed.
I would appreciate any help as I'm completely new to porting. I have some programming and linux knowledge but never attempted this type of things.
Click to expand...
Click to collapse
So am I.
Hmmm...
Right. Lets do it the way I did it.
1. Get the touchscreen working. Through HaRET, you must have got the GPIO interrupt whenever you pressed the touchscreen. You must have got two numbers corresponding to each press - a smaller number and a bigger number. The smaller number is the GPIO, and the larger number is, well, lets say a special GPIO value for the same pin.
Now checkout the Gene branch through git.
Goto /wing-linux/kernel/arch/arm/mach-omap1/board-htcherald.c
Scroll down to a block of code where you'll see the touchscreen code. Enter the smaller number in the .dav_gpio statement, and the IRQ number in the OMAP_GPIO_IRQ() statement below.
2. Follow the Kernel build instructions on the development section of the wing-linux wiki (the two make commands)
Copy the zImage into the linux folder on your SD card
Boot into wing-linux. The touchscreen should start working.
3. Now, hopefully, after the touchscreen's working, You would essentially just require two more buttons - the home button and the back button for minimum functionality. Everything else can be worked on by the touchscreen.
Then follow the instructions on the wing-linux forum (Page 2) to get the KEY(row,col) values of the keys on your handset. Hopefully you should get atleast a couple. Note down the corresponding keys and their KEY(r,c) values output.
4. Fire up board-htcherald.c again and goto the place where you have the KEY(r,c,KEY_blah) thing and replace the codes as per your obtained KEY(r,c,KEY_blah) values (The Home button is the one commented as Left Button)
5. That's all I can help you with as of now. I'm also figuring out a stable way of getting the DPad and the center select key to work, but It'll take some time.
Thanks kshaurya!
(This guy right here is the one who fixed the kernel for Gene, I asked him for some pointers).
I don't want to take my device apart just yet (I usually do my best not take to dismantle anything that I haven't owned for at least 3 months unless absolutely necessary) and I couldn't find a place that states what touchscreen it uses. I'm just hoping that it's the same a tsc2046 as well. [Is there anyone without a warranty and/or willing to check for us?]
I'm gonna double check the values I got from the touchscreen as for some reason I seem to have to IRQ values, probably forgot to get rid of some spamming irq. And, at the same time, I'm currently setting up a VM as a building environment, my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines.
If anyone else have some experience and wants to try this, refer to: http://www.handhelds.org/moin/moin.cgi/HaRET_20Documentation (using haret to get the GPIO and IRQ values needed).
And to:
http://sourceforge.net/apps/trac/wing-linux/wiki/Development (acquiring the source code from Wing Linux and how to build it).
And a quick question for anyone that tried booting Android on the Opal, what screen did you get when Android finally finished booting?
I don't want to take my device apart just yet
Click to expand...
Click to collapse
Huh? where did that come from? Wing Linux will not touch your WM.
I seem to have to IRQ values
Click to expand...
Click to collapse
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.
my main boot is Intrepid 64 and there's no 'psyco' package for 64 machines
Click to expand...
Click to collapse
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.
kshaurya said:
Huh? where did that come from? Wing Linux will not touch your WM.
Click to expand...
Click to collapse
I mean to check the screen, in case it turned out to be different that what you have.
kshaurya said:
Do you mean two? Well, that's exactly what you should get. Even if it's just one, enter that value in the code.
Click to expand...
Click to collapse
Yeah, stupid typo.
I noticed now that one of them appears when I keep the screen 'touched' for a bit longer.
kshaurya said:
Oh no. dont tell me that you are building the entire thing. all you need to do is build the KERNEL! Please! Don't go into building the whole thing from scratch. Use the make ARCH ARM commands given on that page.
Click to expand...
Click to collapse
I'm not gonna build the complete thing. Seems like I got too exited and failed to notice that building the kernel only requires a cross-compile toolchain, te rest is for compiling the whole thing.
I'm not THIS stupid usually . Honestly!
Thanks again!
I'm not THIS stupid usually . Honestly!
Click to expand...
Click to collapse
Its pretty normal
Weird.
I've only changed the two touchscreen values and built the kenrel. It finished without any error but now it won't boot.
It gets stuck, even before the space allocation part, with this error: "sh: can't access tty; job control turned off". And then it displays a prompt.
I'll try modifying an older build, I'm pulling them from the repos at the moment.
After all, the pre2 kernel from Gene didn't boot on my device (although it got stuck later on).
Try doing a clean install - Remove the linux folder and try again.
Also, make sure that you're not forgetting to checkout the Gene branch.
Code:
git checkout Gene
Is your default.txt modified? And have you downloaded the modified initramfs.cpio?
check in the Gene forums for that.
Already tried the clean install, no dice. The default.txt is untouched and I'm using the modified intramfs. What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command. I could probably ssh via usb but I have no clue how that might help.
And I've already checked out the Gene branch from the beginning.
I've tried compiling the kernel for pre1 (after changing the screen values) from SVN and it did boot (both using the cabs for pre1 and pre2) but no touch screen yet. All in all, I'm guessing that there's too much hardware difference here.
And the button for lowering volumes didn't work either, it seems like whatever you changed for getting it to work on Gene is the same as what we need here, but I'll think about that later.
I only have two ideas left:
- Trying to go back to a more stable build (with lesser features and lesser possibilities for errors). Maybe 0.3.
- Trying to create some kind of hybrid kernel using this alongside the HTC Vogue build as it probably has closer hardware to the Opal (obviously, I'm talking about everything beside the MSM7500 400MHz processor that it has). I'm hoping it won't get to this cause I'm definitely under qualified for that at the time being.
What happened this time is different from what happens using the original one, it's not asking me to specify the partition size but instead it's waiting for a command.
Click to expand...
Click to collapse
Could you post a screenshot?
I've tried compiling the kernel for pre1 (after changing the screen values)
Click to expand...
Click to collapse
I'm assuming you mean the touchscreen values? Try interchanging and see.
Trying to go back to a more stable build
Click to expand...
Click to collapse
I wouldn't recommend that. Defeats the whole purpose.
Why don't you try getting in touch with darkstar?
kshaurya said:
Could you post a screenshot?
Click to expand...
Click to collapse
A friend borrowed my digital camera, I tried my laptop's webcam but the text it too blurry. Couldn't fix it using gimp either. So here's exactly what's showing on the screen:
Code:
mdir: Cannot creat directory `/mnt' : File exists
modprbe: could not parse modules.dep
initramfs: Creating device nodes:
initramfs: Loading /initrd.d/10-initfs.sh module
initramfs: Loading /initrd.d/30-wingboot.sh module
Selected:
ROOT_DEVICE=/dev/
CMDLINE=debug quiet psplash=false loglevel=7 init=/sbin/init console=tty0 video=omapfb:accel fbcon=rotate:3 4 root=/dev/
initramfs: Loading /initrd.d/80-loopboot.sh module
initramfs: Loading /initrd.d/85-blockboot.sh module
booting from: /dev/
mount: Mounting /dev/ on /mnt failed: Invalid argument
Unable to mount rootfs device
sh: can't access tty; job control turned off
/ $
And after the prompt, on the same line, there's a flashing '_' waiting for input.
Using the original zImage (from the pre2 cab) it's right around here that the screen clears and the Wing Linux installation script kicks in.
kshaurya said:
I'm assuming you mean the touchscreen values? Try interchanging and see.
Click to expand...
Click to collapse
Will try that next.
kshaurya said:
I wouldn't recommend that. Defeats the whole purpose.
Click to expand...
Click to collapse
I meant it as just a temporary test to till the cause of the incompatibility is figured out. With less things that could go wrong, it'll be easier to locate the ones that are going wrong.
kshaurya said:
Why don't you try getting in touch with darkstar?
Click to expand...
Click to collapse
You're right. I should post a thread on the project's forums asking for his help.
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
Some PPL on the development forums were asking how to boot $auron's UrukDroid out of bubu's openAOS Boot Menu. Since i can't post there yet, i'll post here.
I looked at bubu's initramfs/init script and it should be fairly easy to boot any partition as well as any rootfs.img.
the menu.lst syntax is:
Code:
{NAME(has to be unique)}|{DEVICE(leave blank for img)}|{IMG}|{INIT}
A special thing is putting 'ARCHOS' into {DEVICE}, because that will boot from ARCHOS' stock SQUASHFS file
so adding this line to menu.txt should let you boot UrukDroid from sdcard
Code:
UrukDoid|/dev/mmcblk2p2||/sbin/init
I have to add, i havn't tried it myself yet, because i haven't put bubu's loader on my A70IT yet.
I would really appreciate you letting me know if it works!
Greetings Oro
Orochimarufan said:
Some PPL on the development forums were asking how to boot $auron's UrukDroid out of bubu's openAOS Boot Menu. Since i can't post there yet, i'll post here.
I looked at bubu's initramfs/init script and it should be fairly easy to boot any partition as well as any rootfs.img.
the menu.lst syntax is:
Code:
{NAME(has to be unique)}|{DEVICE(leave blank for img)}|{IMG}|{INIT}
A special thing is putting 'ARCHOS' into {DEVICE}, because that will boot from ARCHOS' stock SQUASHFS file
so adding this line to menu.txt should let you boot UrukDroid from sdcard
Code:
UrukDoid|/dev/mmcblk2p2||/sbin/init
I have to add, i havn't tried it myself yet, because i haven't put bubu's loader on my A70IT yet.
I would really appreciate you letting me know if it works!
Greetings Oro
Click to expand...
Click to collapse
First:
Thanks for your work
Would this also work, with on internal installed urukdroid?
You would have to get the device name of your root partition
since mine is a sdcard install i can only provide that information.
but if you can boot into uruk right now you can do the following to get the device node:
Open any terminal emulator and type:
Code:
cat /etc/mtab
then search for
Code:
<device> / <fstype> rw,noatime,barrier=1,nodealloc,....
in my case that is:
Code:
/dev/mmcblk2p2 / ext4 ....
take the first one (<device>) and put it into the menu.lst line:
Code:
UrukDroid|<device>||/sbin/init
still i haven't tested any of this. it's just the result of my looking at the bootloader's init script
Greetings oro
Orochimarufan said:
but if you can boot into uruk right now you can do the following to get the device node
Click to expand...
Click to collapse
I cant i installed the openaos boot menu, so urukdroid is gone...
I really want to have uruk again, i hate the stock firmware
I know these steps, but is there no way to compile a *.img from uruk?...
i compiled one but these dont worked...
first of all IMO putting Uruk into an image file would be stupid,
second you'd have to either find a way to run the installer on your computer, or ask $auron what exactly it does and put a working rootfs togehter manually or dump an existing thing
your best bet would be to boot openAOS and dd Uruk's Root Partition into some img file. But since you don't know which yout Uruk Root is and i don't either, only thing left would be to ask $auron where he installs it. and if you know that, you can use my method just as well
greetings
Orochimarufan said:
Only thing left would be to ask $auron where he installs it. and if you know that, you can use my method just as well.
Click to expand...
Click to collapse
Okey, i`ll do
Then i have to install urukdroid and after that install the openaos boot menu?
Nope
if you've got the device node of yout Uruk root you should be able to put it into that menu.lst lint i showed you where <device> is.
Just to mention it, I don't know if $auron provides a working live-initramfs, but if he does you should be able to simply flash that through the sde recovery menu.
by live-initramfs i mean one, that doesn't launch EasyInstall but run UrukDroid directly.
greetings
Orochimarufan said:
Nope
if you've got the device node of yout Uruk root you should be able to put it into that menu.lst lint i showed you where <device> is.
Click to expand...
Click to collapse
Yeah, i understand that.. but how do i install uruk?...
sorry i dont understand
Just to mention it, I don't know if $auron provides a working live-initramfs, but if he does you should be able to simply flash that through the sde recovery menu.
by live-initramfs i mean one, that doesn't launch EasyInstall but run UrukDroid directly.
greetings
Click to expand...
Click to collapse
i aksed sauron per pm
Hmm.. how do i explain.
It's like this:
the device node is like a link to the partition.
If you put Uruk on a Partition, you have to tell the bootloader which partition is the right one, the one with Uruk on it.
The bootloader then searches for an init-file there and executes it
so bubu's menu is the bootloader in this case, so you tell him where he has to search for Uruk by putting the right device node into the menu.lst.
hope you understand it a little better now
greetings
Orochimarufan said:
Hmm.. how do i explain.
It's like this:
the device node is like a link to the partition.
If you put Uruk on a Partition, you have to tell the bootloader which partition is the right one, the one with Uruk on it.
The bootloader then searches for an init-file there and executes it
Click to expand...
Click to collapse
Yes, so first i have to install Urukdroid, because if i dont, bootloader doesnt find anything or not?
so bubu's menu is the bootloader in this case, so you tell him where he has to search for Uruk by putting the right device node into the menu.lst.
hope you understand it a little better now
Click to expand...
Click to collapse
Yep, thanks
I´m still a bit new in booting
Nope, because you installed it already.
You said you had an existing installation on your internal memory, didn`t you?
You just have to find out where it is. And tell that information to the bootloader.
Greetings
TapaTalk on A70IT here -- who's there?
Orochimarufan said:
Nope, because you installed it already.
You said you had an existing installation on your internal memory, didn`t you?
You just have to find out where it is. And tell that information to the bootloader.
Click to expand...
Click to collapse
I had have a Urukdroid installation, before i installed the boot menu i completly wiped my archos for a completly frsh install
Okay then youre right. If there's nothing he obviousli cant execute anything.
So if yuo installed it again, would you be kind enough and report back the device node?
Greetings
TapaTalk on A70IT here -- who's there?
Orochimarufan said:
Okay then youre right. If there's nothing he obviousli cant execute anything.
So if yuo installed it again, would you be kind enough and report back the device node?
Greetings
TapaTalk on A70IT here -- who's there?
Click to expand...
Click to collapse
Yep, but i dont do it today, its getting late (school)
I`ll do it tomorrow, thanks for your help!
Yeah youre right and i've to go to school tomorrow too... an a friend of mine is goong to write her final exams in english... guess i'm going to have more than just this problem tomorrow
Just so you know, we'll visit some relatives this weekend, so i wont be here then.
Greetings
TapaTalk on A70IT here -- who's there?
Orochimarufan said:
Yeah youre right and i've to go to school tomorrow too... an a friend of mine is goong to write her final exams in english... guess i'm going to have more than just this problem tomorrow
Just so you know, we'll visit some relatives this weekend, so i wont be here then.
Greetings
TapaTalk on A70IT here -- who's there?
Click to expand...
Click to collapse
Okey, i'll try it and i'll see
another question: any idea how to get the menu booting instead of normal archos android?
(Sde instead of archos, like sauron did at urukdroid)
What exactly do you mean?
Like switching between custom and stock?
That'd be for hold voldown while the archos bootscreen shows up and selecting SDE or Android.
And the SDE entry will launch whatever you put there through the SDE recovery Menu
Greetings
TapaTalk on A70IT here -- who's there?
No, he mean booting on it not by going in the recovery menu, just on pushing the "ON" button.
eagleofdeath13 said:
No, he mean booting on it not by going in the recovery menu, just on pushing the "ON" button.
Click to expand...
Click to collapse
Yep, this will be helpful, when i have urukdroid on my boot menu, because then my normal use will be uruk, until cyanogen is ready for saily use..
Any hints on that?
I don't really know, but doesn't it remember your last choice?
TapaTalk on A70IT here -- who's there?
Hello all!
I've run ICS image from letama on my Archos 101IT gen8 sucessfully.
Here is my image: recovery.img
This image sucessfully runs with zImage and initramfs from OpenAOS Bull, just add recovery.img to menu.lst
In letama's image 101's touchscreen works as a mouse or touchpad, in my image it works as touchscreen and support multitouch (e.g. in Google Maps)
Wifi works.
Battery meter, working as USB drive and not working for now. If you know how to setup this stuff please tell me.
Yes, can get it to boot and connect to wifi - but thats about it.
Wish I knew where to start in trying to get it working but have no idea about kernels or android OS.
CUrrently I'm trying to get battery meter work and set default orientation in normal mode (not upside down). I think it can be done without kernel recompile, just with *.img editing.
Also, there is issue with default browser - when you trying to launch it with network connection, all the system hungs up. Guys from OpenAOS tell me to do that - you must launch Browser WITHOUT any network connections and disable location requests in settings. But it not works for me because I cannot enter this settings
skayred said:
Hello all!
I've run ICS image from letama on my Archos 101IT gen8 sucessfully.
Here is my image: recovery.img
This image sucessfully runs with zImage and initramfs from OpenAOS Bull, just add recovery.img to menu.lst
In letama's image 101's touchscreen works as a mouse or touchpad, in my image it works as touchscreen and support multitouch (e.g. in Google Maps)
Wifi works.
Battery meter, working as USB drive and not working for now. If you know how to setup this stuff please tell me.
Click to expand...
Click to collapse
Would love to get this working but not sure what to add into the menu.lst and do I just place the recovery.img on the root of the internal memory?
At the mo I am running OpenAOS Bull RC2 CM7
skayred said:
CUrrently I'm trying to get battery meter work and set default orientation in normal mode (not upside down). I think it can be done without kernel recompile, just with *.img editing.
Also, there is issue with default browser - when you trying to launch it with network connection, all the system hungs up. Guys from OpenAOS tell me to do that - you must launch Browser WITHOUT any network connections and disable location requests in settings. But it not works for me because I cannot enter this settings
Click to expand...
Click to collapse
For the upside down stuff guess you could just ask the openAOS team as the CM7 builds are not upside down?
zacthespack said:
Would love to get this working but not sure what to add into the menu.lst and do I just place the recovery.img on the root of the internal memory?
At the mo I am running OpenAOS Bull RC2 CM7
Click to expand...
Click to collapse
by bad got it working now and love it!!!
Awesome, need to test this on my A43, Letama's image worked but also had the mouse problem. Make sure you only make the screen upside-down for A101, as the other gen8's have the screen oriented correctly (not sure why they made the A101's panel upside down).
EDIT:
On A43 it still acts as a mouse. You should set up a Git repository for your modifications to ICS as I'd like to look into it and get it working with A43 as well. Also, would be nice to try to compile changes against CyanogenMod's CM9 ICS release which has additional features than AOSP ICS.
In my menu.lst file i have added
ICS||/ics.img|/init|1
I renamed the recovery.img to ics.img - just so I can remember what its is
ArcSmurf said:
In my menu.lst file i have added
ICS||/ics.img|/init|1
I renamed the recovery.img to ics.img - just so I can remember what its is
Click to expand...
Click to collapse
zacthespack said:
Would love to get this working but not sure what to add into the menu.lst and do I just place the recovery.img on the root of the internal memory?
At the mo I am running OpenAOS Bull RC2 CM7
Click to expand...
Click to collapse
In my menu.lst I've done this:
HTML:
ICS||/recovery.img|/init|0
And put recovery.img to device internal root
I'll set up Github repository soon and post URL. About OpenAOS guys - they are recommend to do some stuff with orintation settings, I'll do it as soon as possible
I grinned in joy as my IT finally booted ICS Lots of bugs (mainly everything you touch force closes) but its booting and the touchscreen works (LIKE A TOUCHSCREEN!)
Great work :] love to test more of this
The touchscreen doesn't work. help please
It just doesn't react
Dosn't work
1.Fresh reformated
2.install Stock 2.4.82
3.install Dev Edition
4.flashed zimage and initramfs.cpio.gz from kernel_gen8_20111224_213037
5.edit the menu.lst add "ICS||/recovery.img|/init|0"
6.at my root i have your /recovery.img
so all should work but it doesn't
it doesn't boot
On a old install i have image from letama working with no real touch -.-
and i have test you build the same but its boot ...
What make i wrong ...
AlphaTime said:
Dosn't work
1.Fresh reformated
2.install Stock 2.4.82
3.install Dev Edition
4.flashed zimage and initramfs.cpio.gz from kernel_gen8_20111224_213037
5.edit the menu.lst add "ICS||/recovery.img|/init|0"
6.at my root i have your /recovery.img
so all should work but it doesn't
it doesn't boot
On a old install i have image from letama working with no real touch -.-
and i have test you build the same but its boot ...
What make i wrong ...
Click to expand...
Click to collapse
make sure you have a 'break' i.e press enter after the last line in the menu.lst, i forgot this and it wouldnt boot but after adding it all was fine
The line break must be a UNIX-format line break (yes, there's a difference!). If you use Notepad/Wordpad in Windows it probably won't work. Load it up in gedit or any other program that lets you select the line break format or just use a Linux machine (though on Linux there are programs that allow you to do DOS-format break just as you can do UNIX breaks on Windows). If all else fails, start over or just temporarily rename your old image and new image accordingly.
Ok testing to edit it in Unix mode of Notepad++ dosnt work
then use Ubuntu and gedit dosnt work
So I have a request can someone have it working can upload his Menu.lst pls
Here is my file - note I have renamed the ICS image to ics.img and not recovery
... booting looks fine, but can't unlock ...
Hi all,
realy facinating to ICS on the 101IT ;-), but i couldn't get it further than the locking screen :-(.
I'm running kernel and initrd from the latest openAOS release (Bull) from 2012.04.09.
When i touch the panel, i see a blue circle, moving my finger moves this blue circle ... but not the unlock icon ...
Ciao
Kurt
Kurt Krummbein said:
Hi all,
realy facinating to ICS on the 101IT ;-), but i couldn't get it further than the locking screen :-(.
I'm running kernel and initrd from the latest openAOS release (Bull) from 2012.04.09.
When i touch the panel, i see a blue circle, moving my finger moves this blue circle ... but not the unlock icon ...
Ciao
Kurt
Click to expand...
Click to collapse
Same pb with A70IT2 under Froyo, i thank that is the driver was wrong, but i doubt now.
Boot without pb, but cannot unlock the screen....
Bizcuite
bizcuite said:
Same pb with A70IT2 under Froyo, i thank that is the driver was wrong, but i doubt now.
Boot without pb, but cannot unlock the screen....
Bizcuite
Click to expand...
Click to collapse
me too
Downloading right now. Im really excited get ics booting on my device....
Edit: wow booting real fast. On my 101it touchscreen works but has blue circle pointer.
Got no dev skills, but will help or test wherever i can. Really want to run ics on my tablet in future, such an eyecandy os
Great work thnx.
Gesendet von meinem A101IT mit Tapatalk
ICS Running on 101IT 8g.
No bluecircle pointer. A lot of app crash. Unable to set a wallpaper but a live one.
Most parameters are unreachable but using widgets you can get in, that seem's that it's changing category wich crash. I have been able to turn language as French this way.
I may activate debuging if I know how to use it, and if logs can be usefull to anyone.
Great work !
Kurt did you try to move the unlock icon ? sorry if I misunderstand, but else, you have to move the blue circle on the unlock icon.
hello
For the past few weeks i have been working on porting sailfish os to the LG Aristo 2. Its been a pain too as i had no idea where to start. Any ports to lineage or otherwise never got past boot and after a some searching i could not find a repo.
Any way i have managed to accomplish building a repo on github where curious folks could look me up by my handle. I originally started the project to boot native ubuntu on an sd like the v10 and v20.
But now i have backed myself into a corner. i have been compiling the systemD kernel using msm-3.18 source thats been upstreamed for two weeks now and i still cant get a boot.img that wont boot straight to fastboot.
can some one please help me accomplish this task.
then maybe we can move on to the build errors
Duhjoker said:
hello
For the past few weeks i have been working on porting sailfish os to the LG Aristo 2. Its been a pain too as i had no idea where to start. Any ports to lineage or otherwise never got past boot and after a some searching i could not find a repo.
Any way i have managed to accomplish building a repo on github where curious folks could look me up by my handle. I originally started the project to boot native ubuntu on an sd like the v10 and v20.
But now i have backed myself into a corner. i have been compiling the systemD kernel using msm-3.18 source thats been upstreamed for two weeks now and i still cant get a boot.img that wont boot straight to fastboot.
can some one please help me accomplish this task.
then maybe we can move on to the build errors
Click to expand...
Click to collapse
You should go to IRC #sailfishos-porters, there you will find help from Jolla developers and from community
well i guess theres no help any where. the folks at telegram completely ignore me and are rude as f and if you say any thing about it they say you ate spamming for and claim you are the rude one. ive been ganged up on several times. irq doesnt seem to have enough people to help and i feel all hope is lost at this point.
on the other hand i have built a the whole rom completely and several times over but i cant get it installed and dont know how to see if the kernel works
ok im gonna keep trying to get help from here. I have gotten more help and made it farther in my abilities because of the help and info from this place than any other. Thank you
So this is where i am at. i have compiled Halium\Ubuntu touch several times over and worked it out with no compilation errors and including all of my sources.
But i cannot get it to ssh or telnet. I have followed all of the installation documents and i can see that its pulling the system.img and rootfs to data. i have entered my password on prompt its generated and pushed the rsa keys and every thing. but no go
i have checked the dmsg and kmsg after the attempts and no errors are reported.
so now im trying to go the route of the V20. I have an arm ubuntu 18.04 rootfs that i have unzipped and built up on the 2nd partition of my external sd. i installed every thing needed to build a kernel and any thing else i might need. i have msm-fb-refresher compiled and installed. I also have dev sys and proc mounted bound and and have made the devices using MAKEDEV. But when i try to build the kernel on my aristo 2 in the chroot i get these weird graphics characters and i have to restart my terminal to get my characters back.
in the mean time i compiled the kernel on my pc and had the modules installed to the chroot outside the android device and used update-initramfs to create an initrd.img exteacted it and made a boot.img that i put in the boot directory and installed to laf.
it will not boot stiil from laugh and goes to bootloader. but if i tell the chroot to reboot i get the error system cannot reboot with systemD as init cannot operate.
ok well still no help at any of the halium/ubuntu touch forums or telegram. But the bot said there was no kernel errors.
i have been looking at the lg v20 native ububtu mate rootfs and also the ectracted boot.img contents and i just dont know what it is thats causing it not to boot