yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] beanbean50:
good morning mr max,

love your latest version with the golden fonts, so much easier to read and 100% working fine :)

it's my birthday today and I have one birthday wish... I wish I had an update .zip of the latest version so I can use it in rom manager ...hehe :)
[Desire Android Development] madmaxx82:
HI ;)

Happy birthday!! Then we need to do that.. but already in bed right now.. 4:34am... Let's start later ok?

See you then and have a nice birthday!
[Desire Android Development] beanbean50:
sure no prob...have a nice sleep :)
[Desire Android Development] rophaq:
HAPPY 50th BIRTHDAY boy Beanbean,:):):)
[Desire Android Development] beanbean50:
49 actually....there's a big difference ...hehe
[Desire Android Development] rophaq:
so you're only 8 months ahead of me.:D:D
[Desire Android Development] freak69ize:
HAPPY B-DAY beanbean50!!
[Desire Android Development] madmaxx82:
Sorry freak, didn't see this post yesterday.

I'm sure you already figured that out?

Otherwise: red, green, blue in section "menu colours" for the menu, same for text, but in text section..
[Desire Android Development] angusc:
Good day Madmaxx,

I certainly have had fun today! tried to start from scratch in GParted on Linux Puppy to reformate my card. It seems that if i use the Recovery 2.0.2RC2 to do the formatting then test the card in Linux using Gparted that GParted will not show the partitions that Recovery created. Even though they all show good in the Recovery.

When i did the Partitions in Recovery then copied the files of my EXT4 partition that i had manually backed up on to my PC, then booted my device the rom fired up but the notification message that my memory card was not recognised.

Conversely when i delete all partitions and re create them using GParted the card is not recognised in Recover! Eventually i redid the format in Recovery and then re copied all my files back to the FAT32 and then Nandroid recovered my ROM.

We seem to be up and running again and i will e-mail to you the current recovery.log, please would you mind to check it and advise if it looks all ok for now.

I will be standing by for your next release to test it out, like the others I really like the new mustard yellow menues and graphics that you have now incorporated in version 2.1.0RC1!!
[Desire Android Development] madmaxx82:
Thnx :)

It's extremely strange what's happening with your sdcard.

By any chance: do you have a second one to try?

Although you are the only one yet.. this is certainly not great and I will try to fix your problem by changing pretty much in recovery for the next update.

One thing is for sure: parted does not recognize any partitions on your sdcard but quits with an error! Of course it also can't format your fat32 partition then.

I'm using parted only for detection and for formatting fat32 partitions..

Formatting sd-ext is done with mkfs.ext4 using optimizations you can override by tuning them yourself in 4ext.prop since the last version.

I suspect a bug in this version of parted...
[Desire Android Development] ziggy1001:
It's similar for me recovery detects Fat32 and ext partition identifies them correctly and reports perfect alignment. But before Linux would see both partitions when sd-card mounted and in GParted. Now for some reason only Fat32 is visible. Not a huge problem though:)
[Desire Android Development] madmaxx82:
Angusc's partitions are not detected at all ;)

Regarding partitions seen by the os:

Are u using the latest version?

This is the first one that reports all partitions to the os..
[Desire Android Development] michellin:
...................
[Desire Android Development] madmaxx82:
Sorry? What do you mean?
[Desire Android Development] michellin:
yes i know...but i cant see anything on the screen.

thats the problem.

the problem is "i cannot boot into recovery"

dont like sending my phone to htc service...

up to now, i've done it all myself.

this is a new one for me....i didnt do something forbidden.
[Desire Android Development] angusc:
I do have a 4GB card that i was previously playing around on fdisk and Linux with. I will try that one later today and let you know what results we get. When do you think the next release will be ready then?
[Desire Android Development] madmaxx82:
Ahh ok.

When you hold powerbutton + voldown.. do you see anything?

I mean in the bootloader that is starting when you do that.. BEFORE you can even select to boot into recovery..
[Desire Android Development] madmaxx82:
I don't know yet..

But I might just only change the whole detection first and send you the update.

So you got 2.1.0 RC1 + new detection..

Also I'll try to replace parted as a whole (also for formatting fat32 during partitioning)
[Desire Android Development] michellin:
NO nothing

but when i try to normally boot the phone, it vibrates.

