Database Info

I think something is wrong after flashing EXT4 mod

I think i messed something after flashing the EXT4 mod because when i booted into recovery the text under blue line is orange and yellow and i don't remember it being like that before? i can hit reinstall packages and it loads cwm fine as far as i can tell? this is what it says please let me know whats wrong and how i can fix it please. thanks
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/command
#MANUAL MODE#
--Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/recovery.log
E:Cant open CACHE:recovery/recovery.log
E:Can't mount /dev/block/stl11
(invalid argument)

it is a know issue after flashing ext4, you are still ok, just click on reinstall packages and it will take you to cwm

yeah I'm sure everyone who flashed EXT4 is experiencing the same thing, I am too. CWM still works as far as I'm concerned. I've done like two restores, and flashed trigger rom successfully. I think everyone is getting those mounting errors.
Nevertheless, the phone is ridiculousness fast and smooth !! big ups to dsexton702.

slapshotx2002 said:
it is a know issue after flashing ext4, you are still ok, just click on reinstall packages and it will take you to cwm
Click to expand...
Click to collapse
Crap now that i think about it the OP did mention something about an error botting into CWM i guess this is it right?is it a false alarm?? and how do i fix it? or is there no way to fix it? thanks for the quick reply.

Bryanb82 said:
I think i messed something after flashing the EXT4 mod because when i booted into recovery the text under blue line is orange and yellow and i don't remember it being like that before? i can hit reinstall packages and it loads cwm fine as far as i can tell? this is what it says please let me know whats wrong and how i can fix it please. thanks
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/command
#MANUAL MODE#
--Appling Multi-CSC...
Installing Multi-CSC
E:Can't mount /dev/block/stl11
(invalid argument)
E:Cant mount CACHE:recovery/recovery.log
E:Cant open CACHE:recovery/recovery.log
E:Can't mount /dev/block/stl11
(invalid argument)
Click to expand...
Click to collapse
thats because the recovery on the rom is not compatable with ext 4 but clockwork is hence why u can still get into clockwork but not the stock recovery.

yes OP is correct as of now there is no way of fixing it. just ignore it and click install packages and it works just fine

Bryanb82 said:
Crap now that i think about it the OP did mention something about an error botting into CWM i guess this is it right?is it a false alarm?? and how do i fix it? or is there no way to fix it? thanks for the quick reply.
Click to expand...
Click to collapse
will be fixed along with the chargeing animation once we get more ext 4 roms.

thanks everybody i feel allot better now but one more question. Even if i reflash odin and then reflash bionix the ext4 mod will still be there right? or do i have to do the mod again?

Bryanb82 said:
thanks everybody i feel allot better now but one more question. Even if i reflash odin and then reflash bionix the ext4 mod will still be there right? or do i have to do the mod again?
Click to expand...
Click to collapse
if u odin it flashes back the stock file system u would have to reconvert.

RaverX3X said:
if u odin it flashes back the stock file system u would have to reconvert.
Click to expand...
Click to collapse
i fixed the battery issue but i cant fix the recovery AKA cache mount error in recovery
im still working on it, also i found a way to convert back to rfs so you wont have the recovery cache mount issue but you also wont have ext4

dsexton702 said:
i fixed the battery issue but i cant fix the recovery AKA cache mount error in recovery
im still working on it, also i found a way to convert back to rfs so you wont have the recovery cache mount issue but you also wont have ext4
Click to expand...
Click to collapse
Ive been screwing around trying to get my partition for ext4. And I was able to change my cache mount to mount and now I'm not receiving the cache error. Dont know that I did anything to help it along but my phone seems fine other than the OC problems which are minor
Sent from my SGH-T959V using XDA Premium App

GDofWR420 said:
Ive been screwing around trying to get my partition for ext4. And I was able to change my cache mount to mount and now I'm not receiving the cache error. Dont know that I did anything to help it along but my phone seems fine other than the OC problems which are minor
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
WHAT!!! you fixed the error in red writing when you enter recovery before CWM!!!????
and what OC problems?

