Develop Bugs

*REQUEST* Firerat's Custom MTD Partitions (resize Data,System and Cache)

can any dev. make this happen for our EVO 4G please? I included a link to the thread were the mod is. This mod enables a person to decide how big the partitions in their phone should be. (ei system, data, cache, etc). Its awesome but I just have it on my hero which i gave to my brother and it wouldn't hurt that everyone could have more space for apps on their phone.
Thanks everyone!!!
http://forum.xda-developers.com/showthread.php?t=754805

I found a dmesg for your evo
# dmesg|awk '/0x.+: "/{ print }'
Code:
<5>[ 4.290466] 0x00003f360000-0x00003ff60000 : "wimax"
<5>[ 4.305419] 0x00003ff60000-0x000040000000 : "misc"
<5>[ 4.306518] 0x000004240000-0x000004740000 : "recovery"
<5>[ 4.312377] 0x000004740000-0x0000049c0000 : "boot"
<5>[ 4.315979] 0x0000049c0000-0x00001a7c0000 : "system"
<5>[ 4.730438] 0x00001a7c0000-0x0000247c0000 : "cache"
<5>[ 4.916748] 0x0000247c0000-0x00003f360000 : "userdata"
it has an extra partition to the g1 ( wimax )
see below for working version v1.5.7

Sounds really great! Thank you, Firerat.
But FR-CustomMTD-v1.5.6-Evo4G.zip is not downloadable to me. The site says its set to private.
Firerat said:
FR-CustomMTD-v1.5.6-Evo4G.zip
that zip contains
73d5ba178ffd702c9b963e9de9b4d5bc FR-recovery-v1.5.6-Evo4G-CustomMTD_S.zip
f468aefb7ad1f86b24c0156fb81a36c2 FR-boot-v1.5.6-Evo4G-CustomMTD_S.zip
89b4e67b87f5337e19c2d7dc95e87055 FR-remove-v1.5.6-Evo4G-CustomMTD_S.zip
Click to expand...
Click to collapse

ywjkid said:
Sounds really great! Thank you, Firerat.
But FR-CustomMTD-v1.5.6-Evo4G.zip is not downloadable to me. The site says its set to private.
Click to expand...
Click to collapse
oops,
http://www.mediafire.com/?0ae7y9sekpb3s
b74d178e7ed698879b555123ea494377 FR-recovery-v1.5.7rc1-CustomMTD_S.zip
331c1b31bbc007fa7c3a9ff01c9301dd FR-boot-v1.5.7rc1-CustomMTD_S.zip
ab946b6b9aa83554c452d3d5face18d4 FR-remove-v1.5.7rc1-CustomMTD_S.zip
its a generic version, which _should_ suit all devices with msm_nand
it collects every partition from dmesg
few little bits I want to do, then I'll bump it up to v2

RC1 is not working for me. After flashing FR-recovery-v1.5.7rc1-CustomMTD_S.zip, my RA-recovery 1.8 is broken and generates errors like
E: Can't find MISC:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
Firerat said:
oops,
http://www.mediafire.com/?0ae7y9sekpb3s
b74d178e7ed698879b555123ea494377 FR-recovery-v1.5.7rc1-CustomMTD_S.zip
331c1b31bbc007fa7c3a9ff01c9301dd FR-boot-v1.5.7rc1-CustomMTD_S.zip
ab946b6b9aa83554c452d3d5face18d4 FR-remove-v1.5.7rc1-CustomMTD_S.zip
Click to expand...
Click to collapse

ywjkid said:
RC1 is not working for me. After flashing FR-recovery-v1.5.7rc1-CustomMTD_S.zip, my RA-recovery 1.8 is broken and generates errors like
E: Can't find MISC:
E: Can't mount CACHE:recovery/command
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
Click to expand...
Click to collapse
Ok, I think I see the problem
Not at home right now,
But in the mean time you should be able to flash the remove zip and return to stock
Looks like a copy paste fail and I'm excluding userdata what I shouldn't be
May also be escaping when I shouldn't be
If you have problems flashing the remove zip you can mount cache manually via adb shell
( you can also flash_image a standard recovery.img via adb shell )

Thanks. Just reflashed recovery and restore the nandroid and everything is fine. I am glad there is no permanent damage done. Cannot wait for the working version!
Firerat said:
Ok, I think I see the problem
Not at home right now,
But in the mean time you should be able to flash the remove zip and return to stock
Looks like a copy paste fail and I'm excluding userdata what I shouldn't be
May also be escaping when I shouldn't be
If you have problems flashing the remove zip you can mount cache manually via adb shell
( you can also flash_image a standard recovery.img via adb shell )
Click to expand...
Click to collapse

