By default, Windows will only mount the first listed partition on any Removable Disk. This is unfortunate for CM7 SD version users since the 4th partition of the SD card is the one used to store user data, which frequently need to be viewed and edited.
Purpose:
This tutorial will show you how to modify a Local Disk driver in order for Windows to recognize all the partitions of your SD card.
So, just a couple of things before we start:
- This process is NOT limited to work for just SD cards, you can do this for USB flash drives as well.
- The drivers that we will be modifying are compatible with Windows XP and Windows 7 32-bit. They are NOT compatible with Windows 7 64-bit. If you run 64-bit, you're out of luck. However, if you needed to, you could run Windows in XP mode or use a different OS in a virtual machine.
Procedure:
1.) Download the USB_LocalDisk.zip file attached to this post. Or download it from here: http://www.etcwiki.org/wiki/Cfadisk_usb_driver . Or if that link stops working, try doing a google search of xpfiledvr1224_320.zip. They are the same drivers.
2.) Extract the USB_LocalDisk folder to your desktop.
3.) Insert the SD card (via MMC reader or USB adapter) that you want to be able to view, and open your computer's Device Manager. Click the dropdown arrow of the Disk drives category and find the entry for your SD card. Please note that this name will probably be different for each person based on the SD card and card reader/adapter you're using.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4.) Right click and select Properties. Choose the Details tab, and select Device Instance Path from the dropdown box. Copy that Value that appears in the box. Again, this value will most likely differ from the one in the screenshot.
5.) Go back to your desktop and open the USB_LocalDisk folder. Open the .inf file called "cfadisk" with Notepad or your favorite Text Editor.
6.) Navigate to the 26th line in the file. Highlight "device_instance_id_goes_here"
Paste your Value from before. Save the text file.
7.) Go back to the Device Manager, right click your SD card, and choose Update Driver Software -> Browse my computer for driver software -> Let me pick from a list of device drivers on my computer -> Have Disk -> Browse. From here, go to your desktop or wherever you saved the driver files and open the cfadisk file. Click Okay.
8.) Click next. It might give you a message about driver compatibility, but it's fine, just hit yes. At this point, it will begin installing the drivers. Once again, you might be informed that the driver isn't signed. Don't worry about it, just choose Install this driver anyway. Now it should finish the installation.
9.) If all goes well, your SD card partitions should now be mounted separately in the Local Disk section of My Computer.
10.) You might want to consider renaming the different partitions to help you remember which is which. Again, this isn't necessary, but if you have a bunch of disks and get down to about drive letter P: and Q:, things start to get a little confusing.
If anyone has any suggestions on how to make this tutorial more helpful, let me know.
Lastly, I did not create these drivers or discover this process. I took my information from several sources and created this tutorial.
Sources:
http://www.getusb.info/usb-hack-turn-a-usb-stick-into-a-hard-drive-or-local-disk/
http://chdk.setepontos.com/index.php?topic=2332.0
http://www.ehow.com/how_5941768_make-flash-drive-local-disk.html
Disclaimer:
I am not responsible for any lost data or damages that occur to your computer or SD card. The steps in this tutorial are not harmful, but failure to follow the directions listed has the potential to harm your machine.
Looks nice, thanks. Can't test but i would like to read some feedback about this.
Ah maybe you could change Mount Multiple SDcard to Mount Multiple SDcard Partitions.
~ Veronica
lavero.burgos said:
Looks nice, thanks. Can't test but i would like to read some feedback about this.
Ah maybe you could change Mount Multiple SDcard to Mount Multiple SDcard Partitions.
~ Veronica
Click to expand...
Click to collapse
Where do you mean?
Nice guide you have written here, the main problem windows users have (unlike *nix users) is that an easier way needs to be found to flip the RMB (Removable Media Bit) on the thumb drive so it is recognized as HHD. I am currently researching this, if a solution exists then this would be applicable to all windows versions 32/64 bit and make our lives considerably easier.
EDIT///
Found a 64bit Hitachi cfdisk driver here h t tp : / / hardforum.com /showthread.php?t=1655684, haven't had a chance to test it yet since I am in class on my 32 bit laptop. (sorry I can't post url yet, I have to up my post count still.)
Attached file.
Redman247 said:
Nice guide you have written here, the main problem windows users have (unlike *nix users) is that an easier way needs to be found to flip the RMB (Removable Media Bit) on the thumb drive so it is recognized as HHD. I am currently researching this, if a solution exists then this would be applicable to all windows versions 32/64 bit and make our lives considerably easier.
EDIT///
Found a 64bit Hitachi cfdisk driver here h t tp : / / hardforum.com /showthread.php?t=1655684, haven't had a chance to test it yet since I am in class on my 32 bit laptop. (sorry I can't post url yet, I have to up my post count still.)
Attached file.
Click to expand...
Click to collapse
Nice work! I'm not able to test this right now as I'm out of town and away from my desktop, but I definitely will try this next week.
On a similar note, I am learning that to flip the RMB will require a mass production tool. The good news is that doing so will allow it to be read as a HDD no matter what windows machine you plug it in to (no need for cfdisk!) the bad news is that there is no mass production tool that covers all drives, it varies from manufacture to manufacture.
Redman247 said:
On a similar note, I am learning that to flip the RMB will require a mass production tool. The good news is that doing so will allow it to be read as a HDD no matter what windows machine you plug it in to (no need for cfdisk!) the bad news is that there is no mass production tool that covers all drives, it varies from manufacture to manufacture.
Click to expand...
Click to collapse
Your .zip was corrupt, so I attached a new one in this post and here is the originial source, too:
http://hardforum.com/showthread.php?t=1655684&highlight=cfadisk
@Everyone, be aware that in order to make this work on Windows 7 x64, you must either:
a.) Find a piece of software to sign the driver.
OR
b.) Disable the driver signing manually.
There's more information in the source thread.
Again, DO THIS AT YOUR OWN RISK. I may or may not add a section to this tutorial for the 64-bit OS.
Once the device driver is modified to recognize multiple partitions on an SD card, can one still write an ISO image to the SD card?
Followed your procedure for my 64GB Transcend Jetflash 500 and now I have this in windows explorer:
How do I get my old driver back???
UPDATE:
I reformatted my SDCard, but the first partition is still only recognized.
creeve4 said:
Followed your procedure for my 64GB Transcend Jetflash 500 and now I have this in windows explorer:
View attachment 1546701
How do I get my old driver back???
UPDATE:
I reformatted my SDCard, but the first partition is still only recognized.
Click to expand...
Click to collapse
Hi creeve,
Judging by your screenshot, your SD card is still being read as a removable disk. Looks like something didn't go correctly during the renaming and driver install.
View Last SD Card Partition on Native Nook Tablet Boot Option
Thank you for this. Would anyone know if similarly it is possible to view the last partition with all the storage data from a CM10 SD card when you boot into the native Nook Tablet system? Currently, only the first partition is visible when you boot into the native software.
Thanks!
I don't think it would be possible unless the NT is rooted.
moxda00 said:
Thank you for this. Would anyone know if similarly it is possible to view the last partition with all the storage data from a CM10 SD card when you boot into the native Nook Tablet system? Currently, only the first partition is visible when you boot into the native software.
Thanks!
Click to expand...
Click to collapse
Possibly by editing the vold.fstab file located in /etc to change which SD partitions your tablet mounts.
how to modify vold fstab file entry to show last partition
Solar.Plexus said:
Possibly by editing the vold.fstab file located in /etc to change which SD partitions your tablet mounts.
Click to expand...
Click to collapse
Thank you! I will try it, but is there any potential for damage? Below is the entry in my vold.fstab. What do I have to modify to make the fourth partition of my sdcard show up? By the way this is a CM10 SD Card created based on the intructions here: iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet
If there is some place where I can learn about the setup please point me to it. I am willing to learn!
Thanks again!
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
##
Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <lun_syspath> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## perm_mask - Mount permission mask: octal integer or 'auto' for default permission.
## <lun_syspath> - LUN for the device
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
dev_mount media /mnt/media 10 002 /devices/platform/usb_mass_storage/lun0 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
# TODO: it is preferrable to use 'by-name'
#dev_mount media /mnt/media auto auto /devices/platform/usb_mass_storage/lun0 /dev/block/platform/mmci-omap-hs.1/by-name/media
moxda00 said:
Thank you! I will try it, but is there any potential for damage? Below is the entry in my vold.fstab. What do I have to modify to make the fourth partition of my sdcard show up? By the way this is a CM10 SD Card created based on the intructions here: iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet
If there is some place where I can learn about the setup please point me to it. I am willing to learn!
Thanks again!
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
##
Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <lun_syspath> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## perm_mask - Mount permission mask: octal integer or 'auto' for default permission.
## <lun_syspath> - LUN for the device
## <sysfs_path> - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
dev_mount media /mnt/media 10 002 /devices/platform/usb_mass_storage/lun0 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
# TODO: it is preferrable to use 'by-name'
#dev_mount media /mnt/media auto auto /devices/platform/usb_mass_storage/lun0 /dev/block/platform/mmci-omap-hs.1/by-name/media
Click to expand...
Click to collapse
The bold line in your quote is the line you will need to change in order to mount a different partition of your SD card. I do believe if you change the first "auto" you see in that line to whichever partition number you want (4 in your case), and then reboot, you should be good to go.
Also, if you use a text editor such as the one included with ES File Explorer, a backup of the original file will be automatically created, so you always have your original that you can revert back to if need be.
Solar.Plexus said:
The bold line in your quote is the line you will need to change in order to mount a different partition of your SD card. I do believe if you change the first "auto" you see in that line to whichever partition number you want (4 in your case), and then reboot, you should be good to go.
Also, if you use a text editor such as the one included with ES File Explorer, a backup of the original file will be automatically created, so you always have your original that you can revert back to if need be.
Click to expand...
Click to collapse
Thanks, I did some research and bumped across this site which explains a bit (i have to remove the http cause I can't post links yet):
android.googlesource.com/platform/docs/source.android.com/+/master/src/tech/storage/index.md#
I'm curious why auto is repeated twice? I will try to just change the first auto for now and see what happens...
How to edit a root file?! Granting SU not working...
Solar.Plexus said:
The bold line in your quote is the line you will need to change in order to mount a different partition of your SD card. I do believe if you change the first "auto" you see in that line to whichever partition number you want (4 in your case), and then reboot, you should be good to go.
Also, if you use a text editor such as the one included with ES File Explorer, a backup of the original file will be automatically created, so you always have your original that you can revert back to if need be.
Click to expand...
Click to collapse
I've read around a little and I'm comfortable about trying it. However, I can't seem to modify the vold.fstab file and save the changes. I've tried several file editors including Root Browser. When I tried to save my changes the SU permission request box came up and I granted SU permission. However, I get a message saying: The file cannot be saved.
Please help! It's very frustrating. I've tried 5 different editors (ES, Root Browser, File Expert, etc)
moxda00 said:
I However, I get a message saying: The file cannot be saved.
Please help! It's very frustrating. I've tried 5 different editors (ES, Root Browser, File Expert, etc)
Click to expand...
Click to collapse
Have you mounted system folder as writeable? Root settings in ES.
Successfully modified volt.fstab and accessed 4th partition!!
asawi said:
Have you mounted system folder as writeable? Root settings in ES.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Thanks! That did it! I just had some trouble finding the flag/option to make root writeable. Once I did I was able to change the mount line as follows: dev_mount sdcard /mnt/sdcard 4 auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
I rebooted and it worked! Exactly what I wanted.
Thanks Solar.Plexus!
moxda00 said:
Thanks! That did it! I just had some trouble finding the flag/option to make root writeable. Once I did I was able to change the mount line as follows: dev_mount sdcard /mnt/sdcard 4 auto /devices/platform/usb_mass_storage/lun1 /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
I rebooted and it worked! Exactly what I wanted.
Thanks Solar.Plexus!
Click to expand...
Click to collapse
No problem, my friend. Glad to see you got it figured out!
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is new Android distribution based on Linux, Android and Archos stock os, using SDE from Archos.
Features:
Easy install method for external (SDcard) and Internal storage
EXT4 (much faster than ext3, can store files >4GB comparing to FAT32)
Full read/write access to every part of system
root (su + superuser.apk) out of the box
new services like: samba, sshd, vpnc, openvpn, dvbt, nfs4
3G/usb tether support
Possibility to remove some google/Archos apps
Swap memory in RAM (CompCache) or on disk by default or when you need it
No 300MB limit for apps (and no faulty app2sd required)
You can have SD card Class 8/10 - that can be much faster than internal flash (check this thread)
Many new new kernel modules (usbserial, ntfs, 3G modems, nfs4, cifs, hfs, iptables etc.)
DVB-T support for selected tuners
updated modules, firmware (like WiFi)
User friendly UrukConfig application
... and much, much more - to much to mention all here - please read changelog
Since 1.0 release main documentation source for UrukDroid is on it's WiKi. Please use it as a first and primary information source for UD.
Link to project (googlecode) page is: http://code.google.com/p/urukdroid
Update (10.09.2015)
Since code.google.com is no longer working (read only for limited time) - here are working links to latest (and final) release of UrukDroid: Dropbox,
I hope that new, much more detailed and complete documentation will help you use UrukDroid at it's full potential.
Changelog, proposed futures
Changelog:
UrukDroid 1.6 (02.01.2012) "DOV FUS LOS Wahl ko Daar Sivaas!"
[CHANGE] Incorporated changes from Archos firmware 2.4.19, 2.4.65, 2.4.80 and 2.4.81
[CHANGE] Updated superuser apk and binaries
[FIX] Fixed some library linking
[NEW] Changed top bar button size to 32px permanently
[NEW] New overclock module from milestone-overclock to change CPU voltage and max frequencies on the fly
[CHANGE] Added overclock support to CPUGovernor service
[FIX] Restored proper busybox binary
[NEW] New patches on kernel from December update from Archos git
[NEW] Full iptables support (with NAT, conntrack etc) - so everything is now possible (redirect, proxies etc)
[NEW] Full kernel timing for power consumption monitoring
[NEW] Recompiled WiFi? and HDMI drivers
[NEW] Added python 2.7, iotop (for watching i/o operations), PowerTOP (for power consumption monitoring - but it's not as useful as on x86)
[NEW] Added ntfs-3g support - full read/write support for NTFS file systems (need to be used manually, vold does not use it)
[CHANGE] Added UrukDroid? Rescue Menu - Repair submenu with disabling overclocking (for those who made their device unbootable with overclocking) and Dalvik cache cleaner
[NEW] New feature in cpugovernor script (genconf, current)
[CHANGE] New features in update subsystem
scripts now tries to keep /data/.tmp directory cleaner,
for those with disk shortage /data/.tmp can be now symlink to directory on sdcard
updater now checks if you have enough free space in /data/.tmp before it begin installation
update process now can be during bootup (better one) if you have enough free space on rootfs, or on running system (not so nice - this is default behavior until UD 1.6 release)
[CHANGE] restoring backup in Rescue Menu now erases partition before restore (until now it was just overwriting)
[FIX] added (again ) xbox pad kernel support (was missed out in new kernel compilation)
[FIX] fixes scp/sftp-server (on some configuration refused to start child processes)
UrukDroid 1.5 (16.0.2011) Manamana!
[CHANGE] Since UrukDroid? 1.1 (both beta1/2/3 and release candidate 1/2/3) had stability and compatibility issues - that I was unable to trace down (too many changes on changes etc.) - I've decided to implement all stuff from beginning on fresh OS. Since all "reverse engineering" stuff was already made and I already have required knowledge - It should be the fastest method. So entire system is cleaned up, updated to latest binaries - and so far looks good . That's why I've bumped version to 1.5 - just to make it a bit more visible it's not a straight continuation of 1.0/1.1.
[FIX] No more "soft reboots" (system reloaded it's graphics UI part)
[FIX] No more turning off WiFi issue (but it happens that WiFi can't pop in after full reboot - another reboot is required)
[FIX] CIFS startup on boot (Issue 57)
[CHANGE] Update process should be now more chatty and report more errors
[CHANGE] Reverted back WPA service (which enable UrukDroid? WPA supplicant with AdHoc? support) - since some people reported problems with adding new networks with Uruk version of WPA supplicant.
[CHANGE] Merged changes from Archos 2.3.28 OS
[NEW] New wpa_supplicant - hopefully with all features and without most of known problems (sometimes it still refuses to start)
[CHANGE] Updated modules and kernel
[FIX] Fix camera support for A43
[CHANGE] Merged changes from Archos 2.3.26 OS
[CHANGE] Redesigned services to output more reliable status
[FIX] Mediascanner fixes (did not rescan data sometimes)
[NEW] Introduced in 1.0 "Rescue Menu" now fully functional (RM)
[NEW] RescueMenu now have Alternative OS? boot feature
[NEW] RescueMenu now have "bare metal" backup/restore functionality
[NEW] Update process will now communicate with user with help of UrukConfig
[NEW] Enabled cgroups
[FIX] "Moved" boot image on A101
[FIX] 3Gmodem_init.sh fixes
[NEW] You can dissable boot from SDCard by naming any of it's partition "noboot" ('[email protected]:/root# e2label /dev/block/mmcblk2p1 noboot')
[NEW] patch (by Sibere) increasing USB current in Host mode
[NEW] New default apps in UrukDroid 1.5: WiFi Manager, FileExpert, QuickPic, Opera browser
UrukDroid 1.0 (30.04.2011)
[FIX] sshfs missing files fix
[FIX] EasyInstall: changed datafs max size from 2GB to 1.95GB (for market to work), fixed partition sizes for A101 16GB when doing internal install with resize, fixed installation for A70H devices
[NEW] small script to copy UrukDroid files from SDCard (external) to Internall (copy_from_sd_to_internal.sh)
[CHANGE] Changed behaviour of dvb service (device configuration)
[FIX] Added some missing modules for DVB support
[CHANGE] New kernel modules for more dvb devices (but it requires manual loading and testing)
[NEW] rsync tool
[CHANGE] swap service now can work on swap partition (or like before on swap file), also after mounting sdcard ext4 partition
[NEW] Ad-Hoc WiFi connection support by default (networks are visible with "*" on beginning of it's SSID)
[CHANGE] Some new progress indicators during install/upgrade
[NEW] Simple Animation during late phase of bootup
[NEW] New service: cifs (to load cifs modules)
[NEW] Added cgroups kernel setting
[NEW] Moved some modules dependencies (cifs,ntfs,dvb) to /etc/modprobe.d
UrukDroid 0.7 (28.02.2011) you're damn right it's a gift!!
[NEW] NFSv4 client support
[NEW] FS-Cache (cachefilesd) support for NFS (local disk cache for NFS files)
[NEW] sshfs support
[FIX] OpenVPN fix - thanks to nenadr
[FIX] PPtP fix - thanks to nenadr
[NEW] vpnc tool for using Cisco VPN connections
[NEW] vpnc UrukDroid service
[CHANGE] Updated to libc6 2.11 (and all binaries recompiled/changed because of it - big change)
[NEW] new gnu tools: nmap
[NEW] EasyInstall now allows installing UrukDroid on internal (mmcblk1) storage in A70 and A101
[NEW] Integrated 3G USB modem and RNDIS USB tethering service by nenadr
[CHANGE] New iobench.sh (with new bonnie++ test)
[CHANGE] Changed device fingerprint to work better with google market (enable download some missing apps)
[CHANGE] Merged Archos 2.1.8 firmware changes
[CHANGE] Changed DVB subsystem support and kernel/modules dependencies to work with new v4l2 modules (it will brake compatibility with most other kernels probably)
[FIX] Changes it UrukUpdate mechanism to work every time when file is moved to "/data/UrukUpdate"
[NEW] Added required modules and iptables service configuration for DroidWall (firewall) application
[NEW] sudo subsystem for launching properly some root tasks
UrukDroid 0.6 (11.02.2011) Eye of the Uruk... in new logo
[CHANGE] Merged changes from Archos firmware 2.1.2/2.1.3/2.1.4
[CHANGE] DVB support with LiveTV.apk from chulri (for selected cards, there are more modules then listed in /etc/uruk.conf/dvb - but it requires to do some experiment and report it back)
[CHANGE] Changed Uruk service to work better with new UrukConfig
[NEW] New services: openvpn, mediascanner
[NEW] IO Benchmark tool: iobench.sh
[NEW] Possibility to turn off mediascanner and use it on demand only
[FIX] Fixed mount_sdcard.sh script to work with 2.1.2 ext3 partitions
[NEW] Updated boot sequence with progress during upgrade/install
[NEW] You can hide soft buttons (Archos buttons) with UrukConfig
[NEW] Easy Install method - no need to know anything about Linux - just plug and wait...
[NEW] Kernel modules for 3g dongle
UrukDroid 0.5 (27.01.2011) Tom Bombadil... in red
[NEW] CompCache (aka ramzswap) support
[NEW] New CPU governor - interactive. Ported from XDA CyanogenMOD
[NEW] DVB: applied patches by chulri, Siano SMS1XXX USB support
[NEW] DVB: modules from outside kernel tree
[NEW] Some more GNU tools: gzip utils, zip utils, unzip utils, nc (NetCut for DVB streaming)
[CHANGE] New services model - so they can be easily run/configured with help of UI
[NEW] New kernel modules: usbnet, lzo
[NEW] Mediascanner modification - it should has much, much smaller impact on system performance
[NEW] sqlite3 (3.5.9) installed, for easy database file manipulation
[NEW] after restart of UrukDroid it will boot once again to Uruk without need of pressing any buttons, to boot on stock OS please use boot menu
[FIX] mount_sdcard.sh fixed so it will mount first ext4 partition on sdcard if exist, and will not interfere with Vold if its vfat
[CHANGE] New update/upgrade/flash model - everything done on UrukDroid - no boot menu required
[NEW] New application to configure UrukDroid - UrukConfig.apk. Installed with this release. Can be uninstalled in default way.
[FIX] Fixed corrupted logo in A101
[NEW] Unified kernel for UrukDroid on SDCard and internal storage (A70S/A101)
[CHANGE] Services ENABLED with this release: CpuGovernor, CompCache
UrukDroid 0.4.2 (21.01.2011)
Just extracted as a separate update file GoogleMarket
UrukDroid 0.4.1 (15.01.2011) Myyy preciousssss...
Some more tools like: bc, proc utils, vim, tcpdump, bzip2, tar etc.
Android apps (Market, Maps, Talk, Calendar, Contact, Feedback, Locator, Updater) by default
Samba (3.2.5) support for sharing /mnt/storage (internal and sdcard storage) from Archos
Dropbear SSH server
Backported modprobe, depmod etc. tools for modules management
WiFI driver recompiled, WiFi HW firmware update (from 6.1.0.0.335 to 6.1.5.44.7)
Initial DVB-T support (Afatech AF9005, Afatech AF9015, DiBcom DiB0700, Terratec CinergyT2/qanu)
Bootlogo with progress steps
Cleanups of initramfs and rootfs
EXT4 drivers backported from 2.6.30 - some mount changes (to prevent config files corruption)
Initial A70H support
SDCard/HD layout changed
Autoupgrade service and installation helper
ADB fixes
Removed two apps. TelephonyProvider.apk, Phone.apk
Since 0.4 all services are DISABLED by default, to enable it edit proper config file in /etc/uruk.conf/
UrukDroid 0.3 (9.01.2011) Rise my Uruk... not yet Hai
iptables, ntfs support
some more USB modules: usbserial, pl2303
fixed bluetooth problem (not working in Uruk 0.2)
automounting improvements (much more bulletproof)
new configuration files (/etc/uruk.conf/) to enable/disable features
new Uruk services (/etc/uruk.d/)
some more GNU utils openssh-client, coreutils
USB charging enabled (NOT tested!!!) - It would required much more power then standard USB in PC can give, use USB wall/car charges or double/triple USB cables
UrukDroid 0.2 (5.01.2011) Go GNU release
"smart" automounting script (that will mount ext4/vfat third partition from sdcard in RIGHT place, AFTER internal storage is mount)
plenty of useful GNU tools: whole e2fstools (mkfs, fsck for ext2/ext3/ext4), parted (for partition resize, format etc.), vfat tools, new toolbox, mtr, top, strace, bash - and much more (look in /usr/local/bin and /usr/local/sbin)
swap memory ON by default (50MIB file /swap01.file)
required compiled libraries libparted, libncurses, libe2fs... etc. (look in /usr/local/lib)
new text editor in text mode: nano (my favourite)
some init.rc cleanups
kernel changes (mostly toward console output)
fixed small (but problematic) misconfiguration in Archos (yep original one) Android in linking /etc/mtab
UrukDroid 0.1 (30.12.2010) Initial "release"
recompiled kernel with ext4, nfs4, fb console
added su and superuser.apk
bootup changes (to make it work)
Features planed in next releases:
backup scripts
proxy settings
CynanogenMOD parts backported
OC/UC kernel be default
FAQ or Tips & Tricks
More information you can find in seperate thread on this forum - FAQ + Question/Awnsers
How to upgrade from previous releases
To upgrade from 0.5 you should download special upgrade file (UrukDroid-0.6-upgrade.tbz2) from first post. You need to place this file in directory "/data/UrukUpdate".
First method:
Put it on your internal storage by any means - this is /mnt/storage (also visible as /sdcard/). Then use file manager (like Astro or RooteExplorer - not build in one) or do as follow in terminal (or over ssh)
Code:
su
cd /sdcard/
mv UrukDroid-0.6-upgrade.tbz2 /data/UrukUpdate/
Second method:
Use UrukConfig to enable SSHD (if you don't have it started already), and use any SCP/SSH client (like WinSCP, or plain scp on Linux) to copy file (default username is "root", password is "UrukDroid") to "/data/UrukUpdate".
In both cases upgrade will start automatically; alter kernel, initramfs and when finished, device will reboot itself.
How to enable/disable and configure UrukDroid services?
UrukDroid services are configured by text files, that can be found in /etc/uruk.conf/ directory. You can use file manager like RootExplorer or Terminal to edit them, but most convinient way is to use SSHD service and some ssh client (for example putty).
You can also use UrukConfig application - build in since 0.5 release. After you do some changes, restart service (/etc/uruk.d/service_name stop/start) or simply reboot Archos. Since 0.5, by default only CompCache and CPUGovernor are enabled.
Currently available services
samba - it's SMBD server allowing mounting your Archos storage directory on your PC. Default user is "storage" and password "UrukDroid"
sshd - SSH server allows you to connect to your Archos with any ssh client, work on terminal. It also allows to copy files with scp/sft. Default user is "root", password "UrukDroid"
swap - this service enable swap memory. It can make Archos a bit less responsive but memory manager won't kill application so quickly (co you can use WWW browser, email an communicator simultaneously - for example of course)
iptables - this pseudo service will load necessary modules to use iptables (firewall) features
ntfs - if you plan to connect NTFS formatted devices to your Archos - enable this service
dvb - this service load necessary modules to watch TV on your Archos. This service requires configuration from your side - it won't work "as is". Please read and edit config file (/etc/uruk.conf/dvb)
compcache - Start/stop CompCache swap memory service. Compcache is a compressed part of memory, where less used object reside. Usual compression ratio is 70%
cpugovernor - Changes default CPU governor and it's parameters. Governor decides how to scale CPU frequency. Since 0.5 there is new "interactive" governor.
openvpn - It's an implementation of popular free VPN service for Uruk. It will act like the one used in Archos stock config with difference it will work all the time - whenever you go, and you have full flexibility of configuration. Config file resides in /etc/openvpn/archos.conf.
VPNC - It's open implementation of Cisco VPN service. You should edit /etc/vpnc/archos.conf file.
NFS4 - NFS v4 client service allows you to mount remote file storage with use of NFS (much faster then SMB for example). You can also enable use of cachefilesd sub-service - that will cache locally, files transferred with NFS (for smooth playback of movies for example)
How to remove some default apps?
App started at the boot time are stored in /system/app, I've already removed some of them by moving it to /system/app.old/ - but you can do it by your own - but remember - some of them are actually required to run system
Some filesystems benchmarks (that's the reason why I wanted ext4 so badly)
Write tests (I've testes different filesystem and partition sizes)...
Tests on Archos:
internal 8GB
0,71Mb/s ext3,ordered,noatime
5,45Mb/s fat32
Lexar 16GB
2,63MB/s ext3,ordered
6,25MB/s ext4,ordered
Test on computer (the same lexar card)
2.93Mb/s 1GB,ext3,noatime
2.78Mb/s 1GB,ext3
3.04Mb/s 1GB,ext2
8.62Mb/s 1GB,vfat
7.61Mb/s 1GB,btrfs
7.87Mb/s 1GB,ext4
7.87Mb/s 16GB,ext4
Card is 16GB SDHC Lexar class 6 only - so this toshiba nand inside is not state of the art either :/
How to roughly check your filesystem write speed
Go to directory where you can write and were is more then 100MiB of free space and do the line. It will sync devices (flush all write caches), write 100MiB file filled with zeros, and fush caches once again to measure real write speed without buffers. Then easy math... and my laptop disk has write speed 16,66MiB/s
Code:
[email protected]:/tmp$ sync; date; dd if=/dev/zero of=test.file bs=1M count=100 2>/dev/null; sync; date
Wed Jan 5 19:02:28 CET 2011
Wed Jan 5 19:02:34 CET 2011
[email protected]:/tmp$ bc -q
scale=4
100/(34-28)
16.6666
quit
UrukDroid configuration system
I've created (or recreated, since Google threw away existing Sytem V and other solutions) something that works like rc/init.d system. It's old fashion, but for only few services will do it's job.
There are few location to remember:
/system/etc/uruk.d/ - directory with services
/system/etc/uruk.conf/ - directory with configuration files
/system/etc/init.d/ - symlinks Sxxserice/Kxxservice (like S01swap) to be run during startup process
Proper path is /system/etc/ but it's symlinked on every Archos to /etc - so you can also work on /etc/uruk.d, /etc/uruk.conf etc.
To enable iptables support (load proper module) it's enought to edit /system/etc/uruk.conf/iptables
To change swap memory settings edit /system/etc/uruk.conf/swap
How to mount ext4 under Windows?
There is project called "ext2read" that claims to work with ext4 also (I've only tested it with ext2 long time ago - it worked) http://sourceforge.net/projects/ext2read/ - please write some commends if you use it.
What is current directory/disk layout?
/ -> SDCard first partition (512M) - for root filesystem
/data -> SDCard second partition (1GB) - for installed apps
/mnt/storage -> internal 6GB partition - for data used by installed apps
/mnt/storage/sdcard -> SDCard third partition - anything you want, nothing by default
/mnt/sdcard2 - proposed mount point for other volumes, not used by default
And there is something called symbolic links (symlinks) - witch is kind of Win shortcut used on UN*X extensively.
/sdcard -> /mnt/storage
/storage -> /mnt/storage
/mnt/sdcard -> /mnt/storage
So you can enter /sdcard - and you are be using files from /mnt/storage. You can also create symblinks by yourself
Code:
ln -s /source destinations
How to gather data report from UrukDroid
Best way is to use SSH. For this, please start "sshd" service on UrukDroid by using UrukConfig application or by editing /etc/uruk.conf/sshd file.
First start will take one minute or so - since sshd has to generate unique encryption keys.
If you use Windows download putty.exe (ssh client) and run it. Write your Archos IP (it has to be visible in network) and connect.
Use
Login: root
Password: UrukDroid
Click to expand...
Click to collapse
Now you can write Linux commands and cut/paste results for help/debug purpose.
Thanks!
I think you talked me into it! I'll play with it tomorrow.
I've found this on Nook Color thread http://forum.xda-developers.com/showthread.php?t=888216
Can someone test is it worth to do on Archos? I think we don't need phone service running in background. Ill try this tomorrow when i get back to home but maybe someone can test earlier?
sorry for asking,but what is the point in doing step 3,i mean what does it actually do?
This is backup of install instruction, leaving more space for custom approach. Instruction in first post is now much simpler with less 'if/or'.
Material for this thread came from discussion here. So please be kind read also this thread before getting to work
This is mini how-to boot modified Archos Android from SD card, using SDE. It's base on 2.0.71.
Since this Android mod/distribution required some name - let it be Uruk-Droid
Why bother:
ext4 (much faster than ext3, can store files >4GB comparing to FAT32)
full r/w access to every part of system
root (su + superuser.apk) out of the box
possibility to remove some google/Archos apps (already done partly)
swap memory when you need it
no 300MB limit for apps (and no faulty app2sd required)
you can have SD card Class 8/10 - and that's much faster storage than internal flash (inside is something equal class 6 or 4)
Warning
Be aware that this modification requires SDE and probably some Linux knowledge.
By doing described below steps you probably can't brick your Archos - but do it on your own risk.
Root access on your devices makes it less secure form malicious software (user more head - less fingers )
Known problems:
Android automounter (vold) does not recognize EXT4 in stock firmware - so it will claim SD card is damaged (it's just a message) (FIXED)
Before you start:
Read about SDE on forum
Install some terminal emulator from Market (eg. "Android Terminal Emulator")
You should have 2.0.71 already installed (I'm not sure if it's required but only with that configuration tested)
All operations described here, done on Linux or Android should be done from root user (you can switch to that user in terminal by typing "su" or "sudo su" command)
If you don't have Linux - find any recent Rescue CD, Live CD or Virtual disk (VirtualBox or VMware) - distributions does not matter
SD card partition design
First of all, preferably buy card class 6+. So it won't be slower than internal storage
I'm currently using 3 partitions
0,5GB / (rootfs)
1GB /data
rest /mnt/storage/sdcard/
but You can create one big partition instead - I've made my configuration because of easiness to backup and upgrade (rootfs is easy to upgrade later on, /data has only runtime data and application, rest is for movies etc.) Size of /data partition determines how many apps you can install on your device.
Here it's how it looks on fdisk
Code:
linux-machine:~# fdisk -l /dev/sdb
Disk /dev/sdb: 16.0 GB, 16012804096 bytes
199 heads, 44 sectors/track, 3571 cylinders
Units = cylinders of 8756 * 512 = 4483072 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 1 121 529716 83 Linux
/dev/sdb2 122 362 1055098 83 Linux
/dev/sdb3 363 3571 14049002 83 Linux
Step one
Create at least one primary partition on SD card with fdisk, gparted, parted or any other partitioning tool. Assuming your SDCARD is visible as /dev/sdb (on Linux box - check "dmesg").
Code:
su (go root)
fdisk /dev/sdb
fdisk options (it's interactive):
p (print existing partitions)
d n (delete partition by it's number 1,2,3 etc)
n (create partition, you will be asked about type (primary, secondary - go primary), number (give first available), start sector (just enter will set first possible), size (you can give it as +1M, +2G etc)
w (write all changes, until you give this command no changes are made on disk physically)
Format partitions as EXT4 - but without huge_file option (it won't work with this feature since it requires special kernel option that brakes compatibility with existing modules).
Code:
su (go root)
mkfs.ext4 -O ^huge_file /dev/sdb1
If you created more partitions - do those steps for everyone.
Code:
mkfs.ext4 -O ^huge_file /dev/sdb2
mkfs.ext4 -O ^huge_file /dev/sdb3
Kind of "session log" for this steps you can find in this post.
Step two
Extract content of rootfs.tar.gz onto first partition on SD card (it HAS to be first one). Do it from root account on Linux/UNI*X box - or you won't transfer all permissions properly (mainly +s on su/superuser.apk).
assuming your SD Card is visible under Linux as /dev/sdb (you can check it by typing "dmesg" after you connect it)
open terminal/shell - go root: su, or sudo su
create mount point: mkdir /tmp/sdcard
mount it (if it's not mounted already) for example: mount /dev/sdb1 /tmp/sdcard
go to /tmp/sdcard directory: cd /tmp/sdcard
extract rootfs: tar -zxf /path_to_file/rootfs.tar.gz
exit directory: cd
umount your card: umount /tmp/sdcard
Flash initramfs.gz and zImage from SDE boot menu:
reboot Archos70, hold up or down volume key until you see Recovery menu,
choose "Recovery System"->"Developer Edition Menu"->"Flash Kernel and Initramfs",
connect Archos to PC and copy initramfs.gz and zImage to device
Reboot and hold up or down volume, choose "Developer Edition".
You should see all yours apps etc. - it should look like your Archos , but with su/superuser.apk etc. (check it on terminal emulator by typing "su" and enter).
Before go to next step make sure you have booted to SDE system AND it has root access! (check "su" in terminal, run root explorer or titanium backup)
Step three
It's kind of optional - since you have already working system - but it's not fun yet
Now you should copy /data files onto SD card. Use terminal emulator (from market can be "Android Terminal Emulator") or sshd (QuickSSHd and log into your tablet) and do:
If you have ONE partition
Code:
su
cp -rp /data/* /data.new/
If two or more
Code:
su
mount -t ext4 /dev/block/mmcblk2p2 /data.new
cp -rp /data/* /data.new/
umount /data.new/
Poweroff device.
Step four
Put card into computer and:
one partion
remove /data
rename /data.new to /data
On Linux it may look like this:
Code:
su (or sometimes "sudo su")
mkdir /tmp/sdcard
mount /dev/sdb1 /tmp/sdcard
cd /tmp/sdcard
rm -rf data
mv data.new data
edit /init.rc (it's /init.rc on Android - on Linux box it's going to be something like /tmp/sdcard/init.rc) - use any editor to modify file - do it as a root!
Code:
su
vi /tmp/sdcard/init.rc (edit the file)
umount /tmp/sdcard/
What to edit:
Code:
# Comment this
# mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid
# Uncomment this
# mount ext4 /dev/block/mmcblk2p2 /data noatime
mount ext3 /dev/block/mmcblk0p4 /data.old noatime nosuid
two or more partitions
edit /init.rc (it's /init.rc on Android - on Linux box it's going to be something like /tmp/sdcard/init.rc) - use any editor to modify file - do it as a root!
Code:
su (or sometimes "sudo su")
mkdir /tmp/sdcard
mount /dev/sdb1 /tmp/sdcard
cd /tmp/sdcard
vi init.rc (edit file)
umount /tmp/sdcard
What to edit:
Code:
# Comment this
# mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid
# Uncomment this
mount ext4 /dev/block/mmcblk2p2 /data noatime
mount ext3 /dev/block/mmcblk0p4 /data.old noatime nosuid
If you have third partition on SDCARD, whether it's EXT4 (recommended) or FAT32 it should by automounted since 0.2 version.
Reboot - it should work
End
Stuff you can do later:
Vold - automount daemon on android is quit.... crappy - to let go message about "sd card damaged" edit /etc/vold.fstab and hash the line "dev_mount_lun volume_sdcard /mnt/storage/sdcard...."
Other partitions - if, by any reason, you have more partition on SD card (more then 3) you can also mount it putting in init.rc (there are some potential issues with vold to be solved)
for ext4
Code:
mount ext4 /dev/block/mmcblk2p5 /mnt/sdcard2 noatime nosuid
For fat32 partition preferably tweak with Vold config (/etc/vold.fstab) - or add something like this (in init.rc)
Code:
mount vfat /dev/block/mmcblk2p3 /mnt/sdcard2 uid=1000 gid=1015 fmask=0000 dmask=0000
Files (UrukDroid-0.3):
Megaupload.com
initramfs.cpio.gz
zImage
rootfs.tar.gz
Dropbox.com (there can be server error because of download limit)
http://dl.dropbox.com/u/1017593/ArchosGEN8/UrukDroid-0.3/rootfs.tar.gz
http://dl.dropbox.com/u/1017593/ArchosGEN8/UrukDroid-0.3/initramfs.cpio.gz
http://dl.dropbox.com/u/1017593/ArchosGEN8/UrukDroid-0.3/zImage
Nm you said it's faster, interesting... I may test that out.
IMHO you should point out that it is a great security risk for having access to root without any password.
BTW this comment is not meant to insult you in anyway, but I think it is only fair to people that will use it and to cover your own ass.
Maurice
Does this require a clean system to do the SDE Root? what happens to everything already installed etc.
MoonPhantasm said:
Nm you said it's faster, interesting... I may test that out.
Click to expand...
Click to collapse
There was already link to my write speed tests (now I've pasted it to second post) - read speed is about the same. In quadrant I have something about ~2300 (one of quadrants test is I/O benchmark) - but that's not my goal - so I don't care much about that kind of speed.
divx118 said:
IMHO you should point out that it is a great security risk for having access to root without any password.
BTW this comment is not meant to insult you in anyway, but I think it is only fair to people that will use it and to cover your own ass.
Click to expand...
Click to collapse
Of course your are right - but that's kind of obvious, and that's the reason why superuser.apk requires to specify what process can gain root access (I know it's not strong security - but better something than nothing)
Is there any way to do this on the a32, or can will there be a solution for the 32.
I had SDE installed before, but I used the uninstall developer edition option in the boot menu. Now, regardless of if I use the .aos file from archos that has SDE, whenever I reboot holding a volume button, I get to a menu that says "Archos A101IT Recovery", and "Would you like to recover your system?" with the following options:
No
Update Firmware
Repair System
Format System
I select update firmware, and all I get is an update failed error.
I don't know what to do. I have a basic linux knowledge, so I have my sd card properly formatted, without the huge file option. I've extracted the contents of rootfs.tar.gz to the first partition.
Any ideas on what to do?
$aur0n said:
I don't have that problem since I use Linux everywhere
My mmcblk2p3 is also EXT4 partition (since fat 32 has 4/2gb file size limitation it's only place where I can put bigger files - mainly movies. It's one of ther reasons why ext4 is good for the task).
To mount (vfat or ext4) during but of Archos put in init.rc
Code:
mount ext4 /dev/block/mmcblk2p3 /mnt/storage/sdcard noatime nosuid
or
mount vfat /dev/block/mmcblk2p3 /mnt/storage/sdcard
just after mount of /data.old for example..
/mnt/storage/sdcard is the place where automounter would normally mount this device.
Click to expand...
Click to collapse
I did try to add it to init.rc, but it wouldn't mount.
Running "busybox mount -t vfat /dev/block/mmcblk2p3 /mnt/storage/sdcard" after boot seems to work however.
Is /mnt/storage mounted yet at that point? It seems to be separately mounted ("mount" shows /dev/block/vold/179:9 mounted on /mnt/storage, but I can't find any line related to that in init.rc)
Since "Preparing internal storage" appears after boot, I assume the SD card has to be mounted after that (unless I mount it somewhere else, which would break compatibility with some apps)
Actually, I'd prefer if the SD card was mounted on /mnt/storage, and the internal storage on /mnt/storage/internal, is there a way to do that?
Edit: Ah, I checked that /etc/vold.fstab file. It seems to be what I need to edit to auto mount the SD card, but I'm not sure what I need to edit.
The line currently reads:
dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk2
"auto" seems to be the partition number, I tried to change this to different values as well as changing mmcblk2 to mmcblk2p3, but they result in the same SD card damaged message. Is this a no-go and just won't work or am I doing something wrong? Either way, it seems like it's the only way to mount the SD card at boot if I want it mounted to /mnt/storage/sdcard.
Edit 2:
Adding these 2 lines to init.rc and commenting out the equivalent lines in /etc/vold.fstab seems to work:
mount vfat /dev/block/mmcblk2p3 /mnt/storage
mount vfat /dev/block/mmcblk1p1 /mnt/storage/internal
Now I have the SD card mounted on /sdcard
However, the settings won't show the space information now, so I have to connect it to the PC to check free space. Is there a better way to do it?
Jdbye said:
I did try to add it to init.rc, but it wouldn't mount.
Running "busybox mount -t vfat /dev/block/mmcblk2p3 /mnt/storage/sdcard" after boot seems to work however.
Is /mnt/storage mounted yet at that point? It seems to be separately mounted
Click to expand...
Click to collapse
No, this mount point (/mnt/storage/sdcard) is not ready yet at this point - that's why I've changed it to /mnt/sdcard2 in howto. It's not good solutions (since probably some tools won't find media - like movie player) - but the only one for now. Vold is crappy, and even so it should mount _first_ usable partition (with auto option) but it does not want to do that. I can't check it, since I don't have vfat on sdcard, but probably the only solution is to do separate script/service with delayed mount - that's what I'm going to do for now, later on (in next release).
Q: However, the settings won't show the space information now, so I have to connect it to the PC to check free space. Is there a better way to do it?
A: (kind of joke) - user "df -h" in terminal, probably some more smart tools with gui are also able to show space used by "other" devices.
hurrpancakes said:
Any ideas on what to do?
Click to expand...
Click to collapse
I guess it's some Archos SDE bug and you should report it (I thing that after uninstall of SDE and second install you should see developer menu back - if not,
it's error or faulty "watermarking" at work)
jab12 said:
Is there any way to do this on the a32, or can will there be a solution for the 32.
Click to expand...
Click to collapse
My guess - it may also work for you. All gen8 devices have the same kernel and system - so give it a try.
xShadoWxDrifTx said:
Does this require a clean system to do the SDE Root? what happens to everything already installed etc.
Click to expand...
Click to collapse
Everything that is installed on INTERNAL 8GB storage is untouch. So even when sde fails to boot, you can go back to original Archos Android and work on that.
When you follow my instr. you should see second Android with all yours application installed but on ext4 with root etc. etc.
$aur0n said:
I guess it's some Archos SDE bug and you should report it (I thing that after uninstall of SDE and second install you should see developer menu back - if not,
it's error or faulty "watermarking" at work)
Click to expand...
Click to collapse
I think the error may lie in the fact that I have to access my sd card by mounting it through my a101. Tomorrow (or later today, rather) I will get a sd card reader so I won't have to rely on using the tablet.
Hi, thanks for howto.
Can we keep the superuser mode explained in this topic http://forum.xda-developers.com/showthread.php?t=880321&page=13 And use your method (in case i forgot m'y sd card And need root access)
I'm sorry it took so long, I got lots of stuff to deal with. Good things are worth waiting for (i heard)
First off: You are responsible for any of your actions! Changes that are needed to boot Ubuntu on your folio will void your warranty!
Special Thanks goes to DerArtem for posting his Kernels, Weeds2000 for eMail support, topogigi for wifi hacking and last but not least the Ubuntu-Touch Team on IRC that made it possible for me to tweak the touchscreen driver.
However, the system you are about to create is not fully functional, there are still things missing (a working sound driver for example). Its nice to play with it anyway
Heres a quick walk-through:
We will flash a kernel to the toshiba folio tablet which makes it possible to boot from an sdcard or USB-stick (You have to choose one, we need at least 2GB, I'd recommend 4GB so you can install fancy stuff like OpenOffice etc.).
We will then create a root filesystem with rootstock, which will hold our Ubuntu system (similar to your hard drive-Ubuntu).
Finally, we have to tweak that filesystem and change passwords, copy wifi driver etc.
Then we're able to boot a beautiful Ubuntu.
Things you will need:
- A Computer running Linux (Debian / Ubuntu would be great. If you're not running Linux on your computer, running it on the folio would make absolutely no sense. Please don't ask, I don't know how to install it in Windows.)
- The files i added to this post
- A SD-Card, 2-4 GB should be fine.
- optional: A second SD-card, 128MB would be enough (for flashing)
- A USB hub (If you want to boot from USB AND use a keyboard.
- Some time... =)
The first thing you should do is flash one of the update.zip files; choose update-sdmmc.zip (this will boot your folio from sdcard) or update-usb.zip (this will boot from a usb pen drive), open it and unpack the content to a sdcard (This has to be a SDcard, we're gonna flash our device from there.)
Backup all your data on your folio (I'm serious! It'll be gone!) and turn it off.
Put the SDcard in its slot and turn the folio back on. Press + hold both power and volume up.
Follow instructions to do a system update (If you've never done this before you shouldn't start now =) )
When it reboots, your folio will show some funny black and white linux text stuff and hang somewhere. Congratulations! You just bricked your tablet. Now lets see how we can fix it... Turn it off (Keep power pressed for about 5 seconds) and take out the sdcard, put it in your PC.
It's getting messy now, so grab a beer and let's go:
Open a Terminal on your linux computer.
Code:
#echo "Hello world!"
If your console says "Hello World" you got it. Awesome! =)
Code:
#sudo apt-get install rootstock gparted
This will install rootstock, the tool we're gonna need to create our filesystem, as well as gparted, a tool for partitioning our flash drive. You can also install rootstock-gtk, the graphical version. Try it if you like:
Code:
#sudo apt-get install rootstock-gtk
I heard that ubuntu-netbook won't work because there are drivers missing, would somebody try that and report please?
If your beer is already empty when this is done, you need a faster computer. Tell your wife the guys at xda-developers told you so
Back to the terminal:
Code:
#sudo rootstock -f MyCoolHostName -l myCoolUserName -p myCoolPassword --seed xubuntu-desktop -i 2G --notarball
This will create our filesystem with a user called "myCoolUserName" and (theoretically) his password "myCoolPassword" and install a basic xubuntu-desktop. I had to change the password manually because it didn't work this way... We'll do that later.
Rootstock will download lots of packages (You could also set it up with "--seed ubuntu-desktop", then youll download even more packages or "--seed ubuntu-minimal" or kubuntu... I still didnt find a list of seeds online :-/
The creating will take quite some time, get another beer.
When this is done, you'll get a file like this : "qemu-armel-201104112120.img". We will now mount this image: (make sure the directory /mnt/ does exist and is empty:
Code:
#ls -la /mnt )
Code:
#sudo su
(its simpler to be root for now)
Code:
#mount -o loop qemu-armel-201104112120.img /mnt/
(You are aware that your filename is different, are you? Try this:
Code:
# mount -o loop qemu-armel-*TAB*
and your terminal will automatically fill in your filename. Awesome linux, huh? =)
)
Code:
#cd /mnt/etc/
#mv fstab fstab.bak
#echo "proc /proc proc defaults 0 0" > fstab
#echo "dev /dev tmpfs rw 0 0" >> fstab
Note that the first time we create a file called fstab (echo asdf > fstab), then we add one line to this file (echo asdfasdf >> fstab)
Now we need to copy our wifi-driver over. Remember I told you to write down the directory you put them in? =)
Code:
#cp /home/YourUserName/Desktop/FolioStuff/firmware /mnt/lib/firmware
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK.
Code:
#cd /
#chroot /mnt/
#passwd myCoolUserName
#passwd
#exit
That's it, we're out of the chroot.
It's now time to prepare the SDcard (The steps are the same for a USB Flash drive, I think you'll figure them out.)
Find out how your SDcard can be accessed (You should still be root):
Code:
# fdisk -l
In my card reader, it's "/dev/mmcblk0", it could also be "/dev/sdb1" in your computer.
Now there are two possibilities:
1. You know what youre doing. Then it's easy: You wipe the only partition (or, if there are more than one, the first partition) on your sdcard and format it with ext3:
Code:
#mkfs.ext3 /dev/mmcblk0p1
Note: The device is called /dev/mmcblk0, the partition itself /dev/mmcblk0p1 (Partition 1)
2. You are not sure about this. No problem, start gparted: (as root!)
Code:
#gparted
In the upper right corner, select your flash drive, delete all partitions and create one formatted with ext3. Close gparted.
Mount your freshly created partition somewhere (i chose /mnt2/):
Code:
#mkdir /mnt2/
Code:
#mount /dev/mmcblk0p1 /mnt2
We can now copy our filesystem over. Make sure you use exactly the same flags (rfp for recursive, force, preserve (attributes))
Code:
#cp -rfp /mnt/* /mnt2/
OK, that could work. Unmount the sdcard:
Code:
#umount /mnt2/
Put it in your folio and cross your fingers.
Wifi drivers will be up soon...
It's recommend to add build-essentials to your rootstock image too..
Because then you can easily build the wireless lan drivers on your devices..
Maybe I'll post a howto this afternoon!
Is this Ubuntu really usable (for daily work) with the folio 100 (touch, response speed, ecc.)?
Thanks.
Yup, it's usable for everyday work. It's quite fast on the Folio 100, I've been pretty impressed when I tested it a few weeks ago.
Thanks ph84
It seems most difficult than expected but, great job !
Only i have 1 question, bricking the tablet sounds dangerous... is possible break out the tablet and get a rock?
Thanksss!!!!!
if ubuntu is installed on sd, does that mean that we can dual boot foliomod from nand and ubuntu from sd/usb?
Hm... I'm using Ubuntu 11.04 and I'm getting this error at the end of the rootfs creation :
E: Sub-process /usr/bin/dpkg returned an error code (1)
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
umount2: Dispositivo o risorsa occupata
umount: /tmp/tmp.zaZ1j1Tgt6/tmpmount/proc: device is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
umount2: Dispositivo o risorsa occupata
Click to expand...
Click to collapse
Do you have any idea where I can find the log?
And this procedure will build in the tablet a dual boot? Or dualboot is another procedure?
what is the *.rar????
No it's for singleboot only...
You can only start Ubuntu installed on SD-Card/USB-Stick with this procedure...
I don't know wether the boot-partition is locked when you are booting ubuntu/android..
If not it should be possible to build some applications to flash the boot-partition on the running system to change from ubuntu to android
When I do the rootstock step,I got this error!!!Please help!!!
I: Base system installed successfully.
I: First stage install done
I: Using Chroot for installer
Adding 'local diversion of /usr/sbin/invoke-rc.d to /usr/sbin/invoke-rc.d.rootstock'
Generating locales...
en_GB.UTF-8... done
Generation complete.
Generating locales...
en_US.UTF-8... done
Generation complete.
/bin/installer: line 53: syntax error near unexpected token `+'
E: Second stage build in chroot failed !
E: Please see the log to see what went wrong.
I: Cleaning up...
.....
I: Umounting temporary Image
I: A logfile was saved as //rootstock-201104140706.log
I: Done
Click to expand...
Click to collapse
Could you upload an *.img for us in this forum?
or a databank,etc?
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
sony_tornado said:
what is the *.rar????
Click to expand...
Click to collapse
Nvm, I was talking crap...
schnudergof said:
mhmm it always hangs in the xulrunner configuration.. bahh someone know a solution for this? or does i realy have to chroot the rootfst and install everything manualy =(? Cant find any solution on google for this bug =/
Click to expand...
Click to collapse
Just try rootstock without the parameters on --seed..
Maybe it will work..
You wont have a Desktop Enviroment like Gnome or something but you wont need that for installing the wireless drivers...
And after installing wireless drivers you can install ubuntu-desktop or something with apt-get!
Ok, I have been looking at rootstock, and if you install rootstock-gtk and than click on tasksel there is a whole list of seeds to chose from. I Think im going to try build the netbook build.
On a side note:
We will now do something stupid: We chroot into our arm-based system from an intel-system. But since we're only changing passwords, we should be OK
Click to expand...
Click to collapse
with chroot your only changing the root of your file system, your not running anything from there.
But its its in no way a complaint to your awesome guide! Thanks and keep up the good work!
shidima_101 said:
with chroot your only changing the root of your file system, your not running anything from there.
Click to expand...
Click to collapse
Thats right but when you change your root shell to the rootstock-fs you can also use sudo apt-get update/install and install it into the rootfs!
ph84 said:
Meanwhile, open another terminal. (This is linux! We're gonna multitask since our computer is capable of handling that!) Go to where you stored the attached files, for example
Code:
#cd /home/YourUserName/Desktop/FolioStuff
and unpack them:
Code:
#rar x *.rar
Click to expand...
Click to collapse
Where/what is the "attached files"?
Thanks
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
°EraZoR° said:
Just go to the first page, press STRG+F and type attached into the search window...
I hope you will find the attached files.. Else you dont have to try installing ubuntu on your folio >_<
Click to expand...
Click to collapse
The files I found are only *.zip for update bootloader. Where is *.rar file?
Thanks
Hi all--
I'm sorry in advance for the confusion I might have. I'm an extreme noob when it comes to this platform, and I'm not that great when it comes to Windows either...
Basically I was surprised to see that the external SD Card is used so much by CGM7 and is required for so much. For instance, all downloads HAVE to go to the external card. In addition: I don't know if this has anything to do with operating system, but all saved documents from basically any productivity program seems to save here by default as well.
So here are my questions:
Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used... Does the default location for app installation handle this?
What exactly uses the external card by default?
Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Thanks for your help and suggestions. I am using a gTablet, and I couldn't find a more appropriate forum for this question...
scyld said:
So here are my questions:
1. Is there anyway to alter where things are downloaded to by the built in browser? I'd prefer that internal memory (EMMC, right?) be used.
Click to expand...
Click to collapse
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
2. What exactly uses the external card by default?
Click to expand...
Click to collapse
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
3. Using the built-in file browser, why does it not want me to move items from internal to external storage? Why can I only copy and paste them?
Click to expand...
Click to collapse
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
4. I thought CWM was suppose to look on the external SD card when I use "Install zip from SD card." Instead, it looks at whatever is marked as the internal SD card. Why's that?
Click to expand...
Click to collapse
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
rajeevvp said:
There is a thread just for this at the forum.cyanogenmod.com and also here:
http://forum.xda-developers.com/showthread.php?t=1028305
The last link in the first post does what you want. However, read my warnings if you do switch SD cards using that method:
http://forum.xda-developers.com/showpost.php?p=13569415&postcount=26
Click to expand...
Click to collapse
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Is the question what will use the external SD card, or what is using the external SD card. If it is the latter, Settings > Applications > Manage applications & Storage use has that info.
Click to expand...
Click to collapse
Thanks.
You can move them in the default File Manager. Keep your finger on the filename until a menu pops up. There is a "Move" choice.
Click to expand...
Click to collapse
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this. However, I'm a little worried that it has Super User status, making me worried that I might accidentally do something bad with my clumsy fingers. But I suppose that's why I have CWM backing up my tablet.
Speaking of CWM...
I will have to look into this, but I guess what SD card it uses depends on whether you have an external SD card in the slot or not.
The version of CWM I use, which is Clockworkmod Recovery v2.5.1.3, will use the external SD card by default when installing stuff or when making backups and when restoring, if it detects an external SD card. If one is not detected, then it will use the internal SD card instead for all its actions. See the blog post on the front page of http://bekit.net
Click to expand...
Click to collapse
Interesting, thanks. I unfortunately do not remember which version of CWM I use, but I think it is not this one. I should check it out.
scyld said:
Yep, that's exactly the file I flashed in order to switch what SD card was labelled as "EMMC." Hmm, I suppose I could just move all my apps from the phone to "the external SD card"...
Click to expand...
Click to collapse
Here's my /system/etc/vold.fstab in its entirely. With this, my tablet uses the internal SD card as the default for storage.
Code:
## Vold 2.0 NVIDIA Harmony fstab
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
#dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc0 /devices/platform/tegra-sdhci.3/mmc_host/mmc1
# dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
# dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount emmc /mnt/emmc auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
Pardon, I should have explained: when I do use the default File Manager's "Move" command, I get the message "Could Not Move File" whenever I try to move the file from one storage to the other.
I just downloaded Root Explorer, and it allows me to do this.
Click to expand...
Click to collapse
Ah, OK. The reason for the difference is due to the way the move is actually implemented in File Manager and Root Explorer.
I had an idea about why File Manager couldn't move files across filesystems, and to confirm my suspicion I attached strace to a running File Manager:
Code:
$ su
# strace -e rename -p `pidof org.openintents.filemanager`
Process 28466 attached - interrupt to quit
[I]lots of irrelevant output omitted[/I]
rename("/mnt/sdcard/Kernel/Pershoot/lib-2632.40_gb.tar.gz", "/data/local/tmp/lib-2632.40_gb.tar.gz") = -1 EXDEV (Cross-device link)
[I]more irrelevant output omitted[/I]
File Manager calls the rename() system call to move the lib-2632.40_gb.tar.gz file, which, as the spec says, will fail in this case. The program is then supposed to do the move the old-fashioned way if rename() returns an EXDEV error: copy file1 to file2 by reading bytes from file1 and writing bytes into file2; then delete file1 if the copy is successful.
But, File Manager doesn't perform this very basic fallback step. It throws up its hands at the first error and spits out the error message you got. And, it's not just File Manager. The system mv command (if you have it) in /system/bin also exhibits the same dumb behaviour. The busybox mv is more robust. (You should actually report this as a bug to the File Manager people.)
Which brings us to Root Explorer. I got curious about it after the experiment with File Manager. RE handles cross-device moves just fine. What's more, it also moves entire directory trees across devices. Having written directory tree-moving programs before, I know that this is a non-trivial bit of programming. So, I ran strace on Root Explorer to see how it handled things, and the result made me laugh.
Code:
$ su
# strace -f -e execve `pidof com.speedsoftware.rootexplorer`
Process 3602 attached with 12 threads - interrupt to quit
[I]lots of irrelevant output omitted[/I]
10893 execve("/system/xbin/busybox", ["busybox"..., "cp"..., "-pr"..., "/sdcard/Kernel/Pershoot/lib-2632"..., "/data/local/tmp/lib-2632.40_gb.t"...], [/* 19 vars */] <unfinished ...>
10893 <... execve resumed> ) = 0
10914 execve("/system/xbin/rm", ["rm"..., "-r"..., "/sdcard/Kernel/Pershoot/lib-2632"...], [/* 19 vars */] <unfinished ...>
10914 <... execve resumed> ) = 0
[I]more irrelevant output omitted[/I]
Root Explorer is also taking the easy way out: It's actually using busybox to do (almost) all of its work.
I suspected this when I compiled a new version of busybox a few days ago to test out a new compiler toolchain. I moved the newly compiled busybox into /system/xbin without properly testing it first, and discovered that most of the commands died with segfault errors.
I re-uploaded the working version of busybox back onto the tablet in /mnt/sdcard/download, and then went into Root Explorer to move this busybox into /system/xbin, and RE started force closing on every action. Once I had managed to replace busybox through other means, RE started working fine again. At that time, I didn't look at the issue too closely--I thought it was just another example of the random lossage that Android exhibits from time to time. Now I know why.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DISCLAIMER!
Operations on phone’s partition could be EXTREMALY dangerous.
As You surely expect - I take no resposibility if something will go... not as it supposed to. The responsibility for potential damages caused by using this guide is Yours, and Yours only!
New system partition scheme is “designed” for custom ROMs NOT based on original Samsung firmwares (because of it’s size and using /preload partition, which we intend to extremely resize), to name just a few reasons).
The method of modification is created by @Tesla-MADAL93 from Galaxy Advance sub-forum, all credits should go to him!!! He spend many hours using trials and errors method to achieve final success.
Part ONE: Preparations / theory.
1.Procedure requires any Linux distro with usb connection configured (tested on Ubuntu 12.04 LTS).
2.Working ADB (android debug bridge) – you don’t need to install whole ADK, just adb file with correct path added.
[EDIT/CAUTION]You can use Windows with adb configured, as proven by @maxprzemo, but I wasn’t tested by author of this guide!
3.It is strongly recommended to make a backup of your apps and data before start (using titanium backup or simipar app) Restoring nandroid backup will destroy your new partitions, so don’t use it!!!
4.With this method “safe partiotions” of phone’s eMMC memory are being removed and recreated „safe” using „parted” command in adb shell mode. Some partitions are extremely decreased, one is totally deleted. And the most important – partition of your choice will be expanded. Example displayed below sets internal (DATA) partition as large as possible (almost).
5.You will need external micro SD card after remodelling partitions)
6.Memory swap (SD0 and SD1) required BEFORE first start of your chosen ROM!!!
7.You can restore original partition scheme using Heimdall or Odin (not tested by me, problems with Odin reported by the author of whole modification) with repartition selected.
8.Partition numbers and names are very important (crucial), so we need to create them correctly, setting beginning and the end of each one very carefully.
9.Last important thing! I use minimal gapps pack for every ROM. I didn’t tested if full gapss fit on new /system partition! You’ll have to check it by yourself!
Default partitions and sizes are displayed here:
With this guide you will achieve something like this:
[Side Note: this is just an example – you can make internal card (UMS partition) bigger, leaving /DATA partition intact, just to install bigger games – you’ll have to calculate your own values]
Part TWO: Repartition
OK., let’s do it! You have to perform all steps EXACTLY in described order!
1.Turn phone on in recovery mode, connect it to computer using usb cable.
2.Open terminal / console (Ctrl+Alt+T)
2a. Enter command:
Code:
adb devices
You should see device connected (some numbers and letters)
3.Write (press enter after each command):
Code:
adb shell
su
parted /dev/block/mmcblk0
unit kb
print
You should see default partition scheme (just as one first screen above)
OK., say goodbye to your old partitions. Deleting other partitions could (and probably – will) have irreversible consequences!!
Now we will delete partitions, starting from the last one:
Code:
rm 8
rm 11
rm 9
rm 4
Now you will encounter some error – despite of the unmounting partitions before abovementioned procedure - /cache partition is now mounted. Do not unplug phone, just enter “mount and storage” submenu in recovery, and unmount cache partition)
So let’s continue:
Code:
rm 4
rm 5
rm 3
You just deleted all “safe” partitions, enter to check this:
Code:
print
OK., it’s time to (re)create!
(SYSTEM, partition 3)
Code:
mkpart primary 105906 525906
(CACHEFS, partition 4)
Code:
mkpart primary 3848809 3948809
(DATAFS, partition 5)
Code:
mkpart primary 525906 3848809
(UMS, partition 8)
Code:
mkpart primary 3948873 3948937
(HIDDEN, partition 9)
Code:
mkpart primary 3948809 3948873
Let’s rename them properly (probably you can do it in one mkpart command, but it doesn’t matter):
Code:
name 3 SYSTEM
name 4 CACHEFS
name 5 DATAFS
name 8 UMS
name 9 HIDDEN
Almost done, let’s check:
Code:
print
Nice? Of course it’s nice!!! )
One last thing – we have to make our magic /preload (HIDDEN) partition visible for phone [it won’t boot without it!!] Because recovery won’t format it properly, lets use parted command for a last time (wait after each command):
Code:
mkfs
y
9
ext2
Now you can unplug the phone and format (in recovery) partitions:
/system
/data
/cache
OK, as I said before – you’ll have to switch storages BEFORE using phone again.
For now – you will have to manage it by yourself, just to make it short:
-for 4.2.x ROMs you can use modified vold.fstab file
-for 4.3.x ROMs – you have to manually modify build.prop, or use available zip package that will do it for you (that method is supposed to work with 4.2.x ROMs, but I didn’t test it!)
-I never used any of 4.4.x ROMs, but as I heard, there is method for switching memories too.
WARNING!
I didn’t test the way back to original partition sizes! It was tested by tesla-Madal93 though…
Sometimes (when transfer ring from one android version ROM to other, or using some old version where /preload partition was set as SWAP) you will need manualny format HIDDEN partition, just as shown above:
in adb shell mode:
Code:
parted /dev/block/mmcblk0
Code:
mkfs
y
9
ext2
FINAL WORD: If you are not sure – DON’T DO IT!!!
Screenshots are broken... I assume this deletes the "USB storage"? If then, you and the OP are bosses :good:
I can see the pictures (but are linked from other forum, i'll switch them in future), but yes - it deletes usb storage (ok, not really - new usb storage has 64KB and doesn't have to be even formatted)
Good job !:good:
Personaly i wont do it ever because 1,2 GB is enough, and if i get over that surely i have something on phone that i need to delete because i am not using it
Great post.
I would love to see the same mkpart commands to recover the preload partition space and allocate it to the data partition.
I'll do the full repartitioning thing when the team canjica CM11 major bugs have been solved. I'm not too confident about the other cm11's memory swap sustainability over time
Sent from my GT-I8160 using Tapatalk
I suggest you making script for this, and one script to revert everything like it was before
Rox said:
I suggest you making script for this, and one script to revert everything like it was before
Click to expand...
Click to collapse
I don't know if I can make something as a simple script for recovery (maybe with busybox), but for Linux yes (to automate repartition process). In every case, I will tell/send it to @judas1977 that will provide to update this guide.
@judas1977: Nice work
My new system partition
Made under windows 7
Well done judas77 and Tesla-MADAL93 :laugh:
I'll try to make (semi)automate script for linux terminal in couple of days (unless @Tesla-MADAL93 make this) - then we can have/prepare separate scripts for various partition sizes:
- bigger /DATA
- bigger /UMS (like @maxprzemo did)
- etc...
My partition table (actual formatted sizes 602M /system, 28M /cache, 2150M /data, 761M /sdcard -- no need to swap storage)
3 105906kB 747635kB 641729kB ext4 SYSTEM
4 747636kB 777636kB 30001kB ext4 CACHEFS
5 777636kB 3118935kB 2341299kB ext4 DATAFS
8 3118935kB 3918936kB 800001kB fat32 UMS
9 3918936kB 3948937kB 30001kB ext2 HIDDEN
Original partitions:
Model: MMC SEM04G (sd/mmc)
Disk /dev/block/mmcblk0: 3959423kB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
10 524kB 1573kB 1049kB PIT
6 1573kB 3146kB 1573kB CSPSA FS
7 4194kB 14680kB 10486kB ext4 EFS
2 14680kB 31457kB 16777kB ext4 Modem FS
14 32506kB 34603kB 2097kB SBL
16 34603kB 36700kB 2097kB SBL_2
1 36700kB 53477kB 16777kB PARAM
12 53477kB 55575kB 2097kB IPL Modem
13 55575kB 72352kB 16777kB Modem
15 72352kB 89129kB 16777kB Kernel
17 89129kB 105906kB 16777kB Kernel2
3 105906kB 747635kB 641729kB ext4 SYSTEM
5 747635kB 2056258kB 1308623kB ext4 DATAFS
4 2056258kB 2377122kB 320864kB ext4 CACHEFS
9 2377122kB 2712666kB 335544kB ext4 HIDDEN
11 2712666kB 2765095kB 52429kB Fota
8 2765095kB 3948937kB 1183842kB fat32 UMS
Minimum sizes and warnings
/system 530M (approximate value, calculated for CM10.2 + my gApps) (10MB margin)
/cache 8M (assuming dalvik.vm.dexopt-data-only=1 && dalvik.vm.dexopt-cache-only=0) (2MB margin)
/data 350M (assuming about 100M of actual usable app space) (20MB margin) -- in practice less than 600 will be quite tight
/sdcard 1M (depends on apps again and FAT fragments easily by design, avoid less than 100M)
Now what should be nice having are ROM variants with internal storage disabled, so that we can remove partition 8 and both bypass the need for storage swapping but also avoid some apps not desiged for 2 "SDs" getting partially broken
I just repartitioned my phone, but acidentally I partitioned partition 2 instead of 3 :/
Now when I try to rename the partition 2 again in "Modem FS" with the name command, it only names the partition as "Modem". Can someone explain me please how to rename it to the original name again?
Thank you
S.AMU said:
I just repartitioned my phone, but acidentally I partitioned partition 2 instead of 3 :/
Now when I try to rename the partition 2 again in "Modem FS" with the name command, it only names the partition as "Modem". Can someone explain me please how to rename it to the original name again?
Thank you
Click to expand...
Click to collapse
Try "Modem FS" with quotes, or maybe Modem\ FS
Ryccardo said:
Try "Modem FS" with quotes, or maybe Modem\ FS
Click to expand...
Click to collapse
renaming worked with the quotes. Thanks
I restored my old nv_backup and now the device is booting... Let's see if it will work. I'm just confused, because in recovery the partition is called modemfs and when restoring nv backup it is called Modemfs....
botid said:
Great post.
I would love to see the same mkpart commands to recover the preload partition space and allocate it to the data partition.
Click to expand...
Click to collapse
Impossible (well, without LVM or something) because there's USB storage in the middle... but with 10 minutes and a calculator you can create your partition sizes relatively easily
If I'll make the following changes in partitions: UMS resize to 400MB, CACHEFS resize to 30MB, DATAFS resize to 2,313GB, Fota 0 MB and I'll leave SYSTEM and HIDDEN to default sizes can I restore CWM Recovery backup or flash stock rom with Odin?
The HIDDEN partition will have the same size, but the location on mmc is different, as you can see below.
3 105906kB 747635kB 641729 kB ext4 SYSTEM
5 747635kB 3173073kB 2425438kB ext4 DATAFS
4 3173073kB 3203793kB 30720 kB ext4 CACHEFS
9 3203793kB 3539337kB 335544kB ext2 HIDDEN
8 3539337kB 3948937kB 409600KB fat32 UMS
Sorry for my english.
powermetza said:
If I'll make the following changes in partitions: UMS resize to 400MB, CACHEFS resize to 30MB, DATAFS resize to 2,313GB, Fota 0 MB and I'll leave SYSTEM and HIDDEN to default sizes can I restore CWM Recovery backup or flash stock rom with Odin?
The HIDDEN partition will have the same size, but the location on mmc is different, as you can see below.
3 105906kB 747635kB 641729 kB ext4 SYSTEM
5 747635kB 3173073kB 2425438kB ext4 DATAFS
4 3173073kB 3203793kB 30720 kB ext4 CACHEFS
9 3203793kB 3539337kB 335544kB ext2 HIDDEN
8 3539337kB 3948937kB 409600KB fat32 UMS
Sorry for my english.
Click to expand...
Click to collapse
Nandroid: I wouldn't personally do it but it should work
Odin: definitely repartition with PIT and full image first
And be sure to input the partitions in numerical order!
You can make a script? For linux and winzozz?
Sent from my GT-I8160 using XDA Premium 4 mobile app
Don't make CACHEFS partition under a minimum 100 MB!!!
In this partition is stored system apps' dalvik cache on all CM and CM-based ROMs, if available space is insufficient to store dalvik cache of all system apps the ROM isn't stable and has lot of FCs depending on what caches are not stored. If you want to go under 100 MB (that I advice) first check actual used space on this partition with Partition Table (available on Play Store) on your ROM, remember that every ROM has its system-dalvik cache size depending from apps' classes.dex
Inviato dal mio GT-I9070
Tesla-MADAL93 said:
Don't make CACHEFS partition under a minimum 100 MB!!!
Click to expand...
Click to collapse
And why?
I've had zero problems in Android with 10 MB as long as you keep dalvik-cache away from it ( dalvik.vm.dexopt-data-only=1 and …cache-only=0)
Recovery probably uses it more though...
Ryccardo said:
And why?
I've had zero problems in Android with 10 MB as long as you keep dalvik-cache away from it ( dalvik.vm.dexopt-data-only=1 and …cache-only=0)
Recovery probably uses it more though...
Click to expand...
Click to collapse
In this way is okay, but not all people know this I think. Should be added to first post @judas1977
Inviato dal mio GT-I9070
Just tried to install Remix OS on my old laptop for a windows 10 and remix OS dual boot. It was stuck at detecting android-x86 with a flashing gray background with white text (sorry I don't have pic).
Decided to boot back to windows 10 and tried to fix it; however, now the installation tools keep saying :
"Windows cannot find 'R:\RemixOS\UninstallRemixOS.exe'. Make sure you typed the name correctly, and then try again."
I tried to go into the regedit to find the key (HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\remixos), but the only thing that was under Windows was the office, nothing about CurrentVersion.
Can someone help?
Btw my old laptop runs nvidia ion, tried adding the line with i915 or something but that didn't get it to boot into remix.
Me too i faced this problem, i fix by another installer, type on google "Android x86 installer"
Sent from my GT-I8190 using Tapatalk
To get rid of it manually you can simply delete the files in the RemixOS folder and deleting the boot entry via EasyBCD.
Sent from my iPhone using Tapatalk
Does anyone know how to execute UninstallRemixOS.exe?
The only way I can see the file UninstallRemixOS.exe is using the minitool partition wizard. I open the MiniTool Partition Wizard, arrow down to my *:REMIXOS partition, then click on "Explore Partition", then expand my RemixOS folder. This folder has three folders (EFI, BOOT, and .disk) along with 18 files, one of which is UninstallRemixOS.exe. Unfortunately no file execution or file editing can be done from within MiniTool Partition Wizard. So I can see the file is there, but I have no idea how to execute it. Does anyone know how to execute UninstallRemixOS.exe?
I cannot see the *:REMIXOS partition in an elevated command prompt using the >mountvol X: /s, only the ESP partition (volume) shows up, which is also shown by the MiniTool partition Wizard. One unusual thing when using the mountvol command is that substituting any * drive letter (e.g. mountvol h: /s) gives me the same exact result: Volume in drive * is ESP. The "volume" is always ESP, and whichever drive letter used in the mountvol command, there are only two directories (EFI and boot) and an executable batch file named setenv.bat. One convenience with the mountvol procedure is being able to edit the grub.cfg file located in the X:\EFI\RemixOS\ folder using notepad. Always unmount whatever volume that was mounted with the "mountvol <drive-lettet> /s" command. I just type C: at the command prompt, then type the command,
C:\Windows\System32>mountvol X: /d
---------- Post added at 05:06 PM ---------- Previous post was at 05:00 PM ----------
Have to thank @HypoTurtle for suggesting MiniTool Partition Wizard. :good:
@namitutonka - have a look for assign or change drive letter in minitool for the *:REMIXOS partition
This is the solution to both find and execute uninstallremixOS.exe
HypoTurtle said:
@namitutonka - have a look for assign or change drive letter in minitool for the *:REMIXOS partition[/QUO
@gary93, @Xkirnel99, @putr4s. @HypoTurtle has solved this completely. Within MiniTool I highlighted *:REMIXOS then chose "change letter" and arbitrarily assigned it the letter R:.
RemixOS still successfully starts, and when booted into Windows10 drive R: with volume label REMIXOS shows up in explorer where every file can either be edited or executed with ease.
If any one does execute UninstallRemixOS.exe please leave feedback.
Click to expand...
Click to collapse
namitutonka said:
HypoTurtle said:
@namitutonka - have a look for assign or change drive letter in minitool for the *:REMIXOS partition[/QUO
@gary93, @Xkirnel99, @putr4s. @HypoTurtle has solved this completely. Within MiniTool I highlighted *:REMIXOS then chose "change letter" and arbitrarily assigned it the letter R:.
RemixOS still successfully starts, and when booted into Windows10 drive R: with volume label REMIXOS shows up in explorer where every file can either be edited or executed with ease.
If any one does execute UninstallRemixOS.exe please leave feedback.
Click to expand...
Click to collapse
While your at it check if you have that 16mb unallocated space. Of you do, format it to fat16 copy over the remix files from efi/esp and you won't need to bother wirh mountvol again
Click to expand...
Click to collapse
HypoTurtle said:
namitutonka said:
While your at it check if you have that 16mb unallocated space. Of you do, format it to fat16 copy over the remix files from efi/esp and you won't need to bother wirh mountvol again
Click to expand...
Click to collapse
@HypoTurtle
The copy operation involved a restart since original ESP volume is active. The volume is fat32 just under 500Mb with just over 60Mb used. Copy by minitool is allowed only into an unallocated unformatted partition, I created a 1.7Gb unallocated partition, after restart the original and the copy were both the exact size 500Mb fat32 partitions with leftover unallocated partition space. The copy's status is 'boot' while the original ESP volume remains active. Assigning a drive letter to the copy makes it visible in windows.
Still I would think the use of mountvol upon the active partition would be necessary to edit the grub.cfg file with notepad within an elevated command prompt. That is unless (with a restart) the active ESP volume could be deleted and my new readable/writable windows Drive H: could sucessfully dual boot the PC. If so I would also think my new boot partition (drive H, if it does boot, would change it's status from boot to active. Back to either mountvol or rebooting MiniTool copy/restart procedure.
Click to expand...
Click to collapse
namitutonka said:
HypoTurtle said:
@HypoTurtle
The copy operation involved a restart since original ESP volume is active. The volume is fat32 just under 500Mb with just over 60Mb used. Copy by minitool is allowed only into an unallocated unformatted partition, I created a 1.7Gb unallocated partition, after restart the original and the copy were both the exact size 500Mb fat32 partitions with leftover unallocated partition space. The copy's status is 'boot' while the original ESP volume remains active. Assigning a drive letter to the copy makes it visible in windows.
Still I would think the use of mountvol upon the active partition would be necessary to edit the grub.cfg file with notepad within an elevated command prompt. That is unless (with a restart) the active ESP volume could be deleted and my new readable/writable windows Drive H: could sucessfully dual boot the PC. If so I would also think my new boot partition (drive H, if it does boot, would change it's status from boot to active. Back to either mountvol or rebooting MiniTool copy/restart procedure.
Click to expand...
Click to collapse
Just the efi/RemixOS folder from X:/ which should only be a couple mbs is needed.
Click to expand...
Click to collapse
HypoTurtle said:
namitutonka said:
Just the efi/RemixOS folder from X:/ which should only be a couple mbs is needed.
Click to expand...
Click to collapse
@HypoTurtle , OK I've got to find a more appropriate thread to discuss grub.cfg file locations as applied to RemixOS, besides many other files. There literally are dozens of XDA threads with grub.cfg in them. And to think that getting a handle on this file is a miniscule tip of the RemixOS iceberg.
I will search and learn while wading through dozens of XDA threads. I will find which file location edit of grub.cfg affects both the boot sequence and if such edits affect the other grub.cfg files. Maybe RemixOS does something on shutdown to check core file changes and implements those changes into the next cold boot.
These are my file locations:
C:\REMIXOS\RemixOS\boot\grub\grub.cfg
C:\ESP\EFI\RemixOS\grub.cfg
C:\ESP\boot\grub\grub.cfg
Sorry for beginning to threadjack here @gary93. Thanks @HypoTurtle :good:
Click to expand...
Click to collapse