Hello.
Yesterday I was copying a file to an external disk. But I didn't look at the charge percentage, I'm out of charge. And I couldn't pick up the phone again.
But I was able to enter TWRP and Download mode.
I tried to wipe System, repair System, change file system of the System but just some errors like: E: /system not mounted and when I click System in mount menu nothing happened.
And I flash Stock ROM to my phone. Then TWRP was gone but the blue "system update" screen came up. After a few seconds, some text started to appear on the screen.
I found someone using the same phone as me and getting the same error:
Note 5 bricked after update
Symptoms: Turn phone on it goes to System updating and then spits me out at a black and white screen with messages of stats failed efs mount. Then proceeds to reboot and the process repeats it's self until the battery dies. What i've done to...
forum.xda-developers.com
How can I fix?
Related
Hello,
Like many other users on this forum, I am having trouble with my i9000M sdcard after doing some ROM flashing.
Although there is some extensive threads collecting the different situations people are experiencing, I was hoping I could get some help for a specific circumstance relating to the sdcard issue.
I'll start by..
- Detailing the firmwares I have flashed, and what happened
- What is working / not working now, and how I got to get to the current situation
- And finally, I'll detail what I'm trying to do and where I'm getting stuck.
I would really appreciate some help with this, and thank anyone who takes the time to read it. I am trying to be very thorough to give you as much information as possible.
-----------------------------------------------------------------------------
1. Started with stock firmware. I am not sure what it was.. I believe the phone is equivalent to the Bell i9000M, but I am on the SaskTel carrier.
2. Flashed firmware I9000XXJP2: This worked, and I was using Froyo 2.2 fine.
3. Tried to root Froyo 2.2 firmware: This FAILED and the trouble began. I was using the update.zip method, and the source claimed it was compatible with 2.2. I had to hard reboot the phone, but it would stall on the white text intro screen (not the animated one).
4. Went into Download mode. Tried to flash firmware I9000UGJH2 (apparently the most current bell firmware), using Odin v1.1. This FAILED, and I had to hard reboot, which resulted in the PHONE - ! - PC error. I am aware the i9000M can still be recovered from this state.
NOTE: I could do nothing at this point: all firmware flashes failed, UNTIL I CHANGED TO ODIN V 1.3!
Using Odin v.1.3:
5. Flashed a series of firmwares.. (I9000UGJG8, I9000XXJM1, I9000XWJG5), ALL resulted in the phone either being in a shutdown-boot loop to the white Glaxaxy text screen, or the battery charging screen.
I could enter Download mode to reflash, but NOT recovery mode.
6. The ONLY semi working firmware is I9000XXJP2, Samsung Froyo 2.2. This is what the phone is now.
- I CAN enter Download mode, Recovery mode, and the phone stalls on the white Galaxy boot screen, but goes no further, and does not restart.
- I CAN run abd commands
Here is the output I get from each of the options in the Recovery mode:
Code:
I9000XXJP2
Odin 1.3
512.pit
Flashes fine
Goes into recovery mode
Displays error:
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
copy default media content failed.
Try to format sdcard:
Formatting SDCARD:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/mnt/internal_sd)
ensure_root_path_unmounted ret 0
ensure_root_path_unmounted It's not mounted
update media, please wait
E:Can't mount /dev/block/mmcb1k0p1
(No such file or directory)
E:copy_dbdata_media: Can't mount SDCARD
your storage not prepared yet. please use UI me nu for format and reboot actions.
Try to wipe cache partition:
-- Wiping cache...
Formatting CACHE:...
ensure_root_path_unmounted**
ensure_root_path_unmounted (/cache)
ensure_root_path_unmounted ret 0
unmount (/cache) attempt 1 (Unknown error: 0)Cache wipe complete.
Try to apply sdcard:update.zip
Same errors as 1) can't mount sdcard therefor installation fails.
Reboot system:
- Will accept adb download reboot
note: I can reach download mode using the button combination
- recovery mode: can access with button combination or 'adb reboot recovery'
- power off: battery charging indicator shows
note: it does not loop the battery indicator
- power on: stalls at Galaxy S GT-19000 white lettering screen.
note: i recieve an indication on windows desktop that a device has been connected which is capable of USB high speed point
ADB COMMANDS WORKS: device is detected
Things I have tried:
I tried booting into a Ubuntu Live cd to see if I could format the sdcard, as suggested in this thread: (sorry, forum won't allow me to hyperlink, thread id=759910)
The disk utility picked up the Samsung drives (One was labeled something like Samsung_Galaxy, and the other Samsung_Galaxy sdcard, but I'm not 100%) but could not format them. There was also no info being listed about the size.
Things I would like to try / have hunches on:
Before all this happened, I made a Nandroid backup of the orriginal firmware, and copied it from the i9000's sdcard to my computer. I made the backup using Rom Manager's Clockworkmod.
Is there a way to use Odin to flash Clockworkmod, so I can restore this backup?
-everything out there says to use Rom Manager, which I can't access because the phone is pseudo dead.
Will the backup even still be on my sdcard?
Wait, my sdcard isn't mounted.. can we try mounting it with abd? (I tried, but am not sure of the command / path of how to do this..
Can abd be used to restore my backup stored on my computer? Is this dependent on the sdcard being mounted?
I fully appreaciate those you take the time to read through this as it is rather lengthy. I just want to ensure I have tried every means to revive the device, and hopefully some more skilled users can help with the mounting and adb syntax.
All comments and ideas are welcome and appreciated! Thank-you
Sorry to be the bearer of bad news. But time and time again this error has proven to be a hardware error. Mine did the same thing and samsung/bell had to replace the mainboard in my phone. Good luck, but unfortunately, anything you do further is a waste of time short of sending it back for repair.
As per the title. I have an S4 Active, humming along happily with "activeroot" applied when it first became available. I realized this morning that I never deleted the activeroot app itself, but when long-pressing the icon to get to the uninstall menu, my finger slipped. I really like geohot and his work, a whole lot, but the fact that there isn't at least a confirmation screen before overwriting important system files really grates on me. The instant the tap happened, the screen went black, and became immediately stuck on the AT&T logo at reboot.
If I power the phone up normally, I only see the AT&T logo for as long as I care to stare at it before powering it down. I can reboot into the stock recovery, but because the phone doesn't ask me for the disk-encryption password as in a normal boot, I see the error "Can't mount /data (Invalid argument)". The only non-destructive thing I could do at that menu was to wipe the cache, which obviously did nothing for my bootloader or encrypted disk. I feel pretty sure I haven't lost any data on that encrypted disk yet, and I know I could do a full factory wipe, but I'm hoping I have a better option:
1) Could it possibly be as simple as trying to send "towelroot", the newest root, to the phone via adb and execute it?
2) Without the ability to write to the disk, can I get a log file for further troubleshooting / ideas?
3) Is there a way to decrypt the disk over usb to at least pull over any non-backed-up files before performing a factory wipe?
4) Can I install a different recovery which might give me more or better options?
Thanks for any help you can provide! = )
I woke up today and my Note 3 was dead. I assumed the battery died as that is in all likelihood what happened. I plugged my phone into the charger and attempted to turn it on. It stayed on the Samsung logo for several minutes. I then booted it into recovery mode, and noticed at the bottom, E: Failed to mount /efs (invalid argument). I attempted a cache wipe and at first it said failed to mount /cache, however another attempt and it completed without error. I then tried a reboot with the same problem. Next I tried a system/data wipe and got the same problem (failed to mount efs).
So, I used a 4 part Odin flash to 5.0 Lollipop OEM. This succeeded and upon reboot the phone got as far as the AT&T logo then hung again. Once in recovery I noticed the same E: Failed to mount /efs (invalid argument). I have searched on this and many other forums attempting to resolve this issue without success. I've been at this nonstop for 12 hours now. I know of a way to use adb to create a generic EFS folder, the problem is the phone is 100% stock, including no developer options(adb), custom recovery, etc. Not even busybox.
Anyone with any info on how I can unbrick this phone would greatly appreciated. Or even how I can use Odin to install safestrap w/ root thereby giving me the ability to mount the system with TWRP and send adb commands that way. To clarify, I have access to nothing but the stock recovery and download mode without ADB active on the phone. Thanks for your time.
The Good:
I can charge the battery, boot to CWM, WebOS Recovery or TPTB_v42 from moboot.
The bad:
If I boot to CM the Android icon shows for a few minutes and then the screen goes blank and stays blank.
In TP Toolbox I can Flash A6 and Mount Media Volume
Repair Android Volumes fails with
"e2fsck unable to set superblock flagts on dev/store/cm-cache"
and "Failed to correct errors on volume cm-cache."
Resize Android Volumes returns: "Help File 'confirm_repair_bad' is missing" and e2fsck -fp detected error on fs on vol cm-cache rc=8"
Complete Data Reset returns: "Failed ERROR LUM config erase check FAILED. Possible read-only failure.
In CWM
I can install zip but it makes no difference to above.
I wiped cache partition and Dalvik - no change to above
I formatted cache - no change to blank screen
I think I need to do the equivalent of an fdisk through novaterm but am at a loss of how to accomplish this. Any help would be greatly appreciated.
hi. i'm having the same issue. TP was working fine until a few weeks ago. i'm trying to just start over but i'm seeing the same "bad" as you. Even after doing a factory reset within android, it just reboots and everything is still there.
Hoping someone can assist.
Carey4782 said:
The Good:
I can charge the battery, boot to CWM, WebOS Recovery or TPTB_v42 from moboot.
The bad:
If I boot to CM the Android icon shows for a few minutes and then the screen goes blank and stays blank.
In TP Toolbox I can Flash A6 and Mount Media Volume
Repair Android Volumes fails with
"e2fsck unable to set superblock flagts on dev/store/cm-cache"
and "Failed to correct errors on volume cm-cache."
Resize Android Volumes returns: "Help File 'confirm_repair_bad' is missing" and e2fsck -fp detected error on fs on vol cm-cache rc=8"
Complete Data Reset returns: "Failed ERROR LUM config erase check FAILED. Possible read-only failure.
In CWM
I can install zip but it makes no difference to above.
I wiped cache partition and Dalvik - no change to above
I formatted cache - no change to blank screen
I think I need to do the equivalent of an fdisk through novaterm but am at a loss of how to accomplish this. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Minus Toolbox, I am having this exact same problem. Have either of you figured out how to fix it yet?
Since last night my note 8 has been having a severe charge problem. Basically, it died and powered off and now, every time I plug it in the powered-off charge percentage goes from 0 to 100 in like half a second. When I try to turn it on, It just turns back off during the boot process so, I'm guessing it thinks its fully charged and doesn't accept any more charge. I tried to reboot the phone to bootloader and now its just stuck on a bootloader boot loop. Any option I choose, it goes to the Samsung logo then, it shows installing system update, then no command, and then, finally, it boots into the bootloader. The bootloader also says:
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Maybe a flash of the stock rom can fix this but, I have no idea how to do that so, any help will be