Today I was messing with my new Epic and I installed the 1clickclockwork recovery3 for the stock recovery. It worked and formatted my system and backed it up. I went to update DI18 to DK28 (which failed, i got error 7) & now I'm always stuck on the Samsung screen. I can still boot into both recovery and download modes. Running the restore file didn't work either. I got some kind of sdext error if I recall. I cannot mount the USB from recovery. I get "E:Unable to open ums lunfile (no such file or directory)" errors. Also running Ubuntu 10.10, not on a windows machine.
Boot into download mode and either odin to dk28 or odin back to di18 and try again.
thanks man
Related
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
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
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
ericmerl said:
Hey guys, I seem to have soft-bricked my AT&T S3.
I was running Paranoidkangdroid 2.32 (based on CM10.1, 4.2.2), but started having some stability issues. Thinking it was time to start fresh with a new ROM, I downloaded SlimKat 4.1 and tried to install it following these instructions.
Upon rebooting, my phone hit the SlimKat loading screen and never finished booting. I rebooted to recovery, and saw errors saying it was unable to mount /cache, /data, and /system. I still have access to recovery and download, and have tried flashing and reflashing a variety of different ROMs, both custom and stock, but haven't been able to get past those errors.
When flashing from recovery, I get errors saying the partitions aren't able to be mounted. I can flash ROMs from Odin, and they do seem to be installing (no errors in Odin, and the Current Binary setting does change depending on whether it is a stock or custom ROM).
Best I can tell, my partitions are screwed up. Any advice on what I did wrong and the best way to proceed? If the partitions are screwed up, is there a way I can rebuild the partitions through the shell?
Click to expand...
Click to collapse
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Stock ROMs
Larry2999 said:
What stock ROM did you try to flash via Odin and did you get the <PASS> message? If you did, then it would seem the flash was successful. Can you try booting into recovery and doing a hard wipe/reset? Unless your phone has hardware issues, flashing a complete stock image should update all partitions.
Finally, if you were already on Android 4.3, you may try doing a stock restore using the instructions in the following thread ...
http://forum.xda-developers.com/showthread.php?t=2658486
Click to expand...
Click to collapse
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
ericmerl said:
The ROM I had previously installed was based on 4.2.2, so I'm not sure the instructions in that thread will apply...
I have tried installing the UCDLK3 ROM, as well as a couple of custom ROMs. I'm about to try another stock ROM (UCALEM), and will report back with the results in a few minutes.
Click to expand...
Click to collapse
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
ericmerl said:
Sad times.
I just tried installing the UCALEM stock ROM with Odin. Everything seemed to go well, and it finished with no errors and a "PASS!" result.
When my phone rebooted, a screen briefly popped up with red text. It didn't stay up long, but the errors I saw were similar to what I had seen before (unable to mount, etc.). The background was the red exclamation with the android robot lying down. The phone quickly rebooted, and sat with a black screen. When I pulled the battery out and powered it back on, it tried to enter recovery mode on its own, but only flashed the Samsung Galaxy S3 screen and remained on a black screen.
I can still access download mode, and the Current Binary now reads "Samsung Official." My phone did this same thing earlier when I flashed another stock ROM, and I was able to get back to recovery mode by flashing a fresh instance of CWM.
Click to expand...
Click to collapse
To follow up again, I was able to re-flash TWRP using Odin. Once that was done, the phone no longer tried to boot straight to recovery. I was able to three finger into TWRP, though it took a super long time for it to boot.
Here's the console log taken from TWRP once it boots:
Code:
E:Could not mount /data and unable to find crypto folder.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/system'
E:Unable to mount '/data'
E:Unable to mount '/cache'
E:Unable to mount internal storage.
E:Unable to mount /data/media during GUI startup.
E:Unable to mount '/cache'
Full SELinux support is present.
E:Unable to mount '/cache'
Running boot script...
Finished running boot script.
E:Unable to mount '/cache'
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E:Unable to mount '/data'
Hi I was wondering if someone could help me.
My dad's phone which is a S3 somehow soft bricked itself. It was on a stock rom before.
It turns on and then gets stuck on the Samsung Galaxy SIII screen.
I am able to boot into download mode as well as recovery.
I was able to flash a stock ODIN file UVUEMJC as well as the PIT file and everything went smoothly and it passed.
However, the same problem remains, it is still stuck on the Samsung Galaxy SIII screen when I boot it.
Also went into recovery and tried to wipe data, but it is unable to mount any partitions, e.g. can't mount cache, can't mount data, etc.
I was able to throw on TWRP and boot into that, and it gives me similar errors as the stock recovery. TWRP also says that my internal storage is 0 GB and I can't put any files onto the phone.
I am quite confused because if NAND was corrupted then I shouldn't I not be able to boot into recovery at all?
ADB is also working...can't push/pull anything though.
If someone could help me I would really appreciate it. Thanks.
So I flashed CWM cause I read on XDA someone said that formatting data through CWM works, now...it says there is no pit partition and there is a flash read failure whenever I try to flash a stock tar with odin w/ pit. Also tried flashing pit by itself, doesn't work.
Try installing cwm or twrp again, boot into recovery, mount sdcard0, connect to Windows machine, and try to format the partition using fat32.
I'm not sure if anyone can help me-a long time ago I stupidly formatted my G6 edge using TWRP. Now that obviously wiped everything. Well I need a backup phone and I can't get odin to flash the firmware no matter what I try. I have even tried to flash some files individually either through odin or adb sideload-including the firmware-to no avail.
What Rom Ver.
I have stock 7.0 but i did a nand wipe before i put it on and my custom boot screen is still there (alienware) its bugging on diagmon random reboots and vol up, home key, power to bootloader brings up a android says updating but doesnt then goes to a fail android then to Android Recovery apply from SD card =E:failed to stat /dev/block/sdb1
E:failed to mount /sdcard (No such file or directory) --Couldn't mount /sdcard otherwise no other bugs i know of. I cant get my TWRP back it wiped it I try in ODIN but all hangs or fails with some weird asian letters after english