Database Info

Rebuild Rogers kernel for tethering

I've got Ubuntu up and running and I'm willing to rebuild the kernel to enable tethering.
Problem 1 is that I have not received my Magic yet
Problem 2 is that I have no idea what I need to do
So who wants to help?

sammypwns said:
I've got Ubuntu up and running and I'm willing to rebuild the kernel to enable tethering.
Problem 1 is that I have not received my Magic yet
Problem 2 is that I have no idea what I need to do
So who wants to help?
Click to expand...
Click to collapse
I'll help. I've got tethering working using Azilink, but it would be nice to get it working using the Hero's built-in tethering option. Here's my post at ubuntuforums.org:
http://ubuntuforums.org/showthread.php?t=1202059
So are you rebuilding the kernel to get the iptables? I can't even get to make Ubuntu see the Magic as a communications device now.

It took me about 15 minutes to get the SDK up and running on Ubuntu 32 bit but I don't know where to find the source for the kernel or evena copy of the kernel itself. Once I have those it shouldn't take more than 5 minutes to compile the kernel including iptables. In fact if I had the source to a kernel that does allow tethering it would be even faster because I could just drag and drop what I need into the build directory. I haven't seen the source but I think that the HTC branded kernel only differs by a few files and it might even be easier to move the HTC files to the Google kernel. Need more help and testers.

sammypwns said:
It took me about 15 minutes to get the SDK up and running on Ubuntu 32 bit but I don't know where to find the source for the kernel or evena copy of the kernel itself. Once I have those it shouldn't take more than 5 minutes to compile the kernel including iptables. In fact if I had the source to a kernel that does allow tethering it would be even faster because I could just drag and drop what I need into the build directory. I haven't seen the source but I think that the HTC branded kernel only differs by a few files and it might even be easier to move the HTC files to the Google kernel. Need more help and testers.
Click to expand...
Click to collapse
Do you have the port tools? They allow you to unpack the boot.img. I'll upload the port tools for you:
http://www.mediafire.com/?fnzdtnj4gmy
Just put all of the tools in your /android/tools folder.
To unpack the boot.img, you just have to run this command:
unpack-H.pl boot.img
Click to expand...
Click to collapse
That's it. Good-luck. Messing around with the kernel is way above my know-how.

@hotweiss thanks a bunch

This guide shows you how to push the IP tables on the Magic:
http://android-unleashed.com/2008/1...d-g1-phone-with-iptables-no-proxy-needed.html

do I just need to incorprate the iptables binary with the kernel when I build it. Again I haven't seen either kernel to compare them.

sammypwns said:
do I just need to incorprate the iptables binary with the kernel when I build it. Again I haven't seen either kernel to compare them.
Click to expand...
Click to collapse
Haven't done it myself yet, but it looks like it's just an issue of following a few steps. The biggest problem right now is to make Ubuntu see the Magic as a modem.

again I don't have my magic yet so I can't comment on that but if anyone has a google branded version could you please check and see if you can get ubuntu to recognize it as a modem. if so then we know that it has only to do with the kernel itself.
EDIT: Also I can't get unpack-H.pl to work, i keep getting bash: /home/sammy/android-sdk-linux_x86-1.5_r2/tools/unpack-H.pl: Permission denied

sammypwns said:
again I don't have my magic yet so I can't comment on that but if anyone has a google branded version could you please check and see if you can get ubuntu to recognize it as a modem. if so then we know that it has only to do with the kernel itself.
EDIT: Also I can't get unpack-H.pl to work, i keep getting bash: /home/sammy/android-sdk-linux_x86-1.5_r2/tools/unpack-H.pl: Permission denied
Click to expand...
Click to collapse
right click on unpack-H.pl, set the permissions, and make it executable.

hotweiss said:
This guide shows you how to push the IP tables on the Magic:
http://android-unleashed.com/2008/1...d-g1-phone-with-iptables-no-proxy-needed.html
Click to expand...
Click to collapse
well you dint need go all the steps , just pushing iptables and insmod should be enough if you use wifi tethering app. but is the kernel in htc magic and g1 the same , do they run the same binary ?
i will check it but dont know if it works.
Edit :
No ipfilter in the kernel = not working
the binary itself works just fine (strange)

