Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
you need to get into recovery via the power menu...depending on what kernel version your running, three fingering into recovery will cause a bootloop. the same thing applies to all ICS roms. If you can no longer get the phone to boot up then simply odin cwm4 fixed for cm7, three finger into recovery, wipe data, then reflash the rom. Make sure everything is backed up first. More information can be found in section 3 here:
http://forum.xda-developers.com/showthread.php?t=1238070
Thanks for your reply. I explained that the phone doesn't boot up anymore (gets stuck in a loop), and while booting into ClockworkMod works (3 fingers), I get these errors, so even though the up/down/power buttons work (I can scroll through the recovery menus/options), certain things don't work, like wiping the cache (it cannot mount or open the cache) or re-flashing CM7 from SD-card... I get errors.
I've had problems with Odin before (it said it flashed stuff, but stuff didn't work), so I've been using Heimdall for a while instead. Like I said, I was able to successfully re-upload ClockworkMod to the phone (in d/l mode) with Heimdall, but it doesn't fix the problem. The problem seems to be that the cache partition is corrupted, and I can't do much from within ClockworkMod (though it worked without problems in the past).
I've found tips on here (http://forum.xda-developers.com/showthread.php?t=1284196) that the errors I get are sometimes (though not always) because of physical corruption of eMMC. Is it possible to flash CM7 or CM9 using Heimdall or (Heimdall-frontend), are there instructions on this, though I doubt it will work...I'm new to this lol. I want to at least have a working phone, until I can figure out how to fix the cache problem and make Clockworkmod work again. Thanks.
Is it possible to just fix the cache partition or re-partition using a program like Heimdall?
bollorr said:
Hi guys,
I'm afraid my emmc is fried. After occasional crashes/freezes/FC's in different apps/Android modules in CM7 over a few months, one day I opened this site in the browser, and the browser FC'ed and then kept FC'ing when opened. When rebooting, the phone gets stuck looping in the CM7 animated start-up logo. When I boot in Clockworkmod (v4.0.1.0) , I get this error:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
and I can't use Clockworkmod. Cannot mount/wipe cache, cannot install anything. I tried checking the eMMC with ADB and FASTBOOT, but they can't see the device, though Heimdall does see it as I was able to flash recovery.bin again in d/l mode (but without fixing the problem). Please help, I've run out of ideas and have no phone...
Click to expand...
Click to collapse
i have the exact same problem with my fascinate i would think that if i could get odin to flash a new rom to it it would boot but im not intirely sure
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
bollorr said:
I've found others who have the same problem... in my opinion it's clear that the cache partition got corrupted for some reason, either software (fixable) or hardware (the internal memory/eMMC which then it would need replacement or a new phone lol).
Click to expand...
Click to collapse
you need to flash back to a stock rom via odin, heimdall, or adb...thats the only way to fix it at this point. if you can get odin to recognize the device try section 5 of my guide.
Thanks. I'll give it a try. Odin doesn't see my device, so I'm using Heimdall Frontend which is a little bit different. Do you have instructions for it? I load atlas.pit, but then in order to load the GB rom (which is .tar.md5), it asks for a BIN file, and I also have to add a partition and it's got a lot of options there. Why doesn't Odin see my device, but Heimdall does?
I got Odin to recognize my device (stupid USB ports), I followed the instructions, phone says downloading, do not turn off target, Odin says the same... it's been more than 5 minutes, the same...does it mean I have a bricked device now?
and I forgot, Odin says in top left corner, SET PARTITION...it's been 15 minutes now, maybe it cannot set the partition
Update...I rebooted the phone into Recovery after 20 mins or so of Odin not being able to flash (set partition)... of course Odin detected it and a big red FAIL appeared in the top left corner, and the bottom log said Re-partition operation failed, so, is there anything else I can try or the memory chip fried?
http://rootzwiki.com/topic/8867-romsch-i500-vzw-ed05-froyo-heimdall-linux-friendly/
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Is Re-Partition checked in Odin? If it is, try unchecking it. If it isn't, try checking it. If it's unchecked, it won't fix the corrupted cache partition, but it should at least let you flash the OS
yes, I tried that in odin, doesn't work
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
bollorr said:
Thanks, I tried what you said, and just like I thought, Heimdall (like Odin) gave this error:
Uploading PIT
ERROR: Failed to send file part packet!
PIT upload failed!
Ending session...
ERROR: Failed to send end session packet!
please help, I have no phone
Click to expand...
Click to collapse
your last option is to try adb.
MultipleMonomials said:
Yikes. You seem to be stuck between a rock and a hard place. Honestly, it seems that the only possible option here is to get a new phone. It seems as though there must be physical damage to the chip, otherwise Odin/Heimdall would have worked.
Click to expand...
Click to collapse
that's usually the diagnostic (fried eMMC chip) for these error messages (though not always) and that's what I thought, and I was looking for ways to determine for sure whether the chip is fried or not, as to know what to do and not waste my time and the time of the people on this board...for some reason adb doesn't work, or I don't know how to use it (first time using it)...I type adb devices, I get error, no devices, adb shell, error again
droidstyle,
do you have instructions anywhere on how to use adb, it was one of the first things I tried, but it doesn't see the devices, I cannot start shell (adb shell)...thanks
I made an ADB for Noobs guide about a year ago. It never gained much traction but it should still be current. Anywhere it says CM7, the same goes for CM9.
Related
Ok, so start I took my SGS2 i777 with Shostock3 and tried to enable encryption on it. Should've been a simple click of a box and a reboot, right? The battery was charged and I had it connected to a cable. I hit start, it rebooted a few times, I entered my password halfway through, and woke up to it asking for my password as if everything was complete. I entered the password, then it loaded to the initial start screen and asked me to input all my google account info (even though I'd done this months ago). As soon as I'd hit start it would reboot the phone and I'd be back at the screen asking for my encryption password.
So I deleted all user data to see if that would help and then it wouldn't accept any password. Then I tried reflashing through recovery and adb but I always got the error that it couldn't mount /sdcard and /emmc. This seems to be the root of the problem. No matter what guide I follow, I can't access these. I can't format them either using CWM.
I recently followed guide titled: "Prepare Your Phone to Return to the Store or for Warranty Replacement by following these steps:"
and I get the following error when I enter the heimdall flash command.
(heimdall flash --kernel zImage --factoryfs factoryfs.img --cache cache.img --hidden hidden.img --modem modem.bin?)
Popup window saying Unable to mount the MTP device (although it shows up in my computer on linux mint)
"ERROR: Partition "kernel" does not exist in the specified PIT.
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
"
After having previous issues, I tried flashing the PIT using the --pit command in heimdall, under the assumption that the encryption ruined the formatting.
Summary:
So right now I can get into recovery and download modes through CWM but nothing I do has any effect. I've put new .zip files on sd cards and it doesn't work, .zip files through adb won't work, and heimdall is giving me these issues.
Any other ideas? I know since I can get into download mode that it shouldn't be that hard to fix, but I can't find out what to do right now.
If you can, I would suggest you use a windows computer with Odin to flash back to stock.
I know very little about encryption except that it seems to be loaded into a partition that is not changed by flashing or wiping.
While booting into recovery and trying to flash a new radio on pa 4.5 I ran into an error message in recovery that said E:Unable to mount '/cache'.
I tried to flash various different ROMs and even a different recovery but I still ended up getting the same message that it was unable to mount cache. I tried to manually mount cache in TWRP but it wouldn't let me, finally I tried a factory reset but that failed as well with the same error message.
Next I tried to go into fastboot and flash a new recovery, but I got an error message saying "FAILED <remote flash write failure>". I then tried to format cache through fastboot but that failed as well.
Lastly I tried LGNPST in order to return to stock but I got an error at 85% in LGNPST and still got it even though I tried on 3 different computers running both Windows 7 & 8.
I have contacted LG and they told me to mail the phone in for repairs, is that my only option now, or is there an other way to fix this and not have to pay LG to do it?
Thanks in advance to anyone that can help me sort this out.
Same problem here
Same situation here any solution plz help me
OK, so first, My padfone S automatically reboot and stuck on asus logo for a while, then after exhaustively waited , i manually hit power button for 30 second and it reboot but, still stuck on the asus logo. At this time i try to enter the recovery mode and try to wipe cache wipe /cache partition. It gives a bunch of can't mount error line. But still there's one line saying wipe completed. Then i try to wipe everything, and same error can't mount but still wipe completed was shown. At this time i was so stressed i try to follow the recommendation which posted http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818 ..
I skipped to the part where i enter fastboot and open up adb tools to flash TWRP_2.8.7.0 to unlock bootloader. Before this, I try using adb devices command line but, my devices was not shown. So after i flashing TWRP as mentioned, it show exactly what Ninekaw has said, [ It will show that flashing FAILED (remote: can't flash unsigned image), it fact, it was succeeded, ] .. Then when i try to enter the recovery mode as for the next step, It stuck on the Asus logo. Now i can't even enter to recovery mode, my adb tools can't detected my devices. I don't know what to do. Please oh please merciful android race. HELP ME. I'm a noob to this kind of technology.
Oh.. the error command line in recovery mode
and the error command line was,
E: can't mount, change path -dev/lock/emmcblk1
E: can't mount /cache partition
E: can't mount /cache/recovery/log
E: can't mount /cache/recovery/log1
E: can't mount /cache/bootloader
E: can't mount /cache/bootloader1
Seriously?
Seriously guys? no help at all? man, i'm disappointed after all the website i go through mention to go consult in this website.. maybe the community here wasn't as good others pictured it would..
Hi, I was running leedroid m9 rooted s-off with twrp and it was working great until I had some bizarre out of nowhere system app crashes earlier tonight (I guess yesterday by now). Commence boot loop. At first I was unable to access recovery and was just met with another shorter boot loop. I was eventually able to get into recovery through the bootloader menu but with a glaring fault. It gave me the prompt as if it was the first time booting into twrp, asking if I wanted to leave the partitions in read only mode. I thought "well kinda weird but ok". Then I try to restore my last post install image. It starts out with something about being unable to mount data or find the crypto header, and then it's nothing but "failed to mount x (invalid argument)". Same result for everything. Wipe, failed, adb sideload, failed, even manually attempting to mount in terminal failed (invalid argument). We even tried just completely opening up permissions (I know, very bad move for security but we were at our wits end). Unable to detect the phone via RUU or ADB in any state I can get it to boot to. I imagine something going on with encryption is to blame here? But I don't recall opting for or setting up any encryption?
Basically, is this phone beyond hope? Is there anything magical I can do through the bootloader (also not detected by adb)?
Also, looking in terminal in twrp, I'm still a root user? Don't know if that helps shed a light on this.
Hello, today I was trying to restart my phone after it was updating an app from the google play store for several hours and since then it gets stuck on the Samsung Galaxy Note 8 logo. My phone is rooted and has TWRP installed.
I still can enter TWRP recovery mode but literally everything I can do there fails. I get the "unable to mount storage" message whenever I try to wipe or format something and it is showing 0MB for all partitions.
I tried flashing the stock firmware using adb sideload but I am still just getting unable to mount storage/cache/data messages after a second. I also tried flashing the .zip file through USB OTG cable but got the same result.
When I tried flashing the file with JOdin3 (Odin for Linux) I got this message: "A corrupted file was detected. In order to continue, you must select a valid Odin File" (Still got this message after I redownloaded the file)
If anyone has any suggestions, please leave a comment.
Edit: Tried flashing with Heimdall and it somewhat worked but if I boot my phone now I get "fail to open recovery cause no such file or directory" error for a split second and then it reboots...
Please can anyone help me?