dsexton702 said:
WHAT!!! you fixed the error in red writing when you enter recovery before CWM!!!????
and what OC problems?
Click to expand...
Click to collapse
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App

GDofWR420 said:
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
try 1400 instead of 1375 for the core and internal maybe to 1200
also might have to warm the rom up to OC'ing because my 1.5 was extremely stable but not till awhile with the rom

dsexton702 said:
try 1400 instead of 1375 for the core and internal maybe to 1200
also might have to warm the rom up to OC'ing because my 1.5 was extremely stable but not till awhile with the rom
Click to expand...
Click to collapse
Kool ill stretch this baby out on 1.2ghz and work my way towards something a little higher. Also I made a note to try those settings next time I try 1.5ghz. Its wild though at 1.2ghz my quadrant scores are in the 1800's all thanks to your easy to follow steps. Thank you sir
Sent from my SGH-T959V using XDA Premium App

I was also screwing around in the sd card yesterday night and noticed I had 3 nandroid back ups I deleted the 2 oldest and kept the newer one now I'm also not getting that mounting error in cwm and as far as OC goes I've notice that my phone is stable at 1.5ghz but depending on which of dr honks kernels I use it requires different voltages:
the 2.1 UV it's stable at core voltage 1400mv and internal 1175mv and the non UV Kernel it's stable at 1400mv and 1150mv. in either one of these settings the scaling need to be set to conservatiove or performance starting at 200mhz instead of 100mhz.

ssmokey727 said:
I was also screwing around in the sd card yesterday night and noticed I had 3 nandroid back ups I deleted the 2 oldest and kept the newer one now I'm also not getting that mounting error in cwm and as far as OC goes I've notice that my phone is stable at 1.5ghz but depending on which of dr honks kernels I use it requires different voltages:
the 2.1 UV it's stable at core voltage 1400mv and internal 1175mv and the non UV Kernel it's stable at 1400mv and 1150mv.
Click to expand...
Click to collapse
yea i noticed they needed to be changed also but i wasnt sure to what
so thank you very much smokey!
also your saying that your ext4 right now, but you dont have the recovery issue?
ive only made one back up and it was on my ext4 sgs4g and im still having the recovery issue even after making some cache adjustments like godofwar did
hmmm need to figure this out

GDofWR420 said:
Yea I was going in and out of cwm trying to partition like Lenny hodapp and I noticed the red text error wasn't coming up so I went to mounts and cache was the only one that said unmount so I mounted it and I have not received that error since. If I see it come back I will let you know.
And my OC problems are things like xda app freezing and market sometimes makes the phone vibrate and back out of some screens on it's own. 1 or 2 fc's and that's about it. Also I turned off stability watch and still unstable at 1.5ghz. Should I increase internal voltage by +25 or +50?
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
just a fyi, when you SEE "unmount" that means what ever your looking at is "mounted" when you click on it and see "mount" that means its unmounted. I had to pm a dev for that info.

I had to odin my phone to KD1 then formatted the fs to ext4 then flashed Bionix frost from cwm I went to recovery and I had those erros in the page. I went into reinstall packages/ apply update from sdcard/ Yes - Install /sdcard/update.zip then rebooted recovery and I had no more mounting erros in the recovery page. I hope this helps

Can't mount /cache/recovery/

Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4

Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?

ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.

Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849

Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.

having the same problem.. so should i try to wipe the cache and see what happens?

I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.

I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?

What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?

OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers

EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?

@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.

Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers

EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?

[Q]My 9003 is broken

My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!

realcode said:
My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
Click to expand...
Click to collapse
Dont restore the backup of one firmware over another firmware.
Flash xxkpe twice aand over it flash xxkpq with factory reset after flashing each time. Use this guideforum.xda-developers.com/showthread.php?t=1133787
Sent from my GT-I9003

