yashsingh1/xdaforums huggingface dataset:
[Desire HD Android Development] joostnl:
Downloaded yesterday: 3.0.2.6 from

newest

rom manager and it works great!
[Desire HD Android Development] CodeNameUnknown1:
i clicked on the .exe file and the Phone was on FastBoot USB, but it still didnt work.

It would send the .img file to the phone, but wouldnt install it, it just reboots - (Gives me the FAILED text on cmd)

any solution?
[Desire HD Android Development] baltazar.nilsson:
Bad download.. Download again and check MD5 checksum before flashing to see that it downloaded OK..

EDIT: @JDMJOSH

It´s the same for you as above..
[Desire HD Android Development] SERGI.3210:
flashed now!!!! and working perfect... pressing thanks button
[Desire HD Android Development] ATZ-007:
On RM, why is 3.0.2.6 still the latest version when .8 been out for awhile?

Sent from my Desire HD
[Desire HD Android Development] Mr_JMM:
Because like has been mentioned SEVERAL times already, it takes a little time for ROM Manager to be updated.

Sent using witchcraft via XDA Developers Premium App.
[Desire HD Android Development] ATZ-007:
Few pages back someone mentioned that it takes couple of days or few days but .8 been out for little while now so I was wondering if there is any problem with the new version... That's all

Sent from my Desire HD
[Desire HD Android Development] Mr_JMM:
I guess it depends on how busy Koush is.

The guy does good work (ignoring references to being a asp developer *spit*) so I'm happy to let him sort things out in his own time.

And before anyone asks for an ETA, that is considered a faux-pas so please don't.
[Desire HD Android Development] Spyr0s:
Anyone know why recovery fails to format cache partition to ext4 with a flashable script?

E:Error in /sdcard/LeeDrOiD_EXT4_FULL_WIPE.zip

(Status 1)

#Updater-script LeeDrOiD HD
#For the HTC Desire HD (ace)
#Follow me on Twitter @LeeDrOiD

show_progress(0.500000, 0);

ui_print("-Checking Model ID");
assert(getprop("ro.product.device") == "ace" || getprop("ro.build.product") == "ace" || getprop("ro.product.board") == "ace");
ui_print("-Success!");
ui_print("-Model ID - HTC Ace");
ui_print("-Ok to proceed");
ui_print("Now preparing for a clean install of LeeDrOiD HD V3.X.X GB");
ui_print("Please be patient");
ui_print("1st boot may take a few minutes");

show_progress(0.500000, 40);

ui_print("-Formatting Data");
format("ext4", "EMMC", "/dev/block/mmcblk0p26");
mount("ext4", "EMMC", "/dev/block/mmcblk0p26", "/data");

ui_print("-Formatting System");
format("ext4", "EMMC", "/dev/block/mmcblk0p25");
ui_print("-Writing System");
mount("ext4", "EMMC", "/dev/block/mmcblk0p25", "/system");
package_extract_dir("system", "/system");

show_progress(0.400000, 0);

ui_print("-Formatting Cache");
format("ext4", "EMMC", "/dev/block/mmcblk0p27");

show_progress(0.100000, 0);
ui_print("-Cleaning Complete");
ui_print(" ");
ui_print(" ");
ui_print("-Now flash the rom!");
ui_print(" ");
ui_print(" ");
unmount("/data");
unmount("/system");
unmount("/cache");
[Desire HD Android Development] :
Thanks for this!
[Desire HD Android Development] mero01:
Is it possible to have " Adb logcat " from within CWM ?
[Desire HD Android Development] hirotearii:
Working perfectly!

thx a lot!!!!! :)
[Desire HD Android Development] Spyr0s:
Any answer on why we can't format cache partition to EXT4 through recovery?
[Desire HD Android Development] ioneng:
Is there any way we can change the size of /system and /data partitions? I use cm7 and there are 400MB of empty space on the /system partition. When I still used hd2, I could flash recovery with different partition sizes, is this the same with DHD? if not, is it possible at all?
[Desire HD Android Development] Boskoel03:
Hi have strange thing going on,flashed 3.0.2.8,and all worked just fine,now when i wont to flash rom there is only opening update,instaling update,reflashed recovery,and flashed rom once,now even that not helps, i am constatly on cm7 nightly and i00.rom changing beetwen,but alwaus full wipe manualy,any answer please?
[Desire HD Android Development] bartolinio:
Are there any plans for adding to CWM formatting partition in the system EXT4?

