Ok so i tried flashing Epic got into a bootloop...so went to stock KF1...ODINed the Cognition kernel with CWM...flashed Fasty II V2.0 onto it...The ROM booted up just fine!
Then I went to Market to Download TiBu..but got a error message saying "Device doesn't have sufficient space blah blah" ...I know this..just need to wipe cache partition and am back up running...but when I boot into Recovery...I get this message:
E: can't open /cache/recovery/command
E: can't open /cache/recovery/log
E: can't open /cache/recovery/log
E: can't open /cache/recovery/last_log
E: can't open /cache/recovery/last_log
And every time I try to wipe cache partition..it just skips the wipe and gives the above error again
Shot a PM to LostLogic...till then anyone else who knows the solution to the problem please help me
How do I remove these errors?
I'm afraid you're just another victim of the "eMMC brick" (otherwise known as "kiss your device goodbye")... Looks to me a lot like what my HTC DS is displaying everytime I boot into recovery. :/
Search for "eMMC brick" on the forums, it's a well-documented issue. But up to now, I was under the impression that only HTC devices were concerned, looks like those ****ty chips are getting mounted on every device these days.. :O
Snakeforhire said:
I'm afraid you're just another victim of the "eMMC brick" (otherwise known as "kiss your device goodbye")... Looks to me a lot like what my HTC DS is displaying everytime I boot into recovery. :/
Search for "eMMC brick" on the forums, it's a well-documented issue. But up to now, I was under the impression that only HTC devices were concerned, looks like those ****ty chips are getting mounted on every device these days.. :O
Click to expand...
Click to collapse
Lol that scared the **** outta me but Anyways I fixed this by :
1) ODINed back to Stock KF1
2) ODINed the Stock KH3 tar file onto it
3) ODINed boog's kernel
4) Installed Fasty II V2.0 using CWM 4.0
Now everything seems to be fine again.
No errors while going into Recovery!
I'm having the same problem on my Sony Ericsson Xperia x10 Mini. Investigating ways of fixing it. I'll post here if I succeed.
Related
Hello all,
I'm having a problem getting my phone to boot up when I tried flashing back to stock with Odin 1.37 using .512 pit and SGH-T959UVKA6. I have done it successfully in the past, but the mistake i made this go round is I accidentally checked "re-partition" and it gets stuck on the following error in Android System Recovery 3e:
update media, please wait
E: Can't mount /dev/block/st110
(invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet. Please use UI menu for format and reboot actions.
copy default media content failed.
Can anyone advise if they have fixed this error in the past? I really need to get this phone back to TMO for under warranty repair and am kind of scared of being screwed here.
Bigbass12 said:
Hello all,
I'm having a problem getting my phone to boot up when I tried flashing back to stock with Odin 1.37 using .512 pit and SGH-T959UVKA6. I have done it successfully in the past, but the mistake i made this go round is I accidentally checked "re-partition" and it gets stuck on the following error in Android System Recovery 3e:
update media, please wait
E: Can't mount /dev/block/st110
(invalid argument)
E: copy_dbdata_media: Can't mount DBDATA:
your storage not prepared yet. Please use UI menu for format and reboot actions.
copy default media content failed.
Can anyone advise if they have fixed this error in the past? I really need to get this phone back to TMO for under warranty repair and am kind of scared of being screwed here.
Click to expand...
Click to collapse
Nothing to big happened. I check repartition every time I never have any problems.
If it shows u anything ur good.
Boot into download mode and odin back again.
Sent from my SGH-T959 using XDA App
Hmm....
I would agree with you except the following:
1. Tried to flash same without checking repartition...failed x3.
2. tried to flash to JI6 with same pit file...failed.
3. tried to change pit file to 513 and tried again with KA6...failed.
4. tried to go back to 512 and JI6...failed.
I have tried several times variants of all those combos...all failed.
Per the following post I am trying this fix:
http://forum.xda-developers.com/showthread.php?t=734475
hopefully going back to JFD will fix this....
****NOTE: When I say "Failed" I mean I get the same message that I got when I first received the error.....
Success
Wow the post really did it! Gotta love XDA...quick someone teach me how to thank around here...lol
I have a GT-I9100M from Bell in Canada. My phone is broke and I've spent the last 24 hours trying to fix it with no avail
I was running the stock ICS rom from Bell. I rooted the phone and removed all the Bell bloatware and that was it.
Yesterday I came across a Rom that had the S3 version of Touchwiz so I decided to try it out - Salman ICS ROM for Galaxy S2 i9100! [TouchWiz UX][S Voice][GS3 ROM]
The rom installed perfectly and when it restarted, it stopped at the Samsung Galaxy boot screen. I attempted to go into recovery mode and it couldn't.
It would go into download mode. So I tried to flash the stock bell ICS rom - I9100MUGLD3_I9100MBMCLD3_BMC_www.samsdroid.com. It flashed with no issues but when it rebooted - back to the boot screen I go.
I flashed a CF kernal so that I could get into CWM and attempt to wipe it. It kept hanging on formatting /data.
I came across this guide - http://forum.xda-developers.com/showthread.php?t=1449771 and followed the steps and got no where.
Is my phone completely dead and if it is not - how do I get it back in working condition?
Help!!:crying:
When you flashed Bell's stock ROM from the guide thread, could you reach the recovery mode screen? I had the same problem and I simply did a factory reset after I flashed the stock ROM.
After I tried to flash my stock firmware with ODIN
I get stuck at Android System Recovery <3e>
and get these errors:
E: failed to mount /cache (no such file or directory)
E: Cant mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Cant open /cache/recovery/recovery_kernel_log
E:failed to mount /efs (No such file or Directory)
E:failed to mount /cache (no such file or directory)
E:cant mount /cache/recovery log
E:cant open /cache/recovery log
and as you can imagine the list goes on..... and when I hit reboot system now - it just freezes at the Samsung i9100 boot screen.
AAARRGGG
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
kmacsouris said:
I did some more reading and someone suggested trying a Frankenstein rom KK5 as it does a complete wipe of the data partition on the phone. When I tried this, it does stuck on datafs.
I believe that my phone is broken
Click to expand...
Click to collapse
looks like you have hit the eMMC brick, you could try to flash a pit file, and flashing it with repartition activated... This its the only thing you could try, before sending it off for repair
Best regards
Sendt fra min GT-I9300 med Tapatalk2
try to find a Stock ICS which does a full wipe. Usually the first edition of stock ICS
of each region does that.
Dear friend i understand your fear and i wan t to share with you my research, my trouble came for downgrading from ics to GB and now i have the red letters with the e cant mount **** , so i found that installing this rom (XXKH3) with the Phone Bootloader Update filed checked could fix it.
The original post is in spanish so if you need it it is here.
Scroll down until ERROR: E: Can't mount cache
http://www.taringa.net/posts/celulares/14623579/samsung-galaxy-S2---downgrade-ICS-a-Gingerbread.html
But on this post the link to XXKH3 is broken so i found this other link on english with the link working
http://www.theandroidsoul.com/how-to-install-xxkh3-on-samsung-galaxy-s-2-ii-i9100/
I'll try this thing in a couple hours when the download finish due to my 1.5 mb internet and i'll let you know any new,
Good luck
I recently tried to flash a Htc Wildfire S rom which was HenseMod7 on my phone by mistake. Now I get the same errors when I boot into recovery.
E:Can't find MISC:
E:Can't find PERSIST:
E: Can't mount CACHE:recovery/command
It wont let me restore either...
When I tired to go into emergency mode I got stuck on the downloading screen.
Can someone guide me through this process honestly i have no idea what im supposed to do.
i think ther is sme error with the root filesystem. it might hav happnd while u flashd the htc rom. flashing the lg original firmware using kdz may solve this.
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
imfukked said:
I recently upgraded phones and I'm looking to sell my old gs3. But I had put a costom Rom on it awhile back but during the process at one point I ran into the same problem with the logo screen but I fixed it (I completely forget how) and that was that untill recently when I attempted to return the phone to stock by updating it to 4.3 with kies and that was fine it wasn't until I ran a master reboot that the logo problem resurfaced at that point I tryed to use Odin to flash stock firmware which after doing further research was a terrible idea to do with 4.3 but that's where I'm at my phone does not boot up past the Samsung logo luckily I can still access the dowload mode. I am thinking that I'm going to try flashing a root66 stock 4.3 is that a good idea. Any help would be much appreciated, thank you
Update:I tryed flashing the root 66. I did the newest 4.3 tmobile download i could find which is what fixed it when this happened about a year ago but this time it did nothing. Also when i boot into recovery mode at the bottom under where it says Seccessfully applied multi-CSC it says in red lettering
E:failed to mount /data (Invalid argumen
t)
can't mount '/data'(invalid argument)
E:failed to mount /data (Invalid argumen
t)
E:Can't mount /data/log/recovery_log.txt
Click to expand...
Click to collapse
Hmm . Did you have the device encrypted or anything along those lines?
I'm good dude. I figured it out.
imfukked said:
I'm good dude. I figured it out.
Click to expand...
Click to collapse
Good deal. Care to share in case others run across this issue?
stuck booting at logo screen
hello, my s3 did the same thing keis wouldnt even recognize my phone after rooting and trying to go back to stock rom, found when installing using odin, i installed tar file in boot img i had to download a zip unpack it and istalled kernal tar and bingo solved my problem, hope it helped..
Hello,
Yesterday I unlocked my Galaxy S3 i9300, turned the Wifi on and soon after that my phone started to reboot.
This happened a few times before, but this time it got stuck on the "Galaxy S3" Screen.
So I booted in the Recovery Mode (TWRP 3.1.10) and was planning to wipe the cache partition, but I got the Error that the Recovery is unable to mount Any Partition..
So I cant do anything.
I wanted to ask, why my phone can not mount any Partitions anymore for example (system, efs, cache..).
What exatly is damaged and is it repairable?
I took a picture of the Error Message, but i dont know how to upload it. So I wrote it down.
Hope someone can help me and sorry for my bad english.
Kind Regards.
Error Message:
Updating partition details...
Failed to mount ´/efs´(invalid argument)
Failed to mount ´/cache`(invalid argument)
Failed to mount ´/system´(Invalid argmunent)
Failed to mount ´/data´(Invalid argmunent)
Failed to mount ´/preload´(Invalid argmunent)
Flash stock rom via Odin. Root it and try again.
ArdaCsknn said:
Flash stock rom via Odin. Root it and try again.
Click to expand...
Click to collapse
I am facing same errors. in these type of error i can't flash with odin, can't hard reset, can't install any recovery, i have tried many roms but all failed. i was thinking about to re-partition it but there is a file required for this .pit file. i have searched on google but i didn't find any .pit file for my Samsung S3 SHV-E210k. i have asked in thread but no response from anyone. so i am thinking to threw my phone away. :crying: :crying: :crying:
E30325i said:
Hello,
Yesterday I unlocked my Galaxy S3 i9300, turned the Wifi on and soon after that my phone started to reboot.
This happened a few times before, but this time it got stuck on the "Galaxy S3" Screen.
So I booted in the Recovery Mode (TWRP 3.1.10) and was planning to wipe the cache partition, but I got the Error that the Recovery is unable to mount Any Partition..
So I cant do anything.
I wanted to ask, why my phone can not mount any Partitions anymore for example (system, efs, cache..).
What exatly is damaged and is it repairable?
I took a picture of the Error Message, but i dont know how to upload it. So I wrote it down.
Hope someone can help me and sorry for my bad english.
Kind Regards.
Error Message:
Updating partition details...
Failed to mount ´/efs´(invalid argument)
Failed to mount ´/cache`(invalid argument)
Failed to mount ´/system´(Invalid argmunent)
Failed to mount ´/data´(Invalid argmunent)
Failed to mount ´/preload´(Invalid argmunent)
Click to expand...
Click to collapse
Try to find .pit file and flash it with odin. and then flash your stock rom.
My phone's model is SHV-E210K, i have searched on google but haven't found any .pit file related to my phone.
The sboot.bin file is the bootloader and it is not flashing because the bootloader in the phone is newer than than the bootloader in the ROM, the ROM is not for the phone, try a different USB cable, and/or try different USB ports.
The problem is recovery has gone crazy. Recovery mounts partitions. I've seen this problem a lot with twrp. When it happened to me I flashed the latest official cwmr via Odin. If you have a stock rom on the phone you can flash a stock recovery too. DO NOT FLASH A STOCK RECOVERY IF YOUR ROM ISN'T STOCK/ROOTED STOCK!!!
Beamed in by telepathy