its because the kernel is missing netfilter too. there are actually 3 things we require for this to work. we need to build netfilter as a module, build iptables as a module and then include the iptables binary so that other programs can talk to it. unfortunately i don't have a magic but if you could pm me your im screen names we could do this faster

sammypwns said:
its because the kernel is missing netfilter too. there are actually 3 things we require for this to work. we need to build netfilter as a module, build iptables as a module and then include the iptables binary so that other programs can talk to it. unfortunately i don't have a magic but if you could pm me your im screen names we could do this faster
Click to expand...
Click to collapse
Things will be complicated by the fact that the Rogers and T-Mobile Magic's are different. I'm still confident that we'll work it out.

hotweiss the google branded ion does not require these modules

Android Wired Tether is patched and working for Evo

This post is now irrelevant, Alex put these commands into the main program. See second post for links.
I figured out how to get it fully working. Big thank you to tonyb486 and canteenboy for figuring out that you need to disable adb and usb mass storage for tethering to work. That only left the problem of disk mounting not working after you are tethering. Here are two scripts to get the whole thing running smoothly and without a problem.
First, if you haven't already, install android-wired-tether. Next install GScript Lite (on the Market) which will let us automate toggling the USB function switch.
Create a new script with SU enabled and use this as the code.
Code:
echo 0 > /sys/devices/platform/msm_hsusb/usb_function_switch
That command shuts off usb_mass_storage and adb so everything is disabled and ready for Wired Tether to come in and do its job. Your usb_function_switch will look like this after running the command.
usb_mass_storage:disable
adb:disable
diag:disable
serial:disable
ether:disable
modem:disable
nmea:disable
When you are done tethering, use this command to re-enable adb and usb_mass_storage:
Code:
echo 3 > /sys/devices/platform/msm_hsusb/usb_function_switch
If for some reason you don't use USB debugging (adb), you can use this command to turn on usb_mass_storage by itself.
Code:
echo 1 > /sys/devices/platform/msm_hsusb/usb_function_switch
For those of you new to GScript, you can place shortcuts to scripts on your home screen. To simplify my life, I put them in a folder with Wired Tether so I have everything in one place. It's not an elegant solution, but you won't need to reboot your phone to get SD card mounting to work again. Perhaps someone with more knowledge of GScript can write some code that will automate running the first script, starting Wired Tether, and then running the last script after it notices that tethering has stopped. (Or better yet, get these commands into the actual program itself.)
(Optional)
For completeness, if you use any of the other usb functions listed above, you can use other 'echo #' commands to find the right combination. They don't toggle individual settings, but rather represent entire combinations of settings. I think around 32-33 it cycles back to 0 (everything off), I didn't have time to figure out if there is a pattern. You can find out what each number does by using another script to read out the switches.
Code:
cat /sys/devices/platform/msm_hsusb/usb_function_switch

Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21

Thanks! I'd like to add that the scripts and the patched app are both working great on my Incredible.

O Whoa, Wired Tether works on my stock Eris now Thank You

Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.

jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
Same. I was going to try the app on the Eris because the same manual fix works :\

jerdog said:
Do you have the link to the exact program that has the commands built in? Perused both links and couldn't find the link to the fixed one for the Evo.
Click to expand...
Click to collapse
yeah me too cant find it

Wow, I thought nobody gave a **** about this. Here it is, all compiled and ready to go.

Thanks duder, works like a charm...
Sent from my phone.

THANKS!!!!

Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.

dalstrs said:
Has anyone figured out how to get this to work on Froyo? I get a kernel unsupported error when trying to run it.
Click to expand...
Click to collapse
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.

I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App

striker012 said:
I have stock froyo on my evo and use easythether, it works perfect, all you have to do is set it to debug mode in the settings, install the app on your computer and when connected set it to charge only.
Sent from my Evo using XDA App
Click to expand...
Click to collapse
The problem with that is having to install stuff on the computer. With wired tether you don't have to install anything on the computer.

XevoX said:
Same here, I'm using netarchy's 4.0.3a kernel and SteelH's stock Froyo RevE.1 ROM.
Click to expand...
Click to collapse
I'm running the same kernel on evio rom and it's working fine for me...
Sent from my phone.

I've been able to make this work on my stock kernel, rooted FroYo Evo, so this is indeed possible and I've narrowed it down to what is necessary. Please star/follow issue 23 in the Google Code tracker for updates.

Unsupported Kernel message...
Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E

