yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] dpanter:
Tried again, hangs forever at white background HTC logo.

What can I do to find out what the f*ck is going wrong? Where can I find error messages and such?

Recovery.log seems useless...

Starting recovery on Sun Jan 6 00:51:42 1980
framebuffer: fd 3 (480 x 800)

Welcome to 4EXT Recovery Touch

by madmaxx82

Preparing boot.. 0I:start load volumes..
Preparing boot.. 0 Preparing boot.. 0I:st.f_bsize: 4096
Preparing boot.. 0 Preparing boot.. 0 Preparing boot.. 1 Preparing boot.. 1I:st.f_bsize: 4096
Preparing boot.. 1recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data ext4 /dev/block/mmcblk0p3 (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system ext4 /dev/block/mmcblk0p2 (null)

I:end load volumes..
I:Completed outputting fstab.
I:Processing arguments.
Preparing boot.. 1I:Checking arguments.
Command: "/sbin/recovery"

ro.build.date=Thu Nov 29 23:03:06 CET 2012
ro.build.date.utc=0
ro.product.model=HTC Desire
ro.product.brand=htc_wwe
ro.product.name=htc_bravo
ro.product.device=bravo
ro.product.board=bravo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.board.platform=qsd8k
ro.build.product=bravo
ro.com.android.dateformat=MM-dd-yyyy
net.bt.name=Android
ro.serialno=HT03TPL06742
ro.baseband=5.11.05.27
ro.carrier=HTC-Nor
ro.bootloader=6.93.1002
init.svc.recovery=running
init.svc.adbd=running
ext.version="1005.9.0"
ext.feature.version_check=yes
ext.build=40
ext.edition=ng

I:preparing..
Preparing boot.. 1I:prep sys1: 0
Preparing boot.. 2I:preparing.. fin
Preparing boot.. 2 Configuring settings..

I:Not using tz from prop
Your configuration settings:

Using button backlights level: 60
Restore: MD5Sum checks: enabled
Backups: generate MD5Sums: enabled
Backups: mode: tar
Backups: exclude /cache: disabled
Backups: exclude dalvik-cache: disabled
Preserve theme: enabled
Hide useless directories: disabled
Haptic feedback: enabled
Haptic feedback strength: 28
Using 24h-hour time format

I:theme propok
Recovery is ready..

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
The recovery hasn't been configured!

Use 4EXT Recovery Control or the free app
4EXT Recovery Updater, which is available
on www.4ext.net to setup the recovery
and to unlock configurable features.

Hint: check out recovery settings ;)
[Desire Android Development] spezi77:
You should copy the recovery.log right after flashing the ROM, so that we can see whether any installation errors have occurred.

Other than that please take a logcat at boot time. The command is: adb logcat. Please search on xda for hints on how to use this.

Gesendet von meinem Nexus 4 mit Hilfe von XDA Forums
[Desire Android Development] Codename13:
Hi [MENTION=5091819]spezi77[/MENTION], I have a few questions about your work. Do you use PMEM or ION or a hybrid in the kernel for this ROM? Which Adreno libraries/drivers do you use? Is SELinux set as enforcing, permissive, or disabled in this ROM (and do you have SELinux policies written for your device)? I'm asking these questions because I have a device that runs on the msm7x27a chipset, which also uses an Adreno 2xx series GPU, and it is sorta stuck in the past (uses PMEM, 3.0 kernel, legacy display and media drivers). I was able to boot Lollipop on my device awhile back (using the legacy drivers with some hacks in the code that I had to do for compatibility) but I gave up because it was buggy as hell. Now that I've found someone else who seems to be using legacy drivers and code to boot Lollipop for their device, I'd be interested in trying again for my device and diffing some changes from your sources to potentially fix bugs on my device. I don't know much about actual coding (I'm more of a "copy and paste, guess and test, try again" type of person), so I would appreciate if you could take the time to help me out a bit here.
[Desire Android Development] spezi77:
Hey there [MENTION=4702565]Codename13[/MENTION],

I just saw your message and looked up the information for you.

PMEM is only in use by camera, everything else is ION based. However, I couldn't bring camera to work in this rom. Camera works only in the later codebase with 5.1.1/CM12.1 for legacy devices.

I use the Jelly Bean version of Adreno blobs from the Nexus 4 (mako_jb_mr1; Build Date: 04/11/13 Thu; see here).

SELinux is set as permissive. If you have it disabled, the rom will get into bootloops. I believe that this is the key to solve your problem (fingers-crossed).

You don't need to write your own device specific SELinux policies. In AOSPA they use sepolicy from CyanogenMod. And I did only a few small alignments (see here).

I hope that this was helpful in any way..

Best of luck! ;)
[Desire Android Development] Codename13:
Wait, why would the ROM bootloop if SELinux is disabled? I thought it only bootloops if it's set as enforcing? So I'll use the CyanogenMod sepolicies. Great thank you!

