AOKP - Galaxy Tab 10.1 General

As there is a useless requirement for posting in development I have to come here to answer a simple question,
Yes on build 28 I have the same MAC address, that will be a big problem since the ROM should not be changing that.

lorinkundert said:
As there is a useless requirement for posting in development I have to come here to answer a simple question,
Yes on build 28 I have the same MAC address, that will be a big problem since the ROM should not be changing that.
Click to expand...
Click to collapse
Sure. Wait, what?

Lol
sent from my nokia 3210

I´ve also notice that since a few versions back, there is a static MAC address in the ROM.
This one: 00:90:4c:c5:12:38, my orginal MAC was like this: 8c:77:12...
(If you don´t know what your MAC was before flashing this ROM ? Look at your WLAN Hotspot Log...)
When someone uses 2 Devices (with this ROM) in the same WLAN, only one would be connected.
You can edit 2 text files in "/etc/wifi" and change the MAC to the one you like or have.
nvram_mfg.txt
nvram_net.txt
Yes, of course, the filesystem should be remounted:
open Terminal:
mount
su
mount -t ext4 -o remount, rw /dev/block/mmcblk0p4 /system
Then set permissions 755 on directory "wifi" and the 2 files.
Now you can edit the files.
An other and easier way to temporary solve the MAC problem is to edit the 2 files in the ROM zip archive itself,
then flash the ROM again.
I hope that in one of the next releases the orginal hardware MAC should be used again.

There is a dev thread with a download to change your mac .... recently started
Sent from my GT-P7500 using XDA

lorinkundert said:
As there is a useless requirement for posting in development I have to come here to answer a simple question,
Yes on build 28 I have the same MAC address, that will be a big problem since the ROM should not be changing that.
Click to expand...
Click to collapse
Also, solution is here: http://forum.xda-developers.com/showthread.php?p=23468681&highlight=module#post23468681
or, same thread, post 1607. I downloaded the module, copied it to the path pershoot specified (backed up the old module), fixed permissions, rebooted, and all fixed.

Related

Debian working niceley on Desire.