Hello, all. I'm running Fresh Evo 3.1.0.1 and King's latest kernel and I get the unsupported kernel message. When I try to ignore as is suggested in post 24 on the Google code page for the wired tether, I get a FC once I click to start tethering. Any ideas? Thanks in advance. -E
Click to expand...
Click to collapse
Hi EindhovenOne, I responded to you on the issue tracker for Wired Tether, but I'll respond here just for some others to know the situation.
I found a fix that worked for me on my stock, rooted FroYo Evo and I coded the change and sent Harald a patch. He incorporated the patch and did the build for Wired Tether for me to test, which I have done (and it does indeed work for me, but does currently have the unsupported kernel dialog*). At the same time, though, it is listed in the downloads (you have to select all and then search), but this is in beta state for the changes (hence the deprecated tag I believe).
* I have fixed the unsupported kernel message and sent Harald a patch on this as well, so when he finds time to build it, that should be corrected, too.
So back to the "it's not working" portion, since I'm not running anything but stock (ROM and kernel), my system won't be the same as everyone's. I have no problem with other variations of ROMs and kernels (Evo's and non-Evo's) trying the 1.3 APK, giving feedback, and I'll try to do what I can (and someone else can step in if more suited than me even).
If you do run into issues, you can tag them in the issue tracker, which I try to follow frequently right now. Also, most importantly, if you can provide as much information as possible (what ROM and kernel you're using, a LogCat run just after the error occurs, any other pertinent information we can use to diagnose the problem, etc.), that helps tremendously in tracking down the problem and identifying a fix.

Saturn2K said:
Huge thank you to Alex C. Hofbauer. He implemented these commands into the program. Now the program works flawlessly (or I assume, I haven't tested it yet).
Attached to this post:
http://forum.xda-developers.com/showthread.php?t=706602
http://code.google.com/p/android-wired-tether/issues/detail?id=21
Click to expand...
Click to collapse
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO

superevilllama said:
Is there a way we can find this patched version of android-tether? It is no longer attached to the first post. Also, the version I download from google still says incompatible kernel. It would be awesome to get wired tether working for the EVO
Click to expand...
Click to collapse
The beta-in-progress version 1.3 is located here. It still warns about the kernel currently but you can ignore it (simple lapse in patching that as well at the time). It works perfectly for me (starting and stopping), but there are a couple of issues outstanding right now that I'm working through with the users.
If you do run into a problem, though, just let me/us know through the issue tracker preferably, but you can also contact me directly (here, or my email via the issue tracker).
PS: I have patched the kernel message already, but I don't have write access to the project yet and I don't have the build system in place to handle the native code just yet, so I have been handing builds off to Harald who graciously has done the 1.3 so far for me. When he has time to do the one including the kernel warning fix, I'll post again with an update on that.

[Q] Tun/tap driver for infuse sgh 1997

Hello!
I'm very new to the android os and owner of an infuse (android 2.2.1, kernel version: 2.6.32.9, froyo.uckd5) since a couple of weeks.
Honestly I feel a bit lost because I'm looking for a tun.ko module for this device and as far as I can see there isn't, at least for the production rom. All the tun.ko I found are compiled for kernel different from mine.
I really need openvpn and now I'm wondering if I should:
1) keep looking
2) figure out how to compile a tun.ko on my linux machine for the arm7 architecture
3) look at some modified rom with the module built in
Do you have any suggestion?
Thank you
Cheers

dventurin said:
Hello!
I'm very new to the android os and owner of an infuse (android 2.2.1, kernel version: 2.6.32.9, froyo.uckd5) since a couple of weeks.
Honestly I feel a bit lost because I'm looking for a tun.ko module for this device and as far as I can see there isn't, at least for the production rom. All the tun.ko I found are compiled for kernel different from mine.
I really need openvpn and now I'm wondering if I should:
1) keep looking
2) figure out how to compile a tun.ko on my linux machine for the arm7 architecture
3) look at some modified rom with the module built in
Do you have any suggestion?
Thank you
Cheers
Click to expand...
Click to collapse
3) As far as I can tell, all of the alternative kernels have this module. The Infused ROM contains the Voodoo kernel, but I believe you can run the Voodoo or Infusion kernels on the stock ROM.

ok I see.
Could you suggest to me a starting point to deal with the custom roms?
I'm have a good experience with linux since years but not enough on smart phones and android in general.
For instance, is there an official website for Infused ROM?
Any tip is welcome.
Thank you!