and thats it.!!!!
[Desire Android Development] madmaxx82:
Okay.. this sounds really bad :(

Either your display is dead, or the bootloader got damaged when you used alpharevx :(

Did you follow the link someone posted a few sites in this thread before?
[Desire Android Development] madmaxx82:
BTW: I don't know what the symptoms are concerining the display when the bootloader is dead..

Does anyone know about that?

If the display is supposed to turn on regardless, then it should really be a dead display...
[Desire Android Development] madmaxx82:
Thanks to BeanBean50 who did all the testing and found all the files that need to be replaced, there is now a fake flash available to use for people who would like to use rom manager!

This is not a fake flash that works on its own when you haven't flashed a custom recovery!

For this to work you need to have 4EXTRecovery flashed.

Version should not matter.

For a "real" fake flash that works without having flashed a new recovery, I still need the kernel config from someone that didn't flash a recovery yet (someone who only used rom manager yet).

To make this work you need to replace update.zip that is directly on your sdcard with this one.

You also need to replace all other recovery-xxx.zip files in the clockwork folders. Just do a search on /sdcard/clockworkmod for "zip" and replace those files with the one that is attached to this post.

BIG THANKS TO BEANBEAN!!!

- download this update.zip

- put it onto your sdcard replacing any update.zip that might be already there

- do a search for "zip" in your clockworkmod folder

- replace all (one or two) zip files you might find there (usually named recovery-xxx.zip)

- now you should boot into 4EXT if you use your rom manager..
[Desire Android Development] madmaxx82:
Okay, I will dump parted as a whole in the next update ;)

Also for creating the fat32 file system when partitioning.

This should also reduce the size of the recovery by at least a few hundred kb and I hope speed up its boot!
[Desire Android Development] sjknight413:
You have yourself an SLCD brick, not sure how to fix it, google it. basically i think you flashed something [a rom or recovery image maybe? or an old version of alpharev] designed for amoled screens.

EDIT: i know you CAN fix it, so dont worry.

EDIT2: this might be of some use? http://xdaforums.com/showthread.php?t=748498

EDIT3!: another useful resource, will explain your problem in a lot more detail: http://androidforums.com/desire-all-things-root/226723-unbricking-slcd-bricked-desire-howto.html
[Desire Android Development] bmonster:
Not that bad, just flashed a rom that doesn't support SLCD, easy enough to fix.

Read This:

http://xdaforums.com/showthread.php?t=831734
[Desire Android Development] bmonster:
Your phone is working, although you can't see anything, power on with back button held down, you will go into bootloader but won't see anything, plug in usb and run the correct ruu for your phone, it will flash and your phone will be working again, do you have a gold card, if not you'll need an ruu for your provider.

http://xdaforums.com/showthread.php?t=695667
[Desire Android Development] themoviesss:
Installed 202rcb last week, now updated to you're latest version. Great improvement over CWMR, a lot more options, new color is a lot better/easier to read. Startup delay now on 7 secs, so I'm not complaining. Keep up the good work!

Swyped from XDA-app Htc Desire
[Desire Android Development] angusc:
Hi madmaxx,

I just sent you an e-mail with my logs from my 32GB card and using 2.1.0RC and guess what we also got a "sd_fstpes.log" output! for what ever reason it seems that todays reformatting of my card has possibly sorted it out and now it works. I'm just re downloading the later version that you e-mailed to me last night (not the 15 second delay one) to see what happens when i flash that version.

Let me know what thos recovery.logs look like to you.

EDIT: Just installed 2.1.0 RC1 and all good! One comment i just noticed that the EXT partition is listed first and before the FAT32. I cant remember if this was the case with the 2.0.2RC2 version. Is there any signioficance in that? we know that the FAT32 partition should always be before the EXT Partition. When i checked the card uding Mini Partition Tool it corrctly shows the FAT32 then the EXT4 which is how i partitioned the card. So just a comment if it is possible can the Recovery list the partitions in their actual order and if someone did have their EXT before their FAT then they would get a warning. (I know that if they used the Recovery to do the partitioning then this would never happen, but I'm thinking about people who first install this Recovery and may have partitioned their card incorrectly using Gparted or similar). I know that i made that mistake when i first started to use Ext4 partition for my +A2SD ROM.

EDIT 2: can you add a 1.5GB partition size to your list (1536 MiB) this is a popular size for those that want to use Data2SD i believe and also who have a lot of Apps to install.
[Desire Android Development] pascanu:
Just installed it and I really like it! Works quite well.

Request: can we have a setting that makes it remember defaults for backup? (i.e. when I backup I don't want it to backup the recovery or the 2-nd ext partition).

Regarding concerns of bricking your beloved Desire, it might be useful to remind everybody that you can test a recovery without flashing it by doing the following in fastboot mode:

fastboot [B][SIZE="4"]boot [/SIZE][/B][I]path[/I]:\recovery.img

instead of

fastboot [B][SIZE="4"]flash [/SIZE][/B]recovery [I]path[/I]:\recovery.img

After testing that everything works properly you can take the plunge and flash it.
[Desire Android Development] madmaxx82:
Yes will add that setting.

You are right, fastboot boot is convenient to test if something boots up or not.. but I don't see how this would prevent real damage..

If it was possible to brick a device so much that the display doesn't turn on anymore (from the start of, black screen inside the bootloader, et.c.), I don't see the difference if it was just loaded in ram, or flashed.. it was executed after all..

And keep in mind that the recovery won't work if you use fastboot boot...

You can only check if it boots up.
[Desire Android Development] madmaxx82:
Thanks to Ghisy, who sent me the original recovery's kernel config and tested this, there's now also a fake flash for those that still have the original recovery.

Ext4 support wasn't tested yet!

If anyone would try it out, would be great ;)

This is different to the previously posted update.zip in that it works when you have no custom recovery flashed..
[Desire Android Development] madmaxx82:
Doing that on an incredible s forces a reboot whenever you execute any function. Boot + adb works so it's definitely useful, but you cannot test anything more than that.

Might very well be that this behaves differently on the desire.
[Desire Android Development] madmaxx82:
First flashable 4EXT Themes :)

http://xdaforums.com/showthread.php?p=15716549#post15716549
[Desire Android Development] madmaxx82:
BTW: reporting "backups didn't work until this version" but now I'm here isn't very useful.

I was in the assumption that all backups worked since the last 2,3 versions. Until I got exactly 1 bugreport (where it could have been worked around by changing a value in the config).

Please report it earlier if you have a problem, so I can fix that asap!

Thnx!
[Desire Android Development] madmaxx82:
Updated first post with a "theme uninstaller". It will delete any flashed theme and revert to your custom settings you had before flashing that theme!
[Desire Android Development] Sebby:
hi madmaxx:D

i see you have still some little problems:mad:

i flashed the new version

and all is working (backup,restore,partition,enz):D

only thing i do if i partiton the complete sdcard

if the partitionning is done then i format the sdcard fat32 with gparted in mib

if i don't do that and don't format fat32 after partitioning then the speed off the sdcard is really slow around 5 a 6mb/s (the rom is slower to)

and if i format the sdcard fat32 after i partiton the sdcard with gparted

then my speed is around 11 a 12mb/s (and the rom speed is much faster to)

i dont use the usb with the recovery to transfer files (big files or a lot off files)

first it go's fast and then it stop's for 1min then it go's again)

still bad

and if i have a full background picture for the install screen

then the progress bar is at the bottom of the screen i see half of it

can you not make a option in 4ext.prop to move the progress bar up

oke thats all

and keep up the great work:D

the best recovery for the desire (number 1):D

oke see you:D
[Desire Android Development] madmaxx82:
Hi Sebastiaan ;)