ywjkid said:
Thanks. Just reflashed recovery and restore the nandroid and everything is fine. I am glad there is no permanent damage done. Cannot wait for the working version!
Click to expand...
Click to collapse
new version here
http://www.mediafire.com/?7w9sh54lm3mwi
9074fde94c8e534585da4adaa5e59e14 FR-AutoMTD_partitionPatcher_v1.5.7.tar.bz2
919db3e671d0688af9824f37b16ccc87 FR-boot-v1.5.7-CustomMTD_S.zip
05828d98920540c711e06abe5028388f FR-recovery-v1.5.7-CustomMTD_S.zip
changed the 'remove' option
to revert to the stock MTD layout set system size to 0 in mtdpartmap.txt and flash the recovery patcher
e.g.
echo "mtd 0" > /sdcard/mtdpartmap.txt

Great! now the recovery error is gone and the mod is working on my EVO, beautifully. More than 600M for /data. Thank you so much, Firerat. You're the best!
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.4M 0 207.4M 0% /dev
tmpfs 207.4M 0 207.4M 0% /mnt/asec
/dev/block/mtdblock4 240.0M 195.1M 44.9M 81% /system
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /data
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /cache
PS. It seems /cache and /data now share the same space. It is new to me. Does that mean there is only one size need to specify in mtdpartmap.txt?
Firerat said:
new version here
http://www.mediafire.com/?7w9sh54lm3mwi
9074fde94c8e534585da4adaa5e59e14 FR-AutoMTD_partitionPatcher_v1.5.7.tar.bz2
919db3e671d0688af9824f37b16ccc87 FR-boot-v1.5.7-CustomMTD_S.zip
05828d98920540c711e06abe5028388f FR-recovery-v1.5.7-CustomMTD_S.zip
changed the 'remove' option
to revert to the stock MTD layout set system size to 0 in mtdpartmap.txt and flash the recovery patcher
e.g.
echo "mtd 0" > /sdcard/mtdpartmap.txt
Click to expand...
Click to collapse

ywjkid said:
Great! now the recovery error is gone and the mod is working on my EVO, beautifully. More than 600M for /data. Thank you so much, Firerat. You're the best!
Code:
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 207.4M 0 207.4M 0% /dev
tmpfs 207.4M 0 207.4M 0% /mnt/asec
/dev/block/mtdblock4 240.0M 195.1M 44.9M 81% /system
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /data
tmpfs 8.0M 4.0K 8.0M 0% /app-cache
/dev/block/mtdblock6 637.6M 374.7M 262.9M 59% /cache
PS. It seems /cache and /data now share the same space. It is new to me. Does that mean there is only one size need to specify in mtdpartmap.txt?
Click to expand...
Click to collapse
you still need to specify size of cache , the minimum is 2mb
on your phone /cache is actually a bind mount of /data/cache
its there if anything needs to use it, for instance your rom may want to put dalvik-cache in /cache/dalvik-cache
it will actually be on /data, the advantage is that you can make better use of what was free space on /cache

That's indeed a nice advantage. A million thanks. Now I can throw everything in the phone storage without worrying about the space.
Firerat said:
you still need to specify size of cache , the minimum is 2mb
on your phone /cache is actually a bind mount of /data/cache
its there if anything needs to use it, for instance your rom may want to put dalvik-cache in /cache/dalvik-cache
it will actually be on /data, the advantage is that you can make better use of what was free space on /cache
Click to expand...
Click to collapse

Noob tutorial
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
Hope this mod helps everyone. Just like it is helping me
Thanks anyone.
TUTORIAL FOR NOOBS
In TERMINAL:
1. for Fresh Evo 3.4.0.1: echo "mtd 210 3" > /sdcard/mtdpartmap.txt *****(you can do less than 210 for cm6 if you desire)*****
2. adb shell reboot recovery
In RECOVERY MENU
1. nandroid backup
2. wipe data/factory reset
3. wipe cache
4. wipe Dalvik-cache
5. flash fr-recovery.zip
6. wipe data/factory reset
7. wipe cache
8. wipe Dalvik-cache
In TERMINAL
1. adb shell reboot recovery
In RECOVERY MENU
1.2*. IF YOU GET A CACHE ERROR DO NOT ALARM IT MEANS SOMETHING WENT WRONG. ALL YOU NEED TO DO IS WIPE DATA, CACHE, AND DALVIK-CACHE AND FLASH fr-recovery.zip and then when it finish flashing - adb reboot recovery - from terminal
1.3** IF YOU DID NOT GET THE ABOVE ERROR GO TO STEP 2
2. flash ROM (or nandroid backup)
3. flash app (I.E. cm6 google apps)
4. flash kernal (if one)
5. flash fr-boot.zip
6. reboot
7. DONE!!! AND ENJOY THANKS TO FIRERAT (DONT FORGET TO THANKS HIM)
If you want to update/install a kernal
In TERMINAL
1. adb shell reboot recovery
In RECOVERY MENU
2. wipe cache
3. wipe Dalvik-cache
4. flash KERNAL
5. flash fr-boot.zip
6. reboot
7. Sit and let EVO turn on
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
+++IF I DID ANYTHING WRONG UP THERE FEEL FREE IN CORRECTING ME +++