@dventurin - I had the same issue. I have the Infused rom installed and it has the same issue. I installed SL4A and wrote my own scripts, the app is what's broke everything works at the CLI. I then used Tasker but I think you can do it with Gscripts as well build my own shortcuts. As for where to find the Infused ROM look in the Dev section here. There a several ROM's available but I've only used Infused.

@3GBeyotch
were did you get the Infused rom? Is there an official website with documentation? Honestly I don't feel comfortable when I have to use stuff found on a forum: how can I trust them?

dventurin said:
were did you get the Infused rom? Is there an official website with documentation? Honestly I don't feel comfortable when I have to use stuff found on a forum: how can I trust them?
Click to expand...
Click to collapse
If you want the Infused ROM, head over to the "Infuse 4G Android Development" forum....
http://forum.xda-developers.com/forumdisplay.php?f=1161
From there, you will want to look at 2 threads....
1. You need to root your device first. Check out the very first thread (entitled: [How To] Root the Samsung Infuse 4G) shows how to root your device.....
http://forum.xda-developers.com/showthread.php?t=1082247
(the second link under SOURCE: has a video tutorial)
Side note: When downloading Superoneclick, make sure to get the one that has the drivers included. Also, make sure your external SD card is unmounted!
======================
2. Next, you'll need to install the Infused ROM. Look at the thread (entitled: [ROM] Infused v1.5.0 - (06/18/11) - Faster and smoother than ever!), which has the instructions, etc, for installing the Infused ROM.....
http://forum.xda-developers.com/showthread.php?t=1105413
You basically need to root your device first, then install the Infused ROM.
As far as feeling comfortable with using the sources from the forum, you have nothing to worry about. In regards to the Infused ROM, gtg465x is the one who developed it. All you have to do is follow the instructions, and if you feel uncomfortable about doing one of the steps, ask someone here!
I've had the Infused ROM installed now for a few weeks, and I have not been disappointed! Hope this helps.

Open VPN on Infused ROM tun.ko problems?
Greetings! This discussion is about what I am trying to solve, so I decided to post here. I have searched and read other threads, but can not figure out a solution. I am a noob in this.
Anyway, I also would like to make OpenVPN working on my Samsung Infuse.
I have rooted it, installed the Infused ROM Version 1.5.3 (awesme!)
About Phone gives me the following info:
Firmware version 2.2.1
Baseband version i997UCKE3
Kernel version 2.6.32.9
Build number Infused v1.5.3
No the problem. I have openvpn installed with OpenVPN Installer. My config, key, certificate files are in /sdcard/openvpn folder. Everything seems okay.
When I try to connect to my router at home, however, the tun.ko module would not load. It gives an error. I even tried to load it manually from the Terminal Emulator (insmod /system/lib/modules/tun.ko) It gives me an error still. The module file is in the folder.
What am I doing wrong? Has anyone been able to make openvpn work on the Infused ROM?
I had the same problem on the original AT&T ROM, but that one did not have the tun.ko at all, so it was understandable.
I would appreciate any suggestions.
Thank you in advance.

iovchinn said:
Greetings! This discussion is about what I am trying to solve, so I decided to post here. I have searched and read other threads, but can not figure out a solution. I am a noob in this.
Anyway, I also would like to make OpenVPN working on my Samsung Infuse.
I have rooted it, installed the Infused ROM Version 1.5.3 (awesme!)
About Phone gives me the following info:
Firmware version 2.2.1
Baseband version i997UCKE3
Kernel version 2.6.32.9
Build number Infused v1.5.3
No the problem. I have openvpn installed with OpenVPN Installer. My config, key, certificate files are in /sdcard/openvpn folder. Everything seems okay.
When I try to connect to my router at home, however, the tun.ko module would not load. It gives an error. I even tried to load it manually from the Terminal Emulator (insmod /system/lib/modules/tun.ko) It gives me an error still. The module file is in the folder.
What am I doing wrong? Has anyone been able to make openvpn work on the Infused ROM?
I had the same problem on the original AT&T ROM, but that one did not have the tun.ko at all, so it was understandable.
I would appreciate any suggestions.
Thank you in advance.
Click to expand...
Click to collapse
What's the error?

