yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] John_Blaze:
Idk.. ive never knew to much about how to partition.. i guess i should learn though eh? what is swap?
[Desire Android Development] TheUntouchable:
Flashed the new version. Thanks for the fast update!

The system, data and cache partition are now displayed. But for the capacity i only get an (null) and for free nothing but iB for system and data, cache seams to work.

partition | fs | capacity | free

mtd: successfully wrote block at 0

I:Set boot command ""

mount: mounting system on /system failed: Invalid argument

df: /system: can't find mount point

umount: can't umount /system: Invalid argument

system yaffs2 (null) iB

mount: mounting userdata on /data failed: No such file or directory

df: /data: can't find mount point

umount: can't umount /data: Invalid argument

data yaffs2 (null) iB

cache yaffs2 (null) 792.0iB

sd-ext ext4 1024 MiB 570.1MiB

mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy

sdcard fat32 14231 MiB 6.0GiB
[Desire Android Development] mattman83:
Stupid question, which install method is best for S-ON users?

M.
[Desire Android Development] John_Blaze:
Fake Flash method.. but i really see no reason to if your not S-OFF.. its really not hard to do.. unless you dont wanna void your warranty.
[Desire Android Development] mattman83:
Yeah i know, i'm just trying to help another user who needs the fix permissions. Was trying to keep it simple but I think S-OFF is probably easier in that case :)

M.
[Desire Android Development] John_Blaze:
Yea exactly.. S-OFF is the way to go i believe
[Desire Android Development] Smiffyboots:
Fantastic work! Thank you for your hard efforts :)
[Desire Android Development] mattman83:
Yep that's what I've recommended in the end, put myself back on 4EXT at the same time too (i really wasn't having a crack at 4EXT the other day when i had issues LOL - I think it's awesome).

M.
[Desire Android Development] madmaxx82:
ok, bad luck :(

I hope displaying free space/capacity without yaffs2 partitions is sufficient for the next two weeks ;)

I won't support that version since there is a final around.

Need to get ready with the next one where the detection works completely differently and so it's wasted time to get that done for yaffs2 in v2.
[Desire Android Development] madmaxx82:
thnx very much :)
[Desire Android Development] keyra74:
no problem so far, just that it takes a while to show
[Desire Android Development] madmaxx82:
Maybe I should upload another update that removes displaying of yaffs2 again.. since it doesn't look nice at all.

However: If anyone gets any problem in 2.1.2, please downgrade to the final version (2.1.1b).
[Desire Android Development] jigners:
excellent conception! works well in conjunction with SuperNova Xtreme Official GingerBread 03/Aug| Stable Data2SD | Unlimited memory
[Desire Android Development] TheUntouchable:
Its okey ;) I can wait for the next to weeks! If you need someone to test it let me know ;)
[Desire Android Development] madmaxx82:
Thank you both :)

I have removed 2.1.2 because of this doesn't look very nice.

Anyone can keep their 2.1.2, it doesn't effect any functionality, just cosmetics.

Will upload 2.1.2b that doesn't include yaffs2 output like in any previous version.
[Desire Android Development] John_Blaze:
Ok thanks Max.. you the Man!! ;) :D
[Desire Android Development] madmaxx82:
:D

Okay uploaded 2.1.2b with removed yaffs2 info display.

Also moved text output a little bit higher so it doesn't interfere with the progressbar anymore.
[Desire Android Development] madmaxx82:
I need your help guys :)

Just received my Desire locked to orange uk.

When I first booted the phone, the battery might have been depleted, although I booted it while conntected via usb.

There was also no sdcard inserted..

And I didn't insert any simcard..

I moved around the homescreen when I accidentally touched the track button.

The phone rebooted automatically and is now in a boot loop.

I then booted into bootloader and chose clear storage.

Then it auto rebooted as it said on the screen and while booting again the battery vibrated I think 3 times.. now stuck at HTC logo.

Now my question is:

Are that signs of a hardware defect?

This vibrating for 3 times?

Thank you ;)
[Desire Android Development] John_Blaze:
It vibrated 3 times on splash?
[Desire Android Development] madmaxx82:
Yes when booting when you see the HTC logo..
[Desire Android Development] John_Blaze:
Im thinking you should atleast have simcard inserted.. ive never had my fone reboot from touching the trackball. Have you taken the battery out and tried to rebbot again?
[Desire Android Development] John_Blaze:
Thats weird.. mines never vibrated more then once on splash
[Desire Android Development] madmaxx82:
Yes didn't boot up anymore.. bootloop (orange boot animation was shown)