mrcamposd said:
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
Can anyone post a tutorial for noobs?
Or is this the same as for the HERO?
Hope this mod helps everyone. Just like it is helping me
Thanks anyone.
Click to expand...
Click to collapse
I can confirm the process is the same as for the HERO.

mrcamposd said:
THIS IS SO COOL. THANK YOU SO MUCH FIRERAT.
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
Click to expand...
Click to collapse
How do I flash this? It doesn't show up in the list of zip files in recovery. I tried renaming it and extracting it but it doesn't look like it's in a flashable format.

antiphon said:
How do I flash this? It doesn't show up in the list of zip files in recovery. I tried renaming it and extracting it but it doesn't look like it's in a flashable format.
Click to expand...
Click to collapse
i think you just need to rename the file's extension to xxxxx.zip (because .zip's are the one you flash in recovery), but then again I have not used that file. So not responsible for damages or anything. Try it at your own risk buddy.

mrcamposd said:
*****for reset partitions--- echo "mtd 0" > /sdcard/mtdpartmap.txt**** (IF YOU WANT TO GO BACK TO STOCK) and flash the FR-AutoMTD_partitionPatcher then flash any ROM you want or NANDROID BACKUP
+++IF I DID ANYTHING WRONG UP THERE FEEL FREE IN CORRECTING ME +++
Click to expand...
Click to collapse
FR-AutoMTD_partitionPatcher , is linux shell script to shoehorn the boot patcher into a rom zip ( so the end user dosn't need to flash the boot patcher , its automagic ) ,, you don't really need it
to get back to stock layout,
do the mtd 0 thing
nand backup
flash the recovery patcher
format system cache and data ( I recommend clockwork recovery )
reboot
nand restore ( providing the backup will fit stock ! )
flash boot patcher
your done
Note, v1.5.7b is newer

Had this working well on my Hero, so I'm looking forward to putting this on my new Evo as well!

Doesn't Calkulin have an evo version posted?
Sent From My HTC Evo 4G Using Tapa Talk Pro!

[GUIDE] How to make an Odin ROM

How to make an Odin flashable ROM
This is just a small guide I want to share with anyone who's interested in the commands I personally use. Feel free to correct me or give better commands / instructions.
@Moderators:
If this thread is in the wrong section or already present at XDA, PM me.
This needs a UNIX compatible OS - like Linux or Mac OS X.
On Windows, you can use "Cygwin".
Click to expand...
Click to collapse
Use the dd (datadump) command to make the .rfs files
Of course you need to connect your phone via USB and have ADB prepared on your computer.
# Get Root access first
Code:
su
# Do this first to mount the /system R/W
(thanks to scheichuwe for the simplified command)
Code:
mount -o remount,rw /dev/block/stl9 /system
# Dump the needed data / partitions to your /sdcard
Code:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096
dd if=/dev/block/bml12 of=/sdcard/modem.bin bs=4096
# Make the tar ball
Code:
tar -H ustar -c factoryfs.rfs cache.rfs modem.bin zImage > darky.tar
# MD5 it for a security check
Code:
md5sum –t darky.tar >> darky.tar
# Rename the tar file
Code:
mv darky.tar darky.tar.md5
Optional:
Make your own pit file
The pit file is used to set the partition layout (Partition Information Table).
# Dump the pit
Code:
dd if=/dev/block/bml2 of=/sdcard/darky.pit bs=4096
I hope I could help you with that
- darkyy.

Nice
Yeah first

Oh and one more thing:
If someone is gonna rate this thread 1 star, please explain here why.

So this means I can make an Odin rom of my current installed config? Or am I missing something?
If you then flash your tar + pit, you have your kernel and rom restored? This would be an awesome way to backup a good config, no?

VenQWish said:
So this means I can make an Odin rom of my current installed config? Or am I missing something?
If you then flash your tar + pit, you have your kernel and rom restored? This would be an awesome way to backup a good config, no?
Click to expand...
Click to collapse
Exactly - these commands will dump the data directly from your current phone.
And yes, you'll have a 1 to 1 Backup.

That is actually VERY useful! I'm constantly switching between a modded Insanity and CM7, and constantly reverting to stock, flashing custom kernels and flashing nandroids is getting quite annoying now.
Don't have access to a linux machine now, I'll try this asap, thanks!

Wow, dasch mal nützlich ville dank^^
Neat. Thank you!

Quipeace said:
That is actually VERY useful! I'm constantly switching between a modded Insanity and CM7, and constantly reverting to stock, flashing custom kernels and flashing nandroids is getting quite annoying now.
Don't have access to a linux machine now, I'll try this asap, thanks!
Click to expand...
Click to collapse
Well you can install cygwin, just remember to install bash terminal when cygwin setup is running.
Sent from my GT-P1000 using Tapatalk

Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
Galaxy S is running on yaffs2? Interesting
Code:
mount -o rw,remount /system
That should work too...

Is this the same as this?
http://forum.xda-developers.com/showthread.php?t=943588

Mackzen said:
Is this the same as this?
http://forum.xda-developers.com/showthread.php?t=943588
Click to expand...
Click to collapse
No:
The instructions from drakyy create a flashable ROM from the phone.
The Application from bohdans creates a flashable ROM from files on your computer

scheichuwe said:
Galaxy S is running on yaffs2? Interesting
Code:
mount -o rw,remount /system
That should work too...
Click to expand...
Click to collapse
Thanks - gonna change it in the first post

Verified?
Cool stuff Darkyy,
is this working without any issues, any testers?

mr_at_sgs said:
Cool stuff Darkyy,
is this working without any issues, any testers?
Click to expand...
Click to collapse
It's what we used for the Darky's Resurrection Edition

Damn. Left my laptop charger at work. Just when I need battery also.
Great thread. Thank you.
Tricky103 UltraSlim Essential Rom on DamianGTO Ultimate kernel

I have a problem. When tryign to create the tar-file i get:
cannot create jesper.tar: read-only file system.
What to do?

Does this also work when the partitions are NOT RFS.
Like all in ext4?
Will Odin be able to flash that image?
I somehow doubt it...

zurchpet said:
Does this also work when the partitions are NOT RFS.
Like all in ext4?
Will Odin be able to flash that image?
I somehow doubt it...
Click to expand...
Click to collapse
Good question..... I'd like to know this too..
Although even if having to disable lag fix to create it the apply again after flashing is still a quicker way to toggle between your current rom and cm7..

Neat Darky
but can i do these dumps on the phone without a pc or adb
Sent from my GT-I9000 using XDA App

Perhaps some could write a script to do this at the phone
Sent from my GT-I9000 using XDA App

[Q] extend internal memory

hi
here in this fantastic site i saw there are some tips to extend some roms inernal memory up to 2gigs!!!!!
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
or not i like a 720p roms with this abality.
what is your suggestion
it is soooooo necessary
i'seen you answer all the questions so would you please answer mine too??

royalrose said:
hi
here in this fantastic site i saw there are some tips to extend some roms inernal memory up to 2gigs!!!!!
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
or not i like a 720p roms with this abality.
what is your suggestion
it is soooooo necessary
i'seen you answer all the questions so would you please answer mine too??
Click to expand...
Click to collapse
The only way that i am aware of increasing internel memory is to install a rom which is compatable with a D2EXT script which makes the phone use an ext partition of your memory card as internal memory.
To find out if a particular rom is capable of this you will have to reed about them in the development section and, if you are still unsure, ask the question.
Hope this helps.

royalrose said:
but my rom is InsertCoinDATAplusplusv03 or i can even change it to LeeDrOiD_V2.4_A2Sd
is there any way to extend this roms to that capasity or not.
Click to expand...
Click to collapse
For LeeDroid 2.4 you might look here. Beware that there may be some issues ... It's sort of experimental !

bobsie41 said:
The only way that i am aware of increasing internel memory is to install a rom which is compatable with a D2EXT script which makes the phone use an ext partition of your memory card as internal memory.
To find out if a particular rom is capable of this you will have to reed about them in the development section and, if you are still unsure, ask the question.
Hope this helps.
Click to expand...
Click to collapse
thanx bro but as i'm new in this site i can't post any question there
i expereinced many kind of roms(include d2xt) but i had the same problem

Some Guy told me he physically removed the 512 memory chip (ram) from his Samsung galaxy s and replaced it with a gig one. Some soldering required I suppose.

mercianary said:
Some Guy told me he physically removed the 512 memory chip (ram) from his Samsung galaxy s and replaced it with a gig one. Some soldering required I suppose.
Click to expand...
Click to collapse
thanks but I think there should be an easier way too.

no answer?????

royalrose said:
no answer?????
Click to expand...
Click to collapse
You already got your answer, no? use a data2ext rom..
I personally use insertcoin 2.0.1 data2ext, and cant recommend it enough.
very fast, very stable, more than most hd roms ..
http://forum.xda-developers.com/showthread.php?t=861690

snakeeyes21 said:
You already got your answer, no? use a data2ext rom..
I personally use insertcoin 2.0.1 data2ext, and cant recommend it enough.
very fast, very stable, more than most hd roms ..
http://forum.xda-developers.com/showthread.php?t=861690
Click to expand...
Click to collapse
i had that rom too.it's so nice and fast but after instaling 15 apps or game my internal memory became full again.
is it usual??

Do you have an EXT partition on your sdcard?

cgmorris89 said:
Do you have an EXT partition on your sdcard?
Click to expand...
Click to collapse
yes bro
both ext 3 & 4
but still i have low memory

stumped
are your partitions in the correct order?

cgmorris89 said:
stumped
are your partitions in the correct order?
Click to expand...
Click to collapse
I think it's
usualy it's in this form
first fat32(6.5g)
2nd ext2(500mb)
3rd ext4(500mb)
4th swap(500mb)

You can also have a look at DATA2SD (see my sig) and adapt it manually to your favorite ROM

Try this:
Download a terminal app from the market.
Open it, allow SU permissions.
Type "a2sd cachesd"
The phone should now reboot.
And, if need be, try my guide here.
http://androidforums.com/desire-tip...ed-device-noobs-guide-updated-09-02-11-a.html

sibere said:
You can also have a look at DATA2SD (see my sig) and adapt it manually to your favorite ROM
Click to expand...
Click to collapse
i read your useful guide but some where i had a problem.
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
E:\New folder\android-sdk\platform-tools>adb shell
~ # mount /system
mount /system
~ # mount /data
mount /data
~ # mount /sdcard
mount /sdcard
~ # exit
exit
E:\New folder\android-sdk\platform-tools>adb push c:\01data /system/etc/init.d
28 KB/s (367 bytes in 0.012s)
E:\New folder\android-sdk\platform-tools>adb shell
~ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
~ # cd /
cd /
~ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
~ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: can't open '/sd-ext/ext2': No such file or directory
~ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
mke2fs: can't open '/sd-ext/ext2': No such file or directory
i spend 8 hours to do it but.....

royalrose said:
i read your useful guide but some where i had a problem.
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
E:\New folder\android-sdk\platform-tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
error: device not found
E:\New folder\android-sdk\platform-tools>adb shell
~ # mount /system
mount /system
~ # mount /data
mount /data
~ # mount /sdcard
mount /sdcard
~ # exit
exit
E:\New folder\android-sdk\platform-tools>adb push c:\01data /system/etc/init.d
28 KB/s (367 bytes in 0.012s)
E:\New folder\android-sdk\platform-tools>adb shell
~ # chmod 755 /system/etc/init.d/01data
chmod 755 /system/etc/init.d/01data
~ # cd /
cd /
~ # mount /dev/block/mmcblk0p2 /sd-ext
mount /dev/block/mmcblk0p2 /sd-ext
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or director
y
Click to expand...
Click to collapse
Here is the problem, your recovery doesn't have sd-ext directory. You must create it with a mkdir /sd-ext command
~ # dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd if=/dev/zero of=/sd-ext/ext2 bs=1048576
dd: can't open '/sd-ext/ext2': No such file or directory
~ # /system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
/system/xbin/busybox mke2fs -F -L userdata /sd-ext/ext2
mke2fs: can't open '/sd-ext/ext2': No such file or directory
i spend 8 hours to do it but.....
Click to expand...
Click to collapse
How this is the old way with an ext2 file mounted via a loop device. Now it's an ext4 partition of max 2GB. Default is without journal but informations are provided to use journal for safety specially on AOSP ROMs.
Droidzone has created also some ready 2 flash ZIP files for both AOSP and SENSE ROMS. Check-out the OP page again.

thanks for tips

[Script] Flash recovery from Terminal v1.0 [2012_0513]

I have create a script file that will flash a recovery from the terminal in the Galaxy Nexus.
I got the command from xda but I could not remember it when I wanted to flash a recovery,
so I wrote a script to do it.
AS WITH ANY FLASHING OR MODDING OF "YOUR" PHONE, I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU MAY CAUSE!
I have tested this on my:
Unlocked Galaxy Nexus 4.1.1 takju (flashed from yakju)
Sprint Galaxy Nexus 4.0.4
Thanks to -viperboy- for help.
Code:
Created by Smurph82 2012_0512 (c) v1.0
flashr [-h] [-r] [-m] [-s s] -- Flash a recovery
to the Galaxy Nexus.
where:
-h show this help text
-r will reboot after flashing is complete.
-m image is in the root of the sdcard
-s source of the recovery image (/sdcard/recovery.img).
To use the script:
Download and Flash the script file from your current recovery
Or download the zip file and move the flashr file in the /system/bin folder to /system/bin with RootExplorer
or other root level file manager.
If you manually add the file you must
Code:
chmod 0755 /system/bin/flashr
or change the permissions from RootExplorer
Then open Terminal and type
Code:
su
first, yes you have to be rooted to do this!
Next type
Code:
flashr
or
Code:
flashr -h
to get the help
If you want to flash a recovery you must have the recovery.img
somewhere on your device that you can remember. Like the root of the sdcard.
To flash a recovery type
Code:
flashr -s /sdcard/recovery.img
or if the recovery is in the root of the sdcard type
Code:
flashr -ms recovery.img
If you want to reboot after the flashing is complete next use
Code:
flashr -mrs recovery.img
In the code examples above I used recovery.img as an example.
This should be "what ever you named the recovery".img it does not have to be recovery.

Reserved
Change Log:
v1 - Initial Release

i know you might think that im trolling, but im really not. what id like to know is what makes that better than just flashing the recovery, via the terminal, the old-fashioned way..
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter, if you want to go to the recovery)
providing ithe file is on the main fs in the sd storage.

