Database Users

[q] help! Tried to update rom and now phone isnt working!

ok so i tried to put rafdroid on my phone (link below):
http://forum.xda-developers.com/showthread.php?t=908528
I have tmobile HD2 running gingerbread 2.3.2. When I tried following the instructions and formatting/partitioning the SD card, my phone wouldnt work. i have clockworkmod recovery on my phone and i used it to install the rom zip file. it got to the screen where it has a picture of android and says dafdroid by dafpigna and stayed there for well over the initial startup time (over 20 min). I tried installing the dafdroid kernel as well (thru clockworkmod) and its still doing the same thing. when i tried formatting the sd card to anything other than quick format it wouldnt work and it wouldnt complete partitioning through the computer it would only work through clockworkmod on my phone. i tried to flash to another rom and even back to windows and it kept giving me an error message about some rampi.dll (something like that) isnt there.
please help! i cant use my phone at all! i have a 500 dollar paperweight

Hi,
Need a bit more information.
Can you still boot into magldr (holding down power button after switching on?)
What operating system are you running on your pc/laptop?
How far did you get when you were fomatting your sd card?

i find it quite common that an android rom wont complete the first boot after flash. mostly, pulling teh battery and booting again solves it.
Its also far more common when you didnt wipe the partitions from the previous rom first. (CWM, wipe data/factory reset, you can later use cwm - advanced restore - and just restore data and sd-ext to get your data and apps from teh previous rom back)
Partitioning, could be a dodgy sd card, no suggestions
rampi.dll - was it rapi.dll? update activesync to latest version.

I have an issue cannot install larger nand roms onto my phone previous roms worked tried various typhon cm7 roms, various miui roms both magldr and clk roms does not matter used task29 increased cwm size from 150 up to 250 and boot just hangs. Noticed roms larger than 90 MB zipped does not work at all they install but just hangs on boot

invalid boot image header no matter what I do! Please help

I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin

fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
Hi. I am not sure , but you can try to formar the SD card, because with the phone seems to be O.K. I am formatting always with Panasonic sd formatter , before flashing.

fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
Hi,
It sounds like your CWM partition is too small .
Are you sure you are flashing the correct CWM size according to your ROM's [OP]?
Try using KSUBEDI's TOOLKIT (Don't forget to thank him).
It's a simple way of partitioning your CWM.

yes i make sure CWM is correct partition size
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.

yes i make sure CWM is correct partition size
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.

fxdstudios said:
Yes I always make sure I use the recommended partitioning in the op of the rom I choose.
I have formatted my SD-card with the panasonic tool
as far as the toolkit. It may be something I did wrong but this started with my phone after my FIRST USE of the toolkit.......PROBABLY NOT THE TOOLKIT although I would love to know what I did to my phone.
I just flashed another HD2 about 10 minutes ago and no issues at all.
The only thing I can think of is possibly nand corruption but then again all things I try to do complete 100% except booting nand.
Click to expand...
Click to collapse
Hi,
Did you transfer the ROM by cable or card reader?
Corruption can occur with cable(USB)transfers.

card reader in my laptop.
Like I said I have done this numerous times. Close to 100 times I would guess. I do two hd2s for friends today. no issues with either. although mine is still giving the error no matter what I do.
First time I have seen this error and I do not care about my data or backups or anything of the sort.
I have done EVERYTHING to try and rectify this issue I am having to no avail.
I am stumped at this point

bump I am unsure of what to try now

Did you find a solution????
I also have the invaild boot image header error.
This used to be my phone, but i have handed it down to an employee.
He has caused a fault where it force closes with android.process.media, especially when i go to market.
I thought i would update the rom and hopefully "delete/overwrite" the problem.
One thing i did was a backup with ROM manager and upgraded that to 4.
This phone will boot into the existing ROM - Nightlys typhoon 3.2.8, but if i try to go into recovery I get the error.
Anyone found the answer????