because we have not impossible to restore the nandroid backup ROMs, which are base on the EXT4 partitions :(
[Desire HD Android Development] BumAround:
I have a question: If I do restore from the "Advanced Restore" and only choose "restore data", what exactly am I restoring?
[Desire HD Android Development] mike1986.:
@udK

Is it possible you can make alternate version with EXT4 formatting and EXT4 NANDROID? Just like it was done here - http://4pda.ru/forum/index.php?showtopic=194571&view=findpost&p=7648148
[Desire HD Android Development] Software Guru:
Works perfectly

However ROM manager still shows v3.0.2.6 but booting into recovery shows it

correctly as 3.0.2.8

;)
[Desire HD Android Development] kalagas:
You mean that now if we get f.e a Nandroid Backup of ARHD 5.1.7 with 3.0.2.8, then we CAN'T restore it??
[Desire HD Android Development] mike1986.:
You CAN restore it but it will be EXT3. NANDROID backup is not working like 1:1 image. Restoring (full) works this way:

1. Formatting cache, system and data partition in EXT3

2. Restoring cache, system and data partition file by file
[Desire HD Android Development] quezacotl:
Thank you for the new ClockworkMod!
[Desire HD Android Development] kalagas:
So for now CWM doesn't support ext4...

So i would prefer to re-install ROM from beggining cause i like the ext4...
[Desire HD Android Development] ein777er:
@mike

I this case it should be possible to restore a nandroid backup done with 3.0.2.6 with the new 3.0.2.8 EXT4 version, IF all partitions will formatted by CWM as EXT4?!

Do I think correct, or faulty?

regards
[Desire HD Android Development] udK:
First post updated, 3.2.0.0 available!
[Desire HD Android Development] icematrix:
Thanks My Boss :D
[Desire HD Android Development] DubelBoom:
thats new on 3.2.0.0??
[Desire HD Android Development] valcyone:
@udK

Does the new version 3.2.0.0 support EXT4?

I mean, does it include EXT4 formatting and EXT4 NANDROID?
[Desire HD Android Development] Moskiller:
When 3.2.0.0 will be released on Rom Manager? It stops to 3.0.2.6 :(
[Desire HD Android Development] itsme_4ucz:
Thanks for the new ClockworkMod!
[Desire HD Android Development] fotone:
Thanks.

:)
[Desire HD Android Development] dannyling:
Any one got any ideas as to what's new in recovery ,
[Desire HD Android Development] preacher65:
I've just tested this on my phone, and it still formats and restores as ext3.
[Desire HD Android Development] Patrics83:
I can confirm that :/
[Desire HD Android Development] udK:
No.

Probably never!
[Desire HD Android Development] RichmondoUK:
sd-ext

hmm can't see my sd-ext partition to mount, etc. not tried if it formats on delete data/factory!
[Desire HD Android Development] Moskiller:
why?:confused:

I can't download zip, can someone give me another link?
[Desire HD Android Development] :
When I do a wipe data/factory reset with CWM usually you get to see the process log on the screen but with 3.2.0.0 the process log disappears after the operation. So is that normal for the new 3.2.0.0? Or am I the only one experiencing this?
[Desire HD Android Development] preacher65:
Because Koush controls what is available through ROM Manager. udK is kindly compiling these for our DHDs from Koush's source code.

See this post:
[Desire HD Android Development] quezacotl:
Flash unsuccessful?

hm, I flashed v3.2.0.0 in fastboot menu and it restarted the device instantly. but it still says v3.0.2.6 on CWM menu... did i do anything wrong :confused:
[Desire HD Android Development] :
Do you mean ROM Manager or CWM? Mine says 3.2.0.0
[Desire HD Android Development] preacher65:
Do you mean in ROM Manager or in CWM? ROM Manager won't display the correct version number but will still work. If it still shows the 3.0.2.6 version number in CWM itself then the flash didn't work properly.
[Desire HD Android Development] SERGI.3210:
yeah... rom manager still shows 3.0.2.6 but the labbel that is into CWM changues... ;)

anyone has tested this version?

i´m afraid for if anything goes badly.....

like the problem of bricked devices in older versions....
[Desire HD Android Development] quezacotl:
CWM still v3.0.2.6

It was in CWM itself that still says v3.0.2.6 instead of the new CWM that I flashed (v3.2.0.0)