flash_image does not work with ics, that I have found. So I wrote my own. If there is a new flash_image that works with the galaxy nexus then I could not find it. Maybe it is because I'm still using the stock rom and kernel. I took the flash_image out of cm9 but it didn't work for me.
Sent from my Galaxy Nexus using XDA Premium HD app

Would you be willing to share the sources for this? It would be interesting to know how this works, since it may be useful also for other purposes than flashing recovery images. Or not?

I will post the source later today. It really is not much.
Sent from my Transformer Prime TF201 using XDA Premium HD app

E:V:A said:
Would you be willing to share the sources for this? It would be interesting to know how this works, since it may be useful also for other purposes than flashing recovery images. Or not?
Click to expand...
Click to collapse
Hope that this is helpful to someone.
Code:
#!/system/bin/sh
usage="Created by Smurph82 2012_0512 (c) v1.0
flashr [-h] [-r] [-m] [-s s] -- Flash a recovery
to the Galaxy Nexus.
where:
-h show this help text
-r will reboot after flashing is complete.
-m image is in the root of the sdcard
-s source of the recovery image (/sdcard/recovery.img)."
# Read in the options turn off verbose and require -s to have input
while getopts :hrms: opt; do
case $opt in
h) echo "$usage"
echo
exit;;
m) sdroot="/sdcard/";;
s) sourcedir=$OPTARG;;
r) reboot="t";;
*) echo
echo
echo "Invalid option: -$OPTARG" >&2
echo "$usage"
echo
exit;;
esac
done
shift $(($OPTIND - 1))
# This was for testing
#echo
#echo "Vars: m $sdroot: s $sourcedir: r $reboot: dir $sdroot$sourcedir"
#echo
# Check to make sure somthing was typed if not show help
if [ "$sourcedir" == "" ]; then
echo "$usage"
echo
exit
else
# Check that something is in that location if not dont flash
if [ -s $sdroot$sourcedir ]; then
echo "Flashing image from: $sdroot$sourcedir"
cat $sdroot$sourcedir > /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
else
echo "File not found at $sdroot$sourcedir"
exit
fi
fi
# Early in the morning I was getting cute
if [ "$reboot" == "t" ]; then
echo "Rebooting in 5.."
sleep 1
echo "Rebooting in 4.."
sleep 1
echo "Rebooting in 3.."
sleep 1
echo "Rebooting in 2.."
sleep 1
echo "Rebooting in 1.."
sleep 1
reboot recovery
fi

