Database Info

[Q] SGH-i896 bricked?

Hey everyone, today I tried to revert to my original stock rogers firmware via the clockwork recovery backup I made. After booting, it gets passed the i896 page and continues until it says ANDROID in a graphic image. This flashes every once in awhile. But after an hour of just leaving it, it's still in the same cycle. I can boot into recovery but when I try to install a new rom it says:
"E: Can't mount /dev/block/st19
(No such file or directory)
E: Can't mount SYSTEM:
E: Failure at line 2:
copy_dir PACKAGE:system SYSTEM:
Installation aborted"
If I go into the Mounts and Storage Menu it shows that /system isn't mounted and the same error occurs if I try to mount it. If I try to do a restore from either of my clockwork backups it says the MD5 sums don't match.
As I'm fairly knew to android I'm apprehensive to go any further because I think I'll probably make it worse. I'm thinking I'll use Odin, if there aren't any other suggestions, I've just never used it before and don't have windows installed at the moment.
What do you guys think is the best course of action?
Thanks for your help.

Get yourself into download mode and flash to stock using Odin. Then root and install the rom of your choosing (I recomend Assonance)

[Q] E: failed to mount /efs (invalid argument)

Hello everyone. I'm a new member here so if I forget to mention crucial information needed to get technical support, please let me know.
Surprisingly it all started when my Galaxy Note Pro 12.2 (SM-P900) was low on battery yesterday. I had to go to college so I took my external battery with me and charged it in my backpack. I didn't need my tablet so I left it in there (was working fine before) and I came back to it this morning to find that it had restarted. It was on the glowing blue Samsung logo, but it wouldn't load past that. I tried restarting it and it wouldn't boot past the logo no matter what. So I tried booting into Android System Recovery (Power + Volume UP) to wipe the cache and still, same results. This is where I can see the error "E: failed to mount /efs (Invalid argument)".
I also did the following:
*Download Samsung Kies (both version 3 and the other since each one says it's not supported and to download the other) and try to resolve the issue. Tablet could not be recognized by either version. No fix.
*Download ADB and the official firmware and flash it (adb gives various errors, ex: can't connect. I may be doing the commands wrong as I'm no expert at this). No fix.
*Download Odin in an attempt to flash it, but the first search result in google was a professional-looking website that actually had a trojan-horse for download; had to shut down my PC and run MalwareBytes, Avast! and McAffee to ensure that nothing remained.
I've been at this since morning. I've also looked at other topics and websites about this problem but I can't seem to find a straight-forward solution. Can anyone please help? I desperately need my tablet for work as soon as possible.
Thanks in advance, and please be precise and clear with your answers (because I'm not so good at Android/Linux commands, or rooting or anything that isn't spoon-fed).
Update: Still not working after I tried to apply TWRP 2.8.6.0 (zip) through System Recovery. After finding, opening and verifying the package it gives the following error message:
E: failed to seek in /tmp/sideload/package.zip (Value too large for defined data type), E: signature verification failed, E: failed to mount /efs (Invalid argument).
I should also note that throughout the entire time I used the official firmware, I haven't used any custom ROMs but I'm now open to it since I have to do all this.
Update 2: Downloaded Cyanogenmod Installer and while it was about to install, it detected the device needed to be repaired. My device was in Android System Recovery under the "apply update from ADB" selection, and these errors came up when Cyanogenmod tried to fix it: "E: footer is wrong, E: signature verification failed".
BIG Update (3): I managed to find the legit Odin application and flashed TWRP v2.8.6.0. However, I'm not sure what to do from this point on out. Help?

Hi.
I am in the same situation. Have you found a solution ?
Thanks in advance.

[problem] GPS issue/unknown system error

Hello, first i have to explain that i tried everything to avoid ask for help here, but i have no more ideas how to try a fix by myself.
I have a huge issue in my S8+ (exynos), the first is that GPS doesn´t working properly, the second (maybe because a nand system error), everytime i go to the original recovery, a error message appears.
#fail to open recovery_cause (no such file or directory)
reboot recovery cause is [UNKNOWN]
Support single-SKU
File based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Manual mode v1.0.0
remove failed dir /system/carrier/ATT/priv--app/attIqi_ATT nmo such file or directory
can´t open directory: sup cid permissions
E: [Libsfs_mgr] firmware info was not valid /proc/device-tree no such file or directory.
why i have these errors in my recovery, is the GPS problem related with this issue?
I tried everything that i know: rooted my device, backed up the EFS folder, used this thread and flashed my phone via TWRP, did a fully nand wipe (EFS included) without solving anything.
https://forum.xda-developers.com/ga...1ara2-devbase-v5-0-encryption-t3752964/page61
I did a full nand wipe a lot of times, i also used a PIT file to rebuild the entire partitions, but something else still missing , my knowledge about this specific issue is very basic at this point.

Paulo1024 said:
Hello, first i have to explain that i tried everything to avoid ask for help here, but i have no more ideas how to try a fix by myself.
I have a huge issue in my S8+ (exynos), the first is that GPS doesn´t working properly, the second (maybe because a nand system error), everytime i go to the original recovery, a error message appears.
#fail to open recovery_cause (no such file or directory)
reboot recovery cause is [UNKNOWN]
Support single-SKU
File based OTA
Supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
Manual mode v1.0.0
remove failed dir /system/carrier/ATT/priv--app/attIqi_ATT nmo such file or directory
can´t open directory: sup cid permissions
E: [Libsfs_mgr] firmware info was not valid /proc/device-tree no such file or directory.
why i have these errors in my recovery, is the GPS problem related with this issue?
I tried everything that i know: rooted my device, backed up the EFS folder, used this thread and flashed my phone via TWRP, did a fully nand wipe (EFS included) without solving anything.
https://forum.xda-developers.com/ga...1ara2-devbase-v5-0-encryption-t3752964/page61
I did a full nand wipe a lot of times, i also used a PIT file to rebuild the entire partitions, but something else still missing , my knowledge about this specific issue is very basic at this point.
Click to expand...
Click to collapse
Those errors are ok. It at least are on us snap dragon models. Some ones flashed as us based csc on it. This is not related to GPS. Do not worry about them leave it be.
I see you say GPS isn't working correctly. Which tells me it is just not good. Is this a correct assumption

TheMadScientist said:
Those errors are ok. It at least are on us snap dragon models. Some ones flashed as us based csc on it. This is not related to GPS. Do not worry about them leave it be.
I see you say GPS isn't working correctly. Which tells me it is just not good. Is this a correct assumption
Click to expand...
Click to collapse
well, it´s a akward situation because the GPS troubles started when i flashed a diferent rom that was not released in my country, mine is TPH, i flashed a unlocked firmware from Germany, but i did mess because put the second CSC file (that is used to keep personal data untouched) in the userdata tab in odin. :/
thanks a lot man

Big issue with G950F Samsung GS8

Hello everyone
I truly hope that someone can help me. I would like to say sorry in advance because Im asking a question I might find the answer to by reading the thread(s) myselfe. Only thing is - I truy don't know where to look. When it comes to phones Im lost, so to speak. And right now Im lost. I hope you can helpe me:
When I turn my phone on it boots up in androide recovery mode. I have tryed reboot system and wipe data. When wiping data I get this message:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
File-Bassed OTA
Supported API: 3
E:unknown volume for path [/odm]
E:unknown volume for path [/vendor]
dm-verity verification failed...
E[libfs_mgr]is_dt_compatible():firmware info was not valid : ´/proc/device-tree/firmware/android/compatible : No such file or directory
-- Wiping data...
Formatting /data...
Formatting /cache..
Data wipe complete.
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : ´/proc/device-tree/firmware/androdi/compatible': No such file or directory
Maybe it can be saved maybe no. The case is I don't know what to do next. All I know is, that a program called Odin might do the trick if you add the right "things" in BL, AP, CP and/or CSC??
Can someone please tell we what I need, and where to find it?
Kind regards
Inish

Can't boot Android or recovery mode

I have a Samsung Galaxy Note 10.1 GT-N8010. One day it suddenly stopped booting Android and wouldn't pass the first screen (it didn't even reach the one with only the Samsung logo, only the one that says "Samsung GALAXY Note 10.1"). I booted into recovery mode and tried to factory reset, but I got this error: "E:failed to mount /efs (invalid argument)." So I followed this guide: https://forum.xda-developers.com/t/how-to-fix-e-failed-to-mount-efs-invalid-argument.2858056/
Here is where the problem begins. When I rooted to remove the factory mode (just following the guide), I did it using CF-Auto Root. But then my tablet stopped booting to Android (again, not passing the first screen), and when I try to boot into recovery mode, the CF-Auto Root screen boots instead (even after flashing stock firmware and TWRP). On this screen, it says the following:
CF-Auto-Root
Copyright (C) 2011-2016 Chainfire
Detecting devices . . .
- Recovery: /dev/block/mmcblk0p6
- System: /dev/block/mmcblk0p9
- Cache: /dev/block/mmcblk0p8
Preparing cache . . .
Mounting . . .
- System
- Cache
Rooting (SuperSU) . . .
Restoring stock recovery . . .
Cleaning up . . .
Rebooting in 10 seconds . . .
Then nothing happens. It still doesn't boot into Android, and if I try to access recovery mode, I get to the same CF-Auto Root screen. I can only access Download Mode, but I don't know what to flash to solve the problem. As I said, I tried flashing the stock firmware and TWRP (when I did that, Odin said PASS!).
I have been using Odin 3.10 and flashing this firmware https://sfirmware.com/es/samsung-gt-n8010/ (ARO). I also tried with a firmware downloaded through Frija (probably the same one).
I think that's everything. If I missed any information, please let me know.
Any help is welcome!
Thanks,
Whilz.