I was attempting to build OmniROM up until a few days ago and comparing it to CyanogenMod code, I saw that OmniROM's code looks sort of borked for legacy devices compared to the CM12 code, so I've synced CM12 code and it's building much more smoothly. Once I get past the libwebviewchromium.so "file format unrecognized" build errors (apparently caused by memory issues because it takes a lot of memory to build Chromium libraries), I'm pretty confident that I'll get a nice build of CM12 pumped out. I'll test it out, see if I can get it booting. I guess I'm going into No Man's Land, because I don't think there are any other developers who have built Lollipop using PMEM only (and no ION) AFAIK. But like I said, I've done it before (that is to say, I've gotten Lollipop to boot using PMEM only) and I can do it again, better even. Thanks for the help :)
[Desire Android Development] spezi77:
You are welcome!

I never used enforcing, and I can only speak for this ROM. I started with a kernel in which selinux was disabled, and it caused bootloops.

Another thing you should take into consideration is moving to another filesystem, e.g. ext4 and install the system partition to the SD card (sd-ext). This should fix issues with filesystem permissions in selinux.

Have fun with Android, and keep me posted.. :)
[Desire Android Development] thinhx2:
Spezi77 now building cm13 for bravo,waiting
[Desire Android Development] spezi77:
Ah, you found it on my github. ;) it is still WIP..
[Desire Android Development] thinhx2:
Booted?
[Desire Android Development] spezi77:
Yes, CM-13 is booting, but a few things are not working, yet.

You are building for Nokia Normandy, is this correct? Which ROM do you want to make? SlimRom?

You have to align the make files in your device tree. Here is an example for SlimLP: https://github.com/spezi77/android_device_htc_bravo/commit/aa339185c4cfeecbdf8eb77f79c67027a94029c3

I would suggest that you read this guide: http://xdaforums.com/chef-central/android/tutorial-compile-lollipop-ubuntu-t2929410

Best of luck!

;)
[Desire Android Development] thinhx2:
Very very thank bro

---------- Post added at 04:06 PM ---------- Previous post was at 04:05 PM ----------

Yes i building slimlp and omni for nokia normandy. Cm13 booting and go to home screen?
[Desire Android Development] FaserF:
WOW :o really? Cant wait :) Happy to see such a great dev supporting our device.
[Desire Android Development] thinhx2:
bro build complete cm12.1? can upload
[Desire Android Development] spezi77:
Sorry, I don't understand your question.
[Desire Android Development] thinhx2:
bro can build cm12.1? or now bro build and testing cm13 for bravo?
[Desire Android Development] FaserF:
He is working on CM13 and not on CM12.1 at the moment, so I think he won't build it at the moment, as he is working on cm13.

I am so hyped about cm13 on the Desire :D
[Desire Android Development] thinhx2:
yes all friend have hope have cm13 for desire
[Desire Android Development] YaSsIN225:
thanks

thanks man you are great dev and i hope the best for you

------

note-- the rom is nice but is very slow

hav i nice day:good::good:;);)

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