thank u very much for this! so easy now!!

It is just as easily done in a terminal by the following (assuming you downloaded the recovery you want to /sdcard and named it recovery.img):
su
dd if=/sdcard/recovery.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/recovery

efrant said:
It is just as easily done in a terminal by the following (assuming you downloaded the recovery you want to /sdcard and named it recovery.img):
su
dd if=/sdcard/recovery.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/recovery
Click to expand...
Click to collapse
Yes I know that but who wants to type all of that out. I just made it shorter more
or else. If you want to type the whole command then by all means have at it. I just
think that "flashr -mrs twrp.img" is a whole lot easier. Just my thoughts.

Hi
Nice enough script.
Although I feel I should warn people that it looks like this script will write anything you tell it. making no effort to verify that the file is a valid or correct for your phone. so be careful not to specify the wrong file.
fastboot flash recovery $file is much safer.

That is true if you are connected to a computer but this script is run on the phone from the terminal. If someone knows a way to check a file from the terminal running on the phone please tell me and I will update the script. I understand that there is currently no verification of the file that is being written so please make sure that you are writing the right file.
Sent from my Galaxy Nexus using XDA Premium HD app

[HOW TO] Check your filesystem (a la 'fsck')

I've been having lots of trouble with my SD and local filesystems getting corrupted, which in turn has been causing the flush-179 process to go ballistic (100% CPU loop, reboot hangs, etc.). If only there was a way to run a quick FSCK(8) on my Android's unmounted filesystems to check for problems. Well, there is!
This may be old, old news to some of the more seasoned OS hackers, so please be kind with any negative feedback about it being intuitively obvious. It wasn't to me, but after some research and testing, I've come up with these simple steps:
Boot into Recovery
Connect via USB to ADB shell
Code:
C:\Scratch\Android> [B]adb devices[/B]
C:\Scratch\Android> [B]adb shell[/B]
Mount /system and /data to determine the /dev/block names, then umount each
Code:
~ # [B]mount /system[/B]
~ # [B]mount /data[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 308620 64 308556 0% /dev
/dev/block/mmcblk0p27
295509 121021 159231 43% /cache
/dev/block/mmcblk0p26
1184268 848052 276060 75% /data
/dev/block/mmcblk0p25
562384 461416 72400 86% /system
~ # [B]umount /system[/B]
~ # [B]umount /data[/B]
Run e2fsck against each /dev/block filesystem
Code:
~ # [B]e2fsck -n /dev/block/mmcblk0p25[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p25: clean, 4168/35760 files, 117605/142847 blocks
~ # [B]e2fsck -n /dev/block/mmcblk0p26[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p26: clean, 7173/75200 files, 216745/300799 blocks
~ #
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave

some help
ViperGeek said:
I've been having lots of trouble with my SD and local filesystems getting corrupted, which in turn has been causing the flush-179 process to go ballistic (100% CPU loop, reboot hangs, etc.). If only there was a way to run a quick on my Android's unmounted filesystems to check for problems. Well, there is!
This may be old, old news to some of the more seasoned OS hackers, so please be kind with any negative feedback about it being intuitively obvious. It wasn't to me, but after some research and testing, I've come up with these simple steps:
Boot into Recovery
Connect via USB to ADB shell
Code:
C:\Scratch\Android> [B]adb devices[/B]
C:\Scratch\Android> [B]adb shell[/B]
Mount /system and /data to determine the /dev/block names, then umount each
Code:
~ # [B]mount /system[/B]
~ # [B]mount /data[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 308620 64 308556 0% /dev
/dev/block/mmcblk0p27
295509 121021 159231 43% /cache
/dev/block/mmcblk0p26
1184268 848052 276060 75% /data
/dev/block/mmcblk0p25
562384 461416 72400 86% /system
~ # [B]umount /system[/B]
~ # [B]umount /data[/B]
Run e2fsck against each /dev/block filesystem
Code:
~ # [B]e2fsck -n /dev/block/mmcblk0p25[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p25: clean, 4168/35760 files, 117605/142847 blocks
~ # [B]e2fsck -n /dev/block/mmcblk0p26[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p26: clean, 7173/75200 files, 216745/300799 blocks
~ #
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave
Click to expand...
Click to collapse
on my phone i have a fiel called fsck.exfat and fsck_msod i think and im trying to run one (though not sure what the difference is) to fix some corrupted files in data internally. im trying to see if the file can be run through recovery without putting it through adb to unmount the data. im not too sure how to figure out what the data block is called because when i rum the mount i get a ton of different blocks (about 32 of them).
im trying to clean up the lost+found files i have and i have 3 of from a corrupted nandroid