I tried to format the data, but it didn't work. I can see the previous installed application broken even I flashed with new ROM(Re-partion).
It seems something was locked by system.

Follow this guide to flash XXKPQ Check if everything works well. Try to restore your CWM backup

I tried to flash XXKPE/XXKPQ, but I got a wrong message "E: failed to mount /data (Invalid argument)" when the phone startup".
And the phone repeated to restart, I can't the normal phone.
It seems there is something wrong with the partion of /data.
Is there other way to fix it?

the /data is ext4, I am not sure XXKPQ support ext4 or not.

When flashing XXKPE with pit and all the other stuff you should see Re-Partition checked. Then everything should be formatted with the standard RFS filesystem unless you convert it. The stock Kernel doesn't support ext4, but that doesn't mean that you can't try to flash a Kernel that supports ext4.
Did you let the phone boot up completly after every flash?

I didn't let XXKPE boot up completely after flash.
It seems that the /data partion was not reset in flashing with the "Re-partion" selected.
I got error message when I tried to check the disk status.
/sbin # fsck.ext4 /dev/block/mmcblk0p3
fsck.ext4 /dev/block/mmcblk0p3
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p3: recovering journal
fsck.ext4: unable to set superblock flags on /dev/block/mmcblk0p3

[q] no internal storage

I flash with odin and make mistakes.
Flashed:
CSC in PDA
PDA in CSC
Click to expand...
Click to collapse
So everytime I entered recovery I get this kind of messages
E:failed to mount /data (No such file or directory)
E: failed to mount /sdcard (File exists)
E: copy_cache _media: Can't mount /sdcard
your storage not prepared yet,p lese use UI menu for format and reboot actions
E:failed to mount data (Invalid Argument)
Click to expand...
Click to collapse
And I get Bootlop on samsung logo (the second one)
Don't know why, none Roms managed to boot EXCEPT THIS ONE (CM7) http://forum.xda-developers.com/showthread.php?t=1527359
BUT I'm facing this bugs:
#No internal storage at all (It says 0 and can't install google play apps because it says that I have no free space)
#Reboot erase all config and apps installed. It takes the phone like it recently flashed the rom.
#EFS is missing (Have backup, restored, but the problem above makes all difficult)
I'm thinking that the /device files might be corrrupted. But I don't know how to solve this.

try flashing pit file

mehran 92 said:
try flashing pit file
Click to expand...
Click to collapse
Done it 3493493414 times.

jutopa said:
Code:
E:failed to mount /data (No such file or directory)
E: failed to mount /sdcard (File exists)
E: copy_cache _media: Can't mount /sdcard
your storage not prepared yet,p lese use UI menu for format and reboot actions
E:failed to mount data (Invalid Argument)
Click to expand...
Click to collapse
It looks like that the eMMC is not working, /sdcard and /data are on it.
I don't think the problem is due to the fact that you wrongly flashed the files. As long as you don't mess with bootloaders, things can most of the time be fixed.
It looks like an hardware failure, but I could be wrong. I've no ways to determine it.
Anyway, the eMMC is not the most important memory in our device, you can replace it with the external SD. There are several ways to do it, some users posted their solution here in the forum, this for example.

loSconosciuto said:
It looks like that the eMMC is not working, /sdcard and /data are on it.
I don't think the problem is due to the fact that you wrongly flashed the files. As long as you don't mess with bootloaders, things can most of the time be fixed.
It looks like an hardware failure, but I could be wrong. I've no ways to determine it.
Anyway, the eMMC is not the most important memory in our device, you can replace it with the external SD. There are several ways to do it, some users posted their solution here in the forum, this for example.
Click to expand...
Click to collapse
Yeah, I'm starting to think that.
I will try to swap SDs.
But I have a question. My main problem is that most of ROMS don't boot. Don't know why, but the only ROMs I managed to boot are CM7 and MIUI 2.3 also. Why this? If I try a different rom it gets stuck in bootloop or doesn't even install it at all.
If a swap sd would this limitation of roms will be solved? I mean, this swapping is permanent or it goes away every time I flash a new build????