Good afternoon. I cannot guarantee that this will help you, as I have not encountered this problem and have not used these instructions. But maybe this will help you.
I found these instructions on the russian forum of the platform our devices are built on (n80**, i9300, etc.)
I will give the translation in this post and links to the original posts.
Spoiler: E:failed to mount /efs (Invalid argument) and how to deal with it!
Original post: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry26179020
According to the instructions, you need to flash I9300_Repair_efs.tar.zip efs image via Odin3. IMEI and S/N will be lost, so you will have to think about restoring it.
Spoiler: Error "E: unable to mount /efs (Invalid argument)" or "failed to mount /efs..."
Original: https://4pda.to/forum/index.php?showtopic=514244&st=0#entry24433995
Attention! This method will not raise IMEI and S / N without efs backup. If you do not have it, then you can only download your phone, but there will be no network.
Tested on SGS III​
1. If you currently do not have root rights, then download them from the link from the topic header, the version for installation via Odin, install.
2. Download Custom recovery. Also versions for Odin (.tar.md5), install.
3. Download AROMA Filemanager
4. Install the File Manager through the recovery as a normal update.
5. Run the built-in terminal File Manager (press menu / select "open console" or "terminal" from the list).
6. We write commands (after each enter - input):
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
reboot
The commands are taken here - http://forum.xda-developers.com/showthread.php?t=1896470
7. Reboot into the system (reboot system now).
8. We read the instructions for restoring efs (who did what) and restore.
If during loading we see a translucent pop-up window with yellow inscriptions on the desktop
then we decide like this - Club of Samsung Galaxy S III lovers (Post # 16738476)
Spoiler: Problem Solution: failed to mount /... (Invalid argument)
Original: https://4pda.to/forum/index.php?showtopic=343514&st=8900#entry38837011
There's quite a lot of information here that I'm not moving here. Perhaps you can learn something for yourself by translating the page into the right language.