Formatting fat32 is done with an older version of parted in the recovery. This might be the reason for your speed problem with fat32.

All other partitions (sd-ext)are formatted with mkfs.ext4 which is great.

From the next version on, I will drop parted completely (for detecting partitions AND formatting fat32), so this should solve any speed problem you might have with fat32 if formatted while partitioning.

About the progressbar: you need to use a picture as background with the right resolution for your device.. use the same resolution that's used on your device for the pictures, otherwise it is possible that it doesn't show correctly.
[Desire Android Development] Sebby:
That is now the strange thing about the progressbar

The picture is the same size of the resolution of my phone 480x800

Thats way i ask you about this
[Desire Android Development] madmaxx82:
That's strange!

I have not had any problems or reports like you describe yet. But then I also didn't have ANY reports regarding custom pictures on the Desire :D only incredible s, Desire HD and Desire S

Could you make a screenshot?
[Desire Android Development] Sebby:
i have sent you the picture by email
[Desire Android Development] madmaxx82:
So the progress bar is moved a little more towards the bottom of the phone when you have set a custom picture?

I have no picture to compare, so I don't know the exact difference when I look at the screens you sent me.

Could you try a lower res background picture? To see if the position of the progressbar changes..
[Desire Android Development] beanbean50:
good afternoon guys