Now after selecting clear storage in bootloader I'm stuck at htc logo.. with 3 times vibrating when starting up.
[Desire Android Development] John_Blaze:
Does clear storage clear everything.. rom included maybe?
[Desire Android Development] John_Blaze:
Try this..

1. When the phone is off, press and hold the Home and Power button until the phone comes on.

2. You should see a little icon with an exclamation mark. Now press and hold the Home and Power button again.

3. You should see some instructions and some options. Use the trackball to select Factory reset. This will erase all your phone's data, but if you're in the cloud (ie your contacts are with Google), you should be fine, you'll just have to reconfigure everything (ie mail accounts, keyboard calibration, home screens, app downloads and preferences)

oops i mean this..

With the phone turned off, press and hold the VOLUME DOWN button, and then briefly press the POWER button.

Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button..

Press VOLUME DOWN to select CLEAR STORAGE, and then press POWER.

Press VOLUME UP to start the factory reset.

After clearing storage did you do a factory reset?
[Desire Android Development] madmaxx82:
I selected clear storage before.

When I do that it states the phone will reboot in 5 seconds..

Then I tried to enter recovery to do a factory reset, but couldn't get into it..

Will try again..

Now I get to see the orange logo for a short time when I boot up and then the phone resets itself.

I could unlock it with XTC Clip and flash another firmware, but I'm afraid that they won't take back the phone if it is truly dead.. so I'm hesitating doing that..

Edit: could enter recovery and did a factory reset.. reporting back..
[Desire Android Development] madmaxx82:
Yeah!! Booting again!

Thank you very much :)

Will try pressing thanks buttons now, but dunno if I'm over the limit already, if I am I will do that 24h later ;)
[Desire Android Development] John_Blaze:
Cool im glad you got it bud.. :) better get S-OFF now and stay away from the trackball.. hahaha no trackball shouldnt reboot your fone.. idk why it wouldve done that.. as for the 3 vibrates on splash.. ive had that happen either
[Desire Android Development] madmaxx82:
****!!!!

After setting up the phone for the first time, everything seemed to work.

I selected power off, but after it went off it booted again.

Now I see the HTC logo for about 4 seconds, then bootloops.