شكرا لك كثيرا على هاته الروم المعدلة ولك كل الود والتحية ياطيب القلب
[Desire Android Development] spezi77:
Ha-ha, thanks man. You should also try my latest marshmallow rom for the htc desire.

All the best for you! ;)
[Desire Android Development] YaSsIN225:
Thank you very much

I'm just joking with you

Rom work well

Thank you very much and your team on these Beautiful costume rom

and I am a big fan of your works software

yassin from morocco ;):good::cool:
[Desire Android Development] kdotnon:
help, i have followed all instructions but when i install the rom it is stuck in "Magick by spezi77". waited for more than 3 hrs and same thing still. over and over again. there's this message on booting recovery which says the recovery isn't configured, might this have something to do with the problem earlier? im very sorry, i am a noob, please help.
[Desire Android Development] spezi77:
Share your recovery.log
[Desire Android Development] kdotnon:
This is the recovery log right after flashing the 4ext recovery for android 5. I tried with the rom again sir and it seems to be same as before. :(
[Desire Android Development] spezi77:
I cannot find any issues in your recovery.log. It just tells me that recovery got successfully installed.

wrote recovery partition from /tmp/recovery.img
# Recovery Installation Successful! #
script result was [1.000000]
######################################

Install from sdcard complete.

Please boot the new recovery and again share a recovery.log
[Desire Android Development] halo6534:
i got the "Encryption Unsuccessful" bug

i installed in the correct order and booted up normally

how to fix this
[Desire Android Development] gamerlucky:
i cant download http://fs1.d-h.st/download/00163/E5AK/PB99IMG_Lollipop_5_5_427.zip is not working
[Desire Android Development] ze7zez:
Try now. OP has updated the links.

There is unfortunately no access to pa_gapps-modular-pico-5.0.1-RC4-20150208-slimmed.zip.

You can try other versions pa gapps from SiteOwner, for example pico or nano.
[Desire Android Development] d. bucevac:
Da li je moguce instalirati 6.0.1 na moj HTC 820s ?

---------- Post added at 09:17 PM ---------- Previous post was at 08:54 PM ----------

Neka mi neko odgovori
[Desire Android Development] Robbie P:
Is it possible to install 6.0.1 on my HTC 820s?

Let somebody answer me

please use english on this forum-molimo koristite engleski jezik na ovom forumu.

google translate might help-može vam pomoći Googleov prijevod

Do not try to install this rom on your octacore phone, I doubt whether it will work-Nemojte pokušavati instalirati ovaj rom na vaš oktacore telefon, sumnjam hoće li raditi

:):):):)
[Desire Android Development] d. bucevac:
:crying:
[Desire Android Development] farshad 65:
:confused:
[Desire Android Development] aravindaud:
Root
[Desire Android Development] volteado999:
Root acces
[Desire Android Development] spezi77:
Thread closed due to noob posts.
[Desire Android Development] Saf98:
I'll try again later, what about twrp recovery?
[Desire Android Development] spezi77:
Not necessarily.
[Desire Android Development] spezi77:
Please give it a shot, maybe it works out for you.
[Desire Android Development] Saf98:
heres the recovery log ill flash twrp recovery too.
[Desire Android Development] Saf98:
with an older twrp from a different dev/port it flashed but still black screen but with the latest chromiums version it failed. i copied log to sd card in recovery and i checked in windows nothing is in the .txt file?
[Desire Android Development] spezi77:
Hum, i have discovered a line that worries me.

"blkdiscard failed: Operation not supported on transport endpoint"

I have never seen this when flashing LP and I am pretty sure it is the root cause.

Sent from my Nexus™4 ?
[Desire Android Development] spezi77:
With which older twrp did it flash?

Sent from my Nexus™4 ?
[Desire Android Development] dxmachina:
Sehr hübsch!!!

It works! First Boot-time 6min, next less than 1min...

Look an feel like my nexus4.

Nice!

deusXmachina
[Desire Android Development] bla0258:
Could you send some screenshots ??

And how did you flash it ?
[Desire Android Development] dxmachina:
Flashed with 4EXT Recovery Touch v1.0.0.5 RC9

