yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] azure89:
Mini-guide for splash1 fix and recovery freeze

Ok, finally i've got it flashed to my Desire!

Here's what I did, i hope it would be useful to someone who have issue with flashing this rom.

1. I did my partitions using Gparted and Linux Shell (fat32+btrfs+swap)

2. **I didn't flashed the alignment zip cause the log says that my partition was already aligned** / I guess you could safely flash it, it should work as long as you follow the 3rd step =)

3. Flash ROM, be careful when it's done don't press anything (if i press the Back button on my phone, my recovery hangs and it seems that my partitions are empty.

To prevent this just type "adb reboot" and you will be rebooted to recovery again.

4. Now just reboot to phone and everything should be fine! =)

Well, if someone will be interested i'll trying to make some benchmarks with btrfs when i have time
[Desire Android Development] koenvbeek:
Ah, I already thought I was the only one that was experiencing this. I'm gonna try that, see if it works when I don't give recovery the chance to freeze :p
[Desire Android Development] azure89:
I'm pretty sure that the 3rd step of my mini-guide, it's a workaround for that problem. =)

Let me know if it works for you!
[Desire Android Development] koenvbeek:
I did the following:

- Partiton sd in Gparted (all primary partitions, all aligned to Mib):

1: fat32

2: ext3

3: swap

- Full wipe in recovery

- flash alignment zip for reiserfs

- flash rom

- instead of going to main menu after flashing, use "adb reboot" to not letting recovery freeze.

- once recovery rebooted, select "reboot system now" in recovery

- waiting... It never gets past the splash screen, and 'adb logcat" gives this error:

"link_image[1995]: failed to link /system/bin/sh"

Now i'm trying to partiton sd with reiserfs and then skip flashing the alignment zip.

EDIT: formatting the 2nd partition as resierfs and skipping the alignment zip doens't work either.

What should I do?
[Desire Android Development] thebazman:
hi

how long should the screen stay at "install from sdcard complete" in recovery?

regards

now on white screen with htc logo and a blue led for 10 mins is this normal?

its now 30 mins lol
[Desire Android Development] Lanbase:
Listen its not so hard,

If you use gparted with align to mib for any partion than its not nexesary to flash the align zips.

You can just straigt flash 0.6 or 0.7 them.

Btw melhrtron cam i use the align zips in any rom?

Edit ; leave the phone alone for as long as it doesnt start flirting with you during flashing.... patience maby 10 minutes

Edit 2 i think adb reboot during or right after flashimg is also a bad idea...... be sure batery is full enough.... dont toutch !!!

Edit 3 still problems? Mabey try recovery 2.5.0.7
[Desire Android Development] azure89:
By the way, i think it's pretty pointless to flash align zip of the same type of file system (ex: i already formatted to ReiserFS and i flash the ReiserFS one, of course you should use GParted and align to MiB).

Try to setup directly via GParted your SD and flash directly the ROM (remember always to full wipe etc.)

@thebazman: Uhm, I guess you can safely reboot after "Install from SDCard Complete", so no need to wait. If your recovery freezes, try to wipe - reflash rom - reboot to recovery via adb (adb reboot recovery) - then reboot.

Three hours here with my BTRFS as sd-ext, the ROM overall it's pretty fast and with btrfs it's pointless to flash life-on-the-edge (a little-nothing speed up).

Quadrant makes 2100+ without overclock (even if it's not trustworthy) and TAP Benchmark 3000+, so i'm pretty satisfied with this ROM, probably with ReiserFS and other filesystem it would be even better, but i'm want badly to try BTRFS =)

Notes: Wow, the ROM it's full customizable! (you can setup I/O Scheduler, cpu frequency, undervolting etc.)

I'm playing a bit with CPU and I/O Scheduler and I'm going to try a quick Quadrant + TAP.

---------------------

I/O Scheduler = VR

CPU = 245000 / 1194000

Quadrant = 2461 (6345/1145/4099/312/402)

TAP = 3149

---------------------

I'm staying with this setup atm. I'm pretty impressed since this is an HD Rom, really good job =)

@Lanbase: Yes, generally is a bad idea. But if your phone freezes after flashing the ROM, you have no choice but...

1. Drop Battery

2. ADB Reboot

3. Any other thing that allow you to power off
[Desire Android Development] koenvbeek:
So I haven't waited long enough then. I will leave it on during first boot while i'm going to sleep then :)
[Desire Android Development] thebazman:
i did the adb reboot and it didnt hang just waiting for it to boot now

still waiting its at the white screen htc logo
[Desire Android Development] thebazman:
sorry about double post