fxdstudios said:
I always search and read although this one I have not found what I am looking for.
Issue:
Phone started to reboot over and over right after a phone call. It had been working properly for months never doing this before.
Anytime I boot AD NAND I get "INVALID BOOT IMAGE HEADER"
setup when issue started.
MAGLDR 1.13
CWM 3.0.2.4 135m
Typhoon CM7 3.3.0
I HAVE DONE THE FOLLOWING.....
TASK 29
Reflashed MAGLDR
Reflashed CWM
Used CWM to install typhoon CM7 3.3.0 and also tried 3.3.5 after re-doing those steps
I also tried hd2 ginerbread, Kingdom sprint wwe, and a few others..also re-doing everything first between them.
All of this yeilds the "invalid boot image header" error. It seems to be permanent???
Am I missing something? I have flashed over 40 hd2's and have never seen this error before.
The phone is my personal one and I could not even count how many times I have flashed it. Could the nand be corrupted or would that cause other errors installing magldr/cwm?
PLEASE HELP ME.....like I said its my personal phone and I have no backup
THANK YOU FOR YOUR HELP!
Justin
Click to expand...
Click to collapse
well i dont think that 135 is the exact partition ....135 is used for nexus hd2 but for typhoon rom or hyperdroid rom u must use 150 mb systeme partition with 5 mb cach ...try from the start with task29 to clear everything and flash angain i'm sure it will work

Are you still having this? I seem to be having the same problem now. If I restore a backup it will give me "invalid boot image header". If I put a new ROM over my backup it works fine. I have task 29d. Loaded cLK, CWM, and then a new ROM. Backed this up and then immediately restored it and got the same error when trying to boot. I can get into recovery fine. I have tried different cLK partition layouts too. ):

I did it too, this is the problem and the fix
http://forum.xda-developers.com/showthread.php?t=1040564

HTC HD2 Stuck on Android bootscreen.