wow massive hangover from last night never gonna drink again haha...

I'm trying to flash the custom theme (ThemeTeamDutchFlag) it says successful and reboots back into recovery but it's still the 'old' gold colour....any ideas what I'm doing wrong?
[Desire Android Development] madmaxx82:
Hi!

Great to read you had a long party :D

That's because Whiskey messed up this one :D

Just checked

The other two do work..

IF you want to fix it yourself just do the following:

Open the flashable zip, look inside the folder system/4ext and open 4ext.prop

Remove all lines past "bitmaps.usericons.location"

And set that option (bitmaps.usericons.location) from '/sdcard/4ext/icons'

to '/system/4ext/icons'

Then flash again.

I will tell Whiskey about the problem.
[Desire Android Development] Sebby:
a little more to the bottom , alot to the bottom

it is at the bottom of the screen and cut in half in lenght

it look like the bottom of the picture pushed the progressbar down

towards to bottom

if i do that the picture is centered to the middle

and then i see black bars around the picture

it is with all the full screen custom background picture's

try it with your phone a full screen custom background for the install screen

you see it pushed the progressbar down
[Desire Android Development] madmaxx82:
Can you try flashing one of those themes?

And see if you get the same problem?
[Desire Android Development] Sebby:
they have only a full main screen picture (icon_clockwork.png)

not a full install screen picture (icon_installing.png)

i looked at it already
[Desire Android Development] madmaxx82:
Okay I will look at that.

But I have extremely much todo at the moment.. have to get work finished by today evening. And there are more "technical" things that must be improved first.

But I promise you I will try to improve that issue with the installing picture.

The recovery must place the progressbar somewhere on top of your custom picture at the right position and not below it.

You could try to fix that by cutting your picture at the position where the progressbar should appear!
[Desire Android Development] Sebby:
oke thanks madmaxx:D

but i cant cut the picture at the bottom then the picture moves down (center to the middle of the screen)

then i have on top of the picture a black bar and at the bottom a black bar

i already tryed that (tryed everything) but no luck:confused:
[Desire Android Development] madmaxx82:
Grrrr, this must be possible somehow already now when it works with the default icon too..

Sorry, I really can't look into that now.. :(

But I will!
[Desire Android Development] Sebby:
madmaxx one more thing

progress_empty.png

progress_fill.png

what do's this do

is it the progressbar

are these png files in the recovery

if so can you sent it to me then i can try putting them in the

icon folder see what happens
[Desire Android Development] beanbean50:
Ha! yeah that's fixed it, now looking even cooler :) many thanks

*ironically whiskey also messed up my head last night...hehe
[Desire Android Development] madmaxx82:
Yes those are the progressbar.. but there are also more icons for it. Look at indeterminantex.png

If you put the original ones into your icons folder, it won't have any effect..

But you can customize them!

Here they are:
[Desire Android Development] madmaxx82:
:D

Great it worked!

He will upload a corrected version ;)
[Desire Android Development] Sebby:
hi madmaxx

i have here some recovery icons

it's the same size as the usb icon in your recovery

than you can put in the recovery

a install icon

and a error icon

looks better
[Desire Android Development] angusc:
Hi madmaxx,

I did not see any reply from you on the above to comments so bump it up again just in case you missed it yesterday.
[Desire Android Development] madmaxx82:
Hi!

Sorry missed that!

Regarding the fat32 partition: this was always like that.

The reason is that recovery will distribute all remaining space after you selected your sizes for sd-ext1/2 and swap to the fat32 partition..

It would be quite difficult to ask the user about a size for fat32..

But this has nothing to do with the partition order..

Fat32 will always be the first partition on your sdcard!

Regarding the size: yes of course this is possible. I will add all the sizes you need.

Maybe add a setting to add your own sizes in 4ext.prop.

Does anyone else have any suggestions about partition sizes I should add by default?

I already got a request for 34xMB.

So now there is 1.5, 34x... any other size I should add?
[Desire Android Development] madmaxx82:
Thanks for icons!

