Hello forum Seniors
I have a problem with my a100 device, I searched for days a solution, but had no success.
I bought this device with original HC and updated with ACER_AV041_A100_0.002.00_ww_GEN1 ICS rom, to this point everything working.
everything worked, boot recovery/gps/games/ics/ everything
And I used it for a long time. Then I reseted the device.
And the problem began.
the device does not turn over.
I can START fastboot, but it dont sync with pc (I got drivers instaled)
I can START recovery, but dont install nothing ( I think my recovery is damaged)
I hope that there is a solution. But have not found any yet.
my recovery does not install or mount sdcard and external sd
when I enter, I see a red triangle with a dead android
I PRESS HOME key and recovery list this
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
________________________________________
E:/dev/block/mmcblk1 does not exist
Finding update package...
E:failed to mount /mnt/sdcard (No such file or directory)
E:Can't mount /mnt/sdcard/update.zip
Instalation aborted.
----end----
I can navigate with VOL keys but i CAN'T select any option
Device not unlocked in fastboot (unluck mode) dont listed
I have the number of ADB connect, is this a CPUID to use in EUU_SBK????
There is a guide to using the EUU_SBK??? link please?????
This is my last hope.
sorry my bad inglish im a brazilian noob
thank all
E:/dev/block/mmcblk1 does not exist
That's recovery. Its saying recovery doesn't exist. If you can wait for a bit I'm working on fixing this but its going slow as some people aren't as clear about whats happening as you are, I was chasing a fix that didn't even need fixing, thank you. Its either something different and new, or its something thats been happening this whole time, but no one mentioned the error output aside from the update.zip failure.
I'll begin work on this new issue, and hopefully it can be fixed with the rest. The other devices seem to have recovery, however it seems it only works in CWM or TWRP, you seem to have stock recovery. I would suggest maybe trying to install CWM from HERE. Follow the instructions exactly and see if you can flash the CWM recovery and get into that. Please report back if this works or not, and what happens when you try.
Hi pio_masaki
Device not BOOTup, freeze in acer logo and I never root this device only apply official update
fastboot can't sync with pc for install a recovery and fastboot is locked
Fastboot display
"Bootloader v0.03.06-ICS: Starting Fastboot USB download protocol"
but fastboot no running any commands
fastboot erase
fastboot flash recovery.img
I try now a new SDcard formated with FAT32 clean, root directory with update.zip, renamed Acer_AV041_A100_1.014.00_WW_GEN1 to update.zip
boot in recovery
------------------------------------------
Erasing cache before SD update...
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
----end-----------------------------------
now display dead android with RED TRIANGLE (!), press HOME key
-------------------------------------------
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
________________________________________
E:/dev/block/mmcblk1 does exist
Finding update package...
E:failed to mount /mnt/sdcard (No such file or directory)
E:Can't mount /mnt/sdcard/update.zip
Instalation aborted.
------------end-------------------------
note now display E:/dev/block/mmcblk1 does exist<<<<<<<<<<<<<
but I can't select any option in recovery only VOLUME keys work and HOME hide text
I can make Hard Reset with keys
(VOL-)+Power on vibrate swift lockscreen
display
-------------------------------
Erasing cache...
Erasing data...
--------end--------------------
restard and freeze in acer logo.
thank you and sorry my inglish
Your english is fine, don't worry
Ok, so previously mmcblk0p1 was NOT found, now it IS found? Well thats better then nothing. I've seen this on another device, though it was cache that was mounting and not mounting at almost random times.
I've been tracking this as far as I can, and it appears the A100 shares an issue with the A500 (and maybe A200?) that results in a bad sector(s) and must be partitioned around. If this is the actual cause, its a hardware failure, not software, and isn't anything you did, it just died.
This explains the string of bricks that seem to occur out of nowhere.
My original method was to DD a working image to the device, completely restoring the partition with a clone of my working system, cache, recovery, etc. However if its a damaged EMMC, this will not work either. This also explains why past attempts have failed on other devices that I've tried helping with off the forum.
As I can emulate a "bricked" device, I don't have a device with this actual issue to diagnose and attempt to fix, my device doesn't have this problem. I'm not real sure I can proceed much farther until either my device does this bad sector thing, or I get my hands on a device that is already bricked and begin finding the method to repair it.
Ok..now dealing with what DOES work...
==========================================================
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
=========================================================
have you tried selecting any of these options? Highlight with volume, and hit power to select, try from
apply update from external storage and record what it says (hopefully it just installs and your're good to go)
then
apply update from cache and again record what it says, hopefully it works fine.
then
wipe data/factory reset and again record what it says
then
wipe cache partition and record what it says
Do these in the order I mentioned, only doing the next if it fails. If it does install, don't do the rest, just report back success and what you did, in the order you did it, to get it going again.
Edit: Oh and reboot after each selection if it fails, and reboot into that menu again.
This is the problem, can't select any option
I select a option with VOLUME key, put cursor on apply updade from external storage so i hit power
And nothing happens.
If i hold power, device force power off...
Power key work perfect, only in recovery dont work...
Thank you
My friend have the same device with the same update 0.002.0_WW_GEN1, his device work normaly, when i go into recovery, I cant select any option too
I think if i reset his device, this cant boot to...i dont try it
I can upload video in youtube for you, if it help u see my case.
Ok, if power doesn't work on either device, try the home button. It's been so long since I ran stock recovery I may have gotten the buttons mixed up with CWM recovery, which uses Power as Enter. And good call on not doing anything on the other device, you never know. It shouldn't cause issues, but just in case, don't. We don't know exactly what is causing this, and if its anything like the hardbrick bug in some Samsung devices, anything can trigger it if it happens in the right order or time.
pio_masaki
Recovery does not select options when press power /home/reset/volumes
I need a guide for use EUUs_SBK rom, I have my CPUID
And in my friend's device, how i back to original hc?
Recovery have the same problem does not intall update.zip, if I install the CWM, Can I do official update to back original state? I really need back to factory rom and recovery.
Thank you for help
If the device is having issues, I wouldn't suggest going back to HC, it can only cause more problems. If you run the official update.zip it returns back to how it came from Acer, stock recovery, locked bootloader and unrooted stock ICS.
The EUU and SBK stuff has been attempted before and failed. Its in various threads with the same bricking issues, and doesn't seem to help, or work. At this point I think NVFLash is about the only option we have left to try to bring these back from a bricked state. Sadly Acer decided to try to lock out NVFLash, so it'll take some time to see if it will work with our A100s. Vache has the NVFlash config files, so its a start, it may work it may not, however I can't test much as my device doesn't have this bricking issue, so any testing on my a100 doesn't really mean anything.
I've actually looked around locally for a bricked a100 to see if I can get and begin working on a method to repair it, but either there are none locally bricked, or none are up for sale (sent back to Acer for repair).
I'm working on it, but I have a couple roadblocks preventing me from really trying, time, and no bricked device.
Ok doing some more digging around, I've come across a thread with some posts that seem to lead me to believe that (non stock) our bootloaders don't respond to the correct SBK, mine doesn't either, and I think it's because our method for unlocking the bootloader uses the A200 bootloader, which will NOT accept the SBK, even if correct, because its wrong for that bootloader.
This leaves out NVFlash, it can't authenticate with the bootloader so it gets blocked, so while it would fix the bricks (outside of hardware failure) it's not an option for us until we find out the correct SBK for our bootloaders.
For those on stock, the update.zip failures seem to be common, however I have a few things for you to try (I think you're stock ICS right?)
download this update.zip
Its ICS 014, should work.
It seems people had issues with it working because it originally came encrypted, and had to be decrypted to work. If it wasn't, you got update.zip not found or various other errors like you did. Thanks to azmode for this.
Take your external SD card, insert it into your PC however you can, and format it FAT32. Before doing this, copy any and all files you wish to keep safe to the PC as this will erase the card completely. If your card reader has a light, wait for it to stop flashing before moving on.
Take the update.zip file you downloaded and place it on the card. Nothing else, no folders or pics or music or anything else. Again wait for the activity light to stop for a few seconds BEFORE hitting eject. Also verify the file is named update.zip nothing else, and not update.zip.zip which can sometimes happen. All lowercase letters.
Once that is done make sure the tablet is OFF, completely, not sleeping but off. Leave it off for at least 30 seconds (or if its been off the whole time don't worry about it) then insert the SD card. Hold Volume Down (closest to lock switch) then press and hold Power and hold for about 3 seconds until the text FIRST comes up, immediately release the buttons as soon as you see any text coming up.
This should once again attempt to read update.zip from the external sd card, and hopefully finds it, or gives a different error then before.
These instructions aren't much different from before, as various other users have outlined this procedure before, in particular blackshinobi who has spent alot of time on the bricked threads.
That update.zip should be decrypted which should allow it to pass the bootloader checks. I think this is where some of the issue is coming from, its that stupid bootloader encryption blocking even valid attempts to restore the tablet to working condition or updating.
If anyone is willing, could they pull their 100% official stock bootloader and stick it somewhere to play around with? Or, I suppose, someone with a 100% official stock ICS system try NVFlash on their system and see if it allows or gives permission denied? If the 100% official still denies, then our SBK generation is wrong, if it does, then its our bootloaders, and we can attempt to fastboot flash the correct bootloader to pass SBK for EUU.
Have you a alternative link? For update.zip
Error 509
Im upload video now, I'm using update.zip from this link http://forum.xda-developers.com/showthread.php?t=1611696
ACER_AV041_A100_0.002.00_ww_GEN1 is the rom instaled and freeze from here http://vache-android.com/v1/index.php?site=files&file=139
--I think if you install it, you will have the same problems.
and i try this link too http://vache-android.com/v1/download.php?fileID=109 and http://vache-android.com/v1/download.php?fileID=116
-------------------Edit----------------
This is a video for try update with recovery in a100
same problem with 2 devices, but my a100 freeze in normal boot
http://youtu.be/CWFlA1W08wE
Im using a formatted microSD with only update.zip file
I tried all the links above.
thank you for help
Did you ever have any luck getting your tablet running again?
It looks like I am having the same issue as you are. with a couple of minor variations. I've tried all the recommendations in this thread and the ones linked from here but I'm not making any progress. I fear there is nothing I can do and that the device is now a fancy brick does anyone have any other ideas on getting this fixed?
1. When I boot to recovery, get to the dead Android I see the following messages in yellow
E:Can't open /dev/block/mmcblk0p5 (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/mmcblk0p5 (No such file or directory)
E:failed to mount /cache (No such file or directory)
2. When I try to unlock the bootloader in fastboot mode (fastboot oem unlock) the screen blinks off and back on and I never get the lock.
wperry1 said:
Did you ever have any luck getting your tablet running again?
It looks like I am having the same issue as you are. with a couple of minor variations. I've tried all the recommendations in this thread and the ones linked from here but I'm not making any progress. I fear there is nothing I can do and that the device is now a fancy brick does anyone have any other ideas on getting this fixed?
1. When I boot to recovery, get to the dead Android I see the following messages in yellow
E:Can't open /dev/block/mmcblk0p5 (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:Can't open /dev/block/mmcblk0p5 (No such file or directory)
E:failed to mount /cache (No such file or directory)
2. When I try to unlock the bootloader in fastboot mode (fastboot oem unlock) the screen blinks off and back on and I never get the lock.
Click to expand...
Click to collapse
Those errors have been identified as a dead emmc, which is currently unrecoverable. And is happening on quite a few of iconia's. This thread was prior to the devs and users finding thee issue. See all the brick threads here.
Ajuda em portugîes
rollidark said:
Hello forum Seniors
I have a problem with my a100 device, I searched for days a solution, but had no success.
I bought this device with original HC and updated with ACER_AV041_A100_0.002.00_ww_GEN1 ICS rom, to this point everything working.
everything worked, boot recovery/gps/games/ics/ everything
And I used it for a long time. Then I reseted the device.
And the problem began.
the device does not turn over.
I can START fastboot, but it dont sync with pc (I got drivers instaled)
I can START recovery, but dont install nothing ( I think my recovery is damaged)
I hope that there is a solution. But have not found any yet.
my recovery does not install or mount sdcard and external sd
when I enter, I see a red triangle with a dead android
I PRESS HOME key and recovery list this
Android system recovery <3e>
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
________________________________________
E:/dev/block/mmcblk1 does not exist
Finding update package...
E:failed to mount /mnt/sdcard (No such file or directory)
E:Can't mount /mnt/sdcard/update.zip
Instalation aborted.
----end----
I can navigate with VOL keys but i CAN'T select any option
Device not unlocked in fastboot (unluck mode) dont listed
I have the number of ADB connect, is this a CPUID to use in EUU_SBK????
There is a guide to using the EUU_SBK??? link please?????
This is my last hope.
sorry my bad inglish im a brazilian noob
thank all
Click to expand...
Click to collapse
Ola Amigo parece que você resolveu esse problema, sou brasileiro como você. Estou com o mesmo problema, como voce resolveu isto?
help
Dear All i have the issue with my Skyvega A 800s that whenever i start my phone its open in recovery mode and when i check log it says " dev/block/mmcblk1p1"
Cant format unknown volume: /emmc
Actually before this everything i going smoothly i flashed the rom and the tried to update from sky station when its complete and phone restart the problem comes please help me out please.....
leitejr said:
Ola Amigo parece que você resolveu esse problema, sou brasileiro como você. Estou com o mesmo problema, como voce resolveu isto?
Click to expand...
Click to collapse
adnandani said:
Dear All i have the issue with my Skyvega A 800s that whenever i start my phone its open in recovery mode and when i check log it says " dev/block/mmcblk1p1"
Cant format unknown volume: /emmc
Actually before this everything i going smoothly i flashed the rom and the tried to update from sky station when its complete and phone restart the problem comes please help me out please.....
Click to expand...
Click to collapse
Well this isn't a forum for that device, and not being familiar with it I can only guess. mmcblk1p1 is usually external SD card, if one is inserted, remove it, if one is not, insert one. See what it does on each try. It may be internal SD card too, hard to say since I don't know that device, although a link to it's recovery.fstab would help there, or just /system/etc/vold.fstab.
Sorry,
I'm one concept
This possible installed replicant recovery?
Just for '' flash img'' option
I'm test replicant os for my gtab2 3110, i'm look this option, i'm just copie img for my device and selected '' flash image'' this installed os
( my problematic for my a100 is i'm manually wipe,problem i'm erase file system ( etc,block,bin etc...)) yes i'm stupid men
Sent from my GT-I9305 using XDA Premium HD app
winny57 said:
Sorry,
I'm one concept
This possible installed replicant recovery?
Just for '' flash img'' option
I'm test replicant os for my gtab2 3110, i'm look this option, i'm just copie img for my device and selected '' flash image'' this installed os
( my problematic for my a100 is i'm manually wipe,problem i'm erase file system ( etc,block,bin etc...)) yes i'm stupid men
Sent from my GT-I9305 using XDA Premium HD app
Click to expand...
Click to collapse
AFAIK it hasn't been made for the a100, so other then that, I dunno.
Sent from my Galaxy Nexus using Tapatalk 2
Ok thanks
You not any solution for me?
Sent from my GT-I9305 using XDA Premium HD app
winny57 said:
Ok thanks
You not any solution for me?
Sent from my GT-I9305 using XDA Premium HD app
Click to expand...
Click to collapse
Besides making that recovery not really, though you can fastboot flash images also.
I'm test this
My device reboot fastboot, this working
I'm flash not working
Sent from my GT-I9305 using XDA Premium HD app
---------- Post added at 02:45 AM ---------- Previous post was at 02:43 AM ----------
I'm not at home but try to remember but as I flash with fastboot
Sent from my GT-I9305 using XDA Premium HD app
Related
I had Cyanogen 7 on my Defy, I needed to get my personal data off of it to sell it.
As there was no nandroid type backup on it I decided to re-flash it.
I forgot to wipe/ clear cache etc before re-flashing.
I can see phone in RSD lite and flash it with whatever I like, but each one does not boot.
I have tried various firmwares.
I get the 'M' or sometimes 'Moto blur start up screen' depending on which firmware I have put on it. I cannot get beyond this.
I have tried https://motorola-global-en-uk.custh...00/~/defy---master-reset-/-factory-data-reset
But I do not get a menu to clear cache etc when I touch the bottom right of the screen.
What is my next step?
When booting press Volume Down and when u see Android logo than press Volume Up and Volume Down together, You will get other options in that Wipe Factory reset and wipe cache than reboot go in boot loader by pressing volume Up and than flash SBF of ur choice...Best of Luck
hmm I get
E:Can't mount Cache:recovery/command
E:Can't mount Cache:recovery/caller
E:Can't mount Cache:recovery/log
...
eMMC chip is dead. Send phone to warranty.
Allso tried this? At your own risk:
Other thing you could try:
http://forum.xda-developers.com/showthread.php?t=938708
Read from post 6.
Allso read this:
http://forum.xda-developers.com/showthread.php?t=922430
YOU CANNOT DOWNGRADE TO 2.1 WHEN YOU FLASH THIS.
sam_bris said:
hmm I get
E:Can't mount Cache:recovery/command
E:Can't mount Cache:recovery/caller
E:Can't mount Cache:recovery/log
...
Click to expand...
Click to collapse
Error is not a problem just wipe factory reset and cache and flash SBF. It works for me when i was in same situation like you...I too got the Error still when ever i go to Stock Recovery i get this Error, But NO PROBLEM till now for me AT LEAST..
romuleta said:
eMMC chip is dead. Send phone to warranty.
Click to expand...
Click to collapse
Thanks for inducing a load of unnecessary paranoia there!
I was just freaking out, cleared the cache, flashed the phone. No problems.
Probably best to keep those kind of opinions to yourself unless you are sure..
Thanks to everyone else for your help.
Thanks
Sam
sam_bris said:
Thanks for inducing a load of unnecessary paranoia there!
I was just freaking out, cleared the cache, flashed the phone. No problems.
Probably best to keep those kind of opinions to yourself unless you are sure..
Thanks to everyone else for your help.
Thanks
Sam
Click to expand...
Click to collapse
I heard that the Defy is not so brickable, i think that is only possible when you do something to the flash (bootloader) partion of the phone. As long as you can get into the bootloader and/or RSD recognises your phone there sould be a way to revive the phone yourself.
Hello folks, hopefully somebody can help me out with this issue or I may just have to bite the bullet and see what the repair costs are going to be from Acer. I have an Iconia A100 that is unlocked and rooted. I never did get around to loading a custom ROM (was waiting for the JB ROMs to get a little bit more stable) and was just running the stock ICS. It also seems that I didn't successfully load a recovery image so I now seem to be totally out of luck. I went to use my tablet while it was still on but the screen refused to turn on after pressing the home button or pressing the power button. So I decided to reset it and figured that would fix it. Now it's stuck booting to the screen with the distorted text at the top and the multiple acer logos at the bottom. I've tried a factory reset to clear the cache and that didn't help although it did say deleting user data and cache. I tried booting into recovery but found that the CWM that I thought I had installed wasn't installed and all I get is a fallen down android icon with a red exclamation over it. If I power up holding down the volume up key and then flicking the screen rotation switch I get it to display that it's in USB fastboot mode but if I type in adb devices it doesn't get listed as an attached device when hooked into my PC. One other note if I leave it at the distorted text and plug it into my PC via USB Windows 7 detects it as a MPT USB Device which it's not able to locate a driver for.
Ok, some additional information:
I was trying to get something out of the screen where I have the fallen down android with the red exclamation point over it and it seems that the default recovery is still installed in Android system recovery (3e). I can't seem to select any menu options on the screen but it does give some additional info. It looks like the eMMC may be partially or completely borked, I'm not sure which. Here's what's on the screen:
Android system recover (3e)
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Then in yellow text:
E: Can't open /dev/block/mmcblk0p5
(No such file or directory)
E: failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E: failed to mount /cache (No such file or directory)
This goes on for a bit of being unable to open various directories. Is there anyway at this point to re-lock the bootloader and erase traces of doing so? I find it hard to believe that unlocking the bootloader would cause what seems to be a hardware fault but I could be wrong.
nsafreak said:
Hello folks, hopefully somebody can help me out with this issue or I may just have to bite the bullet and see what the repair costs are going to be from Acer. I have an Iconia A100 that is unlocked and rooted. I never did get around to loading a custom ROM (was waiting for the JB ROMs to get a little bit more stable) and was just running the stock ICS. It also seems that I didn't successfully load a recovery image so I now seem to be totally out of luck. I went to use my tablet while it was still on but the screen refused to turn on after pressing the home button or pressing the power button. So I decided to reset it and figured that would fix it. Now it's stuck booting to the screen with the distorted text at the top and the multiple acer logos at the bottom. I've tried a factory reset to clear the cache and that didn't help although it did say deleting user data and cache. I tried booting into recovery but found that the CWM that I thought I had installed wasn't installed and all I get is a fallen down android icon with a red exclamation over it. If I power up holding down the volume up key and then flicking the screen rotation switch I get it to display that it's in USB fastboot mode but if I type in adb devices it doesn't get listed as an attached device when hooked into my PC. One other note if I leave it at the distorted text and plug it into my PC via USB Windows 7 detects it as a MPT USB Device which it's not able to locate a driver for.
Ok, some additional information:
I was trying to get something out of the screen where I have the fallen down android with the red exclamation point over it and it seems that the default recovery is still installed in Android system recovery (3e). I can't seem to select any menu options on the screen but it does give some additional info. It looks like the eMMC may be partially or completely borked, I'm not sure which. Here's what's on the screen:
Android system recover (3e)
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Then in yellow text:
E: Can't open /dev/block/mmcblk0p5
(No such file or directory)
E: failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E: failed to mount /cache (No such file or directory)
This goes on for a bit of being unable to open various directories. Is there anyway at this point to re-lock the bootloader and erase traces of doing so? I find it hard to believe that unlocking the bootloader would cause what seems to be a hardware fault but I could be wrong.
Click to expand...
Click to collapse
Its a typical emmc brick, there's threads all over about this. All you can do is send it to acer for repair, sorry to say.
Plug it in and let try to boot on its own for an hour or so, what you want is failsafe, blue power led on but screen off. Then send it to Acer.
Sent from my Galaxy Nexus using xda app-developers app
I had been using my tablet normally and set it aside for a while. When I went back to it, it was stuck at the boot splash screen that is black with the white Google text on it. I tried rebooting several times and it would return to this state.
I booted into fastboot mode and went to recovery mode. The following errors were displayed at the bottom of the screen:
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/msm_sdcc.1/by-name/misc (I/O error)
E:failed to mount /cache (Invalid argument)
I tried doing "wipe data/factory reset". It says:
-- Wiping data...
Formatting /data...
... and then goes into many more errors regarding failures mount/open /cache
Thinking maybe the cache partition was bad, I went back to fastboot mode and issued the following command from my pc:
fastboot format cache
... but the command never returns (after an hour, it had not returned, so I cancelled)
The same happens if I try
fastboot format userdata
... it never returns.
I can't unlock the bootloader to attempt to flash a new image. I can issue command
fastboot oem unlock
and get the correct screen, but selecting unlock just locks up the tablet. I left it this way for a couple hours, no change.
So to summarize: I can access fastboot, I can access recovery, but I can't seem to affect any change that will recover the system.
I've exhausted everything I know to try. Any thoughts?
It's ironic because I hack on these all the time at work, but this was my personal unit that was stock and unrooted.
Yours is not a common situation, but there have been a few reported just this last week. Unless someone knows of a solution, like why the bootloader hangs at unlocking or if it can be reflashed (not possible AFAIK without unlocking), your only option seems to be warranty service. Sorry.
Pandae said:
Yours is not a common situation, but there have been a few reported just this last week. Unless someone knows of a solution, like why the bootloader hangs at unlocking or if it can be reflashed (not possible AFAIK without unlocking), your only option seems to be warranty service. Sorry.
Click to expand...
Click to collapse
Not what I wanted to hear, but thanks. I wonder if a recent update has stressed the file system or ECCM.
Someone posted a way to test the ECCM chip via command line, but I can't find it. Do you recall?
I've only heard of Android apps that test the eMMC's integrity, nothing that can be run from a PC.
I had a similar problem and when I used to enter 'fastboot devices" I used to get '?????? fastboot'. and the bootloader used to freeze but recovery mode (TWRP) was fine.
I then realized that I wasn't using the USB cable that came with the Nexus 7. When I switched cables. It recognized the device using 'fastboot devices'. Then I just ran the .bat file in the factory image files. I hope this helps.
I have the exact same issue that just started as of Tuesday, January 7th. I feel like I've exhausted all options and continue to get the mount cache error. I secretly suspect the storage went bad on that very cold day in NYC. My old Nexus 7 was off at the time and still works but the new one might have been on in my backpack walking around.
BootlegZani said:
I have the exact same issue that just started as of Tuesday, January 7th. I feel like I've exhausted all options and continue to get the mount cache error. I secretly suspect the storage went bad on that very cold day in NYC. My old Nexus 7 was off at the time and still works but the new one might have been on in my backpack walking around.
Click to expand...
Click to collapse
I'm on the same boat as you, guys. what a coincidence, even on the same date, January 7th. I was browsing on chrome and it froze a second, rebooted and got stuck at the Google Logo. Official KitKat, not rooted.
Nothing works, wiping data via Recovery gives a tonne of "mount /x" errors and flashing through fastboot is impossible because it gets stuck trying to unlock the bootloader.
I, too, think it's a hardware issue, probably with the storage. The only difference is that I am in the very warm Venezuela, so I think the NYC cold wasn't the problem!
The sad thing is my uncle bought it for me in Italy a month back because prices here are ridiculous, so now it's going to be a bit of a problem to return it to Amazon.it :crying::crying:
If any of you find a solution please post it!
Sorry for any misspellings.
Febo00 said:
I'm on the same boat as you, guys. what a coincidence, even on the same date, January 7th. I was browsing on chrome and it froze a second, rebooted and got stuck at the Google Logo. Official KitKat, not rooted.
Nothing works, wiping data via Recovery gives a tonne of "mount /x" errors and flashing through fastboot is impossible because it gets stuck trying to unlock the bootloader.
I, too, think it's a hardware issue, probably with the storage. The only difference is that I am in the very warm Venezuela, so I think the NYC cold wasn't the problem!
The sad thing is my uncle bought it for me in Italy a month back because prices here are ridiculous, so now it's going to be a bit of a problem to return it to Amazon.it :crying::crying:
If any of you find a solution please post it!
Sorry for any misspellings.
Click to expand...
Click to collapse
I honestly don't think there is a solution. I just contacted ASUS support via their website and started a RMA warranty repair.
Can you take a picture with another phone or something of the errors?
Also, can you try to mount the partitions manually in recovery
or go into recovery with adb shell and try to mount the partitions manually.
Also, what recovery do you have?
vaughnsphotoart said:
I had been using my tablet normally and set it aside for a while. When I went back to it, it was stuck at the boot splash screen that is black with the white Google text on it. I tried rebooting several times and it would return to this state.
I booted into fastboot mode and went to recovery mode. The following errors were displayed at the bottom of the screen:
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)
I tried doing "wipe data/factory reset". It says:
-- Wiping data...
Formatting /data...
... and then goes into many more errors regarding failures mount/open /cache
Thinking maybe the cache partition was bad, I went back to fastboot mode and issued the following command from my pc:
fastboot format cache
... but the command never returns (after an hour, it had not returned, so I cancelled)
The same happens if I try
fastboot format userdata
... it never returns.
I can't unlock the bootloader to attempt to flash a new image. I can issue command
fastboot oem unlock
and get the correct screen, but selecting unlock just locks up the tablet. I left it this way for a couple hours, no change.
So to summarize: I can access fastboot, I can access recovery, but I can't seem to affect any change that will recover the system.
I've exhausted everything I know to try. Any thoughts?
It's ironic because I hack on these all the time at work, but this was my personal unit that was stock and unrooted.
Click to expand...
Click to collapse
mine also
Mine developed this same problem on January 5th while watching a video. I just sent it off for warranty yesterday (Thursday). Was anyone using ART. I know I was
latenighter49 said:
Mine developed this same problem on January 5th while watching a video. I just sent it off for warranty yesterday (Thursday). Was anyone using ART. I know I was
Click to expand...
Click to collapse
I was using Dalvik.
I had a similar issue as you guys therefore I decided to use the factory images to solve the issue. Be warned: using it will erase everything on your device. Photos, music etc.
If you do not mind, proceed on to download the factory images but please download the correct ones and put them into your fastboot folder which will contain these files:
api
image-razor-jss15q(unzipped file)
systrace
adb
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-flo-flo-03.14.img
fastboot
flash-all
flash-all.sh
image razor-jss15q (this is the zip file)
notice
source.properties
Once everything is all in there, open command window by left shirt and right click on your mouse and select command window and put your devices into fastboot and type into the command window: flash-all .bat
And it'll restore your device back to stock
---------- Post added at 08:35 AM ---------- Previous post was at 08:32 AM ----------
Here's the link to the factory images for the Nexus 7 2013: https://developers.google.com/android/nexus/images#razor
Bobbi lim said:
I had a similar issue as you guys therefore I decided to use the factory images to solve the issue. Be warned: using it will erase everything on your device. Photos, music etc.
If you do not mind, proceed on to download the factory images but please download the correct ones and put them into your fastboot folder which will contain these files:
api
image-razor-jss15q(unzipped file)
systrace
adb
AdbWinApi.dll
AdbWinUsbApi.dll
bootloader-flo-flo-03.14.img
fastboot
flash-all
flash-all.sh
image razor-jss15q (this is the zip file)
notice
source.properties
Once everything is all in there, open command window by left shirt and right click on your mouse and select command window and put your devices into fastboot and type into the command window: flash-all .bat
And it'll restore your device back to stock
Click to expand...
Click to collapse
Hi, thanks for replying.
Correct me if I'm wrong, but you need to unlock the bootloader before flashing an image right? I tried it and it gets stuck trying to unlock it.
Code:
>fastboot oem unlock
<bootloader> Unlocking bootloader...
<bootloader> erasing userdata...
It got stuck trying to erase the data. Whic would be similar to the errors on recovery where it couldn't access the storage.
Febo00 said:
Hi, thanks for replying.
Correct me if I'm wrong, but you need to unlock the bootloader before flashing an image right? I tried it and it gets stuck trying to unlock it.
Code:
>fastboot oem unlock
<bootloader> Unlocking bootloader...
<bootloader> erasing userdata...
It got stuck trying to erase the data. Whic would be similar to the errors on recovery where it couldn't access the storage.
Click to expand...
Click to collapse
You are correct, flashing anything requires unlocking the bootloader. You aren't the only one who's getting stuck at unlocking, which could be a corrupted bootloader or a bad eMMC. I've never heard of solutions except to call for warranty repair.
Hy,
Today, i've the same issue. Nothing to do, i tried a lot of things like you.
Can't wipe cache or data, always failed to mount /cache.
My nexus was on stock rom locked, no root.
I'll go to the store, hope they can repair or change it quickly.
Lexso
Same here in middle east.
I also saw similar post several days ago.
http://forum.xda-developers.com/showthread.php?t=2644981
Anyway, I have exact the same symptom as you guys; locked bootloader and couldn't pass that stage.
I sent it to dubai for a RMA. Hope they will fix it and send it back to me ASAP.
Exactly the same thing just happened to me right now. The tablet restarted itself and do not pass the Google Logo. I did not unlock or whatever else my tablet.
In fact a week go i got a system update and since, my tablet is freezing or restarting without reasons. But that time it is for good. Is the ASUS warranty international ? Cause I bought my tablet in France (I am french) but I am living in Czech Republic.
donatien said:
Exactly the same thing just happened to me right now. The tablet restarted itself and do not pass the Google Logo. I did not unlock or whatever else my tablet.
In fact a week go i got a system update and since, my tablet is freezing or restarting without reasons. But that time it is for good. Is the ASUS warranty international ? Cause I bought my tablet in France (I am french) but I am living in Czech Republic.
Click to expand...
Click to collapse
Yes, it is global warranty. There must be a ASUS local service partner in Czech Republic.
Contact http://vip.asus.com/VIP2/Services/QuestionForm/TechQuery
and the customer service will let you know where you should contact.
I bought my N7 at Italy, but I'm fixing it in middle east.
You try unlocking its bootloader manually and don't use and program to do so
---------- Post added at 09:41 PM ---------- Previous post was at 09:38 PM ----------
If you return the device back for warranty , you'll come back with a reconditioned device.
So I'm hoping that you try unlocking its bootloader manually yourself.
Boot the nexus into fastboot and type into fastboot (cmd) : fastboot oem unlock
Than it'll unlock the device than use the factory images with the links I provided earlier to flash them
Are you adverse to completely wiping it?
If you aren't then maybe hard reset it, fastboot oem unlock, and then flash it with Kit-Kat?
I try to reinstall a rom after some unexpected self reboots. It is s-on and the bootloader is unlocked. I wiped the data, start the installation so far so good, no errors. After a reboot and half of hour of waiting nothing happens, no progress only the htc logo on screen.
I tried to reinstall the rom, i was able to start to recovery TWRP 3.0.0.-2 but if i try to factory reset it failed.
Updating partition details..
Failed to mount '/cache' '/system' '/data' (Invalid argument) and so on.
Boot to recovery posible, boot to download mode posible. If i use the advance options, then file manager i can see a lot of folders. Boot/cache/carrier/cota/data..... but they are all empty. I use adb in recovery mode an push mkfs.ext4 to the /tmp folder it works. I create a new folder (mkdir /p /data/media/0) it works. I push a new rom to the new folder it works.
Everything i try it ends in the same result -> storage not mount.
Some other ideas, hints or tips?
Try an older twrp. When updating the m9 it can take over an hour!. Just because it is sat at the htc screen people think it has frozen but it hasn't, you must wait at least an hour before you can even begin to think it may possibly, but probably hasnt, but could have, frozen. Yes it is one of those "you'll never know" moments.
Any mounting errors are usually recovery related as that handles the partitions when booting.
Twrp 2.9.0.1 which works fine for me: https://drive.google.com/file/d/0B4vTiHTBB629XzliRF9OaTdjZ00/view?usp=drivesdk
Double check the file size before you flash it with the regular fastboot (not htc_fastboot as that is for flashing firmwares).
Beamed in by telepathy.
deltaquadrant said:
I try to reinstall a rom after some unexpected self reboots. It is s-on and the bootloader is unlocked. I wiped the data, start the installation so far so good, no errors. After a reboot and half of hour of waiting nothing happens, no progress only the htc logo on screen.
I tried to reinstall the rom, i was able to start to recovery TWRP 3.0.0.-2 but if i try to factory reset it failed.
Updating partition details..
Failed to mount '/cache' '/system' '/data' (Invalid argument) and so on.
Boot to recovery posible, boot to download mode posible. If i use the advance options, then file manager i can see a lot of folders. Boot/cache/carrier/cota/data..... but they are all empty. I use adb in recovery mode an push mkfs.ext4 to the /tmp folder it works. I create a new folder (mkdir /p /data/media/0) it works. I push a new rom to the new folder it works.
Everything i try it ends in the same result -> storage not mount.
Some other ideas, hints or tips?
Click to expand...
Click to collapse
Did you fix it ?
One day after I charged my note 2 phone (SGH-T889), unplugged charger and started playing an app game for 5 mins. The phone suddenly crashed and began to restart nonstop but couldn't get passed the welcome screen animation. Eventually, it kept restarted and stuck in the logo screen.
I tried all the factory reset, wipe cache in recovery mode (holding the 3 buttons), taking out SD card, or all the basic stuff. The phone is not rooted at all. I even tried to install firmware through ADB (with digital signed software) but still failed to do so (even with some software to sign the zip file) because i got signature verification error. I also see failed to mount efs and system error. Also I wouldn't be able to get into recovery mode unless i hook up the usb, otherwise it will continuously fail to reboot in the logo screen.
I would like some guidance to reformat/ flash the whole phone with files linked or attached. Any official firmware version is fine for me. I only just learned ADB but I know nothing about odin. I don't want to root the phone if possible. Any help would be greatly appreciated. Thank you very much!
The stock ROM for your phone can be found here: http://www.sammobile.com/firmwares/database/SPH-L720T/
The stock ROM from sammobile is flashed via Odin as Odin is Samsung's official flashing method.
This the forum for the phone is here: http://forum.xda-developers.com/showthread.php?t=2621862
audit13 said:
The stock ROM for your phone can be found here: http://www.sammobile.com/firmwares/database/SPH-L720T/
The stock ROM from sammobile is flashed via Odin as Odin is Samsung's official flashing method.
This the forum for the phone is here: http://forum.xda-developers.com/showthread.php?t=2621862
Click to expand...
Click to collapse
I typed the wrong phone. I typed s4 instead of the note 2 model. Sorry.
Ok i flashed my note 2 with odin v3.11.2 with T889UVUCOH4_T889TMBCOH4_HOME.tar.mp5 in the AP tab in ordin. However, I get stuck in the green robot where there is a percentage bar after reboot. It gets stuck there then just reboot with the same thing happening. What do I do? Thanks.
I was using this odin tutorial http://odindownloader.com/tutorials/use-odin-downloader
aznsaiyan1029 said:
Ok i flashed my note 2 with odin v3.11.2 with T889UVUCOH4_T889TMBCOH4_HOME.tar.mp5 in the AP tab in ordin. However, I get stuck in the green robot where there is a percentage bar after reboot. It gets stuck there then just reboot with the same thing happening. What do I do? Thanks.
I was using this odin tutorial http://odindownloader.com/tutorials/use-odin-downloader
Click to expand...
Click to collapse
Ok Eventually it goes to recovery mode cwm.... Now i get even more E error. Pretty much fail to mount data, system, recover/ log, cache, etc..... even more errors T_T
Open Odin, uncheck everything except f reset time, flash rom, when you see the word reset in the status window, remove cable from the phone, remove battery, replace battery, boot into recovery, wipe, and reboot.
audit13 said:
Open Odin, uncheck everything except f reset time, flash rom, when you see the word reset in the status window, remove cable from the phone, remove battery, replace battery, boot into recovery, wipe, and reboot.
Click to expand...
Click to collapse
Doesn't work after i put back battery in. In fact, i had trouble going to cwm after that. When I try to go to cwm, it goes to the green robot for a split second and jump back to logo screem in loop.
What happens when you put the battery back in? Does it flash stock without errors? Cwm should not be in the phone after flashing stock.
aznsaiyan1029 said:
Doesn't work after i put back battery in. In fact, i had trouble going to cwm after that. When I try to go to cwm, it goes to the green robot for a split second and jump back to logo screem in loop.
Click to expand...
Click to collapse
and pretty much i have errors like these.
E:failed to mount /efs (No such file or directory)
E:failed to mount /system (No such file or directory)
# Manual mode #
-- Appling Multi-CSC...
E:failed to mount /system (No such file or directory)
E:Can't mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_recovery
E:failed to mount /data (No such file or directory)
E:Can't mount /data/log/recovery_log.txt
E:failed to mount /system (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
(a few more such errors)
audit13 said:
What happens when you put the battery back in? Does it flash stock without errors? Cwm should not be in the phone after flashing stock.
Click to expand...
Click to collapse
stuck in logo and when i try to wipe and factory reset liek u told me with holding vol up, power button, and home button, i go back to samsung logo loop
When booting to recovery, let the power button go as soon as the phone starts to boot but keep holding the home and volume up buttons.
audit13 said:
When booting to recovery, let the power button go as soon as the phone starts to boot but keep holding the home and volume up buttons.
Click to expand...
Click to collapse
I get only e: fail to mount efs and system ( didn't get fail to mount system the 1st time) now instead from the recovery screen. Wiped and got stuck in the sam sung start up animation, but then it becomes the same old logo reboot loop.
aznsaiyan1029 said:
I get only e: fail to mount efs and system ( didn't get fail to mount system the 1st time) now instead from the recovery screen. Wiped and got stuck in the sam sung start up animation, but then it becomes the same old logo reboot loop.
Click to expand...
Click to collapse
Ok this is what happened when I did the whole process again precisely as you told me. After I flashed with odin with (T889UVUCOH4_T889TMBCOH4_HOME.tar.md5), my phone is still in the download mode screen but everything is done downloading already. I unpluged usb, battery, micro SD card. When I try to reboot in recovery (I did your let go of the power button the moment the logo poped up), I am unable to do that, except I get reboot non stop and sometime I can see the green robot with the percentage bar screen. Eventually after multiple logo reboot loop, it just stuck at the screen and not do a thing.
Pretty much nothing I can do when I unplugged the phone from the USB, but when I plugged back the phone to the USB i can go to recovery mode somehow and I get all the e fail to mount errors for everything like i posted previously.
Also tried to install cwm through odin, but after odin said it pass and restarted with or without taking out the battery, I cant even go to recovery mode anymore....
omg my phone does the same thing except I cant flash at all keeps saying complete (write) operation failed. someone did resovle this please pm me or reply....
only thing that manages to connect with my phone but never complete is cwm4_fixed_for_cm7-odin.tar
I see the blue bar its complete but nothing ever happens
Sounds like there is a hardware problem with the phone. There could be a few causes but the failure to mount partitions means the memory may be damaged.
audit13 said:
Sounds like there is a hardware problem with the phone. There could be a few causes but the failure to mount partitions means the memory may be damaged.
Click to expand...
Click to collapse
it connects only to that? so what to do @audit13
I would look around to see if I could find a cheap note 2 with a smashed screen and working motherboard to switch the parts.
If you don't want to do that, maybe ask a cell shop for a repair estimate?
The phone is not worth too much so I would not spend a lot of money fixing it.
omg are you serious so thers nothing I can do? can I show you the pictures or something what is cwm4_fixed_for_cm-7-odin.tar? why is that only working ...im broke lol!!and a noob
Did you try flashing a stock ROM with a pit file?
audit13 said:
Did you try flashing a stock ROM with a pit file?
Click to expand...
Click to collapse
can u upload correct pit file cause all the pits file I have fails...but no I have not tried together let me try and upload pic