Related
Hi all,
Yes, I'm a newb here at xda, but not to the hacking scene. As my interests are in custom Firmware development/modification I am having to post here in General because of the 10 post limit for the Development forum portion. I hope that I may get a response here, but worried that as with most "newbie chat" type forums, they seem to get ignored.
Regardless, I have been trying to install the CM9 and CM10 to my MK802 PC thumbstick without any luck. The end result is either a bootloop with no video or a blank screen with no video output altogether.
I have been using instructions from here, but there seems to be a simple step that I am missing.
All requirements for Superuser, busybox, and smanager have been fulfilled, I am able to install CWM to do my factory resets and flashing, but I am not successful in the flashing. I'm not sure if I need to resize my system partitions, but that is something I've a feeling may affect the install. I've not seen any statements on the requirement, only that if the system partition is less than 350MB or so, to avoid flashing the gapps file, which I've followed.
I've attempted this on the FW710B, and the NEW03 image from the Rikomagic website as well.
If anyone has any ideas or can point me in the right direction to an already customized image I can flash with Livesuit, I'd appreciate it.
Thanks again,
T3ch42
optimal swap and / partition sizes??
Well, a little bit of an update. I took the plunge and repartitioned my internal SD memory. I chose 512MB for the system, and 64MB for the swap. That may have been not enough for the swap, but this was a new test.
This particular iteration was successful. I got the CyanogenMod boot screen and everything this time. The boot took a little while, hopefully just the initial boot.
It seems that this would be a pretty big step to take, but I really can't say that I saw mention of resizing the internal memory as being required.
If anyone has suggestions as to the optimal swap and system sizes, I would appreciate it.
Thanks
t3ch42 said:
Well, a little bit of an update. I took the plunge and repartitioned my internal SD memory. I chose 512MB for the system, and 64MB for the swap. That may have been not enough for the swap, but this was a new test.
This particular iteration was successful. I got the CyanogenMod boot screen and everything this time. The boot took a little while, hopefully just the initial boot.
It seems that this would be a pretty big step to take, but I really can't say that I saw mention of resizing the internal memory as being required.
If anyone has suggestions as to the optimal swap and system sizes, I would appreciate it.
Thanks
Click to expand...
Click to collapse
Good to know, I have the same problem as you. How did you repartition the internal SD memory? thanks
woonaval said:
Good to know, I have the same problem as you. How did you repartition the internal SD memory? thanks
Click to expand...
Click to collapse
I believe that I used the partition tool through the recovery app that you install, but I'm beginning to wonder. CT says that you cannot resize it. I have installed the Uberoid image a few times, and that may have resized it for me in all actuality. I did notice that when I had a SD card in the machine, that the SD card was resized instead of the internal memory which threw a kink in the works. After CM9 was installed, I wasn't able to use the internal memory.
Still doing some tests though.
May have more info in a little bit.
What steps did you take to get CWM on the stick. I tried several all not giving me a screen on reboot.
nyarnon said:
What steps did you take to get CWM on the stick. I tried several all not giving me a screen on reboot.
Click to expand...
Click to collapse
Install the Uberoid img through live suit and format.
After it boots, check your internal storage. It should say about 1.69GB
install the recovery, and boot to it.
Do a factory reset in recovery as usual, and then install your cm9 or cm10 images(the zips).
Install the gapps and compatability zips and reboot.
That should be it.
I think that's the steps I took that were successful.
If I tried to partition it myself, I found that the internal sd would not be recognized, even after trying the format memory zip that is used to fix th ad card.
Hope that helps.
I may have not looked closely enough.
You're having trouble with the cwm install?
For that, I just installed su, updated that to the newest version, click on the i and let it check the installed version.
Install busybox and the script installer. Use the cwm 4.0.4, I believe it is, and install the recovery image to the mk802.
The recovery.img needs to be in the main memory to run the script. Once you've run both of the scripts as root by clicking the little button in the script installer, then the mk802 should boot into recovery.
If this is what you meant, then hope this clears it up.
UPDATE: This can't be used with CM10 Alpha 4 (or later) as it is due to the new partitioning system.
____
I made this thing time ago and I thought to share.
What it does is to boot a stock ROM from the external SD card. It's nothing special, I simply changed few things here and there. I did it because I needed a stock ROM for a couple of minutes and this was the faster way to get it.
I'm using CM and I made this with that in mind, so, don't use while using a stock ROM. It won't mess your current setup, but it won't work.
You need to change kernel to boot the stock ROM (reboot recovery > flash zip. Simple and fast). That's because, as you probably now, kernels made for stock ROMs are not compatible with CM.
Prepare you SD card
You need first to repartition your external SD like this:
Code:
1° partition (mmcblk1p1): FAT - it will be the usual external SD
2° partition (mmcblk1p2): ext4 - /system (make it around 300MB big, 254MB will be more or less the space used)
3° partition (mmcblk1p3): ext4 - /data
I can't help you with this, I did it with adb and parted (the command is available in CWM). Look for instructions on the web, it's full of guides out there. Your external SD card is /dev/block/mmcblk1 (mmcblk0 is the internal one).
If you'll use the zip linked to flash the ROM, the two partitions (mmcblk1p2 and mmcblk1p3) will be automatically converted, unless they are already two ext4/ext3/ext2 partitions.
It shouldn't matter which kernel you are currently using and it should be safe flashing it, the only important thing is to have three partitions. If mmcblk1p2 or mmcblk1p3 are not detected, the installation will be aborted (it means that your SD card is not partitioned). Nothing else will be touched.
If you don't want to use the zip, mount mmbclk1p2 and copy the ROM there.
/dbdata will be the usual one (it's not used in CM. This will also makes Samsung apps a lot faster when using a slow SD card), same for /cache.
The flashable ROM is a stock XXLE4 + su/Superuser.apk.
How to use the additional ROM
To use the ROM on your SD, flash kernel-stock-SD.zip (see below) from recovery.
To go back to the real ROM you have to flash its kernel. Here below you can find CM10 Alpha 2 kernel, flashable from recovery. If you have doubts, reflash the entire ROM, it won't wipe your data.
I only mentioned CM10 because it's what I'm using, but this thing should work with CM9 too.
Things to know
I built the kernel using the latest Samsung sources with inbuilt ext4 support (and ext3/ext2 compatibility). Nothing else was changes, so I think there's no need to publish the sources, they are available here.
I attached the tools I use to unpack/repack boot images (they are a modified version of skin1980's tools):
Code:
./unpack.pl boot.img
./repack.sh [gz|lzma|bzip2|xz]
To see the changes I made, compare "out/android" with the stock XXLE4 ramdisk and the other two directories with CM10 boot.img ramdisk.
I changed recovery.fstab accordingly, but I can't tell you if flashing stuff from CWM while using the additional ROM will work as expected. You should read the updater-script to know it for sure.
I can only tell you that dhiru's builds will be flashed into the real /system partition and not your SD card.
Backups should work too, but I didn't try.
Of course, performances depends on your SD card. Mine is not that good I think, I took it from an old phone and I really don't know anything about it. The ROM is still usable, but apps that intensely use databases are slow (not Samsung apps, those will use /dbdata). Maybe disabling journaling will help (search for more info).
The Galaxy SL screen will last more than usual because I intentionally added a delay (3 seconds, SD cards are detected after a while) and of course because of the slower load.
Please, use this if you have some experience.
Note: dual booting two ROMs with a single kernel is possible, but only if they use the same kernel image. See this and this.
Downloads
XXLE4-CWM.zip: CWM flashable ROM
kernel-stock-SD.zip: kernel to boot the ROM from the external SD, flashable from recovery
kernel-CM10-Alpha2.zip: CM10 Alpha 2 kernel, flashable from recovery
Wow ! thats dualboot for i9003 ! sweet gud to see development back in action
Good work.
The class of an SD card can be misleading. It is only a measure of the sequential Write access and that doesn't tell the whole story. Class 10 cards are great for cameras and applications that write or read sequential data, such as saving a picture and transferring a file. They are not so good for random access which is what the Android OS does when operating. In fact the random access speed for class 10 cards is lower than class 4 or 6 cards. From what I have seen, the sweet spot for smartphones is class 6.
Awesome. Only if we could achieve dual boot without flashing kernel everytime. But anyways awesome guide. Thanks.
Reminded me of dual booting of maemo and android on my brother's n900.
Whats the benefits of dual boot? I heard about it but i dont have an idea
juztinlee said:
Whats the benefits of dual boot? I heard about it but i dont have an idea
Click to expand...
Click to collapse
Dual Booting means you can have two OS's (here firmware) on the phone at the same time. You can choose on which you want to go. This, besides being awesomely cool, is really helpful in many scenarios.
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
santoshsadani009 said:
^But this can be useful when you have to go for a long trip and want to record videos which only our stock rom is capable of doing good. Thanks to the developer.
Also, if anyone can, please tell me what is the possibility we can create a dualboot kernel like siyah kernel?
Click to expand...
Click to collapse
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
loSconosciuto said:
I didn't say dual boot
Creating a single kernel for ICS/JB and GB is not possible, or at least not an easy thing.
CyanogenMod is using newer graphic drivers not compatible with GB. I tried to use my CM10 kernel with GB, just to see what could happen. Well, it works, but with no hardware rendering as expected. It doesn't mean "it's laggy", it's painfully slow. And if we'll have the 3.0 kernel working, I guess this will be even more difficult.
The only option I think is kexecing an additional kernel, but kexec is hard to implement.
However I dual booted CM10 and CM9 (SD) with a single kernel (there are traces of this in my unpack/repack tools), I simply added an additional "cpio.gz" inside the boot.img. There's an additional boot reason that we never use, so we can use it to choose the corrent "cpio.gz" by parsing /proc/cmdline. The only problem is that you need to boot the ROM first and the reboot, because to get the other boot reason you have to run this:
Code:
reboot arm11_fota #or arm9_fota
(if you are using a stock ROM and try to reboot with the command above, you'll see weird stuff, but nothing should happen to your phone. I did it once.).
Maybe there's something else possible, but dual booting never interested me. As I said, I did it because I needed it.
You can do a lot of things, I even stored a ROM in a subdirectory in /data and use it from there (=> fast).
I don't know how exactly dual booting with this kernel works. I actually don't know how usually dual booting is implemented in Android.
I just looked at it. It allows you dualbooting only two ICS+ ROMs (so no GB), it automatically creates an hidden partition, automatically stores the ROM there, provides additional tools in CWM and other nice things.
I guess is something possible, but don't expect it from me. As I said, I'm not interested in dual booting and this thing requires time and knowledge.
Click to expand...
Click to collapse
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
vishal24387 said:
But its not exactly a dual booting. On galaxy s2 dual booting uses a single kernel but in our case.we are still using two different kernels which has to flash saperately.
Really we should create a kernel which can be used for cm9/10 & for stock GB rom. Then real fun will begin
Click to expand...
Click to collapse
Ya a Universal kernel will do the trick.If later then we can achieve dual boot then the people who were holding back from CM9 or CM10 can flash that for features and a stock rom for stability and camera.
shriomman said:
so that means we can dualboot cm9/10 with miui v4 . right ? since they both use the same kernel
Click to expand...
Click to collapse
As long as the kernel is the same, yes.
If you want, here you can find the unpacked boot.img I (probably) used to dual boot CM10 and CM9 (SD).
There's no zImage in there, use the one you prefer, CM10 and CM9 are using the same kernel.
EDIT:
I almost forgot. "out/ramdisk/2ndROM" is for the ROM stored in your SD card, so you have to adjust the mount points there (already done in the one linked). "out/ramdisk/android" should be the "stock" ramdisk.
recovery will work only for the primary ROM in this case, maybe with some scripting you can make it works for both the ROMs, but I won't do it (if it's something possible).
The tools I posted will automatically take care of the additional ramdisk.
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
nick0016 said:
Possible to fix the download links? I want to boot rom from SD card since my internal is corrupted...
Click to expand...
Click to collapse
I don't know what happened to the links, probably I deleted the files by mistake on dev-host. Sadly I no longer have them and I currently don't have the time to make them again.
Anyway, I suggest you to follow other guides in order to replace only the corrupted memory instead (we have two different memories). This one for example, but there are other guides probably.
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
nick0016 said:
Thanks for your answer, problem is that my "device" memory is corrupted (as in read only).
I did the SD / USB storage swap but still have the problem that I cannot run/remove/install. So I need a ROM that loads completely from the external SD card and also uses it for data/storage...
I can flash a rom/kernel without problems, but changing version makes it only worse because the data does not get erased (background/applications/settings.... stays the same everytime, even after a wipe from the recovery).
If it helps I would love to pay/donate money to you as a thanks for your help and effort because the phone itself is working fine (except the corrupted memory of course) and would like to use it again
Click to expand...
Click to collapse
The guide I linked is fine then.
It explains how to repartition your SD card and the script Dipu K attached to his post is to use the newly created partition inside your external SD for /data. It's not to swap internal and external SD.
As I said, we have two memories, /data is in one, /system, kernel and other things are in the other memory. The corrupted one must be the one which holds /data.
Try to do as explained in the guide, if the problem persists, I'll see what I can do to help.
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
nick0016 said:
I followed the guide and got the Device memory replaced (data partition). Problem is now it is stuck in at boot because the partition is empty.... and when I copy the files from the corrupted data partition it boots fine but get message that I must wipe my data or the system will be unstable (which is correct because I get then flooded with unexpected errors which make it unusable). But formatting data partition gives stuck @ samsung boot logo??
So I need to get the "factory" data files from somewhere... I am running stock KPE ROM with BAM kernel (for init.d support).
Is it possible to extract the data partition from the stock rom?!
Click to expand...
Click to collapse
The content of /data is generated, there's nothing like what you asking for.
Maybe the problem is that the script posted in the guide copies the content of the old /data partition to the new partition inside the SD card. Wiping data shouldn't work because the path to the SD card is not specified.
Try the script attached. I zipped it to be able to upload it here, but it's not flashable. Since you've been able to follow the guide I assume you know how to use adb.
Wipe the content of the data partition you created inside you SD card (/dev/block/mmcblk1p2). You could reformat it with make_ext4fs, use a computer and so on. What's important is that it's ext4 formatted.
While in recovery, run:
Code:
adb shell mount /system
adb shell mkdir -p /system/etc/init.d/
adb push [I]PATH_TO[/I]/remount_data /system/etc/init.d/
adb shell chmod 777 /system/etc/init.d/remount_data
I'm sorry, but I currently don't have much free time to help more than this. With no logs or access to the device it's really hard for me to know what's the problem.
Data2SD MOD: Moves /data partition to External SD, noticeable performance increase
All files attached are flashable .zips Installation instructions updated.
clemsyns cpu OC 1800 kernel is out! Good stuff!
Symlink added to /data2 (internal storage now found as /sdcardi)
You will need to disable journaling using the guide in post #3 if you are on CleanROM 2.1 to 2.3
as the rom does this as standard. If not you will get error!
I have had nothing to do with the development of this MOD, all credit goes to TweakerL
Also a huge thanks to scrosler for the fantastic CleanROM
Thanks to clemsyn for the amazing kernel!
Feel free to go to original thread and give your thanks: http://forum.xda-developers.com/showthread.php?t=1803252
and also to seek information, the thread is full of it.
What/Why/How?
This MOD was developed to aid the I/O-issues the Transformer Prime has and the Infinity inherited. Since it was a known fact that the internal
storage was slow/poor, TweakerL decided to try mounting the /data partition to the MicroSD card. Hence an obvious necessity
will be that you have a fast MicroSD card. Several have been tried and there is no real conclution as to what is the best in regards
to manufacturer or class (a class 6 card can have better random write speeds than a class 10 card), I use a Sandisk 64GB UHS-I
class 10 card and so does several others with good results.
The way this works is that you change the ramdisk so that it mounts /data to the second partition of your micro sd. Your internal
storage (the old /data partition) will be mounted as /data2.
Requirements
1. Unlocked and Rooted
2. You MUST repartition your Micro SD. The .zip you flash will mount /data to mmcblk1p2, which basically says "mount /data to the
second partition in the external SD." also, the ramdisk expects that partition to be ext4, so essentially:
Make sure you have an external SD with at least two partitions and that the second partition is formatted to ext4. I use fat32 on the first partition
because it's recognized by most devices.You will also need to make both partitions "primary" partitions. I personally use Gparted to repartition
my stuff, but feel free to use whatever you like. Even if you're on windows you can still use gparted by using virtualbox, or you can use a tool
called MiniTool Partition Wizard, I haven't tried it myself but it is reported to be good.
3. Research your Micro SD, find out if it has good random write speeds. There is no use in this mod if you card is slower than your internal
memory.
4. Although it's not a requirement it is a recommendation to have gone through the Nvflash procedure. It has saved alot of people from bricks
and is just great to have.
5. Verify that the .zip is compatible with your ROM, if it is not listed feel free to ask for a version for your preferred ROM.
Disclaimer
I take no responsibility for whatever happens to your device using this MOD, it is flashing a kernel so take precautions!
Installation
1. Boot to recovery, flash your preferred ROM
2. Reboot to initial setup (Don't run through)
3. Reboot to recovery, flash the matching Data2SD.zip
4. Disable journaling (Optional on all ROMs except CleanROM)
5. Reboot
When it reboots you will get a blue progress bar and it will be just as you flashed a new rom, you'll get the device setup screen.With my
MicroSD I get about twice the Random Write speed with this mod; Internal=0.20mb/s External=0.40mb/s . We will have a look at doubling
these figures further down (I currently have Random write speed average of 0.8mb/s).
Reverting
Flash a ROM
Feel free to ask any questions!
MD5 checksum for cm10-1025data2sd : 78b9e62e27204efeb0bdd3c926c4a30a
MD5 checksum for CleanROM2-3Data2SD: 60eef4e666ec97216ee0801189233719
MD5 checksum for clemsyn's 600 OC kernel ver8: e07b4a5a5f7ae2976a86460e5309199a
MD5 checksum for clemsyn's 650 OC kernel ver8: cf6d36da2d26db2e72c1c110a87cad7f
MD5 checksum for clemsyn's 650 OC kernel ver22: 1ec0e9c5c5ac7b012e3095f03f7dd234
Modded Recovery
Enough with the screenshots, I think people know what it's all about by now!
TWRP 2.3.1.0 Data2SD Edition
Modded by flumpster, thanks a million!
Attached is a version of the latest TWRP recovery, the only mod done is changing where
it mounts /data so it backs up the correct partitions!
Backup to External will backup to your first partition (fat32 maybe) and backup to internal will
backup to your ext4/2 partition.It is recommended to back up to external which is the fat partition.
If you backup to internal which is now the ext partition and something goes wrong with that partition
you wont have access to your backup.
Instructions:
You must remove the old twrp settings from your prime for this to work correctly. Delete any
TWRP folders that are in sdcard, data2/media and removable/sdcard. If you have backups there
already that you want to keep leave the backups folder in the TWRP directories and then just
delete the files that are in the root of the TWRP folder to get rid of the settings left behind.
If you are on a windows pc just extract the zip somewhere and run the bat file and then follow the
onscreen instructions. It will flash it for you. If not, navigatate to the fastboot folder, find the .blob
and flash the usual way with fastboot.
I have tested it myself but would love some feedback on this as I am currently the only one testing.
Disabling journaling!
This is a mod that flumpster tested and found to work fine. I have tested it to and it is fast as a shark. It is somewhat
controvertial though, someone thinks disabling journaling on the ext4 file system could cause crashes. Also if you are
plagued with random reboots it can cause data loss. I've been running it for a couple of days without issues and getting fantastic results.
Here is a description on how to do it if you want to try:
To Disable Journaling in EXT4
Go into TWRP and then open a command prompt on your computer where adb is.
Type adb shell and enter it then type the following commands one at a time.
umount /data
umount /sdcard
e2fsck -f /dev/block/mmcblk1p2
tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk1p2
e2fsck -f /dev/block/mmcblk1p2
Watch out for the fourth line, after tune2fs - that is a capital O not a zero. The one further along the line is a zero.
To check if it has worked type the follwing after them
tune2fs -l /dev/block/mmcblk1p2 | grep features
If you don't see has_journal in the output all is good.
And the size of the ext4 partition should be?
I was planning on taking a stab at porting this project to the TF700 this weekend. Thanks for your work! Going to test ASAP.
maxrdlf95 said:
And the size of the ext4 partition should be?
Click to expand...
Click to collapse
That is up to you really, the ext4 partition will be your new "internal storage" so if you if you need to store alot there like big games etc. you'll need more. If like me you have little use for internal storage you increase the size of first partition. I have 49gb fat 32 as my first partition and 11gb ext4 as my second.
I transfer movies etc. from a windows machine to the fat32 partition.
Good question though, I should have mentioned it in the OP.
Sent from my ASUS Transformer Pad TF700T using xda premium
The mysterious CheckROM that you've mentioned twice is just CleanROM, right?
Kisakuku said:
The mysterious CheckROM that you've mentioned twice is just CleanROM, right?
Click to expand...
Click to collapse
Yes, of course. Thank you for pointing that out, I've used CheckROM on another device so it got mixed up. OP updated.
fordwolden said:
Data2SD MOD: Moves /data partition to External SD
Click to expand...
Click to collapse
This looks very interesting!
fordwolden said:
Disabling journaling!
Click to expand...
Click to collapse
Actually the ROM does this during install. However on 2.0 it was causing issues with the latest TWRP so I temporarliy took it out.
It ended up being a twrp issue. IM going to put it back in for version 2.1 (with will be 10.4.4.18 based) and revert to the old version of twrp. The newer 2.3.x builds dont seem as reliable at this time.
But good write up!
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Edit: No longer applicable, sd-ext backup no longer supported. Modded TWRP recovery in post #2
fordwolden said:
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Click to expand...
Click to collapse
heh... i was just going to ask about that. thanks for the clarification.
fordwolden said:
Also worth to mention that this mod makes it a little bit harder to do nandroids. But in TWRP you have a option to backup sd-ext, that will actually be a backup of your data partition. So to restore data you just restore sd-ext. All other partitions will backup and restore normally.
Click to expand...
Click to collapse
People really use Nandroid? lol :angel:
scrosler said:
People really use Nandroid? lol :angel:
Click to expand...
Click to collapse
Some feel more comfortable doing it! I feel like it's "bringing a knife to a gunfight"! False safety.
Since the 12/10 update to .18 that I installed just yesterday my performance skyrocketed. I don't experience any lag anymore, no hickups, much faster loading etc. I suddenly don't feel like this tablet was a waste of money anymore
It's all stock and normal.
So if you don't have this update yet, try it out before trying anything like this.
Would there be any way of getting this working on a rooted stock FW?
I saved root before updating to JB so I'm going to stay unlocked for as long as I have warranty.
Moning2 said:
Since the 12/10 update to .18 that I installed just yesterday my performance skyrocketed. I don't experience any lag anymore, no hickups, much faster loading etc. I suddenly don't feel like this tablet was a waste of money anymore
It's all stock and normal.
So if you don't have this update yet, try it out before trying anything like this.
Click to expand...
Click to collapse
Gospel singers from the General section? Now that's a first for me! I'm glad you're happy with your tablets,
now try downloading CleanROM 2.1 while multi-tasking on your device, still happy? I bet you want to unlock
before the download is finished!
New version for CleanROM 2.1 coming up, sorry for the delay. Been getting some sleep and my Inet connection
is about as stable as Uranium!
New version has symlinked /data2 partition so your internal storage will now be found in /sdcardi. Just for ease
of use.
rikc said:
Would there be any way of getting this working on a rooted stock FW?
I saved root before updating to JB so I'm going to stay unlocked for as long as I have warranty.
Click to expand...
Click to collapse
You meant going to stay locked, right! No, sorry this is not possible for locked bootloaders.
fordwolden said:
You meant going to stay locked, right! No, sorry this is not possible for locked bootloaders.
Click to expand...
Click to collapse
Ok, thanks, that's clear!
I want this on stock rooted unlocked ROM
fordwolden said:
New version for CleanROM 2.1 coming up, sorry for the delay. Been getting some sleep and my Inet connection
is about as stable as Uranium!
.
Click to expand...
Click to collapse
Oh come on, Uranium has been around Earth for four and a half billion years and it's still here, can't be that unstable
Gesendet von meinem GT-N7000 mit Tapatalk 2
At the suggestion of several users, I am forking the previous thread. I am planning on supporting several ROMs and this is the best course to keep everything organized and provide support.
What is this?
Background:
The speed of the flash memory in the Transformer line of tablets is very poor. This is very apparent when installing or updating applications from the Play Store, copying files over USB, or using an app that caches lots of data like a web browser. The tablet will hiccup and stutter due to the I/O bottleneck. Running Androbench shows random write speeds averaging less than .2MB/sec.
The workaround:
Utilizing a fast, class 10 microSD card, we can move the /data partition to something significantly faster. The /data partition is where apps are installed to and where they store their configuration information and data. By redirecting /data to these fast microSD cards, we eliminate this bottleneck from our devices. With a properly fast card, users have reported a complete elimination of I/O related hiccups and system freezes. I have based my enhancements on the initial work by TweakerL on the Transformer Prime. Credit to fordwolden to porting his work to the Infinity.
The enhancements:
Previous implementations of this mod had the internal data partition mounted to /data2, with the media subfolder (your internal user storage) only available via root apps. There were symlinks set up at /sdcardi, etc, but these still required root permission to access. This is due to permissions on the /data partition and applies to both /data and /data2. Google gets around this by creating a "virtual" sdcard that points to /data/media. I have created a second "virtual" sdcard that points to /data2/media. This mod creates the scenario below:
/data = ext4 partition on microSD (fast)
/data2 = ext4 partition on internal storage (slow)
New changes:
/data/media -> Virtual SD Card Daemon -> /storage/sdcard0
/data2/media -> Virtual SD Card Daemon -> /storage/sdcardi
/sdcardi -> Symlink -> /storage/sdcardi
/mnt/sdcardi -> Symlink -> /storage/sdcardi
/storage/sdcardi is the virtual SD card for the internal storage. You should see all the files you had saved to this space before using data2sd. These files should be accessibly by any standard non-root Android app.
Note to kernel developers: This mod is more than just changes to the kernel. In order for the internal storage to be properly mounted at /storage/sdcardi, I have modded the Virtual SD Card Daemon that comes with Android. The stock binary is /system/bin/sdcard. I made a copy, modified it using a hex editor, called it /system/bin/sdcardi, and included it in my flashable zips. If you wish to make a data2sd version of your kernel, you must include this file in your zip. Additionally, be sure to add the "service sdcardi" line to your init.cardhu.rc that I have in mine.
Installation
Requirements
1) Class 10 microSD, at least 8gb
2) A computer with card reader
3) Partitioning software. Recommended: gparted LiveCD
Instructions
1) Decide how big you want to make the ext4 partition for /data. Remember, this is going to be the space for installing applications AND the /sdcard space that games will use the cache their extra data. Kindle books, Dropbox files, pics from the camera WILL ALL GO HERE. Personally, I decided to make the ext4 partition the whole 64gb of my card.
The ext4 partition has to be partition #2 on the microSD card. Why? This is to give people with large cards the option of creating a FAT32 or NTFS area as partition #1. This allows the card to be read by a Windows or Mac computer using a card reader. I use my tablet as my card reader with the USB cable, so I wasn't worried about this. I used gparted to create a small 8mb unformatted partition as partition #1, then a second 64gb partition to fill the rest of the card. I formatted this second partition in ext4.
2) Format your microSD card - Download Gparted Live CD (http://goo.gl/dJQAu) and use Imgburn (http://goo.gl/33MY9) to write to disc. Boot to Gparted using your CD after setting the CD as the primary boot device in your BIOS. Once in Gparted, create the 2 partitions described above, the first partition is Fat32, the second partition is ext4 or ext2. Set both partitions to type: Primary.
3) Insert microSD into tablet and flash any data2sd kernel for your ROM. (Note: Flashing any ROM will overwrite your data2sd kernel. You will have to re-flash the data2sd kernel if you change ROM or even upgrade your current one) After booting back into Android, you should be greeted with the Setup Wizard. Remember, this is a fresh /data partition, so it's a clean slate. It's a good idea to take a TitaniumBackup** ahead of time. I am experimenting with ways to make the transition more painless.
**Note about taking a TitaniumBackup before switching to data2sd. After the conversion, your internal storage will be mounted to /sdcardi. By default, TitaniumBackup looks for previous backups in /sdcard not in /sdcardi. You have two choices. Copy the TitaniumBackup folder from /sdcardi to /sdcard and restart the app, or change the backup location to /sdcardi/TitaniumBackup in the app preferences. Either of these options should work fine.
Optional: Verify data2sd is working. Pick any method you like:
a) Open a file explorer such as Root Explorer, ES, etc. You should see /sdcard and /sdcardi and be able to browse the files within. /sdcard is your ext4 partion on the microSD while /sdcardi is the internal storage. You should able to copy data between them.
b) Download "Androbench" app from the market and run "micro" sdcard check, if you see 0.4mb/sec or more in random write you're on data2sd.
c) Power off your device, remove your microSD card, then power back on your device. You should received an error message "Encryption unsuccessful". Insert microSD and reboot to fix.
Uninstallation
Don't like data2sd? Just flash a non-data2sd kernel using recovery and when you boot back into Android your /data will be on the internal storage. This could also be accomplished by flashing your ROM on top of itself without wiping.
Troubleshooting
1) Grab the mount-data2sd.zip from the second post.
2) Boot into TWRP and flash the mount-data2sd.zip. This will mount the microSD as /data in recovery. It will allow us to wipe it, format, etc using recovery.
3) Wipe "Internal Storage". This will erase the entire ext4 partition on your microSD.
4) Flash ROM
5) Flash data2sd kernel for ROM
*CAUTION*: If you don't flash mount-data2sd.zip before your wipe, you will be wiping your internal memory.
Download data2SD kernels
These are flashable zips. It will disable journaling on the microSD ext4 partition. You do not have to do this manually! Flash these after flashing the ROM.
CyanogenMOD 10.1 - beta2: http://d-h.st/rOe (Based on 4-2 nightly and may behave unexpectedly on other builds)
CleanROM 3.2.2: http://d-h.st/sCa - WORKS WITH CleanROM 3.3!
clemsynTFUniversalCyano650GPUFsyncver3: http://d-h.st/duw
ClemsynTFUniversalStock: http://d-h.st/IBm
clemsynTFUniversal650GPUver7 (Stock/CleanROM): http://d-h.st/S4k
Recovery
I made a flashable zip to help the recovery console understand our modification. By default, if you go into recovery and do a factory reset, it is formatting the /data partition on the internal storage. The issue same applies to nandroids. We may be using the second partition of our microSD card for /data, but the recovery does not know this. It will look to the internal /data partition during backup and restores.
This zip does not make any modifications to your tablet or copy any files. It simply updates your recovery mount points. The changes are temporary and are lost during the next reboot. You will need to flash it each time you boot into recovery.
After flashing this zip you will be able to:
1) Wipe data / Factory reset. The /data partition on the microSD will be wiped
2) Backup and restore nandroids. The /data partition on the microSD will be backed up or restored.
3) Choose "Flash zip from internal sdcard" and browse the files on the internal storage
4) Access and flash zips from the microSD storage. Choose "Flash zip from internal sdcard" and notice the !microSD folder at the top. This is a symlink that will kick you over to the microSD storage. This !microSD folder appears on your internal storage after you flash this zip for the first time. It remains unless you delete it. Even so, next time you enter recovery this !microSD symlink will not go anywhere until you flash this zip.
Please report your experience with this.
http://d-h.st/pPe
This one too.
So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.
can I use flash this on cleanrom 2.3 to diasable journalling on my ext4 partition
Diogenes5 said:
So this is basically flashable on CleanRom 2.3 right? Only thing wrong is that it doesn't show up in windows over USB? I can live with that as long as apps can read it in the Android OS itself.
Click to expand...
Click to collapse
Nope. This has changes to framework-res.apk which is ROM specific. I will post a CleanROM 2.3 version in a few minutes for you guys.
Thanks - Appreciate your hard work
---------- Post added at 08:46 PM ---------- Previous post was at 08:37 PM ----------
wow that was fast-thanks
---------- Post added at 08:58 PM ---------- Previous post was at 08:46 PM ----------
i was getting 6000 with clemsyn -I got low 5000's with this new mod
clownberg said:
i was getting 6000 with clemsyn -I got low 5000's with this new mod
Click to expand...
Click to collapse
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.
Mistar Muffin said:
This is not clemsyn's kernel, this is the stock CleanROM 2.3 kernel. I will mod clemsyn's latest kernel and post it for you.
Click to expand...
Click to collapse
Unable to have it work with cleanrom. Boot loop
titou00075 said:
Unable to have it work with cleanrom. Boot loop
Click to expand...
Click to collapse
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.
May be a stupid question but do you still need TWO primary partitions on the SD card (i.e., first is FAT32 while second is Ext4 and used by the mod)? If this isn't necessary or not possible, should the recovery (i.e., installation) files be placed in internal storage?
Forgot to mention I'm using Windows 7 MTP and CleanROM 2.3
Mistar Muffin said:
Use recovery to wipe the /cache partition. Due to the changes in framework-res.apk this may be necessary if you aren't coming from a completely clean install of a ROM.
I just booted to recovery and wiped my microSD /data partition. I also wiped /cache and /system. I installed CleanROM 2.3 and in the same recovery session I flashed the clemsynTF700ver22GPU650VC-data2sd kernel and it booted right up.
Click to expand...
Click to collapse
Ok thanks. Will do:thumbup:
Your Awesome, Thank you!
cheers
Thanks Gonna try this.
done the work install all three files in the OP, however it is taking a long time to boot....Can someone give me an idea as to how long this normally take onn first bootup after a fresh install?
please advise
tyfoxx
Couldyou make one for blackbean? i tried thecm 1029,but it doesnt boot. Would greatly appreciate it.
Sweet
I just ran every shortcut I could think of:
I used Mini partition tool to reduce reduce my 32 gig fat down to 16 gigs & then created a 16 gig ext4 partition.
Wiped everything in twrp and re flashed Clean 2.3 then the new zip.
All I can say is WOW.
Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app
Diogenes5 said:
Restored everything. Works great no more stalls and stable so far. Hope it stays this way. Now to focus on battery life.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Glad it's working! I've prepared a little treat for everyone to make our recovery lives a little easier. Need to test a few more things before I post!
I'm running CleanROM 2.3 and ClemsynTF700ver22GPU650VC (awesome combo, btw). If I want to use this MOD, should I need to flash first CleanROM-2.3-data2sd.zip and later ClemsynTF700ver22GPU650VC-data2sd.zip, right? Of course, also, formating my microSD using ext4.
Awesome work here Mistar!!!! Thank you so very much for this!!! Gonna replace my SanDisk 32gb Class 4 card with a SanDisk 64gb Class 10 before I run this on CleanRom. I'm super excited about this mod!!!!!! Thanks a million!!!!!!
Sent from my EVO 4G LTE using xda premium
This was the 6th post in the thread. I swapped it with the original first, because this one contains the instructions on how to get dualbooting to work.
@brewmeister:
Thanks, I've got it working, since Graiden05 added the support for it. ^^
@f69m:
I'm stalking your thread, ready to pounce once sd cards and linux are supported. If you see a shadow in the corner of your eye, while writing a post in your thread, then that's most likely me.
@Trigger911 and everyone else interested:
It's quite easy now. But takes a while, if you're doing it for the first time. Note that I'm talking about the MicroSD card slot in the tablet. This won't work with the slot in the Dock. Also you need to have your tablet unlocked, a 4.2 Bootloader and a custom recovery, like TWRP 2.5.0.0-42. See the Cromi-X thread in the developer forum:
forum.xda-developers.com/showthread.php?t=2425390
The rootfs is a bit dated. It's xubuntu 13.04. There are instructions on how to create your own roots in the 2nd post of the xubuntu thread in the dev forum. We'll just use the dated one.
Also webdoctors wrote a nice post about just installing xubuntu. There are links to the rootfs, installer script v2.2.9 and the modules needed:
forum.xda-developers.com/showpost.php?p=48947306&postcount=342
Download the installer script and Cromi-X to the internal storage of your tablet.
To get both Cromi-X and xubuntu booting from the sdcard you need to partition it:
Create four patitions on your card. The order is important and don't forget to make a backup! All data on the card will be lost during the process:
1st: vfat (any size you want, there was a technical reason, that the first partition needs to be vfat, but I can't remember)
2nd: ext4 (will be the data partition for your apps and stuff, as big as possible)
3rd: ext4 (system, for cromi-x, 1GiB, more would be a waste of space)
4th: ext4 (rootfs, for xubuntu, at least 4GiB, made mine 10GiB, on a 64GiB card)
Detailed Instructions on how to partition a sd card can be found at the end of the 2nd post of sdbags' Cromi-X thread.
Installing Cromi-X:
Get Cromi-X 5.4 and flash it with the ROM2SD Option selected. Instructions on how to install Cromi-X are in the 1st post.
Cromi-X will use the 2nd and 3rd Partition.
Once the installation is done, reboot and check if it is working. During the boot you will see Penguins and some text below. If at the end of it there's something like "setting up for Rom2SD", then it's working and booting from the card.
Installing xubuntu:
For the next steps I use Ubuntud. It might work on a rooted phone/tablet too, if you use a terminal app, like Terminal IDE or Terminal Emulator. But you might need to use su instead of sudo and use another folder than /media.
Follow these instructions and enter the commands in a terminal. If you want to learn more about what a command is doing type "man" followed by the command, e.g. "man sudo" or "man mkdir":
1. Create mountpoints for the rootfs-partition and the downloaded rootfs-image:
sudo mkdir /media/xubuntu
sudo mkdir /media/rootimage
2. Determining the path of your sd card under Linux. Don't play with this! fdisk you can wreak havoc to your harddisk. The -l option tells fdisk to show you a list of all partitions of storage mediums connected to your pc:
sudo fdisk -l
3. Mount the rootfs partition of the sdcard. Assuming the path to the sd card is /dev/sdd, then the 4th partition is adressed as /dev/sdd4. Change it accordingly:
sudo mount -t ext4 /dev/sdd4 /media/xubuntu
4. Download the rootfs. Use the link in webdoctors post.
5. Extract the image from the file.
6. Mount the image, so you can copy it's content to the rootfs partition on the card. You need to change the path to match your situation. Here I simply downloaded it to my Downloads folder and extracted it there:
sudo mount -o loop /home/<username>/Downloads/xubuntu_13.04.img /media/rootimage
8. Now we can copy the files in the image to our root partition. We use the options -pr, which will (p)reserve access rights, owner, group, etc. and copy (r)ecursivly the contents of all directories in the image:
sudo cp -pr /media/rootimage/* /media/xubuntu/
9. Wait till it's done copying, then unmount both the image and root partition:
sudo umount /media/xubuntu
sudo umount /media/rootimage
10. Put the SD card in the tablet and boot to recovery: Press Volume Down and keep holding it. Press Power for a second and release it, while keeping Volume Down pressed. Once you see three icons, with RCK blinking, release Volume Down and Press Volume Up.
11. Now it's time to flash the installer script. Doing this will enable us to boot xubuntu, but we will loose wifi in Android. We will fix this afterwards. In TWRP chose install, locate the V2.2.9.zip and flash it. The tablet will reboot, show a blue bar and reboot again.
12. You will be greeted by a new bootmenu. Waiting for 10 seconds or hitting 1 will boot xubuntu, pressing Volume Down or 2 will boot Cromi-X. For now we want to boot to xubuntu.
13. On the login screen just hit login.
Fixing WiFi in Android
Now we need the mod_update.zip from Graiden05.
1. Get it from: forum.xda-developers.com/showpost.php?p=47990253&postcount=311
2. Unzip it and open the mod_update.sh file in an editor.
3. The script assumes, that we've installed Android to the internal storage, which we did not. So we need to change a line and point it at the right direction.
In the 3rd line we need to change "/dev/mmcblk0p1" to "/dev/mmcblk1p3". Now the script will mount the system partition of the sd card and not the one from internal storage.
Save and quit.
4. Open a terminal and navigate to the folder containing the script.
5. Run the script by typing:
sudo sh ./mod_update.sh
6. Done! Sit back, relax and enjoy dualbooting your TF300T!
Add swap to xubuntu:
Stop relaxing and get back to work! We ain't done yet. *cracks a whip*
We're gonna add a swap file for xubuntu to use because: "If you don't setup a swap space, programs will randomly get killed when you run out of RAM, which is kinda annoying if you want a stable and fast system." (shamelessly stolen from webdoctors' post)
And because we already got four primary partitions on the card, we can't add another one. We could try using extended/logical partitions, but I'm not sure if those are supported on a card and haven't tried it. The only disadvantage will be, that we can't use the swapfile while running Cromi-X... Or can we? Hmmm, mount the xubuntu partition and simply use the swapfile? Got to think about/try it.
Anyways, a good description on how to setup swap is here: http://www.thegeekstuff.com/2010/08/how-to-add-swap-space/ (again shamelessly stolen from webdoctors' post).
Use the second method and don't forget to add "sudo" to the beginning of every line. Also change the value for count in the dd command according to your needs, e.g. count=512 instead of count=1024 to use 512MiB of swap instead of 1GiB.
Ok, it is possible to use the swapfile on the xubuntu partition while running Cromi-X. I don't know how to make these changes permanently yet, so you'll have to mount the partition (step 3) and activate the swapfile (step 4) on every boot to Cromi-X. Also note that using the card for swap will increase it's wear.
With that said, let's get it on! *dingding*
1. Start a terminal app and get root right. In Terminal Emulator just type "su" and hit enter.
2. Create a directory to mount to:
mkdir /sdcard/xubuntu
3. Mount the xubuntu partition:
mount -t ext4 /dev/block/mmcblk1p4 /sdcard/xubuntu
4. Activate swap. If you didn't follow the guide and created it in another directory or under another name, then you have to change the path accordingly:
swapon /sdcard/xubuntu/root/myswapfile
5. Check that it's working. The first number after swap should be anything but 0:
free -k
6. Done! Stop working and get back to relaxing! *cracks a whip*
Things to note:
Suspend is not working. Don't use or you'll have to hard power down the tablet (pressing power for 7? 10? seconds). This is bad and you don't want do that. Always shut the tablet down, when you're done. Booting to xubuntu only takes about a minute.
Doing a distribution upgrade in xubuntu is not working. I tried and had to use a backup for the rootfs.
I'm not sure if this is related to making the tablet dualboot. But sometimes, when I used Android and put the tablet to sleep for some hours, it won't wake up and the battery in the dock took quite a hit. The cause for this could be anything; The modules used, kernel, a badly programmed app, bug in Cromi-X, corrupted partition, cosmic rays blasting my tablet or the tablet's just like me and doesn't like being woken early.
I can try to build GRIMLOCK based kernel which should make it possible. But there is one problem left to solve - choosing partition to boot certain OS.
Really hope to see this happen can only find solutions for 4.1
try v2.2.9
Try the updated kernel and rootfs from xubuntu thread, if i remember right, data2sd was implemented in v2.2.6 kernel, latest kernel is 2.2.9.
Look at the 2nd or 3rd thread(I think?) on pg 35 of xubuntu thread. Also consider setting up a linux swap partition at the end of your sd card.
Hope you get it working, good luck.
The official MultiROM has quite flexible support for dual-booting different Linux systems, but that is disabled in my early TF300T port due to lack of time. I am currently concentrating on Ubuntu Touch.
If someone is willing to try, I am happy to provide experimental MultiROM builds and some support. All I am asking in return are some howto docs to include in the MultiROM thread.
Sent from my TF300T using Tapatalk
This was originally the 1st post.
Hi,
I am trying to get dualboot to work with Xubuntu and Chromix 5.2a from an external SD-Card.
Since I can't post in the Dev-forum yet, I have to do it here instead of the corresponding thread.
Hardware/Software infos:
My Tablet is an Asus TF300T with 4.2 Bootloader (Asus Firmware WW 10.6.1.27.5 -> Chromix 5.2a Deodexed), TWRP 2.5.0.0, Nvflash enabled, ADB and fastboot access.
There is Chromix 5.2a with _that-v6 Kernel installed to both internal memory and SD-Card (Rom2SD). The Xubuntu rootfs is on the card too.
The card is a Samsung MB-MGCGBEU Class 10 microSDXC Pro 64GB and got these partitions:
/dev/mmcblk1p1 8GB vfat
/dev/mmcblk1p2 40GB ext4, data partition
/dev/mmcblk1p3 1GB ext4, system partition
/dev/mmcblk1p4 10GB ext4, rootfs for xubuntu
Journaling is disabled for the ext4 partitions, to keep the wear down for the card.
Rom2SD requires the first three partitions.
Goal and Problem:
What I am trying to do is being able to boot both Android and Xubuntu from the external SD-Card.
Also I want to keep Chromix on the internal memory as a fallback, in case the card gets damaged/lost/stolen by aliens and misused in weird experiments.
Right now I can only access either Android or Xubuntu from the card, but not the other:
When I flash Chromix 5.2a via TWRP, I can boot to Android from the card but have no access to Xubuntu.
Flashing Graiden05's testV2.2.4.zip from http://forum.xda-developers.com/showpost.php?p=47649660&postcount=265&nocache=1&z=7287232739506702 I can boot to Android from internal memory and Xubuntu form the card.
I know that the installers don't know anything about each other and hope it's only a matter of modifying them or some boot scripts.
Maybe change the installers so they use their own partition and don't overwrite each other. And then extend _that's dualboot method (http://forum.xda-developers.com/showthread.php?t=2501129) to multiple OS on an external sdcard.
Something like: (Note: I've only got some vague ideas about what's going on during installation or booting)
1. Add a 5th partition to the sdcard.
2. Install Chromix with Rom2SD.
3. Change the testV2.2.4.zip to do it's xubuntu magic on the 5th partition and not overwrite the Rom2SD stuff
4. Modify _that's dualboot method to include xubuntu and wait for VolUp or VolDown to select what to boot.
5. ???
6. Profit!
7. ???
8. World domination!
I hope someone can help me with this problem. It would really rock to be able to boot this baby with multiple OS from a fast SD-Card!
nice
glad your up and running and thanks for the details. this would be a good post to reference for those wanting to try this (along with web doctors post in the xubuntu thread) - I would however set up a fifth partition for linux swap and set it up as detailed in the link in webdrs thread. How is cromi running with rom2sd? right now i've got mine set up with cromi on data2sd and xubuntu on internal. all I have is a 16 gb micro and i'm thinking of switching my setup once i get a bigger card. does cromi run any better from the card? anyways thanks again and a huge thanks to all those that have made this possible (graiden, join the realms, fm69, shrdlu and anyone else that i may have missed)
also got to give a huge thanks to sbdags for his awesome cromix rom
brewmeister said:
glad your up and running and thanks for the details. this would be a good post to reference for those wanting to try this (along with web doctors post in the xubuntu thread) - I would however set up a fifth partition for linux swap and set it up as detailed in the link in webdrs thread. How is cromi running with rom2sd? right now i've got mine set up with cromi on data2sd and xubuntu on internal. all I have is a 16 gb micro and i'm thinking of switching my setup once i get a bigger card. does cromi run any better from the card? anyways thanks again and a huge thanks to all those that have made this possible (graiden, join the realms, fm69, shrdlu and anyone else that i may have missed)
also got to give a huge thanks to sbdags for his awesome cromix rom
Click to expand...
Click to collapse
Ah yes right, I forgot about the swap part. Gonna add it.
Performancewise I'm happy with running Cromi-X from card. To be honest, I haven't booted from internal memory for some months now. Then again, it all depends on the card. If you've got a fast one, I'd say give it a try. If it's not fast enough for you, you can just power down, remove the card and the bootloader from the v2.2.9 script will simply boot from your internal memory.
Can somebody help me a little? Because after mod update (on rootfs 12.10 tried also files from installer.tar.gz) I can't start xubuntu
Currently I have latest kernel 2.2.9 from dev thread and CROMi-X. Tried also rootfs for 13.04 but i won't start anyway. Using 12.10 I can at least login to the system.
I partially figured it out. My problem was caused because of wireless kernel modules. I can again run xubuntu but without wi-fi. Unfortunately modules from dev thread doesn't work for me
Does 3G work on tf300TG while in Xubuntu?