But with my version, it doesn't work? Could you please try it and then check the log in the advanced menu to see what went wrong?
Sent from my Nexus S using Tapatalk
[RECOVERY][MOD][Desire][02-Nov-2011] Clockwork 5.0.2.7.111102
- Thread starter zyonee
- Start date
But with my version, it doesn't work? Could you please try it and then check the log in the advanced menu to see what went wrong?
Sent from my Nexus S using Tapatalk
But with my version, it doesn't work? Could you please try it and then check the log in the advanced menu to see what went wrong?
Sent from my Nexus S using Tapatalk
no i have been testing a new recovery from the desire s ext4recovery to work on my desire the guy is working on it to fix the little bugs so no i dont wan't to flash a other recovery
i am done for today ....sorry.....
But with my version, it doesn't work? Could you please try it and then check the log in the advanced menu to see what went wrong?
Sent from my Nexus S using Tapatalk
No problem formatting through a full wipe but there's an error formatting SD-Ext only (via mountage and storage).
Last edited:
Ok, then at least I know what to look for. Maybe it's the binary that isn't working, since the "full wipe" you're talking about most likely merely removes directories and files, while the formatting option actually runs a format binary.
Just my guess. I'll see if it can be fixed.
roalex: I discovered that in mmcutils/mmcutils.c, the file system parameter for mkfs.ext4 is written as -t ext4, but when running mkfs.ext4, it's listed as -T (capital letter). Does this make any difference? It seems people have been having trouble formatting from the "mounts and storage" menu, and maybe this is the cause?
did you remove NULL ext3 from fstab ? i didnt look to much as the syntax since it worked, if it works on my build it should work on yours
-T looks proper though since its what it says
this is the fstab.recovery i use
--------- beginning of /dev/log/system
I/Vold ( 104): xVold 2.1.3.2 (Revenge of the Sith) firing up
D/Vold ( 104): Volume sdcard (/mnt/sdcard) state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 104): Volume sdcard (/sd-ext) state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 104): Volume sdcard (/mnt/sdcard) state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 104): Volume sdcard (/mnt/sdcard) state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Vold ( 104): Trying to mount /sd-ext
I/Vold ( 104): /dev/block/vold/179:2 being considered for volume sdcard
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 1 (Idle-Unmounted) -> 3 (Checking)
I/Vold ( 104): Filesystem check completed OK
I/Vold ( 104): Creating /sd-ext/app
I/Vold ( 104): Creating /sd-ext/app-private
I/Vold ( 104): Creating /sd-ext/dalvik-cache
I/Vold ( 104): Creating /sd-ext/data
I/Vold ( 104): Device /dev/block/vold/179:2 mounted @ /sd-ext
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 3 (Checking) -> 4 (Mounted)
I/Vold ( 104): System properties set
works well for me with -T as well id change it if i were you
Last edited:
okie guys..how to update cwm recovery??? Do I need to use unrevoked again or just flash like normal zip???
Its not recommanded unless you are S-OFF, if you are then pick up the file, boot into the bootloader and flash it via fastboot, fastboot flash recovery patch_to_the_recovery\recovery.img
did you remove NULL ext3 from fstab ? i didnt look to much as the syntax since it worked, if it works on my build it should work on yours
-T looks proper though since its what it says
this is the fstab.recovery i use
--------- beginning of /dev/log/system
I/Vold ( 104): xVold 2.1.3.2 (Revenge of the Sith) firing up
D/Vold ( 104): Volume sdcard (/mnt/sdcard) state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 104): Volume sdcard (/sd-ext) state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 104): Volume sdcard (/mnt/sdcard) state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 0 (No-Media) -> 2 (Pending)
D/Vold ( 104): Volume sdcard (/mnt/sdcard) state changing 2 (Pending) -> 1 (Idle-Unmounted)
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 2 (Pending) -> 1 (Idle-Unmounted)
I/Vold ( 104): Trying to mount /sd-ext
I/Vold ( 104): /dev/block/vold/179:2 being considered for volume sdcard
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 1 (Idle-Unmounted) -> 3 (Checking)
I/Vold ( 104): Filesystem check completed OK
I/Vold ( 104): Creating /sd-ext/app
I/Vold ( 104): Creating /sd-ext/app-private
I/Vold ( 104): Creating /sd-ext/dalvik-cache
I/Vold ( 104): Creating /sd-ext/data
I/Vold ( 104): Device /dev/block/vold/179:2 mounted @ /sd-ext
D/Vold ( 104): Volume sdcard (/sd-ext) state changing 3 (Checking) -> 4 (Mounted)
I/Vold ( 104): System properties set
works well for me with -T as well id change it if i were you
Aha! I thought "NULL ext3" was needed for backward compatibility. How about other devices like Desire HD, LG Optimus 2X and Nexus S? Should they have the "NULL ext3" flags? I just want to get everything working properly on all these devices (and maybe more):
ace (Desire HD)
bravo (Desire)
buzz (Wildfire)
crespo (Nexus S)
p990 (Optimus 2X)
passion (Nexus One)
and I appreciate all your help very much!
its not and it will mess everything up trust me , leave it to ext 4 and you will see its working
Even when people are using ext3 partitions? I just want to be sure.
I just hope that it will also apply to system and data partitions on devices where these are also ext4 like nexus s, etc.
Sent from my Nexus S using Tapatalk
Last edited:
Even when people are using ext3 partitions? I just want to be sure.
I just hope that it will also apply to system and data partitions on devices where these are also ext4 like nexus s, etc.
Sent from my Nexus S using Tapatalk
this is made for Desire and others nand devices so not for those you speak of, for those you need to use the builtin features.
Hmm. Just wondering if there's any way to combine those features to make them work on both...
Sent from my Nexus S using Tapatalk
New version (4.0.0.5.z110623) uploaded. This should hopefully get ext4 working. Please test wiping, formatting, backup and restore with ext4 partition.
Hi.
If in the recovery, I go to "mounts and storage", then "format /sd.ext" gives a error. Is that normal?
Thanks.
If in the recovery, I go to "mounts and storage", then "format /sd.ext" gives a error. Is that normal?
Thanks.
What does the log feature say? Is it today's new version?
Sent from my Nexus S using Tapatalk
hello zyonee
the new recovery is working
-restore works
-backup works
-format boot cache data system sd-ext working
-and it is still ext4
if you wipe the battery stats you now see
deleting /data/system/batterystats.bin
now you can see that the file is delete (loving it)
i have pulled the recovery.log file
the new recovery is working
-restore works
-backup works
-format boot cache data system sd-ext working
-and it is still ext4
if you wipe the battery stats you now see
deleting /data/system/batterystats.bin
now you can see that the file is delete (loving it)
i have pulled the recovery.log file
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
27First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
- Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
- Added option to wipe cache partition and dalvik cache at the same time
- Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
- Rearranged wipe menu to avoid accidental factory wipes
- Added "Reboot Bootloader"
- Moved SD Card partitioning into a function of its own for both int/ext SD card
- Merged 5.0.2.6 sources from CM7 repo
- Added a menu choice of ext2/ext3/ext4 when partitioning SD card
- Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
- Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
- Added "Reboot bootloader" option in advanced menu.
- Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
- Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
- Reverted and correctly added roalex's ext4 additions.
- Modified recovery.fstab for ext4 support on some devices.
- Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
- Added "Advanced backup". Now you can backup/restore individual partitions.
- Some other commits from other devs in github
- Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
- Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
- Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.3about the ext4 thingy, its true if recovery.fstab is set to ext4 it will format ext4 but its meant for devices which use internal sdcards so it will not work properly for a2sdext, after 1 reboot it will die ><
if its set to ext3 in fstab it will work fine, but on every wipe/format your sd-ext will be ext3 again
so i played around a bit with this sources and i managed to make it wipe/format ext4 properly.
im using this fstab:
*we really don't want MISC in there.
my changed are located here , only the last 4 commits are needed, the others simply some tryouts which i reverted.
btw the ext4 format logic i added is pretty much Cool's Alignment script
for the brave ppl added a build as well.2
I think it'll be avaliable on github once koush pushes the update to his repo. Until then, look for @koush and @clockworkmod on Twitter for some news.
Sent from my Nexus S using Tapatalk