But you cannot make sure all users would like to have them. I will make a flashable zip with your icons and put it in 1st post as a download for alternative icons :)
[Desire Android Development] pascanu:
You are right, but reporting "it doesn't work" without any other info, logs etc. would be just as wrong. I was kind of busy and didn't have time to test and report properly.
[Desire Android Development] madmaxx82:
Yes, but it would help to KNOW that something doesn't work in the first place..
[Desire Android Development] Andreas75k:
Thanks, tried this today with my Desire GSM and installed LeeDrOiD HD port with it. All went well and I like the extended functionality of this recovery!
[Desire Android Development] Droidzone:
An excellent piece of work! Kudos!
[Desire Android Development] madmaxx82:
Fakeflash version download in 1st post ;)

Thanks to beanbean50 and Ghisy for testing and providing kernel config!
[Desire Android Development] beanbean50:
benben...?

LOL
[Desire Android Development] Ghisy:
No problem, glad I could help out! Sorry I wasn't able to try the ext4 support, I'm sure someone will do it and post some feedback!
[Desire Android Development] Droidxda:
:p nop yet :eek:

really nice work, i flash the recovery, update the rom manager zip file, and for the moment, everything is great :p
[Desire Android Development] madmaxx82:
**** :D

Sorry! Corrected it :)

Yes I suppose we will soon know :)

Thank you very much for the feedback.

Did you use this while you still have your original recovery flashed, or do you have 4ext "permanently" flashed either?
[Desire Android Development] o$$!ram:
I have a small problem: dont know if this is realy from your recovery but i think so ...

If i only wipe data and sd-ext from wipe menu i cant get any rom to work :( Then logcat only shows: "file dont found ...."

Only help: complete formation of all partitions ...
[Desire Android Development] madmaxx82:
Hi!

To find out what the problem might be, regardless if it has anything todo with this recovery or not, please repeat that process where it does not work for you and before you reboot send me your recovery.log (advanced menu/copy recovery.log to sdcard).

Please send it to the mail address in my sig :)
[Desire Android Development] Nekromantik:
good work :)

made this my permanent recovery!
[Desire Android Development] Droidxda:
Rom Manager

I have the mod on my permanent recovery, and i use Rom Manager too,

I follows the note, and change the update.zip on the SD root, and in the clockwordmod recovery, but i can't use Rom Manager, to restore, backup or manage ROM.

it only rebbot the phone un recovery, do anything and restart the phone.

Any ideas ?
[Desire Android Development] madmaxx82:
Thnx :)

Did you replace all the xxx-.zip files that might be in any subdirectory beneath clockworkmod on sd?

Sorry for the dumb question, but you replaced them keeping their names didn't you?

So if it was recovery-213.zip inside somewhere in /sdcard/clockworkmod you named the update.zip recovery-213.zip and then replaced recovery-213.zip?
[Desire Android Development] beanbean50:
after installing all 3 files did you reflash the rom manager...? (first option in rom manager)
[Desire Android Development] Droidxda:
No because the menu said recovery 2.5.0 last version.

Should I?

HTC Desire - Leedroid HD Port-R2

XDA application Premium
[Desire Android Development] beanbean50:
yep, most definately flash it...it will always say 'recovery 2.5.0 last version'...but it's lying...hehe :)
[Desire Android Development] Droidxda:
:) :) :) :)

Thank you. It's work :P

HTC Desire - Leedroid HD Port-R2

XDA application Premium
[Desire Android Development] madmaxx82:
:D

Hi BeanBean :)

So after replacing the files you still need to install recovery using rom manager?

So probably replacing update.zip on /sdcard isn't needed as it will be replaced by rom manager anyway.. hmm..
[Desire Android Development] beanbean50:
Hi,

yeah, I guess so...!

:)
[Desire Android Development] bmonster:
Still having no problems here with current version, and I'm a rom addict, so reckon I must have tried all roms to date.

The only one I had a slight problem with was leedroid, wouldn't Identify the rom name, which isn't a problem as I rename everything to get rid of the date.

Maxx, Do you have a newer version that requires testing.:)

Current Setup:

Model : Desire GSM SLCD

HBOOT : Alpha Rev S-Off Stock 0.93.0001

Current ROM : Reflex S 2.1.7

SD Card : PNY 16gig Class 10 15gig fat32, 1gig Ext4