Database Info

[q] ext 4 [solved]

Hey, I don't think EXT 4 is working right on my phone, how can i tell if its enabled?

ChadBFlores said:
Hey, I don't think EXT 4 is working right on my phone, how can i tell if its enabled?
Click to expand...
Click to collapse
get the app terminal emulator
and enter "mount" without parenthesis
the first few lines you should see somewhere in the code ext4 before /system /cache and /data

dsexton702 said:
get the app terminal emulator
and enter "mount" without parenthesis
the first few lines you should see somewhere in the code ext4 before /system /cache and /data
Click to expand...
Click to collapse
Thanks dsexton so just to verify it should look like: ext4/ system
ext4/ data
ext/ cache
??
what if mine shows:
/ system ext4 rw
/ data ext4 rw
/ cache ext4 rw
??
I attached the full results form the terminal if u want to take a look

ChadBFlores said:
Thanks dsexton so just to verify it should look like: ext4/ system
ext4/ data
ext/ cache
??
what if mine shows:
/ system ext4 rw
/ data ext4 rw
/ cache ext4 rw
??
I attached the full results form the terminal if u want to take a look
Click to expand...
Click to collapse
Here are the lines you're looking for:
Code:
/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /data ext4 rw,noatime,nodiratime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
You ARE on ext4

FBis251 said:
Here are the lines you're looking for:
Code:
/dev/block/stl9 /system ext4 rw,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl11 /cache ext4 rw,noatime,nodiratime,barrier=0,data=writeback,noauto_da_alloc 0 0
/dev/block/stl10 /data ext4 rw,noatime,nodiratime,barrier=0,nodelalloc,data=ordered,noauto_da_alloc 0 0
You ARE on ext4
Click to expand...
Click to collapse
haha i got scared there for a sec, thanks!

ChadBFlores said:
haha i got scared there for a sec, thanks!
Click to expand...
Click to collapse
lol sorry i put it in the wrong order, but yea what fb said

dsexton702 said:
lol sorry i put it in the wrong order, but yea what fb said
Click to expand...
Click to collapse
haha its alright, thanks for the help, ur all awesome devs!

Boot loop Unresolvable? Hardware problem?

Hey all, new to xda. Hope I'm not asking stupid questions.
My friend gave me a Galaxy S to fix. Model: GT-I9003.
It has a boot loop problem, cycling the Samsung introduction animation (and sound first time round). The recovery mode didn't work to start with - also trapped in a boot loop.
I followed the instructions here (using Odin3 v1.85) and flashed XXKPE. It seemed to all work fine, but the boot loop remained. I booted it into recovery mode and the following error messages appear.
E:failed to mount /data (No such file or directory)
Click to expand...
Click to collapse
and under -- Wiping data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p3
Click to expand...
Click to collapse
then
Data wipe failed.
Click to expand...
Click to collapse
From my research I believe it's a corrupted internal SD-Card and is fixed via parted? Could anyone go into more detail on how I would do this?
Many thanks.

I am facing a similar problem on my Galaxy SL... Need a solution too... I would appreciate any help...

Data partition has been corrupted, try flashing userdata.rfs with heimdall. A friend of mine had an stock/untouched phone and this happened to it, even with the corrupted partition i was able to boot cyanogenmod, and tried a lot of things, but nothing worked, it was on warranty, so i flashed back the original firmware and he took it to the service center.