Entropy512 said:
What's the error?
Click to expand...
Click to collapse
OpenVPN Settings gives the following error: "FATAL: Cannot allocate tun/tap dev dynamically".
When I run "insmod /system/lib/modules/tun.ko" it gives me: "Failed (Exec format error)
Again, thank you for your response.

iovchinn said:
OpenVPN Settings gives the following error: "FATAL: Cannot allocate tun/tap dev dynamically".
When I run "insmod /system/lib/modules/tun.ko" it gives me: "Failed (Exec format error)
Again, thank you for your response.
Click to expand...
Click to collapse
out of curiosity, is there also a tun.ko in /lib/modules in addition to /system/lib/modules?

Entropy512 said:
out of curiosity, is there also a tun.ko in /lib/modules in addition to /system/lib/modules?
Click to expand...
Click to collapse
Man, my hat is off!
Indeed, there is one in /lib/modules and it did work when I tried to load it, instead of the one in /system/lib/modules/. Any idea, why the other one did not work? Not that it matters now.
Also, your signature says that you run Cyanogen Mod with Infuse. My understanding was that Infuse was not yet supported. Is it easy to install it? Any published instructions?
Again, thanks a bunch for the tip.

iovchinn said:
Man, my hat is off!
Indeed, there is one in /lib/modules and it did work when I tried to load it, instead of the one in /system/lib/modules/. Any idea, why the other one did not work? Not that it matters now.
Also, your signature says that you run Cyanogen Mod with Infuse. My understanding was that Infuse was not yet supported. Is it easy to install it? Any published instructions?
Again, thanks a bunch for the tip.
Click to expand...
Click to collapse
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.

Entropy512 said:
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Click to expand...
Click to collapse
It seems, you are right. /system/lib/modules/ has only one file in it and it is tun.ko. That one did not load. Must be some left-overs from previous reincarnation. The one in /lib/modules/ has lots of different *.ko files and tun.ko among them. This one loads just fine.
Again, thank you very much for your help.

Entropy512 said:
My guess is in your previous attempts to add a tun.ko module, you stuck one in /system/lib, or maybe gtg accidentally included some "cruft" in /system/lib that shouldn't be there.
As to CM7 - Right now it's a source-only unofficial build, links to the git repo are in the Development section. There are occasionally binary releases floating around, however not anywhere on these forums. Good things come to those who expand their horizons and do research.
Click to expand...
Click to collapse
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.

iovchinn said:
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
Click to expand...
Click to collapse
Unfortunately someone else will have to help you there - I haven't used VPN functions on my phone.

iovchinn said:
By the way. Perhaps, I can get a bit more help with this. My joy was short-lived. My Infuse connects to my Tomato - no problem. However, it does not force traffic to the VPN tunnel. It is still using whatever service I connect: Wi-Fi, or Cell Provider's.
Any hints on how to fix it? I tried the "Fix HTC Routes" option in "OpenVPN Settings." No luck.
I would appreciate some help.
Click to expand...
Click to collapse
Having the same problem, am able to connect to openVPN running on ddwrt but the phone isn't directing traffic through it. Anyone have any ideas?

Tubuntu - questions and issues

This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex

Serkenar said:
This should probably be posted here, but I sadly don't have the required 10 posts to do so.
There's one issue that I noticed that is actual in 0.2.2alpha. When you choose to flash Jhinta 3.1x kernel and not 2.6x kernel, it is still linux.img that is being flashed, instead of jlinux.img.
Also there's one question (or rather a feature request). Once you have dual boot up and running it would be nice to be able to flash linux rootfs only (ubuntu.img) without changing the partition table and loosing current android install. You can't currently do that with Tubuntu, right?
Best regards,
Alex
Click to expand...
Click to collapse
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option

x3maniac said:
hi!
that will be on my next release cause i flash my tubuntu image so much. i'm trying to push out a backup menu along with that new rootfs option
Click to expand...
Click to collapse
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you

Serkenar said:
Hi,
I'm really glad to hear that! Looking forward to the next Tubuntu release
I'd also like to ask to include cifs kernel module in your kernel build.
Thank you
Click to expand...
Click to collapse
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support

x3maniac said:
new version is up with Flash rootfs only :laugh:
future release of kernel i will put cifs. right now i'm trying to get zram and overclocking right 1st.
lol i feel like a one man operation. make the program to flash ubuntu images, didn't find one i liked. so i went ahead and made one. feel that the kernel is missing too much stuff. and went ahead and i'm making that now lol... am i missing anything else i need to learn/do? hahahaha
but i'm loving it!
thanks for the support
Click to expand...
Click to collapse
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you

