Database Info

Converting to ext4

Does anyone have a link to a guide/tutorial about converting ext3 partitions to ext4? Now that we have a CWM image that supports ext4 and several ext4 kernels, it would be really nice if someone could also explain how to convert Android partitions (specifically the ones on the G2X) from ext3 to ext4. Thanks in advance!

baldwinguy77 said:
Does anyone have a link to a guide/tutorial about converting ext3 partitions to ext4? Now that we have a CWM image that supports ext4 and several ext4 kernels, it would be really nice if someone could also explain how to convert Android partitions (specifically the ones on the G2X) from ext3 to ext4. Thanks in advance!
Click to expand...
Click to collapse
When you use a kernel or ROM that uses ext 4 it will automatically convert it. If you nandroid back to a ROM that uses ext 3 it will convert it back.

CrazyCharlie said:
When you use a kernel or ROM that uses ext 4 it will automatically convert it. If you nandroid back to a ROM that uses ext 3 it will convert it back.
Click to expand...
Click to collapse
Hmmm okay thank you! I'm just curious though...isn't there some kind of script or executable that can be used through the terminal to manually convert them? I believe I heard that one version is included in CyanogenMod and that there's also a version on desktop versions of Linux.

baldwinguy77 said:
Hmmm okay thank you! I'm just curious though...isn't there some kind of script or executable that can be used through the terminal to manually convert them? I believe I heard that one version is included in CyanogenMod and that there's also a version on desktop versions of Linux.
Click to expand...
Click to collapse
That would be a bit outside my technical know how. Maybe somebody better versed in Linux could chime in here. Anybody?

I didn't find a guide, but I tried this and it seems to be working.
flash ext4 recovery using nvflash: http://forum.xda-developers.com/showthread.php?t=1086687
in recovery flash normal cm7 nightly, gapps, and an ext4 kernel from: http://forum.xda-developers.com/showthread.php?t=1073626
run the following commands from adb shell:
Code:
umount /cache
umount /data
umount /system
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p1
/sbin/e2fsck -p /dev/block/mmcblk0p1
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
/sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7
/sbin/e2fsck -p /dev/block/mmcblk0p7
then reboot and it should work... at least it seems to be working for me

sainth said:
I didn't find a guide, but I tried this and it seems to be working.
flash ext4 recovery using nvflash: http://forum.xda-developers.com/showthread.php?t=1086687
in recovery flash normal cm7 nightly, gapps, and an ext4 kernel from: http://forum.xda-developers.com/showthread.php?t=1073626
run the following commands from adb shell:
Code:
umount /cache
umount /data
umount /system
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p1
/sbin/e2fsck -p /dev/block/mmcblk0p1
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p2
/sbin/e2fsck -p /dev/block/mmcblk0p2
/sbin/tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p7
/sbin/e2fsck -p /dev/block/mmcblk0p7
then reboot and it should work... at least it seems to be working for me
Click to expand...
Click to collapse
Awesome! Thank you very much!

To go with this post, does anyone know the commands for converting partitions back to EXT3? Thanks!

well if u just re flash the nightly ur using it will be ext3. cm isnt ext4 setup yet so pretty much all the roms rite now are ext3 so if u just flash the nightly or rom over what u have u will be fine it will install kernel too all u have to do is wipe cache then dalvik n flash rite on top n ur golden

now if u want the trinity kernel or faux kernel there ext 4 when u flash those kernels it converts everything to ext4 so dnt flash those if u wanna stay ext3 ext4 is faster tho y ext3?

