I made this to tide myself over until $auron can finish UrukDroid 0.6. This is a combination of the stock Archos 2.1.04 firmware, Ardatdat's Overclocked Kernel, and a manual EXT4 Conversion. It is permanently rooted and includes SuperUser. My main reason for making it was to enable read/write access to the filesystem, which rooting DOES NOT do on the stock Archos firmware, as the squashfs will still be mounted read only by /etc/mountpoints. Also, EXT4 is much faster than the compressed squashfs Archos uses. Quadrant gives ~2200 with the data partition converted to EXT4 as well, ~1800 without conversion. I have already updated Busybox to a fully compiled version, 1.16, another thing Archos decided to "secure" despite the supposed Open Source status. I have NOT edited the .hosts file to block ads, as I believe the app developers deserve to make some money, you'd be amazed how little they make, but you can do it yourself without Archangel scripts now, as the filesystem will be read/write again.
I designed it on an A101it, but it should work on any Gen8 with internal flash storage. A70H users, I can't remember your block allocations, it may work fine, but I'll need someone to post the storage layout of /dev/block/ to be sure.
For the power users, here's a quick install outline: First, make a second partition on your storage/sdcard in EXT4, extract the rootfs.tar.gz to it, and flash the appropriate initramfs and zimage. Pretty easy.
For the rest of you(probably most of you):
There is only one short step in Linux, which is setting up an EXT4 partition on your Internal Storage or your SD Card. You must make it as a second partition, not 1st, 3rd, or anything else. This means you can still use it as a storage device as well as running Android. I find it incredibly simple, and can be done in less than 3 minutes, but I will be relying on you guys to tell me what you don't understand, and I will update the instructions as needed.
This can be run off the SD Card or the Internal Storage, both versions are included in the download. It will use the existing data partition if you already have the SDE installed and 2.1.04 firmware. Otherwise, you will need to flash the SDE, which erases your data, so please use Titanium Backup first if necessary.
Step 1:
Download my files:http://www.multiupload.com/HR6SRRR8P8
And install the SDE from Archos: http://www.archos.com/support/download/firm_dev/firmware_archos_android_gen8.aos.
Step 2: Boot into stock Android and connect to a Linux PC. If you do not have Linux, download Tuxboot and use it to create a GParted Live Disk:http://gparted.sourceforge.net/liveusb.php
Step 3:
Mount your Internal Storage/SD Card from the Archos. It should now show up in GParted on the Linux PC, make sure you have the correct device selected, it should be called Archos A101T(make note of the location, e.g. /dev/sdb). Resize your existing partition with GParted, leaving about 300MB at the end of the Internal Storage/SD Card. Make a new partition in the empty space, and select ext4 as filesystem. Apply Changes. Now open a terminal, elevate yourself to root by typing
Code:
sudo -s
and format the new partition by typing
Code:
mkfs.ext4 -O ^huge_file /dev/sdb2
Substitute "sdb" for whatever your device location was in GParted. The "2" on the end of "sdb" denotes that it is the second partition. Do NOT format "sdb1" or any other "sd"s. Mount the new partition by opening Nautilus or any other file manager and double clicking on the "300MB Filesystem" entry on the left. Untar the rootfs.tar.gz from my files with the Archive Manager, it works just like winzip or winrar, into the root of the new partition. Eject the device from Linux, then reboot into the Developer Menu by holding vol- or vol+ while booting.
Step 4:
Flash the initramfs.cpio.gz and the zimage from my files. Use the files from the "internal" folder if you are running from Internal Storage, or the files from "sdcard" if you are running from the SD Card.
Step 5:
Use the Dev Menu to boot into Developer Edition. Let me know about any bugs. After I removed the Android Boot option from the Dev Menu, I had a few strange loops of the Archos animation while booting, but it did boot, and function, just fine.
Thanks go to Ardatdat for the kernel, Archos for the crappy "securing" of the squashfs, and $auron for motivating me to get back into development.
Hi msticninja ,
I did it It seems so smooth. I used my internal storage. But linux steps were not so simple for me I used a Fedora 14 VMWare image.
I'm at work so I can't play with it but it seems stable and it can awake.
Quadrant (I know it's not accurate) score is about 1900 (internal and ext4).
I think that you should add some descriptions about linux steps (for noobs like me).
Thanks...
PS: Did I move my DATA partition to EXT4? (I did all steps you wrote). If no how can I do?
Nice work! I'll be trying to add more instructions for the Linux section for the next couple of days.
Your data partition is still EXT3, I haven't found a very easy way to convert it yet. Basically, I made another partition on the Internal Storage, copied the data partition there, and flashed a new initramfs to boot off the new data partition. Then you fdisk and format the original partition from a terminal in the Archos or ADB, copy everything back, and flash ANOTHER initramfs to use the original, now EXT4, partition.
So far, I don't think the performance gain for the data partition is worth all that work.
It works and installs well but your guide how to install it is not complete. For example, I had to manually maintain write permissions of the partition and sudo is needed by the mkfs.ext4 -O ^huge_file /dev/sdb2
Hondaracer said:
It works and installs well but your guide how to install it is not complete. For example, I had to manually maintain write permissions of the partition and sudo is needed by the mkfs.ext4 -O ^huge_file /dev/sdb2
Click to expand...
Click to collapse
Sorry, i automatically elevate permissions when I do stuff like this. I've added sudo to the instructions. As far as manually maintaining the partition permission, what did you have to do there?
msticninja said:
Sorry, i automatically elevate permissions when I do stuff like this. I've added sudo to the instructions. As far as manually maintaining the partition permission, what did you have to do there?
Click to expand...
Click to collapse
I had to type this: sudo chown -R username:usergroup /media By the way thanks for the work you've done
Hondaracer said:
I had to type this: sudo chown -R username:usergroup /media By the way thanks for the work you've done
Click to expand...
Click to collapse
If that was before using mkfs.ext4, then that is strange. After mkfs though, the owner should be root. I should point out that the rootfs.tar.gz should be extracted as root, which means you have to open the archive manager from a terminal. I need to find an easy process that will work on all distros, as I don't know how many have nautilus installed.
Thanks for your replies, this is much needed feedback.
msticninja said:
If that was before using mkfs.ext4, then that is strange. After mkfs though, the owner should be root. I should point out that the rootfs.tar.gz should be extracted as root, which means you have to open the archive manager from a terminal. I need to find an easy process that will work on all distros, as I don't know how many have nautilus installed.
Thanks for your replies, this is much needed feedback.
Click to expand...
Click to collapse
I had to do this to be able to write the rootfs to dev/sdb2. But I must say I did a reboot before I copied the files cause Ubuntu started to act very weird. And for the beginner I'd might be good to mention that you have to unmount in GParted.
I've tried it and feels slower than Uruk 0.6RC2 on Scandisk SDHC 8GB Class 4 (without OC).
Thank you for your great work!
chisco said:
I've tried it and feels slower than Uruk 0.6RC2 on Scandisk SDHC 8GB Class 4 (without OC).
Thank you for your great work!
Click to expand...
Click to collapse
I'm not surprised. This is the stock firmware with none of Uruk's enhancements, other than ext4 and a new kernel. As i said, this is to tide people over until the official Uruk thread gets 0.6. You're already on the beta 0.6, so there's not much need for my firmware.
I just wrote an automatic install script. All you have to do is copy a file to your internal storage or sd card, and flash the initramfs/zimage in the Dev Menu. This one will replace the current Archos partition so you won't lose any space on your storage device. Should be uploaded tonight.
I tried this method with last OC Kernel (11 FEB): very good... With this method, we use same data as for stock ROM, so no need to reinstall all apps...
Thanks.
I AM NOT RESPONSIBLE IF YOU DAMAGED YOUR SDCARD OR NOOK TABLET
WHAT IS THIS?
It's a flashable file (a file that you can install from recovery) that will create a bootable SDCard for your Nook Tablet.
What it does is creates 4 partitions on your SDCard.
100MB for partition 1 (BOOT)
400MB for partition 2 (SYSTEM1)
Size for partition 3 (DATA1) and partition 4 (SDCARD) vary.
It'll also copy over boot files to your SDCard, making the SDCard bootable on your Nook Tablet.
INSTRUCTIONS:
This will only work with the provided CWM 6.0.2.9 because it contains fdisk with advanced options.
Format your SDCard with SDFormatter if you are on Windows and OSX. Linux? GParted.
Copy CWM 6.0.2.9 recovery (renamed the internal recovery img to recovery.img) to your SDCard.
Copy flashable_create_bootable_sdcard.zip to your internal storage.
if [ Stock_Rom ]; then
# If you are still on Stock Rom, you need to be rooted and have terminal installed.
# Open up terminal.
# Backup stock recovery
su
dd if=/dev/block/mmcblk0p3 of=/sdcard/stock_recovery.img
# Store the stock_recovery.img on your computer for future need.
# Install CWM 6.0.2.9 recovery
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p3
# Boot to recovery. Power up device by holding Power + Home keys.
else
# If you already have previous CWM version of recovery installed, just flash the new one.
reboot recovery
fi
Insert formatted SDCard.
Make sure the USB cable is not plugged into your computer.
1) Install zip from sdcard
- choose zip from internal sdcard
- flashable_create_bootable_sdcard.zip
Ignored the "can't unmount /dev/block/mmcblk1p1".
Be patient with the loading bar. It's not frozen, just wait.
The larger the data1 size, the longer the process take.
Power off device and turn it on again.
If successful, it will boot into Cyanoboot.
Then you can install *SDC Rom.
The default data1 (Partition 3) size is 600MB in flashable_create_bootable_sdcard.zip.
My recommendation.
600MB is for 2GB SDCard
1000MB is for 4GB SDCard
2000MB is for 8GB SDCard
3000MB is for 16GB-64GB SDCard
To make data1 size larger, just rename the file 'createsd_*.sh' to 'createsd.sh' inside flashable_create_bootable_sdcard.zip.
createsd_600MB.sh
createsd_1000MB.sh
createsd_2000MB.sh
createsd_3000MB.sh
*added 4000MB and 5000MB scripts. Rename createsd_X000MB.sh.txt to createsd.sh.
Do test and tell. I've only tested on 2GB, 4GB, and 32GB sdcard.
I'm curious how I go about installing a rom onto the sd card after i have this?
Koneesha said:
I'm curious how I go about installing a rom onto the sd card after i have this?
Click to expand...
Click to collapse
There should be a guide on how to flash ROMs to SD somewhere in the forum...it was intended for making a triple boot Nook...although the scripts may not work for CM10/10.1 as they were for CM7/9
If you find it (back 1-2 pages) you could use it, if I find it I'll link you...
http://forum.xda-developers.com/nook-hd?nocache=1&z=7773671285249293
If you indeed have a Nook HDplus, then you are posting in the wrong forum. Try posting in a HD+ forum and perhaps someone might be willing to help, in spite of your rather abrasive attitude.
SD-based CM11 ROMs for HD+:
http://forum.xda-developers.com/showthread.php?t=2583952
http://forum.xda-developers.com/showthread.php?t=2600572
http://iamafanof.wordpress.com/2013/12/20/cm11-0-kitkat-android-4-4-2-for-nook-hd-xx-20dec2013/
I have a init.d script that involves sdcard activity, but the card is obviously not mounted whilst the script is being executed. So is it possible to write a init.d script that would mount an sdcard at boot time?
Im looking for this solution too.. I believe mount sdcard on init will be a great idea.. because i have apps on sdcard so, it will need to be scan only after it boot to the OS.
Same here... could u get the solution ?
I want my script to copy some file from /sdcard to /data at boot time.
Hello guyz, i'm trying to install int2ext script on my phone, but without success. I've got a Samsung S4 Clone with J.B 3.1, stock rom and stock recovery. I managed to create an ext2 partition through windows and enable init.d scripts with an googlestore app. Using a script named 05mountsd, the system manages to mount the ext2 partition and i'm able to browse it with root explorer. But when i copy any of the int2ext/int2ext+ scripts in the init.d folder (remember, i dont have cwm recovery to install from zip) the phone boots normaly and 5secs after i see my background, the phone goes back in loading android screen.
I have to delete the 40int2ext script from init.d through adb shell, for the phone to boot up normally again. Then inside the ext2 partition i am able to see that the script has managed to create some files and folders! But i cant install apps in there. Also link2sd app gives a message that the partition cannot be mounted and that i should try fat.
Any ideas how to get int2ext or any other storage script to work?
Bump!!!
I managed to install a cwm recovery that supports my phone's UBIFS format.
Still can't get any script that links apps to sd to work.
When i try to install CronMod_int2ext.zip through recovery i get an error. Also i cant mount or format the sd-ext partition in the recovery, though i tried partitioning the sd inside the recovery as well as from windows. Both attempts fail to mount in recovery.
With Mounts2sd app, i get bootloop problem.
Anyone!?
bump
931 6923243
bump!
Hi!
Partitioned my 32GB sdcard, and put CM10.2 on it, but when I check it I have only about 400mb of space or something like that. I had the same amount of space on a 4GB sdcard I used before. Why am I not able to use up the rest of the GB's?! Can someone tell me how to fix it, I don't know if I'm partitioning wrong or doing something wrong, but I want to be able to have lots of extra space for music, apps, etc. Please help! Thanks!!!
I believe you used a low level utility like dd or similar to flash an image onto a partition.
You need to run fsck on that partition, then run resize2fs to expand the ext2/3/4 partition.
Let's say your partition is /dev/block/mmcblk1p1
You would do (in a terminal):
adb reboot recovery
adb shell
# umount /dev/block/mmcblk1p1
# e2fsck /dev/block/mmcblk1p1
# resize2fs /dev/block/mmcblk1p1
After that, your partition will get expanded to whatever size you made it.
It takes a while so be patient. The larger the partition, the longer it will take.
Zenile said:
Hi!
Partitioned my 32GB sdcard, and put CM10.2 on it, but when I check it I have only about 400mb of space or something like that. I had the same amount of space on a 4GB sdcard I used before. Why am I not able to use up the rest of the GB's?! Can someone tell me how to fix it, I don't know if I'm partitioning wrong or doing something wrong, but I want to be able to have lots of extra space for music, apps, etc. Please help! Thanks!!!
Click to expand...
Click to collapse
if you got a prebaked image of a bootable cm card from somewhere, then it usually has 4 partitions on it that were set to the sizes the author of the card specified.
/boot
/system
/data
/sdcard
You would need to put the card in a PC, and use a disk partitioning utility to resize the partitions
some of the images include additional flash files that you install to expand the card's partitions for you. (succulent's), but
you have to do it as you install for the first time.
I prefer to build the card empty first, and load the boot files and zips manually.
linux tools like gparted, Parted Magic , booting from a live USB or CD work pretty well.
Windows based ones like Easus Partition master, or Paragon, not so good.
Mini Tool partition wizard (windows/free) sometimes works
this looks to be a decent write up
http://www.mobileread.com/forums/showthread.php?t=202660
mikeataol said:
...
I prefer to build the card empty first, and load the boot files and zips manually.
linux tools like gparted, Parted Magic , booting from a live USB or CD work pretty well.
Windows based ones like Easus Partition master, or Paragon, not so good.
Mini Tool partition wizard (windows/free) sometimes works
this looks to be a decent write up
http://www.mobileread.com/forums/showthread.php?t=202660
Click to expand...
Click to collapse
The write-up is also posted on XDA at http://forum.xda-developers.com/showthread.php?t=2098419. It was written back in the days of CM10.1, so to use it for CM10.2 or CM11:
Obtain the boot files: MLO, u-boot.bin, and flashing_boot.img -- as well as the files boot.img and recovery.img, from the /boot partition of the pre-made SD CM image. Make sure that MLO is the first file to copy to the freshly made /boot partition.
Substitute in the appropriate ROM and Gapps zip files corresponding to the particular CM build of interest.