[Q] Samsung EPIC 4g BRICKED - won't boot!!! - Epic 4G Q&A, Help & Troubleshooting

Hello Everyone,
I tried flashing Cyanogen7 onto my rooted EPIC 4G using ClockworkMod Recovery v3.0.2.4 and this immediately bricked my phone and kept it from booting up.
When I try to boot up my phone it gets stuck at the SAMSUNG boot up screen and the four capacitive buttons (menu,home,back,search) say lit up. When I try to boot into Recovery Mode I get the following screen:​
ClockworkMod Recovery v3.0.2.4
- Reboot system now
- Apply update from sdcard
- Wipe data/factory reset
- Wipe cache partition
- Install zip from sdcard
- Backup and Restore
- Mounts and Storage
- Advaned
- Power Off
- *****Go Back*****
------------------------------------------------------------------
E:Missing bitmap icon_clockwork (Code -1)
ClockworkMod Recovery v3.0.2.4
E:failed to open /etc/recovery.fstab (No such file or directory)
E:unknown volume for path [/cache/recovery/command]
E:Can't mount /cache/recovery/command
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [/cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]​
When, for example, choose Wipe data/factory reset from the menu above it simply shows:​
-- Wiping data...
Formatting /data...
E:unknown volume "/data"
Formatting /cache...
E:unknown volume "/cache"
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard/.android_secure"
Data wipe complete.
E:unknown volume for path [/cache/recovery/log]
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:unknown volume for path [cache/recovery/last_log]
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:unknown volume for path [/cache/recovery/command]​
I'm really not sure what to do here. Any help would be appreciated.​
Thanks guys...

Have to tried to Odin back to stock and then retrying it? Your phone isn't bricked. It's not even close to being bricked. In fact, it's just fine. A simple couple clicks in Odin and your right back to stock let me know if ya need anything else

Ur not bricked go into download mode by holding 1 on the keyboard while powering on and Odin back to stock I am truly bricked where as my phone won't get into anything or even charge

tried looking into Odin...seems to only work on Windows...don't suppose there's an alternative that I could use on my Mac is there?

Heimdall. Read the directions twice.

And in the future, don't touch ROM Manager or any of the CWM versions it offers. Ever.
EDIT: This thread title gets more annoying every time I see it...

Failed to Detect Compatible Device
Hey all,
So I was able to get Heimdall up and running (thanks a bunch for that) but for some reason my phone doesn't seem to be able to connect to my computer when it's in downloading mode (screen where the yellow android with a shovel pops up). When I click 'Start' on Heimdall it just tells me that it cannot detect a compatible device. But I'm sure that my Epic is plugged in correctly.
The only thing I can think of is that my cord is messed up for some reason. Going to give it a try with a different one. Is there anything else it could be?

I don't know mac but the same thing happens on windows if after you installed samsung drivers you did not re boot pc. Maybe a problem you might run into is that when the phone is running and you connect it will install the drivers. Hopefully it installs what you need without a running connect.
Sent from my SPH-D700 using XDA App

ldartez said:
Hey all,
So I was able to get Heimdall up and running (thanks a bunch for that) but for some reason my phone doesn't seem to be able to connect to my computer when it's in downloading mode (screen where the yellow android with a shovel pops up). When I click 'Start' on Heimdall it just tells me that it cannot detect a compatible device. But I'm sure that my Epic is plugged in correctly.
The only thing I can think of is that my cord is messed up for some reason. Going to give it a try with a different one. Is there anything else it could be?
Click to expand...
Click to collapse
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X. Samsung fixed this for certain bootloaders running on certain devices however I'm unsure about the Epic 4G. I recommend starting a thread asking about it. If no one knows then unfortunately you'll have to use Windows or linux.