My ROM Manager is v4.2.0.2 (it also says v3.0.2.6 for CWM as well)
[Desire HD Android Development] SERGI.3210:
u tried to reflash it again?
[Desire HD Android Development] SERGI.3210:
ok i flashed it can´t wait lol... can u give me the changue log? the page that is in the first post redirects to git-hub.... i can´t see the changuelog there...thank´s!!!!!:)
[Desire HD Android Development] :
strange, 3.2.0.0 doesn't seem to wipe my ext partition. Gone back to 3.0.2.8 for now.
[Desire HD Android Development] BumAround:
+1

there's no more option to wipe off ext partition.

So best course of action is reverting back to 3.0.2.8 which is very good in itself.
[Desire HD Android Development] nitr00:
Can we expect EXT4 support anytime soon?
[Desire HD Android Development] Steven_belfast:
Flashed a few days ago,

No issues at all working great,

Keep up the good work folks :)
[Desire HD Android Development] vBB:
I was wondering if my old backup from 3.0.2.6 version of CWM will work (I would be able to restore it) on CWM 3.2.0.0?
[Desire HD Android Development] PayAndDie:
Please i need ur help

ROM Manager is v4.3.0.1

ClockworkMod is 3.0.2.6

what does it means? do i have rightly flashed 3.2.0.0?
[Desire HD Android Development] :
Please bring back the feature for wiping /sd/ext partition.
[Desire HD Android Development] BumAround:
Check THIS out, credit goes to whoever authored/posted it up.

If you find it useful, click THANKS. :D
[Desire HD Android Development] PayAndDie:
hell yeah, got it :)

just installed it again
[Desire HD Android Development] deadnc34:
Evrything works fine. Thx
[Desire HD Android Development] Patrics83:
Hit the thanks button in the correct post :p
[Desire HD Android Development] gongoscho:
I think this is a problem with ROM Manager. Maybe the v3.2.0.0 CWM-RECOVERY is not online..

On your sd card is a folder: "clockworkmod" and in this folder is a settings file: ".settings" from ROM Manager

{"is_clockworkmod":true,"current_recovery_version":"3.0.2.6","readonly_recovery":false,"recovery_timestamp":1305978533119,"flash_recovery":"dd if=%s of=\/dev\/block\/mmcblk0p21 bs=262144 ; ","reboot_recovery":"","detected_device":"ace"}

Flash the recovery without ROM Manager:

grEEtZ,

gongoscho
[Desire HD Android Development] nteeb:
I use recovery 3.0.6.2.

Does it mean that I can't nand.backup formerly ext4-formatted system-only in ext3?Even if I flashed fullwipe1.5 ext4 before install the rom?Everything will backed up(and later restore) in ext3 using that recovery?

I asked because I did it:right after my restore(using cwm 3.0.2.6) I see all the partitions(system, data, and cache) remained ext4(used Android System info to check it).

So what are the benefits using f.e. CWM Recovery 3.0.2.8 EXT4 version?
[Desire HD Android Development] preacher65:
If you check that way, all you can tell is whether your ROM mounts the partitions as ext4. It can do this even if they are formatted as ext3.

To check if they're formatted as ext4, use adb. Go to recovery, connect your USB cable, then from a command prompt type:

adb shell "mount /system"
adb shell "mount /data"
adb shell "mount | grep ext"

If your partitions are formatted as ext4, you should see results like this:

/dev/block/mmcblk0p27 on /cache type [B]ext4[/B] (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p26 on /data type [B]ext4[/B] (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)
/dev/block/mmcblk0p25 on /system type [B]ext4[/B] (rw,nodev,noatime,nodiratime,barrier=1,data=ordered)

As to the benefits of ext4 formatting compared to just mounting ext3 as ext4, that's debatable :) but some people say they see a speed improvement.

Edit: This method seems more reliable: http://xdaforums.com/showthread.php?p=14421249#post14421249
[Desire HD Android Development] nteeb:
OK, I tried it and all the partitions are ext4.

I formatted them before, using Fullwipe 1.5 ext4.zip, but later I backed up the system with recovery 3.0.2.6, which is known not to handle ext4, only ext3, if I know well.So I expected to find ext3 partitions after restoring from this backup.

Did I misunderstand something???
[Desire HD Android Development] preacher65:
Did you definitely do this while the phone was in CWM? Which ROM are you on?
[Desire HD Android Development] nteeb:
Yes, it was in cwm, and I use K@ng@r00 0.5.
[Desire HD Android Development] preacher65:
Honestly, I'm stumped. Myself and quite a few others tested backup and restore with CWM 3.0.2.6, and it always restored as ext3. :confused:
[Desire HD Android Development] nteeb:
OK, just to test again, I made the followings:

1.Flashed recovery 3.0.2.8

2.From recovery flashed Fullwipe 1.5 ext4(just to be sure...), and right after that Sergio's Core Droid HD 6.7

3.Reboot:all the partitions are in ext4.

Now I flashed recovery 3.0.2.6 and

4.Nand.Backup my current system from recovery(N.B.:with the old recovery!)

5.Restart the system, and later back to Recovery(not into RomManager...)

6.Restore the system from this backup

7.Reboot:all the partitions remained ext4(using Terminal Emulator with command "mount")

So what it is now???:eek:
[Desire HD Android Development] gongoscho:
[FIX] ROM Manager for newer ClockworkMod Recovery versions!

The ROM Manager from ClockwordMod show now only recovery images from v2.5.1.4 to v3.0.2.5.

To fix it with a newer version of ClockworkMod Recovery: v3.0.2.8, v3.2.0.0, this steps are needed or only extract attached files:

Open the ".settings" file in the "clockworkmod" folder on your sdcard with a editor (notepad++) and edit the version nummer to your recovery version. Here is a example for v3.0.2.8:

"is_clockworkmod":true,"current_recovery_version":"3.0.2.8","readonly_recovery":false,"recovery_timestamp":1306870389048,"flash_recovery":"dd if=%s of=\/dev\/block\/mmcblk0p21 bs=262144 ; ","reboot_recovery":"","detected_device":"ace"}

Delete all files and folder in the "download" folder from "clockworkmod" folder but NOT the "-2110140792" file!

Open the "-2110140792" file with a editor (notepad++) and find the "HTC Desire HD" section and edit the version nummers to your recovery version. Here is a example for v3.0.2.8:

{
"name": "HTC Desire HD",
"flash_recovery": "dd if=%s of=/dev/block/mmcblk0p21 bs=262144 ; ",
"version": "3.0.2.8",
"init": "init.spade.rc",
"legacy_versions": [
"3.0.2.8",
"3.0.2.5",
"3.0.0.6",
"3.0.0.5",
"2.5.1.4",
"3.0.2.8"
],
"key": "ace"
},

I have attached fixes for v3.0.2.8, v3.2.0.0. Only extract on your sdcard and the Rom Manager detect the correct version of your recovery!

grEEtZ,

gongoscho
[Desire HD Android Development] ippoglosso:
thanks but unfortunately the problem remains

Ippo
[Desire HD Android Development] Doo Doo:
can this be flashed without having ENG S-Off if so how?
[Desire HD Android Development] gongoscho:
With this fix the Rom Manager detect the correct version of your recovery and you can use the Rom Manager!

grEEtZ,

gongoscho
[Desire HD Android Development] preacher65:
We seem to be going round in circles here. ;) If you type "mount" in Terminal Emulater, it will show ext4 as that's how the partitions are

mounted

by Android. If you want to know how they are

formatted

, see this post:

http://xdaforums.com/showpost.php?p=14371592&postcount=291

Edit: The results you get from the link above seem to vary on different CWM builds. I think the method below is more reliable.

Or do this:

1. While in Android or CWM, connect your phone to PC using USB cable.

2. Open a command prompt.

3. Type

adb shell "tune2fs -l /dev/block/mmcblk0p25 | grep features"

4. You will get a result back like this:

Filesystem features: has_journal resize_inode filetype [B]extent[/B] sparse_super large_file

5. If the word "extent" (or "extents") appears then you have ext4 on this partition, which is the system partition. You can do the same thing again but change the partition:

mmcblk0p25 is system

mmcblk0p26 is data

mmcblk0p27 is cache

mmcblk0p28 is devlog

Beyond this, I'm not really sure what you're trying to ask or to achieve, sorry. :confused:

Edit: I've linked this post from a few places now, so I'll say here what I've said elsewhere: I'm not an expert on linux filesystems, I just adapted this from info I found on the web. If anyone sees any technical errors, please let me know.
[Desire HD Android Development] ippoglosso:
thanks, then it is only fair if I see

Current Recovery 3.2.0.0

and the list there are still only the old versions?

Tks
[Desire HD Android Development] globalm:
Two issues with 3.2.0.0. The first I'm re-iterating if I understand the previous posts correctly

