Someone has knowledge of this error that occurs in the Z Fold 2 when you want to delete an esim ?
"SIM card busy, try again later. Code ERROR: SIM_APDU_NULL_RESPONSE".
E: [PDP] lstat c____/pdp_b__ : 0 - No PDP Scene
Related
Please help I have installed December security update, don't know if this is the cause. I am also using an 8GB older microsd as I do not normally use a sd card(64gb is enough for me). I am using beta 2 because that is the only thing I can find for AT&T. Here is what I get:
Manual Mode v1.0.0#
-- Appling Multi-CSC...
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
Applied the CSC-code : ATT
Successfully applied multi-CSC
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
--Deleting RSU selective file
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
Successfully verified for dmverity hash tree
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
--Install /sdcard/update.zip ...
Finding update package...
Opening update package...
erifying update package...
Update package verification took 87.1 s (result 2)
mount: failed to mount /dev/block/by-name/system at /system: Permission Denied
E3001: Package expects build fingerprint of samsung/dream2qltesq/dream2qltesq: 7.0/NRD90M/G955U1AQGL:user/release-keys or samsung/dream2qltesq/dream2qltesq:8.0.0/OPR1.170623.026/G955USQU1ZQK1 user/release-keys; this device has samsung/dream2qltesq:7.0/NRD90M/G955USQSBQL1 :user/release-keys.
E:Error in /sideload/package.zip
(Status 7)
E:ensure_path_unmounted failed to unmount /efs (Device or resource busy)
Successfully verify for dmverity hash tree
Installation aborted.#1
Please help, let me know if this post is in violation of rules. I am new here.
E3001: Package expects build fingerprint of samsung/dream2qltesq/dream2qltesq: 7.0/NRD90M/G955U1AQGL:user/release-keys
Your MUST be on AQGL firmware for it to flash, you are on BQL1
I'm on G955U1UES2AQL1 CAN'T FLASH ANY AP FILE IN ODIN JUST EVERYTHING ELSE WHEN I USE THE UPDATE ZIP IN STOCK RECOVERY I GET THE SAME ERROR 7 . I THINK I'LL WAIT TIL THE OFFICIAL OREO TRYING TO GET THE BETA ON MY PHONE CONSUMED TOO MUCH OF MY TIME.
Sent from my [device_name] using XDA-Developers Legacy app
hai i am new in xda... i would like to ask about my vivo v9 bootloop stuck at logo.
i have tried using qfil but it gives me sahara error...
i tried to factory format it gives me error...
i already send to repair shop but all cannot repair..
...wiping data....
E: failed to mount /data: invalid argument
formatting / data . . .
E: failed to mount /data: invalid argument
E: format_volume failed to mount /data, formatting instead
E: /sbin/mke2fs_static failed with status 1
E: format_volume: failed to make ext4 on /dev/block/bootdevice/by-name/userdata: invalid argument
data wipe failed.
Hello i have a problem with my phone.
After installing the Stock firmware, it show up a blue screen with android guy and it says "Installing Update"
Then it restart to recovery and it shows this:
#fail to open recovery_cause (No such file or directory)
#Reboot Recovery cause is [UNKNOWN]
Support SINGLE-SKU
File-Based OTA
E:Failed to mount /efs: Invalid argument
Supported API: 3
E:Failed to mount /efs: Invalid argument
E:Unknown volume for path [/odm]
E:Unknown volume for path [/vendor]
E:Failed to mount /efs: Invalid argument
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible firmware info was not valid : '/proc/device-tre
/firmware/android/compatible: No such file or directory
Can someone help to solve my problem?
TheDoctorMoDz said:
Hello i have a problem with my phone.
After installing the Stock firmware, it show up a blue screen with android guy and it says "Installing Update"
Then it restart to recovery and it shows this:
#fail to open recovery_cause (No such file or directory)
#Reboot Recovery cause is [UNKNOWN]
Support SINGLE-SKU
File-Based OTA
E:Failed to mount /efs: Invalid argument
Supported API: 3
E:Failed to mount /efs: Invalid argument
E:Unknown volume for path [/odm]
E:Unknown volume for path [/vendor]
E:Failed to mount /efs: Invalid argument
dm-verity verification failed...
E:[libfs_mgr]is_dt_compatible firmware info was not valid : '/proc/device-tre
/firmware/android/compatible: No such file or directory
Can someone help to solve my problem?
Click to expand...
Click to collapse
Just reboot to system and that's it. Unless it just boot loops back to recovery.
Hi, i need your help.
My Samsung Galaxy A30 (A305G) doesn't turn on. It stays in bootloop and if I try to boot into Recovery, it doesn't work. The device has the bootloader locked and it also doesn't let me flash any stock / official firmware.
When I boot into recovery, some letters appear at the bottom of the screen, which say the following:
#no data on recovery_cause#
#Reboot Recovery Cause is [UNKNOWN]#
Support SINGLE-SKU
Block-Based OTA
Supported API: 3
E: failed to mount /efs (Invalid argument)
# MANUAL MODE v1.0.0 #
E: failed to mount /cache: Invalid argument
E: failed to mount /system_root: Invalid argument
E: failed to mount /cache: Invalid argument
E: failed to mount /cache: Invalid argument
E: failed to mount /cache: Invalid argument
': Can't mount /cache/recovery/last_locale
after that, it restarts, returns to recovery and repeats the same infinitely, a kind of bootloop but in recovery.
What did you do/flash to this before it came into this situation?
I following this instruction:https://source.android.com/docs/setup/build/building-kernels
I initialized repo and synced
Using Bazel to build (with build/build.sh same error)
Using this command:tools/bazel run --lto=none //common:kernel_aarch64_dist -- --dist_dir=out/android13-5.10/dist
And get this error:
ERROR: /home/aaron/Builds/android-kernel/common/BUILD.bazel:26:22: Checking for kmi_symbol_list_
strict_mode //common:kernel_aarch64 failed: (Exit 1): bash failed: error executing command (from
target //common:kernel_aarch64) /bin/bash -c ... (remaining 1 argument skipped)
Use --sandbox_debug to see verbose messages from the sandbox and retain the sandbox build root f
or debugging
ERROR: Differences between ksymtab and symbol list detected!
Symbols missing from ksymtab:
- __cfi_slowpath
Symbols missing from symbol list:
Target //common:kernel_aarch64_dist failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 3572,647s, Critical Path: 3535,69s
INFO: 7 processes: 3 internal, 4 linux-sandbox.
FAILED: Build did NOT complete successfully
FAILED: Build did NOT complete successfully
Hello, I also encountered this problem, how did you solve it?