trying to install .7 which doesnt seem to be wanting to boot , so i wipe everything and try to flash another rom which gets to;

E:cant mount /dev/block/mmcb1k0p2

(file exists)

E:cant mount SDEXT

E:failure at line 8

copy_dir package:data SDEXT

installation aborted

any help appreciated

regards
[Desire Android Development] koenvbeek:
I've had that problem as well.

At first I tried using the following command (it's for repairing the card reader in the phone if it gets 'bricked'): "fastboot oem enableqxdm 0"

That didn't solve the problem for me, so I just repartitioned my sd (it was my test-cd card anyway) and then it worked again.

Question for the experts: I've flashed 0.7 1.5 hours ago, and it still shows the splash screen. Is this normal for this rom?
[Desire Android Development] MATRIKS:
Flash align.zip
[Desire Android Development] thebazman:
i flashed that before i flashed the rom

regards

can you install a rom thru adb commands?

if so could anyone give me them cheers

ive just f*cked up as i didnt back up my rom before i tryed to flash this rom (yes im a ****wit)

so ive nothing on my sdcard as i partitioned it (I FIXED MY STUPIDNESS)

any help lol
[Desire Android Development] koenvbeek:
If you want a working phone no matter what it takes, you can always flash an RUU, it will then even run without an sd...

But I would put the sd in my pc using a cardreader and put a rom on it to flash.
[Desire Android Development] thebazman:
cheers for replying but i sorted it m8, i just mounted storage thru recovery and put rom on card then "het presto"

i'll be honest for 5 minutes there i thought i had made a major booboo

but im still not on this v.7 i was on .5 which was good

regards
[Desire Android Development] koenvbeek:
You're welcome.

@ the experts: 2,5 hours after flashing, it's still at the splash screen.
[Desire Android Development] thebazman:
i think @2.5 hours it wont be booting, after 35 mins i pulled the battery.

do you get the blue led where its usually green or orange when on spalsh screen?
[Desire Android Development] koenvbeek:
Nope, It doesn´t even get to the boot animation. But it reacts at adb calls, so it´s not frozen.

Can you give me an EXACT guide to get it to work? I've tried it several times, but haven't succeeded once...:(

Thanks in advance...
[Desire Android Development] thebazman:
mine rebooted into the white screen thats says htc and the led is blue its the first time i had seen that colour as it was always green or orange

regards

sorry m8 i couldnt boot it either but i want to . going to have to wait til later on today for mele and co
[Desire Android Development] koenvbeek:
Hmm, did you have the charger/pc connected? I did. Maybe that blocks the blue led at mine.

I've seen the blue led before, using the app "LED me know", which is made for the Desire.

Let's wait for the hero of the day, who's gonna help us :p
[Desire Android Development] thebazman:
yes i had charger in and the led was blue only after i came out of recovery

yes we are waiting and they are out partying selfish gits:p
[Desire Android Development] koenvbeek:
rofld...

You made me spitting coffee over my keyboard!! :D:D:D
[Desire Android Development] martino2k6:
@melethron

Could you please shed a bit of light on my attached logcat? Those JavaBinder errors keep appearing very regularly at times, like every minute or two...

Thanks.
[Desire Android Development] thay:
This problem is commonly with v7 i had it with 2 devices for me this rev won't work.To resolve and install another version of rom pull sd - recovery -wipe all- delete partitions and create new layout with gparted-copy new rom to sd and flash it
[Desire Android Development] thebazman:
cheers for replying

i already done that but without gparted.

seems strange the blue led being there or is that a feature:p
[Desire Android Development] skullz:
0.7 not working for me either, after installation it goes to a screen that says 'android' and it just sits there until I have to pull the batt..

Have tried re-installing/full wipe/repartition ext3,ext4,reiserfs but to no avail :(
[Desire Android Development] 160bpm:
Hi all,

Did de flash of 0.6 because 0.7 reboots every time...

With 0.6 i get the white screen and HTC in green...

Volume is working... home i can press...

How can is solve this..

Did recovery and reboot by ADB.... and partitions are ok as i got form Matriks

EDIT: NOW i see the setup but responding very slow........
[Desire Android Development] koenvbeek:
It's a feature, see the changelog for 0.7.
[Desire Android Development] thebazman:
So it is , even though i did check it when the .7 went live , i missed that.

regards
[Desire Android Development] 160bpm:
Now try it on my 8GB Sandisk card... everything same...

1) fat32: , Ext2:, Swap

2) flash rom

3) adb reboot

4) not again white screen with HTC logo...

