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.
This might be in another thread. I searched pretty extensively for an answer and can't find one. Is there an app or way to install exe files and run them on my Magic 32B? My phone is rooted and running Cyanogen's 4.2.5 I figured my phone does everything else, why shouldn't it be able to run exe files?
Sorry for the bump. I can access the exe file on my memory card with Linda File manager, but I don't know what the open the file with??? Linda File Manager gives me the option to > Open With... Any ideas?
Android cannot open Windows based files.......
WEAK!
One thing I have learned from xda is that if theres a will theres a way! Comon guys there has gotta be a way!
Android is not windows..
In theory you could port qemu or something and run it in that. But that would be so slow a turtle would think of itself as fast if it saw it
Sent from my Gingerbread on Sapphire using XDA Premium App
tvall said:
Android is not windows..
In theory you could port qemu or something and run it in that. But that would be so slow a turtle would think of itself as fast if it saw it
Sent from my Gingerbread on Sapphire using XDA Premium App
Click to expand...
Click to collapse
Agreed. I want to say someone got Wine to install in Android but could never get it to work right.
Sent from my LG-P500 using Tapatalk
The idea is sweet and innocent but is much more complex...
The "exe" files are binaries. The .exe extension is something windows has as a standard for postfix, and is not necessary for running binaries (linux does not use any postfix and therefor also Android).
So what is a binary?
It's a list of machine instructions which the intended cpu understands. Every cpu has it's own instruction set ( a language). You need to make sure that the list of instructions you are running can be understood by the cpu. Inside this list you will find special instructions which is called "system calls". They are not intended for the cpu but for the operation system which you are running on.
So to sum up;
1) to run windows binaries on Android you need to change to instruction set of the binary because the cpu you have is not the same as those running on the Android device. E.g. x86 cpu on computer vs. ARM cpu on mobile devices vs. PIC micro-controllers. So the binary does not speak the same language as the cpu.
2) You need to change the system calls because Windows and Android does not have the same system calls.
So as a final sum up, it's not easy to make those binaries to run on Android, specially those which has a instructions list bigger than 20-30 instructions... They are just to complex and sometimes not even possible!
The WINE project is shot of doing the exact problem. It will run the binaries and translate them on the fly for the operating system. It succeed most times and fail others. But it's a HUGE project and need a normal computer power for it to run. The devices we have right now, does not have the horse power to run such projects.
I hope the info shades some lights on the problem :0)
NB: i know some of the info is not 100% but it's REALLY simplified to give the general idea and complexity of the problem :0)
mumilover said:
The idea is sweet and innocent but is much more complex...
The "exe" files are binaries. The .exe extension is something windows has as a standard for postfix, and is not necessary for running binaries (linux does not use any postfix and therefor also Android).
So what is a binary?
It's a list of machine instructions which the intended cpu understands. Every cpu has it's own instruction set ( a language). You need to make sure that the list of instructions you are running can be understood by the cpu. Inside this list you will find special instructions which is called "system calls". They are not intended for the cpu but for the operation system which you are running on.
So to sum up;
1) to run windows binaries on Android you need to change to instruction set of the binary because the cpu you have is not the same as those running on the Android device. E.g. x86 cpu on computer vs. ARM cpu on mobile devices vs. PIC micro-controllers. So the binary does not speak the same language as the cpu.
2) You need to change the system calls because Windows and Android does not have the same system calls.
So as a final sum up, it's not easy to make those binaries to run on Android, specially those which has a instructions list bigger than 20-30 instructions... They are just to complex and sometimes not even possible!
The WINE project is shot of doing the exact problem. It will run the binaries and translate them on the fly for the operating system. It succeed most times and fail others. But it's a HUGE project and need a normal computer power for it to run. The devices we have right now, does not have the horse power to run such projects.
I hope the info shades some lights on the problem :0)
NB: i know some of the info is not 100% but it's REALLY simplified to give the general idea and complexity of the problem :0)
Click to expand...
Click to collapse
Just in addition, most programs aren't just based on the .exe file. DLLs and other files are needed for the program to run, attempting to port all this stuff to Android would most probably result in failing.
K3n H1mur4 said:
Just in addition, most programs aren't just based on the .exe file. DLLs and other files are needed for the program to run, attempting to port all this stuff to Android would most probably result in failing.
Click to expand...
Click to collapse
I just hope Android is so popular that, like turning Windows into Linux using Wine (excuse the metaphor or whatever that was), someone might persist with this no doubt huge endeavour. I'm sure I'm not alone in wanting to never run a Windows app in Windows ever again, nor kowtow to Apple's interface demands even though I'd like something as responsive, integrated and occasionally useful as an iSomething.
Android was my future salvation till my employer handed over a handy Win App recently that I can't really avoid using - well I could, but I'd have to work that much harder - fat chance! So I'm stuck with a Samsung XP netbook and WM6.5 on my HTC Touch HD until someone somewhere, or lots of someones everywhere, do a Wine for Android
Seriously, you want to pretend in some reality somewhere that someone will first create an x86 emulator for an arm chip that barely likes to play xvid files then on top of that use wine to run a mobile windows app rather than just use something similar or pay someone to write you something similar that runs natively on android?
Which do you think is the non-insane option?
you cant run it on android persay but you can download dosbox and run it that way sorry for the bump
work for now
For now install your exe app on a windows PC if you have one. And run something like team viewer. Won't look the best but you'll get basic function out of it.
Thanks for the suggestions (cellsafemode excepted! )
I ended up buying a couple of iPads and have installed VMWare View, ICAB HD and Slashtop/CamCam giving remote access to my Windows PC at home. Gets the job done - bit slower, but the small Windows-only app I need to run infrequently isn't a huge load on the hardware or the network. Saves carting a netbook around for just one small but important task, and I guess it's accomplishing much the same as the Android suggestions above. When my iPad enthusiasm wears off, I'll have an Android option
Found a Way
Ok, I got a way! You need root, and itll be very slow on a phone but faster on a tablet!!
http s : / / play . google. com / store / a pps / de tail s? id = com . galoula.LinuxInstall&feature=search_result#?t=W251bGwsMSwyL DEsImNvbS5nYWx vdWxhLkxpbnV4S W5zdG FsbCJd
1)Download Above Link remove spaces
2)On your new Ubuntu or whatever you chose get wine from winehq
3)Get your exe and presto!!
--DISCLAIMER--
I havent tried it so if it breaks your phone/tablet its not my fault... USE AT OWN RISK
nikhiljha said:
Ok, I got a way! You need root, and itll be very slow on a phone but faster on a tablet!!
http s : / / play . google. com / store / a pps / de tail s? id = com . galoula.LinuxInstall&feature=search_result#?t=W251bGwsMSwyL DEsImNvbS5nYWx vdWxhLkxpbnV4S W5zdG FsbCJd
1)Download Above Link remove spaces
2)On your new Ubuntu or whatever you chose get wine from winehq
3)Get your exe and presto!!
--DISCLAIMER--
I havent tried it so if it breaks your phone/tablet its not my fault... USE AT OWN RISK
Click to expand...
Click to collapse
Good luck finding wine compiled for arm and some windows programs built for the (currently nonexistent) arm version of windows
2Noob4U said:
This might be in another thread. I searched pretty extensively for an answer and can't find one. Is there an app or way to install exe files and run them on my Magic 32B? My phone is rooted and running Cyanogen's 4.2.5 I figured my phone does everything else, why shouldn't it be able to run exe files?
Click to expand...
Click to collapse
if your mobile does everything else then can you do multitasking just like people do in Nokia N9??
yes its possible ..
ohhh yaaa its possible to install .exe file on any android device ..
just follow these simple steps and you are done :
Step 1
Install a DOSBox app on your Android device. AnDOSBox, aDosBox and DosBox Turbo are three different DOSBox apps available from the Google Play store.
Step 2
Open the DOSBox app.
Step 3
Type "cd \foldername" into the command line, where "foldername" denotes the folder in which your EXE is contained. For example, if your EXE is in the Download folder, type "cd \download."
Step 4
Click Enter on your Android keyboard.
Step 5
Enter the name of the EXE file. You do not need to enter the .exe extension.
Step 6
Tap "Enter" on your Android keyboard.
Tip
The command-line interface is not case-sensitive.
mydevilace said:
ohhh yaaa its possible to install .exe file on any android device ..
just follow these simple steps and you are done
Click to expand...
Click to collapse
Excellent! Never say 'Never'!
I also see it's possible to run iOS apps on Android as well.
Wing Nut said:
Excellent! Never say 'Never'!
I also see it's possible to run iOS apps on Android as well.
Click to expand...
Click to collapse
yeaaahhhhh
Sent from my Micromax A110 using XDA Free mobile app
So this confirms exe files r able to run on Android its just slow . Only thing left to do is find a way to lighten it up some by reduced graphics n bmp files ?
Hi,
I am new to the android development and a bit confused from all this (root, no root etc).
Say I want to write a new kernel driver to handle keyboard input, and want it to run only on my phone. And my phone is not the developer phone, nor exploitable for root privilege escalation.
Can I download the source files and compile a new kernel with my driver? I guess I cannot use the Android sources, but need my phone specific branch. e.g if I own an HTC Hero I need to get the specific sources from HTC, and they don't publish kernel sources for all their models...
But if I found the source, add my sources and compiled it, It should be easy (and legit ) to load the new image to the consumer phone right ?
Thanks
Roee
More or less that is correct. The source code will contain the license terms, if it says GPL then you are golden. If you get the source from a questionable route and it's not necessarily "public" then it goes into a gray area. Generically speaking, if you get the Android source, and the source code for your keyboard, build an image with it, flash it to your phone, then you are perfectly fine. If you choose to redistribute that code that you mashed together, it's arguable you'd then also have to publish your mashed up code or at the very least the 2 sources you used to mash it together. Mash is the best word I can think of right now
-Chad
Thanks for the reply Chad.
If the software is GPL, and I don't intend to publish the code, I just want to play and check couple of things.
I wonder if i can only compile a new keyboard driver (for example), and just load the ko file somehow without flushing the whole kernel.
I don't have much experience in the linux world, but I would guess it will be something like :
get the branch from the android git
compile a new kernel object for the keyboard
use adb to load the ko file to the device
insmod the new device
somehow remove the current keyboard device and map a new device with the new kernel driver
is this the correct flow ? is there example of how to do it somewhere ?
Cheers
Roee
Ok, I think I have a little better understanding after I played with my G1 today...
So now I understand how to enumerate all the devices in the system, and find the proper devices (e.g using cat /proc/bus/input/devices , or in /devices/virtual/input/ ), but I fail to understand how to replace the proper lkm module. When I run lsmod, the only module loaded is the Wlan module.
How can I find which file is responsible for the keyboard and replace it with my driver? Or must I recompile the whole kernel in order to replace the driver with my modified driver?
I guess it became an easy linux questions.... (just not easy for me )
Hello, I found a driver online that I want to add to my Android phone. It is a DisplayLink device driver.
magoroku15/DisplayLink-driver-for-android (from github)
The part I am confused about is how to go about adding the driver to my phone. Do I need to download the Android source code, add the driver to that, and then build the whole thing? Or is it possible to just load the driver as a module?
I've searched Google but haven't found anything definitive. I'm not even sure if I'm using the right terms here, as I haven't ever played around with adding drivers to anything before.
Any help would be greatly appreciated!
yes. i would also like to know how this is done.. please share. thanks
me 3! tell usssss
you would need a dev environment setup to cross compile for that device (your phone) then compile the source as a module and load it from a command line. (insmod <module>). if you get a new line in the terminal without error, its loaded.
thanks! ill try this later..
nenn said:
you would need a dev environment setup to cross compile for that device (your phone) then compile the source as a module and load it from a command line. (insmod <module>). if you get a new line in the terminal without error, its loaded.
Click to expand...
Click to collapse
What if you don't (or don't want to) have root access on the phone?
well this guy in his thread is loading a lot of drivers *.ko i thing?
helpful?
*edit* forgot the link
http://sven.killig.de/android/N1/2.2/usb_host/
Any answers?
I'm looking for the same thing: I want to install a new driver on Android devices, but I can't Root the devices - I need to add the driver(s) to stock Android installations.
Just curious.. why do so many ppl seem to add driver to their system? :/
My task is similar to noted earlier.
I want to make "virtual driver". In other words, the device doesn't have specific hardware and I need to emulate it programmately.
Any hints and links would be useful.
Thanks.
jkoshi said:
What if you don't (or don't want to) have root access on the phone?
Click to expand...
Click to collapse
I think you would need root access on your device in order to load your kernel module: 'insmod your_module.ko' or whatever.
- jc
Hey i was looking to do this exact thing so i could connect a mimo monitor to my phone any progress or step by step instructions
Subscribed
you need to have right kernel module compiled on the same kernel version that you android is running on.
it is a may be not only *.ko file, but it may need also another firmware files.
if it is only one file, you are lucky, you need just that ko file with right kernel version and put to vendor directory with modules.
and if not automaticaly loaded, you must call insmod command from rc file on device boot or manually from terminal.
better solution is to compile kernel yourself with driver inside it.
for details see 'linux kernel modules'.
Note: for sure you need root access to such as system modify operations...
And here : https://hex.ro/wp/blog/compile-an-android-kernel-module-outside-the-kernel-source-tree/
Hello People. This is basically a combination of batch scripts made by me to make WSL less daunting for people who do not want to do Powershell things and introduce MANY more people to Linux [and make existing dual boot Linux users just stick to Windows w/o the ugly GRUB].
Disclaimer: Only you know what you're doing. I have tested everything on me and my friend's PC and it seems to work fine. If your PC catches fire or starts an apocalypse it's not my fault. So yeah be careful about what you're doing.
Things the scripts can do:
1) Enable WSL 2 in any Windows 10 2004 computer. [NEW: Older versions of windows 10 are now supported.]
2) Download all the available distros with a couple key presses.
3) Automatically detects the downloaded distro and installs it without any user input.
Downloads are attached in the thread and instructions are given in the zip file.
How to know which zip to download (1 or 2) [Don't Skip]:
1) Go to the start menu.
2) Type "Run" and press enter
3) Then type there "winver" and press enter.
4) If you see 2004 there, ONLY THEN are you able to download the WSL-2 zip. Otherwise update your Windows or use the WSL-1 zip.
Note to self: Things to do in the future--
1) Make a GUI of sorts.
2) Anything else the people want.
Not going to force you or anything, but I would appreciate if you pressed the Thanks button after benefiting from my zip (I see 78 downloads but only 2 thanks...)
Edit: NEW DOWNLOAD LINKS
https://mega.nz/file/NAxASK4I#2qr4ra4KJAcliEqDuCNQd0GnJeHe4FXpvw3KUfqtKxc [for WSL 1]
https://mega.nz/file/lE40AKDa#3Qqk6WH04vzYW8wrrcruuOdqpde-KUzYnu0o50tmZzo [for WSL 2]
WSL-2 Changelogs:Version 1:
Initial Release
Version 2:
Complete Redesign
Compressed all my code to 2 very compact Batch files [previously it was 4 Batch files and 5 Powershell files]
Added Distro Downloaders and Installers (x64 only as of now)
Made it more stable [the previous method was very hacky and used bypasses]
Fixed all typos
Made it more user-friendly
Version 2.1
Quality of Life improvements
Version 2.2
Back-Ported the 'more sophisticated' Distro Downloader from WSL-1
Made Instructions better
WSL-1 Changelogs:Version 1:
Initial Build
Version 1.1:
Made the instructions more newbie friendly.
Backported the WSL-2 Distro Downloader and Installer to WSL-1
Version 2.0:
Complete redesign of the Menu [Looks MUCH more visually pleasing]
Made the in-built Distro Downloader A LOT more sophisticated
Cleaned up the back-end a little bit
Improved Instructions
Announcements27/10/2020
I have started learning C++ so let's see if I can make a GUI with that
18/10/2020
Added a new WSL-1 zip file for people who do not have version 20H1
17.5/10/2020
Fixed Everything and restored download link. Now you can download again!
17/10/2020:
Removed download link because I noticed a couple typos. Fixing them and uploading the file please wait.
Thank you, bro, because I use both windows and linux, now I don't have to restart the computer every time.:good:
JohnMes said:
Thank you, bro, because I use both windows and linux, now I don't have to restart the computer every time.:good:
Click to expand...
Click to collapse
you're very welcome
Just have to. Say thanks had this opFeat installed since maybe it was first available in the list and never researched how. To. Use it or. What it really did. Just gotta find out if this will run fine on my surface too (anything except liveOS off usb will work and causes windows to eff up despite grub/4win/stock/grub if it works excites to use kali on there properly}
Nsomnia said:
Just have to. Say thanks had this opFeat installed since maybe it was first available in the list and never researched how. To. Use it or. What it really did. Just gotta find out if this will run fine on my surface too (anything except liveOS off usb will work and causes windows to eff up despite grub/4win/stock/grub if it works excites to use kali on there properly}
Click to expand...
Click to collapse
You're very welcome but I would be happy if the thanks button was pressed Also, it should work fine on any Windows 10 computer [remember I am using a Haswell computer and it still works]. I also have Kali working but it does not support Monitor Mode and Packet Injection just yet [Microsoft does not want to implement this feature due to security concerns]. You can also get a GUI up and running with ONLY kali using Win-Kex [look it up]
Our PC system has been attacked by a ransomewhere virus, called as .lisp file virus and our files has been encrypted to .lisp sub-extension. Any technical advice?
Thanks but any chance of getting clean links that don't require allowing JavaScript before i can access them ?
It's blocked by my browser security and even if i allow it ,the download link gets blocked by Eset.
Doesn't anyone vet the links that get posted in the forum here ?
There's no need for a download link to be like that.
oldman820 said:
Thanks but any chance of getting clean links that don't require allowing JavaScript before i can access them ?
It's blocked by my browser security and even if i allow it ,the download link gets blocked by Eset.
Doesn't anyone vet the links that get posted in the forum here ?
There's no need for a download link to be like that.
Click to expand...
Click to collapse
sure, giving
NullCode said:
sure, giving
Click to expand...
Click to collapse
Great ,links worked ok ,cheers.
oldman820 said:
Great ,links worked ok ,cheers.
Click to expand...
Click to collapse
Are they useful to you?