jutopa said:
Yeah, I'm starting to think that.
I will try to swap SDs.
But I have a question. My main problem is that most of ROMS don't boot. Don't know why, but the only ROMs I managed to boot are CM7 and MIUI 2.3 also. Why this? If I try a different rom it gets stuck in bootloop or doesn't even install it at all.
If a swap sd would this limitation of roms will be solved? I mean, this swapping is permanent or it goes away every time I flash a new build????
Click to expand...
Click to collapse
I can't explain why CM7 is working, there could be several reasons (/cache is inside the OneNAND, it's using your SD card for /data etc...).
The changes for the swap are usually in the kernel ramdisk or /system and both of them are entirerly wiped during ROM updates, so you should do them on every ROM update.

[Q] Cant mount SDcard in CWM recovery

Hi! i have a motorola defy MB525 , and its running Eclair 2.1, so i wanted to flash CM11 , i did everything successfully until the part where you have to flash your ROM ! good thing im cautious and always check the zip. install before wiping any data, and i got the following message when trying to install zip. from sdcard :
E:can't mount /sdcard
because i haven't wiped my data yet, the phone is now working 100%, but i want kitkat not eclair,so can anyone help ??
my clockworkmod version is 2.5.1.8
NOTE: i googled this and found out that sometimes CWM can only read FAT32 file system , but my sdcard is already formatted to FAT32 file system, and if it makes any difference i did format it again to the same file system FAT32 , but i still get the same error!
I REALLY WANT CM11 BECAUSE MY CURRENT ROM IS VERY BAD AND OUTDATED! SO PLEASE HELP!!
Thx

Did anybody found the answer yet?
Im still stuck at the same problem....any help??

Try Flashing The CWM Recovery Again.......
sazzam10 said:
Hi! i have a motorola defy MB525 , and its running Eclair 2.1, so i wanted to flash CM11 , i did everything successfully until the part where you have to flash your ROM ! good thing im cautious and always check the zip. install before wiping any data, and i got the following message when trying to install zip. from sdcard :
E:can't mount /sdcard
because i haven't wiped my data yet, the phone is now working 100%, but i want kitkat not eclair,so can anyone help ??
my clockworkmod version is 2.5.1.8
NOTE: i googled this and found out that sometimes CWM can only read FAT32 file system , but my sdcard is already formatted to FAT32 file system, and if it makes any difference i did format it again to the same file system FAT32 , but i still get the same error!
I REALLY WANT CM11 BECAUSE MY CURRENT ROM IS VERY BAD AND OUTDATED! SO PLEASE HELP!!
Thx
Click to expand...
Click to collapse
i think Your CWM REcovery got corrupted.........
try reflashing the recovery and Try Again.....
say Thanks If this helped You

sazzam10 said:
Hi! i have a motorola defy MB525 , and its running Eclair 2.1, so i wanted to flash CM11 , i did everything successfully until the part where you have to flash your ROM ! good thing im cautious and always check the zip. install before wiping any data, and i got the following message when trying to install zip. from sdcard :
E:can't mount /sdcard
because i haven't wiped my data yet, the phone is now working 100%, but i want kitkat not eclair,so can anyone help ??
my clockworkmod version is 2.5.1.8
NOTE: i googled this and found out that sometimes CWM can only read FAT32 file system , but my sdcard is already formatted to FAT32 file system, and if it makes any difference i did format it again to the same file system FAT32 , but i still get the same error!
I REALLY WANT CM11 BECAUSE MY CURRENT ROM IS VERY BAD AND OUTDATED! SO PLEASE HELP!!
Thx
Click to expand...
Click to collapse
Any luck with that?