I don't understand how i can solve this...
[Desire Android Development] howdid:
using your rom for 2 days now, everything is fine : ) thx 4 your hard work!
[Desire Android Development] koenvbeek:
I've got the same problem. I've tried both 0.6 and 0.7 with ext3/ext4/btrfs/reiserfs. It never gets past the splash screen. When I do "adb logcat" I always get this error:

link_image[1995]: failed to link /system/bin/sh

CANNOT LINK EXECUTABLE

What am I doing wrong??

EDIT: Problems solved!!! I've been using the Sense HBOOT all the time... I Agree, that is a stupid mistake. Thanks for the help though.
[Desire Android Development] louis47:
Process com.android.phone unexpectely stopped

Ik have try 0.7 over 0.6 but I get Process com.android.phone unexpectely stopped

I have recovery 3.0.0.5

16 GB sd class6

1,9 GB ext4

Swap 6 MB ( without swap the same results)

Rest Fat32

I try 0.7 clean install then still rebooting.....
[Desire Android Development] melethron:
@all:

sorry i didn't have much time these days. For all those with issues getting the ROM to work. Please make sure you use the default h-boot partition table (as stated in the op - thats the

Bravo Stock 1.8	parttable).

Also can someone who has issues with 0.7 (but 0.6 working fine) post me a logcat of the boot.

I/O errors could be a corruption on sd-card (which should be fixed on reboot). Please check the Avaritia-log for that.

If you have an errorfree log then it might also be issues with deadline scheduler on your sd-card. Try cfq then.
[Desire Android Development] Aegishua:
Great ROM but not to my likings unfortunately =( However, I was just wondering if i could request a copy of the blue battery mod in the notifications bar since it looks pretty darn awesome.
[Desire Android Development] melethron:
on:

echo 1 > /sys/devices/platform/leds-microp/leds/blue/brightness

off

echo 0 > /sys/devices/platform/leds-microp/leds/blue/brightness

Edit: For other colors use "amber"/"green" instead of "blue".
[Desire Android Development] melethron:
Ownhere's 720p recording fix for Avaritia v0.7 as flashable zip:

http://files.c0urier.net/melethron/Avaritia_HD/Mods/720p-fix.zip
[Desire Android Development] koenvbeek:
Should we flash the 720p fix right after flashing the rom, or after first boot?
[Desire Android Development] melethron:
Doesnt matter.
[Desire Android Development] MATRIKS:
Melethron any plans?

BTW ROM v0.7 work smoothest with JFS part.
[Desire Android Development] melethron:
Im not working on the ROM atm. Don't have much time. But im quite happy with v0.7 atm.
[Desire Android Development] Chaqmol:
can anyone post a benchmark score?(v0.7)
[Desire Android Development] 160bpm:
and what did you have done so it was working... How can you see you using sense hboot?
[Desire Android Development] koenvbeek:
If you hold Power + vol down, you start HBOOT. If you are S-OFF, the top line is '--- AlphaRev ---' in purple. That's because the HBOOT is replaced by the S-OFF procedure, by a customized HBOOT which doesn't check the security (so S-OFF)

If you've got the Sense partition layout, which is NOT default, 'Sense' is shown after '--- AlphaRev ---'. Have a look at http://alpharev.nl.

So if you already have S-OFF, your HBOOT is replaced by a customized one with default partitioning.

To flash another HBOOT:

- make a nandroid backup via recovery

- start phone in fastboot-mode (select in HBOOT using vol. keys and power button)

- download your new HBOOT img from http://alpharev.nl

- check the MD5

- Run the following command: "fastboot flash hboot <img file here>"

- restore your nandroid backup

Please note that Avaritia only works with the stock partition layout. SO if you've never flashed another HBOOT, you will have the default one most likely.
[Desire Android Development] thebazman:
ive never flashed a hboot and i cant boot this, how long does it stay on the whitescreen with htc logo?

regards
[Desire Android Development] koenvbeek:
First: If you never flashed a different HBOOT, your problem is different than mine was. Do you see your blue LED during boot?

When I solved my problem, first boot took around 5 mins, mostly while the boot animation was playing. It was about 1-2 mins at the splash screen.
[Desire Android Development] thebazman:
when i reboot i get the blue led and white htc screen then nothing, no animation

regards

when partitioning sdcard in recovery what ext is used?
[Desire Android Development] koenvbeek:
If the blue LED comes up, that means that the install script has started.

You should be alble to do "adb logcat" and then you can see what your phone is doing. If I'm correct adb is already worikng on the phone when the install script is working.

EDIT: For partitioning: ext3 is the most reliable choice...
[Desire Android Development] thebazman:
what i meant was when i partition in recovery it doesnt say what ext it is , was asking if you or anyone could tell me

will probably give it another try after my dinner

regards
[Desire Android Development] martino2k6:
Thanks. The errors seem to have disappeared at some point, but don't remember whether I rebooted or not in the meantime.
[Desire Android Development] thebazman:
the reason this isnt booting for me is because im partitioning my sdcard thru clockwork recovery which according to logcat is ext 2 and ive been using ext4 alignment then tried ext3 alignment.

iv been trying to find out what ext clockwork recovery uses(knows now) so been doing trial an error

so looks like im gonna hav to do the ext thru gparted cause cant see ext2 alignment

regards

checked in gparted and i did hav ext3 hmm
[Desire Android Development] Saenic:
Will it work if I partition my SDCard with AmonRA Recovery 2.0.1 ? 8GB Class 8 -> 512MB Swap + 1024MB Ext4 + Fat32 Rest

I don't want to use Clockwork Mod or gparted
[Desire Android Development] 160bpm:
Thanks. I will try it when i have time... :)
[Desire Android Development] thebazman:
well thats me partitioned in gparted ext 3 lets see if i can get this to work