Serkenar said:
Thank you for your effort
Speaking about your own kernel, I tried compiling one from Jhinta source, but I received odd errors at boot time. First it was this kind of errors:
lists.litmus-rt.org/pipermail/litmus-dev/2012/000215.html
it was suggested there to try changing CONFIG_DEVTMPFS_MOUNT kernel config value, I did that, and then I got some other odd errors, so I gave up
Right now I have a more or less stable 12.04 kubuntu+3.10.1 jhanti kernel with hw acceleration, sound, zram (used netinstall 0.6). I'm only missing overclocking and a cifs module, that's why I tried building my own kernel, but never got it booting. I don't know any sane methods of backing up and restoring linux on tf101 (well, dd + gzip should work, but that's rather stupid), so I'm a little hesitant about flashing your lubuntu right now. I think I'll still give it a go, but before I do that, don't you know any easy way to back up my current linux install?
Thank you
Click to expand...
Click to collapse
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps

Thank you for your work on this
x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks

thelangosta said:
x3maniac I was wondering if you have ever checked out openELEC linux. They just pushed out a new version on Distrowatch and it looks like it will have support for ARM devices. It is very lightweight at 106mb and is made to run XBMC out of the box. Might be worth a try due to its size and media streaming abilities.
Thanks
Click to expand...
Click to collapse
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols

Cool
x3maniac said:
thanks for the info. i will look into it, i do have a arch linux version working with 3.1 which is only about 200mb.
edit:
they have a arm version 83mb! lols
Click to expand...
Click to collapse
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks

thelangosta said:
Wow that is small. I have seen Roms that small but never an os. Wait, is that openELEC or Arch you are talking about.
On another note if I do end up getting around to trying your method with arch which desktop would you recommend?
Thanks
Click to expand...
Click to collapse
openelec(rasbery pi)
if you want it to look nice then enlightment e17. for a light weight DE they make it very pretty with all the effects like compiz
or lxde

x3maniac said:
i'm now compiling from his source. for the 3.1.10 kernel i'm using. why try to reinvent the wheel? i just recompiled and added oc and cifs, i didn't run into any compile issues but i did run into boot issues so changing the kernel to compress with lzmo instead of gzip fixed it. hope that helps
Click to expand...
Click to collapse
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!

Serkenar said:
Compression was already set to lzma. I can't figure out what I was doing wrong. Yet, you're right, no point to reinvent the wheel.
I see you've recently released your Lubuntu V1.1-rc1. The specs sound great! Could you please post the rootfs download link and also post your kernel img?
Thank you for the great work you're doing!
Click to expand...
Click to collapse
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157

x3maniac said:
the link to image and kernel is up. http://forum.xda-developers.com/showthread.php?t=1995157
Click to expand...
Click to collapse
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards

Serkenar said:
I gave it a go First of all, Tubuntu flashes .\images\linux.img when choosing to flash "2.6x x3maniac kernel", I assume it should flash .\images\xlinux.img
That's not a big issue, but should be fixed
A quick list of things I noticed.
1. Things that work:
-1.2 GHz OC
-Usb mouse (when plugged before system boots, otherwise not - that's due to 3.1.10 kernel, I guess)
-cifs module
-chromium
-terminal (right clicking on your tf101linux gadget -> Shortcuts -> Terminal)
-screen brightness up/down buttons. You just have to be mindful to avoid turning the screen off this way - it won't turn on afterwards and you'll have to force reboot.
-ntfs read/write
2. Things that don't work:
-touchpad
-XF86poweroff button
-System Tools -> XTerm/UXTerm
-sound: Audacious complains "ALSA error. No suitable mixer element found. snd_mixer_find_selem failed". Gnome MPlayer just won't produce any sound, and youtube html5 videos too.
-plugging in an external usb drive. It's totally ignored. A pen drive doesn't even blink, nor the drive appears in /dev it works now. It didn't during initial launch. Don't know why, but a reboot cured this.
Also, it happens quite often that system freezes for no apparent reason and only force reboot helps. It happened twice with me already, although it's been less then an hour since I flashed lubuntu.
Tell me if you need some additional info
Regards
Click to expand...
Click to collapse
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet

x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2

x3maniac said:
i love your report! keep up the good work. this helps me narrow down the problems but without a dock i can't fix some of the issues. but try this
touchpad:
edit /etc/X11/Xorg.conf
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
should fix the touchpad issue.
i will look into fixing my script for the brightness issue. located int /usr/local/bin/tfbright
what were you doing when you freeze? i don't have a dock(still waiting for it in the mail) so i don't know if it's related to that.
i've been looking at nvidia git and downloaded there source for the linux4tegra kernel. it' compiled fine but wont boot. don't know why yet
Click to expand...
Click to collapse
Strange, but there's no /etc/X11/xorg.conf
I tried creating it with `Xorg :1 -configure`, but I get "No devices to configure. Configuration failed."
I also tried creating /etc/X11/xorg.conf with the following content
Code:
Section "InputClass"
MatchIsTouchpad "on"
Identifier "Touchpads"
Driver "mtrack"
EndSection
but touchpad wont' work.
Like I said, there appears to be no apparent reason for those freezes The only things they had in common are the following:
(as far as I can remember)
-I had a cifs share mounted
-pen drive was plugged in
-chromium was opened
I understand that isn't helpful at all, but atm I can't reproduce those freezes myself. They occur kind of randomly.
I hope linux4tegra kernel does boot after all
Thank you for your work
EDIT: 30 minutes without freezes, I hope they're gone for good! :laugh:

djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
+1 Totally agree

djlenoir said:
x3maniac, I know it is off topic a bit but I just wanted to mention that I appreciate your attitude towards your work and especially criticism (aka feedback) from others about your work. Reminds me of my EVO 4G days running tommytomato's classic rom. His threads were always friendly and optimistic, much like your own.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Serkenar said:
+1 Totally agree
Click to expand...
Click to collapse
as far as i see it, you guys are helping me get a working version. user/tester are as important as the devs making them. or else dev's would be out of the job. lols that's how i see it

I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.

Serkenar said:
I let lubuntu running and it froze smth like 20 minutes ago Without me doing anything. Chromium was running, pen drive plugged in and a cifs share mounted.
I'll leave it running without a pen drive plugged in, shares mounted and chromium running to see if it freezes eventually.
Click to expand...
Click to collapse
i'm guessing jhanti's kernel is not stable. i was starting to use it more and got a random freeze. cpu1 went to sleep and wont wake up. looking into that.. i might just take nvidia's kernel 3.1.10 and try to get that working.

Is it possible to root the "Nokia 8110 4G" running KaiOS ?

Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB

sgmarouf said:
Hello everyone.
Can we please get root on this phone?
Specs are:
Operating System: KaiOS
System chip: Qualcomm Snapdragon 205 MSM8905
Processor: Dual-core, 1100 MHz, ARM Cortex-A7, 32-bit, 28 nm
Graphics processor: Adreno 304
System memory: 0.5 GB RAM
Built-in storage: 4 GB
Storage expansion: up to 64 GB
Click to expand...
Click to collapse
Im also wondering the same thing

Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.

nexus511 said:
Yes, have been able to flash my own system and it is also possible to get ADB.
I am currently working on it, but it might take some days to get something useful out of it. As I just created a new account here, I am currently not able to post any links, but you can find my stuff linked on Twitter via @nexus511.
Click to expand...
Click to collapse
Good job! :good:

0312birdzhang said:
Good job! :good:
Click to expand...
Click to collapse
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.

nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
This is a good news! I just bought a "banana" today, waiting for your good news :fingers-crossed:

nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse
Sounds like you've made some impressive progress here, can't wait for more details!
Will you be posting a more detailed tutorial/how-to here or on your blog in the future?
Keep up the great work! :good:

Great work, would be great to uninstalled preinstalled *tty demo games.

@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
nexus511 said:
Short update:
I have been able to gain root and I have also been able to modify selinux policies on the device. Then I have been running into some strange behavior. It actually looks like the kernel is telling to be running in permissive mode but even a permissive context seems to be enforcing instead.
I will try to use something like "Magisk" instead and see, if a service can solve this issue.
For anyone interested: The kernel-config can be extracted via /proc/config.gz. The dtb is compiled into the kernel image. Maybe I try extracting the dtb and building a codeaurora kernel for the device and see, how far I get with that. This might resolve the strange selinux issues I currently see.
Click to expand...
Click to collapse

fpb4 said:
@nexus511, any way you could please share the root procedure or point to some resources?
Or...at the very least when you get a spare second, how you did manage to unlock your bootloader knowing Nokia has publicly acknowledge disabling Device > Developer?
Muchas,
Click to expand...
Click to collapse
Use OmniJB can enable "Developer Mode".
Tested on sideload mode

0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?

0312birdzhang said:
Use OmniJB can enable "Developer Mode".
Tested on sideload mode
Click to expand...
Click to collapse
Is there anyway I could revert installing omniJB? I'd love to be able to install factory updates again.

hello all, just give an update on how's everything regarding nokia 8110 is going

fpb4 said:
Cheers mate :good: , that's a step forward (and cookie points to OmniJB's dev for the firefox 52.9 esr trick) - now WebIDE lists all runtime apps in Unrestricted DevTools privileges...which is great should I be willing to debug any of those or create my own. What I am looking for though is a way to *delete/un-install/remove* (no cigar remounting /system/b2g/webapps rw without root) some of the certified pre-installed applications (assistant to start with or the bunch of packaged Gameloft bloatware). Any idea - i've pm'ed @nexus511 for some root procedure but no answer yet?
Click to expand...
Click to collapse
Could you remove the pre-installed apps?