Pictures unfortunately, no (New members (those with fewer than 10 posts) are not permitted to post...)
[Desire Android Development] Saf98:
What? Really didn't work on mine...

Whats your bootloader info?

---------- Post added at 09:51 PM ---------- Previous post was at 09:47 PM ----------

This one

http://xdaforums.com/showthread.php?t=1791371
[Desire Android Development] dxmachina:
Bravo PVT4 ship s-off

hboot-6.93.1002

microp-051d

touch panel-synt0101

radio-5.17.05.23

10.10.2010 17:52:10

system 250 MB

data 182 MB

cache 5 MB

sdcard 11,3 GB

sd-ext 2048 MB

sd-ext2 1024 MB

swap 513 MB
[Desire Android Development] code4bugs:
if it helps this is my configuration :

Same bootloader info as dxmachina

My partition scheme is a little different

system 250 MB

data 147 MB

cache 40 MB

sdcard 4.6 GB

sd-ext 2048 MB

sd-ext2 1024 MB

Flashed on 4ext Recovery Touch v1.0.0.5 RC9 Testing build 40

link to image of reached "about phone" (remove spaces)

http: // postimg.org / image / y28eem9dz /
[Desire Android Development] Saf98:
Why have you both made 2 partitions and swap?

---------- Post added at 10:58 PM ---------- Previous post was at 10:57 PM ----------

What does it say ontop of the hboot revolutionary or alpharev?
[Desire Android Development] code4bugs:
Alpharev (stock hboot) , for the number of partition i tried single partiton sd-ext with no luck, so i tried 2 partition (no swap partition for me). Single sd-ext partition not working for me
[Desire Android Development] dxmachina:
Alpharev too

The second partition results from flashing all 4.4 Roms to my HTC-Desire, not especially for this ROM...

