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
Hi there, so I'm having a bit of a problem. I tried to revive my old M9. I remember flashing it with a custom ROM (Android HD Revolution) and everything was fine. I left it since I got a new phone and today wanted to play around with my M9 again.
However, it would be stuck with the HTC Logo while loading, and my TWRP was gone, could no longer boot into it and my download mode was also screwed, as it gave me the error (failed to boot to download mode).
Anyway so I tried restoring to one of my TWRP backups, by mounting a TWRP img file first using my PC. It went fine, after that I booted into system and the HTC logo would be on white background and preventing me from using the screen, although funnily enough the system was functionally normally i.e. the volume keys worked and I could see it change on screen but, it was just as if I had a some kind of overlay and couldn't use the screen itself by touching.
I then tried to flash with the same custom ROM, but after installing it and rebooting the phone it was stuck in a boot loop, where it would shutdown and try to boot again.
So I turned it off using power up and home button, and tried to wipe the partition to install another ROM, using the same TWRP method I did above.
Only this time, I can't do anything: wipe, install, format etc. I get the error "Failed to mount '/data' (Invalid Argument)" "Failed to mount '/cache' (Invalid Argument)" whenever I try doing anything within TWRP. I can't even mount cache, system or Data. It is if they're not there.
And now my phone is back to where it started, i.e. infinite boot screen with HTC Logo and "This build is for etc..." text.
Note: Trying to change file system from ext4 to ext2/3 and back to ext4 does not fix the problem ,as the same errors pop up when trying to change file system.
90% chance the nand is goosed. 10% chance of recovering by flashing a stock firmware in download mode (same version as currently installed, external sd card method).
Twrp has a known issue for bricking devices at random.
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Janxr said:
I wanted to revert my mi 10t pro back to stock miui, but as I wanted to wipe the data, but I got errors like "E:Unable to decrypt FBE device. Code: 1000" or "Failed to mount '/metadata' (invalid argument) and some more. I was told to change the file system to EXT2 but this got me into a bootloop, where I land in fastboot every time I restart. I can navigate to recovery again tho.
Please help me. Im a bit desperate right now.
Edit: My recovery is twrp.
Click to expand...
Click to collapse
Just simply download and flash the Apollo's stock Fastboot ROM in fastboot mode
I tried flashing with with this: "apollo_global_images_V13.0.5.0.SJDMIXM_20220704.0000.00_12.0_global_3391fe8ef8"
is that the right version for my phone (bought in Germany)? I dont get an error while flashing but i just is not finishing. Its running for an hour now and still nothing happended. Ill update this if it finishes.
Edit: False alarm: After restarting the pc, i can connect again. But I still dont know what to do now.
I stopped the process after 2 hours and it got worse. In the recovery, i get the same issues as before, but my fastboot menu got replaced by onother one (I just see orange text that says fastboot). With that new fastboot menu I can not connect to my computer anymore.
Solved: I will never touch these Xiaomi tools again. platform-tools is just better and works
How did you solve the problem with the phone that cant connect to pc?