Can however enter bootloader..
[Desire Android Development] John_Blaze:
I dont know bud.. sounds as if you may have a defective fone. :( although i have had problems like that before occasionally. if you can get it booted back up again try leaving it on for awhile. Do you have Droid Explorer? You can enter recovery using it even if your in a bootloop. you can also go from booted rom straight to recovery.
[Desire Android Development] John_Blaze:
Hey Max.. you ever get that fone lined out?
[Desire Android Development] madmaxx82:
Hey bud, hours of wasted time :(

Now I can't even enter recovery.

It was difficult at first either.. needed a few tries and clear storage before I was able to get into it.. now it seems it won't work anymore..

All I can do is get into the bootloader.

I tried using the XTC Clip to get it s-off and flash a ruu, but no chance.. phone reboots..
[Desire Android Development] John_Blaze:
Wow thats jus wierd bud.. Id be sending that fone back! something really wrong with that. Or maybe give HTC a call and see what they say
[Desire Android Development] carlo0810:
hi max, currently using CWM 2.5.0.7, tried to falsh this recovery using the 2nd method where you flash with PB99IMG during the HBOOT screen, a blue bar shows up like its flashing, but when i get to recovery i still see CWM, any ideas?
[Desire Android Development] mattman83:
If you can get to bootloader then you should be able to flash RUU via PB99IMG method?
[Desire Android Development] madmaxx82:
Yes think so :( but still trying.

Did it say it successfully flashed?

If so, how do you enter recovery? If you want to enter recovery via rom manager you also need the fake flash update.zip!

Yes tried that, all partitions get updated BUT radio.. radio_v2 failed-pu...

GREAT!

Currently trying with RUUs.. but they also failed till now.

Now trying with the gingerbread ruu
[Desire Android Development] carlo0810:
thanks, i am currently on your recovery now, however when i tried to convert ext3 to ext4, it says cant mount ext4?
[Desire Android Development] madmaxx82:
What exactly did you do and when does it say what exactly?
[Desire Android Development] Droidzone:
Edit. Sorry wrong thread

Swyped with my HTC Desire on Supernova Extreme Rom - Gingerbread goodness with Unlimited Internal Memory!

Ignore the typos, swype isn't perfect.. ;)
[Desire Android Development] madmaxx82:
Haha unbelievable!

I could not flash any RUU successfully because of that radio_v2 flashing problem.

Got the famous 4 triangle screen then where you can't escape ;)

Tried at least 10 different ruus when I stumbled across 1-2 posts mentioning "put it into a freezer". Unbelievable.. but this worked and was even reproducible (tried tmo first which worked after freezing it for 5mins, and afterwards latest wwe which gave me the error again -> freezer -> same wwe -> worked)

However same problem as at the beginning: phone gets into a bootloop after you power it off for the first time and needs to be reset completely to get it to boot again, where it's even difficult to enter recovery.

Strange phone.. will return it back immediately.
[Desire Android Development] Sebby:
dit you try it with a goldcard (branded phones)

dit you use a RUU from orange

here is a link with a lot off RUU's including orange

http://shipped-roms.com/index.php?category=android&model=Bravo
[Desire Android Development] madmaxx82:
Hey friend, long no see!

Yes, otherwise I couldn't have flashed those ruus.

Now there is the WWE unbranded flashed, but the phone still has the same bug as before with the orange fw.. so I need to send it back :(
[Desire Android Development] Sebby:
oke i hope you get a good phone now

i was on vacation and looking for work
[Desire Android Development] Droidzone:
Sounds like hardware fault to me.. Send it back asap :)
[Desire Android Development] madmaxx82:
Yes I hope that too ;)

Good luck to you finding a good job!!

Great you were on vacation. Should do that too.. but no time and money at the moment :D

Yes :(

I'm lucky though that the seller seems to have great support..

Just angry that I put so much time into that.. should have returned it immediately.
[Desire Android Development] madmaxx82:
v2.1.3

UPDATED with additional sizing options for the partitioning menu​

v2.1.3 unsupported

Released: Aug/6

Fixed a bug that sometimes occured with 2.1.2 (unsupported) where Rom Manager couldn't run a backup.

New: Backups will now error and stop if there isn't enough available space on sdcard instead of just printing a warning message which could be overlooked easily.

This was the case with any previous 4EXT version and with CWMR at least until version 4.0.0.5 (haven't yet checked if this behaviour has changed in newer versions)​

Text output now doesn't cover the progressbar anymore as was the case in 2.1.2 (unsupported)

Download:

Desire GSM:

4EXTRecovery v2.1.3 recovery.img

md5sum: 17d5cb5c85f71cbb56ef9879e9ee01bb

4EXTRecovery v2.1.3 PB99IMG to flash via bootloader

md5sum: a598f1009b97930ab8467aecbc5b3d74

Desire CDMA:

4EXTRecovery v2.1.3 recovery.img

md5sum: 482add15bb5870eb25a00b3cf6ae3f39

Desire GSM & CDMA:

4EXTRecovery v2.1.3 update.zip (fake flash)

md5sum: 3230950eda8c2cae4624456f577308cb

​
[Desire Android Development] sibere:
4K alignment?

Hi !

I may have missed something but I read on the OP that this excellent recovery is aligning to 4K the partitions, right ?

If this is wrong, then pardon me and disregard the following.

To get the best of an SD, it has to be partitioned and aligned to a minimum of 256Kb. That is the SD "max erase block size" (SD standards). reading on a SD is not the main issue. Writing is.

On a flash memory device like SDs, writing is made by blocks. Each manufacturer can use a different block write block size, but the maximum is 256Kb. So the alignment has to be done to 256Kb (or any multiple like 512K or 1024K).

Secondly, the data has to be written to the beginning of the block, otherwise you can get a big performance drop by writing to extra blocks for nothing.

This is the reason why I recommended on my thread to align to 256Kb or 1Mb, optimise the FAT32 partition to write to the beginning of data blocks, and use stripe, stride and extents on EXT4 partitions for the same reason.

Aligning to 4K is useless.

By aligning to 1Mb and optimizing the FAT32 formatting , I almost doubled my writing speed... You should try it :)

Same reports of better performances for optimizing the EXT4 partition.

Read the relevant bits and comments on my Thread OP.

Hope this helps :)
[Desire Android Development] madmaxx82:
ALigning to 4k is not useless.. that's what you actually do when you create a partition that starts at 1024K.

If you partition using 4ext your first partition will start at 1024K and all the other ones will be aligned to that.

If you use any other alignment check script you will notice that.

stride and stripe width does not make sense if it's a single physical disk. This has the same effect as specifying a block size of 4k.

However since many of your scripts do that anyway, to make you happy, 4ext formats those partitions using:

-b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -E stride=64,stripe-width=64 -m 0
[Desire Android Development] John_Blaze:
Hahaha right! should have.. but we always like to think we can fix stuff. Yea id say you got a fualty fone bud. Mine has rebooted itself for no reason before but is always booted back up. How are you today bud?
[Desire Android Development] madmaxx82:
Hahaha yes. I even tried the xtc clip now and set it s-off to see if it changes anything. but of course not.

Fine thnx.. had a far too long night because of that crap and I'm way behind of so much work I need to get done.. but otherwise everything is ok.

How are you?
[Desire Android Development] John_Blaze:
Not to bad.. I just tried to fake flash recovery through Rom Manager and all it says is Downloaded succesfully. I replace the files that were already there with 4ext.. renamed them to exactly what was there.. idk.. its no big deal.. jus wanted to see if i could do it
[Desire Android Development] madmaxx82:
That's good ;)

What did you do after replacing the files?

You need then to install recovery (where it usually installs cwmr) through rom manager (first option)
[Desire Android Development] John_Blaze:
There was only two places where i seen that needed replaced. Thats what i did.. 1st option.. it just says successfully downloaded clockwork recovery and thats it.. doesnt flash
[Desire Android Development] madmaxx82:
Strange but maybe it worked..

Did you also replace update.zip on the root of your /sdcard ?

This might not be necessary.. I need a device to test that that uses rom manager with fake flash only to find that out :D
[Desire Android Development] angusc:
Mad max

What exactly is wrong with your desire? I can't believe it is defective straight out the box.....

Have you managed root and s-off?

Sent with Desire
[Desire Android Development] John_Blaze:
Ok forgot about that one.. I jus deleted it from root of sdcard and replace it but when i tried to open rom manager its totally gone from my fone and i had to reinstall it.. weird eh? Oh well its no big deal.. i hardly ever used rom manager for flashing anyways
[Desire Android Development] madmaxx82:
It was a used one..

After booting for the first time with original firmware and then selecting "power off" it reset instead of powered off and went into a bootloop..

Only entering recovery and doing a factory reset got it to boot up again.. for exactly one time, after which this process repeated itself.

I didn't want to S-OFF before I made sure it was ok.

So I created a goldcard and tried to flash RUUs.. which resulted in radio_v2 errors.. even more fun :D

Then I got it flashed by the freezer method.

Now it had latest official wwe RRU and still the same symptoms.

Then I set it s-off by using an xtc clip, but of course didn't change anything..

Edit: there seems to be a problem with the radio..

The xtc clip needs a working radio to work. When trying to activate the radio when the rom was in a condition where it boot looped (only resolvable by factory reset) it just rebooted when the clip tried to power on the radio.

After factory reset, the clip was able to unlock the device.

So with the original installed rom which was still eclair and with the new wwe ruu, it's exactly the same :(
[Desire Android Development] madmaxx82:
Did you try rebooting into recovery by using rom manager? maybe you got it installed..
[Desire Android Development] Sephi:
Any chance I can use that without s-off? I'm stuck in the recovery menu!
[Desire Android Development] madmaxx82:
Yes you need to use the fake flash update.zip
[Desire Android Development] angusc:
Sorry I might be a bit slow......I'm drinking. Have you flashed a custom rom yet? Have you got sdcard partitioned with ext and fat 32....i recommend you use 4ext..... :p

Or are you still on the orange rom

There is a way to get root via terminal emulator.

Sent with Desire
[Desire Android Development] madmaxx82:
hehe :)

No, the device doesn't work even with stock roms ;)
[Desire Android Development] Bibracte:
Hello,

1) With v2.1.3, you have removed the choice of partition size (1536/341) ?