Hi,
I've got an HTC HD2 here, with Android installed on it. (NAND, I believe.)
It was bought second-hand with Android pre-installed.
Because it was still linked to the google account of the previous owner, I had to restore the whole phone to factory settings. Since that didn't work, I've just decided to install another Rom.
After some messing around, I managed to install Clockworkrecovery. (It wouldn't boot for some mysterious reason) And then I installed an Android Rom. (Energy™ -.¸¸.·´¯ Sense 3.5 Runnymede)
After some time, the phone rebooted and got stuck on the Android boot screen.
I tried to install another Rom, but now they all get stuck on the boot screen. (I have tried another Runnymede rom, and RCMix3D)
Does anybody know how I can fix this?
I wiped my Dalvik Cache, I wiped my Cache partition, I wiped my data/factory reset. I am using the MAGLDR as boot thingie, but that's working perfectly.
I have formatted my SD-card with G-Parted, on my Ubuntu-PC. (First partition FAT32-750MB, Second partition EXT3 - 1GB and a Linux-Swap of 100MB)
For some strange reason, ClockworkRecovery cannot format my SD-card. (Well, it says it can, but as soon as I stick the card in my PC, the PC tells me it's corrupted. (Windows XP on my Father's PC tells me it has to be formatted, on my Ubuntu it doesn't show up as mountable)
Thank you in advance
P.S. I don't mind losing data, there's no personal data on it. Any solution (which doesn't involve buying a new phone) will do.

Quickest solution I would try is format the entire card to fat32, and see if your pc detects it. Once it does, put the rom on it, put in in the phone, boot into clockwork format data/cache/dalvik install the rom then reboot and see if it goes past the bootscreen (keep in mind first boot takes a while, but if it takes more than 2-3 minutes theres still a problem.
Do you know what partition layout of clockwork you installed by any chance? Some roms require specific layouts in order to work correctly.

Thank you for your reply.
Unfortanetly, that didn't work.
I have installed Clockworkmod like they say on jayceooi dot com. (I cannot past links yet, but here's the step-by-step guide:
Step by Step Guide
Power on your phone and don’t let go power button.
DFT MAGLDR Bootloader will be loaded.
Use volume down button to go down to 5. USB Flasher.
Then press call button to load USB Flasher mode.
Connect USB cable from PC to phone.
You should see Wait USB…USB.
At PC, right click on DAF.exe and select ‘Run as administrator’.
Click ‘Yes’ if User Access Control prompt up.
Follow onscreen instructions to install.
Phone will be rebooted after installation finished.
DFT MAGLDR Bootloader will be loaded then.
Disconnect USB cable from phone.
Use volume down button to go down to 8. AD Recovery.
Then press call button.
ClockworkMod Recovery will be loaded then.
That’s all.)
I used the 150MB-Partition one.

Didnt work how? Does the pc detect the sd card now after you formatted?
The directions you posted are right, so maybe try a different partition layout. The roms that you said you tried use different layouts than what you have and that may be a problem. Test a CM7 rom and see if it will boot, they tend to have less problems and are overall more stable than sense roms.
I recommend Typhoons rom: http://forum.xda-developers.com/showthread.php?t=933951
Try to install it and see if it boots. It uses the same partiton layout that you have now. If it boots, thats indication that you may need a different layout if you want to run a sense rom.

Well, I could re-format my sd-card and re-partition it, but it (Android) still got stock at the boot screen.
Using the Typhoon rom, I got the same problem. The Rom appears to be succesfully installed, but it didn't really boot.
I now tried to installed Windows Phone 7, this works fine. (I don't want to install WP7 however, I want to install android)
I tried the following too: (Post by a3r0n1)
http://forum.xda-developers.com/showpost.php?p=18868874&postcount=14
/
At the "Using "HD2 Toolkit" select "Magldr repartition" Make sure that you are using the recommended partition size for your rom!" part, I got an error that the file was too big when I tried to choose a partition of 300MB, I honestly have no idea what the partition size should be. (I want a sense-rom, I don't have a clear preference which)
I did install the Clockworkmod with 400MB with succes now.
However, still got the same problem. Android seems to get in a loop somewhere in the boot screen
EDIT:
I noticed that the Micro-SD card always corrupts after CWM installs the Android-Rom.
I think that may be the core of the issue here.
Does anybody know how I can install Android without CWM?

Are u repartitioning the phone? That might be the problem. Hope this helps
Sent from my Nexus One using XDA App

I manager to install an old Desire-based rom with Android 2.2 through a daf installation.
This one works fine but I still would like to install a Rom with Android 2.3 via a more regular way.
One problem I'm facing with this Rom is a very limited amount of internal storage. (about 55MB)
And I've got a big battery leak, the battery drains very fast. Much faster than my Desire HD. (The HTC HD2 we're talking about isn't mine, It's my mother's)
So does anyone know how I can install a regular Rom (preferably runnymede based) without CWM? Or does anyone know how I can resolve my problem?
@akaruna: I do not know how to partition the phone, I believe I didn't do that. Should I? I did partition the SD card. (CWM made unreadable cards for some obscure reasons, so I partitioned the SD card using gparted on Ubuntu)
Thanks in Advanced
Sjoerd

If you have limited internal storage then the main problem is the partition table is not correct. This is also why the roms you install are stuck on the bootscreen. When you install roms that require a bigger partition table than what you already have on your phone they will be stuck in a bootloop.
Go and download the HD2 NAND TOOLKIT: http://forum.xda-developers.com/showthread.php?t=1090783
Check out the video to familiarize yourself with the features, then repartition your MAGLDR with the correct partition table that the rom you want requires. Go into clockwork and install rom from zip.

Yes the tool kit is the best.

Yea the toolkit works wonders. Even though I still do it the original way ;p I do everything faster that way for some reason
Sent from my Nexus One using XDA App

Oh and yes, always read the thread from that certain Tom so that way u know exactly what partition table/size to use. Usually linked also.
Sent from my Nexus One??? (HD2) using XDA App

I tried it again with this rom: "[18Dec 2011] [CMR] Sensation xl Sense3.5/2.3.5 v2.7 BETA OC & marc1706 0.1.3 kernel" (I believe I'm still not allowed to post links)
I used the NAND toolkit this time for the System Partition Size.
The only thing I actually did was clicking 350MB as System Partition Size and then I clicked repartition. And then I followed the on-screen instructions, which involved clicking next and after some installing some drivers everything went fine. (With the HD2 in USB-flash mode of course, it also said the job was completed succesfully)
I wasn't able to choose a bigger size for some reason, it told me the 400MB was too big.
Still the same problem, the phone gets stuck at the Android boot-screen.
Does anybody have an idea? Thanks in advance (Again, I'm not scared of losing any data, if anyone has any solution at all: I'm more than happy to hear it)

I tried another DAF rom and got the following error:
"Error Description: Size is too big.
Info: .\RSPL\RSPL.cpp (800)"
So I tried repartitioning the System Partition Size (MAGLDR) to 400Mb.
However, It gave me the exact same error.
Does anyone know has any idea? (For example, how I can change the partitions in another way)
(Partitioning it at 360MB works fine)

Not sure what it is but the DAF file I use let me partition to 445...... those sense time are heavy and if the partition isn't right it will bootloop or not
Sent from my HTC HD2 using XDA App

" sense time " and do you have the sdcard partition at 1gb?
Sent from my HTC HD2 using XDA App

............ sense rom.........
Sent from my HTC HD2 using XDA App

[Q] No screen input from android / wm

Hey guys, I need some quick suggestions if anyone has it. Currently I have a non working phone.
I have been running an ICS NAND rom on my hd2 for a while now, havnt had any issues (a few niggles with the rom, nothing major) so I thought today I would update to the latest version.
I used the hd2toolkit to resize the partition to the biggest size it would allow, then used ad recovery to flash the new .zip to the nand. This is where my problems started, whenever i booted it just showed the boot animation, (I waited over an hour and pulled the battery out and re booted / reflashed a few times).
I found with a differnet rom i tried, pulling out the SD car would allow it to get to the welcome screen, but no screen input was accepted. I thought this was a bit weird but pushed on. I tried a different rom and it stated after flashing that it was optimising applications and looked like it was stuck in a boot loop. I did some reading up about it and found that task29 should help. I ran this but then all the phone would do is show the green HTC on the white background, it wouldnt let me to get into magdlr menu.
I then decided to to a full restore and go back to the wm rom from th HTC site (The australia telstra version), this seemed to flash on fine, but now I can not slide or click buttons in wm, no screen input is accepted. Which is strange as it was doing this in an android rom, as I mentioned previously.
Any ideas on how I can get touch working / get a NAND android rom to work again.
Thanks in advance guys

First verify that you have hspl installed by powering on while holding vol down button to get to bootloader screen
Go back to the hd2 nand toolkit
1.task29
2. Select either cLK repartition or Magldr repartition and select size for your rom (not the maximum size). 200 mb is fine for ics using sdext partition.
3.Select magldr update recovery or cLK install recovery depending on your selection above.
4. Reboot phone by pressing power and holding to get to magldr or power and home button to get to cwm recovery.
5. Install ICS from sd card as before

Thanks for the help, I had to flash a different radio version to get magdlr to boot.
I now have android running of my NAND, but the screen is non-responsive now, as it was yesterday.
I doubt it is hardware related, because I have never had an issue before yesterday when I wanted to change the android version, any ideas how I could get it working?

Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.

htccraze said:
Make a backup and then repartition again using HD2 toolkit. Maybe you got a bad download or something. Seems simple but it does happen. To me if I didn't know you choose the biggest it would sound like the partition wasn't big enough. Maybe try a cyanogen ROM since it reguires very little partition size and report back if successful.
Click to expand...
Click to collapse
I have tried two different android roms and the stock wm image from htc's site, all of which the screen doesn't work on. I will have a try with a cyanogen ROM and see if that makes a difference. Thanks

http://forum.xda-developers.com/showthread.php?t=769026
I just tried this rom and still no deal. This is very weird as I haven't had any issues with the screen at all, the phone is still in new physical condition.
Does anyone want to have a stab in the dark, as I really need to use it as a GPS tomorrow and any help would be appreciated.

Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.

htccraze said:
Tell me what the steps you take to install a new ROM. Do you have MAGLDR or clk? Have you task29 yet? Are you sure your using the right partition? Are you using nand or sd Android?
If all else fails maybe check out this thread to reinstall
MAGLDR and then cwm. I've had problems in the past installing HyperDroid without
wiping my SD card first. Maybe check out this nand ROM instead or Coredroid found in my signature.
Click to expand...
Click to collapse
When installing a new rom, I have resized the magdlr partition, then copied the .zip to the sd card, then in ad recovery installed the zip through there. This has worked fine in the past. I followed the videos you have linked and I'm pretty sure I'm doing everything right and yes ive used task29 several times. In AD Recovery every time it states that installation has been successful. I have also formatted my SD card many times.
The ROM you linked, I can find download links on the page, not sure if I'm just missing them.
I just tried an SD card rom, its doing the same thing, no touch input is accepted.
Does NAND roms and SD roms not working imply that it could well be hardware? I just dont understand as it stopped working when I was reflashing yesterday and it was not dropped or roughly handled in anyway during this process.
I am now going to investigate MTTY (for bad blocks) and try reflashing back to original WM again. Please post more suggestions if anyone has them.

Another update: I just restored to default using the method listed below.
http://www.jayceooi.com/2011/08/15/how-to-restore-stock-rom-on-htc-hd2-video/
It took around 40-ish minutes and still no input from the screen, this is seriously frustrating.
WM boots fine and everything, but still no input is accepted.

I'm sorry to say but if your having the same problem with all that then it sounds like the digitizer stopped working. Maybe someone else knows something I don't so I would wait to see if they could help out.
Sent from my HTC HD2 using XDA

Thanks mate, I am not sure why it would have just stopped last night. Appreciate all the help! I'll see if anyone else has any suggestions.

It's not a problem. I do have to admit that it does seem pretty odd the timing of it. Hopefully it's a not the digitizer and someone would be able to point out what might be the cause of everything.
Sent from my HTC HD2 using XDA

This may seem a little crazy, but after having a search online about my issue, it seems that a ribbon going to the screen / digitizer is behind the power button on the HD2s, which apparently can get loose and after a sharp press of the button it started accepting screen input again!
The issue for me now is that when the power button it will stop accepting input again, untill I press it firmly again. I think I may need to open up the phone and check all the connections now.

[Q] Where am i going wrong

I did everything needed. When i use de DFT flasher i finally got a working image file (The DFT desire rom). But i have no CWM available anymore.. When i converted the IMG files from the DFT install to upgrade.zip and installed it. It worked, well the install did. But as soon as i run the phone i get errors. The same kind i got when i started useing the eclipse mod (3.52). Which is weird. Since i cannot locate the problem. why do all these errors keep comming up.
Other then that i was kinda happy with the stock desire rom which runs completely from the HD2 internal memory, but the i tried makeing changes in the system folder and it seems i have no superuser abilities. So why is this? Or do i need to root this standard desire rom and if so. How does that work cause i imagine its different from the way you would root a untouched phone. Weird enough it does show a superuser icons in my list of programs.
Im almost there i need to figure out these minor tweaks to fully enjoy all those nice roms out there.
Hope anyone is out there to get a light shining on it

That's a really old rom and flash method,,thereare no other roms that work that way.it was the original proof of concept .
Find any other rom,findout what popartition size it requires, use the nand toolkit to set that size, which will apply cwm too, thenflash the rom from within cwm.

Here is the problem every flash I do with a rom. I end up getting errors after the boot. I have a 8gb sd card. Formatted to 2048 ext 4 and 128 swap (useing cwm).
For now I'm running the DFT Rom. I edited the install and added the cwm img aswell. So now o can boot CWM to even though useing the DFT Rom. I used CWM to root the DFT Rom. To be honest for now it will do. But I'd love to have some more eye candy. But I can get the toms installed. After installing CWM 3 TIMES with different sizes and useing the CWM to install 3 different roms I get the same error on every install. I assume something goes wrong accessing the ext4 partition on the sd card. But I have no idea.
I suppose there is no 400mb Rom with sense 3 or 3.5 that runs without sd ?
Sent from my HTC One X using xda app-developers app

You say that you get the same error each time, but you haven't actually mentioned the error message (as far as I can see). What is the error that you get?

Its the same kind of errors I get from installing the eclipse Rom.
Com.xxxxxxx.xxxxx
Errors. That they stopped for some reason. Xxxxx is Google and phone and all kinds of programs. I just don't understand why flashing with CWM keeps going wrong. But I updated a couple of things and installed su.2.xxxxx.signed.zip and a couple of changes o wrote. With CWM and that all works fine.
I just think that for some reason when booting the first time all those Roma that need ext4 on sd. For some reason can't find them.
Sent from my HTC One X using xda app-developers app