just about to reboot it

wawee got animation looks like this is a goer

thats me running .7 now, looks like gparted was the difference

regards
[Desire Android Development] koenvbeek:
Filesystem Benchmarks

I've done some benchmarking with rom 0.7 as a clean install - nothing was modified apart from the filesystem of the sd-ext partition. I've switched between the filesystems by making a nandroid, flashing an alignmen zip and restoring the sd-ext backup.

In the attached image you see 3 runs per filesystem. The green scores are the best for that particular filesystem, the blue is the overall best score. I'm going to install a new daily rom using btrfs!

For the testing I used a SanDisk 4GB Class 6 card.
[Desire Android Development] thebazman:
what sdcard you using?
[Desire Android Development] koenvbeek:
For the testing I used a SanDisk 4GB Class 6 card.
[Desire Android Development] louis47:
I still do all of this, I did go accidentely to sense and then back to stock but now I stay in bootscreen after a restore. What shall I do?

Edit: Solved! I wiped everything. And restored again, I'm back .
[Desire Android Development] melethron:
Yes it should work fine.

Strange. Wonder what caused your issues with the zip file .....

Please note that Benchmarks arent actually a meassurement for the "feeling". Ext4 is rather slow but still "feels" good. The reason is that ext4 uses "delayed allocation". Writes are delayed and thus take longer. But it still "feels" nice because in some situations you dont need to wait till the write is done.
[Desire Android Development] melethron:
Yep. adbd service is started before "init.d". Its in ramdisk:

on property:persist.service.adb.enable=1
start adbd

Also the "property:persist.service.adb.enable" is set as for all rooted roms.
[Desire Android Development] koenvbeek:
Ah... thanks for the info!
[Desire Android Development] martino2k6:
I'm using ClockwordModRecovery 3.0.0.5 and my sd-ext is formatted to ext3. When I backup, it doesn't backup the sd-ext partition. I only see android_secure, boot, cache, data, recovery and system img files. Anyone else have the save problem? I wanted to change to ext4, but I guess I'll have to hang on for a while...
[Desire Android Development] melethron:
I think that ext2/3 support was removed in CMR 3.0.0.0. But it should have been added back in 3.0.0.5.

I recommend using an older version of CMR. 3.0.0.5 has no advantages over 2.5.1.8 on the desire (im quoting IEF on this). All it does is causing issues. Removing ext2/3 support wasnt necessary, removing amend support wasn't necessary, changing the way sd-ext is backed up wasn't necessary (it packs a yaffs image on 2xxx version which is a fine way to backup ...)....
[Desire Android Development] 160bpm:
I'm crying....

Hboot: done... now AlphaRev Hboot

SDcard: fat32, ext2, swap

Rom: Avaritia 0.6

Get a white screen with HTC and then a popup that some system proces stops... force close or wait..

Avaritia 0.7 is also not working... white screen with HTC...