Benjamin Dobell said:
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X
Click to expand...
Click to collapse
This may be, but the stock Samsung cord is a notorious piece of horse ****. (Yes, it's that bad.)

Benjamin Dobell said:
I doubt it's your cord. Unfortunately Samsung have released a lot of dodgy secondary bootloaders that don't work on OS X. Samsung fixed this for certain bootloaders running on certain devices however I'm unsure about the Epic 4G. I recommend starting a thread asking about it. If no one knows then unfortunately you'll have to use Windows or linux.
Click to expand...
Click to collapse
I've tried starting a thread b4 on this and no one responded to it
Sent from my SPH-D700 using XDA Premium App

Honest suggestion? Just find a friend with a Windows computer and use Odin on his. Also, I've never had any problems with my Samsung data cable, but I also bought a blackberry micro cable for like $1.50 on amazon and free prime shipping, and it works great too.

Phone fixed!!
I ended up being able to fix my phone. The problem ended up being that Mac, for some reason, is not able to detect samsung phones (or at least mine..Epic 4g) while they are in Download Mode. I loaded the .msi drivers that I needed, Odin ( as opposed to heimdall for the sole reason that Heimdall requires Visual studio files to be installed on Windows) and the stock android image onto a flash drive.
I plugged these into a windows machine and everything worked perfectly.

k0nane said:
And in the future, don't touch ROM Manager or any of the CWM versions it offers. Ever.
EDIT: This thread title gets more annoying every time I see it...
Click to expand...
Click to collapse
if not rom manager or CWM then what do you usually use for flashing roms?

He's just saying don't use Rom Manager or the versions of CWM it specifically installs. Just use the CWM versions found here on the Epic 4G forums. Yes, CWM is how we flash roms.
ldartez said:
if not rom manager or CWM then what do you usually use for flashing roms?
Click to expand...
Click to collapse

well i just ran into this problem, with rooted stock froyo (think its EC05) and the customized purple cwm for the epic... so clearly using the recovery image found on these forums is NOT foulproof... and all i wanted to do was perform a back up so i could try out a eg22 rom... sigh... anyway thanks to odin im back up but now i have to re do everything and i was not able to back up my STOCK!!! image. is there a different recovery available or perhaps one that works?

duplissi said:
well i just ran into this problem, with rooted stock froyo (think its EC05) and the customized purple cwm for the epic... so clearly using the recovery image found on these forums is NOT foulproof... and all i wanted to do was perform a back up so i could try out a eg22 rom... sigh... anyway thanks to odin im back up but now i have to re do everything and i was not able to back up my STOCK!!! image. is there a different recovery available or perhaps one that works?
Click to expand...
Click to collapse
Did you go into recovery with the 3 finger method or did you use quck boot or ROM manager? Never use any of those when doing a backup or restore. The purple recovery worked well for me when I needed it but now am using Bonsai's recovery rooting with Masterkey Unlocker. You can find Bonsai's site by googling Bonsai Android.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
Did you go into recovery with the 3 finger method or did you use quck boot or ROM manager? Never use any of those when doing a backup or restore. The purple recovery worked well for me when I needed it but now am using Bonsai's recovery rooting with Masterkey Unlocker. You can find Bonsai's site by googling Bonsai Android.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
yeah, i used the three finger method...
bonsai eh? ill have to look it up. edit: or i could just click the link in your sig... lol
off topic: im new to the epic (finally retired my weary hero), so anything you would recommend?

duplissi said:
yeah, i used the three finger method...
bonsai eh? ill have to look it up. edit: or i could just click the link in your sig... lol
off topic: im new to the epic (finally retired my weary hero), so anything you would recommend?
Click to expand...
Click to collapse
I try not to advertise the link in the sig (shhh). I do recommend trying the Masterkey Unlocker if you are unhappy with CWM 3.1.0.1. It is a nice graphical interface and works well. You can Odin to either EB13 or EC05 stock, root with the MK and then 3 finger to nand backup your phone or use Titanium Backup.
Sent from my SPH-D700 using XDA App

Related

[Q] Recovery not working, can't install ROM [Solved]

Hey all, I was trying to switch from G2 HBOOT to the Desire Z HBOOT. I was following the guide and it seemed to work ok. I am not a complete noob when it comes to flashing ROM and using ADB, but it seems I have done something wrong. I don't think my phone is bricked, but I can't do anything with it.
I can't seem to boot into my current ROM (an MIUI ROM), so I am trying to reinstall the ROM. I can reboot into bootloader and recovery from ADB. But when I reboot into Clockwork Recovery, none of the options work. Below the yellow line in CWR I see the following:
ClockworkMod Recovery v.3.0.2.4
E:Can't mount /cache/recovery/command
E:Cant mount /cache/recovery/log
E:Can't open cache/recovery/log
E:Can't mount cache/recovery/last_log
E:Can't open /cache/recovery/last_log
When I select one options (e.g. Install zip from sdcard) it just gives me a black screen with the ROM Manager logo (the funny black hat with the orange circle).
All I want to do is flash a ROM so I can use my phone. I don't care if I have to do a full wipe of everything. I tried finding a way to update CWR, but the link in the thread doesn't seem to point anywhere. I also searched for a way to flash a ROM using fastboot, but none of the options seem to be for the G2.
Options I could use most:
1. How to mount system and wipe
2. How to install ROM via adb/fastboot
3. How to install the latest ClockworkMod Recovery
Any help would be appreciated.
First thing is your SD Card sound?
Are you sure changing hboot work 100% ?
Should be able to mount/wipe from recovery,
you can flash a recovery from fastboot,download the recovery .img look around for the instructions goes something like flash recovery recovery.img
Stick with v.3.0.2.4 as well
http://download.clockworkmod.com/recoveries/
You need the vision version
Or as the two other posts mention don't use the power button to select things!!!!!!!
The errors you are getting are normal after changing hboots.
What button are you using to select items in cwm?
Sent from my HTC Vision using Tapatalk
Don't use power to select stuff in clockwork.
use either trackpad or camera button.
-Nipqer
You know guys, I make a promise to myself every morning that I won't think like, act like, or in any way be like a noob. Today I broke my promise.
Thanks guys. Honestly, I never had a problem using the power button to select options before, so that's why this was totally freaking me out and I didn't even think that that might be the problem. But now I have installed a new ROM and am up and running again.
(quietly to myself)
I will not be a noob...I will not be a noob...I will not be a noob

Can no longer flash a rom

So I have an issue. After I was formatted system and wiped my data to install 1.9 I accidentally reboot the phone before I installed the rom, now when I'm in clockwork mod I get a
E:unknown volume for path [/sdcard]
E:Can't mount /sdcard/
error whenever I try to select the zip to install. How do I fix this?
The phone won't load past the boot screen either because there is no rom installed. I even tried to reset it to stock and it won't load past the startup screen
This happened to mine too. Looking for answers
There's always a usb jig to force it into download mode. Then just reflash a tar. Look for the thread "the jig is up"
Sent from my SPH-D710 using xda premium
This happened to me. I odin'd an older version of cwm, and installed a rom from the internal storage. For some reason the older one worked for me.
Sent from my SPH-D710 using XDA App
Or you can try to mount USB in mounts and storage, transfer rom to internal storage, and flash from there.
Sent from my SPH-D710 using XDA App
Happened to me tons of times. Just Odin the recovery again and it'll work fine.
OP, much like others have suggested, boot into odin mode and reflash recovery
Having major issues here please help and thanks!
My phone-Samsung Galaxy S2 Epic 4G Touch (Sprint) SPH-D710
RUNNING AOKP ICS ROM DOWNLOADED FROM EPIC4GTOUCHROOT DOT COM
From my understanding i should have flashed this rom through odin instead of my rouge recovery.I enjoyed the rom for a day or two than decided to flash back to a different rom and rouge recovery no longer showed up. Anroid system recovery <3e> shows up instead. i went to try to flash a rom here and it started than the android guy came up laying down with the chest area open and an exclamation mark above him than said
E: failed to verify whole-file signature
E: signature verification failed
installation aborted.
My computer no longer recognizes my phone iv tried re-installing the drivers and no luck. I've tried installing from sd card and still no luck. Ive tried mobile odin and it doesnt pick up anything in my sd card.
SOMEONE PLEASE HELP WHAT DO I DO???
-THANKS

CWM help please!

Here's the scenario. I was going to update to the latest starburst Rom so I made a back up with CWM. After it backed, I got a long error message. I thought nothing of it and reboooted the phone.
It sat there with the yellow triangle for a couple of minutes and never booted. I booted into CWM and this is what it reads:
E: failed to open /etc/recovery.fstab ( no such file or directory )
E: unknown volume for path ( /cache/recovery/command )
E: can't mount /cache/recover/command
E: can't mount/open /cache/recovery/last_log
What the heck is this!? It won't go into the restore, won't go into the installzip from sd card option...I can't even factory restore if I want.
I can still boot into odin. It's like the phones sd storage just took a dump. Is there anything I can do? I've never had an issue like this before.
Sent from my ADR6400L using XDA App
The usual response is to flash another ROM with ODIN, then start the process all over. ODIN will get you up and running.
smikwily said:
The usual response is to flash another ROM with ODIN, then start the process all over. ODIN will get you up and running.
Click to expand...
Click to collapse
^THIS. Due to how the kernel and recovery is stored on this phone it may cause the recovery to break. Flash another kernel with CWM and you'll be good to go. Chris41g's Stock repacked with CWM should suffice.. If not, flash ACS' stock tar then start over.
chunology said:
^THIS. Due to how the kernel and recovery is stored on this phone it may cause the recovery to break. Flash another kernel with CWM and you'll be good to go. Chris41g's Stock repacked with CWM should suffice.. If not, flash ACS' stock tar then start over.
Click to expand...
Click to collapse
I can't even get CWM to install a zip file from the sd card. It gives an error and returns to previous menu. Do I need to rename the kernel update.zip to get it to flash?
I'm pretty sure I won't be able to do anything with the current CWM installed. Flashing ACS'S tar thru odin should do the trick correct?
Sent from my ADR6400L using XDA App
Ben's said:
Here's the scenario. I was going to update to the latest starburst Rom so I made a back up with CWM. After it backed, I got a long error message. I thought nothing of it and reboooted the phone.
It sat there with the yellow triangle for a couple of minutes and never booted. I booted into CWM and this is what it reads:
E: failed to open /etc/recovery.fstab ( no such file or directory )
E: unknown volume for path ( /cache/recovery/command )
E: can't mount /cache/recover/command
E: can't mount/open /cache/recovery/last_log
What the heck is this!? It won't go into the restore, won't go into the installzip from sd card option...I can't even factory restore if I want.
I can still boot into odin. It's like the phones sd storage just took a dump. Is there anything I can do? I've never had an issue like this before.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Use Odin to root your phone again and it'll fix the recovery.
[Insert witty signature here]
Just had this happen today whole trying to install syndicate ice. I used Odin to flash lost kernel and am back in business
Sent from my SPH-D710 using XDA App

[Q]+1 A100 bricked

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

Absolutely Perplexed...

I currently have a T-Mobile Galaxy S2 with CM10.1.
I flashed my phone to the STOCK ROM recently, and flashed the UVLE1 radio along with it. However, after I flashed it with CWM, my phone went into a boot loop.
I decided to flash back to CM10.1 but it freezes every time it reaches the cache. I also tried to DARKSIDE SUPERWIPE everything, but it freezes at the cache as well. I think my cache partition is corrupted, but I have no idea as to how I can fix it...
I tried to purchase a USB Jig in order to reflash the phone with ODIN. I can get into Downloading mode, but neither ODIN nor Kies can recognize my computer. I just don't know what to do now.
I hope someone can help me.
Thanks!
FosuBoy said:
I currently have a T-Mobile Galaxy S2 with CM10.1.
I flashed my phone to the STOCK ROM recently, and flashed the UVLE1 radio along with it. However, after I flashed it with CWM, my phone went into a boot loop.
I decided to flash back to CM10.1 but it freezes every time it reaches the cache. I also tried to DARKSIDE SUPERWIPE everything, but it freezes at the cache as well. I think my cache partition is corrupted, but I have no idea as to how I can fix it...
I tried to purchase a USB Jig in order to reflash the phone with ODIN. I can get into Downloading mode, but neither ODIN nor Kies can recognize my computer. I just don't know what to do now.
I hope someone can help me.
Thanks!
Click to expand...
Click to collapse
Have you installed your phone drivers on your computer? Did you try to fix permissions or format system then flash back CM10.1 and proper radio / gapps?
jonmassot said:
Have you installed your phone drivers on your computer? Did you try to fix permissions or format system then flash back CM10.1 and proper radio / gapps?
Click to expand...
Click to collapse
Yes, I've installed the phone drivers. I've also tried to fix permissions. I've formatted the system and data many times with Darkside's Superwipe, but it always freezes at the cache. I've even tried to flash to CM10.1. No avail. It just places CM10.1 on a bootloop.
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
FosuBoy said:
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
Click to expand...
Click to collapse
Have you tried plugin it to another computer? I remember when my computer crashed while I was doing a ODIN install, after reboot, my computer didn't recognized my smartphone... Might help!
---------- Post added at 09:17 AM ---------- Previous post was at 08:53 AM ----------
FosuBoy said:
Bump.... I am desperate to fix this...
I also noted that every time I go on recovery, I see this.
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Every now and then it posts an error saying that it can't mount the sd-ext itself, but i am able to access it just fine.
Click to expand...
Click to collapse
Also, did you try to completly erase your internal sd card and completly reinstall everything? And if I'm not wrong, with CM10.1, latest, you don't need to use darkside cachewipe...
jonmassot said:
Have you tried plugin it to another computer? I remember when my computer crashed while I was doing a ODIN install, after reboot, my computer didn't recognized my smartphone... Might help!
---------- Post added at 09:17 AM ---------- Previous post was at 08:53 AM ----------
Also, did you try to completly erase your internal sd card and completly reinstall everything? And if I'm not wrong, with CM10.1, latest, you don't need to use darkside cachewipe...
Click to expand...
Click to collapse
I'll try and plug it into another computer. But how exactly do I go about erasing my internal sd card?
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
gc84245 said:
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Kies doesn't ask for my serial number... just a recovery code. Is it possible for me to mount my storage to the PC through the CWM? Every time I try to do that, it doesn't work at all either.
------------
UPDATE! I found where to put my serial number!
Will keep you posted...
gc84245 said:
Plug in your phone to your computer and open up kies. Select "emergency firmware recovery", Kies will probably say it can't detect your phone and ask you to enter serial number. Enter serial number from under the battery.
Don't use dark side wipe unless you know for sure that it is required!! Otherwise it can mess up your phone.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
It tells me that the "SGH-T989" does not support 'initialising.' I'm devastated.
That's too bad it didn't work. Something similar happened to me. I remember kies couldn't recognize my phone either and asked me to input serial number... That was a while ago though, so I cant remember all of the details. I still think kies is your best bet, it took a while to work for me too.
Sent from my Nexus 7 using xda app-developers app
I think the problem here is that my computers cannot recognize the phone, no matter what. I think some part of the phone is corrupted to the point where it does not even want to boot a ROM. I've attempted to narrow the corruption down to the cache partition.
Is there anyway I can re-format the cache without using a PC? CWM Recovery cannot access the cache without freezing. Is there a ZIP file I can download that can format everything?
Better yet, is there a ROM that I can flash that will re-flash the cache as well? I tried re-flashing CM10.1 and nothing happens. Even restoring different nandroids makes the CWM Recovery freeze at the cache!
I've also wiped the Dalvik cache countless times, no avail. Will a TWRP recovery work? I have no idea what it is.
FosuBoy said:
I'll try and plug it into another computer. But how exactly do I go about erasing my internal sd card?
Click to expand...
Click to collapse
With TWRP, you can just erase everything in tools or advanced, can't remember wich one, but I don't know about CMW.
Try re-installing all you drivers, meaning uninstall, reboot, re-install and see if your computer recognize it again.
Never use Darkside Superwipe with CWM 6.x.x.x, you get a bootloop.
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
------------------------------
nivekx9 said:
Never use Darkside Superwipe with CWM 6.x.x.x, you get a bootloop.
Click to expand...
Click to collapse
Ugh, I know this. I have CWM 5.x.x.x.
FosuBoy said:
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
------------------------------
Ugh, I know this. I have CWM 5.x.x.x.
Click to expand...
Click to collapse
The only thing left, is to try it on another computer, worked for me.
FosuBoy said:
I just reinstalled the drivers on my computer and followed the right protocol. Nothing. To set things straight, I've probably used every method possible to fix this thing. Nandroid Recovery, ROM Flashing, and Kies have all been fruitless attempts to get this thing to work.
.
Click to expand...
Click to collapse
Odin back to stock.
Edit: sorry just reread your OP and Odin isn't working. Try flashing TWRP and see if it helps at all.
I'll get you the link.
Update! My computer seems to recognize the device, but it says that the 'device is malfunctioned' and lists it as an unknown device. However, I know where the Samsung USB drivers are located. Could I just manually install a driver onto the 'unknown device?'
I'll try and get a picture of the drivers because it seems like there is more than one that I can install...
TWRP 2.5.0.0
I've flashed the TWRP.. now it freezes on the teamwin logo. 5 steps backwards now.. I can't access the ROM nor do I have a way to recover any files.
FosuBoy said:
I've flashed the TWRP.. now it freezes on the teamwin logo. 5 steps backwards now.. I can't access the ROM nor do I have a way to recover any files.
Click to expand...
Click to collapse
It sounds like you have a NAND problem. I am searching Google but haven't found anything helpful yet. Have you tried using Odin on all the different USB ports? Or like someone else said, another computer?

Categories

Resources