sarni84 said:
now if u want the trinity kernel or faux kernel there ext 4 when u flash those kernels it converts everything to ext4 so dnt flash those if u wanna stay ext3 ext4 is faster tho y ext3?
Click to expand...
Click to collapse
Oh okay thanks a lot for your response! And to answer your question, in order to have EXT4, you have to use a custom kernel (clearly -- CM doesn't support it yet). Anyway, the CM kernel is updated with every nightly whereas the custom kernels aren't necessarily updated each time. So if you want to have the most recent fixes, etc. the CM kernel is the way to go (in my opinion).

Thanks that cleared my confusion....
do roms, such as CM7 come with there own kernals? (im a noob)

lbpiscool said:
Thanks that cleared my confusion....
do roms, such as CM7 come with there own kernals? (im a noob)
Click to expand...
Click to collapse
Read the post above yours......... most rims do have their own kernel......
Sent from my LG-P999 using Tapatalk

ClockworkMod Recovery v4.0.0.4

I've compiled a recovery.img of ClockworkMod 4.0.0.4 for anyone interested. This is actually git committish 7905c80940acfe796619631e74999202f3dd5394.
Now you're asking yourself if this is worth it: I don't believe so. It does not allow us to root devices that aren't, and it doesn't restore amend functionality. Because I don't know of any value to it, I'm not providing install instructions until there's a good reason to use it
THIS IS AN UNOFFICIAL RECOVERY, it's not supported, it might cause gnomes to steal your headphones, or the end of the world. You have been warned
I created this for no particular reason other than to test s-off fastboot flashing. Again, I don't know of any benefits of this over any other recovery.
Removed until I can solve the nandroid issues.
I could not get nandroid backup/restore to work for me...

From what ladios said,offmode charging would be the only thing.however thank-you for compiling and uploading it.
Sent from my Liberty using XDA App

nandroid backup doesn't work in this recovery :-/

s0be said:
nandroid backup doesn't work in this recovery :-/
Click to expand...
Click to collapse
it worked for me as far as ive seen?

drowningchild said:
it worked for me as far as ive seen?
Click to expand...
Click to collapse
Hmmm.... odd. I just built 4.0.0.5 which has a few bug fixes. Will see if I still have problems.

s0be said:
Hmmm.... odd. I just built 4.0.0.5 which has a few bug fixes. Will see if I still have problems.
Click to expand...
Click to collapse
I'll try to restore to see if there's any issues
Sent from my Liberty using XDA App

No issues so far
Backed up & restored fine from a full wipe
Sent from my Liberty using XDA App

Nandroid should be fine, after I've added sd-ext to recovery.fstab.
An easy customization is to put an OC kernel into recovery image. My recovery run at 806 max as default. Note that since offmode-charging (image resources) added, kernel size has become a bit limited. Building the kernel without TUN, CIFS, and WLAN, then it should be small enough to fit in the image.

Very odd... my cwm restarted every time it tried to backup or restore system. 2.5.x.x works fine. Will have adb access in a couple hours to see what's up.
Sent from my Liberty using XDA App

Still stumping me:
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at c2a6c00000000
I:Set boot command ""
SD Card space free: 10378MB
Backing up boot image...
Backing up recovery image...
Backing up system...
Starting recovery on Sat Jun 18 20:13:24 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ClockworkMod Recovery v4.0.0.5
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
mtd: successfully wrote block at c2a6c00000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
Anyone have any hints how to get more verbose errors out of CWM?

I just repo synced and built recoveryimage and it was 4.0.0.5. It backed-up with nandroid just fine, but I think it hosed the sd-ext partition as it rebuilt the dalvik cache. My dalvik is on sd-ext. So what is the best working version of 3.X that has offline charging?
Edit: Nevermind, this 2.5.0.7 version seems to be the best recovery I have found for my device. http://forum.xda-developers.com/attachment.php?attachmentid=563834&d=1302280803

the one that was posted works 100% for me?
sd-ext fine

drowningchild said:
the one that was posted works 100% for me?
sd-ext fine
Click to expand...
Click to collapse
Ill try it again. Nothing to lose but dalvik on sd-ext.

[Q] Rooted? I can't flash any roms though.

TF101. 16GB
As far as I know I am rooted. When I boot into recovery it is using ClockworkMod Recovery v3.0.2.8
Android version 3.1
Build Number
HMJ37.US_epad-8.4.4.5-20110527
Anytime I try to flash any rom I get an error 7.
What am I doing wrong? Anymore information needed to help?

ls3mach said:
TF101. 16GB
As far as I know I am rooted. When I boot into recovery it is using ClockworkMod Recovery v3.0.2.8
Android version 3.1
Build Number
HMJ37.US_epad-8.4.4.5-20110527
Anytime I try to flash any rom I get an error 7.
What am I doing wrong? Anymore information needed to help?
Click to expand...
Click to collapse
are you verifying the MD5SUM of the OS post pushing it to the SdCard.

neidlinger said:
are you verifying the MD5SUM of the OS post pushing it to the SdCard.
Click to expand...
Click to collapse
I have not. I have tried multiple sources and roms (stock and modded). I can't get any to flash.

Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.

ls3mach said:
Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.
Click to expand...
Click to collapse
are you extracting the OS are leaving it in a .zip

neidlinger said:
are you extracting the OS are leaving it in a .zip
Click to expand...
Click to collapse
It is in a zip format. When I insert my SD card into my TF101 it recognizes that it has a system file on the card.

ls3mach said:
It is in a zip format. When I insert my SD card into my TF101 it recognizes that it has a system file on the card.
Click to expand...
Click to collapse
If it's the stock ROM, you actually have to unzip it after download to get to another zip file inside.

ls3mach said:
Well, I accidentally wiped my tablet. That didn't help. The exact error is
assert failed: write_raw_image(" /tmp/blob", "staging")
E:Error in /sdcard/ASUS/Update/US_epad-User-8.6.5.21.zi[
(status 7)
Installation aborted.
Click to expand...
Click to collapse
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision

gee one said:
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?

baseballfanz said:
If it's the stock ROM, you actually have to unzip it after download to get to another zip file inside.
Click to expand...
Click to collapse
I am pretty sure I have done that. It is recognizing that their is a system file when the card is inserted.

ls3mach said:
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?
Click to expand...
Click to collapse
You could try the Team Rouge recovery but I don't know if it will help or not

ls3mach said:
It has the option to mount
/system
/cache
/data
/sdcard
I mounted all of them and tried to flash a stock rom, which has been extracted from the original zip to the (what I believe to be) update zip. Is there a way to update my CWM to one that doesn't have this issue?
Click to expand...
Click to collapse
You can mount via adb or extract the ramdisk from cwm and add staging partition to the etc/recovery.fstab
I'm not sure which versions of cwm have staging. As I said, I think roach's 3.2.0.1 has it. I'm actually using a modded version of his, but I won't post it because it will probably cause more bootloops and headaches.
sent from my cyanogen(mod) vision

You could also flash a rom that doesn't use the staging partition.
sent from my cyanogen(mod) vision

gee one said:
You could also flash a rom that doesn't use the staging partition.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I tried to flash the new ICS rom, but it wouldn't load for me either. Are you sure this is a staging issue? Also, why can't I flash the stock ROMs? After I get a new one loaded is this going to be a continuing issue?

gee one said:
Some versions of cwm don't have the staging partition mounted. Go into mounts and see if there is an option to mount staging (might as well mount system while you are at it).
If there is no option to mount staging, use adb and type
mkdir /staging (it might already exist?)
mount /dev/block/mmcblk0p4 /staging
The last chars above are zero pee four- don't mess it up!
Then re-flash the rom.
If you don't have adb in recovery, then either repackage the rom or get a recovery that has it, although I'm not sure which ones will- I think roach's 3.2.0.1 will work, but you have to mount the partitions through the menu.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I have the SDK installed and updated. How do I make those ADB commands work? I am in PROMPT and the correct folder. Sorry, I don't use this program often and haven't since I installed the mod originally and I have had my TF101 since they were new.

ls3mach said:
I have the SDK installed and updated. How do I make those ADB commands work? I am in PROMPT and the correct folder. Sorry, I don't use this program often and haven't since I installed the mod originally and I have had my TF101 since they were new.
Click to expand...
Click to collapse
The stock roms usually use the staging partition, the custom roms are hit or miss, so this could potentially be a recurring issue.
rom the command line prompt, type:
adb devices - if all is well, you'll see you tf's serial number
adb shell
su
mkdir /staging - you'll get an error if it already exists, which is fine
mount /dev/block/mmcblk0p4 /staging
exit
Then mount system in cwm and flash your rom.
Good luck
sent from my cyanogen(mod) vision

baseballfanz said:
You could try the Team Rouge recovery but I don't know if it will help or not
Click to expand...
Click to collapse
Well, that worked to flash, but now I get the Android goon when I try to get into recovery.

It sounds like it worked- if you were flashing the 86521 stock rom, it has a stock recovery on it.
You should receive the ICS update now. There is an ICS root exploit in the dev section by rhcp012345, if you want to root.
sent from my cyanogen(mod) vision

gee one said:
It sounds like it worked- if you were flashing the 86521 stock rom, it has a stock recovery on it.
You should receive the ICS update now. There is an ICS root exploit in the dev section by rhcp012345, if you want to root.
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
It did. I appreciate the help everyone. Now to get my HBoot1.5 EVO3d working. My previous one gave up the ghost

gee one said:
The stock roms usually use the staging partition, the custom roms are hit or miss, so this could potentially be a recurring issue.
rom the command line prompt, type:
adb devices - if all is well, you'll see you tf's serial number
adb shell
su
mkdir /staging - you'll get an error if it already exists, which is fine
mount /dev/block/mmcblk0p4 /staging
exit
Then mount system in cwm and flash your rom.
Good luck
sent from my cyanogen(mod) vision
Click to expand...
Click to collapse
I tried....but.....
N:\3\3>adb shell
~ # mkdir /staging
mkdir /staging
mkdir: can't create directory '/staging': File exists
~ # mount /dev/block/mmcblk0p4 /staging
mount /dev/block/mmcblk0p4 /staging
mount: mounting /dev/block/mmcblk0p4 on /staging failed: Invalid argument
~ #
Ivalid argument...any idea?

Can't mount SD

i've boot into bootloader and cilck clear storage
after doing this , my sdcard can't mount anymore
anyone can help?

leslieng509 said:
i've boot into bootloader and cilck clear storage
after doing this , my sdcard can't mount anymore
anyone can help?
Click to expand...
Click to collapse
anyone help?

If you have a custom recovery like twrp boot to recovery and go to mount and make sure sd card is ticked off
Sent from my Nocturnalized Beast

E.Cadro said:
If you have a custom recovery like twrp boot to recovery and go to mount and make sure sd card is ticked off
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
I tried to mount in the CWM recovery and it got error

TWRP is the solution
I'd Rather use TWRP, it's safer and Easier. It has SD Card Support, it's touch and with a Keyboard! you can rename your backups etc.
execute as admin and it should fastboot into TWRP...
forum.xda-developers.com/showthread.php?t=1677447
onexroot.com/one-x-roms/how-to-install-custom-rom-on-rooted-att-htc-one-xxl/
(add www at first, I couldn't add since I'm a new user.)
use a *.bat if you like;
leslieng509 said:
I tried to mount in the CWM recovery and it got error
Click to expand...
Click to collapse

leslieng509 said:
I tried to mount in the CWM recovery and it got error
Click to expand...
Click to collapse
Known issue, SD mount doesn't work on CWM for this device. CWM doesn't really support our device, and TWRP is recommended.
Does the phone boot normally, or can it be seen by ADB?

open terminal
then type
su (enter)
mkdir /sdcard/emmc (enter)
busybox mount -t vfat -o rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020 /dev/block/mmcblk1p1 /sdcard/emmc (enter)
done
Sent from my GT-P1000 using xda premium

redpoint73 said:
Known issue, SD mount doesn't work on CWM for this device. CWM doesn't really support our device, and TWRP is recommended.
Does the phone boot normally, or can it be seen by ADB?
Click to expand...
Click to collapse
everything works fine.but the phone cant find the sdcard and cant find by adb

asvantypography said:
open terminal
then type
su (enter)
mkdir /sdcard/emmc (enter)
busybox mount -t vfat -o rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020 /dev/block/mmcblk1p1 /sdcard/emmc (enter)
done
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
It didn't works...,.....

Help..

Really need help. ..

can you send me a SS?

Are you using TWRP? If so, you should be able to go into the menu and remount. If not, try using adb.

Devs recommend using TWRP because CWM is giving issues.I was in a similar situation with a wiped sd card, so what I did was to relock the boot loader, then get into fastboot, connect the device to my pc, and run the 1.85 AT&T RUU.
Sent from my HTC One X using Xparent SkyBlue Tapatalk 2

finally fixed by flashing ruu
thanks all

leslieng509 said:
It didn't works...,.....
Click to expand...
Click to collapse
asvantypography said:
open terminal
then type
su (enter)
mkdir /sdcard/emmc (enter)
busybox mount -t vfat -o rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020 /dev/block/mmcblk1p1 /sdcard/emmc (enter)
done
Sent from my GT-P1000 using xda premium
Click to expand...
Click to collapse
It worked for me. Thanks.

davidcole said:
It worked for me. Thanks.
Click to expand...
Click to collapse
dont just say thanks hit the button please
Sent from my GT-P1000 using xda app-developers app

[MOD] [PERFORMANCE] ext4 journal disabler [CM|AOSP]

The ext4 filesystem which is primarily used on android phones has a feature called "journal". This is a "file" which acts like a "middleman" when the system writes data on your storage. So before a file gets transferred to the destination a part of the file will always be at first in the journal. The benefit is that you have less chance to "loose" a file when the system is interrupted during the transfer (power failure, connection failure ...) because the journal has a copy of the part which was transferred to the final destination. So when the system restarts the device can finelize the transfer because the journal has the needed information, what exactly was transferred and what wasn't.
But this security feature has a negative impact of your I/O performance. And since a smartphone has a battery and soldered storage chips a fatal failure is much less possible than with conventional PC.
My mini ZIP disable journal on the data and cache partition, because these are the ones on which android writes data. On the system partition android just read the files and a journal will not slow down the read performance (which should be logical if you read the first part)
PS: should be logical but anyway, to use my script you need to have ext4 on cache an data. if you haven't changed the filesystem, then you will probably have ext4 because it's the stock filesystem for android
!!! if you have encrypted system this will not work !!!
so this mod dont work on OxygenOS because its has enforced encryption
the minimal binary:
Code:
#!/sbin/sh
umount /dev/block/bootdevice/by-name/cache
umount /dev/block/bootdevice/by-name/userdata
e2fsck -pv /dev/block/bootdevice/by-name/cache
e2fsck -pv /dev/block/bootdevice/by-name/userdata
tune2fs -O ^has_journal /dev/block/bootdevice/by-name/cache
tune2fs -O ^has_journal /dev/block/bootdevice/by-name/userdata

Hi, thanks for sharing, your file will work on any rom?
Sent from my OnePlus3 using XDA Labs

fanbogo said:
Hi, thanks for sharing, your file will work on any rom?
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
any rom and ext4 on data and cache

I'm using stock oxygen, update from today
Sent from my OnePlus3 using XDA Labs

fanbogo said:
I'm using stock oxygen, update from today
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
i see .. i have tested the script with adb and also the final zip before i have flashed the system. i try to solve it now. its maybe because of the encrypted partition

Ok im waiting
Sent from my OnePlus3 using XDA Labs

It doesn't install on DU 10.4 (AOSP) (same issue as OOS)

nazagan said:
It doesn't install on DU 10.4 (AOSP) (same issue as OOS)
Click to expand...
Click to collapse
is your rom encrypted?

Nope, erased by format data

nazagan said:
Nope, erased by format data
Click to expand...
Click to collapse
ok damn, it seems not to work anymore like on older phones in the past. F2FS would be anyway faster ...
ok sorry guys

Thread closed at OP's request.