Here some pictures (workarround from code4bugs - remove space before //)

http: //postimg.org/gallery/2vzdfc99q/

The sd-ext2 is used for internal memory...

cat /proc/partitions

major minor #blocks name

31 0 640 mtdblock0

31 1 4608 mtdblock1

31 2 3072 mtdblock2

31 3 256000 mtdblock3

31 4 5120 mtdblock4

31 5 187008 mtdblock5

179 0 15558144 mmcblk0

179 1 11886592 mmcblk0p1

179 2 2097152 mmcblk0p2

179 3 1048576 mmcblk0p3

179 4 524800 mmcblk0p4

shell@bravo:/ $ cat /proc/mtd

cat /proc/mtd

dev: size erasesize name

mtd0: 000a0000 00020000 "misc"

mtd1: 00480000 00020000 "recovery"

mtd2: 00300000 00020000 "boot"

mtd3: 0fa00000 00020000 "system"

mtd4: 00500000 00020000 "cache"

mtd5: 0b6a0000 00020000 "userdata"

shell@bravo:/ $ mount

mount

rootfs / rootfs ro,relatime 0 0

tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0

devpts /dev/pts devpts rw,relatime,mode=600 0 0

proc /proc proc rw,relatime 0 0

sysfs /sys sysfs rw,relatime 0 0

none /acct cgroup rw,relatime,cpuacct 0 0

none /sys/fs/cgroup tmpfs rw,relatime,mode=750,gid=1000 0 0

none /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0

tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0

tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0

none /dev/memcg cgroup rw,relatime,memory 0 0

none /dev/cpuctl cgroup rw,relatime,cpu 0 0

/dev/block/mmcblk0p2 /system ext4 rw,noatime,barrier=0,data=ordered 0 0

/dev/block/mmcblk0p3 /data ext4 rw,nosuid,nodev,noatime,barrier=0,stripe=64,data=ordered,noauto_da_alloc 0 0

/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

/dev/block/vold/179:1 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,code

page=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=

cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0

/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

shell@bravo:/ $
[Desire Android Development] Saf98:
I'm on the revolutionary stock hboot but maybe its the way lollipop has to be flashed by having another partition. Might need some script changing.
[Desire Android Development] dxmachina:
On your sdcard create / modify a partitionlable like this...

http: //postimg.org/image/4yc9kojil/
[Desire Android Development] Jss22:
It works with a 2nd partition, tried few minutes ago :D
[Desire Android Development] NachoLozano:
It does not install it

It does not install it

When I try reboot after install it shows me this message:

"Not SO installed. Do you want reboot anyway?"
[Desire Android Development] Saf98:
Do a full wipe again and after flashing it again and reboot with USB cable in and do adb logcat.
[Desire Android Development] Saf98:
What recovery?
[Desire Android Development] NachoLozano:
TWRP v2.6.3.0
[Desire Android Development] Saf98:
I don't think it works with TWRP. It works with 4ext but with 2 partitions.

---------- Post added at 03:33 PM ---------- Previous post was at 03:28 PM ----------

@spezi77 i will try it 2 partitions as well.
[Desire Android Development] spezi77:
Yes, using two sd-ext partitions seems also reasonable to me. I also have two, dunno when this happened. :confused:

Sent from my Nexus™4 ?
[Desire Android Development] maxens63:
It works.

Made 2 sd-ext partitons. Because when you install the rom, it goes on one of the 2 sd-ext.

It doesn't reboot when the screen shuts down. Just wakes up when pressing power button or "back" button.

So it's a good start for having lollipop on our old Desire.:D

Thank's a lot Spezi :good:
[Desire Android Development] spezi77:
Fixed telephony! :D
[Desire Android Development] NachoLozano:
Working !! two sd-ext partitions and 4Ext recovery
[Desire Android Development] Jss22:
Nice! I think bluetooth works, I used it to send the screenshots to pc
[Desire Android Development] Saf98:
I made 2 partitions got black screen for a 1 hour and a half? I'm charging c if that's the problem too.

---------- Post added at 08:39 PM ---------- Previous post was at 07:46 PM ----------

@spezi77 why isn't it working on mine?
[Desire Android Development] spezi77:
I cannot say. Maybe insufficient space. I have seen bad blocks on NAND partitions in your recovery log.

To double check, please repeat installation and share your recovery log and logcat.

Sent from my Nexus™4 ?
[Desire Android Development] Saf98:
I flashed alpha rev hboot too but still didn't work ok ill do a log cat.

---------- Post added at 09:28 PM ---------- Previous post was at 09:07 PM ----------

ive redownloaded and its worked and it says reset phone cos encryptian unsuccessful and the logcat is still going...
[Desire Android Development] Saf98:
[MENTION=5091819]spezi77[/MENTION]

the recovery log dissappeared?
[Desire Android Development] dxmachina:
That means, the rom installs and the ROM causes an error later?
[Desire Android Development] spezi77:
I suggest that you try a different hboot which has a larger system partition, e.g. this one with 255mb: http://xdaforums.com/showpost.php?p=40811167&postcount=5 . I think that during 1stboot a few files need to be compiled and because of too many bad blocks they don't fit into your system.

Sent from my Nexus™4 ?
[Desire Android Development] maxens63:
It's strange, because the rom only uses 2 or 3 mo on system
[Desire Android Development] Saf98:
Yh.

---------- Post added at 11:00 PM ---------- Previous post was at 10:59 PM ----------

Ok ill try again, so what about the 2nd partition is it necessary.
[Desire Android Development] spezi77:
[MENTION=5383638]lilsafbig[/MENTION], something goes completely wrong on your phone. I see this for the first time:

W/MasterClear( 416): !!! FACTORY RESET !!!
E/MasterClear( 416): Can't perform master clear/factory reset
E/MasterClear( 416): java.io.FileNotFoundException: /cache/recovery/command: op
en failed: ENOENT (No such file or directory)
E/MasterClear( 416): at libcore.io.IoBridge.open(IoBridge.java:456)
E/MasterClear( 416): at java.io.FileOutputStream.<init>(FileOutputStream.java
:87)
E/MasterClear( 416): at java.io.FileOutputStream.<init>(FileOutputStream.java
:72)
E/MasterClear( 416): at java.io.FileWriter.<init>(FileWriter.java:42)
E/MasterClear( 416): at android.os.RecoverySystem.bootCommand(RecoverySystem.
java:454)
E/MasterClear( 416): at android.os.RecoverySystem.rebootWipeUserData(Recovery
System.java:422)
E/MasterClear( 416): at com.android.server.MasterClearReceiver$1.run(MasterCl
earReceiver.java:49)
E/MasterClear( 416): Caused by: android.system.ErrnoException: open failed: ENO
ENT (No such file or directory)
E/MasterClear( 416): at libcore.io.Posix.open(Native Method)
E/MasterClear( 416): at libcore.io.BlockGuardOs.open(BlockGuardOs.java:186)
E/MasterClear( 416): at libcore.io.IoBridge.open(IoBridge.java:442)
E/MasterClear( 416): ... 6 more

Did you give the hboot with increased system size a try?
[Desire Android Development] Saf98:
I havnt yet didn't get chance on pc, but yh I noticed that when I pressed reset phone that showed but it never reset my phone.

edit: still the same result.
[Desire Android Development] spezi77:
Was this for 255 hboot?

Sent from my Nexus™4 ?
[Desire Android Development] Saf98:
Yep.

---------- Post added at 02:41 PM ---------- Previous post was at 02:41 PM ----------

Yes the one where it says alpharev spezi in the bootloader.
[Desire Android Development] spezi77:
How did you partition your SD csrd?

Sent from my Nexus™4 ?
[Desire Android Development] Saf98:
4ext recovery made 2 partitions.
[Desire Android Development] dxmachina:
The two ext4-partitions are the second and third partition on your sdcard? (the fat32 (sd-ext) is the first?)
[Desire Android Development] NachoLozano:
Maybe the size of partitions isn´t enough.

My ext4 partitions are: ext4 700MB and ext4 2GB
[Desire Android Development] Saf98:
Mine are both 1gb.
[Desire Android Development] maxens63:
I have mine with:

Ext4 => 1024 mo (2 times)

Fat32=> 2048 mo
[Desire Android Development] LaidbackNikez:
Good work mate
[Desire Android Development] Saf98:
So mine is same as yours. I got 8gb so about 4gb is fat 32.
[Desire Android Development] Saf98:
Would be awesome if u could make k3 for lollipop.
[Desire Android Development] Saf98:
[MENTION=5091819]spezi77[/MENTION] I checked my partition alignment it showed only 1 partition... So all that time I didn't have a 2nd partition? So I repartitioned but 2nd 2gb and it works.:cool:

---------- Post added at 11:04 PM ---------- Previous post was at 11:03 PM ----------

[/COLOR [MENTION=5091819]spezi77[/MENTION] I checked my partition alignment it showed only 1 partition... So all that time I didn't have a 2nd partition? So I repartitioned but 2nd 2gb and it works.:cool:
[Desire Android Development] spezi77:
Congrats! I'm finally relieved to hear about this..

BTW, I believe that I have figured out why the ROM requires two sd-ext partitions. On Lollipop we have to use ext4 as file-system as it is mandatory for booting it with SELinux in permissive mode. It seems that during installation, one sd-ext is allocated for /system and the other one for /data. And that's why the internal NAND memory is not occupied.

Well, that's my theory and it could be wrong.. Does that sound kind of reasonable? ;)

Good night! And have fun..
[Desire Android Development] maxens63:
It's a good explication..

Because once the rom installed, it needs more than 250mo, so a good reason to use ext4. That's What I think;)
[Desire Android Development] Saf98:
So is it better keeping it on sd ext or on the internal partition? Maybe u can test that out try making it so it compiles on the phone.
[Desire Android Development] spezi77:
Edit: Lollipop won't work on NAND for HTC Desire because we cannot change the internal memory from yaffs2 to ext4. At least I dunno how this could be done.

Sad but true, we cannot really use Desire's internal memory. Maybe in the end, when the ROM is fully functional, something useful comes into my mind.