It is seen that ext4 with journaling off is faster than any file system but is slightly less reliable. I have successfully removed journaling from my file system and have found no problems. I see a noticeable difference in performance as well. Also Quadrant score jumped up by 100 - 200 points.
Journaling is an ext4 filesystem log service and it involves using memory and data.So disabling journaling means that memory and data used for maintaining this service are no longer used and are available for other processes. Journaling is required in computer hard drives as a precaution for data loss in situations like unclean shutdown in power outage. And I don't think mobile phones which use flash drives ever require journaling.
Credits to hardcore for the tutorial here and to chris41g for the following idea.
Here are the scripts with cwm flashable zips I made to automatically convert a journaling ext4 to non-journaling ext4 and vice versa(to make things easier).They will work on custom kernels with ext4 support.
How to flash
Flash Journaling disabler via cwm manager or cwm recovery to disable journaling.
Flash Journaling enabler via cwm manager or cwm recovery to enable back journaling.
To disable ext4-journaling- Download journaling disabler here
To enable ext4-journaling- Download journaling enabler here
To check whether journaling is enabled or disabled type in adb or terminal after flashing-
Code:
# /data/tune2fs -l /dev/block/stl12 | grep features
If "has_journal" is present then journaling is present,i.e,output is
Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
If "has_journal" is absent then journaling is absent,i.e.,output is something like this
Filesystem features: resize_inode filetype extent sparse_super large_file
WARNING: This procedure is risky and may result in loss of data
MANUAL TUTORIAL TO DISABLE JOURNALING credits hardcore
1. Make a backup of your data using cwm.
2. Download the tune2fs zip attached to this post, extract it and copy the extracted tune2fs to /data using root explorer or adb.
3. Go to adb shell and type
Code:
$su
#mount | grep ext4
This will give something like this
/dev/stl14 on /cache type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc)
/dev/stl13 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barrier=0,nobh,data=ordered,noauto_da_alloc)
/dev/stl12 on /system type ext4 (ro,relatime,barrier=0,nobh,data=ordered,noauto_da_alloc)
/dev/block/mmcblk0p2 on /system/sd type ext4 (rw,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc)
4. We have to remove journal from the above partitions,i.e., /cache , /system and /data
So,starting with /cache the following procedure will be repeated for each partition.
a) Checking the partition
Code:
# /data/tune2fs -l /dev/block/stl14 | grep features
The output will be
Filesystem features: has_journal resize_inode filetype extent sparse_super large_file
Note the has_journal flag. We have to remove this flag.
b) fsck the partition
Code:
e2fsck -f /dev/block/stl14
Output will be-
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)?
Answer yes.If after that it asks to alter the file system you may press ctrl+c
c) Remove the journal
Code:
# /data/tune2fs -O ^has_journal /dev/block/stl14
(this is a capital "O"!)
d)Check whether journaling was removed
Code:
# /data/tune2fs -l /dev/block/stl14 | grep features
Output should be like
Filesystem features: resize_inode filetype extent sparse_super large_file
So the has_journal flag is now removed.
5) Repeat the procedure for /data and /system partitions
by replacing in the above codes /dev/block/stl13 and /dev/block/stl12 respectively
6) After you have removed journaling from all partitions- reboot.
Better if rom cooks have ext4 with journaling disabled natively, but I guess it's based on opinion..
consegregate said:
Better if rom cooks have ext4 with journaling disabled natively, but I guess it's based on opinion..
Click to expand...
Click to collapse
It would be good...by the way, I have now made cwm flashable zips to automatically disable and enable journaling,hope it works.
Nice guide skynet .
Sent from my Ultima Weapon© using XDA App
Much easier now. Disabled journal for the time being, seeing if there's a difference in normal usage.
What are the requirements to make this work? I tried it on my KPN with internal ext4 partition. Installed it via CWM but installation was aborted.
Sent from my GT-S5830 using XDA App
I tried and it worked well. I will use this for my rom and give u credit. Tks u so much
Stupid me I installed the other zip file . Now it works .
Sent from my GT-S5830 using XDA App
I don't actually see any performance boost , but I did get a boost in quadrant scores .
Journaling enabled:
{
"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"
}
Journaling disabled:
Sent from my Ultima Weapon© using XDA App
EmoBoiix3 said:
I don't actually see any performance boost , but I did get a boost in quadrant scores .
Sent from my Ultima Weapon© using XDA App
Click to expand...
Click to collapse
I am not a quadrant fan but thanks for the scores. I went for no journal method because Journaling is filesystem log service and it involves using memory and data.
So disabling journaling means that memory and data used for maintaining this service are no longer used and are available for other processes. And I don't think mobile phones ever require journaling.
Thanks, flashable zip working.
Thanks. The zip is working and my battery usage 'looks nice' so far.
Sent from my GT-S5830 using xda premium
skynet28 said:
I am not a quadrant fan but thanks for the scores. I went for no journal method because Journaling is filesystem log service and it involves using memory and data.
So disabling journaling means that memory and data used for maintaining this service are no longer used and are available for other processes. And I don't think mobile phones ever require journaling.
Click to expand...
Click to collapse
No , thank you for making this
Which is why you don't need ext4 for sdcards, journaling on it is a waste of power.
consegregate said:
Which is why you don't need ext4 for sdcards, journaling on it is a waste of power.
Click to expand...
Click to collapse
Yes I agree..sdcard ext4 partition is overkill.Ext2 is enough.
But Ext4 in internal partitions is useful because of its unique features like Improved timestamps,Multiblock allocation,faster file system checking which are important for regular and critical system applications and services. But we make sdcard partition for apps which are not system critical and thus not really affect performance .
So I think ext4 without journaling in internal partitions and ext2 in sdcard is the way to go
Will this work on sgs?
burakgon said:
Will this work on sgs?
Click to expand...
Click to collapse
You can disable journaling in any ext4 file system but here the method is specific for galaxy ace since partitions are different on different phones.So in the tutorial you have to replace the partition location with SGS ones. Better look in your own forums.Hardcore had written the original tutorial.
The cwm flashable files made by me are for galaxy ace only.
Skynet28,
I tried to disable journaling using your zip file but it was only successful for two of my partition.
You can refer to the output from terminal:
$ export PATH=/data/local/bin:$PATH
$su
#/data/tune2fs -l /dev/block/stl14 | grep features
Filesystem features: resize_inode filetype extent sparse_super large_file
# /data/tune2fs -l /dev/block/stl13 | grep features
Filesystem features: has_journal resize_inode filetype needs_recovery extent sparse_super large_file
# /data/tune2fs -l /dev/block/stl12 | grep features
Filesystem features: resize_inode filetype extent sparse_super large_file
#
I tried doing it manually, but my Ace crash and I had to reformat my Acr.
Sent from my GT-S5830 using xda premium
Hi,
This worked great on my ace running stock XWKPN 2.3.3 using cf-root kernel b-80 and ext4 partitions.. hopefully see some speed boost...
Thanks for zips !
Related
Hello Community!
First off, the original thread - http://forum.xda-developers.com/showthread.php?t=851407
I wanted to bring this to everyone's attention. I have seen many requests for converting all partitions to EXT2 as it is faster than EXT4. So far the only way to do this is with Z4 modded kernels. Well Hardcore over in the i9000 forums (<3 their development section) posted a method a achieve the next best thing - EXT4 with no journaling! I have yet to test this out, but I will be doing so tonight and posting results. I plan on trying this with ULF (which has been confirmed to work) and ttabbal's all EXT4 Dragon Rom (TW Beta Section). The process just simply removes journaling from EXT4 partitions, so it's as fast or faster than EXT2 but with all the added benefits of being EXT4.
Thought some people might find this useful... enjoy!
Update - I can confirm this works with ULF. I was able to remove journaling from all three partitions no problem following the instructions below. I had no data loss or FC's upon reboot. Below are Hardcore's instructions from the original thread - link posted at the top. I in no way helped in this, just merely sharing what I found. All props go to Hardcore.
hardcore said:
WARNING: This procedure is risky and may result in loss of data.
This is a follow up to findings made in this thread: http://forum.xda-developers.com/showthread.php?t=819580
Many people have been asking for an ext2 lagfix. You can get something similar but (arguably) better: ext4 with no journaling. Ext4 no-journal performs as fast or faster than ext2 because of performance improvements made in ext4.
Quadrant comparison for ext4 /data-only lagfix:
ext4 scores about 1500, ext4 no-journal scores about 1650.
This should work with existing kernels that support ext4 lagfixes. It's tested on a ULFK kernel (SpeedMod).
WARNING: Turning off journaling makes your data more susceptible to getting corrupted, although the risk is small.
Disclaimer: No promises that this will work for you, or that it won't corrupt your data. Try this at your own risk.
Step 0: You start off by applying an ext4 lagfix. If you are already using an ext4 lagfix, you can skip this step.
For ULFK kernels, this is either:
- "Voodoo" ext4 /data
- No-RFS advanced ext4
After the lagfix has been successfully applied and your phone is up and running properly, then you can proceed to convert the ext4 partitions.
Step 1: Make a backup of your data, using CWM (recommended). If anything goes wrong, you can restore the backup later.
Step 2: Download the tune2fs file attached to this post (works for FROYO roms only), and copy it to /data as /data/tune2fs:
adb push tune2fs /sdcard/
adb shell
# su
# cp /sdcard/tune2fs /data/
Procedure if your kernel has ro.debuggable enabled:
Step 3: If your kernel has ro.debuggable enabled, then boot your phone into recovery mode. Then run adb in root mode:
adb root
(wait for adbd to restart)
adb shell
Copy tune2fs to the /tmp folder.
# cp /data/tune2fs /tmp/
If you don't have ro.debuggable enabled, "adb root" will give you an error. Go to Step 3A in the next section.
Step 4: Now in ADB shell, find out which partitions are ext4:
# mount | grep ext4
mount | grep ext4
/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
In this example, the 3 partitions are:
/dev/block/mmcblk0p2 (/data)
/dev/block/stl10 (/dbdata)
/dev/block/stl11 (/cache)
Repeat Steps 5 to 9 for every partition you want to remove the journal from.
The next steps show the procedure for /dev/block/mmcblk0p2 (/data).
Step 5: Unmount the partition:
umount partition_mount_point
for example:
# umount /data
Step 6: Check if there is a journal:
# /tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" in the features. It means this partition has a journal.
Step 7: Fsck the partition:
# e2fsck -f /dev/block/mmcblk0p2
Step 8: Remove the journal:
# /tmp/tune2fs -O ^has_journal /dev/block/mmcblk0p2
(this is a capital "O"!)
Step 9: Check if the journal was removed:
# /tmp/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" is NOT there.
Done for this partition.
Step 10: After you've remove the journal from all the partitions you wanted to, shutdown the phone by pressing the power button.
DONE. You only need to do this procedure once and it'll "stick" until the next time you re-format the partition.
--------------------------------------------------
Procedure if you don't have ro.debuggable enabled:
Step 3A: If you kernel does not have ro.debuggable enabled, then you can try doing this using normal adb with su while the phone is running. But this is much more risky.
To lower the risk, do this right after booting, wait for the Media Scan to complete.
adb shell
# su
Step 4A: Now in ADB shell, find out which partitions are ext4:
# mount | grep ext4
mount | grep ext4
/dev/block/mmcblk0p2 on /data type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl10 on /dbdata type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
/dev/block/stl11 on /cache type ext4 (rw,noatime,barrier=0,data=writeback,noauto_da_alloc)
In this example, the 3 partitions are:
/dev/block/mmcblk0p2 (/data)
/dev/block/stl10 (/dbdata)
/dev/block/stl11 (/cache)
Repeat Steps 5A to 8A for every partition you want to remove the journal from.
The next steps show the procedure for /dev/block/mmcblk0p2 (/data).
Step 5A: Check if there is a journal:
# /data/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" in the features. It means this partition has a journal.
Step 6A: Fsck the partition:
# e2fsck -f /dev/block/mmcblk0p2
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.
Do you really want to continue (y/n)?
Answer yes.
Step 7A: Remove the journal:
# /data/tune2fs -O ^has_journal /dev/block/mmcblk0p2
(this is a capital "O"!)
Step 8A: Check if the journal was removed:
# /data/tune2fs -l /dev/block/mmcblk0p2 | grep features
You should see something like this:
Filesystem features: ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
You should see "has_journal" is NOT there.
Done for this partition.
Step 9A: After you've remove the journal from all the partitions you wanted to, shutdown the phone by pressing the power button. Reboot the phone and hope everything works.
DONE. You only need to do this procedure once and it'll "stick" until the next time you re-format the partition.
Click to expand...
Click to collapse
This is a lagfix for a lagfix? A metalagfix?
Sent from my SGH-T959 using XDA App
Super saiyan lagfix
grennis said:
This is a lagfix for a lagfix? A metalagfix?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This simply takes an existing ext4 lagfix and optimizes performance at the slight expense of reliability.
I'm more interested in this magical dragron rom you speak of. I cant seem to find it. Do you have a link?
wildklymr said:
I'm more interested in this magical dragron rom you speak of. I cant seem to find it. Do you have a link?
Click to expand...
Click to collapse
It's listed in the donators section of ~tw~'s forums.
This really sounds like a great idea. Is there any way you, or a dev could possibly turn the whole process into a CWM flashable .zip?
This is probably the best thing that's happened to my phone... Its flying...!!!
How good is this one compared to JFS overkill?
Idk, that seems like a lot of work for someone who's lazy like myself
djquick said:
Idk, that seems like a lot of work for someone who's lazy like myself
Click to expand...
Click to collapse
no it's not that much work and I'm a total newbie... ran into some newbie minor issues (kept typing 'unmount' instead of 'umount' lol and had to use chmod on the file tune2fs) but otherwise quite painless...
and now onto testing it for the day or two until the next rom release ...
djquick said:
Idk, that seems like a lot of work for someone who's lazy like myself
Click to expand...
Click to collapse
Sonnislav said:
no it's not that much work and I'm a total newbie... ran into some newbie minor issues (kept typing 'unmount' instead of 'umount' lol and had to use chmod on the file tune2fs) but otherwise quite painless...
and now onto testing it for the day or two until the next rom release ...
Click to expand...
Click to collapse
It looks like a lot of work but in actuality is quite simple. Many of the steps are just verification steps so you can see that it worked. Been rocking this for 2 full days and I must say the improvement is quite noticeable.
Bignjuicyjc said:
This really sounds like a great idea. Is there any way you, or a dev could possibly turn the whole process into a CWM flashable .zip?
Click to expand...
Click to collapse
I would love to pack this into a zip for everyone, but I'm afraid I don't have much technical "know-how" when it comes to stuff like that. Maybe if this peaks some interest one of these more bonafied devs could provide that for everyone.
So, After doing some reading of the thread in the I9000 Dev forum, I decided to go ahead and give this a try. I removed the journaling from all three Ext4 partitions. The process was rather painless and smooth.
I'll report back a little later after I've had some time to test it out.
I was only able to remove the journaling from /data(/dev/block/mmcblk0p2)... I typed "mount | grep ext4.. It only displayed the /data/ partition.. If the other partitions dont show, does it mean the other partitions dont have journaling?... But wouldnt they still show...? Im on obsidionv5... With eugene b oc 1125 kernel.. Im getting around 1700 in quadrant
Sms vibrant black body glove
Rom-macnutR2 kernel #53
Latest cwm
Black Htc G1
Sparksmod1.7
Latest radio death spl
Oc kernel 617mhz jit enabled ram hack
Are you sure you have an ext4 file system on the other partitions?
diazf09 said:
I was only able to remove the journaling from /data(/dev/block/mmcblk0p2)... I typed "mount | grep ext4.. It only displayed the /data/ partition.. If the other partitions dont show, does it mean the other partitions dont have journaling?... But wouldnt they still show...? Im on obsidionv5... With eugene b oc 1125 kernel.. Im getting around 1700 in quadrant
Click to expand...
Click to collapse
well I am using r12 with 1125 kernel... also I went into the lagix options from the recovery menu and chose the 'No-RFS advanced ext4' ... my procedure was pretty much a mirror of the example... if you only saw /data then it sounds like you chose the 'voodoo' lagfix from ULF...
btw I am not seeing an improvement on battery life after almost a full day... it does seem a bit more responsive...
diazf09 said:
I was only able to remove the journaling from /data(/dev/block/mmcblk0p2)... I typed "mount | grep ext4.. It only displayed the /data/ partition.. If the other partitions dont show, does it mean the other partitions dont have journaling?... But wouldnt they still show...? Im on obsidionv5... With eugene b oc 1125 kernel.. Im getting around 1700 in quadrant
Sms vibrant black body glove
Rom-macnutR2 kernel #53
Latest cwm
Black Htc G1
Sparksmod1.7
Latest radio death spl
Oc kernel 617mhz jit enabled ram hack
Click to expand...
Click to collapse
gawd...i'm prolly gonna get laughed out of the forums for this one. but, umm, what key on the keyboard is the symbol between 'mount' and 'grep'?
Button key above 'enter' using shift...
Sent from my GT-I9000 using XDA App
What's the point / advantage in running unjournaled EXT4 when you can already run EXT2 this way (minus the extra work)?
It is quite stupid to remove journal from FS just for a higher score,
then put your data in danger!
*** I am not responsible for any damage, lost or explosion. So, try it as your own risk ***
I successfully mount my 250G powered external HD with NTFS partition on this post: http://forum.xda-developers.com/showpost.php?p=14650094&postcount=146
Here are the steps:
1. Root is a must
2. Install any terminal emulator from the market.
3. d/l and extract the ntfs.ko to your i9100
4. load the ntfs.ko with insmod (update: Some custom kernel doesn't work with module, try CF-root kernel or any stock kernel if you have problem loading the module)
5. Connect your drive with OTG.
6. Don't need to worry about "USB storage blank or has unsupported file" complaint in the notification area. But you may need a Y splitter USB cable with power supply if you got an high power consumption complaint.
7. Follow the screen shoot for the mounting command. "iocharset=utf8" is needed if you have non English files/folders name
8. Verify the mount with ls command
9. Verify non root apps (e.g. Astro File Manager) are able to read the files
10. After you done, make sure no process is accessing the mount, then un-mount using the umount command. You may want to remove the module using rmmod.
{
"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"
}
[request] Can this be done with a sdcard? That would be nice.
Maybe built in a rom
Awesome work il give it a try.. Just one question lol whats insmod?
Sent from my GT-I9100 using XDA App
I have a problem with "mount" - "mount: can't read /etc/fstab: No such file or directory". What's wrong? I can't find fstab in /etc, there is only vold.fstab.
Try
#cat /proc/mounts > /etc/fstab
#chmod 644 /etc/fstab
Now I have /etc/fstab but "mount: can't find /dev/block/sd in /etc/fstab".
How can I build a good fstab???
Edit: nevermind, I used a bad command, it works now but read only, so I'm waiting for a full working module. Thanks very much for your works jackleung. Best regards!
jackleung said:
*** I am not responsible for any damage, lost or explosion. So, try it as your own risk ***
I successfully mount my 250G powered external HD with NTFS partition on this post: http://forum.xda-developers.com/showpost.php?p=14650094&postcount=146
Here are the steps:
1. Root is a must
2. Install any terminal emulator from the market.
3. d/l and extract the ntfs.ko to your i9100
4. load the ntfs.ko with insmod
5. Connect your drive with OTG.
6. Don't need to worry about "USB storage blank or has unsupported file" complaint in the notification area. But you may need a Y splitter USB cable with power supply if you got an high power consumption complaint.
7. Follow the screen shoot for the mounting command. "iocharset=utf8" is needed if you have non English files/folders name
8. Verify the mount with ls command
9. Verify non root apps (e.g. Astro File Manager) are able to read the files
10. After you done, make sure no process is accessing the mount, then un-mount using the umount command. You may want to remove the module using rmmod.
Click to expand...
Click to collapse
Can you please upload a video showing how to do it for noobs
Sent from my GT-I9100 using XDA App
Waiting for my OTG Cable to arrive and will 100% try this. Do you get a good playback speed of 720p/1080p videos using ntfs drives?
hakkinenvthh said:
Edit: nevermind, I used a bad command, it works now but read only, so I'm waiting for a full working module. Thanks very much for your works jackleung. Best regards!
Click to expand...
Click to collapse
What command have you use finally? I was thinking you may have different block device instead of hda1.
For writing, we may need NTFS-3G but that I don't know where to get the source for **Android**. And I really don't have time to dig into that yet.
mythoc said:
Waiting for my OTG Cable to arrive and will 100% try this. Do you get a good playback speed of 720p/1080p videos using ntfs drives?
Click to expand...
Click to collapse
I haven't try. Practically, media sharing over Samba (cifs) is more useful for me. I can watch 720p video over the wireless G network shared folders.
@Tulips, it should work but may not be useful without write ability.
insmod = insert modules
lsmod = list modules
rmmod = remove modules
okey, sdcard works using the device /dev/block/mmcblk1p1, but as you said read only.
@jackleung : Where did you get this module from? Did you build it yourself from the kernel source, or downloaded it from somewhere else? As far as I understood, the linux kernel now fully supports ntfs rw capabilities (for several years, if I'm not mistaken).
Tulips said:
@jackleung : Where did you get this module from? Did you build it yourself from the kernel source, or downloaded it from somewhere else? As far as I understood, the linux kernel now fully supports ntfs rw capabilities (for several years, if I'm not mistaken).
Click to expand...
Click to collapse
I built from the kernel source d/l from Samsung. Here is the situation stated in wiki:
The ability to read and write to NTFS is provided by the NTFS-3G driver. It is included in most Linux distributions. Other solutions exist as well:
Linux kernel 2.2: Kernel versions 2.2.0 and later include the ability to read NTFS partitions
....
Note that all three userspace drivers, namely NTFSMount, NTFS-3G and Captive NTFS, are built on the Filesystem in Userspace (FUSE), a Linux kernel module tasked with bridging userspace and kernel code to save and retrieve data.
Click to expand...
Click to collapse
I do find the FUSE in the kernel source, but I believe we still need some user space program like NTFS-3G to manage it.
jackleung said:
What command have you use finally? I was thinking you may have different block device instead of hda1.
For writing, we may need NTFS-3G but that I don't know where to get the source for **Android**. And I really don't have time to dig into that yet.
Click to expand...
Click to collapse
I used exactly the same to you I think it's better if you can make it mounted automatically (by modify the kernel???) or make a software to do it
I can mount a NTFS microsd but after that the phone can't be recognized by the PC, unless I format it by the phone
mythoc said:
Waiting for my OTG Cable to arrive and will 100% try this. Do you get a good playback speed of 720p/1080p videos using ntfs drives?
Click to expand...
Click to collapse
well i watched 1080p clips and they worked perfectly fine, the file size was 8gb, not sure about bitrate or anything though
why is this not in the Dev Section???!!
[email protected]!
My first successful attempt with ntfs-3g can be found here: http://forum.xda-developers.com/showpost.php?p=15001824&postcount=23
jastonas said:
why is this not in the Dev Section???!!
[email protected]!
Click to expand...
Click to collapse
Because nothing being developed. I simply compiled a module from existing source code.
I wrote two small shell scripts for mount and unmount.
Both i can run in GScript (free light version from market).
The first ist mounting:
Code:
insmod /mnt/sdcard/ntfs.ko
mkdir /mnt/sdcard/usbStorage/usb_ntfs
sleep 1
mount -t ntfs -o rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,iocharset=utf8 /dev/block/sda1 /mnt/sdcard/usbStorage/usb_ntfs
And this one for unmounting:
Code:
umount -f /mnt/sdcard/usbStorage/usb_ntfs
rmmod ntfs
Both scripts are attached and if they are saved on sdcard in a folder namend "gscript" they can be imported directly into GScript.
The ntfs.ko file has to be placed in the root folder of the SD-Card (/mnt/sdcard/ntfs.ko).
@jackleung: Thank you for compiling
Ps: sorry for my bad english... ;-)
Could someone please upload a video on youtube showing how to do it. I dont understand all this mount and unmount.. Do i need to unmount before i take out the usb drive?
Sent from my GT-I9100 using XDA App
Could you compile ext3 kernel module too, please ?
I'm trying to mount a linux image but there's no ext3 support so I cannot mount it
alx5962 said:
Could you compile ext3 kernel module too, please ?
I'm trying to mount a linux image but there's no ext3 support so I cannot mount it
Click to expand...
Click to collapse
Maybe ext2/3 doesn't even need a module? Could someone just try this command?
Code:
mount -t ext2 -o uid=1000,gid=1015,iocharset=utf8,umask=000 /dev/block/sda1
(.../dev/block/mmcblk1p1 for microSD)
Help wat do i do i keep getting this
Sent from my GT-I9100 using XDA App
How to install:
Just unzip to your /sdcard
http://xt720.ru/Files/Patchs/or-147-xt720-fix2.zip
my recovery alrealy support ext2,3,4, nilfs2 (6 month ago)
if you want to add filesystem support edit switch.sh (insmod your modules) and edit to
echo "/dev/block/mmcblk0p2 /sddata auto defaults 0 0" >> /etc/fstab
echo "/dev/block/mmcblk0p2 /sddata auto defaults 0 0" >> /etc/fstab
We already have it in switch.sh.
But thanks! =)
Just curious: what changed in open_rcvr.STR?
fjfalcon said:
echo "/dev/block/mmcblk0p2 /sddata auto defaults 0 0" >> /etc/fstab
We already have it in switch.sh.
But thanks! =)
Click to expand...
Click to collapse
i edit this part
#app2ext partition on sdcard
if [ -b /dev/block/mmcblk0p2 ] ; then
mkdir /sddata
insmod "$MODPATH/jbd.ko"
insmod "$MODPATH/ext3.ko"
insmod "$MODPATH/ext2.ko"
insmod "$MODPATH/crc16.ko"
insmod "$MODPATH/jbd2.ko"
insmod "$MODPATH/mbcache.ko"
insmod "$MODPATH/ext4.ko"
insmod "$MODPATH/nilfs2.ko"
echo "/dev/block/mmcblk0p2 /sddata auto defaults 0 0" >> /etc/fstab
#e2fsck -p /dev/block/mmcblk0p2
fi
i remove e2fsck for nilfs2
#chek linux version
LVER=`uname -r | awk '{split($0,a,"-"); print a[1]}'`
MODPATH="/lib/modules/$LVER"
also i add it
it will auto recognize kernel's version and auto mount current modules
I took your OpenRecovery and added/fixed some things:
'Power Off' menu option
'Toggle Display Brightness' menu option (to reduce battery drain--alternates between bright/dim)
Fixed nandroid backup all (by hiding the partitions that don't work)
Fixed 'Wipe Dalvik Cache'
Renamed 'Applications Menu' to 'Utilities'
Added a symbolic link: /sd-ext -> /sddata
Updated e2fsck to a 1.41.10 (for ext4 support)
Added 'SD Card Utilities'
'Scan FAT partition for errors'
'Scan ext partition for errors'
Can convert ext2->ext3, ext2->ext4, ext3->ext4 (requires ROM support)
'Save diagnostics to /sdcard/sdcard-info.txt' for debugging
Eventually this will also manage the app/link2sd directories
Github: https://github.com/Mioze7Ae/openrecovery_xt720
EDIT: updated with statically-compiled fsck_msdos, tune2fs, e2fsck, and mke2fs from the CM6.3.0 source
Mioze7Ae said:
I took your OpenRecovery and added/fixed some things:
'Power Off' menu option
'Toggle Display Brightness' menu option (to reduce battery drain--alternates between bright/dim)
Fixed nandroid backup all (by hiding the partitions that don't work)
Fixed 'Wipe Dalvik Cache'
Renamed 'Applications Menu' to 'Utilities'
Added a symbolic link: /sd-ext -> /sddata
Updated e2fsck to a 1.41.10 (for ext4 support)
Added 'SD Card Utilities'
'Scan FAT partition for errors'
'Scan ext partition for errors'
Can convert ext2->ext3, ext2->ext4, ext3->ext4 (requires ROM support)
'Save diagnostics to /sdcard/sdcard-info.txt' for debugging
Eventually this will also manage the app/link2sd directories
Github: https://github.com/Mioze7Ae/openrecovery_xt720
Click to expand...
Click to collapse
Awesome nice wok man
The SD Card Utilities aren't working if CM6 isn't installed. I need to find a tune2fs that is statically linked. I thought this one was, but I was wrong.
Edit: fixed now in -fix4
What would it take to incorporate these changes into Androidiani OR?
I compiled static binaries for e2fsprogs and fsck_msdos and updated the zip. I should be working now. http://forum.xda-developers.com/showpost.php?p=16812349&postcount=7
3rdstring said:
What would it take to incorporate these changes into Androidiani OR?
Click to expand...
Click to collapse
Some of these changes are pretty easy. Others are a little more involved. You can look at the diffs in github and port ones that you'd like. Eventually I'd like to merge the functionality of both but I'm focusing on OR for now. You can look at what went into each change by looking at the "Commits" tab at github and then clicking on the commit number on the far right side for a particular change and you'll see what changes were made to which files. For example this is the Toggle Display Brightness change.
I can't get neither one of my sdcards ext4 to mount. I wonder if it might be cause I started with CM6.3? Instead of upgrading from CM6.1 to CM6.3? Just a thought since some of us can and can't mount ext4
LibertyMonger said:
I can't get neither one of my sdcards ext4 to mount. I wonder if it might be cause I started with CM6.3? Instead of upgrading from CM6.1 to CM6.3? Just a thought since some of us can and can't mount ext4
Click to expand...
Click to collapse
Can you install the *-fix4 openrecovery and use
OR > SD Card Utilities > Save diagnostics
And then post the /sdcard/sdcard-info.txt?
Do you have a nandroid of your ext2 partition? If so, try restoring it and the using SD Card Utilities to convert it to ext4.
Sent from my MilestoneXT720 using XDA Premium App
Mioze7Ae said:
Can you install the *-fix4 openrecovery and use
OR > SD Card Utilities > Save diagnostics
And then post the /sdcard/sdcard-info.txt?
Do you have a nandroid of your ext2 partition? If so, try restoring it and the using SD Card Utilities to convert it to ext4.
Sent from my MilestoneXT720 using XDA Premium App
Click to expand...
Click to collapse
Yeah I will post the /sdcard/sdcard-info.txt here but it says the same as what fjfalcon was quoting. And yes I do have a Nandroid of ext2 but never tried to restore it yet. I will try now...
L'enfer c'est les autres...
Mioze7Ae said:
L'enfer c'est les autres...
Click to expand...
Click to collapse
Hell is other people? lol
***Here it is View attachment sdcard-info.txt
Are you referring to the info.txt that fjfalcon posted in the CM6 thread? The commands I gave there weren't correct. In any case the sdcard-info.txt produced by *-fix4 are much expanded and look quite different... I can't find any other post by fjfalcon...
Sent from my MilestoneXT720 using XDA Premium App
Mioze7Ae said:
Are you referring to the info.txt that fjfalcon posted in the CM6 thread? The commands I gave there weren't correct. In any case the sdcard-info.txt produced by *-fix4 are much expanded and look quite different... I can't find any other post by fjfalcon...
Sent from my MilestoneXT720 using XDA Premium App
Click to expand...
Click to collapse
Oh sorry Mz didn't mean to make you look for it, I was talking about when he was saying how some aren't mounting. Anyway I posted it above your last post. I have my ext2 restored. I will try to convert it tomorrow. thanks man.
LibertyMonger said:
***Here it is View attachment 694819
Click to expand...
Click to collapse
Ok, try creating an empty /sd-ext/app|/sddata/app directory and reboot. Then go back to OR and recreate the sdcard-info.txt
Mioze7Ae said:
Ok, try creating an empty /sd-ext/app|/sddata/app directory and reboot. Then go back to OR and recreate the sdcard-info.txt
Click to expand...
Click to collapse
I'm sorry not sure what you mean here "empty /sd-ext/app|/sddata/app directory"
app|?
I think I got it... rebooting...
{
"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"
}
INT2EXTV2+ Posted
If you like it please click thanks on this post and give it a rating
Thanks to all users and contributors
About:
CronMod INT2EXT was wrote for use in my rom with the goal to achive a stable and fast way of moving the data partition of your phone to the sd-ext partition, they are available for all users and developers to use in any rooted rom with init.d support.
CronMod INT2EXT scripts are the first universal INT2EXT method released
Developer Stuff Next Post
Features:
(All scripts are tested on Android 2.3.7 - 4.2.2)
INT2EXT
-Mounts /sd-ext to /data
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT4
-Mounts /sd-ext to /data
-Works with EXT 4 filesystem
-ZipAligns /data/app on every boot
-No symlinks
INT2EXT4+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 4 filesystem
-ZipAligns /data/app on every boot
-No symlinks
INT2EXTV2+
-Mounts /sd-ext to /data
-Leaves /data/data on internal for speed
-Works with EXT 2/3/4 filesystems
-ZipAligns /data/app on every boot
-No symlinks
-Supports SWAP2INT
-Completely universal (Testing is needed)
Prerequisites:
-Rooted Rom with init.d support
-SD-EXT partition
-100mb internal is needed for every 500mb sd-ext
SD Card Partitioning:
Partition 1 - Fat32
Partition 2 - Ext 2/3/4
Install:
(Instructions based on ClockWorkMod recovery)
-Download Chosen Script Below
-Place on root of your sdcard
-Reboot Recovery
-Select "install zip from sdcard"
-Select "choose zip from sdcard"
-Select "CronMod-****_signed"
-Select "mounts and storage" category
-Select "format /sd-ext"
-Reboot
(if you already use a A2SD/D2EXT/INT2EXT/M2SD script then you will need to remove it completely)
Downloads:
(Please leave feedback)
INT2EXT
INT2EXT+ (Recommended and featured in CronMod Roms)
INT2EXT4
INT2EXT4+
INT2EXTV2+ (This script is a new int2ext script that should fix all bugs, it cannot be flashed over previous versions, please test and leave feedback)
Dalvik-Cache Wipe Tool (This is for wiping /dalvik-cache when running a INT2EXT script)
Extra:
Bravo/Bravoc GB thread
Bravo/Bravoc JB thread
Dream thread
Sapphire thread
Bugs:
-Some phones can experience a low sound bug (fix: run fix-permissions or try INT2EXTV2+)
Credits
-Wes Garner - "Auto ZipAlign Script"
-CyanogenMod - "Bind Cache Script"
-Matermind1024 "Help with resolving IMEI and Baseband issues"
-vvFICKvv, DK75, and Dark Passenger "Help to fix compatibility issues with Android 4.2.x"
[email protected] "Code to check if mmcblk0p2 exists"
-BlazinReign (my girlfriend) "donating her old laptop to the cause, and putting up with my development work "
-XDA "hosting the fourms"
Donators
(if you make a donation and your name is not here send me a pm)
[URL="https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=RXYPT5A5ACJ7W"]
[/URL]
Developer Area
Developer area
Info
These scripts are for use in your roms if you like them and want to include them all i ask is that you give me proper credit in your thread.
Instructions
To include one of my scripts in your rom just add it to the init.d folder and rename it to 40a2sd/40d2ext/40int2ext depending on the chosen script, if you choose a d2ext/int2ext script then remove the "06mountdl" or "06BindCache" if they exist as the script will do this from now on.
CronMod A2SD/D2EXT/INT2EXT Scripts for Developers
Nice job with all these scripts. I will give it a try in my ported rom, just one question: it will be activated from the first boot or users have to activated from terminal?
rmg2 said:
Nice job with all these scripts. I will give it a try in my ported rom, just one question: it will be activated from the first boot or users have to activated from terminal?
Click to expand...
Click to collapse
They activate on boot and do not require a reboot after firstboot like most d2ext
I can successful install A2SD++ in my Hauwei v8150 w/CM7.2 RC3 ROM and
working normal but Partition 2 of SD card only can format to Ext 3 due to
class-4 limitation!
Thanks so much for your effort!!!
jackson0829 said:
I can successful install A2SD++ in my Hauwei v8150 w/CM7.2 RC3 ROM and
working normal but Partition 2 of SD card only can format to Ext 3 due to
class-4 limitation!
Thanks so much for your effort!!!
Click to expand...
Click to collapse
thanks for the feedback glad you like it
D2EXT or D2EXT+
Hi!
Which one is the best choice for a low-RAM device like a HTC Magic 32B?
Which are the expected features for the incoming INT2EXT script?
Data2ext+ is working well in my device... Thanks for your effort!!!
:good:
gonzalocav said:
Hi!
Which one is the best choice for a low-RAM device like a HTC Magic 32B?
Which are the expected features for the incoming INT2EXT script?
Data2ext+ is working well in my device... Thanks for your effort!!!
:good:
Click to expand...
Click to collapse
i prefer the d2ext+, the int2ext is like d2ext but uses no symlinks
what is the difference between these and mount2sd?? and i like to install d2ext+ or int2sd+ for euroskank rom.is it possible?and what is the best?
siavash2death said:
what is the difference between these and mount2sd?? and i like to install d2ext+ or int2sd+ for euroskank rom.is it possible?and what is the best?
Click to expand...
Click to collapse
i dont use mount2sd so i am unsure, i would recommend if you need stability to use d2ext+ because the int2ext scripts are not long term tested.
Works with the wildfire s, no need to reboot twice to get d2ext+ working, in first boot after rom install working flawlessly. Thanks
andreasf93 said:
I am unsure what to use. I have a Galaxy Mini with very low internal memory. I should install A2SD++ right?
Sent from SGM using CyanMobile
Click to expand...
Click to collapse
try a d2ext script first they give the most space, if you find it to slow use a a2sd script instead
Currently trying A2sd++ on Lg500h Cm7 nightly 7/01. Simple enough to setup, and works flawlessly, keep up the good work :thumbup:
Sent from my LG-P500 using xda app-developers app
is possible to use this script in a sense rom? thank you
katurras said:
is possible to use this script in a sense rom? thank you
Click to expand...
Click to collapse
possibly i have not tried, i have tried it in ics and gb, if you try please let me know the results and i will try to write one for sense if it does not work
andreasf93 said:
I tried both D2EXT and A2SD on cm7.2 official galaxy mini and none worked. Applications get installed in internal memory as usual.
Click to expand...
Click to collapse
then somthing is wrong with your partitions
what is your partition table?
edit: in terminal emulator run "df" if you use d2ext you will see a mount called /data_internal if you do it is working, if you use a2sd you will see mounts called /data/app and /data/app-private and maybe more depending on the chosen script if you do it is working
croniccorey said:
possibly i have not tried, i have tried it in ics and gb, if you try please let me know the results and i will try to write one for sense if it does not work
Click to expand...
Click to collapse
does not work.
Thanks for your effort to keep our old HTC Magic alive
only tried A2SD
katurras said:
does not work.
Thanks for your effort to keep our old HTC Magic alive
only tried A2SD
Click to expand...
Click to collapse
thank you i will try to make 1 for sense roms
hi
getting Status (0) error.what am i doing wrong
Running df
croniccorey said:
then somthing is wrong with your partitions
what is your partition table?
edit: in terminal emulator run "df" if you use d2ext you will see a mount called /data_internal if you do it is working, if you use a2sd you will see mounts called /data/app and /data/app-private and maybe more depending on the chosen script if you do it is working
Click to expand...
Click to collapse
I thought I installed D2EXT+ and it was working. But I see this image and I don't know now...
Is it working?
{
"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"
}
I present you Android Ultimate Toolbox Pro, the ultimate Android utility! As the name says, it's a toolbox-like program that offers many features that make the usually not-so-easy tasks easier.
Caution! This program is not foolproof! Do not try to outsmart it by playing tricks, because you may result with an expensive brick in the worst case!
Requirements
Microsoft .NET Framework 4 (Client Profile is also needed)
Java JDK and JRE and Android SDK
Key features
Update.zip creator
Update.zip signer
Flash kernels
Flash recovery images
Flash upate.zip
Flash system images
Flash data images
Flash splash images
Install APKs (system and user)
Uninstall APKs (system and user)
Unpack APKs
Repack APKs
Sign APKs
Deodex APKs, Jars (both computer and device)
Zip-align APKs
Check MD5 sums
File manager
Root checker
Root your device
Unroot device
Logger (logcat and dmesg)
Rebooter (normal reboot, reboot in recovery, reboot in bootloader, reboot from fastboot)
Backup manager
Backup/restore apps NEW!!
Device ID configurator (device name, build number, Android version)
Unlock bootloader
Lock bootloader
Wipe (system, data, cache, boot, recovery)
And much more to come!
Note: make sure to read the help topics before using Android Ultimate Toolbox Pro.
Download
(If you don't see the download button, click here)
(If you don't see the changelog button, click here)
Latest version: 1.2.0.0
Credits
fdespotovski - icon
RegawMod - AndroidLib library
Google - aapt and zipalign binaries
Ryszard Wiśniewski (brut.alll) and Connor Tumbleson - apktool
Creators of smali and baksmali - smali and baksmali binaries
Martin Gagne - loading circle
cdesai - help
Rebellos - help
Zoran Despotovski - tester
Special thanks goes to my supporters bigrammy, imilleson and DeepUnknown. Thanks guys, you're awesome!
Error reporting
If you want to report a misbehavior of Android Ultimate Toolbox Pro, just fill out this form and I'll take a look at it and fix it as soon as possible.
Before posting a question in this thread:
-please search if the question is already posted and answered
-read all of the help topics
trust me, you'll save both yours and mine time.
Feedback is always appreciated.
What's new?
Code:
v1.0.0.0 [14.09.2012]
Initial release
v1.0.1.0 [24.10.2012]
-Bug fixes
-Performance improvements
-The program doesn’t need the Visual Basic Power Pack anymore
-New feature: Restart Android services (accessible in Settings)
-New setting: enable/disable grid in file manager
v1.0.2.0 [21.11.2012]
-Bug fixes
-Added ‘Check all’ and ‘Uncheck all’ buttons in the Backup configurator window
-New in Update Creator: the text dialogs for file and directory locations and permissions suggest common values
-New in Update Creator: the text dialog for the file location has a check box to set the same location for the next files
-Added buttons for the video review and changelog in the main menu
-Small under-the-hood improvements
v1.1.0.0 [22.01.2013]
-Added ‘Unpack APKs’ feature
-Added ‘Repack APKs’ feature
-Added ‘Sign APKs’ feature
-Added ‘Deodex APKs / Jars’ feature
-Added ‘Zip-align APKs’ feature
-Reorganized the main window
-Added binaries: apktool, smali, baksmali, aapt, zipalign, signapk
-New settings: delete unsigned APKs after signing, sign APKs after repacking, ask for framework dependencies, custom framework location (needed for deodexing), use custom framework for unpacking APKs, zip-align APKs after deodexing
-Usability and performance improvements, bug fixes
-...
v1.1.1.0 [09.02.2013]
-Fixed bug related to unpacking APKs
-Improved the APK uninstallation feature, now you can uninstall more than one APKs at once
-New feature: Update manager, displays latest version and changelog when an update is available
-Updated AndroidLib library to 1.5.1.0
-Updated apktool binary to 1.5.2
-Performance improvements
v1.1.1.1 [09.03.2013]
-Reverted AndroidLib library to 1.3.0.0 because of broken features with version 1.5.1.0 (fixed Update.zip creator and Backup/Restore features)
v1.2.0.0 [4.5.2013]
-Added features: backup and restore apps
-Added 'Size' column to the 'Update entries' list in the Update creator
-Bug fixes
Reserved...
nice tool may come in handy, will this work on non nexus devices because when i installed on bottom left corner it says only for nexus devices, i have an lg device
Very good , thank you very much
hsingh1993 said:
nice tool may come in handy, will this work on non nexus devices because when i installed on bottom left corner it says only for nexus devices, i have an lg device
Click to expand...
Click to collapse
Yes, it will. Only the functions for bootloader unlocking and locking are for Nexus devices, but the others are universal.
kinghunki said:
Very good , thank you very much
Click to expand...
Click to collapse
I'm glad you like it.
Sent from my HTC EVO 3D X515m using xda app-developers app
Will this work for htc devices which doesn't have s- off?
Sent from my HTC One X using xda premium
timlambo said:
Will this work for htc devices which doesn't have s- off?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, but not all features will work. For instance, you won't be able to flash system, data, kernel, recovery and splash images, which require a bootloader that supports fastboot commands (which indeed is a S-OFF bootloader). If you are on unlocked S-ON bootloader (HTC Unlock), then they should also work.
despotovski01 said:
Yes, it will. Only the functions for bootloader unlocking and locking are for Nexus devices, but the others are universal.
I'm glad you like it.
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
thanks great tools now i can remove system app whenever i want and can customize my rom a little.
I recently tried this app, and seems that has very useful functions, thanks.
I have a problem with backup future though. My device(U8800) has a difference about recovery and boot images. Has a seperate fat32 partition which mounted as .cust_backup, in which are the recovery.img, boot.img and some other system files.
So, the app cannot backup recovery and boot. Only backup system and data. The approach used on CMW recovery for my device, is to just copy and compress all this partition which is less that 200MB.
Can you implement support for this in the app?
Here is the mounts of my device:
Code:
[email protected]:/ # cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,user_xattr,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p13 /data ext4 rw,relatime,user_xattr,barrier=1,nomblk_io_subm
it,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=1,no
mblk_io_submit,data=ordered 0 0
/dev/block/mmcblk0p14 /HWUserData vfat rw,relatime,uid=1000,gid=1015,fmask=0002,
dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,u
tf8,errors=remount-ro 0 0
/dev/block/mmcblk0p1 /.cust_backup vfat ro,relatime,fmask=0000,dmask=0000,allow_
utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
0 0
/dev/block/vold/179:14 /mnt/sdcard1 vfat rw,nosuid,nodev,noexec,relatime,uid=100
0,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso88
59-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/foursqwifi.aithanasakis-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.mobappbox.pyramidrun-1 vfat ro,dirsync,nosuid,node
v,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sho
rtname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.svox.classic.langpack.ell_grc_fem-1 vfat ro,dirsyn
c,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/taxy.kwd-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1
000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf
8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/gr.digitalblast.drivesafe-1 vfat ro,dirsync,nosuid,nod
ev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,sh
ortname=mixed,utf8,errors=remount-ro 0 0
thanks in advance.
despotovski01 said:
After months of hard work, I present you the ultimate Android utility, Android Ultimate Toolbox Pro! As the name says, it's a toolbox-like program that offers many features that make the usually not-so-easy tasks easier.
Caution! This program is not foolproof! Don't try to outsmart it by playing tricks, or you may result with an expensive brick in the worst case!
Requirements
Microsoft .NET Framework 4 (Client Profile is also needed)
Java JDK and JRE and Android SDK (for signing update.zip files)
Visual Basic Power Packs 10 - download here
Key features
Update.zip creator
Update.zip signer
Flash kernels
Flash recovery images
Flash upate.zip
Flash system images
Flash data images
Flash splash images
Install APKs (system and user)
Uninstall APKs (system and user)
Check MD5 sums
File manager
Root checker
Root your device
Unroot device
Logger (logcat and dmesg)
Rebooter (normal reboot, reboot in recovery, reboot in bootloader, reboot from fastboot)
Backup manager
Device ID configurator (device name, build number, Android version)
Unlock bootloader
Lock bootloader
Wipe (system, data, cache, boot, recovery)
And much more to come!
Note: make sure to read the help topics before using Android Ultimate Toolbox Pro.
Download
(If you don't see the download button, click here)
Latest version: 1.0.0.0
Credits
fdespotovski - icon
RegawMod - AndroidLib library
cdesai - help
Rebellos - help
Zoran Despotovski - tester
Error reporting
If you want to report a misbehavior of Android Ultimate Toolbox Pro, just fill out this form and I'll take a look at it and fix it as soon as possible.
Before posting a question in this thread:
-please search if the question is already posted and answered
-read all of the help topics
trust me, you'll save both yours and mine time.
Feedback is always appreciated.
Video coming soon!
Click to expand...
Click to collapse
excellent work !
dancer_69 said:
I recently tried this app, and seems that has very useful functions, thanks.
I have a problem with backup future though. My device(U8800) has a difference about recovery and boot images. Has a seperate fat32 partition which mounted as .cust_backup, in which are the recovery.img, boot.img and some other system files.
So, the app cannot backup recovery and boot. Only backup system and data. The approach used on CMW recovery for my device, is to just copy and compress all this partition which is less that 200MB.
Can you implement support for this in the app?
Here is the mounts of my device:
thanks in advance.
Click to expand...
Click to collapse
Hi, mate,
First off, thanks for using my new program. I'm looking forward to adding support for your devce, but first I need to know how do you flash and backup recovery and boot images? Do you just flash that combined partition, or you flash the boot and recovery images seperately?
Sent from my HTC EVO 3D X515m using xda app-developers app
The backup is, as I mentioned, the folder Image(which contains the system files) from .cust_backup partition. The device has a special pink screen in which the pc loads this partition and I just replace the recovery.img with the custom one. Same and with boot.img can happens, but usually, for custom roms, is contained on update.zip.
dancer_69 said:
The backup is, as I mentioned, the folder Image(which contains the system files) from .cust_backup partition. The device has a special pink screen in which the pc loads this partition and I just replace the recovery.img with the custom one. Same and with boot.img can happens, but usually, for custom roms, is contained on update.zip.
Click to expand...
Click to collapse
OK, I will see what I can do with that.
So, what do you think about this program? Is it OK? Should I change anything?
Excellent will take a look as soon as my pc is operational thank you
Is it possible to root Galaxy Nexus running on 4.1 JB with FIDO network???
Cool to see more and more people developing using my library AndroidLib
I was wondering when using this app of yours, what state should the phone/tablet/device be in? ie: recovery, phone on but screen off, phone on and screen on etc etc. And I was wondering also how you are able to make it so that the app can root all sorts of different devices.
ashqmallik said:
Is it possible to root Galaxy Nexus running on 4.1 JB with FIDO network???
Click to expand...
Click to collapse
Theoretically it should be a cinch to root the GNex via this utility as long as you have set up your Android SDK properly. Your bootloader should be unlocked (If not use Feature #20 to do so). Subsequent rooting and then pushing a custom recovery via adb should be very simple.
DISCLAIMER: I have not used this utility to Unlock and Root my GNex. I am only going by the universal methods and assumptions regarding recent Samsung devices. I did use the method given in my signature.