Related
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.
Hello,
i messup with my phone in twpr , while i try to fix ..
my problem is i try to fix by kies , and when pass true
it was no boot up, its stuck on samsung logo , with flasing blu light, even i turn to download mode , or go to orginal recovery ,
in recowery i have that message...
LMY47X.G925FXXU3QOLO
e : failed to mount /efs (invalid argument)
e : failed to mount /efs (invalid argument)
dm-verity verification failed...
also i reset all my phone try to fix and i dont have anything in my phone,
i have a backup on my laptop after first root , but i cant but the phone to put in ,
or try adb but don conect with my phone to?
pleas help mee!!
Sorry for my english,
andriellka said:
Hello,
i messup with my phone in twpr , while i try to fix ..
my problem is i try to fix by kies , and when pass true
it was no boot up, its stuck on samsung logo , with flasing blu light, even i turn to download mode , or go to orginal recovery ,
in recowery i have that message...
LMY47X.G925FXXU3QOLO
e : failed to mount /efs (invalid argument)
e : failed to mount /efs (invalid argument)
dm-verity verification failed...
also i reset all my phone try to fix and i dont have anything in my phone,
i have a backup on my laptop after first root , but i cant but the phone to put in ,
or try adb but don conect with my phone to?
pleas help mee!!
Sorry for my english,
Click to expand...
Click to collapse
use smart switch from smasung to flash your phone or download a firmware from sammobile and flash it....u will do good....
success123 said:
use smart switch from smasung to flash your phone or download a firmware from sammobile and flash it....u will do good....
Click to expand...
Click to collapse
Thanks for replay me,
I did few times went go to the pass message but is steel boot only on samsung logo , i did with odin and did with smart swich , same thing.??
Looks like you wiped your EFS partition. If this is true and you have no backup, just give up immediately and bring it to a Samsung store for repairs.
Zulake said:
Looks like you wiped your EFS partition. If this is true and you have no backup, just give up immediately and bring it to a Samsung store for repairs.
Click to expand...
Click to collapse
I have backup , on pc and thats is the problem, i cat push in to the phone
andriellka said:
I have backup , on pc and thats is the problem, i cat push in to the phone
Click to expand...
Click to collapse
Restore the EFS partition from backup then.
You can push it through ADB commands.
For example: adb push efs.md5 /sdcard/TWRP/backup puts the file called efs.md5 at TWRP/backup on your sdcard. Make sure that file (the backup) is in the same folder as ADB. Then just push it all over and you should be able to restore it from TWRP.
Zulake said:
Restore the EFS partition from backup then.
You can push it through ADB commands.
For example: adb push efs.md5 /sdcard/TWRP/backup puts the file called efs.md5 at TWRP/backup on your sdcard. Make sure that file (the backup) is in the same folder as ADB. Then just push it all over and you should be able to restore it from TWRP.
Click to expand...
Click to collapse
Another thing is i try that, but i cant conect with adb , it dont see my phone, kies and odin do
andriellka said:
Another thing is i try that, but i cant conect with adb , it dont see my phone, kies and odin do
Click to expand...
Click to collapse
And i have in stock firmware and cant flash twpr, meaby am doing wrong,,
With ADB you can't see your Phone...
Test this...adb devices
Meskalin1983 said:
With ADB you can't see your Phone...
Test this...adb devices
Click to expand...
Click to collapse
You need to reflash TWRP. You could try a OTG lead to drop back up from computer onto USB and then connect to phone through OTG in recovery and restore. Had to use this method myself. Hope it works out
Chrisaa63 said:
You need to reflash TWRP. You could try a OTG lead to drop back up from computer onto USB and then connect to phone through OTG in recovery and restore. Had to use this method myself. Hope it works out
Click to expand...
Click to collapse
Thank you for all your help , i will try that but am not sure what is OTG lead, so i will check it before i will try,, but i try to reflash twpr and nothing pass by odin i try few version, and cant flash in, do i neet to do something more am on 5.1.1 andriod PDA- OLO,
Hi, i clean my laptop reinstal adb drivers ,samsung drivers , smart sweitch and try to flash TWPR, realise i need to flas first bootloader so i did , and then i flas TWPR , and then i could go to TWPR , i use OtG to copy full backup to my phone to twpr file, first recower just efs part and then full backup.
And my phone is live again,
Thank you so much , thats because that forum, i could reed all that and have idea , and especialy to Chrissa63. .
Thank you thank youuuuuuuuuuuuu,,,,,,,
Hello again, since that fix i spotted , i have a memory problem, my data is around 28 gb, i clean ,factory reset and steel same, i thin i over write some data while i try to fix the phone, is any chance how i can fix it?
Pleas Help
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.
I have a Samsung S3 Intl. (i9300) which does not boot anymore. When I entered the recovery mode I got a lot of error messages (unable to mount ...). But as the phone has still the stock recovery I cannot connect with ADB. So I started it in download mode to boot/flash a custom recovery mode. While fastboot never detected the phone Odin and Heimdall did. But when I tried to flash the recovery mode with Odin or Heimdall I got error messages that the PIT is broken.
What do I want?
Primary Objective: Recover the Data
Secundary Objective: Repair the Phone
So is there any way to dump the internal memory of the phone while having it connected to a PC in download mode?
If I would have a large file with a broken partition table and broken filesystems I would know my way around.
DiskDumper said:
I have a Samsung S3 Intl. (i9300) which does not boot anymore. When I entered the recovery mode I got a lot of error messages (unable to mount ...). But as the phone has still the stock recovery I cannot connect with ADB. So I started it in download mode to boot/flash a custom recovery mode. While fastboot never detected the phone Odin and Heimdall did. But when I tried to flash the recovery mode with Odin or Heimdall I got error messages that the PIT is broken.
What do I want?
Primary Objective: Recover the Data
Secundary Objective: Repair the Phone
So is there any way to dump the internal memory of the phone while having it connected to a PC in download mode?
If I would have a large file with a broken partition table and broken filesystems I would know my way around.
Click to expand...
Click to collapse
Recovering the data is a lost cause at this point.
It sounds like the partition setup is screwed. You would have to find a way to repatriation everything back the way it was.
If the device is encrypted that will also cause it not to be able to read the partitions (or so I have read as I don't use encryption)
zelendel said:
It sounds like the partition setup is screwed. You would have to find a way to repatriation everything back the way it was.
If the device is encrypted that will also cause it not to be able to read the partitions (or so I have read as I don't use encryption)
Click to expand...
Click to collapse
Well yeah, but as it had a stock rom and was probably not encrypted (Android 4.3) it might be possible the recover some files (I have done things like that in the past). Maybe the /data filesystem is okay and the partition table is just broken.
But without having the data at all I can't even try to recover the files.
heyo, i'm new here, i don't even know if i'm in the right place but welp..
the thing is that i need help
i have a huawei p6 ascend, the screen was failing and one day it just died and revived few days ago
but it's a bootloop, so i was going to factory reset and then boom, failed to mount /cache /data (invalid argument), so wipe data and cache show a big FAIL, and can't install a rom, still fails
i know this problem is common and probably here in the forum but i really need help, things that i tried didn't work
i tried some things, like adb to try to install TWRP (it seems that it could help) but usb debugging is disabled so adb won't detect my device, tried to install rom through "dload" pressing volume + and volume - but nothing, it takes me to the recovery menu soo... :/ and then i tried the huawei miracle box, but ehm, my main pc detected virus and then i used a "disposable" pc but it didn't open
any suggestions? thanks