2) With v2.1.2, I noticed that if one starts the partitioning process but we put zero (choice SKIP) to the size of each partition, then you can not create them because we have a message "insufficient space". I had to take Gparted to make space on my FAT32 partitions and recreate EXT3/4 with 4EXTRecovery

It might be necessary that the place is free rather than reassign to FAT32.

:)
[Desire Android Development] madmaxx82:
Hi,

****, totally missed that.

Currently recompiling with the "lost" sizes.

I don't completely understand the other issue though..

Did you select "start from scratch" or "save fat32 partition"?

Edit: 4ext doesn't support shrinking of the fat32 partition yet.. you must make sure there is enough space available to create or change additional ext4/ext3 partitions when you chose to not "start from scratch"
[Desire Android Development] madmaxx82:
Re-uploaded with the missing size options.

In the next version you will be able to select your own sizes! But this will take more than 7-14 days to get finished.
[Desire Android Development] Droidzone:
Hey madmaxx82, is there a default for 4ext.conf which gives the same options that Sibere recommends? I see block size option here already..
[Desire Android Development] madmaxx82:
This option is not parsed at the moment ;)

But 4ext uses the same stripe-width and stride options as Sibere recommends.

Anyway, this is really not necessary as we are not on a raid here.

From ext4.wiki.kernel.org:

s_raid_stride	RAID stride. This is the number of logical blocks read from or written to the disk before moving to the next disk.
This affects the placement of filesystem metadata,
which will hopefully make RAID storage faster.

s_raid_stripe_width	RAID stripe width. This is the number of logical blocks read from or written to the disk before coming back to the current disk.
This is used by the block allocator to try to reduce the number of
read-modify-write operations in a RAID5/6.

From the ext4 man page:

stride=stride-size
Configure the filesystem for a RAID array with stride-size filesystem blocks. This is the number of blocks read or written to disk before moving to the next disk, which is sometimes referred to as the chunk size. This mostly affects placement of filesystem metadata like bitmaps at
mke2fs time to avoid placing them on a single disk, which can hurt performance. It may also be used by the block allocator.

stripe-width=stripe-width
Configure the filesystem for a RAID array with stripe-width filesystem blocks per stripe. This is typically stride-size * N, where N is the number of data-bearing disks in the RAID (e.g. for RAID 5 there is one parity disk, so N will be the number of disks in the array minus 1).
This allows the block allocator to prevent read-modify-write of the parity in a RAID stripe if possible when the data is written.
[Desire Android Development] Bibracte:
I selected "save fat32 partition". I wanted to do a test to delete all partitions EXT/swap, but without changing the FAT32.

Thank you for your great work ;-)
[Desire Android Development] madmaxx82:
Thnx!

I see.. if you leave fat32 as is and select skip for all other partitions, then I think it will leave everything as is.. haven't tried that ;)

Next version will be completely different in this regard, promised :)
[Desire Android Development] madmaxx82:
BTW: I will enable that config property in the next release or the one after that ;)

Would be nice for everyone to use the options he/she would think are best.

Although messing around with it by someone who doesn't know what he does could break the whole recovery (backup/restore).

So it's dangerous :D
[Desire Android Development] Sebby:
madmax

what do mean by this

Text output now doesn't cover the progressbar anymore as was the case in 2.1.2
[Desire Android Development] sibere:
Starting a partition @ 1024k sounds like 1024K alignment to me ;)

Sorry but this is wrong.

It is making sense on an EXT4 filesystem because of the extent feature.

From my thread OP

stride and stripe-width are RAID options but they are used here to align the filesystem to the max erase block size of an SD card. In conjunction with EXT4 extents feature (not present in ext3), it gives a bit of extra performance thanks to block allocation. It's used and recommended for SSDs, so it should help our poor little cheap (SSDs) SD cards
I use 64 because 64x4 (4kb block size)=256Kb. 256Kb is the max erase block size per the SD standards.
Your card may have a smaller erase block size but 256K is at least compatible with every card.
If you want to change the block allocation size, change the "64" parameter.
Just change it to - say - 32 (32x4=128kb) etc ...

I read a lot of documentation on EXT4 and SSDs before adding those options.

strip and stride "drive" the extent to write data at the beginning of physical memory blocks if the partition is well aligned.

From EXT4 official documentation:

stripe=n	Number of filesystem blocks that mballoc will try
to use for allocation size and alignment.

Thanks but I don't need to be happy myself, I just wanna make users happy with the best performance they can get out of their SD card :)
[Desire Android Development] drbobb:
For me 2.1.3 just hangs on the initial screen and never displays a menu. Booted from fastboot.

EDIT this may be due to my having applied Firerat's custom MTD patch. I'll look into this further when I have more time.