Now i did everything but think i go back to RCMix Rom.. :( TO BAD FOR ME

After 10 - 15min i had the setup screen... but it takes long time when i see the second setup screen (now again white screen with HTC)

EDIT: Playing with the trackball and now i goto the whole setup hopefull when done and reboot i do not get the whitescreen with HTC again... i'll going to hate that screen :)

EDIT 2: Setup is done... Everything was slow.. but after a while it is fast.. Hope the rom is working great... Will reboot now, and do an titanium restore...
[Desire Android Development] Saenic:
It didn't. Got the same "no such file or directory" spam like ciario got

http://xdaforums.com/showpost.php?p=10763420&postcount=788
[Desire Android Development] martino2k6:
You were correct. Downgrading solved the problem. I flashed your recovery, backed up sd-ext, flashed btrfs align zip, restored, and hurray!

I must say that btrfs feels much faster than ext3. Now will just have to see whether its development status will not bite me back into my ass :)
[Desire Android Development] styr:
It seems that i have a problem with the market with 0.7, it FC`s every time, i wiped and reinstalled the rom like 3 times. I`ve attached a logcat if anyone could take a look and help.

E/DatabaseUtils( 761): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=1604, uid=10050 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS

E/DatabaseUtils( 761):	at android.content.ContentProvider$Transport.enforceWritePermission(ContentProvider.java:331)

E/DatabaseUtils( 761):	at android.content.ContentProvider$Transport.insert(ContentProvider.java:179)

E/DatabaseUtils( 761):	at android.content.ContentProviderNative.onTransact(ContentProviderNative.java:175)

E/DatabaseUtils( 761):	at android.os.Binder.execTransact(Binder.java:288)

E/DatabaseUtils( 761):	at dalvik.system.NativeStart.run(Native Method)

W/dalvikvm( 1604): threadid=8: thread exiting with uncaught exception (group=0x40025aa0)

E/AndroidRuntime( 1604): FATAL EXCEPTION: Thread-12

E/AndroidRuntime( 1604): java.lang.SecurityException: Permission Denial: writing com.google.android.gsf.settings.GoogleSettingsProvider uri content://com.google.settings/partner from pid=1604, uid=10050 requires com.google.android.providers.settings.permission.WRITE_GSETTINGS

E/AndroidRuntime( 1604):	at android.os.Parcel.readException(Parcel.java:1247)

E/AndroidRuntime( 1604):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:160)

E/AndroidRuntime( 1604):	at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:114)

E/AndroidRuntime( 1604):	at android.content.ContentProviderProxy.insert(ContentProviderNative.java:450)

E/AndroidRuntime( 1604):	at android.content.ContentResolver.insert(ContentResolver.java:587)

E/AndroidRuntime( 1604):	at com.google.android.gsf.GoogleSettingsContract$NameValueTable.putString(GoogleSettingsContract.java:55)

E/AndroidRuntime( 1604):	at com.google.android.gsf.GoogleSettingsContract$Partner.putString(GoogleSettingsContract.java:126)

E/AndroidRuntime( 1604):	at com.android.vending.compat.MarketCheckinHelper.updateCheckinDatabase(MarketCheckinHelper.java:12)

E/AndroidRuntime( 1604):	at com.android.vending.CheckinUpdater.sendContentSyncViaCheckin(CheckinUpdater.java:219)

E/AndroidRuntime( 1604):	at com.android.vending.CheckinUpdater.performCheckin(CheckinUpdater.java:176)

E/AndroidRuntime( 1604):	at com.android.vending.CheckinUpdater.access$000(CheckinUpdater.java:38)

E/AndroidRuntime( 1604):	at com.android.vending.CheckinUpdater$1.run(CheckinUpdater.java:109)

E/AndroidRuntime( 1604):	at com.android.vending.util.WorkService$1.run(WorkService.java:37)

W/ActivityManager( 517): Force finishing activity com.android.vending/.AssetBrowserActivity

W/DropBoxManagerService( 517): Dropping: system_app_crash (1476 > 0 bytes)

D/Sensors ( 517): close_akm, fd=111
[Desire Android Development] melethron:
This hasn't to be recovery related problem. Could you post a logcat of the boot....

:/ .... no idea what causes this.... Did you make sd-ext larger than 2 GB or made it a logical partition?
[Desire Android Development] styr:
Nope, 1.4GB ext3 primary partition. I've managed to get rid of the errors with an older version of Vending.apk, hopefully it won't crash again after it updates itself.
[Desire Android Development] louis47:
Not be able to install 0.7 properly

If I try to install 0.7 as clean install he still rebooting again and again.

If I try to install 0.7 over 0.6 he started but with the errormessage

proces com.android.phone stopped unexpectely. and reboot.....

I have Desire with sdcard

16 GB class 6

2048 MB ext3

and rest fat32.

I'm S-OFF

See Avaritia.log I don't what is 0.7 or 0.6

Maybe offtopic but I even don't have bluetooth, desire will not connecting to PC.

And when I put desire on powercable he started loading after 3 or 4 minuts.

In format boot menu no problems with connecting PC or powerloading.

That's with every Rom, and I think it happens after making S-Off.