As the title states (but longer)...
My battery life has been great on this unit - A few days ago it died while sitting on my desk (not being used, just sitting there, as it often does).
I plugged it back in, and instead of of seeing the usual battery charging icon (green progress bar), it just displayed a "generic" looking battery with a bolt next to it - Maybe it's the default icon for a dead system, I don't know, not sure at this point.. After sitting awhile, the icon disappeared, so I tapped the power button which usually triggers the icon to pop up. It brought up the same one.. Okay, needs more time I guess..
For kicks, changed cord and supply (known good, but was baffled by it not working), and left it for the day.
Actually, 2, because I forgot about it and had other stuff going on...
Came back to same thing. Read online about holding home, vol up and power to reset it (apparently a "common" issue), and did that. Nothing happened, then I thought well if it's not charging for some reason, won't start.. So whilst holding that sequence, I also plugged it in. Viola! (well sort of)
It whirred to life showing me the Samsung Tab A 10 logo, which was met afterward by a blue android screen saying it was entering recovery mode (or similar, going from memory on that one) then it spits out some text, and restarts and does this loop over and over until I disconnect it and the battery finally dies. (no photo attachment so I will type what it displays)
#fail to open recovery_cause(No such file or directory)#
#reboot recovery cause is [UNKNOWN]#
No support SINGLE-SKU
File-based OTA
E:failed to mount /efs (Invalid Argument)
Supported API: 3
E:failed to mount /efs (Invalid Argument)
E:failed to mount /persdata (Invalid argument)
--Wiping persdata...
Formatting /persdata...
e:format_volume: make ext4 failed on /dev/block/platform/13540000.dwmmc0/by-name/PERSDATA: I/O error
persdata wipe failed.
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
Can't mount /cache/recovery/last_locale
Stays there a few, the restarts with the Android blue screen..
This is a completely stock unit, not flashed/modded/altered in any way. No side-loaded apps, does have SD card, tried it without and with it installed (reset guide mentions removing sd card, so I did)..
Nothing abnormal happened with it while sitting on desk, same routine in life with it, as always..
Anyone have ANY ideas on what could be wrong, or how I can fix it? Appreciate any assistance on this matter
Thanks in advance,
MTXRooster
No one has any ideas on what could be wrong or how to fix it? Again, this is a stock unit, nothing botched during a mod or anything, literally just powered it up after being dead and got this all as the result... Help?
long distance bump of desparation..
Related
I recently had an issue with my Nexus 7 freezing constantly and I tried to perform a factory reset through the tablet's setting itself instead of the recovery menu now it seems to be stuck in some sort of loop when I try to start it. This tablet is non-rooted and completely stock, btw.
When the tablet turns on, it boots into a screen that shows an Android with a spinning blue cage on his chest, the word "Erasing..." and a bar at the bottom, which isn't actually filling to show any progress and is instead full blue with these lines going through it.
After a few minutes of that, the blue cage thing and the bar stop moving and the tablet freezes, bringing me to a screen with an Android laying on his back with a red exclamation point above his open chest.
When I press Power and Vol+, it brings me to the recovery menu, with this at the bottom:
Also, I don't know if this is important or not, but it says Android system recovery <3e> and KTU84P at the top of the recovery menu.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
Being that I'm in the recovery menu, I have the option to reboot, apply update from ADB, wipe data/factory reset, and wipe cache partition. Being as it's constantly telling me that it either can't open or can't mount /cache, I thought wiping the cache partition would help, but that also gives me a bunch of fails:
-- Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After that, I attempted to do a wipe from this menu, which also gave the same errors:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
Data wipe complete.
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After all that jazz and long wall of failure, it brings me back to the recovery menu. Even with all the failing, I thought it did something since it said "Data wipe complete", but now trying to "reboot system now", it brings me to a solid black screen as if the tablet locked up or just turned off. Turning it back on again, it shows the word "Google" before displaying the original screen of the android with the blue spinning cage and the word "Erasing", effectively completing the loop.
My warranty obviously expired ages ago now and I'm hoping somebody here can help.
So, update here: I tried to mess with it some more this morning and it seems that it got through the factory reset it was stuck on, but I'm still having issues with constant freezing.
I can get to the "Google" bootup screen and where the colored circles spin around before bringing me to the menus to set up my Wi-Fi and account and all that (like it did when it was first out of the box), but now it continues to freeze while trying to set up these settings.
I managed to input my Wi-Fi password and skip over the rest of the settings in hopes of getting into the system before another freeze and now it gets stuck on a black screen that only shows the "back" arrow at the bottom and the battery and internet indicators at the top right.
Any ideas, guys? I can effectively get into the bootloader now, but attempting to wipe through the recovery menu gives the same errors as before while clearing cache seems to work without issues.
I attempted to use a Nexus Root Toolkit to "Flash Stock + Unroot" with the "Soft-Bricked/Booloop" option selected and everything seemed to work until it got towards the end when the program stops responding.
Now I can't boot into the system at all and I only get a very primitive "bootloader" that says Google (instead of showing the Android) and that's it. I can use the volume keys to browse between "Start", "Restart bootloader", "Recovery mode", and "Power off". Both Start and Recovery mode bring me to the same exact screen while "Restart bootloader" seems to bring me to a complete bootloader, but choosing any of those options brings me right back to the screen without all the info.
I feel like I'm just messing this up more the more I mess with it and I'm not sure what else to try. This Nexus 7 is completely stock, by the way.
MrTripStack said:
I recently had an issue with my Nexus 7 freezing constantly and I tried to perform a factory reset through the tablet's setting itself instead of the recovery menu now it seems to be stuck in some sort of loop when I try to start it. This tablet is non-rooted and completely stock, btw.
When the tablet turns on, it boots into a screen that shows an Android with a spinning blue cage on his chest, the word "Erasing..." and a bar at the bottom, which isn't actually filling to show any progress and is instead full blue with these lines going through it.
After a few minutes of that, the blue cage thing and the bar stop moving and the tablet freezes, bringing me to a screen with an Android laying on his back with a red exclamation point above his open chest.
When I press Power and Vol+, it brings me to the recovery menu, with this at the bottom:
Also, I don't know if this is important or not, but it says Android system recovery <3e> and KTU84P at the top of the recovery menu.
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
Being that I'm in the recovery menu, I have the option to reboot, apply update from ADB, wipe data/factory reset, and wipe cache partition. Being as it's constantly telling me that it either can't open or can't mount /cache, I thought wiping the cache partition would help, but that also gives me a bunch of fails:
-- Wiping cache...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After that, I attempted to do a wipe from this menu, which also gave the same errors:
-- Wiping data...
Formatting /data...
E: failed to mount /cache (Invalid argument)
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
Data wipe complete.
Formatting /cache...
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: Failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC (I/O error)
E: failed to mount /cache (Invalid argument)
After all that jazz and long wall of failure, it brings me back to the recovery menu. Even with all the failing, I thought it did something since it said "Data wipe complete", but now trying to "reboot system now", it brings me to a solid black screen as if the tablet locked up or just turned off. Turning it back on again, it shows the word "Google" before displaying the original screen of the android with the blue spinning cage and the word "Erasing", effectively completing the loop.
My warranty obviously expired ages ago now and I'm hoping somebody here can help.
Click to expand...
Click to collapse
Hi, MrTripStack...
Unfortunately, this doesn't sound good at all, I'm afraid...
Your error outputs suggest some kind of partition corruption... and given that your device is running unrooted factory stock (ie, no modifications), I'm inclined to suspect hardware failure with the devices internal eMMC chip. The "failed to mount..." errors are suggestive of this.
The only thing I can suggest, is you attempt to fastboot flash back to factory stock (see download link in my sig. below for the factory image for your specific device).
Full instructions available here...
[GUIDE] Flashing a Factory Image with fastboot / return to stock
(But be aware of a known issue fastboot flashing the v4.23 bootloader that ships with some versions of factory stock; fastboot flashing it causes error messages. Pay particular attention to the comment in red, right at the top, in the very first post in the above link/thread.)
-----------------------------------------------------------------------
I'm not optimistic this will work though... if there is a problem with the eMMC chip, you will likely see a whole raft of similar error messages during the fastboot flash process.
For what it's worth... good luck.
Rgrds,
Ged.
ADDENDUM: Just seen your additional post, which you posted whilst I drafting mine... and it seems to confirm my suspicions that you probably have a hardware problem (eMMC chip).
GedBlake said:
ADDENDUM: Just seen your additional post, which you posted whilst I drafting mine... and it seems to confirm my suspicions that you probably have a hardware problem (eMMC chip) .
Click to expand...
Click to collapse
I was afraid of this, but at least my suspicious are seeming more and more confirmed. Is it worth it (or even possible) to replace the eMMC chip or should I just scrap the tablet entirely?
MrTripStack said:
I was afraid of this, but at least my suspicious are seeming more and more confirmed. Is it worth it (or even possible) to replace the eMMC chip or should I just scrap the tablet entirely?
Click to expand...
Click to collapse
I'm no hardware expert, but I really don't think it's possible to replace the eMMC chip. It's pretty much 'embedded' into the motherboard, and soldered into place by a computer controlled machine, with very fine and very precise spot soldering... way beyond the capability of any human equipped with a soldering iron to attempt.
You could though, consider replacing the motherboard itself, which has been attempted by another XDA member, and apparently, successfully...
http://forum.xda-developers.com/showpost.php?p=54798993&postcount=824
Rgrds,
Ged.
Hi folks,
I think my nexus 7 2012 is totally bricked.
It was playing up getting stuck at the flying colours at startup,(has OS 4.44 kitty kat didn't upgrade to 5.0)
So I went into recovery mode and tried reset but got all these messages.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
Just keep restarting after this as far as the flying colours icon.
I went to this site
wugfresh.com/nrt
and downloaded the Nexus Root Toolkit v2.1.6 ran it and installed drivers, PC could see android device ok, toolkit got as far as downloading my android OS 4.4 but seemed to get stuck at the flashing process writing the bootloader I think.
Anyway to cut a long story short my nexus won't even power on now at all, no way to get to the fastboot screen and its showing in windows as an apx device, from reading other threads seems a total brick.
No way back from this I take it, unless a hardware repairor something else major.
Appreciate any advice
Thanks a lot
Joe
you're screwed if you didn't create nvflash wheelie blobs, luckily a new mobo is real cheap and pretty easy to put in
Hello, wondering if I could get any advice/help
Family member has an unlocked S8 they were charging overnight.
In the morning, the phone's screen was off and the notification LED was solid green.
Holding power + volume down keys turns on the phone but gets stuck at the "Powered by Android" screen with "CARRIER", "RPMB fuse blown", etc on the top left corner.
I was not able to get the phone into recovery mode, but was successful in getting it to download mode. However I cancelled out to restart and it then briefly showed an all blue screen with a white Android and the message "Installing system update". The screen then went black and scrolled the following text.
Code:
No Support SINGLE-SKU
Supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity error...
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_kernel_manual
E:Can't open /cache/recovery/last_kernel_manual
E:failed to mount /system (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
Then, the phone will loop between the blue screen and the text above.
My prior Android phones have been the HTC One X, Nexus 5, and Nexus 6 so I am new to Samsung devices.
Is it possible to go into download mode and flash it? If so, would the data be lost?
Thank you for the help
henry_gale said:
Hello, wondering if I could get any advice/help
Family member has an unlocked S8 they were charging overnight.
In the morning, the phone's screen was off and the notification LED was solid green.
Holding power + volume down keys turns on the phone but gets stuck at the "Powered by Android" screen with "CARRIER", "RPMB fuse blown", etc on the top left corner.
I was not able to get the phone into recovery mode, but was successful in getting it to download mode. However I cancelled out to restart and it then briefly showed an all blue screen with a white Android and the message "Installing system update". The screen then went black and scrolled the following text.
Code:
No Support SINGLE-SKU
Supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity error...
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_kernel_manual
E:Can't open /cache/recovery/last_kernel_manual
E:failed to mount /system (Invalid argument)
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
Then, the phone will loop between the blue screen and the text above.
My prior Android phones have been the HTC One X, Nexus 5, and Nexus 6 so I am new to Samsung devices.
Is it possible to go into download mode and flash it? If so, would the data be lost?
Thank you for the help
Click to expand...
Click to collapse
Should be good to go to download mode and flash with odin...get firmware from sammobile.... data erase? Most likely yes
Best of luck bro
If you don't know how to get to download mode - from off you hold volume down, bixby button and power until logo arrives. press volume up when warning comes and your in download mode.
Cheers....
Hi, my cell got bootloop, for the second time in the last 3 years. But this time, shows that when I enter recovery mode:
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache (invalid argument)
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
E: failed to mount /cache (invalid argument)
And when i try power on, stop on asus logo + android screen forever.
The last rom has ASUS_T00F_WW_user_3.23.40.60.
When i try to adb sideload:
Asus Zenfone 5 A500CG Debrick>adb sideload WW_500_1105_1208_20141208.zip
Total xfer: 0.00x
And just that. Someone from zentalk said to try xfstk method and probably emmc is dying:
XFSTK-STATUS--USBSN:1157C0ECFD9F6599--Softfuses Binary absent. Please provide binary.
XFSTK-LOG--USBSN:1157C0ECFD9F6599--GetOpCode
XFSTK-LOG--USBSN:1157C0ECFD9F6599--ReadInAck
XFSTK-LOG--USBSN:1157C0ECFD9F6599--GetAck
XFSTK-LOG--USBSN:1157C0ECFD9F6599--GetAck - HLT0(0x4)
XFSTK-LOG--USBSN:1157C0ECFD9F6599--Softfuse Binary file size = 0 or Number of keys = 0
XFSTK-LOG--USBSN:1157C0ECFD9F6599--void CloverviewPlusDownloader::do_abort()
XFSTK-LOG--USBSN:1157C0ECFD9F6599--Abort
XFSTK-STATUS--USBSN:1157C0ECFD9F6599--FAIL
XFSTK-STATUS--USBSN:1157C0ECFD9F6599--Errors encounter during FW download. Aborting ...
Already tried debrick method but no effect, still the same yellow messages on recovery mode.
There is light at the end of the tunnel ?
https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
valeverson said:
https://forum.xda-developers.com/zenfone-5/help/debrick-asus-zenfoen-5-fastboot-t3377455
Click to expand...
Click to collapse
already tried, no results
My phone is bricked, now my phone is fixed, i have try any thread, but i find thread to fix but i forget where i found that thread
Help me
Help me fix
Pls give link
Trying to fix my girlfriend's tablet, she needs a bunch of artwork that's on it.
I'm not sure how, but it seems it has gotten stuck in a boot loop at low battery. Screen won't turn on without being plugged in. When the tablet is plugged in, it jumps to the title screen (Galaxy Tab A with S Pen) and then goes to a blue "installing system update" screen. After hanging there for a second it shows this screen dump:
No Support SINGLE-SKU
Supported API: 3
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
dm-verity error...
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_kernel_manual
E:Can't open /cache/recovery/last_kernel_manual
E:failed to mount /cache (invalid argument)
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
I've tried to reboot into recovery and have left it in the loop for a couple hours hoping it would charge enough to turn on without being plugged in, but nothing's worked so far. I'm real worried that it's DOA, but I'm holding out hope that there's someone one in the forum that might know of something I can do to save it. I've googled some of the stuff in the dump but nothing's been helpful as far as a fix.
Model: SM-P580
I don't believe it's unlocked or rooted, should just be vanilla. Not sure of the android version, but I know that she hasn't used it regularly in probably a year plus.
Any help or advice is appreciated!!
Based on what it says, I think something happend and cause the kernel to be inaccessible. You could get wanntary from Samsung and have Samsung fix it. If she did not root the thing, wanntary should still be vaild. You could reinstall the os in Odin and I tried it on my SMT380 and I kept all of my data so her artwork should still be there.
captainkirk1701 said:
Trying to fix my girlfriend's tablet, she needs a bunch of artwork that's on it.
I'm not sure how, but it seems it has gotten stuck in a boot loop at low battery. Screen won't turn on without being plugged in. When the tablet is plugged in, it jumps to the title screen (Galaxy Tab A with S Pen) and then goes to a blue "installing system update" screen. After hanging there for a second it shows this screen dump:
No Support SINGLE-SKU
Supported API: 3
E:failed to mount /efs (invalid argument)
E:failed to mount /efs (invalid argument)
dm-verity error...
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_kernel_manual
E:Can't open /cache/recovery/last_kernel_manual
E:failed to mount /cache (invalid argument)
E:failed to mount /system (invalid argument)
E:failed to mount /cache (invalid argument)
E:Can't mount /cache/recovery/last_locale
I've tried to reboot into recovery and have left it in the loop for a couple hours hoping it would charge enough to turn on without being plugged in, but nothing's worked so far. I'm real worried that it's DOA, but I'm holding out hope that there's someone one in the forum that might know of something I can do to save it. I've googled some of the stuff in the dump but nothing's been helpful as far as a fix.
Model: SM-P580
I don't believe it's unlocked or rooted, should just be vanilla. Not sure of the android version, but I know that she hasn't used it regularly in probably a year plus.
Any help or advice is appreciated!!
Click to expand...
Click to collapse
Kindly do tell me if you ever succeeded on this issue you had, and what you did?