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.
My wife has a stock, unrooted, developer options off Asus MemoPad FHD 10 (ME302C) that is stuck on the Asus logo. I am able to get into the bootloader which says:
IFWI VERSION: 51.33
SERIAL_NUM: 1111111111111111
DROIDBOOT VERSION: Local Build or ENG version
PRODUCT: US_EPAD
At the bottom it has:
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we skip check debricking
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we skip check debricking
FASTBOOT INIT...
FASTBOOT CMD WAITING...
I have attempted to do the Factory Reset and it says:
E:failed to mount /cache (Invalid argument)
E: Unable to mount /cache! we reformat now!
At this point the green progress bar pops up but stops moving and it will stay like this until the battery dies.
I have attempted "Fastboot -w" which results in it beginning to erase the user data with the progress bar moving properly but again it will stay like this until the battery dies and fastboot reports that it fails due to too many links.
I have attempted to flash recovery, and boot both ending in send ok write failed. Hopefully someone here may know what to do next.
Same problem, a next step to solve 31122014
Hello, I have the same Problem with this ASUS tablet. There is a different product type, instead of US_EPAD it shows me WW_EPAD.
One next step I found to solve the problem is, that the tablet need a connection to the Internet. In the middle of the screen there are read "No USB cable connected!. Link the tablet to the net and it is changing to "Ready for download".
I am not further which download is it, but maybe someone can tell here? Please!
Problem solved, but it takes to replace motherboard
Pierre again.
I sent tablet to ASUS-Repair in Europe. They checked functions and tried different Software updates. At the end there are no success by repairing or trying things. They changed Motherboard and the issue was solved.
Bye, Pierre
My tablet is the same IFMI VERSION: 51.33 US_EPAD the only way I fixed it was download newest firmware off ASUS support and used fastboot.exe to flash it to my tablet. Good as new. 1. fastboot -w 2.fastboot flash update <update.zip> The second on on my machine looked like this.
fastboot flash update US_ME302C-V5.0.21-0-ota-user.zip The tablet won't work if you try to flash an image older than what you had.
Hello and thank you for your help. I currently have a Samsung Galaxy J7 1st generation. The model number is SM-j727VPP.
I cannot root the phone, because no matter what I've tried the option for unlocking the bootloader will not work (I've tried every method) but the USB debugging option is available.
At some point I believed my phone had some kind of malware or rogue OS installed on it (since there is absolutely no security doing a hard installation (holding volume down, power, and home keys). Basically anybody who had access to my phone when I wasn't there could have installed some OS or malware using the download function since there is no security (i've heard the Galaxy S requires password or other validation to use hard reset/download functions.
At any rate, this is the phone I have and I want to root the phone with a custom OS to get rid of all the bloatware and use it as a Wifi phone (using a different phone as my primary phone).
So I've tried flashing with Odin, with no success and for a year now have been unable to root the phone and tried probably 10 times by now. The unlock bootloader does NOT appear in the developer options no matter what I do. Only the USB debugging options are available.
Also, if I try to do a system repair using the Samsung Verizon software repair tool it downloads the software, reboots the phone into download mode then has the following error: unsupport dev_type, and freezes at 83%.
If I hard reset the phone (holding volume up, home, and power keys it has some kind of error and displays the following messages:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
So basically, what I'm asking help with is to either (a) please help me find a way to root this device and put a custom OS on it to get rid of the bloat ware and/or (b) help me use the Samsung repair tool and get rid of the unsupport dev_type as well as these errors when I hard reset the phone:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
Thank you. ANY information and advice would be greatly appreciated.
Try This
user1003 said:
Hello and thank you for your help. I currently have a Samsung Galaxy J7 1st generation. The model number is SM-j727VPP.
I cannot root the phone, because no matter what I've tried the option for unlocking the bootloader will not work (I've tried every method) but the USB debugging option is available.
At some point I believed my phone had some kind of malware or rogue OS installed on it (since there is absolutely no security doing a hard installation (holding volume down, power, and home keys). Basically anybody who had access to my phone when I wasn't there could have installed some OS or malware using the download function since there is no security (i've heard the Galaxy S requires password or other validation to use hard reset/download functions.
At any rate, this is the phone I have and I want to root the phone with a custom OS to get rid of all the bloatware and use it as a Wifi phone (using a different phone as my primary phone).
So I've tried flashing with Odin, with no success and for a year now have been unable to root the phone and tried probably 10 times by now. The unlock bootloader does NOT appear in the developer options no matter what I do. Only the USB debugging options are available.
Also, if I try to do a system repair using the Samsung Verizon software repair tool it downloads the software, reboots the phone into download mode then has the following error: unsupport dev_type, and freezes at 83%.
If I hard reset the phone (holding volume up, home, and power keys it has some kind of error and displays the following messages:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
So basically, what I'm asking help with is to either (a) please help me find a way to root this device and put a custom OS on it to get rid of the bloat ware and/or (b) help me use the Samsung repair tool and get rid of the unsupport dev_type as well as these errors when I hard reset the phone:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
Thank you. ANY information and advice would be greatly appreciated.
Click to expand...
Click to collapse
Hi there,
Just a quick question are you able to boot into the device, like the home screen.
Sincerely
KIBS2173
KIBS2173 said:
Hi there,
Just a quick question are you able to boot into the device, like the home screen.
Sincerely
KIBS2173
Click to expand...
Click to collapse
Yes. I can boot the device and get into Android. However there is an app running called LLK agent and a user certificate called com.samsung.android.dqagent_SA_SDK that autamatically keeps reinstalling itself. There is also an app called SVC agent and BBC agent. None of them can be removed.
user1003 said:
Hello and thank you for your help. I currently have a Samsung Galaxy J7 1st generation. The model number is SM-j727VPP.
I cannot root the phone, because no matter what I've tried the option for unlocking the bootloader will not work (I've tried every method) but the USB debugging option is available.
At some point I believed my phone had some kind of malware or rogue OS installed on it (since there is absolutely no security doing a hard installation (holding volume down, power, and home keys). Basically anybody who had access to my phone when I wasn't there could have installed some OS or malware using the download function since there is no security (i've heard the Galaxy S requires password or other validation to use hard reset/download functions.
At any rate, this is the phone I have and I want to root the phone with a custom OS to get rid of all the bloatware and use it as a Wifi phone (using a different phone as my primary phone).
So I've tried flashing with Odin, with no success and for a year now have been unable to root the phone and tried probably 10 times by now. The unlock bootloader does NOT appear in the developer options no matter what I do. Only the USB debugging options are available.
Also, if I try to do a system repair using the Samsung Verizon software repair tool it downloads the software, reboots the phone into download mode then has the following error: unsupport dev_type, and freezes at 83%.
If I hard reset the phone (holding volume up, home, and power keys it has some kind of error and displays the following messages:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
So basically, what I'm asking help with is to either (a) please help me find a way to root this device and put a custom OS on it to get rid of the bloat ware and/or (b) help me use the Samsung repair tool and get rid of the unsupport dev_type as well as these errors when I hard reset the phone:
E: unknown volume for path [/vendor]
E: [libfs_mgr]Error loading verity table: invalid argument
E: unkown volume for path [/odm]
E: unkown volume for path [/vendor]
remove failed dir '/system/carrier/ATT/priv-app/AttIqi_ATT' (No such file or directory)
E: [libfs_mgr]Error fetching verity device number: No such device address
E:[libfs_mgr]Couldn't get verity device number!
E:[libfs_mgr]Error removing device mapping: No such device or address
Thank you. ANY information and advice would be greatly appreciated.
Click to expand...
Click to collapse
Make sure its a official device!
DankMemz said:
Make sure its a official device!
Click to expand...
Click to collapse
It is official. When I check the phone status it says Official.
user1003 said:
It is official. When I check the phone status it says Official.
Click to expand...
Click to collapse
Try reinstalling the Samsung drivers