robcop19 said:
on my phone i have a fiel called fsck.exfat and fsck_msod i think and im trying to run one (though not sure what the difference is) to fix some corrupted files in data internally. im trying to see if the file can be run through recovery without putting it through adb to unmount the data. im not too sure how to figure out what the data block is called because when i rum the mount i get a ton of different blocks (about 32 of them).
im trying to clean up the lost+found files i have and i have 3 of from a corrupted nandroid
Click to expand...
Click to collapse
Hi Rob.
I'm not sure if I can be of any specific assistance. exFAT is a type of filesystem format, like UNIX/Android ext3 and ext4, but beyond that, I couldn't tell you what those programs do. I do know that on some operating systems, the only way to fix the file chains and blocks is to make sure it's unmounted in single user mode. ADB is the closest we Android guys can get to UNIX single user mode without some clever Recovery Mode ZIP file programming.
– Dave

alrighty
ViperGeek said:
Hi Rob.
I'm not sure if I can be of any specific assistance. , but beyond that, I couldn't tell you what those programs do. I do know that on some operating systems, the only way to fix the file chains and blocks is to make sure it's unmounted in single user mode. ADB is the closest we Android guys can get to UNIX single user mode without some clever Recovery Mode ZIP file programming.
– Dave
Click to expand...
Click to collapse
well thank you for at least writing back on it. im not sure how to run adb let alone run the progrma to try and fix this but i will be learning up on it

robcop19 said:
well thank you for at least writing back on it. im not sure how to run adb let alone run the progrma to try and fix this but i will be learning up on it
Click to expand...
Click to collapse
ADB isn't all that difficult to use. Here's a good primer on it:
http://droidlessons.com/how-to-install-adb-on-a-windows-7-pc/
Once installed, just boot your phone into Recovery (power off completely, then power on with the Vol Down key held, then select RECOVERY). Once it's sitting there, connect your phone to the PC via USB, wait for Windows to find the right drivers, and you're connected. 'adb devices' should list your phone in the "List of devices attached", after which you're good to go.
– Dave
ps. I've not tried it personally, but there's supposedly a "universal USB driver" available here:
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH

wow
ViperGeek said:
ADB isn't all that difficult to use. Here's a good primer on it:
Once installed, just boot your phone into Recovery (power off completely, then power on with the Vol Down key held, then select RECOVERY). Once it's sitting there, connect your phone to the PC via USB, wait for Windows to find the right drivers, and you're connected. 'adb devices' should list your phone in the "List of devices attached", after which you're good to go.
– Dave
ps. I've not tried it personally, but there's supposedly a "universal USB driver" available here:
Wow thank you very much for the help youre giving me I will see if i can go and start finding a solution
Click to expand...
Click to collapse

ViperGeek said:
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave
Click to expand...
Click to collapse
I figured this out about a week ago now I guess and did indeed find that there were corrupted partitions. My phone had been acting up for several weeks before and it pretty much unusable now. I do manage to clean system and data up, and was even able to flash a new ROM which I hadn't been able to, they'd always abort.
I have a question though, is this only good for ext2 partitions? I have the same version as shown in the tutorial and if you run 'e2fsck -V' the output makes me think that maybe it's not happy checking ext3 and ext4 partitions and that's why i was popping up errors, or at least that's why even when i fixed errors it maybe wasn't really fixing the issue.
Thanks.
I've got a different phone, but a search brought me here to this thread. I think my issues though are more corrupted memory rather than device specific so hope you don't mind my post here.

