Related
Install Uruk 0.3 on second internal flash disk of Archos
UPDATE
At the last end of this guide you will find the steps necessary to upgrade to Uruk 0.6 from Uruk 0.3 or 0.4.
Near the end of this guide you will find the steps necessary to upgrade to Uruk 0.4.2 from Uruk 0.3 or to install it for the first time.
Please note.
If you are upgrading from Uruck 0.3 to 0.4.2 and installed google market hack before upgrade, after upgrade the market will be broken. To solve the problem reed the last step of this guide.
I've manage to boot from the second partition of the second internal flash of 8GB (/dev/block/mmcblk1p2) of my Archos 70IT Urukdroid vers 03 prepared by $aur0n on this post.
Thanks $aur0n for your awesome work.
It may work for other archos generation 8 too, except Archos 70 IT 250GB (i think that model doesn't have a second internal flash disk to boot from for SDE, but the owners can do it creating the 2 needed partitions on the HDD).
I've done it because:
- my micro sdcard is slow compared to internal flash
- i can mount correctly micro sdcard and second internal flash disc in Windows and linux by connecting Archos via USB and
- my sdcard is free. I can boot without sdcard in, take off from archos every time i want and upload files from a card reader or connecting the archos 70 via usb.
If you want to try it, be sure on what you are doing (linux knowledge is needed).
Try it on your own risk.
I don't have any responsibility if you brick your device (actually is hard to brick it following the guide, but pay attention please).
So if you are sure, read carefully this post and ask before if something is not clear enough for you.
I will try to answer as soon as possible (I'm actually a bit busy :-()
First of all install SDE, if you haven't already done (you can get information about it and download the SDE firmware from archos web page archos web page
Attention: Doing that You void your warranty...
Here the Archos notes:
Important notices to be acknowledged before downloading and installing the SDE firmware:
Once the SDE firmware is installed on a device, this device will be watermarked and ARCHOS will be able to detect that this firmware has been installed once.
Installing the SDE firmware is considered by ARCHOS as a voiding of the warranty and ARCHOS declines all liability and responsibility for any issues resulting from the installation of this SDE firmware.
ARCHOS strongly advises that only experts in embedded software development should install this firmware.
This firmware is provided "as is" and is not supported by ARCHOS.
Before following the steps required to install Uruk 0.3 some clarifications:
What you need to have:
- Archos 70 IT with terminal and SDE installed.
- Linux machine (nativly, visualized or LiveCD)
- Optionally Windows PC
Storage map of Archos 70 IT:
a) The first internal flash disk is of approximately 500MB (device /dev/block/mmcblk0) which is used by stock archos firmware and not changed by this guide.
Pay great attention playing with it, you may brick forever your Archos.
This flash disk have 4 partition and the block devices, mountpoints, filesystems type and size are as the following:
The first devices is "/dev/block/mmcblk0p1", mountpoint "/mnt/rawfs", type of filesystem "rawfs", size 32MB
The second devices is "/dev/block/mmcblk0p2", mountpoint "/mnt/system", type of filesystem "ext3", size 119MB
The third devices is "/dev/block/mmcblk0p3", mountpoint "/cache", type of filesystem "ext3", size 30MB
The fourth devices is "/dev/block/mmcblk0p4", mountpoint "/data" (mountpoint only by archos firmware), type of filesystem "ext3", size 300MB
b) The second internal flash disk is of approximately 7,5GB (device /dev/block/mmcblk1) which is used by this guide to boot SDE from and to accommodate the /data mountpoint (not any more on the "/dev/block/mmcblk0p4").
By stock archos firmware it has 1 partition (device /dev/block/mmcblk1p1), mountpoint "/mnt/storage", type of filesystem "fat32", size 7,5GB
After Uruk 0.3 installation it will have 3 partitions and the block devices, mountpoints, filesystems type and size will be as the following:
The first devices will be "/dev/block/mmcblk1p1", mountpoint "/mnt/storage", type of filesystem "fat32", size 5,5GB
The second devices will be "/dev/block/mmcblk1p2", mountpoint root "/", type of filesystem "ext4", size 500MB
The third devices will be "/dev/block/mmcblk1p3", mountpoint "/data", type of filesystem "ext4", size 1GB
C) The sdcard on device /dev/block/mmcblk2. On my case it have 1 partition (device /dev/block/mmcblk2p1), mountpoint "/mnt/storage/sdcard", type of filesystem "fat32".
Let's go:
The first step to do is to backup everything from your second internal flash disk (as above, it has 1 partition formated in fat32, 7,5GB capacity), just for backup purpose.
The simplest way is to connect your archos via usb to your linux box and copy directly that directory to a new directory on your linux with the default graphical file explorer of your distribution.
In my case it mounts automatically to /media/A70S (device is /dev/sdb1):
/dev/sdb1 on /media/A70S type vfat (rw,nosuid,nodev,uhelper=hal,uid=1000,utf8,shortname=mixed,flush)
Click to expand...
Click to collapse
If doesn't mount automatically in your case, find it using "dmesg" command on a terminal after connection complete and mount it manually.
Or you can copy it on your Windows PC (connect Archos via usb, drive mount automatically to A70S).
After backup, don't disconnect your Archos from linux. You have to resize the mounted Archos disk form 7,5GB to 5,5GB.
The easiest way is to do it graphically with your distribution partition manager utility.
First umount it by right click->umount, then resize it letting on the right side of the disk 1,5GB free space.
Create other 2 partition on that free space, first of 500MB and the other with the remaining space approx. 960MB.
Then apply the changes on the partition manager and you will have now 3 partition on the second internal flash disk of your Archos.
The first one with 5,5GB and formated on fat32, the second one 500MB not formated and the third partition of 960MB not formated.
On my case the devices are respectively /dev/sdb1, /dev/sdb2 and /dev/sdb3.
The next step is to format the second and third partition with ext4 filesystems without huge option (as from $aur0n post) on a linux terminal as root:
mkfs.ext4 -O ^huge_file /dev/sdb2
mkfs.ext4 -O ^huge_file /dev/sdb3
Click to expand...
Click to collapse
When finished, just remove safely archos from your linux box.
From the archos open a terminal and just type:
ls /dev/block/mmcblk1*
Click to expand...
Click to collapse
The result will be:
/dev/block/mmcblk1 /dev/block/mmcblk1p1 /dev/block/mmcblk1p2 /dev/block/mmcblk1p3
Click to expand...
Click to collapse
The second partition (/dev/block/mmcblk1p2) will be your new rootfs
and the third one (/dev/block/mmcblk1p3) your new application area (/data).
On this step you are going to copy all the staff on /data (device /dev/block/mmcblk0p4 mounted on /data)
to the third partition of the second internal flash (/dev/block/mmcblk1p3).
Mount the third partition first:
mkdir /tmp/data
mount /dev/block/mmcblk1p3 /tmp/data
Click to expand...
Click to collapse
and copy:
cp -rp /data/* /tmp/data
sync
umount /tmp/data
Click to expand...
Click to collapse
If you get any problems on coping (permissions) then the only way to do it correctly is to use "tar" to make a archive of data to a file on the first partition of the second internal flash disk (/dev/block/mmcblk1p1 mounted on /mnt/storage) like:
tar -cfvz /mnt/storage/data_app.tar.gz /data/
Click to expand...
Click to collapse
and then connect archos via usb to your linux computer (your three partition of the internal flash now will mount in automatic, let say /media/A70S, /media/disk1 and /media/disk2 from the devices /dev/sdb1, /dev/sdb2 and /dev/sdb3)
Now you have to extract the previous tar file (data_app.tar.gz) to the /media/disk2 (the third partition of archos internal flash disk mounted supposedly at /media/disk2):
cd /media/disk2
tar -zvxf /media/disk1/data_app.tar.gz
sync
umount /media/disk2
Click to expand...
Click to collapse
The next step, download the Uruk 0.3 version of rootfs (rootfs.tar.gz) from this link, and kernel image (zImage) from from this link on the /tmp directory of your linux box. I want to remember that this files are prepared and postet from $aur0n on this post.
If you are still connected via usb with your archos (if not, connect it),extract the rootfs (rootfs.tar.gz) directly on the mount point of the second flash partition (as above in my case is /dev/sdb2 mounted on /media/disk1) on linux:
cd /media/disk1
tar -zvxf /tmp/rootfs.tar.gz
Click to expand...
Click to collapse
Change the following lines of the init.rc file (mount point of root filesystem):
mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid
# Uncomment this
# mount ext4 /dev/block/mmcblk2p2 /data noatime
with those:
#mount ext3 /dev/block/mmcblk0p4 /data noatime nosuid
# Uncomment this
mount ext4 /dev/block/mmcblk1p3 /data noatime
Change the line on the file/media/disk1/syste/etc/vold.fsatb:
#dev_mount_lun volume_sdcard /mnt/storage/sdcard 3 /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk2p3
with that:
dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk2
sync
umount /media/disk1
Click to expand...
Click to collapse
and remove safely archos from the linux box and shutdown Archos.
Download the initramfs.cpio.gz_Uruk_0.3.zip from here (or from the attachment on the end of this post) and unzip it on the /tmp folder of you linux box.
Flash the initramfs.cpio.gz and zImage (remember , you downloaded zImage on the step 4 and placed it already on /tmp) on SDE environment doing:
- While power on your archos, press the "Volume -" button
- Go to "Recovery System",then "Developer Edition Menu"
- Select "Flash kernel and Initramfs".
- Attach your Archos via USB to linux computer. Archos will automatically mount, in my case is A70S_REC mounted on /media/A70S_REC/. Copy the files (initramfs.cpio.gz and zImage) from /tmp folder.
cp initramfs.cpio.gz zImage /media/A70S_REC/
Click to expand...
Click to collapse
Disconnect safely archos, then push "Ok", power and the archos will reboot.
- Press the "Volume -" to boot to the ""Boot Menu" and choose "Developer Edition" or just while booting press both "Volume -" and "Volume +" to boot directly to the "Developer Edition".
You are done.
Enjoy booting from internal flash (SDE edition).
Update: Uruk 0.4.2
There are 2 possibilities:
- You want to upgrade from Uruk 0.3
- Install Uruk 0.4.2 for the first time (You are on stock archos firmware).
Let's begin with the upgrade from Uruk 0.3 to Uruk 0.4.2
First of all download the Uruk 0.4.2 rootfs prepared from $aur0n UrukDroid-0.4.2-rootfs.rar on your linux box.
Download also UrukDroid-0.4.2-kernel.rar from here (or from the attachment on the end of this guide).
It's is $aur0n's one with the modifications to boot and mount /data from second internal flash.
Copy the above 2 files on the folder /tmp/archos of your linux machine. In my case is the 2 downloaded files are
under /home/shklifo/Download folder:
mkdir /tmp/archos
cd /tmp/archos
cp /home/shklifo/Download/UrukDroid-0.4.2-kernel.rar /home/shklifo/Download/UrukDroid-0.4.2-rootfs.rar .
Click to expand...
Click to collapse
Unrar both of them (if you don't have rar utility, just install it), giving the command:
rar x UrukDroid-0.4.2-kernel.rar
rar x UrukDroid-0.4.2-rootfs.rar
Click to expand...
Click to collapse
When the unrar process goes ok you will see the following on terminal (example of UrukDroid-0.4.2-kernel.rar):
[email protected]:/tmp/archos# rar x UrukDroid-0.4.2-kernel.rar
RAR 3.90 beta 2 Copyright (c) 1993-2009 Alexander Roshal 3 Jun 2009
Shareware version Type RAR -? for help
Extracting from UrukDroid-0.4.2-kernel.rar
Extracting zImage OK
Extracting initramfs.cpio.gz OK
All OK
Click to expand...
Click to collapse
After that you will have the following files on /tmp/archos:
[email protected]:/tmp/archos# ls -lrt
totale 245668
-rw-r--r-- 1 root root 0 2011-01-17 12:10 UrukDroid-copy_data.cmd
-rw-r--r-- 1 root root 120854073 2011-01-21 17:34 UrukDroid-rootfs-upgrade.tgz
-rwxr-xr-x 1 root root 2255648 2011-01-21 17:57 zImage
-rw-r--r-- 1 root root 1733826 2011-01-22 10:26 initramfs.cpio.gz
-rw-r--r-- 1 root root 119128315 2011-01-22 10:26 UrukDroid-0.4.2-rootfs.rar
-rw-r--r-- 1 root root 3985013 2011-01-22 10:36 UrukDroid-0.4.2-kernel.rar
Click to expand...
Click to collapse
You are upgrading and you have all the applications on second internal flash disk already, so just remove the UrukDroid-copy_data.cmd, you don't need it:
rm UrukDroid-copy_data.cmd
Click to expand...
Click to collapse
Now you have to copy UrukDroid-rootfs-upgrade.tgz to the rootfs of the archos (second partition of the second internal flash disk mounted on / of type ext4 with 500MB space).
To do that just connect archos via usb to your linux box and all the tree partition of archos second internal flash will be mounted automatically.
To verify where those partition are mounted just type:
mount
Click to expand...
Click to collapse
on a linux terminal and on my case is as following:
[email protected]:/tmp/archos# mount
...
/dev/sdb1 on /media/A70S type vfat (rw,nosuid,nodev,uhelper=hal,uid=1000,utf8,shortname=mixed,flush)
/dev/sdb2 on /media/disk type ext4 (rw,nosuid,nodev,uhelper=hal)
/dev/sdb3 on /media/disk-1 type ext4 (rw,nosuid,nodev,uhelper=hal)
/dev/sdc1 on /media/disk-2 type vfat (rw,nosuid,nodev,uhelper=hal,uid=1000,utf8,shortname=mixed,flush)
Click to expand...
Click to collapse
and "df -m" like:
[email protected]:/tmp/archos# df -m
/dev/sdb1 5622 2897 2725 52% /media/A70S
/dev/sdb2 485 244 216 53% /media/disk
/dev/sdb3 973 268 656 29% /media/disk-1
/dev/sdc1 15266 1157 14110 8% /media/disk-2
Click to expand...
Click to collapse
So in my case the second partition of the second internal archos flash disk of 485MB is:
/dev/sdb2 485 244 216 53% /media/disk
Click to expand...
Click to collapse
mounted on /media/disk
Then just copy the UrukDroid-rootfs-upgrade.tgz file on the second partition of the second internal archos flash disk, like in my case:
cp /tmp/archos/UrukDroid-rootfs-upgrade.tgz /media/disk/
Click to expand...
Click to collapse
Safely disconect archos from the linux box and shutdown completely your archos.
Now you have to flash initramfs (initramfs.cpio.gz) and kernel (zImage) to your archos from "Recovery Menu" (you know already how to do it),
or if you forget it just do the following:
- While power on your archos, press the "Volume -" button
- Go to "Recovery System",then "Developer Edition Menu"
- Select "Flash kernel and Initramfs".
- Attach your Archos via USB to linux computer. Archos will automatically mount, in my case is A70S_REC mounted on /media/A70S_REC/. Copy the files (initramfs.cpio.gz and zImage) from /tmp/archos folder.
cp initramfs.cpio.gz zImage /media/A70S_REC/
Click to expand...
Click to collapse
Disconnect safely archos, then push "Ok", power and the archos will reboot.
- Press the "Volume -" to boot to the ""Boot Menu" and choose "Developer Edition" or just while booting press both "Volume -" and "Volume +" to boot directly to the "Developer Edition".
You will see the UruckDroid 0.4 screen with "Initramfs: Loading ...." than Rootfs: Loading .... and finally you will see the Uruck Desktop.
Enjoy
Install Uruk 0.4.2 for the first time
For those who whant to install Uruk 0.4.2 for the first time (now it's simplier that Uruk 0.3) will do:
a) First backup, create the partitions and filesystems on the second internal flash disk of archos (step 1
and step 2 of the Uruk 0.3).
You don't need anymore step 3 (copy of /data folder), because Uruk 0.4.2 do it automatically.
b) Then following step by step the guide Let begin with the upgrade from Uruk 0.3 to Uruk 0.4.2, except removing UrukDroid-copy_data.cmd file, because you need it to copy automatically /data files.
When you are on the step "copy the UrukDroid-rootfs-upgrade.tgz file on the second partition of the second internal archos flash disk", you need to copy additionaly UrukDroid-copy_data.cmd like:
cp /tmp/archos/UrukDroid-rootfs-upgrade.tgz /media/disk/
cp /tmp/archos/UrukDroid-copy_data.cmd /media/disk/
Click to expand...
Click to collapse
Than follow till the end the guide Let begin with the upgrade from Uruk 0.3 to Uruk 0.4.2.
Enjoy
OPTIONAL: Install google market.
If you have already istalled google market (using gAppsInstaller for example), you have to uninstall it (market/vending) first.
Then download UrukDroid-0.4.2-GoogleMarket.zip and copy it on the root (/) filesystem of archos (see above on the upgrade section an do the same steps of copying UrukDroid-rootfs-upgrade.tgz to archos rootfs).
Reboot archos.
NOTE
If you are upgrading from 0.3 version to 0.4.2 and installed before the google market from kenyu73 like i did, then the market will be broken and doesn't work any more.
To get it back, you have to remove all the google applications from SDE (Uruk 0.4.2) including the kenyu73's installer (gAppsInstaller).
Then install the market as on the previuos step OPTIONAL: Install google market downloading the file UrukDroid-0.4.2-GoogleMarket.zip and following the instructions.
After rebooting archos on SDE, you need to fix it, because you can't access the whole market (missing some "protected applications" like copilot etc).
To fix just do the following steps as kenyu73 explain on his post :
Go to Settings-->Manage Applications-->All-->Market (Clear Cache then 'Force Stop', DO NOT clear data).
Setting-->Manage Applications-->All-->Google Services Framework (Clear data then 'Force Stop').
Reboot.
Click to expand...
Click to collapse
I've done it twice the fix step, and after that no problem anymore. All the google applications (downloaded from the fresh working market) are working correctly as before.
Update: How to upgrade to Uruk 0.6 from Uruk 0.3 or 0.4.2
There are 2 possibilities:
a) The first one is the simplest one.
Just download the $auron Uruk 0.6 UrukDroid_0.6-EasyInstall.rar posted on this post, extract it on your computer and delete the file initramfs.cpio.gz, because we don't need it.
Then download the file initramfs.cpio_Uruk_0.6.gz.rar in attachment on the end of this post and extract it on the same directory of your computer (this is the initramfs that you will flash on SDE prepared from $auron and can be found on the /root/ directory of $auron new rootfs UrukDroid-install.tgz).
Then boot Archos on stock Android and connect it to your linux box via USB. The root filesystem of Archos (/dev/block/mmcblk1p2 on Archos) will be mounted on some directory on linux automatically, just find it or manually mount it (it's the filesystem with 500MB space, to be sure just type "df -h" on a terminal).
With root on a linux terminal go to that directory (in my case was /media/Disk-1) and remove all the files there:
Code:
rm -rf *
Then copy the UrukDroid-install.tgz extracted before from UrukDroid_0.6-EasyInstall.rar on the above directory.
So, you will have only the file UrukDroid-install.tgz on your rootfs directory of Uruk.
Then disconect safely Archos from your linux box and flash initramfs.cpio.gz and zImage files on SDE (you know how to do that ...) and boot to SDE.
That is
Uruk 0.6 will automatically copy everything needed as you will see on the boot time.
You have to do a last thing to be able to mount automatically the sdcard on Uruk 6. Uncomment the sdcard line on the file /system/etc/vold.fsatb like:
Code:
dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk2
This is needed on the second method too (the one below).
Who want to install Uruk (version 0.6 in this case) for the first time on internal, must create and format the 2 partitions of the second internal flash disk (like on the beginning of this post described) and follow step by step the above method and at the end copy everything from the data partiotion (last partition of the first internal flash /dev/block/mmcblk0p4) to the third partition of the second flash disk (/dev/block/mmcblk1p3).
b) The second method is more complicated, but works also good.
You just install Uruk 0.6 to a sdcard like on this $auron post, than shutdown Archos, put the microsd card on a card reader connected to a linux PC and with root make a tar archive of the entire rootfs (root filesystem) of Uruk 0.6 (the second partition of the sdcard with 500MB of space on ext4 filesystem) to a tar file that you can put to the first partition of the sdcard (the fat partition of the sdcard).
Eject the sdcard and put on Archos. Turn on Archos and from a terminal on Uruk as root mount the second partition of the flash disk (/dev/block/mmcblk1p2) on a directory and just delete ("rm -rf") everything on there and then extract the tar archive there.
So, you just put everything from rootfs of the sdcard to internal flash, with correct permissions, timestamp, ownership etc.
Now just shudown Archos, take off the sdcard and boot.
This time it will Uruk 0.6 will boot from internal flash
Enjoy it
I wish I could understand more clearly how to do this with a fresh install...
This is what I am looking to do, using it on internal... but this might be a little too complicated for me.
What about 101?
Does this method applicable to Archos 101 model too?
If someone already have been tried it on 101, please reply with details here, if any troubles you have after installation or any changes need to be done.
Also I am curious about does anyone have tried to connect USB thumb drive to the tablet with modified rom and root access? Do we still have any issues with USB drive recognition?
Is this applicable for UrukDroid 4.1 and The Archos IT 35?
well great work but i dont know if i get it to work and Im a little bit confused -
is it writable in windows per media player (mtp) or per explorer or both (with ext-x driver)?
yura-a said:
Does this method applicable to Archos 101 model too?
If someone already have been tried it on 101, please reply with details here, if any troubles you have after installation or any changes need to be done.
Click to expand...
Click to collapse
Why not. The 101 model have the second internal flash (8 or 16GB) as the 70 S model have. To be sure just type mount and df -m on a terminal in Archos device and you will see the flash drive (/dev/block/mmcblk1p1) formated in fat32 and mounted on /mnt/storage.
I only changed the mounting point on the file init, init.rc and /system/etc/vold.fstab from $aur0n files to be able to boot SDE from the second internal flash disk and doesn't change anything else, configuration file of specific model included.
yura-a said:
Also I am curious about does anyone have tried to connect USB thumb drive to the tablet with modified rom and root access? Do we still have any issues with USB drive recognition?
Click to expand...
Click to collapse
I'm still excpecting my host cable from Hong-Kong and can't try that, but i think will not be a problem.
good work
thanks
svennimann said:
Is this applicable for UrukDroid 4.1 and The Archos IT 35?
Click to expand...
Click to collapse
I do not own your device (it is a Archos 32 IT?), but if is that model, it got a 8GB internal flash like archos 70 IT. The firmware is the same for all archos generation 8 devices (with same configuration files change), but i haven't change them (and $aur0n too i think, but he can answer himself).
So just try it, if you have no problem of understanding all the steps on the first post. You can't break anything. And if it will not work (worse case) or have other problems you just have SDE installed (you can remove it if you want) and 2 more partition on the internal flash disk with some files on them.
You can just delete the partitions and risize (increment) the first partition as from stock. In all situation we are able to boot to stock firmware.
I only change the mountpoints as i wrote in the previous posts on the files init, init.rc and vold.fstab from uruk 0.3.
So mine and $auron solution changed only on the boot partition (mine is booting form the second partition of the internal flash disk, him from the second partition of sdcard) and the application data partition (mine on the third partition of the internal the flash, him on the third partition of the sdcard). All the other files are from him (thanks $aur0n).
I've not installed yet the 0.4.1, i got little free time actually and of the market problem (if i install the 0.4.1, i must uninstall the market on stock firmware and will be not able to access it from original/stock firmware).
But if i decide to install it, i will report here.
svennimann said:
well great work but i dont know if i get it to work and Im a little bit confused -
is it writable in windows per media player (mtp) or per explorer or both (with ext-x driver)?
Click to expand...
Click to collapse
Thanks, as i say above you don't loose anything trying to install it, only time
So, if i understand well your question, on my archos i'm able to access the first partition of the flash disk (it's a fat32 as from stock, only risezed in 5,5 GB) on my windows XP PC by usb connection to archos.
The second (boot partition 500MB) and the third (data application area of 1GB) partitions of internal flash disk are ext4 formated (stock ext3) and can't be mount on a windows PC, and for me have any sense mounting them on a PC.
The sdcard is accesible via usb connection (archos to PC) or via card reader. If you format it fat32 is in r/w mode (as i've done), ext3 or ext4 in readonly mode i think (not yet tried), because actually isn't out a driver to be able to write a linux partition on Windows.
From Ubuntu (connecting archos via usb) i can mount all in r/w mode (all the 3 partitions of the internal flash disk and sdcard too).
Later i will post some picture/command output (mount,ls) from Ubuntu.
In attachment a picture of the flash disk (A70S E: ) and sdcard (Disco rimovibile F: ) on my Windows XP macchine.
{
"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"
}
Just a suggestion.. Please be consistent with your instructions, 1 step your instructions are for linux and the next step would be for archos.
It's really hard to follow what needs to be done or how it should be done properly, considering you're messing around with the internal storage there's bigger chance of bricking your device.
I appreciate all your hard work and contributions here, it's just that it's not that user friendly.
GrandStar said:
Just a suggestion.. Please be consistent with your instructions, 1 step your instructions are for linux and the next step would be for archos.
Click to expand...
Click to collapse
Just to be clear, from archos terminal you have to do only 1 thing, copy or tar the "/data" mountpoint/directory, because this is the 4-th partition of the first internal flash disk (/dev/block/mmcblk0p4) and it can't be mounted on linux via usb connection.
All the other steps are from linux (the first step, you can do it from Windows too).
It's really hard to follow what needs to be done or how it should be done properly, considering you're messing around with the internal storage there's bigger chance of bricking your device.
Click to expand...
Click to collapse
There are 2 internal flash disk in Archos, /dev/block/mmcblk0 of 500MB (used by archos architecture and nobody is touching this flash disk, it's dangerous and you may brick your device) and /dev/block/mmcblk1 of 8GB which is used by the this guide to boot SDE from. So, if you are able to understand what you are doing and don't touch the first flash disk, than nothing can happens.
I appreciate all your hard work and contributions here, it's just that it's not that user friendly.
Click to expand...
Click to collapse
With that i'm in line with your thoughs, thanks. I will try to do it more simple and understandable.
I've followed all the instructions exactly. I'm good with linux, so it wasn't very hard, but when I booted into the Developer Edition at the end, I was at the Initial Setup Screen, like it didn't mount the /data partition. Also, I can't get ES to show the file system, so it doesn't seem to be rooted. Any ideas what's going on?
EDIT: You have a typo in the init.rc the change should be to mmcblk1p3, not mmcblk1p2.
EDIT: Another typo: "dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk1" should be mmcblk2, not 1.
Now my data is there, and I can mount SD cards, but I still can't connect to a computer with a USB cable.
EDIT: All Fixed. I flashed a new kernel from http://forum.xda-developers.com/showthread.php?t=897877 and now have USB Storage working. I used the zImage from ardatdat's kernel with your initramfs.cpio.gz and the changes I listed above. Everything seems to work perfectly, and it's way faster than it was before. I was using Ardatdat's full kernel and booting from internal memory before. When I rotated the screen it used to take almost 10 seconds to update all the icons on the home screen. Now it takes less than 2-3 seconds to update. Great work on the EXT4 conversion! If you'll permit me, I'm going to write up a guide that incorporates my experience, and of course give you full credit.
Update: Just updated to UrukDroid 0.4.1. Needed a little more customization, but usb storage worked with the default 0.4.1 kernel instead of needing ardatdat's kernel. Currently testing to see which is better. Uruk says it's kernel has usb charging enabled, a very exciting possibility, but I kind of doubt it works on the A101IT.
msticninja said:
EDIT: You have a typo in the init.rc the change should be to mmcblk1p3, not mmcblk1p2.
EDIT: Another typo: "dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk1" should be mmcblk2, not 1.
Now my data is there, and I can mount SD cards, but I still can't connect to a computer with a USB cable.
EDIT: All Fixed. I flashed a new kernel from http://forum.xda-developers.com/showthread.php?t=897877 and now have USB Storage working. I used the zImage from ardatdat's kernel with your initramfs.cpio.gz and the changes I listed above. Everything seems to work perfectly, and it's way faster than it was before. I was using Ardatdat's full kernel and booting from internal memory before. When I rotated the screen it used to take almost 10 seconds to update all the icons on the home screen. Now it takes less than 2-3 seconds to update. Great work on the EXT4 conversion! If you'll permit me, I'm going to write up a guide that incorporates my experience, and of course give you full credit.
Update: Just updated to UrukDroid 0.4.1. Needed a little more customization, but usb storage worked with the default 0.4.1 kernel instead of needing ardatdat's kernel. Currently testing to see which is better. Uruk says it's kernel has usb charging enabled, a very exciting possibility, but I kind of doubt it works on the A101IT.
Click to expand...
Click to collapse
Thanks for the corrections (you pay the needed attention), but i just modified the first post radically (easier).
Sure, you can do your own thread with your experience on the installation.
I will install Uruk 0.4.1 too, and update the first post.
WORKING
I had to add a new line into the init.rc file, but afterwards I was able to get Uruk 0.4.1 to boot internal
***mount ext4 /dev/block/mmcblk1p2 / noatime*** - I don't htink you have this in your steps...
After I did this, it works. I also am able to see both the internal and external storage in windows.
I didn't know if you need that line or it was left out of your steps process. All I did to get this to work on an existing 0.4.1 was:
1. Move the data off the internal inside windows to a saved directory on my PC.
2. Partition the 3 partitions like you describe on the internal and formated as you describe...
3. Mount the partitions inside my VMplayer Ubuntu sdb2, sdb3, sdc2, and sdc3 (sdb was the internal formated like you describe and sdc was my 16 0.4.1 SD card fromatted using uruk already)
Su terminal CODE:
$su
***password
#
#cd
#cd /tmp
#mkdir sdb2
#mkdir sdb3
#mkdir sdc2
#mkdir sdc3
#mount /dev/sdb2 /tmp/sdb2
#mount /dev/sdb2 /tmp/sdb3
#mount /dev/sdb2 /tmp/sdc2
#mount /dev/sdb2 /tmp/sdc3
4. Copy through terminal everything from sdc2 --> sdb2 using below code and Copy through terminal everything from sdc3 --> sdb3 using below code
**CODE I used:
#cp -rp /tmp/sdc2/* /tmp/sdb2
#sync
#cp -rp /tmp/sdc3/* /tmp/sdb3
#sync
6. Add in the lines inti init.rc to mount the sdb2, and the sdb3 instead of sdc2 and sdc3
mount ext4 /dev/block/mmcblk1p2 / noatime
mount ext4 /dev/block/mmcblk1p3 /data noatime
7. Add the line into tmp/sdb2/system/etc/vold.fsatb (Which is where I mounted that..)
dev_mount_lun volume_sdcard /mnt/storage/sdcard auto /devices/platform/usb_mass_storage/lun1 /class/block/mmcblk2
**I believe in 0.4.1 it is already like this, so i really made no changes to vold.fsatb....***
Unmounted all 4 I had mounted into /tmp using terminal ubuntu
CODE (I was already inside cd /tmp/sdb2 and i had edited the init.rc and saved it):
#sync
#cd..
#umount /tmp/sdb2
#umount /tmp/sdb3
#umount /tmp/sdc2
#umount /tmp/sdc3
EDIT: after this step, you will need to mount the Archos back into Windows, and copy the files you saved into a folder on your windows PC back into the Internal Fat32 storage. This was why you backed it up in the first place.... You might have to reboot and boot into your stock OS to get the internal to mount back into Windows, i did...
Reboot and go into the developer menu
Reflashed your initramfs and Uruk 0.4.1 Zimage and booted to developers edition...
***Remember this will only work if you have a preexisting 0.4.1 on an SD card where it is formatted with #1 fat32 for dtorage #2 500Mb and #3 1G and it already has been working using $auron's method.
BIG thanks to $aron and shklifo and msticninja... I am very happy using my internal memory to boot with instead of the SD card. i will prob keep the SD card I have and use it whenever I need to boot to SD and just get a different one for Videos and Music.
JW
sublimejosh2000 said:
I had to add a new line into the init.rc file, but afterwards I was able to get Uruk 0.4.1 to boot internal
***mount ext4 /dev/block/mmcblk1p2 / noatime*** - I don't htink you have this in your steps...
After I did this, it works. I also am able to see both the internal and external storage in windows.
I didn't know if you need that line or it was left out of your steps process.
JW
Click to expand...
Click to collapse
I really appreciate your feedback.
But you don't need to add the line:
Code:
mount ext4 /dev/block/mmcblk1p2 / noatime
on the file init.rc, because it is present on the init file included on initramfs.cpio.gz.
If you extract the initramfs.cpio.gz attached on my first post with this command on a shell:
Code:
gunzip initramfs.cpio.gz && cpio -i -d -H newc -F initramfs.cpio --no-absolute-filename
You will find the following line:
Code:
$MOUNT -t ext4 -o noatime,errors=continue /dev/mmcblk1p2 /new-root
To upgrade to $aur0n 0.4.2 now it's really simple.
I'm preparing the new initramfs.cpio.gz. And putting the new rootfs of 0.4.2 on the rootfs of our archos (just to remember it is on the second partition of the second internal disk on device /dev/block/mmcblk1p2 mountet on /) and flashing the new initramfs.cpio.gz and zimage, when booting up on "Developer Edition" it will upgrade automatically.
Is there a reason why we want to be on 0.4.2?
I am not having problems with Market, is there other benifits of this update?
JW
BTW: Thanks for this halp on getting to internal.. I am not sure why we wanted to not do this in the first place.. I guess because some SD cards are faster, mine is working pretty fast and I think the internal is at least class 6
sublimejosh2000 said:
Is there a reason why we want to be on 0.4.2?
I am not having problems with Market, is there other benifits of this update?
JW
BTW: Thanks for this halp on getting to internal.. I am not sure why we wanted to not do this in the first place.. I guess because some SD cards are faster, mine is working pretty fast and I think the internal is at least class 6
Click to expand...
Click to collapse
Just see on the $aur0n post about the new version log change. We will have upgraded module, new wifi, more services like samba sshd etc.
I to havn't any speed problem with internal flash. It is fast enough (with dd copying speed test got till 16 mbit/s write speed) on the internal flash and it is way faster than my sdcard class 4.
0.4.2
Well.. I already reverted back to the origional wifi config file using terminal, and my Market is good to go.
I'm not sure that there are any major differences between 0.4.1 --> 0.4.2
If I am wrong, i think it requires to uninstall all google apps to make that upgrade, which I don't think I need to do.
Am I wrong?
sublimejosh2000 said:
Well.. I already reverted back to the origional wifi config file using terminal, and my Market is good to go.
I'm not sure that there are any major differences between 0.4.1 --> 0.4.2
If I am wrong, i think it requires to uninstall all google apps to make that upgrade, which I don't think I need to do.
Am I wrong?
Click to expand...
Click to collapse
From $auron post on Uruk doesn't seem to be difference between 0.4.1 and 0.4.2, except google applications. With the 0.4.2 you can install the google staff separatly with UrukDroid-0.4.2-GoogleMarket.rar. If you have those apps allready on your 0.4.1 than nothing change, you don't need to upgrade.
Thanks and no problem with your methods.
My 16GB microSD card isn't very good and boot / use of archos 101 is very slow with Uruk0.4.2 installed on external SD.
Now it's fast installed on internal SD...
Maybe this help:
if can't mount ext4 partition on your linux box, you can do:
tune2fs -E test_fs /dev/sdbx (sdb2 for instance)
and then:
mount -t ext4dev /dev/sdbx /mnt/sdcard
trouble with fresh install for 0.4.2 $auron....
I was able to create 3 partition internally (sdb1(vfat), sdb2(ext4), sdb3(ext4))
I was able to move rootfs and cmd script to sdb2
I was able to flash initramfs and zImage
But I'm stuck when rebooting into SDE (the screen is all messed up)
Any suggestion?
I didn't modify init.rc and vold.stab since this is a fresh install
yura-a said:
Does this method applicable to Archos 101 model too?
If someone already have been tried it on 101, please reply with details here, if any troubles you have after installation or any changes need to be done.
Also I am curious about does anyone have tried to connect USB thumb drive to the tablet with modified rom and root access? Do we still have any issues with USB drive recognition?
Click to expand...
Click to collapse
Yes this procedure works the same way on the A101. I have the 16GB version so I made the 1st partition a bit bigger but that was the only deviation.
Hi,
A huge thanks to everyone on this forum for their incredible work. I got my G Tablet a couple of weeks ago and its been running flawlessly.
I ran into an issue a couple of days back with rapid FC's on most of my apps.
I am running VeganTab GE upgraded from the stock ROM, CWM 0.8 and Pershoot's 1.4 GHZ kernel. After facing all the rapid FC'S I decided to do a wipeall and start from scratch. I didn't realize the FC's are being caused due to the partition being read only for some reason.
I have tried everything under the sun to resolve this with no luck.
I tried using NVflash and have followed the instructions to the letter and dont it multiple times. Each time it says its successful yet when I boot in VeganTab takes over and all my settings and apps are still there.
Ive tried using NVflash to load CWM and then flash Cyanogen's ROM 7 as well the TapnTap's stock 3588 all to no avail. None of them will load. I cant delete files on the SD card nor write to it. I cant uninstall or install any apps. Everytime I try to do so, it says its uninstalled or installed and I can use the app, but the next time I reboot, things go back to exactly how they were when I started getting those FC's, almost like a restore point in Windows. Anytime I reboot it goes back to that point in time. I have also tried repartitioning the SD card to every possible combination (2048/0, 2048/256, 2048/128, 4096/256) and everytime it says its successful but nothing has changed. I have tried wipe data/factory resets, wipe Dalvik, format all (boot, cache, system, data). I have even tried the Format All zip floating around but it wont load it saying bad file. (Not a file size mismatch since I have downloaded it multiple times from different sources)
I came across this archived thread from a while back where someone had this issue but I haven't found a solution to it yet. I have followed everything in that thread but nothing seems to work. For the time being, the FC's have seemed to have slowed down but my tablet is stuck in some sorta time warp now since I cant seem to update it anymore.
Any help would be greatly appreciated!
It will be of no help, but in general Linux will knock a file system into read only mode when there are too many write errors to the volume. It could be a hardware defect in your unit doing it, or a corrupted file system. However, it seems you've been doing an NVFlash on it, so that should resolve the filesystem I would think.
Maybe in CW you can format /system and /data and see if that helps?
Edit: I see you did format, sorry. I don't know what to offer
Yup I have tried pretty much everything.
Wondering if anyone has any tips or tricks I might have missed. Surely there must be some way to convert this back into write mode.
What other options could I have?
Try this...it puts an empty file in each partition
http://forum.xda-developers.com/showthread.php?t=974422
Then use bekits nvflash files.
Nvflash is like a low level format. You either have a bad usb cable or your not in APX mode when you run nvflash or you have a bad tab. Make sure you are powering on using Power/Vol- not vol+. It will be a black screen and takes several minutes to run
Ive tried that.
Since the SD card is read only, i cant actually copy the file down to the drive to load.
Is there anyway to load this via microSD?
Can CWM view the microSD card?
Sandyjb, which partition is becoming read-only?--I'm not able to make this out after reading your post.
There are 2 distinct kinds of storage devices on the gTablet. You can see them if you type 'mount' in a Terminal Emulator window. For example, here's the output of mount on my tablet:
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk3p2 on /data type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
/dev/block/vold/179:25 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
The output of the mount command may vary slightly depending on whether you get the system mount command or the busybox mount command, but the basic information presented will remain the same. What's of interest to us are the lines beginning with /dev/block/ and the mount flags--the stuff within ().
There are, as you can see, 2 kinds of devices listed
/dev/block/mtdblockn and
/dev/block/mmcblkn
(The /dev/block/vold/n:n is also relevant to this discussion, but, more on this later.)
The /dev/block/mtdblockn device are directly addressable NAND flash devices. These are the only devices that the nvflash utility operates on.
The other type of device, the /dev/block/mmcblkn type, are SD card devices--either internal or external. On the gTablet, the internal SD cards are identified as /dev/block/mmcblk3x, and the external SD cards look like /dev/block/mmcblk2x. The SD card devices cannot be formatted or modified using nvflash. You have to use other tools. The /dev/block/vold/n:n device is also an SD card, but it is mounted (as needed) by the vold program which is why it is named differently.
If your external SD card partitions are read-only, try inserting them into a Windows machine and see if running the SD Formatter mentioned in this thread brings it back to its normal state:
http://micosd-doesnt-work.com/
If the program fixes the card, you can put it back in the gTablet and run ClockworkMod to re-partition it again.
If it is either the internal SD card partitions or the NAND flash partitions that are read-only, then the troubleshooting process is slightly more involved. In any case, send me the output of the mount command on your tablet.
Hi Rajeev.
I dont think I have any issues with my external card ie. microsd. Its the drive marked as sdcard card that I have issues with.
I am not as familiar with the results that came back via the terminal.
Perhaps you can elaborate.
Here is what I got
$mount
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mmcblk3p2 on /data type ext3 (rw,nosuid,nodev,relatime,errors=continue,data=writeback)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)
/dev/block/vold/179:25 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:25 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
/dev/block/vold/179:17 on /mnt/sdcard2 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-0 on /mnt/asec/com.rovio.angrybirds-1 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/dm-1 on /mnt/asec/com.tripit-1 type vfat (ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
$
That mount output looks perfectly normal. You said you were running VEGAnTab-GE. That is a Gingerbread-based ROM, I think, and so should have the SD cards mounted at /mnt/sdcard and /mnt/emmc and not /mnt/sdcard and /mnt/sdcard2.
Whatever the case, I want to check that /mnt/sdcard is writable. So,
1. Can you tell me if there is an /emmc or a /mnt/emmc folder on the tablet. Typing ls -l /emmc /mnt/emmc will do.
2. Try these commands in a Terminal to check if it's an application problem or an OS/hardware problem:
Code:
mkdir /mnt/sdcard/tmp.dir
echo test > /mnt/sdcard/tmp.dir/file.txt
Both commands should succeed if /mnt/sdcard is writable. Next read back the file.txt file:
Code:
cat /mnt/sdcard/tmp.dir/file.txt
should say: test
3. Reboot the tablet and try the cat command again. It should again print: test
4. Remove the directory, and verify that it has gone both before and after a reboot:
Code:
rm -rf /mnt/sdcard/tmp.dir
We'll carry on from here.
Thanks a ton for your help Rajeev!
Here is what I got back after step 2. Seems like everything worked fine there.
$ export PATH=/data/local/bin:$PATH
$ls -l /emmc /mnt/emmc
ls: /emmc: No such file or directory
ls: /mnt/emmc: No such file or directory
$ mkdir /mnt/sdcard/tmp.dir/file.txt
mkdir failed for /mnt/sdcard/tmp.dir/file.txt, No such file or directory
$ mkdir /mnt/sdcard/tmp.dir
$ echo test > /mnt/sdcard/tmp.dir/file.txt
$ cat /mnt/sdcard/tmp.dir/file.txt
test
$
However, after the reboot, it hung up once during restart. After doing another restart, it loaded into Vegantab just fine. The I ran the same command again and this is what I got
export PATH=/data/local/bin:$PATH
$ export PATH=/data/local/bin:$PATH
$ cat /mnt/sdcard/tmp.dir/file.txt
/mnt/sdcard/tmp.dir/file.txt: No such file or directory
$
Didnt do step 4 after that.
Very interesting--it's just like you said: that partition seems to go back in time. If we can't fix this, you should send that SD card to the folks at NASA. They're sure to be interested in an entropy-negating device.
Alright, let's check to see if the other partition on that SD card--/data--exhibits the same problem. Do a reboot, so we can start from a clean slate--I want to see the kernel messages this time when we write to the SD card.
Code:
$ su
# mkdir /data/tmp.dir
# ls -ld /data/tmp.dir
# echo test > /data/tmp.dir/file.txt
# ls -l /data/tmp.dir/file.txt
# cat /data/tmp.dir/file.txt
test
#
Reboot the tablet, and check if the cat command outputs "test" again. But, before you reboot and check, run these commands so you can send me their output. We've written the output to /mnt/sdcard2, so we shouldn't have any disappearing files.
Code:
$ su
# dmesg > /mnt/sdcard2/dmesg.txt
# logcat -d > /mnt/sdcard2/logcat.txt
# ls -l /data > /mnt/sdcard2/ls-data.txt
# ls -l /mnt/sdcard /mnt/sdcard2 > /mnt/sdcard2/ls-sdcards.txt
# cat /system/etc/vold.fstab > /mnt/sdcard2/vold.fstab.txt
Zip up all those text files and attach it to your next post.
[email protected]
Ok here is what I got before the reboot.
$ export PATH=/data/local/bin:$PATH
$su
#mkdir /data/tmp.dir
# ls -ld /data/tmp.dir
drwxrwxrwx 2 root root 1024 May 9 13:15 /data/tmp.dir
# echo test > /data/tmp.dir/file.txt
# ls -l /data/tmp.dir/file.txt
-rw-rw-rw- 1 root root 5 May 9 13:17 /data/tmp.dir/file.txt
# cat /data/tmp.dir/file.txt
test
#
After the reboot:
# cat /data/tmp.dir/file.txt
/data/tmp.dir/file.txt: No such file or directory
And here are the Text files.
Hmm, the external SD card is referred to twice in /system/etc/vold.fstab. Can you try this:
Edit /system/etc/vold.fstab and comment out the last line in it. It looks like this:
Code:
dev_mount sdcard2 /mnt/sdcard/sdcard-ext auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
Just add a '#' character at the beginning of the line, like so:
Code:
# dev_mount sdcard2 /mnt/sdcard/sdcard-ext auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
You can edit it on your PC; then put it back on the tablet and reboot. After the reboot, go through the SD card test commands we did earlier.
To edit the vold.fstab file, you'll have to remount the /system partition read-write. If you know how to use adb, try these commands:
Code:
adb pull /system/etc/vold.fstab vold.fstab
[I]Edit the vold.fstab[/I]
adb remount
adb push vold.fstab /system/etc/vold.fstab
Also, after you've run the SD card test commands, run the "dmesg" and "logcat -d" as before and attach their outputs.
Another thing to try: Remove the external SD card (after you've changed vold.fstab) and see if file and directories persist on the internal SD card.
Ok, after editing vold.fstab, loading microSD back in and rebooting, I ran the test commands.
Code:
$ export PATH=/data/local/bin:$PATH
$su
#mkdir /data/tmp.dir
# ls -ld /data/tmp.dir
drwxrwxrwx 2 root root 1024 May 9 23:48 /data/tmp.dir
# echo test > /data/tmp.dir/file.txt
# ls -l /data/tmp.dir/file.txt
-rw-rw-rw- 1 root root 5 May 9 23:49 /data/tmp.dir/file.txt
# cat /data/tmp.dir/file.txt
test
#
After another reboot and running of the same test command
Code:
# cat /data/tmp.dir/file.txt
/data/tmp.dir/file.txt: No such file or directory
Then I ran the the "dmesg" and "logcat -d" as before
Here are the outputs again.
Thanks again....your time in looking at this is much appreciated!
PS - I didn't understand the last line. Internal directories exist on the main drive (SDcard) when the microSD is taken out? I only started using the microSD very recently and the directory structure on the main drive remains intact irrespective.
sandyjb said:
Ok, after editing vold.fstab, loading microSD back in and rebooting, I ran the test commands.
Click to expand...
Click to collapse
I see that you've placed the '#' on the line before the last line. This makes it a no-effect change. You have to comment out the last line--put the '#' at the start of that line. The last line should look like this:
Code:
# dev_mount sdcard2 /mnt/sdcard/sdcard-ext auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
Thanks again....your time in looking at this is much appreciated!
Click to expand...
Click to collapse
No probs. Actually, I may have good news and bad news for you... but, we'll get to that after you've fixed the vold.fstab file, rebooted, and repeated the tests in post #8, plus these additional commands via adb:
Code:
adb shell lsmod > lsmod.txt
adb shell ps > ps.txt
adb shell find / -name aufs.ko > find-aufs.txt
PS - I didn't understand the last line. Internal directories exist on the main drive (SDcard) when the microSD is taken out? I only started using the microSD very recently and the directory structure on the main drive remains intact irrespective.
Click to expand...
Click to collapse
If you look at that vold.fstab file you sent me, it has a line like this:
Code:
# todo: the secondary sdcard seems to confuse vold badly
After seeing that, I thought it would be best if you removed the external microSD card while you're running the tests. You can put it back in after we're done fixing this.
Ok after making the change to the vold.fstab file, I ran the test again and I got the same error.
$ cat /mnt/sdcard/tmp.dir/file.txt
/mnt/sdcard/tmp.dir/file.txt: No such file or directory
I dont have ADB setup so I cant run those commands. I made the changes to the text file via notepad. Any other way for me to run those commands?
I took out the microsd card and then ran the dmesg and logcat commands. Somehow I feel like I am doing this wrong....
$su
# dmesg > /mnt/sdcard2/dmesg.txt
cannot create /mnt/sdcard2/dmesg.txt: read-only file system
# logcat -d > /mnt/sdcard2/logcat.txt
cannot create /mnt/sdcard2/logcat.txt: read-only file system
#
This error looks right though since there is no microsd card anymore.
Thanks for your patience!
sandyjb said:
Ok after making the change to the vold.fstab file, I ran the test again and I got the same error.
$ cat /mnt/sdcard/tmp.dir/file.txt
/mnt/sdcard/tmp.dir/file.txt: No such file or directory
Click to expand...
Click to collapse
The vold.fstab looks OK now. Incidentally, I just downloaded VEGAn-GE-7.0.0-RC1-Harmony-signed.zip and checked the pristine vold.fstab inside it. Your original file is exactly the same as the official one. So, it looks like I've been barking up the wrong tree in this case. Oh, well...
I dont have ADB setup so I cant run those commands. I made the changes to the text file via notepad. Any other way for me to run those commands?
Click to expand...
Click to collapse
Since we're able to store files on /mnt/sdcard (the internal SD card), at least until the next reboot, just use /mnt/sdcard/ instead of /mnt/sdcard2 in the command lines. You can use the Terminal Emulator for now to run the commands if you don't have adb set up. But, we'll have need of adb soon, so you should get it set up if you can: http://forum.xda-developers.com/showthread.php?t=902860
Questions:
1. You are running VEGAn-TAB 7.0.0 RC1 (aka VEGAn-TAB Ginger Edition), correct?
2. Do you have ClockworkMod installed? And if so, which version? Ideally it should print this when you're in it: ClockworkMod Recovery v2.5.1.1-bekit-0.8. This seems to be the safest CWM for our gTablets according to the posts on the board.
3. You have tried the standard techniques to fix the SD card problem? Namely,
a) In CWM, formatted the internal SD card again (CWM > advanced > Partition Internal SD card).
b) Ran Fix Permissions (CWM > advanced > Fix Permissions)
4. Do you have anything of value on the internal SD card (/mnt/sdcard), because we might have to blow it away completely soon (or, atleast try to ). So, back up the stuff from /mnt/sdcard to /mnt/sdcard2.
You can insert the external SD card (/mnt/sdcard2) back into the tablet and move, not copy, the stuff from /mnt/sdcard into /mnt/sdcard2. We're doing a test along with backing up your sdcard data. After you move your files and folders, check that they are no longer present in /mnt/sdcard. Then shutdown, remove the external SD card, reboot back into VEGAn 7.0.0-RC1 and again check if the stuff you moved has indeed disappeared from /mnt/sdcard.
But, before you do all this, send me the output I requested in post #14.
5. Your gTablet is not a refurbished or second-hand piece, right? Because, I see a difference in the make of the internal SD card between your tablet and mine.
Here's the relevant portion of the difference in kernel messages (the dmesg output) between your tablet and mine:
Code:
- mmc1: new high speed SDHC card at address 1234
- mmcblk2: mmc1:1234 SA16G 14.8 GiB
- mmcblk2: p1
- mmc2: new high speed SDHC card at address aaaa
- mmcblk3: mmc2:aaaa SE16G 14.8 GiB
+ mmc1: new high speed SDHC card at address aaaa
+ mmcblk2: mmc1:aaaa SU16G 14.8 GiB
+ mmcblk2: p1 p2
+ mmc2: new high speed MMC card at address 0001
+ mmcblk3: mmc2:0001 MAG4EM 14.9 GiB
The lines prefixed with '-' are from your kernel; the ones prefixed with '+' are mine. We can skip the lines which mention "mmcblk2"--this is the external SD card. The lines containing "mmcblk3"--which is how the Linux kernel names these SD cards (MMC block devices as the name suggests)--are interesting because they refer to the internal SD card. I, and 2 other people I've talked to on the board, have the same internal SD card: MAG4EM 14.9 GiB, which is an MMC card. You, however, have a different internal SD card: SE16G 14.8 GiB, which is a SDHC card instead of a MMC card.
So, you have a slightly different kind of gTablet as far as the internal SD card goes. However, from what I've been able to find out, SDHC cards are (normally) freely inter-changeable with MMC cards, so I'm not sure if this is the cause of your problems. But, keep this in mind anyway.
1. You are running VEGAn-TAB 7.0.0 RC1 (aka VEGAn-TAB Ginger Edition), correct? YES.
2. Do you have ClockworkMod installed? And if so, which version? Ideally it should print this when you're in it: ClockworkMod Recovery v2.5.1.1-bekit-0.8. This seems to be the safest CWM for our gTablets according to the posts on the board. YES. Version 0.8.
3. You have tried the standard techniques to fix the SD card problem? Namely,
a) In CWM, formatted the internal SD card again (CWM > advanced > Partition Internal SD card). YES. Pretty much every trick there is on the forums, I have tried. Multiple times at that.
b) Ran Fix Permissions (CWM > advanced > Fix Permissions) YES
4. Do you have anything of value on the internal SD card (/mnt/sdcard), because we might have to blow it away completely soon (or, atleast try to ). So, back up the stuff from /mnt/sdcard to /mnt/sdcard2.
You can insert the external SD card (/mnt/sdcard2) back into the tablet and move, not copy, the stuff from /mnt/sdcard into /mnt/sdcard2. We're doing a test along with backing up your sdcard data. After you move your files and folders, check that they are no longer present in /mnt/sdcard. Then shutdown, remove the external SD card, reboot back into VEGAn 7.0.0-RC1 and again check if the stuff you moved has indeed disappeared from /mnt/sdcard. Nope, nothing I care about it on the SDcard. I have tried to manually format it using nvflash, accessing it via USB and just hitting delete on the PC. I even tried to do what you mentioned about, move the file over. It said it successfully did it and the file wasnt present when I checked, but open rebooting, as usual it went back in time.
But, before you do all this, send me the output I requested in post #14.
Here are the attachments from running it on the SD CARD. I will try and get ADB setup as well.
Also, no, I dont believe this is a refurb. I ordered it off Amazon and there it was specified as new.
I'm trying to forward my usb devices to chrooted linux environment (debian)
I've been googling but haven't been able to find much on this subject.
I've tried:
mount --bind /dev /chroot/path/dev
mount --bind /dev /chroot/path/proc
directories are created in the chroot mnt point.
If I run lsusb In ADB I get:
Bus 001 Device 001: ID 1d6b:0002
Bus 001 Device 002: ID 0424:2514
But if I run lsusb in my Chroot I get nothing returned, sometimes It just freezes on the command and I have to Ctrl + C back to prompt.
If I cd to /dev on my chroot I can see the contents of the /dev directory of android.
lsusb in android detects new devices after they are plugged in...
So I'm stumped...
Any help would be much appreciated, thanks.
What are the exact commands that you're running?
That bind command looks wrong. Were you actually running "mount --bind ..." or "bind ...". The latter is a bash built-in command to bind keystrokes to readline actions.
My bad, I'm using mount --bind /dir /chroot/path/dir, wrote the post and missed my mistake. thanks.
You have to bind mount /sys too.
Also, try the chroot setup using a terminal emulator (or through telnet) instead of through adb.
Thanks for reply, I just saw another post that had a long list of files, and some info about /lib and an usb.ids file, I'm not sure if I deleted it somehow, or if you edited your post, it was split second I saw it, then I logged in it was gone , anyways...
I'll try adding /sys
Yes I want the Chroot environment on my tablet, not on my pc. Can you repost what you had before, about the /lib directory and .ids file? I didn't have any of that setup, just the /dev and /proc directories.
Thanks again for help.
Yeah, I originally posted info. for a desktop Linux setup and then realized that that was probably not what you wanted, so I edited the post.
The set up on the gTablet was simpler, actually, because my busybox is a static binary. I just had to copy that into the chroot bin directory, create the lsusb symlink, bind mount /dev, /proc and /sys, and everything worked just fine.
As I said in my previous post, if you're still having problems, try the same commands in a Terminal Emulator instead of via adb. Since the /sbin/adbd on the gTablet also uses the usb ports, lsusb might not work when run through adb. Make sure you also disable "USB debugging" in Settings > Application > Development.
Cool, I'll try this out when I get home, and report back. Thanks!
Edit:
I added mount from adb
--bind /sys /chroot/sys and mount
--bind /system /chroot/system
I added PATH from inside chroot
PATH=$PATH:/system/xbin (busy box location)
Now "busybox lsusb" shows the proper output, I think the issue was just running the wrong lsusb?
The main goal is to add a usb wifi adapter to the tablet, then access it from inside debian chroot. Are there any other issues I should watch out for, anything I should read? I figured it should be as simple as compiling the module for the android kernel, and with these binds, I should be able to access it with wicd or networkmanager or whatever inside the chroot right? let me know. Thanks.
Hey im doing something very similar with backtrack5 running on the galaxy sII. Trying to attach a external usb wifi card. The phone recognizes the decice and is powered correctly. All i need to do is install the driver on the chroot session. How can you forward the usb device.
Any luck?
Hi !
I have an application (CamScanner) with large amount of data (~8Gb). This app doesn't support transfering data do external SD card, so I checked mount -o bind command to bind directory with data stored on external SD to directory in /sdcard and it's working correctly. Question is where I can put this command so that system will run it at boot time after external sd card is ready. There is no /etc/init.d directory on my SGS2 (stock XXKI4). I prefer not to install any applications to perform such a simple task...
Thanks for help, regards !
slig said:
I prefer not to install any applications to perform such a simple task...
Click to expand...
Click to collapse
I think you have no choice, as stock kernels do not have init.d support. You'd need to go down the route of either using an app to run a script on boot, install a kernel with init.d support, or stick with your current method of manually running a script when you need to use the app.
Also, you could try asking the developers kindly to allow saving to external_sd. There's an Email Developer link on the Android market, and a Contact Us link on their website
Thanks for response. I found script named init.rc located in "/", it has several mount commands inside, wonder if it can be used...
Also discovered that app Tasked has ability to run shell scripts with root privileges (at boot or at application start). I suppose I have to put this shell script in /system because in /sdcard owner permissions cannot be set so that file cannot be modified (vfat does not support that) and a security hole would be created...
I think that I'll also ask developer for this feature as You suggest.
slig said:
Thanks for response. I found script named init.rc located in "/", it has several mount commands inside, wonder if it can be used...
Click to expand...
Click to collapse
Everything in "/" is initramfs, a volatile ramdisk changes to which would be lost
on reboot. Only exception are directories in which actual partitions are mounted,
like /system and /data (you can check which directories with "mount" command).
Have you tried just using symbolic link?
INFO
This may be the best solution, try something like:
Code:
mkdir /sdcard/AppFolder
ln -s /sdcard/AppFolder /data/data/com.your.application.data.folder
Just in case you don't know, you can execute those command using
Terminal Emulator. You were considering modifications to /, so I guess you already have root.
Yes, I have rooted my SGS2 via ZergRush.
I didn't know that / is volatile initramfs, thanks for that information.
As for symbolic link - unfortunately on my stock ROM both /sdcard and /sdcard/external_sd filesystems are vfat and don't support symbolic linking. Only working way I discovered is bind mount.
In my case, I have the following:
mount -o bind /sdcard/external_sd/CamScanner /sdcard/CamScanner
And application runs OK, all data is accessible and doesn't consume internal flash memory.
I'll take a look how hard would be to write some small application to do just this task - define some pairs of source and target directories and mount - bind them at start.
I've somehow missed the fact that you're need redirection from /sdcard
to /sdcard/external_sd, I was thinking about symlink on /data...
Anyways, there another nice trick you can do - if you can devote your SD card
to this one application, then just edit /system/etc/vold.fstab to make SD card
mount in /sdcard/CamScanner instead of /sdcard/external_sd.
I have already tried Siyah and Perseus kernel.
What I'm trying to do is create 2 small swap files one in internal sd and the other on the external sd. (Yes just a small memory bump will do)
On windows I did these:
Code:
fsutil file createnew C:\swap1 128000000
fsutil file createnew C:\swap2 128000000
Copied swap1 to /storage/sdcard0
Copied swap2 to /storage/extSdCard
btw /storage/extSdCard is exFat
then on Terminal Emulator.
Code:
su
mkswap /storage/sdcard0/swap1
mkswap /storage/extSdCard/swap2
swapon /storage/sdcard0/swap1
*This is where I get the error "swapon: /storage/sdcard0/swap1: Invalid argument"
(1) Swapper2 app doesnt work for me.
(2) I don't want to use hardswap or swap partition on my external SD.
*NTFS is unstable with uTorrent using Paragon NTFS/HFS+ (i'm getting corrupted files.)
*exFat is unstable when used with more than one partition like exfat/swap or exfat/swap/ext4. (still getting corrupted files.)
I've also tried using losetup, but when I do this:
Code:
# losetup -f
/dev/loop0
# losetup /dev/loop0 /storage/sdcard0/swap1
losetup: /dev/loop0: No such file or directory
I think the loop module is not loaded in the kernel, how do i load it? and where can i find the module?
R: [Q] How to use swapon?
autumnwillow said:
I have already tried Siyah and Perseus kernel.
What I'm trying to do is create 2 small swap files one in internal sd and the other on the external sd. (Yes just a small memory bump will do)
On windows I did these:
Code:
fsutil file createnew C:\swap1 128000000
fsutil file createnew C:\swap2 128000000
Copied swap1 to /storage/sdcard0
Copied swap2 to /storage/extSdCard
btw /storage/extSdCard is exFat
then on Terminal Emulator.
Code:
su
mkswap /storage/sdcard0/swap1
mkswap /storage/extSdCard/swap2
swapon /storage/sdcard0/swap1
*This is where I get the error "swapon: /storage/sdcard0/swap1: Invalid argument"
(1) Swapper2 app doesnt work for me.
(2) I don't want to use hardswap or swap partition on my external SD.
*NTFS is unstable with uTorrent using Paragon NTFS/HFS+ (i'm getting corrupted files.)
*exFat is unstable when used with more than one partition like exfat/swap or exfat/swap/ext4. (still getting corrupted files.)
I've also tried using losetup, but when I do this:
Code:
# losetup -f
/dev/loop0
# losetup /dev/loop0 /storage/sdcard0/swap1
losetup: /dev/loop0: No such file or directory
I think the loop module is not loaded in the kernel, how do i load it? and where can i find the module?
Click to expand...
Click to collapse
Why not use my multitasking mod?
From universe with my gs3
autumnwillow said:
I have already tried Siyah and Perseus kernel.
What I'm trying to do is create 2 small swap files one in internal sd and the other on the external sd. (Yes just a small memory bump will do)
...
Click to expand...
Click to collapse
IMHO swap on internal eMMC is one of the worst ideas ever. There is however somewhere a thread about how you can make one on SD.
xclub_101 said:
IMHO swap on internal eMMC is one of the worst ideas ever. There is however somewhere a thread about how you can make one on SD.
Click to expand...
Click to collapse
It's the same result I think for both SD and MMC. Using them as swap will shorten its life. But I'm okay with that. I plan to upgrade in the near future anyway.
What I'm not okay with is my poweramp music player pauses from playing flac files (choppy, not from notifications). Contacts/Phone/Messaging being too slow to load. Other apps also reloading too much. Not much of multitasking.
Currently i use zram with Yank's kernel. And believe me the 250mb zram is being consumed well.
The idea was to create 2 small swap files (larger) and setting priorities to them. 1 for the faster internal sd and 2 for external sd. Using swapon -p 1/2 swapfile
Why large files? Lesser rewrites. More sd life.