Firstly, ROM Manager does not identify the version of CWM correctly even with the fixes previously published.

Secondly, a nandroid backup with CWM produces the error , "No SD-Ext found. Skipping backup" even though there IS an SD-Ext partiton.

Can anyone help please?

Thanks.
[Desire HD Android Development] preacher65:
I don't use sd-ext myself, but according to other posts in this thread, 3.2.0.0 has some issues with it - unable to mount, unable to wipe.

I would use 3.0.2.8, which is also linked in the first post, as this apparently works fine with sd-ext. The main change with 3.2.0.0 seems to be the ability to mount/wipe devlog, and I'm not really sure how useful that is.

Haven't tried the fix for ROM Manager yet, though I plan to, so I can't comment on that. I prefer doing everything through CWM, so I can see the results before I reboot. I just use RM to rename any backup files I want to label in a particular way, so I don't accidentally delete them. :cool:
[Desire HD Android Development] BumAround:
+1

Just use the 3.0.2.8 for now, choose the version with EXT4.

As for ROM Manager won't detect, the problem lies with the ROM Manager.
[Desire HD Android Development] globalm:
Thanks for the info.

I've reverted to 3.0.2.8 which seems fine.

The ROM Manager issue is an annoyance but hardly a show-stopper!

Thanks again.
[Desire HD Android Development] BumAround:
Sorry if this comes up bit late, but HERE is the version of 3.2.0.0 with working ext4, posted by alienmind on his ROM thread.

Use at your own risk. FWIW, 3.0.2.8 works just fine.
[Desire HD Android Development] quarkw:
I tried n nthng changd. Is thre a way to install dirctly in recoveey mode?
[Desire HD Android Development] nteeb:
OK, I was blind and didn't read everything you mentioned earlier(to go to recovery and mount system+data).Everything is clear now, and of course you have truth.

Thanks for your patience.
[Desire HD Android Development] Doo Doo:
can somebody tell me if this can be flashed without having eng s-off & if so explain to me how please
[Desire HD Android Development] kshting:
You need eng s-off in order to flash a custom recovery image. There are two ways:

1. Through fastboot:

in window's cmd type adb reboot bootloader. While in bootloader (fastboot) type fastboot flash recovery nameofyourrecovery.img, after that type fastboot reboot

2. Through terminal emulator:

type

su

flash_image recovery /sdcard/nameofyourrecovery.img

Hope this helps.
[Desire HD Android Development] Doo Doo:
is there a workaround for just radio s-off?
[Desire HD Android Development] kshting:
I'm afraid not, you need eng s-off to use fastboot to flash any image file or even through terminal emulator.

Here is the one click eng s-off by jkoljo: http://xdaforums.com/showthread.php?t=855403&highlight=one+click+eng+s-off
[Desire HD Android Development] Doo Doo:
i don't really wanna flash eng s-off i heard it can brick your phone if not used right & i don't want to take that chance ya digg

im pretty sure there is a way to flash this without eng s-off
[Desire HD Android Development] kshting:
Yes, I understand how you feel, but if you do follow the guide closely, I am sure you would be successful most times. Flashing is always risk involved.

Anyway, as far as I am concerned, you need eng s-off, if there is any other way, then my apology for not being able to help any further. Maybe others would be able to provide an alternate way.

All the best.
[Desire HD Android Development] dnlilas:
Hello,

Does this version (3.2.0.0) or even 4.0.0.2 work well in nandroid backup/restore?

My past problem was with 3.0.2.6 version were the nandroid backup/restore was executed correctly, but after restore I got bootloop, which is weird.

Due to this problem I can no longer try different ROMs which is the benefit of rooted phone.

The problem occurred with CWM 3.0.2.6 restoring on LeeDroid 2.3.3 (Froyo).
[Desire HD Android Development] PDub11:
Ive flashed this but for some reason 3.2.0.0 and 3.0.2.8 are not showing at all in All CWM Recoveries.

Any ideas what im doing wrong?

im rooted, eng s-off etc.. running leedr0id.

Thanks.
[Desire HD Android Development] preacher65:
You can't flash these from ROM Manager, and RM will not display the correct version number.

There's post elsewhere in this thread on how to get ROM Manager to display the correct CWM version number, but it still won't be available in "All CWM Recoveries" - I think that does a check online to Koush's repository, and these newer versions aren't stored there.