Hi!
It's possible, to get full ADB-Root by injecting a patched adbd-binary. And with real swap instead of zram, the device is more responsive (background-tasks like Launcher/Homescreen are killed less often...)
As soon, as I have build my own patched adbd, I will provide an 'update.zip' -- it seems chainfire doens't like others to use his version. (OpenSource -- anyone? )
BTW: no, I don't have 'su' -- only my own priviledged additional startscript and ADB-Root but for me this is more than enough to 'work'
(my goal is to create native apps with Ada/Gnoga - meaning native but with HTML5-GUI. First tests are working well...)

I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?

It should be possible to remove those apps - but for me it's hard to say how. On my device there were no preinstalled apps/games other than snake. Everything else is (un)installable normally. Could be a region-thing
(I've got the european/german version)
-- but on my device the store seems to be a 'static' bunch of zips - so it could kill the store to just remove those.
(i think I would need to adjust configs for the store if I want to clean them up)
If I remember correctly, there is a flag in the app-manifest to config if an app is removeable... my first try would be to edit this flag and check if I could uninstall it normally after this
On the other hand: there is nearly no need to uninstall - KaiOS-Apps are small and with a sdcard....
(I created an extra 1GB-Swap on /data - even then enough space left)
BTW: if You have a little experience with android-stuff, rooting is simple when You know how
Enable adb --> just type *#*#33284#*#* on keypad of your phone (the digits spell 'debug' )
-- build an update.zip - sign with AOSP-Test-Keys
--- let it create '/data/opt', '/data/opt/bin'
--- put an patched adbd (chainfire's v22 works) in /data/opt/bin
--- create /data/opt/init as a shellscript, remounting / rw, replace /sbin/adbd with patched one, remount / ro kill adbd so it restarts the patched version. (you may add commands for other stuff on boot - I disable zram, enable swapfile, start en Ada-Server....)
--- and add a call to '/data/opt/init' as last line to '/etc/init.qcom.post_boot.sh' so this 'init' will start with root-rights on startup.
This way /data/opt/init will inherit root from /etc/init.qcom.post_boot.sh, so it can replace adbd - and because the patched version won't drop it's root-rights you'll have a root shell over adb.
As You see - it's quite trivial, but at the moment I don't have a patched adbd which I'm allowed to include.
(I hadn't time to build an AOSP-tree until now)

Has anyone tried installing OmniJB from 4pda.ru website? (Sorry can't post links)
If you google "4pda 890710" it will bring it up.
Also, anyway of installing whatsapp yet?

PolePolisher said:
I would love to have this phone without the pre-installed social media and game garbage, would your planned update.zip allow someone reasonably competent at following instructions to do this easily or is experience required?
Click to expand...
Click to collapse
root or create an update to edit /data/local/webapps/webapps.json
it worked on my phone no more s*** games and google stuff

Can I not just replace the /sbin/adbd from the boot.img?
(by extracting the boot.img with a flashable zip, and then unpack/repack with kitchen)