If you want to try do this:
Flash bam kernel PDA_BCK_CF-root_universal_beta14fix.tar (http://forum.xda-developers.com/showthread.php?t=1355675)
Then from CWM flash cyanogenmod (i used cm7, but you can try with cm9)
after that the phone should boot into cyanogemod and give an error on the notification bar
extract the 6 files off the zip i attached and copy them to /xbin
from terminal emulator or adb shell run this for the 6 files:
Code:
chmod 0755 <file>
then run:
Code:
parted /dev/block/mmcblk0 mkfs ext2
When it asks for the partition number, enter 3
finally reboot, and if it worked you can flash a stock rom again, thats it, good luck

My phone boots up, but there are random reboots. Tried a lot of stock and custom ROMs... Nothing works... Warranty expired last week...

Thanks for your time. I appreciate it.

bruisedcrow said:
Thanks for your time. I appreciate it.
Sorry, I'm very new at this - my first hour doing this kind of thing. Could you explain the procedure in more detail - I would like to learn (make the best of a bad situation).
Am I right to say that the Bam Custom Kernel gives super-root level privileges? Allowing the CWM to fiddle with partions?
I've downloaded the normalboot.img for BCK. How do I flash this to my device? Could you link me to a tutorial?
EDIT: Alternatively could you point me to all the prerequisites I need to properly understand the problem and the methods required to fix it?
Click to expand...
Click to collapse
I tried that... My phone was booting up...
I have Android SDK on my PC... It includes some tools like ADB.
If your phone is rooted, you can use ADB to do things, like formatting...
Connected my phone. Booted into recovery. From Command Prompt, I went to ADB folder, then typed "adb shell". Then, typed in the parted command, and followed steps. Successfully done...
But the problem continues...
I have found many other users have faced this problem -- http://forum.xda-developers.com/showthread.php?t=1736118
I am disappointed. My phone is no longer in warranty... I am too late...

it is possible that using cyanogenmod and S2E (simple2ext) will work as a workaround until you send it to service center.
grab a copy of s2e and push it to /system/app/
Repartition your External-SD using the same method used for phones with low storage capacity, warning: it will erase all the data in it, so make backups
Start s2e and mark to move:
App and Private app
Applications data
Dalvik and download cache
This makes another partition, and it does not fix data, but at least you should be able to install apps.

I face this problem too. Please someone give us the solution.

Update: I flashed BAM Custom Kernel and put it in recovery mode. Attached it to the computer, but I'm stuck at this error message.
Thanks again.

More information
EDIT: There doesn't seem to be a /data partition at all! I feel I'm getting closer to fixing this.

There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.

alfrix said:
There are 2 storages chips on this phone, one is mmc and the other is onenand.
I think the mmc chip is dead... it contains both /data and internal-SD, the onenand still works, it contains (system cache and dbdata), you can still use the phone with cyanogenmod if you mount everything that should go on /data on a partition in the external-SD, (the method i described with s2e). However there are some drawbacks, the SD needs to be class 6 or above to maintain the system speed, and the life of the sd is going to be reduced because of the more intensive use.
Click to expand...
Click to collapse
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?

bruisedcrow said:
Thanks. Is there a way to replace the mmc chip without sending it to Samsung?
I've flashed XXFPE then Bam Custom Kernel then when I try install cm7 from CWM it gives:
Checking state of RFS/EXT4...
assert failed: run_program("/tmp/updater.sh") == 0
E: Error in /emmc/update-cm-7.1.0-GalaxySL-Kang-singed.zip
(Status 7)
Installation aborted.
Trying with MIUI instead.
EDIT: MIUI does this too.
How do I get around this? Can't I flash cm7 via Odin like the stock roms?
Click to expand...
Click to collapse
I think that the problem is when /tmp/updater.sh tries to mount /emmc your internal memory (EDIT: I've just noticed you tried with CM7, so, if I remember correctly, /emmc is the external memory, but I think that the problem is always the impossibility to mount the internal memory.) to backup your /efs directory. Because of the not avaible internal memory (/emmc) it simply exits and aborts the installation.
A simple change in updater.sh will allow you to install CyanogenMod, but wait for a confirmation from alfrix, maybe there's something more.
Anyway here there's a thread of a user with the same problem, he solved this by using the external SD as internal SD, as alfrix suggested.

strange, before touching anything try with the release i used that time (14.12.2011), if it doesn't work, then edit the updater.sh and remove
Code:
if ! /tmp/busybox mount -t ext4 /dev/block/mmcblk0p3 /data ; then
/tmp/busybox umount /data
/tmp/make_ext4fs -b 4096 -g 32768 -i 8192 -I 256 -a /data /dev/block/mmcblk0p3
fi
EDIT: is there any mmcblk on /dev/block?
Code:
ls /dev/block/

Weird the has mmcblk0 reappeared.
Code:
~ # ls /dev/block
ls /dev/block
bml0!c bml6 loop6 ram13 ram9 stl6 tfsr2
bml1 bml7 loop7 ram14 stl1 stl7 tfsr3
bml10 bml8 mmcblk0 ram15 stl10 stl8 tfsr4
bml11 bml9 mmcblk0p1 ram2 stl11 stl9 tfsr5
bml12 loop0 platform ram3 stl12 tfsr0!c tfsr6
bml13 loop1 ram0 ram4 stl13 tfsr1 tfsr7
bml2 loop2 ram1 ram5 stl2 tfsr10 tfsr8
bml3 loop3 ram10 ram6 stl3 tfsr11 tfsr9
bml4 loop4 ram11 ram7 stl4 tfsr12
bml5 loop5 ram12 ram8 stl5 tfsr13
So I tried
Code:
C:\Users\Bruised>adb shell
~ # /sbin/parted /dev/block/mmcblk0 mkfs ext2
/sbin/parted /dev/block/mmcblk0 mkfs ext2
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
/sbin/parted: invalid token: ext2
Yes/No? y
y
y
Partition number? 3
3
3
Error: Partition doesn't exist.
~ #

That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app

alfrix said:
That mmcblk is you externalSD its 0 because the internal is missing/broken and it has only 1 partition, because you didn't do the Repartition yet.
Sent from my GT-I9003 using xda app-developers app
Click to expand...
Click to collapse
What should I try next? 14.12.2011 download link is down.

try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip

alfrix said:
try with this:
https://dl.dropbox.com/u/5013311/test_for_broken_mmc_cm-9-20120626-UNOFFICIAL-galaxysl.zip
Click to expand...
Click to collapse
It installs it.
Code:
Checking state of RFS/EXT4...
Install from sdcard complete.
After I reboot CM9 boot screen loads then I get "Encryption unsuccessful" as shown here
After rebooting I get
Code:
CWM-based Recovery v5.5.0.4
Formatting /data...
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p3
Formatting /cache...
Data wipe failed.
Heres the log file from the sdcard:
Code:
+ /tmp/busybox test -e /sdcard/backup/efs/nv_data.bin
+ /tmp/busybox mount -t ext4 /dev/block/stl9 /system
+ /tmp/busybox mount -t ext4 /dev/block/stl10 /dbdata
+ /tmp/busybox mount -t ext4 /dev/block/stl11 /cache
+ /tmp/busybox umount -l /system
+ /tmp/busybox umount -l /cache
+ /tmp/busybox umount -l /data
umount: can't forcibly umount /data: Invalid argument
+ /tmp/busybox umount -l /dbdata
+ /tmp/busybox umount -l /efs
umount: can't forcibly umount /efs: Invalid argument
+ exit 0

[Q] Stuck at recovery cant install rom

First of all. I am biggest noob ever it is common problem but i did not find like mine. Because of phone low memory i installed int2ext and set 2gb size in cm10. But i figured out that is to much phone started to work a lot slower almost like on stock and flashed completly everyhing same again but partition is 1gb but then gapps started to fail ( gapps.andorid.com. process and 3,4 more things) and i just pressed ok ok ok. Then i restarted phone and again it couldnot connect to gsm network and those failures started to come out. Because of that i returned to recovery wiped clear dalvik installed new partition and then nothing phone is stuck at boot animation. I tried again and again and tried everything formating cache system data and then data dalvik tried all custom roms from original section and at the end. I copied backup i made before i installed first rom and restored it and now i when i turn on my phone i see HTC logo for a while then phone restarts and htc logo again and it moves me to recovery. I wiped that again but now when i select to install custom rom it stops during installation and says fail. I flashed phone more then 20x in past two days and i could not sort this problem and i dont have ideas. How to pass this problem and bring phone to life? ( i have to use old nokia s60 until i fix it so be quick . I know i did something wrong.

I think you are only wiping caches..
Do wipe/factory rest.
Wipe cache,
Wipe Dalvik cache in advanced
Format system and boot in mounts and storage..
Then flash your Rom..
If it still does nothing...
Follow NAND recovery by cute_Prince.. may be NAND burn..
Sent from my HTC Explorer A310e using xda app-developers app

What you can do is load into bootloader,click fastboot and connect your phone via usb.Flash a new recovery(try cwm) and then try flashing a new rom and recovering nand.

Thanks a lot on help. I reflashed boot again (connected to fastboot and recovery.bat) and when i now try to install new rom it stops and abort instalation at
Installing update : some symlinks failed
E:Error in /sdcard/cm-10....
(status 7)
Instalation aborted.
Please help
EDIT: I reed that this is common problem and i have fixed it by formating boot and system in mounts and storage. I can only install cm10.1 and mini cm. I cant install rom i have used before (cm10 b6). And now i get stuck and boot animation...

hey installed FLYROM v4....i havnt tried CM roms....what i did fr flashing FLYROM z i flashed yannou09z recoverry which z available on jaggyjaggs rooting tutorial....i use twrp nd other recveries....but wen i flash new rom it stuck on htc logo screen...so i flashed back to yannous....i then partitioned ma mmry card in ext4 through minitool wizard of 1 gb...then i wiped dalvich cache nd then i wipe data/factory reset thru recovery nd flashed flyrom...it wrks smoothly now....i recmnd yannous recovery fr pico....rest z uppon yu....

roshanjoseph23 said:
hey installed FLYROM v4....i havnt tried CM roms....what i did fr flashing FLYROM z i flashed yannou09z recoverry which z available on jaggyjaggs rooting tutorial....i use twrp nd other recveries....but wen i flash new rom it stuck on htc logo screen...so i flashed back to yannous....i then partitioned ma mmry card in ext4 through minitool wizard of 1 gb...then i wiped dalvich cache nd then i wipe data/factory reset thru recovery nd flashed flyrom...it wrks smoothly now....i recmnd yannous recovery fr pico....rest z uppon yu....
Click to expand...
Click to collapse
Tried to install flyrom rom. Installation was successful, but i get stuck at boot animation Any help i'm left out of ideas. And i changed recovery to TWRP (i been using cwm yanous90) and again same thing stuck at boot animation... Please help!
edit : And now in twrp when i try to install roms which i have installed above it shows again symlinks error ?!

If it helps
if you already have twrp recovery. try cute_prince nand recover method (flash_erase file) if not sure about nand burnt.
http://forum.xda-developers.com/showpost.php?p=36868966&postcount=2367
and after that format/wipe every partition inclucing sdcard, when done then reboot in recovery and mount usb storage to pc and copy your desired rom( prefer cm9 or miniCM9) and flash it. wait for it to be succesful and next step is optional if you want sd-ext partition then reboot in recovery again and partition your card with ext3 and 0mb as swap space and wait for it to be succesful. if succesful then reboot to system.

Now i am 100% sure that it is burnt nand. I tried cute prince method have shell with # and when i copy paste command this is what happens... I copied flash_erase set to 775 and copied to xbin... In TWP i unmounted everything. When i type commands one by one su not found and then i cant cd to system/xbin... No i can see that i am close to solution. Please help i cant survive another week with nokia n97 mini...
adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
s./flash_erase -N /dev/mtd/mtd4 0 0
u
./flash_erase -N /dev/mtd/mtd5 0 0cd /system/x
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
~ # su
/sbin/sh: su: not found
~ # cd /system/xbin
/sbin/sh: cd: can't cd to /system/xbin
~ # ./flash_erase -N /dev/mtd/mtd2 0 0
/sbin/sh: ./flash_erase: not found
~ # ./flash_erase -N /dev/mtd/mtd4 0 0
/sbin/sh: ./flash_erase: not found

DJ_MY_SOUL said:
Now i am 100% sure that it is burnt nand. I tried cute prince method have shell with # and when i copy paste command this is what happens... I copied flash_erase set to 775 and copied to xbin... In TWP i unmounted everything. When i type commands one by one su not found and then i cant cd to system/xbin... No i can see that i am close to solution. Please help i cant survive another week with nokia n97 mini...
adb shell
su
cd /system/xbin
./flash_erase -N /dev/mtd/mtd2 0 0
s./flash_erase -N /dev/mtd/mtd4 0 0
u
./flash_erase -N /dev/mtd/mtd5 0 0cd /system/x
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
~ # su
/sbin/sh: su: not found
~ # cd /system/xbin
/sbin/sh: cd: can't cd to /system/xbin
~ # ./flash_erase -N /dev/mtd/mtd2 0 0
/sbin/sh: ./flash_erase: not found
~ # ./flash_erase -N /dev/mtd/mtd4 0 0
/sbin/sh: ./flash_erase: not found
Click to expand...
Click to collapse
If you are sure its a burnt nand, we have a thread here:
forum.xda-developers.com/showthread.php?t=2183130

And my phone is now running great! I installed cm10.1 after i flash_erase burnt nand. But because of symlinks error somewhere on xda i found that someone just added ./flash_erase -N /dev/mtd/mtd3 0 0 to cute prince method and thats it. And again my problem was that in recovery mount everything only sd card leave unmounted. And thats it Goodbye n97

Delete.

bootloop and recovery stuck
salil.bajaj said:
What you can do is load into bootloader,click fastboot and connect your phone via usb.Flash a new recovery(try cwm) and then try flashing a new rom and recovering nand.
Click to expand...
Click to collapse
Hi., my phone just got switched off for no reason and when i try to boot... stuck in boot animation... got to bootloader then recovery but recovery is stuck...i thought of flashing new recovery so i went to bootloader mode and connected the usb cable... it would rarely show FASTBOOT USB and pc would never recognize my device... I dont think i should go to Gaffar Market for this...

[Guide] nand recovery [Pico] using phone

I burnt my nand and no rom is booting for me and the procedure of nand recovery isn't working for me because it requires Android debugging mode . So I found another way to recover it
So all of those guys who burnt their nand due to over clock can follow this method to recover burnt nand by using phone
WHAT YOU WILL NEED:
HTC explorer (Pico)
Working recovery
FOR ALL THOSE GUYS WHO HAVE TWRP RECOVERY FOLLOW THIS
(Scroll down if you don't have)
First download flash_erase.txt and put it into SD card
Boot into recovery
Go to mounts and storage then mount all things
Then go into advanced then file manger then rename that file to flash_erase
Now move this file to system/xbin and set permission as 755
Open terminal command from recovery then go to system/xbin now hit select and
Now type
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0
Now Remove
battery and reinsert it .
Goto recovery and:
format /boot
format /system
wipe data / factory reset
Now install your favourite ROM
Once the ROM is booted, goto storage
settings.. Everything should be fine now and
you should get around 140MB free depending
on your ROM
Download link for flash_erase.txt
http://forum.xda-developers.com/attachment.php?attachmentid=1655489&d=1358514526
Hit thanks if it helped
FOR ALL RECOVERIES OTHER THAN TWRP
First download aroma file manager 1.80 version from here
http://forum.xda-developers.com/showthread.php?t=1646108
Then download flash_erase.txt (link given above)
Put both files in sdcard
Boot into recovery.. now go to mounts and storage and mount all things
install aroma file manager from recovery
A file manager will open now go to sdcard and rename flash_erase.txt to flash_erase
Now put this file into system/xbin and change permission to rwx,rwx, rwx
Now open terminal command and type
./flash_erase -N /dev/mtd/mtd2 0 0
./flash_erase -N /dev/mtd/mtd4 0 0
./flash_erase -N /dev/mtd/mtd5 0 0
Now Remove
battery and reinsert it .
Go to recovery and:
format /boot
format /system
wipe data / factory reset
Now install your favourite ROM
Once the ROM is booted, goto storage
settings.. Everything should be fine now and
you should get around 140MB free depending
on your ROM
Hit thanks if it helped
Sent from my HTC Explorer A310e using xda premium

Journal Disabler For Pico! :D

----------------------- Journaling Disabler For Pico ----------------------
This is just a simple Zip to Disable Journaling on pico! as we use 2 or 3 extra ext4 partitions for OC!
It even clear's /sd-data,/sd-cache - for aosp
and /sd-ext,/sd-data,/sd-cache - for sense 4
Which means you need not always format your sd-card to switch between roms! .. But if you are switching from aosp rom to sense 4 you need to partition the sd-card appropriately!
Steps to USE:
******* Use this Zip Only when installing a Rom from scratch!... cause it wipes everything! ******
-- clear almost everything you can from recovery e.g factory-reset,/system,/boot,/cache etc
-- install this Zip! as like you do with any other zip (Prefered Recovery TWRP 2.4.X)
-- Flash Your Favourite Rom Now!!

I can use this even if i am not oc'ing?? Just like superwipe?
Disabling journal wont harm anything! Right?

Parth_14 said:
I can use this even if i am not oc'ing?? Just like superwipe?
Disabling journal wont harm anything! Right?
Click to expand...
Click to collapse
From the wikipedia's article:
A journaling file system is a file system that keeps track of the changes that will be made in a journal (usually a circular log in a dedicated area of the file system) before committing them to the main file system. In the event of a system crash or power failure, such file systems are quicker to bring back online and less likely to become corrupted.[1]
Click to expand...
Click to collapse
For overclocking, the SD Card is used for the /data and /cache partition. In that case, the SD Card would be read more frequently as the /data and /cache partitions are the most frequently accessed and modified partitions while running the Android system. In that case, using a Journal would slow down the memory access times if the SD Card is not fast enough. Also, as many modifications are made to the /data and /cache partition, the SD Card would be going through the read/write cycle twice the number of times, once for the journaling and once for the "commiting them to the main file system". So, it is likely that the SD Card might get corrupted faster than it normally should. That is the reason why Class 4 and below SD Cards are likely to "go dead" soon when overclocking with cute_prince's new PLL2 overclocking method. And, this is why ateeq72 has made this flashable zip to disable journaling. It would reduce the possibility/risk of losing your SD Card and at the same time allow you to OC your phone.
Using this when you are not OC'ing your phone? I wouldn't recommend that you flash this zip, but you would need a slightly modified zip. Also, journaling, I presume you want to disable in your phone's sd-ext memory. It would increase your phone's performance in case you are using any memory increasing scripts like int2ext which mount the sd-ext partition in the /data folder.

vineethraj49 said:
Using this when you are not OC'ing your phone? I wouldn't recommend that you flash this zip, but you would need a slightly modified zip. Also, journaling, I presume you want to disable in your phone's sd-ext memory. It would increase your phone's performance in case you are using any memory increasing scripts like int2ext which mount the sd-ext partition in the /data folder.
Click to expand...
Click to collapse
Thanks man!
Can you tell what is to be modified in the zip so that i can use it when i am not oc'ing?

Parth_14 said:
Thanks man!
Can you tell what is to be modified in the zip so that i can use it when i am not oc'ing?
Click to expand...
Click to collapse
No need to mod dude, u can use it if u dont OC.
Helped? Thanks maybe!

Parth_14 said:
Thanks man!
Can you tell what is to be modified in the zip so that i can use it when i am not oc'ing?
Click to expand...
Click to collapse
Edit the file named "ateeqscript" using Notepad++.
Make sure the file looks like the one below.
Code:
#!/bin/sh
echo ***************Begin Disable Journaling Partition***************
/sbin/busybox mount -t auto /dev/block/mmcblk0p2 /sd-ext
rm -rf /sd-ext/*
/sbin/busybox umount -l /sd-ext
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p2
fsck.ext4 -Dfy /dev/block/mmcblk0p2
sync
echo ***************Data Partion Done***************
echo ***************Finished No Journaling Partions***************
What I have done? Simple. Removed all code related to /sd-data and sd-cache, and kept only commands necessary for the sd-ext partition.
---------------------------------------------------
@OP, I suggest a few changes in your script. First, the mounting commands are run, so, if the sd-ext is already mounted by the recovery (just in case, accidentally it happened), then, you wouldn't (or rather shouldn't) be able to mount it in another folder, namely /sd-data. I would suggest the following change in your flashable zip. Try to make it look something like the one below.
Code:
#!/bin/sh
echo "\"Disabling Journaling\" Script"
echo "Initializing script..."
/sbin/busybox umount -l /sd-ext
/sbin/busybox mkdir /sd-data
/sbin/busybox mount /dev/block/mmcblk0p2 /sd-data
/sbin/busybox mkdir /sd-cache
/sbin/busybox mount /dev/block/mmcblk0p3 /sd-cache
/sbin/busybox mkdir /sd-ext2
/sbin/busybox mount /dev/block/mmcblk0p4 /sd-ext
rm -rf /sd-cache/*
rm -rf /sd-data/*
rm -rf /sd-ext/*
/sbin/busybox umount -l /sd-data
/sbin/busybox umount -l /sd-cache
/sbin/busybox umount -l /sd-ext
echo "Disabling Journal in sd-data"
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p2
fsck.ext4 -Dfy /dev/block/mmcblk0p2
echo "Disabling Journal in sd-cache"
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p3
fsck.ext4 -Dfy /dev/block/mmcblk0p3
echo "Disabling Journal in sd-ext"
/tmp/tune2fs -O ^has_journal -c 1 -i 1d -m 0 /dev/block/mmcblk0p4
fsck.ext4 -Dfy /dev/block/mmcblk0p4
sync
echo "Partitions Journaling Disabled..."
echo "Finished no journaling partitions"

Do we need to flash this zip for every new rom or just once is enough?
Sent from my HTC Explorer A310e using xda app-developers app

faiPICO said:
Do we need to flash this zip for every new rom or just once is enough?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
i guess one time is enough no need to flash again and again

@ateeq72
Can you edit this script with just the wiping part? As it is not necessary to disable journal for aosp roms!

Parth_14 said:
@ateeq72
Can you edit this script with just the wiping part? As it is not necessary to disable journal for aosp roms!
Click to expand...
Click to collapse
Its already there I guess

vineethraj49 said:
Its already there I guess
Click to expand...
Click to collapse
I've read that it formats through ext2/4 ! What i want is the parition to be remain untouched..

Parth_14 said:
@ateeq72
Can you edit this script with just the wiping part? As it is not necessary to disable journal for aosp roms!
Click to expand...
Click to collapse
vineethraj49 said:
Its already there I guess
Click to expand...
Click to collapse
journal disabling is required for only ext4 partition for max performace
if u dont use ext4 use any wiping script
the script keval gave format partitions to ext2 only not ext4

sakshamx said:
journal disabling is required for only ext4 partition for max performace
if u dont use ext4 use any wiping script
the script keval gave format partitions to ext2 only not ext4
Click to expand...
Click to collapse
NOTE:------------>Do remember the script of sense will format partitions as EXT2 and script for aosp roms will format partitions as EXT4 and sense 4.1 sctript will also format as EXT4
Click to expand...
Click to collapse

vineethraj49 said:
Click to expand...
Click to collapse
u can check the script it formats as ext2 i had also checked from sd card its ext2
i also had thought that as it was given in thread but its not

is it updated script which u posted in facebook

bloodhound42 said:
is it updated script which u posted in facebook
Click to expand...
Click to collapse
yup! it is!

vineethraj49 said:
@OP, I suggest a few changes in your script. First, the mounting commands are run, so, if the sd-ext is already mounted by the recovery (just in case, accidentally it happened), then, you wouldn't (or rather shouldn't) be able to mount it in another folder, namely /sd-data. I would suggest the following change in your flashable zip. Try to make it look something like the one below.
Code:
#!/bin/sh
echo "\"Disabling Journaling\" Script"
echo "Initializing script..."
/sbin/busybox umount -l /sd-ext
/sbin/busybox mkdir /sd-data
/sbin/busybox mount /dev/block/mmcblk0p2 /sd-data
/sbin/busybox mkdir /sd-cache
/sbin/busybox mount /dev/block/mmcblk0p3 /sd-cache
/sbin/busybox mkdir /sd-ext2
/sbin/busybox mount /dev/block/mmcblk0p4 /sd-ext
rm -rf /sd-cache/*
rm -rf /sd-data/*
rm -rf /sd-ext/*
Click to expand...
Click to collapse
Bro thats why i have mounted sd-ext as "sd-ext2" ! to make sure every recovery doesnt have any issue mounting it!

what is journal?
in many posts i found this about this journal what is this actually..