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.
Related
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.
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
when switching through windows inside Recovery or trying to wipe cache i get
E: Can't mount /dev/block/mmcblk0p36
(File exists)
E: Can't mount CACHE:recovery/log
E: Can't open CACHE:recovery/log
E: Can't mount /dev/block/mmcblk0p36
(File exists)
im allways rooted/S-OFF
Recovery is Amon Ra 3.15
Ive tried to reflash the Latest RUU. and itll boot and i can use the stock rom but i usually use custom rom
but flashing the latest RUU didnt solve my problam
I am currently formatting my Internal_Sd and mt Sd card to Fat32 right now
ok im stuck on booting after nandroid restore
someone please help!
Stuck where? I would try flashing the kernel for the ROM in the nand and see if that does it.
Also, I've read conflicting info about whether you can restore a nand that was made before updating firmware with an RUU. If any resident experts can comment on this I'd appreciate it as I was going to post a thread asking this.
Did the RUU update yours or was it already running the same firmware?
Also, you were able to boot when on the RUU or no? If yes, you might just flash a ROM fresh rather than restore a nand.
feralicious said:
Stuck where? I would try flashing the kernel for the ROM in the nand and see if that does it.
If not, then give a little history on what you had on before your troubles and what you're trying to get back to, etc...
Click to expand...
Click to collapse
i fallowed this http://forum.xda-developers.com/showthread.php?t=1615969&page=3
im not getting the error inside the recovery anymore. im about to try a nandroid restore
Boot was completely successful. everything is fixed
(thread closed)
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..
Hi everyone, im having troubles trying to flash a rom on TWRP 2.6.0.1 when i try to flash any zip got this error>>> E: cant mount 'system'.
Also in the mount option dont allows me to choose (system).
I never hadn't had this problem before, now i cant just flash anything, some help will be very appreciated , thanks.
I was forced to flash stock zv4 to unbrik my phone, so im stuck on stock :'(