Related
Hey how's it going? I'm stuck in the boot loader. I had CM7 installed before and it got stuck in a loop. So, tried wiping cache/data and dalvik. Dalvik couldn't be wiped. Tried installing another rom and that didn't work at all. I'm able to get into recovery mode without a problem, but now I'm getting stuck on the HTC screen.
Error wise, I'm getting the following:
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
I've looked around for some help and couldn't find much help, but it was a recovery issue/ Don't have a backup or anything, and don't mind wiping everything and starting from scratch anyways.
I'm on a mac as of now but can grab a windows computer if needed. Any ideas?
Well, last resort should be to flash the ruu file that will get you back to stock. Honestly, this sounds like a hardware failure though. Try going to recovery, fixing permissions, then go to mounts and storage in recovery and manually mount those things and see what, if any errors you get.
Sent from my Incredible 2 using xda premium
Not a hardware failure at all. You just need to reflash your recovery Just follow the Guide #6 in my guides directory, just the part about reflashing the recovery.
Thanks for the replies and glad to hear it isn't a hardware failure. So as I said I'm on my mac and the phone doesn't come up under devices at all. Do I need the drivers still on the mac?
I was able to load the sd card onto my computer and throw the cam file in the root of the card. Is there a way to flash memory from that through clockwork or does it have to be through command prompt?
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
Hello all,
First some background
as you can tell i have an xperia s. I had initially rooted it in .45, installed CWM, installed .55 system and CWM again, and had a perfectly healthy tool on my hands. A week ago i realized it had suddenly started to eat up the battery in half a day. I uninstalled everything i could think of, and nothing happened. So i though of going back to a previous CWM backup.
That proved impossible since the backup sequence always stopped at a formatting error. After a dozen attempts i lost my patience and used flashtool to install and root .45. Then CWM, then OTA to .55, and then CWM again (it was lost after OTA update to .55).
Took me about a day to put everything back.
That was yesterday.
Today i tried to install the camera mod from xperia V (had it before and truly the focusing is faster, cannot vouch for anything else though)
And there it was:
Instructions for installing the zip require to wipe cache first.
Through CWM when i tried to wipe cache, both ways available, i always get the same error
make_extf4fs failed on /dev/block/mmcblk0p13
I have seen that before on my phone but everything works OK in normal mode. Only time problems arise is when i need CWM...
I have also seen it reported in xda but nobody posted a solution.
Any thoughts?
I cannot take it back as defective either, because it works ok:silly:
I decided to take it a step further.
Went into CWM and chose wipe data/factory reset.
Here is the log
CWM recovery for 2012 Xperia V2
by kenjidct
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
--Wiping data...
Formatting /data...
e: format_volume: make_extf4fs failed on /dev/block/mmcblk0p14
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure
data wipe complete
I tried it again right after that and it completed with no errors.
THen tried to format cache and -surprise- no errors...
So i went on to restore my previous backup.
checking MD5 sums
Restoring system
restoring data
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
Error while formatting data
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
Tried to format data after that and again error at block 14
WTF??????????????????
AGAIN???????????
What do you make of this?
Guys. nobody knows, or nobody has the same errors?
I have exactly same issues.. i am running .45 rooted firmware o my SXS.. help us guys
sagardrokr said:
I have exactly same issues.. i am running .45 rooted firmware o my SXS.. help us guys
Click to expand...
Click to collapse
can u connect it to fastboot?
if u yes, from fastboot: fastboot erase cache. fastboot format cache. i think that flashing ftf full wipe can fix that too.
I am having this issue even after multiple(2-3) full wipes.
Let me be clear about that.
First time i encountered the situation i though it was just a glitch. So i went all out and erased everything. Reinstalled .45 , rooted, then OTA-ed to .55, then installed CWM (i actually installed it first at .45 but during the update to .55 it was lost, so i installed it again.) Problem insisted , so i re-did it all a couple of times until i run out of time to keep installing everything!!!
Now, as for the "manual" format you are referring to. How do we do that?
Can we do that through flash tool?
I was thinking of connecting the phone to the flashtool in flashmode and choosing only wipe cache.
But in order to do that i first have to choose an ftf and i was worried that i might erase everything again. I absolutely have no time to be installing everything again...!!!
m1st3r1 said:
can u connect it to fastboot?
if u yes, from fastboot: fastboot erase cache. fastboot format cache. i think that flashing ftf full wipe can fix that too.
Click to expand...
Click to collapse
I never tried but i think i can connect it to fastboot. But i am not much aware of fastboot process. SO i am hesitating to flash it..Though i'll give a try n will let you know the results.
sagardrokr said:
I never tried but i think i can connect it to fastboot. But i am not much aware of fastboot process. SO i am hesitating to flash it..Though i'll give a try n will let you know the results.
Click to expand...
Click to collapse
Don't worry my friend. The phone does everything it is supposed to do.
I have tested it as hard as i can but no error pops up during any operations.
Just when you format cache through CWM
schumifer1 said:
Don't worry my friend. The phone does everything it is supposed to do.
I have tested it as hard as i can but no error pops up during any operations.
Just when you format cache through CWM
Click to expand...
Click to collapse
DId you try the fastboot method?? Any success to pass through the errors?? We cant even install .55 firmware because of those errors..
schumifer1 said:
I decided to take it a step further.
Went into CWM and chose wipe data/factory reset.
Here is the log
CWM recovery for 2012 Xperia V2
by kenjidct
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
--Wiping data...
Formatting /data...
e: format_volume: make_extf4fs failed on /dev/block/mmcblk0p14
formatting /cache
formatting /sd-ext
formatting /sdcard/.android_secure
data wipe complete
I tried it again right after that and it completed with no errors.
THen tried to format cache and -surprise- no errors...
So i went on to restore my previous backup.
checking MD5 sums
Restoring system
restoring data
e: format_volume make_extf4fs failed on /dev/block/mmcblk0p14
Error while formatting data
e: can't mount /cache/recovery/command
e: can't mount /cache/recovery/log
e: can't open /cache/recovery/log
e: can't mount /cache/recovery/last_log
e: can't open /cache/recovery/last_log
Tried to format data after that and again error at block 14
WTF??????????????????
AGAIN???????????
What do you make of this?
Click to expand...
Click to collapse
Same problems here. error at block 13. Is there any fix yet? TIA
edit: So block 12 is for /system and block 13 for /cache I think and block 14 is for /data or sdcard. errors on all of that.
edit again today: Found the fix HERE. by just installing via fastboot ics17.elf (Advance Stock ICS Kernel)
I have the same errors again and again. Now each time i want to change the rom I have to flash Sony .45 rom, upgrade to .55 then root and flash CWM. It's either that or get stuck in à bootloop.
I've sent full error log on another thread.
Sent from my LT26i using xda app-developers app
silvershiver0323 said:
edit again today: Found the fix HERE. by just installing via fastboot ics17.elf (Advance Stock ICS Kernel)
Click to expand...
Click to collapse
Would be great but kernel flashing is for unlocked bootloader only. Mine is locked.
Sent from my LT26i using xda app-developers app
Lodotux said:
Would be great but kernel flashing is for unlocked bootloader only. Mine is locked.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
That's true. My bootloader is locked as well
isn't there way to track the problem and see what causes theses errors. apprently there aret terribly specific to some phones or some roms, stock or custom.
there should be a way to make a log of what's going on and have a dev help us with this.
here's the link i posted my error log with cwm :
http://forum.xda-developers.com/showpost.php?p=40564226&postcount=1445
Lodotux said:
isn't there way to track the problem and see what causes theses errors. apprently there aret terribly specific to some phones or some roms, stock or custom.
there should be a way to make a log of what's going on and have a dev help us with this.
here's the link i posted my error log with cwm :
http://forum.xda-developers.com/showpost.php?p=40564226&postcount=1445
Click to expand...
Click to collapse
According to Arakmar, the CWM formatting issue was fixed by updating the MMC storage driver in the kernel. As far as I know, drivers are a part of the kernel source which is then compiled to give us the zImage. Compiled zImage+ramdisk=custom kernel
As custom zImage cannot be installed on locked bootloader, this method won't work. There must be some other workaround to this problem..
abcdjdj said:
According to Arakmar, the CWM formatting issue was fixed by updating the MMC storage driver in the kernel. As far as I know, drivers are a part of the kernel source which is then compiled to give us the zImage. Compiled zImage+ramdisk=custom kernel
As custom zImage cannot be installed on locked bootloader, this method won't work. There must be some other workaround to this problem..
Click to expand...
Click to collapse
that's this workaround we're trying to find. i've been told that a recent install of busybox should fix the problem but AFAIK it does'nt work on my phone.
Edit : problem is still here. I've tried to change the rom i'm using today, first, by flashing CWM v2, but get the same errors.
Had to flash .45 firmware, upgrade to .55 by sony upgrade, root, flash CWM and then wipe and install rom.
help
I'm also having the same issue
B4 my phone was fine
But after my phone had microphone issue.and Sony service center said,they
Had 2 change the motherboard
Now with new board,I had that 'cant mount' cwm issue
So please help me fix this
I cant use nandroid backup.cant flash...
Tried different Rom except. 45
Plz help...this is a serious issue 4 me...seen different thread,,, but no sol.
Locked downloader here
I had those formatting errors sometimes, too. For me, it was solved by formatting /sdcard (first backing it up), after that, I could format other areas, too.
Anime13 said:
I'm also having the same issue
B4 my phone was fine
But after my phone had microphone issue.and Sony service center said,they
Had 2 change the motherboard
Now with new board,I had that 'cant mount' cwm issue
So please help me fix this
I cant use nandroid backup.cant flash...
Tried different Rom except. 45
Plz help...this is a serious issue 4 me...seen different thread,,, but no sol.
Locked downloader here
Click to expand...
Click to collapse
Same for me too. My XS also needed a motherboard replacement. For everyone, if possible then just unlock your boot loader and flash a kernel in which this bug has been fixed. Hopefully in the JB update Sony will update the mmc driver.
Sent from my LT26i using xda app-developers app
Sliverer said:
I had those formatting errors sometimes, too. For me, it was solved by formatting /sdcard (first backing it up), after that, I could format other areas, too.
Click to expand...
Click to collapse
Deleting 20 giga and restoring it is certainly not my idea of a quick backup and restore .
For the time it would take to copy 20 giga back and forth i could have installed everything again by hand..
Good info though.
I have noticed that formatting /data also lets us use it without the block errors
Hi, I recently got an update notice for my Nexus 7 (2013), previous to this I hadn't rooted or done anything weird with the unit at all. During the update something must have gone wrong because I was left with the robot with a red triangle, and its not in a continuous bootloop.
I've done lots of reading around to try and fix my unit, and because i didn't enable usb debugging I'm unable to use the ADB toolkit fixes so I have to rule these out.
I have been able to get into the bootloader menu and can use fastboot commands to try and unlock my unit. I follow the commands on the unit and select unlock with the volume control but when it gets to erase userdata it just hangs and does nothing.
Every command I try usually gives me the error FAILED (command write failed (Unknown error).
I've tried different USB ports and different cables, and I've tried using a PC and a MAC.
I have tried erase cache/user data in the recovery menu, but this does nothing.
I have emailed Asus UK to try and arrange a warranty return, but because the unit was bought in the USA as a gift for me, I'm not covered and will have to pay.
Is there anything I could try to fix my unit? I really wish I hadn't bothered clicking update now!! I've spent about 10 hours trying to fix this thing now. Any advice would be appreciated - my wife bought it for me and she is quite upset that an update has made it completely useless and Asus don't want to help.
If it is beyond repair, does anyone have any idea what ASUS charge to fix these things?
Thanks for reading
as long as you can access the bootloader and fast boot commands, it can be saved. You need to download the full image from Google. Search for "nexus 7 images" or something of the sort and you should find a code.Google link with images to download. Grab the ones for your device and you can extract the files and run the "flash all.bat" to flash all the needed images. If you need help feel free to pm me and I can get you fixed up.
prshosting.org
prsterero said:
as long as you can access the bootloader and fast boot commands, it can be saved. You need to download the full image from Google. Search for "nexus 7 images" or something of the sort and you should find a code.Google link with images to download. Grab the ones for your device and you can extract the files and run the "flash all.bat" to flash all the needed images. If you need help feel free to pm me and I can get you fixed up.
prshosting.org
Click to expand...
Click to collapse
Thanks for your help and for giving me hope!
I have downloaded images and tried to flash all.bat, but they all seem to rely on being able to unlock the bootloader, and when I try and do that it always hangs on "erasing userdata". I've left it for 5 or 6 hours and it just doesn't work.
I'm able to access ADB sideload functionality - will that give me another chance of fixing this thing?
taviboy said:
Thanks for your help and for giving me hope!
I have downloaded images and tried to flash all.bat, but they all seem to rely on being able to unlock the bootloader, and when I try and do that it always hangs on "erasing userdata". I've left it for 5 or 6 hours and it just doesn't work.
I'm able to access ADB sideload functionality - will that give me another chance of fixing this thing?
Click to expand...
Click to collapse
I don't really have experience with adb sideload, but i do know the factory images should flash fine. How much memory do you have available when trying to do the unlock? Maybe your system can't supply enough. Another thing you can try is reloading the drivers from scratch, but i would try the memory part first. You can also use "fastboot -w" to erase userdata manually then try flashing the images again.
prsterero said:
I don't really have experience with adb sideload, but i do know the factory images should flash fine. How much memory do you have available when trying to do the unlock? Maybe your system can't supply enough. Another thing you can try is reloading the drivers from scratch, but i would try the memory part first. You can also use "fastboot -w" to erase userdata manually then try flashing the images again.
Click to expand...
Click to collapse
Okay, will give it go once more. I think the drivers are okay because i get fastboot devices showing me my unit, so its communicating with it ok I think.
What do you mean when you say how much memory do I have available? On my laptop? How could i change that?
Tried fastboot -w
It still hangs on erasing 'userdata'...
There is something funny about userdata for some reason - when I try and unlock the boatloader it hangs on the same thing.
Is there any way of unlocking without erasing userdata?
Try go to Stock Recovery (you said you hadnt rooted your phone yet), do a factory reset and see if it works.
taviboy said:
Tried fastboot -w
It still hangs on erasing 'userdata'...
There is something funny about userdata for some reason - when I try and unlock the boatloader it hangs on the same thing.
Is there any way of unlocking without erasing userdata?
Click to expand...
Click to collapse
Unlocking automatically erases userdata, so i don't believe there is. I can try and help you out via teamviewer if you want. If nothing works then it may be a bad EMMC flash chip, which means there's nothing we can do and would have to be sent for warranty, which i know is an issue for you.
edit: I got another idea. What about overriding the data partition with the one included with the factory images then trying the unlock?
opticaldh said:
Try go to Stock Recovery (you said you hadnt rooted your phone yet), do a factory reset and see if it works.
Click to expand...
Click to collapse
How do I do that?
I've tried to flash a factory image, and I get command write failed (invalid argument) come up - it really doesn't want to play ball.
taviboy said:
How do I do that?
I've tried to flash a factory image, and I get command write failed (invalid argument) come up - it really doesn't want to play ball.
Click to expand...
Click to collapse
when you are at bootloader, choose Recovery. If you are on stock Recover, there should be an android guy lying with an red triangle on his belly. You will have to press the combination Power + Volume up (power first then volme up), then you should see the option to do a factory reset.
opticaldh said:
when you are at bootloader, choose Recovery. If you are on stock Recover, there should be an android guy lying with an red triangle on his belly. You will have to press the combination Power + Volume up (power first then volme up), then you should see the option to do a factory reset.
Click to expand...
Click to collapse
Okay, tried to flash back to factory, not working - says command write failed.
When I go into recovery I have 4 options: Reboot, Apply update (sideload), WipeData/Factory reset, Wipe Cache
Choosing wipe/factory reset:
Says formatting /data...
formatting cache...
Data wipe complete
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/log etc etc
E:failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error)
E:failed to mount /cache (invalid argument)
Nothing seems to work...
prsterero said:
edit: I got another idea. What about overriding the data partition with the one included with the factory images then trying the unlock?
Click to expand...
Click to collapse
How would I go about doing that?
taviboy said:
Okay, tried to flash back to factory, not working - says command write failed.
When I go into recovery I have 4 options: Reboot, Apply update (sideload), WipeData/Factory reset, Wipe Cache
Choosing wipe/factory reset:
Says formatting /data...
formatting cache...
Data wipe complete
E:failed to mount /cache (invalid argument)
E:can't mount /cache/recovery/log etc etc
E:failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error)
E:failed to mount /cache (invalid argument)
Nothing seems to work...
Click to expand...
Click to collapse
It seems a lot of people that get the invalid argument are because of a USB port or jacked up stock recovery image. Can you manually flash the recovery image then userdata image?
---------- Post added at 07:04 PM ---------- Previous post was at 07:00 PM ----------
taviboy said:
How would I go about doing that?
Click to expand...
Click to collapse
Like when you did "fastboot -w" except in this case you would do "fastboot flash imagename.img" provided that the image file is in the same directory as where you're running cmd from. I'm telling you teamviewer could get this done a lot faster
prsterero mention of USB port got me looking and this sounds like something worth a try, try a different PC, different USB port, don't use a hub, or extension cable, last resort, buy a new known-to-be compatible cable.
mdamaged said:
prsterero mention of USB port got me looking and this sounds like something worth a try, try a different PC, different USB port, don't use a hub, or extension cable, last resort, buy a new known-to-be compatible cable.
Click to expand...
Click to collapse
We did a team viewer session and no additional cables, USB ports, or different computers solved the errors. So it has to be a hardware defect with the EMMC.
Sent from my Nexus 7 using XDA Premium HD app
prsterero said:
(...)So it has to be a hardware defect with the EMMC.(...)
Click to expand...
Click to collapse
Oh, that's weak. Good luck to the OP then.
taviboy said:
E:failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (i/o error)
Click to expand...
Click to collapse
I'm getting the same error, except that wipe cache partition, or wipe data/factory reset, both give errors as well.
The "(i/o error)" suggests to me that there's a hardware issue. Not really sure what to do, other than RMA the thing.
jmasur said:
I'm getting the same error, except that wipe cache partition, or wipe data/factory reset, both give errors as well.
The "(i/o error)" suggests to me that there's a hardware issue. Not really sure what to do, other than RMA the thing.
Click to expand...
Click to collapse
Follow the instructions in this thread to check if your EMMC is fried http://forum.xda-developers.com/showthread.php?t=1284196
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