I think this will answer your question
http://linux.die.net/man/8/fsck.ext3
(It should be good for all ext partitions)
Sent from my Galaxy Nexus using Xparent Cyan Tapatalk 2

ahh the good old fsck
glad i found this thread
thanks a lot mannnn

One more helpful tidbit.
Even if you run 'e2fsck -n' and find a "clean" file system, it may be useful to force a scan via 'e2fsck -f'. This just happened to me. I had something funny going on, and so rebooted into recovery and checked my file systems. Everything was cool like Fonzie, which I didn't believe, and so I used 'e2fsck -f' and found lots of fuglies that got fixed.
Be careful running -f on a cross-linked file system like the /data partition on a Galaxy S3/S4. It can have the tendency to unlink the elfin magic Samsung used and make a mess.
- Dave

(Double-tap post deleted)

This will not work with stock Android - default boot to recovery doesn't enable adb - you have to have CWM for that.
So, the questions remains - how can I run e2fsck without rooting my phone (and possibly voiding its warranty)?

How do I get the Moto X in Recovery mode to accept the adb command?
Because when I put in Recovery (Android Robot lying down) mode, the command adb and fastboot are not recognized.

Can this be done in terminal? And would I need su?

PRose61 said:
Can this be done in terminal? And would I need su?
Click to expand...
Click to collapse
Yes, this can be done in terminal on the phone itself. You do need root/su.

ApTeM said:
This will not work with stock Android - default boot to recovery doesn't enable adb - you have to have CWM for that.
So, the questions remains - how can I run e2fsck without rooting my phone (and possibly voiding its warranty)?
Click to expand...
Click to collapse
Is this why I get can't read '/etc/fstab': No such file or directory?
I'm using a stock Samsung S2, but it is rooted and has superuser and busybox.

Code:
ViperGeek said:
I've been having lots of trouble with my SD and local filesystems getting corrupted, which in turn has been causing the flush-179 process to go ballistic (100% CPU loop, reboot hangs, etc.). If only there was a way to run a quick on my Android's unmounted filesystems to check for problems. Well, there is!
This may be old, old news to some of the more seasoned OS hackers, so please be kind with any negative feedback about it being intuitively obvious. It wasn't to me, but after some research and testing, I've come up with these simple steps:
Boot into Recovery
Connect via USB to ADB shell
Code:
C:\Scratch\Android> [B]adb devices[/B]
C:\Scratch\Android> [B]adb shell[/B]
Mount /system and /data to determine the /dev/block names, then umount each
Code:
~ # [B]mount /system[/B]
~ # [B]mount /data[/B]
~ # [B]df[/B]
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 308620 64 308556 0% /dev
/dev/block/mmcblk0p27
295509 121021 159231 43% /cache
/dev/block/mmcblk0p26
1184268 848052 276060 75% /data
/dev/block/mmcblk0p25
562384 461416 72400 86% /system
~ # [B]umount /system[/B]
~ # [B]umount /data[/B]
Run e2fsck against each /dev/block filesystem
Code:
~ # [B]e2fsck -n /dev/block/mmcblk0p25[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p25: clean, 4168/35760 files, 117605/142847 blocks
~ # [B]e2fsck -n /dev/block/mmcblk0p26[/B]
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p26: clean, 7173/75200 files, 216745/300799 blocks
~ #
The 'e2fsck' command takes the same command-line switches as UNIX FSCK(8), so you can be as creative and daring as you need.
- Dave
Click to expand...
Click to collapse
Thank you for your very well done post. I also realize that this thread is very old. Still it is the best I have found after days of looking. And finally, I have a different phone. Having said that perhaps someone might help.
My phone is a Galaxy S5 Verizon SM-G900V running KitKat 4.4.4. I have root on the phone, but am running stock Verizon Kitkat with stock recovery.
So I have used ADB by plugging in my phone via USB to my Windows computer. I can get root in ADB and find the /data filesystem and its /dev/block/... device. But when I try to
Code:
umount /data
I get a response that the filesystem is busy. This makes sense.
I have booted into recovery via VOL UP + HOME + POWER and it takes me to the RECOVERY menu. But the only option that connects with my ADB shell is "apply update from ADB". When you use the command
Code:
ADB devices
, my phone shows up, but as "phoneid" sideload, and
Code:
ADB shell
exits immediately.
I have also tried to use a terminal shell and then su to root. Again I cannot umount /data since it is busy. (Of course it is, I am using it...)
And finally I have tried
Code:
touch /forcefsck
to create that file in the root directory. This is supposed to force a fsck during boot up. But the root directory (/) is read only. So you can't write the file to it.
I am at my wits end. What I really need to do is mark the /data filesystem as dirty and have the system check it on reboot. But I can't find anyway to do it.
So if anyone can help, I would be very grateful
Joe