Hi
I saw that the TF101 and SL101 are very similar.
On ASUS Website they even provide me with both, TF and SL firmware if I go to downloads.
So my question:
Are any Custom ROMs compatible to both, TF and SL?
Or are there modifications needed?
@Devs: Who's ROM is compatible to SL101?
Use the slider compatibility pack available here: http://forum.xda-developers.com/showthread.php?t=1586382&highlight=slider+compatibility
Then Any tf101 rom works with the slider!
1. Flash ROM
2. Flash slider compatibility pack over it
3. ???
4. Profit.
Thanks.
Another question to ROMs:
I know there is a possibility to run Ubuntu on the TF in dual-boot with android.
What about this on SL101?
If I use this tool: http://forum.xda-developers.com/showthread.php?t=1364095 will I be able to flash the Compatibility Pack afterwards?
And will Ubuntu run clean then?
That may be another matter entirely, as the compatibility pack is for Android 4.0 ICS. I don't think it would help. You can still flash ubuntu, but you may encounter a few bugs, it's an ARM processor build though. It will work, I just can't say whether it would work well or not. Don't flash the compatibility pack with it though.
But didn't I get this right?
I will hae both, Android and Ubuntu on my device then.
I have to flash the comp pack over the Android ROM to get it working perfectly.
So if I use the tool above I install my Android and Ubuntu ROM together. How do I get Android working correctly then?
How does this ubuntu dualboot install?
is it like this:
One half CWM + Android, Other half Ubuntu
or like this:
CWM is above everything and Ubuntu and Android are the next level deeper?
I mean does CWM even have access to ubuntu through normal flash methods?
What if I want to change my android ROM after installing ubuntu? If I just flash using CWM, will I overwrite my ubuntu?
No, the ubuntu zip that you flash simply tells the tab to boot the ubuntu system image you store on your internal memory rather than your android os, your android os is unaffected as you flash the android zip to reboot android.
So I have to flash a zip file every time I want to boot the other OS again?
I mean everytime i want to switch between Ubuntu and Android?
I thought it would be a real Dual-Boot. Unfortunately I am completely new to Ubuntu. The last time I had a dual-booting device was my HD2 with Windows and Android using MagLdr... I thought it would be similar to this.
//Edit:
http://forum.xda-developers.com/showthread.php?t=1191141
If I install in dual boot config did I get that right:
It replaces the ClockWorkMod/Recovery Boot-Option with buntu boot option?
So I will be able to boot Android (normally), Ubuntu (by starting recovery) or flash a new ROM through NVFlash. But I will loose ClockWorkMod
I don't want to spam the thread with this so I ask here. Excuse me for this please.
Yes that is correct, Make Sure, you have NvFlash though. Otherwise you'd be pretty stuck in the event of an issue
Hi,
i'm currently thinking about installing ubuntu on TF101. I recently saw that new kernel 3.1.10 is becoming really stable and supports many tf101 features that 2.x kernel doesn't (in my opinion ubuntu with 2.x was more like a "proof of concept" than a real usable system)
So i think time is mature to a "one-click ubuntu" installer or, even better a dual boot rom with both android 4.0.3 AND ubuntu with 3.1.10 kernel (but i think maybe this technically will never be possible, what do you think ? ).
As today, installing ubuntu on tf101 is really too much of a hassle and, if you succeed (think about sbkv2 users using also wheelie) you then have to manually add files to upgrade kernel.
We are in 2012 and still using 1950's command line
What do you think ? could someone initiate this new project (i have a little knowledge, but really no time ).
Thanks !
TheMac
Eventually, It's on my list.
List:
1) APX 1-click root for peri.
2) APK version of peri..
3) scream at asus for patching root exploit (This is bound too happen..)
4) ???
5) Profit!
6) Workaround root for new patched firmware
7) Update PERI
8) Ubuntu 1-click installer.
Thing O Doom said:
Eventually, It's on my list.
List:
1) APX 1-click root for peri.
2) APK version of peri..
3) scream at asus for patching root exploit (This is bound too happen..)
4) ???
5) Profit!
6) Workaround root for new patched firmware
7) Update PERI
8) Ubuntu 1-click installer.
Click to expand...
Click to collapse
Uhm !
I like number 5 AND number 8
TheMac
I like the 1950's command line!!
still trying to finish my 1click installer foe Ubuntu on sbkv2 devices. Once that's done ill look into adding the newer kernel from jhinta. Ill see about making a 1click from that. If its all working.
Sent from my Transformer TF101 using xda premium
If kenshin is doing it im not gonna bother xD If he needs any help though I'm totally willing.
Thing O Doom said:
If kenshin is doing it im not gonna bother xD If he needs any help though I'm totally willing.
Click to expand...
Click to collapse
If you can do it, it would be better. I have been trying to rip apart exactly how everything is flashed still. Being slowed down from personal projects.
Hi Guys,
I am looking for linux working on TF300T, is there anyone who has anything working? I am planning to start with linux for TF300T, I want to know if anyone has tsarted, how do I collaborate and not reinvent the wheel. I have questions regarding what bootloader to use, lilo / grub / u-boot as Nvidia has a ubuntu distribution for its chip, which uses U-boot. Lot of questions can any dev please reply, so I can think of a place to start.
Thanks
Sent from my ASUS Transformer Pad TF300T using xda premium
So far I'm quite satisfied with my android linux device ( with some chroot debian thrown in for good measure).
I'm wondering about this as well. I've got some experience with linux (servers) but not a clue how the android boot structure works.
I have found this though: http://eeepadhacks.net/transformer-hacks/how-to-install-native-ubuntu-on-eeepad-transformer/
Not to spam, but does anybody have *NIX running on the TF300? I'm very interested since Android is based on the Linux kernel, so I would think that there is some form of *NIX running on this device, since I'm hoping that there is so I could actually use this as a "laptop" for my school work.
I am fairly sure that Android is Linux. However what people are missing is the GNU environment (and tools) that the majority of the Linux distributions have. You can see that Android/Linux is vastly different from GNU/Linux.
Thus, I think the question becomes something like "Is there anyone who has GNU/Linux working on the TF300T?"
There are two methods I know of to get GNU/Linux running on Android: Chroot and Dual boot.
* The chroot method runs the linux services and programs inside Android, but is available for basically most devices.
* The dual boot method works (mostly) with the original transformer (as Citruspers has mentioned)
I myself don't have a tablet yet, but I have been looking to get a TF300T (if I don't buy a TF700T - but that is for another discussion) on the basis I can dual boot Android with a GNU distribution.
Linux = kernel. Android runs a Linux kernel. Android IS Linux.
The two biggest differences between Android and "ordinary" Linux distributions are libc (called bionic in Android) and the lack of a real X server on Android (there is a Java version at https://code.google.com/p/android-xserver/ , but it's wayyyy too slow to get anything done (it's still awesome, though). It needs to be implemented in a lower level language).
/dev/void said:
Linux = kernel. Android runs a Linux kernel. Android IS Linux.
The two biggest differences between Android and "ordinary" Linux distributions are libc (called bionic in Android) and the lack of a real X server on Android (there is a Java version at https://code.google.com/p/android-xserver/ , but it's wayyyy too slow to get anything done (it's still awesome, though). It needs to be implemented in a lower level language).
Click to expand...
Click to collapse
Any chance Wayland will work any better with Android than X? I wouldn't mine tossing a *box or even WindowMaker on my tablet (assuming they play nicely with Wayland).
Edit: Yes, I realize that Wayland barely works with GNU/Linux as it is, and it probably won't be usable even on the desktop until I'm upgrading to a new tablet. I'm not expecting it anytime soon.
Extracted from http://androidroot.mobi/2012/06/17/ubuntu-on-the-transformer-prime-preview/ regarding Ubuntu on Prime 201...
It has been a while since the last post about ubuntu on the Transformer Prime. This post is going to explain a few of the new changes, and show a video preview of the system in action.
There have been a few changes since the last update:
3.1.10 Kernel -- Asus don’t update the kernel while remaining on the same android major release, so they won’t update the kernel until at least Jellybean, but we have worked really hard to bring us up to the latest kernel. This has given us the ability to use the latest Tegra ULP GeForce binary from nvidia and maintain acceleration with the latest releases.
Linux as a bootloader -- With some work to the process we have managed to get kexecboot working to give us a boot menu that will boot not only multiple kernels from eMMC, but also to allow booting from USB, SD, and MicroSD. At this point in time the guest kernel also requires two patches, one for speed (it is really slow to boot without this patch, 30sec-5minutes) and the second to copy ATAGS, this second patch is important so that the new initrd and command line get used.
Ubuntu 12.04 LTS -- The last image was 11.10 which is a little less stable. 12.04 has a new gpower applet which can read the battery levels. 12.04 also includes the mtrack driver allowing the trackpad to work. The biggest change with the new image is the use of armhf over armel.
LVM -- Turning mmcblk0p8 (/data under android) to an lvm volume group has allowed both android and ubuntu to coexist on the eMMC without needing nvflash for reformatting. This however does require a modification to the android initrd to reflect the change and for the lvm binary to be included so it can mount /data. Ubuntu natively supports booting from logical volumes.
Click to expand...
Click to collapse
I know, I know this is TF300 forum, but it seems the TF300 is more similar to the TF201 than the primitive TF101
EndlessDissent said:
Any chance Wayland will work any better with Android than X? I wouldn't mine tossing a *box or even WindowMaker on my tablet (assuming they play nicely with Wayland).
Edit: Yes, I realize that Wayland barely works with GNU/Linux as it is, and it probably won't be usable even on the desktop until I'm upgrading to a new tablet. I'm not expecting it anytime soon.
Click to expand...
Click to collapse
Good call. While we're on the desktop managers, how about KDE's entry in the mobile device space? Aren't they supposed to have a native linux tablet going to retail soon?
My chroot runs smooth but native would be fun! Hope someone get's this working.
I hope once the guys at androidroot.mobi release the installer package for Ubuntu for the Prime, it works on TF300.
I'm looking for the ubuntu on my tf300t too.
Its strange, I know Ubuntu showed off dual booting kernel for android devices like 6 months ago. You basically docked your phone and it became a full Linux desktop with unity. But haven't heard anything since, only a page on Ubuntu's site for hardware manufacturers.
http://www.ubuntu.com/devices/android
(Sorry to revive this old-ish thread, but I didn't think it was any better to start a new one and clutter up the forum)
It seems that no one gave an honest shot into loading linux NATIVELY (not via the "linux on android" project). The original poster mentioned being interested into giving it a shot -- so how things are going on your end aditya?
I am by no means an Android rom developer, hacker, or even linux hacker, but I started my first steps into it, I thought of getting things done by this method:
Instead of wiping the whole recovery partition like the guy on the TF100 did, i'd use a somewhat altered version of a recovery where I launch a recovery-like menu where the user can continue to the "real" recovery, or boot linux
(Basically, I got myself a version of the /sbin/recovery, which has its menus altered to only show "linux" or "recovery". Selecting recovery launches the real /sbin/recovery)
If the user choose to boot linux (which could be automatically selected after a timeout), that's where kexec steps in and boots the right kernel and linux pre-baked image files
I got all that covered (my pre-recovery menu is 90% working, custom kexec'd kernel w/kexec binaries packed into my recovery), but i forgot a small detail: There is no way I could load a full 1Gb Ubuntu image into memory, (in other words, what does happen to the old mount points managed by the first kernel when I load the second kernel via kexec? Gets broken, right?) So I came into realization I would need an initial ramdisk to mount my mmc so I could finally load/mount my main 1 Gb image file.
Honestly, for somebody not into hacking, I am under the impression this is getting out of hand. This could work, but I heard we could have nvflash fully working (read: re-paritioning coming our way, just like for the TF100 where there's linux natively on its own partition).
Is there anybody else trying to do such things like I do? I might also need a reality check on what i'm doing-- altough it seems the right way to me now
Linux and GNU
It's true, Linux is the OS kernel, but with the word Linux you can also mean the GNU/Linux environment with the kernel and all the applications running on top ("The gimp" or "Libre Office" for example).
Should be nice to have a GNU/Linux system running on a tablet device; I read that Canonical (Ubuntu) is working on a project for multi-core devices but I don't know about the development stage.
/dev/void said:
Linux = kernel. Android runs a Linux kernel. Android IS Linux.
The two biggest differences between Android and "ordinary" Linux distributions are libc (called bionic in Android) and the lack of a real X server on Android (there is a Java version at .... , but it's wayyyy too slow to get anything done (it's still awesome, though). It needs to be implemented in a lower level language).
Click to expand...
Click to collapse
Trying to make this work too.
I have a basic changeroot with gentoo and compiled a kernel and initrd. I wanted to try it out using fastboot (fastboot -i 0x0b05 -c real_root=/dev/sdb1 boot kernel-genkernel-arm-3.3.8-gentoo initramfs-genkernel-arm-3.3.8-gentoo) but it doesn't even try to load the kernel. I get an error 0x120000 on the screen of the TF300. I googled a bit and found out that the TF201 has the same problem, you have to flash a boot image.
How can I make a boot image using the gentoo files? I looked into abootimg but it seems it won't work. At least it won't split up the original images, so I fear it uses another format. Has anybody tried mkbootimg?
AEblefisk said:
I have a basic changeroot with gentoo and compiled a kernel and initrd. I wanted to try it out using fastboot (fastboot -i 0x0b05 -c real_root=/dev/sdb1 boot kernel-genkernel-arm-3.3.8-gentoo initramfs-genkernel-arm-3.3.8-gentoo) but it doesn't even try to load the kernel. I get an error 0x120000 on the screen of the TF300. I googled a bit and found out that the TF201 has the same problem, you have to flash a boot image.
Click to expand...
Click to collapse
I only know a part of the story here, but here's my findings so far. I never got "fastboot boot" to work on my TF300, always giving me that 0x120000 error. I am under the impression (I MAY BE WRONG) that "fastboot boot" requires a more devloper friendly device (think HTC G1, GNex, anything Google branded).
That being said, I am curious why you wrote "real_root=/dev/sdb1" as your kernel parameters
AEblefisk said:
How can I make a boot image using the gentoo files? I looked into abootimg but it seems it won't work. At least it won't split up the original images, so I fear it uses another format. Has anybody tried mkbootimg?
Click to expand...
Click to collapse
Personally I was able to look at how a recovery image was used and flashed onto a TF300. Without going into the details, I looked at how xplodwild's recovery was being made, and hacked around that recovery to use my own (basically trivial modifications from his).
To flash my image files, I am using "fastboot flash recovery" with my own recovery, which is basicaly a mkbootimg based image file like you said (you were on the right track), but wrapped around in a BLOB file format (using blobpack / blobunpack, see this xda thread).
So to answer your question, the only way I found so far to boot my custom kernels and init rootdisks is to flash it onto the device outright.
BTW: if you were to look at a pre-baked img file, (or, if you had no idea whats the file contents like), you could load the file into a hex editor (I use 'hexer' on ubuntu/debian, thats a command-line one). If you see "SIGNED-BY-BLOB", thats a blob file (a nvidia tegra and/or asus file format). If you see something else (usually starting with "ANDROID.."), thats usually something you can either mount or unpack using linux natively (most probably with "mount -o loop file /mnt/mountpoint")
EDIT: Slightly off topic, but still for AEblefisk: if you compile your own kernel, i suggest turning on activating the framebuffer tux logo option. More importantly, you could as well try and activate the framebuffer console too, however apparently "fbcon is broken on 2.6.39.4", so says Rayman. But at least, you'd get a hint that your own kernel is loaded and running if you see 4 tuxes on screen (one per core)
Thanks for pointing me in the right direction.
Now I managed to make a blob with the gentoo kernel and ramdisk. It flashes sort of OK with fastboot, sending in 2 seconds, but the write time is 0.016s and it seems nothing is written. I boot into Android when I reboot. (I'm flashing to boot, not recovery). Maybe I'm missing some offset or blocksize parameters?
bilange said:
...
That being said, I am curious why you wrote "real_root=/dev/sdb1" as your kernel parameters
...
EDIT: Slightly off topic, but still for AEblefisk: if you compile your own kernel, i suggest turning on activating the framebuffer tux logo option. More importantly, you could as well try and activate the framebuffer console too, however apparently "fbcon is broken on 2.6.39.4", so says Rayman. But at least, you'd get a hint that your own kernel is loaded and running if you see 4 tuxes on screen (one per core)
Click to expand...
Click to collapse
The real_root is for the gentoo initrd to find the real root filesystem on microSD. I have no idea if it will turn out to be mmcblk1p1, sdb1 or something completely different. I'll probably have to correct that once my initrd boots.
Yes I'm definitely trying to make the framebuffer logos work. Seeing that lineup of 4 tuxes is a goal in itself
I'm using 3.3.8 in gentoo so I hope fbcon is fixed.
AEblefisk said:
Now I managed to make a blob with the gentoo kernel and ramdisk. It flashes sort of OK with fastboot, sending in 2 seconds, but the write time is 0.016s and it seems nothing is written. I boot into Android when I reboot. (I'm flashing to boot, not recovery). Maybe I'm missing some offset or blocksize parameters?
Click to expand...
Click to collapse
I never touched boot so far to tinker around Linux booting, for the simple reason we never use the recovery partition except to flash/nandroid backup (which I rarely do), plus it gave me with Android booting if I dont press the volume button on startup. As far as development went, I think this was a win/win situation, although lilstevie (the guy who did make Ubuntu boot natively on his TF101/200) told me to "never touch recovery, flash boot instead", he was most probably talking about deploying our custom OSes to the world to use.
Now i'm kinda lost as to why the regular Android boot is being shown up. Having 0 experience with the boot partition (which i thought was similar to recovery), i can't really help you. Maybe you should get on freenode into the #asus-transformer and ask around (Don't let the numbers of nicknames scare you, this is a low activity channel, but the most knowledgables people are hanging in there. Just be sure to do your homework (aka Google etc) before asking, you should be fine )
As a sidenote, you should probably use some (most?) of the kernel parameters used in /proc/cmdline from a live Android OS. Most specifically the "tegraboot=sdmmc gpt gpt_sector=..." part. This makes sure your kernel reads the partition table at the right (unusual) location instead of reading where ever it was on a regular system (the first 512 bytes of the drive? don't quote me on this). I suppose this doesn't prevent the kernel from booting, but it will make the SSD partitions visible from your OS.
AEblefisk said:
The real_root is for the gentoo initrd to find the real root filesystem on microSD. I have no idea if it will turn out to be mmcblk1p1, sdb1 or something completely different. I'll probably have to correct that once my initrd boots.
Yes I'm definitely trying to make the framebuffer logos work. Seeing that lineup of 4 tuxes is a goal in itself
I'm using 3.3.8 in gentoo so I hope fbcon is fixed.
Click to expand...
Click to collapse
Would that be a 'vanilla' 3.3.8? I'm asking because, in case you don't know, I think you can't have much success using the regular kernel from kernel.org, and hope it will detect all the devices (specifically touch, sensors, wifi, gps(?), etc). It will maybe boot (your guess is as good as mine), but it will surely lack a few things here and there. That's why there are a ton of devices specific github kernel code base here and there: it's basically a 'stock' kernel source code, with the constructor's additions to make their various devices work, with community enhancements on top of all that. I may be wrong on the following (if there are any veterans reading this, feel free to call me a noob and point me to the right direction), but if you try to compile ASUS' kernel source code for the TF300, funnily enough everything compiles silently UNTIL it gets to the Tegra parts where it gets noisy with over 9000 warnings all along (but it compiles). That led me to believe that 1) NVidia or ASUS are lousy coders and 2) They added (most likely) OR modified a bunch of code to the stock kernel tree to make it 100% functioning on their devices.
All that wall of text only to say that I assume that the broken fbcon issue is most probably due to either ASUS/NVidia additions to the kernel code, or a bug from the 'stock' kernel code, and i'm assuming it was fixed in later versions (which lacks device's constructor modifications then again).
--
Offtopic: it seems ASUS has released the kernel source code for TF300 for their JB update! Compile all the things!! (And hope fbcon as been fixed so I can see something out of the screen)
I'll definitely do my homework now I'm worried I may have flashed some other place than boot, since Android is still booting, so now checking all corners of the tablet is on top of the agenda.
I know some things may not work with a vanilla kernel, but I was hoping enough would work for it to boot. Then I could worry about the rest afterwards. Maybe using the JB kernel source will be easier, but I don't know how much has been changed in android which is used in linux. I suspect Google has worked more on modifying linux for android use than ASUS has worked to make their hardware run in android. Another option is to work on what Nvidia has published.
Now I'm getting more experienced. I hope I get some real progress before I brick it
It turned out I wasn't writing anything to flash. It seems the first blob(un)packing tools mentioned in http://forum.xda-developers.com/showthread.php?t=1697227 aren't working (for me on my tab anyway). But when I tried the BlobTools2 with the blobpack -s option my resulting linux blob was written to flash (using fastboot -i 0x0b05 flash boot boot.img).
Unfortunately my gentoo linux kernel wasn't any good. I never got past the first Asus logo and on top of that CWM recovery couldn't restore Android. CWM went through the motions but nothing booted. I had to flash the stock blob, then I got my Android back.
Is there any way to install linux distribution aside from android onto my TF101, dual boot if possible, with not-so-many-bugs?
I tried x3maniac's way of installing it, however, I had 1.35GB available disk space (which ****** sucks), and I couldn't even load pages in Chromium, so basically, it was no use. After apt-getting codeblocks, i couldn't save a .cpp file lol.
Thank you in advance.
You can get an app called complete Linux installer from the market. Thing is, you need a kernel that supports loop devices, and it runs on TOP of android. That's the best I've seen
Sent from my Transformer using Xparent Blue Tapatalk 2
erik.loncarek said:
Is there any way to install linux distribution aside from android onto my TF101, dual boot if possible, with not-so-many-bugs?
I tried x3maniac's way of installing it, however, I had 1.35GB available disk space (which ****** sucks), and I couldn't even load pages in Chromium, so basically, it was no use. After apt-getting codeblocks, i couldn't save a .cpp file lol.
Thank you in advance.
Click to expand...
Click to collapse
For x3maniac's you need to run 'sudo resize2fs /dev/mmcblk0p8' in the terminal after installing to resize the partition to ~5gb, the chromium issue has also been fixed with the new kernels and they are also overclocked. The only problem is that x3maniac's kernels have problems with the system freezing.
NoDiskNoFun's net-install was very stable especially with jhinta's kernel, the only problem I had with it was that the boot time would take 1-2 minutes extra if the system couldn't connect to a known wifi network. The major thing is that you wont be able to complete the install without a wifi connection (has to download several hundred megabytes of packages to setup).
lilstevie's 11.10 image while stable, was fairly slow, lacked hardware acceleration and couldnt report battery levels (only from the terminal).
NoDiskNoFun's ubuntu would probably be the most stable and the fastest for you, x3maniac's still has it's issues.
Net-install Wifi issues
Mn5612 said:
NoDiskNoFun's net-install was very stable especially with jhinta's kernel, the only problem I had with it was that the boot time would take 1-2 minutes extra if the system couldn't connect to a known wifi network. The major thing is that you wont be able to complete the install without a wifi connection (has to download several hundred megabytes of packages to setup).
.
Click to expand...
Click to collapse
Hey Mn5612,
I've installed x3maniac's tubuntu, and while I do really like it and appreciate all of his work, I have heard that NoDiskNoFun's net-install had many advantages in terms of customization and stability. I flashed his img over my recovery partition, and everything was fine, booted into setup, but then I can't get the wifi to connect to complete the installation. I am running open WEP
Nothing comes up when I do a scan, status is "Could not get status from wpa_supplicant," and when I manually try to add values I get "Failed to enable network in wpa_supplicant configuration." So I go through setup, and nothing downloads while I'm completing all of the steps.
I tried using v0.5 where the install is primarily in terminal, tried all of the WEP options, then I tried tethering my phone with all of the different encryptions, then left it as an open hotspot, nothing, no detection, no connection.
I've looked all over the forums and at general llinux forums for solutions, but no one seems to have quite the same problem, or their solution is not feasible on this distro or someone working in windows. I have a very basic knowledge of linux, I mainly run a windows box, but I always like to learn more. In any case, any help would be greatly appreciated. Thank you
erik.loncarek said:
Is there any way to install linux distribution aside from android onto my TF101, dual boot if possible, with not-so-many-bugs?
I tried x3maniac's way of installing it, however, I had 1.35GB available disk space (which ****** sucks), and I couldn't even load pages in Chromium, so basically, it was no use. After apt-getting codeblocks, i couldn't save a .cpp file lol.
Thank you in advance.
Click to expand...
Click to collapse
Hey,
I had the same question about a year ago. I looked around and found this thread from lilstevie. It will guide you to install a dual boot setup between a nvflashable ROM of your choice and Ubuntu. I had it running very well with no major issues, but of course there will be some bugs. Heck, Linux often has bugs even on a normal PC platform. I remember flash player was probably the biggest issue, but I'm sure there are ways to get it working. If I remember correctly I think I gave Ubuntu 8gb and I gave Prime 3.2 whatever was left out of the 32gb tablet.
First a disclosure, I'm a Windows network guy so I know my way around symlinks and vhds and that ilk, but Linux / Android just isn't letting me do what I am trying to.
My goal is pretty simple: I want to migrate all the erroneous files laying around the /sdcard/ to folders that are more organized. Ideally, I would like to be able to scrip this process so the things I use regularly and the things people I work with use regularly can be 'formated' similarly since I'll want to do this for my other androids I own and I'll no doubt have a few (not necessarily a lot) of people who see my system and go "DO WANT" (it happened with my Windows setup, so I expect similar).
The problem I am having is not only can't I can things to "stick", but I can't even get a script to work at all.
I've been most successful so far running down my list through ADB, but the problem is, when I reboot, everything resets.
I've also tried writing a script and running it through the below version of busybox:
https://play.google.com/store/apps/details?id=com.jrummy.busybox.installer
That just errors out completely =(.
The links I am trying to make are as follows:
https://www.dropbox.com/s/gbieej5genkzwk0/Symlinks.xlsx
The script I tried using is as follows:
https://www.dropbox.com/s/kajafjlzzy0bcm6/mount.sh
The resource page I am using for Linux commands is as follows:
http://www.ss64.com/bash/
The resource page I am using for ADB is as follows (though should be obvious!):
http://developer.android.com/tools/help/adb.html
The device I am currently working with is a Galaxy S3 T-999 running Slimbean 4.3, though once successful, I plan on implementing these on changes on another Galaxy S3 T-999 runing Slimbean 4.3, a Galaxy S2 T-989 running Slimbean 4.3, a Galaxy S1 i897 running Slimbean 4.3, a Transformer TF201, a Vizio Co-Star running Stock Vizio (maybe if it doesn't make me want to kick it, which is the more likely outcome) and an Android AK-802MiniPC running Stock Jellybean.
Heck, maybe I'll try to tear the offal iOS7 off the iPhone 4 I inherited and try to install Android on it and do that too, lol.
Thanks for any help!
You may want to research how to set up your init.d
http://ilovegalaxyy.blogspot.com/2013/06/how-to-enable-initd-on-android-mobile.html
soupmagnet said:
You may want to research how to set up your init.d
http://ilovegalaxyy.blogspot.com/2013/06/how-to-enable-initd-on-android-mobile.html
Click to expand...
Click to collapse
That pointed me in the right direction --- The app you tossed at me illustrated that the problem is in fact that my Kernel doesn't support init.d and that's probably where all my problems are stemming from. Thanks!
That Universal Init.d app seems to get around the problem, but I think I am going to look into another kernel. I know from experience the Cyogen kernels are compatible with the rom I am using. I'd prefer to stick to Slimrom because its such a nice, slim setup, but I guess that means if I have too many problems and my primary goal is cross device compatibly, Cyogen might end up being my best bet.