Debian for Desire.
If you are able to try this on another android device, please do as I will be very interested in the results.
Download
http://www.multiupload.com/79TSI1AAF9
You will need.
-Root access.
-Busybox (included in most custom roms)
-1.4gig free on SDCARD
-VNC Client (ie. AndroidVNC)
-Terminal Emulator (ie. ConnectBot)
-7zip
Instructions
-Extract the file deSIREbian.7z on your PC using 7zip.
-Copy the contents (debian.img and deboot) to root directory of SDCARD.
-On your phone in terminal emulator type
su
sh /sdcard/deboot
Click to expand...
Click to collapse
You should get a blank screen showing "localhost:/#" after a couple of seconds.
-On your phone in your VNC client log in using these details
Password - password
Port - 5901
Click to expand...
Click to collapse
Nickname and Address are not needed, call it what you want though.
Changing the colour to 24bit and enabling local mouse pointer and full screen bit map are not neccesary but reccomended.
-Thats it.
Notes.
-You can log in via ssh, (gives a much better terminal, ie works properly with aptitude). Use [email protected] and password "toor"
-The version of Debian is Armel Lenny, installed using debootstrap.
-It is just the base package with LXDE on top, you only get a desktop, a file browser, an internet browser, and a pic viewer.
-If you want more packages there's tonnes of room on the image. eg apt-get install openoffice.org or apt-get install abiword or apt-get install any flipping thing u want
-You can access the SDCARD from Debian at "root/sdcard" (read-write)
-You can access Debian filesystem from Android (When Debian is running) at "sdcard/debian" (read only)
-debian.img is mounted at "sdcard/debian" using "dev/block/loop5"
-So far the only rom i have come accross that this dont work with is one of the cyanogen nightlies from last week. apart from that, working on opendesire, cyanogen, defrost, leedroid, official 2.2 with busybox...
Issues.
Debian cannot be shut down. You need to reboot the phone to do this. (You can kill the VNC server with "vncserver -kill :1" there is an icon on the festoons to do this.)
Update log.
deSIREbain.
-First release.
deSIREbain2
Fixed
-Loading a second terminal no longer breaks vnc.
-You no longer need to create the folder debian on sdcard.
Added
-ssh server (login with root and toor)
Removed.
-The image has been downsized from 2 gig to 1.4
Hey,
thank you for your work, i will test it so far and will tell you the results
got this error:
Code:
# su
su
# sh /sdcard/deboot
sh /sdcard/deboot
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: mounting /sdcard on /sdcard/debian/root/sdcard failed: No such file or di
rectory
net.ipv4.ip_forward = 1
chroot: can't change root directory to /sdcard/debian: No such file or directory
#
If you have the same problems try out
su
mkdir /sdcard/debian
losetup /dev/block/loop3 /sdcard/debian.img
mount -t ext2 /dev/block/loop3 /sdcard/debian
ls /sdcard/debian
thx to mercianary for help
greetings
I found this guide quite helpful at getting a bootstrapped Debian setup running.
http://www.saurik.com/id/10
I didn't need to insert the ext2 module as it's already loaded for me, I guess G1s didn't have that convenience back then.
blackstoneuser5 said:
I found this guide quite helpful at getting a bootstrapped Debian setup running.
www . saurik.com/id/10
I didn't need to insert the ext2 module as it's already loaded for me, I guess G1s didn't have that convenience back then.
Click to expand...
Click to collapse
I used parts of this for reference too. Its a great guide, explains things really well.
i've just updated this. link is in the first post.
Fixed
-Loading a second terminal no longer breaks vnc.
-You no longer need to create the folder debian on sdcard.
Added
-ssh server (login with root and toor)
Removed.
-The image has been downsized from 2 gig to 1.4
debian for desire--help please
hi
I spent much time for searching debian or ubuntu for desire, but nothin worked
know i found this and i have download everything and start to install over the terminal
but the " sh /sdcard/deboot" is not workin to
there's only this answer:
# su
su
# sh /sdcard/deboot
sh /sdcard/deboot
[: not found
losetup: not found
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
mount: No such file or directory
busybox: not found
sysctl: not found
chroot: not found
may somebody help me?
i really want to have it on the desire
thanks
It looks like you had not installed busybox
Which ROM do you use ?
oh i'm sorry
i'm a newbie and don't really know what a rom is
but i had problems with busybox and there was a somebody who said i can get the app titanium and let it install the busybox
could you please show me a tut how to install busybox
maybe a german tut
thanks
Getting error at: sh /sdcard/deboot
line 5: syntax error near unexpected token `else'
Rosi1337 said:
Getting error at: sh /sdcard/deboot
line 5: syntax error near unexpected token `else'
Click to expand...
Click to collapse
dont know why that happened.. works on mine. syntax looks ok to me.
try with this one (attatched), it's the same but without the bit that's not working for you.
what rom are you using, i shall try to replicate the error so I can try to fix properly.
thepuechen said:
could you please show me a tut how to install busybox
maybe a german tut
thanks
Click to expand...
Click to collapse
There should be a guide on installing busybox somewhere if you want to search for it, i know i remember seeing one a while ago.
Too be honest, your better off just flashing a rom that includes busybox, it would be MUCH easier.
have a look here and see what takes your fancy, I would recomend defrost, because it is stable and easy to overclock.
Thanks mercianary,
It works fine!,
I use customised DeFroST_0.9b_uvonly with USB-host patch.
By the way I would like to add more options to kernel line.
Where can I find like a menu.lst file ? or How to add it to kernel line.
There is no /dev/graphics/* in running Debian console.
I would like to use FrameBuffer on running Debian.
thanks,
Android VNC won't connect Trying to get a handshake, but then says that VNC connection failed
please paste at that time log
jacobtc said:
Android VNC won't connect Trying to get a handshake, but then says that VNC connection failed
Click to expand...
Click to collapse
Please paste at that time log.
Maybe vnc server does not running.
tknv said:
Thanks mercianary,
It works fine!,
I use customised DeFroST_0.9b_uvonly with USB-host patch.
By the way I would like to add more options to kernel line.
Where can I find like a menu.lst file ? or How to add it to kernel line.
There is no /dev/graphics/* in running Debian console.
I would like to use FrameBuffer on running Debian.
thanks,
Click to expand...
Click to collapse
You should understand that this is not a really booted native linux. Instead you are working in a chroot environment. So there is no kernel running that can get parameters. Only the the stock kernel of your DeFroST. Also there is no FrameBuffer as the graphic hardware ist not accessible. Instead this approach uses a vnc-server to which you can connect via a local viewer.
The advantage of this approach is clear:
- run almost any linux package available in the debian repository
- use your phone as before with the nice android
The disadvantage:
- no graphic output, so no 3D-games (which are rare under linux on the arm platform ;-)
- you can crash your android by eating up to much ram (not such a problem - it restarts on its own and if not you just have to reboot)
Thread is dead?
It seems this thread is dead. The problems many users seem to have come from a dirty setup. The image is broken in many terms:
- wrong file permissions on important binaries, like su
- wrong file permissions on many device files under /dev, so the ttys are only accessible by root
- wrong permissions on other places so there are always errors when installing additonal software (e.g. with the man pages)
- wrong setup that uses the root user for the desktop - instead an unprivileged user should be used
- missing packages for timezones and locales so the time is only right, if you are in a UTC region and console programs having trouble displaying anything else then plain english
I can not recommend using this setup image. It is better to use one of the instructions available online to get a clean setup.
Su doesn't work because your allready root.
Getting anything but root to work would be a real pain.
As you said its a chroot environment, its never going to be perfect.
The image was made using debootstrap just like all the other 'clean' ones.
Yep, it is broken as hell, but it works for what most people would need it for...make,gcc,python,a proper web browser,torrents, and some emergency word processing on the train to work.
The problem most people have is not being able to mount the image, this is due to fro-yo a2sd taking up all the loop devices.
Just thought I'd add my 2 cents.
I tried this on a MIUI rom and the scripy didnt do anything - ie i ran it using:
"# sh /sdcard/deboot"
.....and all it said was:
"#"
I entered all the lines in the shell script but the last one said it failed to launch VLC and no commands registered property (not even ls)
So i tried it on Defrost 5.1, and the script still didn't work.
But when i entered everything manually, it did work. Not too sure about the green theme though.
But thanks alot! Saves me spending a few hours trying to coax a working debootstrap out of my computer.
Thanks!
Josh.
mercianary said:
Su doesn't work because your allready root.
Click to expand...
Click to collapse
Nope. Actually su works only for root. It's missing the setuid root flag like all other binaries that should have it set.
mercianary said:
Getting anything but root to work would be a real pain.
Click to expand...
Click to collapse
Nope. I am always working as a normal, unprivileged user in my chroot. You just have to be in the proper groups. No need to work as root. Android works also with an unprivileged user.
mercianary said:
As you said its a chroot environment, its never going to be perfect.
The image was made using debootstrap just like all the other 'clean' ones.
Yep, it is broken as hell, but it works for what most people would need it for...make,gcc,python,a proper web browser,torrents, and some emergency word processing on the train to work.
Click to expand...
Click to collapse
This is what I do not understand. There is no need that it is broken, as mine works without any errors. So I think something went wrong in creating yours. For sure a chroot is no running OS but you can server almost any service with it and run anything you want (if your ram does not get exhausted ;-).
mercianary said:
The problem most people have is not being able to mount the image, this is due to fro-yo a2sd taking up all the loop devices.
Click to expand...
Click to collapse
Yes. Everyone with a good rom should have a2sd+ (aka the old a2sd) which saves more space than the froyo one and leaves your loop devices for you.
jo

[Solved] 2+ Kindle Fires on Same Wifi Router Disrupt Each Other

Me and my best friend both have Kindle Fires now. I rooted & flashed the latest MIUI onto both of them successfully over the past week, so we're running the latest version available. What we've found is that when we both try to attach to his wireless router, they seem to disrupt each other or confused the router and eventually our wifi goes bye-bye on our Kindles. When just one of us is trying to attach to his router, it goes through fine & seems to stay connected well without any issue.
Can anyone offer any recommendations on how to perhaps customize the wifi connection on either the Fire or the wifi router to try and resolve this issue?
Thanks much for your help in advance! Please ask any questions if I left out any details that could help : ]
Does MIUI have the MAC address problem? That'd be the first place I'd check. THen I'd check the router and see exactly what they're trying to do. My thoughts:
Either they have the same MAC, same name, or are vying for the same IP.
http://forum.xda-developers.com/showthread.php?t=1406845
Thanks for the feedback, guys! And thank for that related thread link! I reviewed that post and I have to admit, I'm a lil lost with where to start or what to do with that. I have a feeling both devices may be running the same MAC address, but I'm in the process of confirming that today. I also tried forcing a static IP on the Fire when connecting, but that didn't seem to resolve the problem.
Anyone have any, dare I say, more simple instructions for how I might go about altering my devices MAC address with MIUI? I'm not sure that the information in that post is fully applicable to the MIUI rom, so I'm hesitant to begin trying to give it a go, and plus, I might need something a little more noob-friendly... I could use a little more handle-holding with this, as I'm fairly fresh to rooting & flashing ROMs (but fairly computer literate).
look at post #24 in the linked thread - seems to be a easier solution
Oh, thanks! ... That does look much more manageable Now to just figure out where to get the file from the stock ROM and replace it. I did a backup of my stock stuff via TWRP prior to flashing MIUI, so does anyone know where I can locate this file from the stock amazon ROM after I've completed a backup of stock via TWRP?
I then assume that after locating the stock version of the file, that I would just replace the file in the root directory/system/bin right on the Kindle when it's attached to my PC via USB.
Yah.. I'm a noob, but trying! : \
Stock file I need to find: /system/bin/wlan_loader
there is one attached 2 or 3 posts after #24 - that should do it for your needs
Great! Thanks again!!!
This part of the post gets me a little lost. I assume I need to purchase & download Root Explorer ($3.99 in Market). As for performing the same thing this person did, I'm not quite sure how to go about doing that. One question I have is: Is Root Explorer absolutely necessary to perform this file replacement? It seems a little more involved than just simply replacing the file on the device while it is plugged in to my PC via USB.
I used root explorer, mounted as r/w, made a copy of the original JIC, overwrote the existing file within /system/bin and modified the permissions to appear as the original (rwxr-xr-x) rebooted leaving the system as r/w
Sure enough mac address is the same as when I was in 6.1 Kindle Fire OS.
Click to expand...
Click to collapse
Specifically, here are the things I'm not 100% clear on:
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
3) Can file permission changes as described above be performed in Root Explorer?
I greatly appreciate any insight! This appears to be the solution to my problem, not it's just a matter of execution on my part. Thanks, guys!
would use file explorer from the market - no cost and does the same
if you activate "root explorer" and "mount as root" in the settings all at the bottom
here the link:
https://market.android.com/details?id=com.estrongs.android.pop&feature=search_result#?t=W251bGwsMSwyLDEsImNvbS5lc3Ryb25ncy5hbmRyb2lkLnBvcCJd
1) 'mounted as r/w' - I assume this means mounting as read/write; is this performed via Root Explorer?
Click to expand...
Click to collapse
file explorer does this with the above settings automatically
2) 'made a copy of the original JIC' - I do not understand what is meant by 'JIC'
Click to expand...
Click to collapse
would mean he means the file to exchange
3) Can file permission changes as described above be performed in Root Explorer?
Click to expand...
Click to collapse
you can also do with file explorer - long tap on file - properties - change permission
Awesome - b63 - you're excellent
Ummmm... But I have to ask a really stupid question. I can't seem to find the /system directory on my Fire. I already had ES File Explorer... and I'm in it now, and I can only look around on my SD card it seems... Is the /system directory on the main internal storage of the device, or on the 'SD card?' Any help in finding this directory on my device would be appreciated! Sorry for the nooby questions n such
are the root settings made in the settings of es ?
then you can set your start directory to / somewhere in the settings
or simply go one directory up
when you are on / then you see the system directory like all the others (sdcard also)
OK... I'M SO CLOSE!
I got up to the root directory ( / ) and found the /system/bin directory... I have the new (well, old stock version) wlan_loader file from the linked thread that I downloaded on my Kindle on the SDCard ready to overwrite the existing file.
I definitely have Root Explorer on in ES File Explorer - it prompted me to allow and I did every time it asked. I then tried to copy the stock version of the file over my current version in /system/bin, but it said that the copy failed. I then went and tried to delete the existing file in /system/bin, but it said something like 'this file cannot be deleted' I'm not sure what is keeping the file locked. Do I need to modify the permissions of the file to be writable or something?
I hard-pressed on the file and tried to play around with it, but the only close option I have is 'Properties,' which didn't seem to allow me to change anything about the file though. So, I'm stuck : \ Help!?
OK, I got it! I didn't flip the 'Mount /, /system as writable option after switching on Root Explorer :\ My bad! But I was able to overlay the file now Let's test my MAC address now after rebooting.
looks promising ...
GET-R-DONE!
Yahoo! I got it!
I rebooted and everything seems to be functioning just fine - I'm connected to Wifi like normal, no big deal... AND, my MAC address is totally different than what it was before, so I think this did the trick!
Now to test it concurrently with my best friend's Kindle to ensure we can sit on the same network / router together. If it doesn't work, then I'll look to replace his wlan_loader file as well
Thanks for all your persistent assistance b63! I really appreciate it : ]
Was fun, and I learned a lot : ]
but take care if you change his one as well not to end up with the same mac again ...
and as allways - glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

[Q] Cifs/Mount Manager "Empty Folder"

Been trying to get this to work for hours, followed endless amounts of tutorials, I've hit a brick wall and am finally at the point I need to ask for more specific help.
I have 32gb Nexus 7 wifi only
Version: 4.2.1
Kernal: Motley's kernal 3.1.10-motley-v3+
Build Number:JOP40D
I started with CifsManager, couldn't get it to work because of no/wrong modules, tried many I found in tutorials around the net, eventually found I needed a new kernal, settled on Motley's, this finally allowed cifs to mount the folder, but the folder is always empty.
Came across Mount Manager, set it up, same problem.
Here's what my settings look like:
CifsManager:
Share Path: 192.168.1.18/y
Mount Point: /mnt/sdcard/cifs/pcY
Username: Comp1
Password: Password
Options: iocharset=utf8
I have tried it with options blank, same thing, yes my share is called y, Comp1 is the account I set up to access shares, no my password is not really password but you get the idea. I can access this share fine from other devices including my wii using the same settings.
Mount manager is basically the same except I made the mount point /compY because I didn't know if it would conflict, and it has file_mode and dir_mode = 0777.
Thank you for your time and any help is greatly appreciated.
Still searching for a solution, even a nudge in the right direction would help a lot right now.
I found out how chainfire solved this problem. (And did not said how ) I think my thread got lost ist the Android General section.... I should have posted it in the Nexus 7 General. (I tested it on my Nexus 7)
http://forum.xda-developers.com/showthread.php?t=2062768
vorcers said:
I found out how chainfire solved this problem. (And did not said how ) I think my thread got lost ist the Android General section.... I should have posted it in the Nexus 7 General. (I tested it on my Nexus 7)
http://forum.xda-developers.com/showthread.php?t=2062768
Click to expand...
Click to collapse
Thank you very much for your reply.
I am very new to this, I can't quite follow what I am supposed to do, I think start the file debuggerd as a system service? I can find the file, but I can't find out how to start it, I've done a few searches on this site and google but have come up empty, could you please explain exactly what I need to do to make this solution work?
Thanks again for your help
(For germans: "Bitte nagelt mich nicht darauf fest" (Auf die Informationen) Sorry, I don't know the english phrase for this...)
The "debuggerd" is an "debugger daemon". It can be started with "start debuggerd" and stopped with "stop debuggerd". I think errors at excecution are posted in dmesg or logcat.
The main thought behind this, that the debuggerd is started by "start" with higher privileges even then our normal su. (Or it does mount something, I don't know) So, if you backup the original /system/bin/debuggerd and write your own commands into that file and start it via "start debuggerd" these commands are executed with these "high privileges". For example, if you write these content in debuggerd and start it, the share should be available for all apps. (Well, only if "others" have r (? wx ?) permissions on server...)
/system/bin/debuggerd
Code:
#!/bin/sh
busybox mount -t cifs //server/share /mnt/sdcard/mnt -o username=max,password=mustermann)
You can also mount devices with this method...
Well, you can't use this with the manager, because the manager needs to be changed to support this.
I hope this helps you.
You can turn on your "ADB over network".Then you con connect from your device with
adb connect 127.0.0.1:5555
Click to expand...
Click to collapse
now youre ready to mount but the foders are visable only in the apps that are been started befour mount can see the folder.
Tornadough said:
Still searching for a solution, even a nudge in the right direction would help a lot right now.
Click to expand...
Click to collapse
Here's a solution that can be implemented by ROMs or kernels to fix app mount support in Android 4.2 without requiring modifications to CifsManager or other apps.
I'd recommend asking your favorite ROM to incorporate the dalvik/init.rc patches.
vorcers said:
The main thought behind this, that the debuggerd is started by "start" with higher privileges even then our normal su.
Click to expand...
Click to collapse
What's happening is that the debuggerd process is spawned directly by init, which uses the default mount namespace, so any mount operations are shared with/visible to all other processes.
The problem is that when an app calls "su" to mount a file system, it's already walled off in a separate mount namespace by virtue of the app itself having been spawned from zygote. Basically, any process whose ancestry can be traced back to zygote can't mount file systems visible to other apps. Those whose process ancestry don't include zygote can. Which is why manually mounting file systems from adb (with either "su" or "adb root") also works.
After all this time nobody has updated any app to fix this problem?

[GUIDE][Dual Boot][TheEasyway] How to setup Linux RootBind Method [Updated May 16th]

Hello everyone ! I made this guide for all who want to try to dualboot Android and Ubuntu using the RootBind method.
But first, what is RootBind ?
Actually, the RootBind method consist to have a Linux file system, living in a folder of our Android partition.
The default location for this linux file system is /data/linuxroot.
The way to switch between Android and Linux is to flash an Android kernel or the linux kernel. That's all.
It means you'll be able to have a linux installation, without erasing Android ( Still available, not touched at all ) and it means that you can easily manage your Linux installation.
You dont want it anymore ? Just delete a folder. You want to try another version, but you dont want to lose your current data ? Just do a zip of the folder, and extract a new version instead.
Advantages :
No need to repartitionate your tab.
It works with all TF101.
It doesnt touch current Android Installation.
It has same free space as your /data Android partition.
You can easily access it from within Android.
It has good performances
Kernel has everything working
And you only need to flash an Android or Linux Kernel to boot desired OS.
Everything is possible thanks to @jrohwer and @DjDill and @TravellingGuy.
Dont forget to thanks them : jrohwer Kernel Thread - jrohwer 14.04 Kubuntu IMG / DjDill images thread / TravellingGuy Image thread​Of course, every manipulation is risky, Me, jrohwer, DjDill, Travelling Guy, my dog, or even my math professor, can NOT be responsible for any damage on your tab, use this guide at your own risk​First Post : Dualboot setup
Second Post : How to change the linux location / How to have multiple linux installations
Third Post : FAQ & Tips​
DualBoot setup. Linux installation
First of all, here is all what you'll need :
The last rootbind kernel : Download Here Take the zip version.
[*]WARING : Note that if you use the last kernel ( 15 one ) YOU MUST TAKE MODULES AND EXTRACT IT IN /lib/modules/ when installation is done
The last Linux IMG of your choice, DjDill made imgs for this method with everything pre working here : DjDill images thread / TravellingGuy Image thread / jrohwer 14.04 Kubuntu IMG
Kernel for booting back Android You can find the KatKiss kernel there for exemple : KatKernel
A terminal emulator in Android or ADB Shell
If you dont want to use one of DjDill img, you'll need the bcm4329 tar from there : http://forum.xda-developers.com/showpost.php?p=43203818&postcount=569
You need to have a rooted device with a custom recovery. Check by here or by there
This method works on any TF101
Note that all command can be done with ADB shell aswell.
If you choose to install one of DjDill img :
Boot to Android as usual
Copy all download files to your tab. You can rename the kernel zip to Linux_Loader.zip and Android_Loader.zip to be clearer.
Now, I assume you have files in internal storage ( change sdcard0 by sdcard1 if it's on microSD )
We will now ensure terminal has root permissions :
Open Terminal emulator
Type su then Enter
SuperUser will ask terminal emulator root permission, allow it.
If you have an error with this command, your device may not be properly rooted.
Now we will setup installation location and extract our linux tar.gz ( Be aware it may take a while ) :
Code:
busybox mount -o remount,rw /
mkdir /data/linuxroot
chmod 755 /data/linuxroot
cd /data/linuxroot
tar -pxvzf /storage/sdcard0/yourubuntufilename.tar.gz
busybox mount -o remount,ro /
If you don't choose to install one of pre configured img :
Boot to Android as usual
Copy all download files to your tab. You can rename the kernel zip to Linux_Loader.zip and Android_Loader.zip to be clearer.
Now, I assume you have files in internal storage ( change sdcard0 by sdcard1 if it's on microSD )
We will now ensure terminal has root permissions :
Open Terminal emulator
Type su then Enter
SuperUser will ask terminal emulator root permission, allow it.
If you have an error with this command, your device may not be properly rooted.
Now we will setup installation location and extract our linux tar.gz ( Be aware it may take a while ) :
Code:
busybox mount -o remount,rw /
mkdir /data/linuxroot
chmod 755 /data/linuxroot
cd /data/linuxroot
tar -pxvzf /storage/sdcard0/yourubuntufilename.tar.gz
cd /data/linuxroot/lib/firmware
tar -pxvzf /storage/sdcard0/bcm4329.tar.gz
cp nvram.txt nvram_3429.txt
busybox mount -o remount,ro /
The setup is now complete.
In order to boot your linux installation, flash the linux kernel.
To get back to Android, flash the Android kernel.
​
How to change the linux location / How to have multiple linux installations
Here we are, so in order to have multiple linux instllations or change defaut linux installation location, you will need a Linux computer. ( Or a Virtual Machine, that's what I use, with Virtual Box for exemple.
You will need 3 tools to get it done too.
You can get it there abootimg, blobpack and blobunpack files at the end of first post ( Thanks to @shaola ).
I post the zip in attachement for mirror.
MORE INFORMATIONS ABOUT THESE TOOLS : http://forum.xda-developers.com/showpost.php?p=13713619&postcount=3
Now you have to get in the Rootbind kernel, the blob file. Blob file in Asus ROM can contain any partition of the device ( System, kernel, recovery etc ). In this kernel blob, there is only the kernel partition. Soooo, here we go for some commands.
Open your linux computer
Place all four files in same place ( better to have a folder created for this ). I'll take exemple of ~/kerneltf/ It's a exemple, so adapt in consequencies of course.
Now you have your four files in same place, blobunpack, blobpack, and abootimg-i686 so let's start with commands :
Go to the desired place :
Code:
cd ~/kerneltf
Unpack the blob containing partition imgs
Code:
./blobunpack blob
This will create partitions img. The one that interest us is the .LNX partition. ( Here blob.LNX )
Now unpack the kernel parition img
Code:
./abootimg-i686 -x blob.LNX
This will create 3 files, bootimg.cfg, zImage and initrd.img
The file we want to edit is bootimg.cfg. so open it with a text editor.
You'll see the last line is a cmdline. At the end we have the location of linux system place.
For exemple here : root=/dev/mmcblk0p7 bind=/linuxroot that means, the folder takes place in mmcblk0p7 ( /data partition of device ) and is placed in /linuxroot folder. So with Android layout it means /data/linuxroot.
You can now change the location of your folder, so you have some choices :
1-Change the folder location or name. ( This can be used to have multiple linux systems )
So you have this part : root=/dev/mmcblk0p7 bind=/linuxroot
If you want to change folder place/name change this part : bind=/linuxroot into whatever you want
For exemple root=/dev/mmcblk0p7 bind=/linuxroot2 or root=/dev/mmcblk0p7 bind=/linuxroot3 ( To have more linux systems )
Or root=/dev/mmcblk0p7 bind=/Linuxroot/Linux1
ATTENTION as said in rootbind thread : Make sure, however, not to put the Linux rootfs to the "internal storage" (/data/media) or any subdirectories thereof. This plays havoc with the Android media scanner when re-booting into Android and your tablet may slow down to a crawl.
2-Change the folder location in order to have it on an other partition like SDCard
For this choice, a 2nd partition on your SDcard is greatly recommended and should be in ext4. ( Must be the second partition, it is better for general use of SDcard )
So root=/dev/mmcblk0p7 bind=/linuxroot will become root=/dev/mmcblk1p2 ( can be p3 p4 or more if you have more than 2 partitions in your sdcard to have several systems on your SDcard ) the bind argument must be deleted as it will not be used.
3-Change the folder location in order to have it on first partition on SDCard
The problem here if you want your linuxroot folder in you SDcard with your other files, is that sdcard MUST be formatted in ext4 and so will not be recognized directly by Windows ( Using MTP in the TF will work but not Storage Mount ) cause Windows doesnt support ext4 partition. It's definitively the worse choice IMHO. The precedent process is definitively better choice. More than that it could make MediaScanner in Android going crazy too ( a .nomedia can maybe do the trick but not sure ).
More again, it hasnt been tested at all so you're the only responsible, but if you want to do it :
For exemple, to put folder on SDcard, you should change root=/dev/mmcblk0p7 bind=/linuxroot to root=/dev/mmcblk1p1 bind=/linuxroot
This means your folder is in sdcard ( The one in the tab ) at root in /linuxroot folder. ( /storage/sdcard1/linuxroot in android )
THIS HAS NOT BEEN TESTED YET, I CANT TELL YOU IF IT WORKS OR NOT.
Sooo, now you seted up your new location ( BE SURE TO DONT TOUCH ANYTHING ELSE ON THE CMDLINE, ONLY THIS PART ):
We will now repack the kernel to get it flashable.
Once again, be sure that you didnt make mistake with the file, and you only edited root=/dev/mmcblk0p7 bind=/linuxroot this part without deleting something or got a typo error.
We will now update the new bootimg :
Code:
abootimg-i686 -u blob.LNX -f bootimg.cfg
Then we will rename old blob file to create a new one with our modified kernel:
Code:
mv blob blobold
Now, we will repack our blob in order to make a new flashable zip with our kernel:
Code:
./blobpack blob LNX blob.LNX
You're done, make a copy of the old zip, rename it as you wish ( avoid spaces in the zip title ) for exemple Linux_Loader_2.zip
Then open it, and replace the blob file with your new one.
Now you're good to flash. Be sure to install a linux system in desired location before flashing it of course. See post 1 for this !
And a last one !
Envoyé de mon Nexus 4 en utilisant Tapatalk
Nice does work with TF101 G model (3G+) ?
Envoyé depuis ma TF101G-B80 with Revolution HD 4.0 (3.6g release) by Mike _1986
stephane.papin said:
Nice does work with TF101 G model (3G+) ?
Envoyé depuis ma TF101G-B80 with Revolution HD 4.0 (3.6g release) by Mike _1986
Click to expand...
Click to collapse
Yes, it works with all TF101
Si t'as besoin d'aide, hésite pas à me MP
Is a bootloader within the realm of possibility?
Thanks for the write-up.. I'm at the drinking my coffee while the untar keeps chugging stage, and it occurs to me that a bootloader would be very cool to have. Kernels flash so quickly, the recovery method isn't far off in terms of usability.. but it did motivate the question: is it possible?
So I'm just curious - is there any reason why we couldn't have the android and linux kernels both on disk to be loaded by a bootloader based on user choice?
Hello,
I have tried the "DjDill img" method.
When it finishes booting, it tells me that there are networks, and yhat I have to configure wifi.
I can't find how.
ifconfig shows lo and wlan0, and wlan0 is up but of course has no address.
if I try a iwlist scan, it tells me that wlan0 is an interface that doesn't support scanning.
In "settings manager/network connections", if I try to add a connection, it doesn't see my ssid.
Do you have any idea or point me to some doc/tuto.
Thanks in advance
nbenm
nbenm said:
Hello,
I have tried the "DjDill img" method.
When it finishes booting, it tells me that there are networks, and yhat I have to configure wifi.
I can't find how.
ifconfig shows lo and wlan0, and wlan0 is up but of course has no address.
if I try a iwlist scan, it tells me that wlan0 is an interface that doesn't support scanning.
In "settings manager/network connections", if I try to add a connection, it doesn't see my ssid.
Do you have any idea or point me to some doc/tuto.
Thanks in advance
nbenm
Click to expand...
Click to collapse
What kernel and what image did you used?
Tapatalké depuis mon Nexus 4 MIUI !
Couple questions
First, BIG thx to you and all the devs for hacking the tf-101!!
I've tried several of the images and they all worked as posted (Go figure ). I will be trying to compile a kernel for some custom work.
1 - Are the kernels compiled on the TF-101 and the tarballed?
2 - Any idea if Kali Linux 1.0.6 ARMHF Image, build will work?
I'll be using an external wifi dongle and not the internal.
Again much excitement to the tf-101 world!
Kingzak34 said:
What kernel and what image did you used?
Tapatalké depuis mon Nexus 4 MIUI !
Click to expand...
Click to collapse
I'm using kernel:Ubuntu-3.1.10-12-rootbind-oc1.0GHz.zip from your rootbind kernel link
I use image:tf101-14.04-xubuntu-armhf.tar.gz which is a DjDill image.
Before you reply me, I wanted to try "TravellingGuy Image". On its page, it was told to create wlan0 entry in the interfaces file. I did this and it works now.
But I can't understant why:
- iwlist scan doesn't work
- network manager doesn't see any of the multiple essids tahere are here
When I try to iwconfig essid "my_ssid", it says "cannot read /proc/net/wireless". Does it need some module ?
Thanks
nbenm
nbenm said:
I'm using kernel:Ubuntu-3.1.10-12-rootbind-oc1.0GHz.zip from your rootbind kernel link
I use image:tf101-14.04-xubuntu-armhf.tar.gz which is a DjDill image.
Before you reply me, I wanted to try "TravellingGuy Image". On its page, it was told to create wlan0 entry in the interfaces file. I did this and it works now.
But I can't understant why:
- iwlist scan doesn't work
- network manager doesn't see any of the multiple essids tahere are here
When I try to iwconfig essid "my_ssid", it says "cannot read /proc/net/wireless". Does it need some module ?
Thanks
nbenm
Click to expand...
Click to collapse
Ubuntu-3.1.10-12-rootbind-oc1.0GHz.zip doesnt exist ?
It's Ubuntu-3.1.10-12-rootbind-oc1.2GHz.zip
Or Ubuntu-3.1.10-10-rootbind-1.0GHz.zip
If you choose the Ubuntu-3.1.10-12-rootbind-oc1.2GHz.zip, wifi will works by default with defaut network manager without needing any cmd config or anything on pre installed DjDill img, IDK for Travelling guy img I didnt tested it, but you can try the other method if you're on Debian img and wifi doest work.
If you choose DjDill img, choose one of the lastest, This one http://forum.xda-developers.com/showpost.php?p=50335555&postcount=1
Or the 1.1 14.04 one, end of this post : http://forum.xda-developers.com/showpost.php?p=50335574&postcount=2
Or the Lxde build from same post.
But I suggest to use the first for now, it's the newer and have a lot of fixes.
Updated !
With second post and added jrohwer 14.04 IMG !
image: Kubuntu 14.04 With Tegra drivers.
kernel: Ubuntu-3.1.10-12-rootbind-oc1.2GHz.zip also tried Ubuntu-3.1.10-10-rootbind-1.0GHz.zip
It boots into KDE fine now but initially had some warnings even after running depmod -a. I had to issue the comnmand depmod -a a few times and it black screened once on boot.
I cant seem to get the wifi networking working even though it finds local networks clicking on the networks in the GUI doesn't do anything. Any help here. This is my first linux boot on the transformer but I have used Ubuntu since gutsy. I have to admit I am a little confused after reading a couple of posts here about exactly comes with these premade images. For instance the nvidia drivers are they included as modules in these images. When i read jrohwer's thread for the image he includes his apt sources list and states that the it took a little to get the nvidia drivers working?
Like I said on the other thread to setup Wi-Fi you have to setup in cmd line. Search on the net to setup with nmcli command or you install another network manager
Tapatalké depuis mon Nexus 4 MIUI !
Kingzak34 said:
Like I said on the other thread to setup Wi-Fi you have to setup in cmd line. Search on the net to setup with nmcli command or you install another network manager
Tapatalké depuis mon Nexus 4 MIUI !
Click to expand...
Click to collapse
Yes sorry I was struggling with the command for nmcli. I should have elaborated ... Tried various commands .. and this was what worked.
Code:
nmcli dev wifi
to list off the possible availables ap's then to join what you want
Code:
sudo nmcli dev wifi connect "whatever ap u want to connect to"
much easier to hunt down answers with a working intenet connection
Sorry bout that. I suppose my other question about the nvidia drivers is most likely too silly to answer ??
dasbooter said:
Yes sorry I was struggling with the command for nmcli. I should have elaborated ... Tried various commands .. and this was what worked.
Code:
nmcli dev wifi
to list off the possible availables ap's then to join what you want
Code:
sudo nmcli dev wifi connect "whatever ap u want to connect to"
much easier to hunt down answers with a working intenet connection
Sorry bout that. I suppose my other question about the nvidia drivers is most likely too silly to answer ??
Click to expand...
Click to collapse
What question ?
You dont have to do anything with the driver as in 14.04 build from jrohwer, is pre installed.
Kingzak34 said:
What question ?
You dont have to do anything with the driver as in 14.04 build from jrohwer, is pre installed.
Click to expand...
Click to collapse
Thanks i was reading jrohwer's thread for the 14.04 image and he was discussing the fact that it took alot of work to get the nvidia drivers up and running and then gives his apt sources list for download but after what u said it sounds like this is for people who want to get there own images together with working nvidia drivers. So compiling your own modules. Sorry I just wasnt sure. Anyways thanks for the trouble. I have connected to the ap but cant get a connection out to the internet. Oh well maybe I will try that lubuntu image on the first page. Thanks
dasbooter said:
Thanks i was reading jrohwer's thread for the 14.04 image and he was discussing the fact that it took alot of work to get the nvidia drivers up and running and then gives his apt sources list for download but after what u said it sounds like this is for people who want to get there own images together with working nvidia drivers. So compiling your own modules. Sorry I just wasnt sure. Anyways thanks for the trouble. I have connected to the ap but cant get a connection out to the internet. Oh well maybe I will try that lubuntu image on the first page. Thanks
Click to expand...
Click to collapse
Sounds weird, you successfully connected but dont have access to internet ?
Correct command for connecting on AP with a password is
sudo nmcli dev wifi connect <ssid> password <password>
And yes, the files that jrohwer gave, is for those who want to create a 14.04 with nvidia driver working img.
Kingzak34 said:
Sounds weird, you successfully connected but dont have access to internet ?
Correct command for connecting on AP with a password is
sudo nmcli dev wifi connect <ssid> password <password>
And yes, the files that jrohwer gave, is for those who want to create a 14.04 with nvidia driver working img.
Click to expand...
Click to collapse
Ya its at a hospital with no wpa type encryption only a login web page with name and password. I am most certainly connected ifconfig shows I have pulled a IP address etc etc. I have been reading about similiar problems in other linux type threads where there is automatic redirection to the login page. I actually use an app hellowifi to automatically enter the info in katkiss 4.4.2 so I am actually having trouble getting the address of that login page lol. I will give it a try at home where i have a wpa2 encrypted connection
dasbooter said:
Ya its at a hospital with no wpa type encryption only a login web page with name and password. I am most certainly connected ifconfig shows I have pulled a IP address etc etc. I have been reading about similiar problems in other linux type threads where there is automatic redirection to the login page. I actually use an app hellowifi to automatically enter the info in katkiss 4.4.2 so I am actually having trouble getting the address of that login page lol. I will give it a try at home where i have a wpa2 encrypted connection
Click to expand...
Click to collapse
Ho yeah I see, sometimes I cannot get login at the university hotspot, cause it doesnt want to redirect to login page.
I dont think you'll got problem with a 'normal' router.

Pac-Rom + Pink kernel 20140319: WiFi not working: workaround

Hello,
Sorry, I have to post this workaround here because I'm new on xda and I can't post an answer on the development forums. So if someone see that, please post a link to this thread on PAC ROM or pink kernel topic
It seems there is a new file in the modules directory which is a symbolic link named wlan.ko. As an easy workaround, simply replace this file (/system/lib/modules/wlan.ko) by this one: /system/lib/modules/pronto/pronto_wlan.ko (move this file to the parent directory and rename it). Then reboot, you should have the WiFi working now
PS: I guess it's maybe better to modify the symlink or load the correct module but it's harder to write command lines with a smartphone
According to some people, this bug should be fixed now.
Doesn't work!
Sadly, doesn't work on PA/C-RoM.
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Mycroft-Dev said:
Sadly, doesn't work on PA/C-RoM.
Click to expand...
Click to collapse
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
matttbe said:
Did you try the latest nightly version? I no longer have this problem with the latest PAC-ROM (And I think there is a another fix for your XT1033 )
PS: You can also try to just remove the symlink: /system/lib/modules/wlan.ko
Click to expand...
Click to collapse
Well, Wi-Fi still refuses to work after removing the symlink!
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Cheers, mate!
Mycroft-Dev said:
D'you know any other fixes? Tried lots of stuff, meself, but that is one stubborn bug!
Click to expand...
Click to collapse
No :-/
Maybe you can try to reinstall the latest nightly version of your rom (released after March 20th -- I think it's the case for C-RoM), reboot and check if the WiFi is working. If yes, don't disable it now then reinstall the latest version of Pink kernel.
But if the WiFi is still not working, it's annoying... You can reformat /system where kernel modules are installed but I think it's automatically done when installing a rom. Maybe they are not using the latest version of the kernel?
Mycroft-Dev said:
Edit: Thought I'd elaborate a bit. There's no wlan.ko in /system/lib/modules/, so I just copied the pronto_wlan.ko, renamed it to wlan.ko, repacked it and flashed it.
Click to expand...
Click to collapse
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Clarification
matttbe said:
What did you mean by saying: "repacked it and flashed it"? If you flash the ROM, it will format and reinstall /system partition (correct me if it's wrong).
When I had this bug, I replaced wlan.ko symlink file by this one: pronto/pronto_wlan.ko. Then I rebooted (or I guess you can use this command if modprobe is available but it's easier to reboot : adb shell "modprobe -r wlan && modprobe wlan").
Click to expand...
Click to collapse
As in, I repacked the kernel, and then flashed it.
I'll try tweaking a bit here and there, and let you know how it goes.
And yes, I flashed the latest C-RoM.

Categories

Resources