Now the usual way we know we have an eMMC problem is that we get:
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
appearing as a debug message, this is actually the full “cache” partition being corrupted. Obviously the majority of rom chefs have run into this problem many times and myself included I have seen that message on more than one occasion over different handsets.
Usually there isn’t a fix for any error like that, once the cache partition is corrupted you really cannot recover from that, it is a catastrophic failure. The only way I have been able to fix this a couple of times and that was by immediately removing the battery and letting it sit for a couple of minutes before putting the battery back in.
Then if you boot directly into the boot loader and hit into recovery mode.
Now if you haven’t received any major errors you cahce partition should now be formatted as ext3, so if you cycle through the menus and format it to ext4.
Do a full wipe of everything, including factory reset, davlik cache and battery stats
Flash the rom of your choice again (now make sure it is the correct rom for the phone) and hope for the best that it works.
Now hopefully that potentially can resolve your problems, if not then you will probably have a serious eMMC problem and potentially will have bricked your phone.
I will say this method has worked 9 out of 10 times with me and I still have these notes saved for the next time it occurs.
Key things to remember, always track changes in the rom – see if there is a good user base and check them against other more popular roms to see the differences and benefits if there are any.
I take no credits for this, all credits goes to unknown
I'll keep this in mind if mine ever goes bad.
Though, I do have to say though my first reaction to noticing a bad EMMC chip is to try restarting. I can't imagine myself seeing it, doing a battery pull, then seeing what the deal is. I'm less prepared than you I guess haha
I can say this didn't work me at all. I had that exact failure before last year, pulled the battery an let it sit, didn't do a single thing. Not for me at least.
I also highly doubt a battery pull will fix a busted emmc, just doesn't seem correct in my eyes.
If I helped, give thanks, if you please.
........Death before dishonor........
Team inferno
Leader
Hate to be "The Guy"..but...
i hate to be "the party pooper" or "that one guy"... but did you read my whole thread carefully?
saranhai said:
A: there are two things that cause this. both have VERY similar symptoms. the first is because of the failed eMMC chip (refer to eMMC chip section), and the second is because the recovery got messed up, probably because you've been switching between a lot of EXT3 and EXT4 roms.
Click to expand...
Click to collapse
the issue that your OP fixes is the corrupted recovery.. that can easily be fixed by flashing a new recovery. as of now, there is no known way to fix the failed eMMC issue, unless you switch out the whole board. eMMC chip is hardware, not software related. sorry to be "that guy" once again...
however, i do appreciate you trying. most people just give up...
yea... what ^ that guy.. said
saranhai said:
i hate to be "the party pooper" or "that one guy"... but did you read my whole thread carefully?
Click to expand...
Click to collapse
No, of course he didn't.
Related
I have spent a couple of days in hell and would now like to share my experience as a big thank you to the XDA community. However, I am fairly noobish when it comes to Android so if you feel that this does not help, please feel free to delete this entry.
It all began when I restarted my G Tablet and got lots of popus about various applications, including acore, failing. I thought that this was due to me screwing up the system in some way after more or less having followed r34p3rex's superb guide here: http://forum.xda-developers.com/showthread.php?t=827209.
Ignoring this for a moment I tried to install one of the NDK sample apps on the device. This failed with the message: "read only file system". Looking in logcat it was pretty apparent that this was also causing all other applications to fail, since they were logging errors with not being able to write under /data/.
Looking at dmesg output finally confirmed this, where it reported that the /data partition had journal errors and could only be mounted as read only (this was also confirmed by issuing the mount command from within an adb shell).
This led me on a journey from just trying to remount the partition as read only (which failed with no further message), through installing clockworkmod, different versions of tnt lite, formatting and repartitioning (or so I thought), to flashing the device through its APX interface (using nvflash). None of them worked.
Not until I read a post by raydog153 - in this archived thread: http://forum.xda-developers.com/archive/index.php/t-857875.html - did I succeed by re-partitioning the sdcard (under the advanced section).
You could argue that it was stupid to not realize that a re-partitioning was required in the first place - since the ext3 partition obviously had errors and Android does not provide a fsck command (or does it?) - but I guess I thought that this was what was actually being done in other clockwork commands or at least when doing the nvflash, but obviously that was not the case.
Anyway, sorry for the lengthy entry. I just wanted to give back to the community and help others who might get the same problems I had. Also, on the positive side I have learned a lot and, like someone else wrote, I have completely lost my noob fear of bricking my G Tablet.
Keep up the good work, guys! You Rock!
almost a week without problems with FCs, thanks for this usefull info.
Hey guys,
followed every single word from all the threads concerning Data2SD, and still can't get it to work...
I keep on getting an error message as soon as the device is done booting.
I then get a "unsuccesful encryption" message stating that I should do a factory reset etc.
However, even after trying like all the possible combinations of .zip orders, I still keep getting that message.
I'd appreciate if someone could give me a hand
(PS: I did try to do the disabling journaling, but it seems the problem should be found there!
Let me show you in the attached screenshot of my adb commands! )
adelancker said:
Hey guys,
followed every single word from all the threads concerning Data2SD, and still can't get it to work...
I keep on getting an error message as soon as the device is done booting.
I then get a "unsuccesful encryption" message stating that I should do a factory reset etc.
However, even after trying like all the possible combinations of .zip orders, I still keep getting that message.
I'd appreciate if someone could give me a hand
(PS: I did try to do the disabling journaling, but it seems the problem should be found there!
Let me show you in the attached screenshot of my adb commands! )
Click to expand...
Click to collapse
I believe the issue is with your SDcard. Your device did not see the second partition ext4.
Dear all,
I have flashed my MZ605 (32GB) using EOS 3.0 for MZ601 with TWRP and that has worked quite well for some time, but last week I was fiddling with the navigation app and the tablet suddenly froze. The only way to get it back to life was doing a volume-up+power. Now the system still boots: i get to the lock screen, but as soon as I unlock (no password, just swiping to the right), I receive a shower of f/c messages and no icons apear. The settings screen still seems to work, but since the stream of f/c messages doesn't stop, it's very hard to do anything at all. I tried all the standard stuff first: Flashing EOS 3.0 using TWRP and Factory Reset: It seems to do nothing at all. Everything stays the same! When trying to delete cache, userdata, etc. Right after displaying the message "updating partition details", it complains that it is not able to access certain files in /data/media (a bunch of mp3 files)
Figuring that something must be wrong with the filesystem, I fired up the console of TWRP and did an e2fsck (e2fsck -vfcp) on partition 8,9 and 10, resulting simply in "unable to set superblock flags". I tried formatting the thing by hand but when doing mke2fs, it acts like it it's creating the fs (you see the numbers fly by), but when mounting the fs again, nothing changed at all!
About the partition table: Accessing the kernel messages (dmesg) with ADB says that the primary gpt table is corrupt and will try to use the backup table. It then merrily continues booting. However, when checking the partition table with gdisk (using ADB): it says nothing is present. Using the recovery options show that the primary table contains garbage and the backup partition table doesn't seem to contain anything. :S This contrasts with the fact that kernel still sees the partitions and that they are mountable both when booting normally as well as with TWRP
As a last resort I downloaded RSDLite 5.7 and the most recent SBF image. It flashes the whole thing without any errors, but when booting the system: nothing changed at all???
For the tl;dr people: Sorry! In a nutshell: fs seems to be frozen: mke2fs does nothing, fastboot flash does nothing and even sbf flash doesn't do anything at all. However the device still boots, albeit with a shower of f/c on unlock screen.
Any suggestions what to? I have been googling for many days now and reading this forum. Nothing has helped so far...
My next try would be to redefine the gpt partition table using gdisk and then hope that'll fix the frozen that. After that I would of course do a wipe all and flash a new ROM. The problem is, I can't find the standard partition layout details for the Xoom anywhere, nor do I have any other ideas what to do in case this does not work
If anyone has any hint or idea, please let me know. Thanks!
Nobody?
If anyone could please tell me their partition layout, like start - end - type for each partition. It'd really appreciate it!
Thanks!
No one?
Hello,
have you fixed it ?
Nope
jkd said:
Hello,
have you fixed it ?
Click to expand...
Click to collapse
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
ioish said:
Unfortunately I haven't been able to fix it. I still have the tablet though, hoping that one day I will come across a fix. I have two theories as to what may have caused it:
1) Physicalically the write pin of the internal flash got disconnected
2) Somehow a readonly command was send to the flash and made it read-only. I don't know if this is possible neither how to undo it.
If you have a solution, please let me know. I'm also willing to do tests and experiments to try to solve the problem.
Click to expand...
Click to collapse
Actually I have the same problem, I have read several forums and I have not found an answer
jkd said:
Actually I have the same problem, I have read several forums and I have not found an answer
Click to expand...
Click to collapse
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
ioish said:
That's too bad
Did you by any chance install a custom rom or performed any non-official other update?
Click to expand...
Click to collapse
my xoom caracteristic:
- Recovery: TWRP v2.6.3.0 (RunAndHide05 Edition), I can not tell if it's a bigpart or no recovery. Also I am unable to change recovery is cwm or another version of TWRP. I always find my TWRP recovery v2.6.3.0.
- ROM omni: 4.4.2-20140102-1218 + 0100-wingray-HOMEMADE (I don't know if is bigpart rom)
- kernel:2.6.39.4-ElementalX-Xoom-2.1+
***original post copied verbatim******************************************************************
So I was rummaging around the dev section, QA, so forth. And I have seen numerous threads, questions, posts, where people have had issues with ROMs or just general left field issues that were resolved by going back to square 1 doing a fresh clean install of "rom.zip..
My goal with this thread is to contribute some insight and experience with customizing android devices in the way we all do... at square one, clicking the download button.... we also do not have a thread dedicated to this one subject alone, so here it is. I feel stickying this thread would be extremely useful, as so many people could see it right from the get-go and get valuable information from it.
Just getting right into it, I will say this, I have flashed (I'm sure) damn near 1,000 ROMs to various devices. Mine. Friends. Etc. And never once have I installed a corrupt zip file to these devices. This should never happen, and among other important details to any installation of a ROM, this one is the most important...
VERIFY THAT YOUR DOWNLOADS ARE GOOD!
How do you do this??? Well I will show you... it is with this handy little app called md5 checker from the play store. EVERY. SINGLE. ONE OF US.... should have this app, guys (and gals, because I know you are out there it is a free app. No excuses
What is an MD5 checksum? Trusty link to get the gist of it.. http://www.fastsum.com/support/md5-checksum-utility-faq/md5-checksum.php
Making this simple - I will break this down into steps. Follow this meticulously and 99.9% of the time you will not have an issue or be one of the random bugs popping up when everyone else seems fine.
1. Download md5 checker.
2. Download all zip files needed for your ROM. (whether you do this from your mobile device or a desktop/laptop it doesn't matter, because you WILL verify the file AFTER you have transferred it to where it needs to be allocated - your device). Basically, download it, transfer it.
3. Open md5 checker, the app is pretty easy to use. Much like a file explorer in its layout with the obvious differences.
4. Retrieve md5 for your zip files.
5. Verify them with ROM developer, or others using that particular ROM. Any discrepancies - back to step 2.
6. All is well? Boot to recovery.
7. Wipe data 3 times (you don't need to wipe dalvik cache, that directory is found in the data partition - wiping data = wiping dalvik cache)
8. Wipe cache 3 times (this sometimes does not need to be done either depending on whether or not your recovery wipes cache with data.. most recoveries will spit out some text during the wiping phase letting you know the details of the process and you'll see see something like this when wiping data)..
"Wiping /data...
"Wiping /cache
If you see cache being wiped, you are good. No need to manually wipe cache.
9. Format your system partition through recovery 3 times
10. Install your ROM. Reboot. Let it sit for a minute or two, reboot it again. If you are not installing a custom kernel, stop here. You are done, and winning.
11. Reboot to recovery, wipe cache partition 3 times AND dalvik cache. They are both there as options, for this reason - the goodies we install after a full ROM install.
12. Flash kernel zip. Reboot. Let it sit for a minute or two, reboot it again. You are done, and winning.
Interesting fact about all the ROMs I have installed over the years, NOT ONCE, have I ever installed something corrupted, and every issue/bug I have ever had with a ROM was a known issue. This also doesn't mean your particular device is always going to be able to run for weeks on end without needing a quick reboot. Sometimes its good to do the dishes, I get that. But my disclaimer here is for all to note, if you follow these steps meticulously, you will ALWAYS be able to say to yourself with confidence "nope, did it right, there is something else going on here." And thus you will be a greater problem solver and contributor to the community as a whole every single time you pose a thought or question regarding any problems you are having.
"Do it right once, instead of doin it wrong twice before doing it right."
We are nothing useful without useful information. Useful information = posting in a thread in this tone...
"Hey, installed ROM correctly/thoroughly, verified downloads, XXX is buggy blah blah etc etc... can somebody else here verify if they are or aren't having this issue? Thanks!"
Based on people's response you'll know if it is just you or a legitimate issue, in which case, you brought it to the attention of us all, and the dev(s), and you have now been very useful.
What you don't want to do is this....
"My phone keeps rebooting!!! Haaaalp"
The reason why you shouldn't post like that is because you will ALWAYS get a sour response or people will just ignore you. Or, they will reply with questions you should have already asked yourself... "did you verify your downloads were good??? Did you do a clean and thorough install???"
Long post, but I hope somebody will find it useful and utilize it. It will increase your experience with your android device in a positive way, as it has for me. Cheers
Ah yes i get random freeze screen with some ROM installer
why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?
Very nice guide. Extremely helpful for beginners
Sent from my GT-N7100 using xda premium
And please have to say that use a wipe script it's such a kind of blasfemy ...
Alienator9191 said:
why not format every partition 3 times (idk how recovery looks at this device, im used to 4ext on the HTC sensation) and the wipe data to set al parations right again and install the rom? even why wiping 3 times instead of 1?
Click to expand...
Click to collapse
agreed
since nand ram has its life time of cycle. wiping the nand for more than needed is some kind of suicide mission to your droid....
I disagree. If you are the type that flashes a ROM 5 times a day then yes that might be a factor.... might be. Each android device I have owned I have flashed a ROM/kernel to it literally thousands of times and nothing was ever damaged because of scrubbing the disk too much and flashing to it too much. Sorry, but misinformed about just how robust these disks are.
It needs to a must read for noobs
Sent from my GT-N7100 using xda premium
Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.
First of all thz for this step-by-step guide, for newbie is useful.
Phistachio said:
Most definitely, wiping 3 times is completely unnecessary. Only 1 time is enough for the NAND to perform the wipe commands. Not only that, but also you're wearing out the flash drive by wiping so much, even though you flash a lot. Another reason to only wipe once.
Click to expand...
Click to collapse
I agree, why repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND...
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:
zenzip said:
First of all thz for this step-by-step guide, for newbie is useful.
I agree, why to repeat 3 time the same wipe command, when 1 time is enough for wipe data from NAND ?
unless there is an hidden reason, I don't see a good reason to do that! :cyclops:
Click to expand...
Click to collapse
1 wipe is more than enough
plus this thread should be in general section
I never face any problem with these steps (surely more then 100 flashing)
1.Downoad and flash ROM with Odin (odin doesn't check md5??)
2.Reboot, nevermind if stuck
3.Reboot to recovery, wipe cache and data.
Thats it.
If your counter is already raised, first make sure you have stock kernel and recovery
Reset counter
Start from step 1 above.
**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard
BullHorn7 said:
**knock knock knock**
Leonard
**knock knock knock**
Leonard
**knock knock knock**
Leonard
Click to expand...
Click to collapse
Lol... this is Sheldon wiping style...
Inviato dal mio GT-N7100 con Tapatalk 2
Persistent bricking of a Moto G XT1040 LTE
I'm happy to PayPal $20 to anyone who figures this one out...
One day it was working, and then - it froze and went to the loading screen and stayed there. I've unlocked and rooted and used for months with no issue. I've tried everything I can find to fix my Moto G LTE gen-1 XT1040, and I'm at my wits end.
It works, in the sense that I can load fastboot, and I can load CWM (I cannot load any version of TWRP), but I can't get into an operating system. I've tried flashing the stock OEM, I've tried flashing lolipop, slimkat, cyanogenmod - no luck with anything. It does not load into recovery (stock, CWM or TWRP) but can load CWM with "fastboot boot cwm.img" (fastboot flash boot cwm.img then booting into recovery fails).
It looks like some parts of the cyanogenmod flashing stuck, but since then nothing else seems to do anything. Also, the system partition seems to be "raw" when I try to use it - I can't delete my user data (things have persisted despite wiping commands from fastboot and in adb and in CWM). It looks as though anything I'm trying isn't "sticking". I've tried to be as detailed as possible with screenshots.
Maybe: corrupted system partition? somehow things are "locked"? should be hardbricked and then reinstalled as device driver? hardware issue?
All images / screenshots / logs with details are here: imgur.com/a/dQQGD
Any suggestions, tips, advice on this one? Your help would be very appreciated.
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
lost101 said:
Sounds like the emmc corruption (making phone read-only) that possibly affects many phones. There are certainly numerous cases of this happening with Moto G - so many infact that I have looked into getting ROMs to boot via OTG-USB drives. There appears to be many 'solutions' if you search around, but I know of no single case where someone has fixed the problem. Replacing Motherboard is of course an option.
Click to expand...
Click to collapse
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
canwond said:
Hmm.. Thanks for your reply. In another thread user liveroy posted "The eMMC is not corrupted or defunct, you just got the fs on those positions destroyed, therefore they are not formatted now, thus being RAW. If you still have custom recovery installed, try formatting /system, /data and flash CM12."
Any way to follow-up on that? Is there a way to do the formatting from adb?
I'm OK with replacing the motherboard, if that's needed. No idea where to find this particular part though.
Tried "mount -o rw,remount -t yaffs2 /system" got "mount: can't find /system in /proc/mounts"
Click to expand...
Click to collapse
I was under the impression the appearance of partitions being 'raw' was just another symptom of corruption. I gave some ideas to try regarding formatting in the later posts of this thread.
Look for an XT1040 with broken screen, but still functional; as a cheap way to get a motherboard.