Related
I made this to tide myself over until $auron can finish UrukDroid 0.6. This is a combination of the stock Archos 2.1.04 firmware, Ardatdat's Overclocked Kernel, and a manual EXT4 Conversion. It is permanently rooted and includes SuperUser. My main reason for making it was to enable read/write access to the filesystem, which rooting DOES NOT do on the stock Archos firmware, as the squashfs will still be mounted read only by /etc/mountpoints. Also, EXT4 is much faster than the compressed squashfs Archos uses. Quadrant gives ~2200 with the data partition converted to EXT4 as well, ~1800 without conversion. I have already updated Busybox to a fully compiled version, 1.16, another thing Archos decided to "secure" despite the supposed Open Source status. I have NOT edited the .hosts file to block ads, as I believe the app developers deserve to make some money, you'd be amazed how little they make, but you can do it yourself without Archangel scripts now, as the filesystem will be read/write again.
I designed it on an A101it, but it should work on any Gen8 with internal flash storage. A70H users, I can't remember your block allocations, it may work fine, but I'll need someone to post the storage layout of /dev/block/ to be sure.
For the power users, here's a quick install outline: First, make a second partition on your storage/sdcard in EXT4, extract the rootfs.tar.gz to it, and flash the appropriate initramfs and zimage. Pretty easy.
For the rest of you(probably most of you):
There is only one short step in Linux, which is setting up an EXT4 partition on your Internal Storage or your SD Card. You must make it as a second partition, not 1st, 3rd, or anything else. This means you can still use it as a storage device as well as running Android. I find it incredibly simple, and can be done in less than 3 minutes, but I will be relying on you guys to tell me what you don't understand, and I will update the instructions as needed.
This can be run off the SD Card or the Internal Storage, both versions are included in the download. It will use the existing data partition if you already have the SDE installed and 2.1.04 firmware. Otherwise, you will need to flash the SDE, which erases your data, so please use Titanium Backup first if necessary.
Step 1:
Download my files:http://www.multiupload.com/HR6SRRR8P8
And install the SDE from Archos: http://www.archos.com/support/download/firm_dev/firmware_archos_android_gen8.aos.
Step 2: Boot into stock Android and connect to a Linux PC. If you do not have Linux, download Tuxboot and use it to create a GParted Live Disk:http://gparted.sourceforge.net/liveusb.php
Step 3:
Mount your Internal Storage/SD Card from the Archos. It should now show up in GParted on the Linux PC, make sure you have the correct device selected, it should be called Archos A101T(make note of the location, e.g. /dev/sdb). Resize your existing partition with GParted, leaving about 300MB at the end of the Internal Storage/SD Card. Make a new partition in the empty space, and select ext4 as filesystem. Apply Changes. Now open a terminal, elevate yourself to root by typing
Code:
sudo -s
and format the new partition by typing
Code:
mkfs.ext4 -O ^huge_file /dev/sdb2
Substitute "sdb" for whatever your device location was in GParted. The "2" on the end of "sdb" denotes that it is the second partition. Do NOT format "sdb1" or any other "sd"s. Mount the new partition by opening Nautilus or any other file manager and double clicking on the "300MB Filesystem" entry on the left. Untar the rootfs.tar.gz from my files with the Archive Manager, it works just like winzip or winrar, into the root of the new partition. Eject the device from Linux, then reboot into the Developer Menu by holding vol- or vol+ while booting.
Step 4:
Flash the initramfs.cpio.gz and the zimage from my files. Use the files from the "internal" folder if you are running from Internal Storage, or the files from "sdcard" if you are running from the SD Card.
Step 5:
Use the Dev Menu to boot into Developer Edition. Let me know about any bugs. After I removed the Android Boot option from the Dev Menu, I had a few strange loops of the Archos animation while booting, but it did boot, and function, just fine.
Thanks go to Ardatdat for the kernel, Archos for the crappy "securing" of the squashfs, and $auron for motivating me to get back into development.
Hi msticninja ,
I did it It seems so smooth. I used my internal storage. But linux steps were not so simple for me I used a Fedora 14 VMWare image.
I'm at work so I can't play with it but it seems stable and it can awake.
Quadrant (I know it's not accurate) score is about 1900 (internal and ext4).
I think that you should add some descriptions about linux steps (for noobs like me).
Thanks...
PS: Did I move my DATA partition to EXT4? (I did all steps you wrote). If no how can I do?
Nice work! I'll be trying to add more instructions for the Linux section for the next couple of days.
Your data partition is still EXT3, I haven't found a very easy way to convert it yet. Basically, I made another partition on the Internal Storage, copied the data partition there, and flashed a new initramfs to boot off the new data partition. Then you fdisk and format the original partition from a terminal in the Archos or ADB, copy everything back, and flash ANOTHER initramfs to use the original, now EXT4, partition.
So far, I don't think the performance gain for the data partition is worth all that work.
It works and installs well but your guide how to install it is not complete. For example, I had to manually maintain write permissions of the partition and sudo is needed by the mkfs.ext4 -O ^huge_file /dev/sdb2
Hondaracer said:
It works and installs well but your guide how to install it is not complete. For example, I had to manually maintain write permissions of the partition and sudo is needed by the mkfs.ext4 -O ^huge_file /dev/sdb2
Click to expand...
Click to collapse
Sorry, i automatically elevate permissions when I do stuff like this. I've added sudo to the instructions. As far as manually maintaining the partition permission, what did you have to do there?
msticninja said:
Sorry, i automatically elevate permissions when I do stuff like this. I've added sudo to the instructions. As far as manually maintaining the partition permission, what did you have to do there?
Click to expand...
Click to collapse
I had to type this: sudo chown -R username:usergroup /media By the way thanks for the work you've done
Hondaracer said:
I had to type this: sudo chown -R username:usergroup /media By the way thanks for the work you've done
Click to expand...
Click to collapse
If that was before using mkfs.ext4, then that is strange. After mkfs though, the owner should be root. I should point out that the rootfs.tar.gz should be extracted as root, which means you have to open the archive manager from a terminal. I need to find an easy process that will work on all distros, as I don't know how many have nautilus installed.
Thanks for your replies, this is much needed feedback.
msticninja said:
If that was before using mkfs.ext4, then that is strange. After mkfs though, the owner should be root. I should point out that the rootfs.tar.gz should be extracted as root, which means you have to open the archive manager from a terminal. I need to find an easy process that will work on all distros, as I don't know how many have nautilus installed.
Thanks for your replies, this is much needed feedback.
Click to expand...
Click to collapse
I had to do this to be able to write the rootfs to dev/sdb2. But I must say I did a reboot before I copied the files cause Ubuntu started to act very weird. And for the beginner I'd might be good to mention that you have to unmount in GParted.
I've tried it and feels slower than Uruk 0.6RC2 on Scandisk SDHC 8GB Class 4 (without OC).
Thank you for your great work!
chisco said:
I've tried it and feels slower than Uruk 0.6RC2 on Scandisk SDHC 8GB Class 4 (without OC).
Thank you for your great work!
Click to expand...
Click to collapse
I'm not surprised. This is the stock firmware with none of Uruk's enhancements, other than ext4 and a new kernel. As i said, this is to tide people over until the official Uruk thread gets 0.6. You're already on the beta 0.6, so there's not much need for my firmware.
I just wrote an automatic install script. All you have to do is copy a file to your internal storage or sd card, and flash the initramfs/zimage in the Dev Menu. This one will replace the current Archos partition so you won't lose any space on your storage device. Should be uploaded tonight.
I tried this method with last OC Kernel (11 FEB): very good... With this method, we use same data as for stock ROM, so no need to reinstall all apps...
Thanks.
Hello, fellow gTablet users!
I'm kinda newbie here, so first of all my apologies to everyone if that was already asked, 'cause I did some research on the matter and couldn't find all the necessary info for solving my particular issue.
Ok, so here's the deal. I was using my gTab for about half-year now. When I received it, I installed VeganTab-7 Ginger Edition on it (thanks for the devs - very nice ROM!) and it worked flawlessly until yesterday. But then something not good happened and the tablet stopped booting. Now it starts from birds screen, goes on to G-Tabdevs screen, after which VeganTab GingerEd boot screen appears, it has flashing letters for a couple of seconds and then tablet goes black and tries to boot again. I guess it's a boot loop so it's kinda soft brick and I'll have to do wipe data/factory reset through CWM to solve the issue. So this isn't the biggest problem - I've already found all the instructions.
The real problem is that I didn't make backup of my data (guilty!), but I don't want to lose some of it, especially the browser data. I was using Opera Mobile, so I guess that its data should be on /data partition. So I'll need an advice on how I can dump the necessary data before doing factory reset!
I've already tried connecting to desktop, using guide from this (http://forum.xda-developers.com/showthread.php?t=1010943) thread (third method from it), but it didn't work, at least on my Win7 Pro x64 SP1: the tablet shows as removable disk, but I can't access it. I tried to mount /data or /sdcard partitions through CWM recovery menu, but it tells me that it can't find /dev/block/... - I guess that's block device, associated with those partitions. So what are my best options of backuping data?
And the last question: I'll probably install some other ROM just to try something different, but unfortunately I don't remember what loader I have. I'm nearly sure that I installed VeganTab for 1.1, 'cause I did it back in May 2011 and there wasn't one available for 1.2 yet. But just to make sure: how can I find my loader version before I do reset? Or maybe I just have to do the reset and look for it when back on stock ROM?
Seriously, guys, doesn't anybody know how to solve these problems?
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Thank you for reply, rajeevvp.
When I'm trying to mount /data and /sdcard it says respectively:
Code:
E:Can't mount /dev/block/mmcblk3p2
(No such file or directory)
Error mounting DATA:!
E:Can't mount /dev/block/mmcblk3p1 (or /dev/block/mmcblk2p1)
(No such file or directory)
Error mounting SDCARD:!
Unfortunately I didn't have ADB installed. Now I'm trying to use the guide from here: http://forum.xda-developers.com/showthread.php?t=902860, but fail on step 4, cause there is nothing like "Nvidia harmony" appearing under other devices in my dev manager, just "Nvidia Tegra 2 USB Device" under Disk Drives and "USB Mass Storage Device" under Universal Serial Bus Controllers. I guess these devices are gTablet's internal memory presented as disk drive...
I'll try to install ADB and then write back how it worked.
Interesting error messages. Now I really have to see those text files.
If you're having problems installing ADB on Windows, try using Linux.
Ok, thanks you very much! I'll try that, but unfortunately tomorrow, as it's already too late here.
Btw, I read your post about linux - you're suggesting Knoppix Live CD there. Is it mandatory to use it? I mean I already have PartedMagic live CD burned, maybe I could use it instead...
anary said:
I mean I already have PartedMagic live CD burned, maybe I could use it instead...
Click to expand...
Click to collapse
If sudo and adb work, then no problem.
rajeevvp said:
Boot into CWM first, then try mounting both /data and /sdcard using the CWM menu. Note down the exact error message displayed in each case. Then connect the USB cable and run these ADB commands on your PC:
Code:
C:\> [B]adb shell dmesg >dmesg.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk3 > fdisk.txt[/B]
C:\> [B]adb shell fdisk -l /dev/block/mmcblk2 >> fdisk.txt[/B]
Post the error messages and those 2 .txt files here.
Click to expand...
Click to collapse
Ok, I finally managed to do it. Sorry for the delay.
The files are attached. Did everything how you told me.
Actually I don't think that I understand too much in Android inner mechanics But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Btw, thanks a lot for your advice about using Knoppix - it's really very easy and handy!
anary said:
But having looked through these files, I thought that inner sdcard device (mmcblk3) doesn't seem to produce any strange behavior...
Click to expand...
Click to collapse
You have lost your /data partition altogether. You are supposed to have 2 partitions on that internal SD card: a 14GB FAT32 partition and a 2GB ext3 partition. You only have a single FAT32 partition spanning the entire SD card now.
I may be able to help you get both partitions back if you give me these details:
1. How and when did this happen?
2. Current ROM.
3. Current version of CWM.
4. Did you try to repartition the (internal) SD card recently?
5. Have you ever repartitioned the internal SD card? If yes, then using which version of CWM?
6. After you noticed the problem what steps did you take to fix the problem?
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Ok, here are the details:
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory? I checked through file manager though, and all the files seemed intact...
2. VeganTab GingerEd from this thread: http://forum.xda-developers.com/showthread.php?t=1031250. I'm pretty sure that I didn't install anything except for it.
3. Don't know. But it says ClockworkMod Recovery v2.5.1.1-bekit-0.8 in recovery menu, so I guess its version is maybe 0.8.
4. No I didn't, at least intentionally.
5. I think I did it just once, when installing the ROM. I'm pretty much sure that I used this instructions for repartitioning: http://viewsonic-gtablet-for-dummies.webs.com/repartition.htm (not exactly this, but I did the same as it's written there). To install the ROM I used the instructions from the ROM thread, mentioned above. I didn't whant to do a lot of modding, just wanted the device to work at least better than with stock ROM, so didn't try to change any other low-level things.
6. I just tried to mount partitions through CWM recovery and I tried wiping out cache partition and Dalvik cache. Nothing else.
anary said:
Yeah, I remember I was curious where it stores OS's kernel if all it has is FAT32 partition - now I get it...
Click to expand...
Click to collapse
The OS kernel is not stored on the SD cards. They're stored on a "boot" partition on the NAND flash. And, if the OS was messed up you would get hung up on the initial splash screen (the one with the 3 birds)--you wouldn't go into a boot loop.
1. I don't really know what has happened, but I guess that it happened when I tried to use tablet like cardreader for microsd card. During that I sort of formatted external sd - maybe that actually was internal memory?
Click to expand...
Click to collapse
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
I checked through file manager though, and all the files seemed intact...
Click to expand...
Click to collapse
Files where? The internal SD card or the external one? And, how did you check this? After formatting the internal SD card, the very next boot into the ROM would've put you into a boot-loop because the /data partition is missing.
I think I may be able to get stuff from /data, but, everything on /sdcard is most likely gone. (Actually, the files are most likely all there, but, without direct access to the tablet, it's very difficult to get the retrieve any of them.) Just don't touch the tablet until I've figured out the commands you will have to use.
That's what caused this problem. CWM-2.5.1.1-bekit-0.8 does not work on the external SD card (but, CWM-2.5.1.3 and CWM-4.0.1.5 do).
Did you format the internal SD card using CWM?
Click to expand...
Click to collapse
No, I was going to format external SD card and I tried to do it through Android (or maybe VeganTab) menu. I think that doing this, I could accidentally format internal SD, but I'm not sure this could be done from within the OS. During the same logon session I checked files on internal SD with file manager and all of them were where they should have been. So I thought that all was ok. But when I rebooted next time, it wasn't booting... That's why I told you that maybe it was because of formatting.
And just to be clear: I didn't do anything using CWM after it stopped booting, apart from wiping system and Dalvik caches.
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
rajeevvp said:
Do you have a large capacity micro SD card (anything larger than the maximum amount of data that's currently on the internal SD card) that you can use to save retrieved data into?
Click to expand...
Click to collapse
Yep. Won't be any problem.
anary said:
Yep. Won't be any problem.
Click to expand...
Click to collapse
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
rajeevvp said:
OK. Format that micro SD to contain a single DOS partition; then we'll proceed.
Click to expand...
Click to collapse
Ok. That's done.
Boot into CWM, go into the "mounts and storage" menu, unmount all mounted partitions, connect the USB cable, and run these commands using ADB--do not back out of that "mounts and storage" menu while we're fixing this. We're trying to see if the data on the current /sdcard partition can be retrieved.
Code:
$ [B]adb shell[/B]
~ # [B]mount -r /dev/block/mmcblk3p1 /sdcard[/B]
~ # [B]ls -l /sdcard[/B]
If the ls listing looks OK, then we force a filesystem check before copying the data to the external micro SD card:
Code:
~ # [B]mount -r /system[/B]
~ # [B]umount /sdcard[/B]
~ # [B]/system/bin/fsck_msdos -f -y /dev/block/mmcblk3p1[/B]
If the listing doesn't look OK, then the data on /sdcard is lost.
Post the exact output of each command.
Ok, mount says this:
Code:
mount: mounting /dev/block/mmcblk3p1 on /sdcard failed: Invalid argument
and ls after that gives no output - I think it shouldn't give any, 'cause I didn't mount anything...
Does this mean I'm screwed?
Try this mount command:
Code:
~ # [B]mount -r -t vfat /dev/block/mmcblk3p1 /sdcard[/B]
The same result.
Hi all.
I recently went about updating my tablet, and in the back of my mind I was under the impression that TWRP would backup the internal sdcard's files during the normal backup, so I thought nothing of wiping the internal sdcard. Whoops. It, of course, didn't, and now I find myself with a whole slew of stuff gone. Not much else was written to the internal sdcard (which is on an ext4 filesystem), so I suspect that a good bit of my stuff can still be sitting there in the data graveyard. Hopefully.
Since I'm on Linux and can't mount the sdcard directly (since for some odd reason Linux has issues with MTP), all I've been able to do was this:
I booted the tablet into recovery mode and opened up adb, and ran the following command through the adb shell:
Code:
~ # dd if=/dev/block/mmcblk0p8 of=/dev/block/mmcblk1p1
Where mmcblk0p8 is the internal sdcard with the lost data, and mmcblk1p1 is an external sdcard. I thought that by running that command, I could create a carbon copy of each and every little thing on the old sdcard, write it onto something my computer could read, and then go through the normal recovery process. In this case I planned to use a Linux tool called "extundelete."
Here's where I get stuck. The sdcard appeared to have cloned correctly, given that the entire thing is now filled up and reads as an ext4 filesystem on gparted (when it was previously fat32), but now I can't mount it. And if I can't mount it, I can't restore anything. Here's what I get when I try to mount it:
Code:
Error mounting /dev/sdb at /media/user/57f8f4bc-abf4-655f-bf67-946fc0f9f25b: Command-line `mount -t "ext4" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb" "/media/user/57f8f4bc-abf4-655f-bf67-946fc0f9f25b"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
So to sum it up, I accidentally wiped my tablet's internal sdcard using TWRP 2.3.3.0, and now I want to recover what was lost during the wipe. Not that it matters, my tablet is a Transformer Infinity in case anyone asks. Though I don't think that's really relevant here.
If anyone knows how to help me, or knows of a better way I should go about getting my data back, that would be, for a lack of better words, super awesome.
Thanks!
BJSerpas said:
Error mounting /dev/sdb
Click to expand...
Click to collapse
Seems you tried to mount /dev/sdb, not /dev/sdb1.
Also, did you make the SDcard partition the same size as the source partition? And what did dmesg say?
Also, http://forum.xda-developers.com/showthread.php?t=1994705 might be of some help..
kuisma said:
Seems you tried to mount /dev/sdb, not /dev/sdb1.
Also, did you make the SDcard partition the same size as the source partition? And what did dmesg say?
Click to expand...
Click to collapse
When I plugged it in, Linux automatically mounted it to sdb and not sdb1. And the external SD card was the same size as the internal one, 32gb. Currently not home so I can't run dmesg at the moment.
And thank you bodh, that looks very useful and is more or less what I was trying to do. I'll have to get on a windows PC it seems, but no issue there. In the meantime, is there a way to write protect the internal SD from the android terminal emulator until I get home? I don't want my old files accidentally overwritten. Or I could just not use the tablet if that's the better option here.
Thanks guys!
I'm not sure you could write protect the internal sd. I've tried changing permissions on it and get errors. You're best bet is probably to go without the tablet use for now.
BJSerpas said:
When I plugged it in, Linux automatically mounted it to sdb and not sdb1. And the external SD card was the same size as the internal one, 32gb. Currently not home so I can't run dmesg at the moment.
Click to expand...
Click to collapse
I'm talking about the number of blocks exactly, not "32gb" or so. And mount /dev/sdb1 manually, don't rely on Gnome failing to mount /dev/sdb.
Hey guys, wondering if you could help me. I'm running Jelly Blast V-3.5, with Rafaels Kernel 2.6.35-7 on my S5380i. I've been trying to increase the internal storage on my device by partitioning my 32gb card in CWM with a 1gb ext. I've tried every solution I've found on this forum but I simply cannot get it to mount. Link2sd yields 'invalid argument' no matter where I point it, and when trying to format/mount the ext. in CWM it just says 'apps 2 sd partition not found'.
Here's a list of the things I've tried which have failed to solve this:
Partitioning in minitool, with various sizes and exts, and setting the partition as active.
Flashing conrod script, doesnt seem to be effective.
Script to mount sd-ext at boot, followed iamareebjamal's guide found here http://forum.xda-developers.com/showthread.php?t=1971689
S2E
Mount2SD
I'm completely at a loss, and with the internal storage of the S5380i being what it is, it would be great if anyone could offer me any advice.
Thanks!
do one thing , I'm recovery check if sd-ext is mounted
it used to happen to me that when I flashed new roms I had to mount sd-ext from mounts and storage
so mount it then reboot your phone
go to link2sd and create mount script as ext4
if problem persists , go in storage info of link2sd so see if the partition is mounted
if not you will have to enable auto mount at boot ( if option present in rom ) or mount using terminal emulator
Sent from my GT-S5670 using xda premium
soham jambhekar said:
do one thing , I'm recovery check if sd-ext is mounted
it used to happen to me that when I flashed new roms I had to mount sd-ext from mounts and storage
so mount it then reboot your phone
go to link2sd and create mount script as ext4
if problem persists , go in storage info of link2sd so see if the partition is mounted
if not you will have to enable auto mount at boot ( if option present in rom ) or mount using terminal emulator
Sent from my GT-S5670 using xda premium
Click to expand...
Click to collapse
Thanks for responding.
Attempted to mount in CWM but just receive an error. It's as if the partition isn't there at all. Re-partioned the card but still, no luck.
My rom doesn't have the auto mount at boot option, so it looks I'll have to mount with terminal emulator. Could you run me through the process, or point me towards a guide? Cheers
what error did you get in cwm while mounting ?
yry this line in terminal
mount -o rw /dev/block/
mmcblk0p2 /sd-ext
also is mount2sd file present in your /etc /init.d folder ?
Sent from my GT-S5670 using xda premium
The error in CWM when attempting to mount is: 'Error mounting /sd-ext!'
'mount -o rw /dev/block/mmcblk0p2 /sd-ext' in Terminal Emulator yields the following line: 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
The mount2sd file is not currently present in my init.d folder as I restored my phone from a backup, though when it has been there, the error in CWM is still the same.
The only difference I have noticed is that when partitioning with MiniTool, Link2SD will say that the partition is not mounted, but when partitioning with CWM it will say that the partition is not found.
galaimo said:
The error in CWM when attempting to mount is: 'Error mounting /sd-ext!'
'mount -o rw /dev/block/mmcblk0p2 /sd-ext' in Terminal Emulator yields the following line: 'Usage: mount [-r] [-w] [-o options] [-t type] device directory'
The mount2sd file is not currently present in my init.d folder as I restored my phone from a backup, though when it has been there, the error in CWM is still the same.
The only difference I have noticed is that when partitioning with MiniTool, Link2SD will say that the partition is not mounted, but when partitioning with CWM it will say that the partition is not found.
Click to expand...
Click to collapse
Did you format ext2 in the secind partition? Normally when you format with cwm, first partition is fat32 and the second partition is ext2. Try to format all available space to 1 partition and using cwm format the card to two part. May be partitioning before makes cwm recognize the wrong part and gives error.
:: Today is the first day of what's left of your life. ::
ChelebiTech said:
Did you format ext2 in the secind partition? Normally when you format with cwm, first partition is fat32 and the second partition is ext2. Try to format all available space to 1 partition and using cwm format the card to two part. May be partitioning before makes cwm recognize the wrong part and gives error.
Click to expand...
Click to collapse
Ensured all the space on card was unallocated and partitioned in CWM recovery.
Attempted to mount /sd-ext again and still receive the following error: 'Error mounting sd-ext!'
Attempted to format /sd-ext and receive the following error: 'No apps2sd partition found. Skipping format of /sd-ext'
Tried so many different ways/combinations of partitions now. Do you think it could be a kernel or rom issue?
galaimo said:
Ensured all the space on card was unallocated and partitioned in CWM recovery.
Attempted to mount /sd-ext again and still receive the following error: 'Error mounting sd-ext!'
Attempted to format /sd-ext and receive the following error: 'No apps2sd partition found. Skipping format of /sd-ext'
Tried so many different ways/combinations of partitions now. Do you think it could be a kernel or rom issue?
Click to expand...
Click to collapse
Make sure you have backed up all your files in your sdcard they will all be deleted and recreated with two partition.
In CWM enter Advanced --> use Partition SD Card
Set your second (ext2/3/4) partition size then set swap to zero (0).
ChelebiTech said:
Make sure you have backed up all your files in your sdcard they will all be deleted and recreated with two partition.
In CWM enter Advanced --> use Partition SD Card
Set your second (ext2/3/4) partition size then set swap to zero (0).
Click to expand...
Click to collapse
This is exactly what I've done, countless times. It simply will not mount. Really struggling to understand this problem.
galaimo said:
This is exactly what I've done, countless times. It simply will not mount. Really struggling to understand this problem.
Click to expand...
Click to collapse
Using a card reader enter your sd card to a computer and test if card has a problem or partitions are correctly created. If your answer is yes you may have a misconfig on your phone. Make sure u have the latest busybox available, have rooted your phone correctly, vs...
Or create your partitions in computer and try...
Ps: I created my partition in Stock Rom. So it must NOT depends on kernel or rom...
ChelebiTech said:
Using a card reader enter your sd card to a computer and test if card has a problem or partitions are correctly created. If your answer is yes you may have a misconfig on your phone. Make sure u have the latest busybox available, have rooted your phone correctly, vs...
Or create your partitions in computer and try...
Ps: I created my partition in Stock Rom. So it must NOT depends on kernel or rom...
Click to expand...
Click to collapse
Partitioned with CWM again. Plugged in to laptop and in MiniTool and this is the result:
galaimo said:
Partitioned with CWM again. Plugged in to laptop and in MiniTool and this is the result:
Click to expand...
Click to collapse
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
:: Today is the first day of what's left of your life. ::
ChelebiTech said:
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
Click to expand...
Click to collapse
Thanks for taking the time to talk me through this.
Turns out my SD card is defective, swapped for another card and I've now increased my internal storage!
I'll be sending the other one back.
Thank you again for your time :good:
ChelebiTech said:
That unallocated space is your problem. Try to create an ext2/3 partion with mini tool. And if minitool gives error than you probably have a defected sd.
And one more suggestion try the cwm in rafaels kernel thread.
Edit: Sorry for cwm use http://forum.xda-developers.com/showthread.php?p=23715776
:: Today is the first day of what's left of your life. ::
Click to expand...
Click to collapse
Thanks for the link! seems like my CWM wasn't detecting sd-ext.. this fixed!! feared my sd card was ruined.. really thanks a lot!
hello,
I'd ask the question in the dev UBUNTU testing thread, but I don't have enough posts yet.
I am following the lifeinarootshell.blogspot.com/ instructions and have been following the Ubuntu thread since its beginning. I'm a bit of a newbie with linux, so it's taking some time.
I can't mount the micro sd card... I'm trying with the command "mount /dev/block/mmcblk1p1 /data/mmc"
When I type "mount" from a terminal on the TF201, I don't see "/dev/block/mmcblk1p1" listed.
This micro sd has my roofs on it that I need to chroot into. I've tried reformatting like 10 times now using various methods. I've used an HP format tool at fat32, then used the Minitool partition wizzard and formatted as ext4. I've also tried the gparted tool in a ubuntu vm. It's set as a primary partition.
Can anybody point me in the right direction?
Okay, got it figured out....
nookusr said:
hello,
I'd ask the question in the dev UBUNTU testing thread, but I don't have enough posts yet.
I am following the lifeinarootshell.blogspot.com/ instructions and have been following the Ubuntu thread since its beginning. I'm a bit of a newbie with linux, so it's taking some time.
I can't mount the micro sd card... I'm trying with the command "mount /dev/block/mmcblk1p1 /data/mmc"
When I type "mount" from a terminal on the TF201, I don't see "/dev/block/mmcblk1p1" listed.
This micro sd has my roofs on it that I need to chroot into. I've tried reformatting like 10 times now using various methods. I've used an HP format tool at fat32, then used the Minitool partition wizzard and formatted as ext4. I've also tried the gparted tool in a ubuntu vm. It's set as a primary partition.
Can anybody point me in the right direction?
Click to expand...
Click to collapse
I needed to use the busybox, so the command to mount is "busybox mount /dev/block/mmcblk1p1 /data/mmc"
Hope it might help someone else if they have the same issue.
hope it's not a big deal to be in the question thread
nookusr said:
I needed to use the busybox, so the command to mount is "busybox mount /dev/block/mmcblk1p1 /data/mmc"
Hope it might help someone else if they have the same issue.
Click to expand...
Click to collapse
Being a noob, I hadn't realized what busybox was really. Now I see it adds more functionally to the terminal.
What was funny was that I could mount and browse the files in TWRP, but not within android....
Yes well, I can now proceed....
Figured it out....
nookusr said:
hello,
I'd ask the question in the dev UBUNTU testing thread, but I don't have enough posts yet.
I am following the lifeinarootshell.blogspot.com/ instructions and have been following the Ubuntu thread since its beginning. I'm a bit of a newbie with linux, so it's taking some time.
I can't mount the micro sd card... I'm trying with the command "mount /dev/block/mmcblk1p1 /data/mmc"
When I type "mount" from a terminal on the TF201, I don't see "/dev/block/mmcblk1p1" listed.
This micro sd has my roofs on it that I need to chroot into. I've tried reformatting like 10 times now using various methods. I've used an HP format tool at fat32, then used the Minitool partition wizzard and formatted as ext4. I've also tried the gparted tool in a ubuntu vm. It's set as a primary partition.
Can anybody point me in the right direction?
Click to expand...
Click to collapse
I thought I'd post my solution here just in case if anyone else had the smae problem.
I had busybox installed and did not know what it did. It looks like busybox allows a selection of terminal commands. Therefore, I needed to type "busybox mount /dev/block/mmcblk1p1 /data/mmc"
this mounted without errors.