Hi,
I have a rooted Samsung Galaxy S4 i9505. During the last few days I tried to update from Android 4.2.2 to 4.3 (using OTA, Kies, Odin (Windows PC and Mac)) but had lots of issues. In the end I managed to flash some partition files with Heimdall 1.4 (using a Mac). The phone boots correctly and the status says "Android 4.3". But since some partition files failed to be flashed some components, like WLAN, don't work at all.
Successfull:
Boot
Cache
Hidden
Recovery
System
Failed:
Apnhlos
Aboot
Mdm
Rpm
Sdl2
Sdl3
Tz
The latter ones fail with the Error:
Failed to unpack received packet.
Failed to confirm end of file transfer sequence.
Upload failed.
Suggestions to use Heimdall 1.3.x doesn't work. Flashing fails with the Error Failed to initialize Protocol.
I assume that I don't have permissions to write onto these partitions. I might be wrong, but I don't know how to check and change this.
I'd be thankful for any idea how to continue!
Hi there, I'm having difficulties flashing Magisk 14.0 on my Moto G4 Plus from TWRP (I'm using stock rom with SuperSu). This is the error that displays:
Quote:
MTP Enabled
Installing zip file '/sdcard/Download/root things/Magisk-v14.0.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
******************************************
Magisk v14.0 Boot Image Patcher
******************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found boot image: /dev/block/sde18
- Unpacking boot image
- SuperSU patched boot detected!
- Adding auto patch script for SuperSU
! SU image mount failed. . .
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/root thing/Magisk-v10.2.zip'
Updating partition details. . .
. . . done
EnzoD14 said:
Hi there, I'm having difficulties flashing Magisk 14.0 on my Moto G4 Plus from TWRP (I'm using stock rom with SuperSu). This is the error that displays:
Quote:
MTP Enabled
Installing zip file '/sdcard/Download/root things/Magisk-v14.0.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
******************************************
Magisk v14.0 Boot Image Patcher
******************************************
- Mounting /system(ro), /cache, /data
- Device platform: arm64
- Constructing environment
- /data/magisk.img detected!
- Mounting /data/magisk.img to /magisk
- Found boot image: /dev/block/sde18
- Unpacking boot image
- SuperSU patched boot detected!
- Adding auto patch script for SuperSU
! SU image mount failed. . .
! Please immediately flash SuperSU now
! Installation will complete after flashing SuperSU
Updater process ended with ERROR: 1
Error installing zip file '/sdcard/Download/root thing/Magisk-v10.2.zip'
Updating partition details. . .
. . . done
Click to expand...
Click to collapse
3 lines above that error says what you need to do now.
Boot/kernel is got modified when you installed SuperSU, so now modified kernel may work or may not with magisk (as that 3 line says it failed to mount.) Do as those lines says (flash superSU again then try magisk again),
Otherwise boot to system, unroot your device(from superSU app > Settings > full unroot.) Then try to flash magisk.
Before doing anything, make backup, it's only way to get out from black hole.
*gulp* I thought I wouldn't say this, but I've been messing around with my phone (no warranty) and I went and installed a custom ROM which didn't work. Now I flashed an official ROM, but the phone is giving me an error of a Modem crash. My phone is a G360R6, TWRP recovery. G360R6WWU1AOI2, I need some help. Please.
Ramdump Case : : [0xfc]
Subsystem Crashed: MODEM!
Modem info
Error type: Error fatal
Task: WFW_SW_CMD_
File: rflm_diag_error.cc
line:311
[email protected]_wcdma_ccs. c:1145 Assertion (rv == RFLM_ERR_NONE)
fai
pm8841_rev : 0x0
Wait...
Done!
Hi,
I was on Magisk v16.x, and tried to update the to v18. Magisk Manager updated successfully, but there was some trouble updating the Magisk zip file. After a reboot, my Nexus 6P keeps booting up to the boot loader rather than Android OS. I'm able to boot to TWRP via the boot loader, and tried wiping dalvik cache/etc, and even doing a full factory reset, but it just keeps booting to the boot loader after.
This is the output at the bootloader
Code:
BL: angler-03.54
Baseband: angler-03.61
Serial Number: <my S/N>
CPU: MSM8994 0x20001
eMMC: 32GB Samsung
DRAM: 3072MB SAMSUNG LPDDR4
Console: NULL
Battery OK
Device is UNLOCKED
Qfuse Statis: ENABLED
Off-mode-charge: ENABLED
Download mode: DISABLED
Connect USB Data Cable
I also tried flashing the Magisk zip file manually in TWRP, but it keeps failing with the following output:
Code:
...
- Unmounting partitions
Updater process ended with ERROR: 1
Error installing zip file '/usb-otg/Magisk-v18.0.zip'
Updating partition details...
...done
Any help would be appreciated.
Hi guys I own an S8, SM-G950F. The previous software I was on was Android 8 U2 (can't remember exact one). I flashed the new DBT Android 9 software via ODIN (using CSC, not home CSC). However the phone stays in the "Powered by Android" screen and does not go any further.
I can go into the Samsung recovery mode and have tried wiping both the cache and data/factory reset but this seems to make no difference. As an alternative I have tried flashing the Android 8 files (with bootloader U4), which is successful in ODIN but shows "No command" when booting.
USB debugging was also turned on before applying this update.
Other info:
FRP Lock: Off
OEM Lock: Off
RP SWREV: B:4 K:3 S:3
Any ideas what I could do?
Thanks.
Try Flash Same Firmware Reigon You have own in prev Version
MA7MOD_GSM said:
Try Flash Same Firmware Reigon You have own in prev Version
Click to expand...
Click to collapse
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
hs102 said:
Thanks for your reply. I have tried this although it does not work as the boot loader version is now at V4, whereas the previous software I had was V2. I have tried flashing other Android 8 software with boot loader V4 but it goes into the “No command” state where I can’t access the recovery, only download mode is available.
Click to expand...
Click to collapse
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report 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]
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
I think you Flash worng Firmware send download mode photo
MA7MOD_GSM said:
I think you Flash worng Firmware send download mode photo
Click to expand...
Click to collapse
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
same as me. loaded twrp and no ver opt and magestic but thats all cool but all i want is official with no root or anything. why wont my damn phone boot without all the crap. this method will not allow any kind of ota. same issue when i flas pie via odin except it even worse. cant get to boot
hs102 said:
Firmware was fine not sure what the issue was.
Got around it by flashing latest TWRP and no verity and it loaded successfully.
Thanks
Click to expand...
Click to collapse
after TWRP your fone boot working ... because I have the same issue Samsung warranty center told me to replace the motherboard
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report 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]
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
Click to expand...
Click to collapse
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Kdom81 said:
I also am seeing the same message in recovery mode. Also in odin mode(download mode) there is extra lines of text. Although in saying this the s8 boots and seems to function as per usual. The storage used from stock firmware is 12.4 GB... Is this normal??
All I am wanting to know is "is this normal for the exynos galaxy s8 running One UI, android 9" ?
or Did I Download a dodgy Rom?
Click to expand...
Click to collapse
Same here.
https://forum.xda-developers.com/galaxy-note-8/help/weird-message-recovery-e-libfsmgr-t3936625
Did you arrive to any conclusion?
Hey I have the same problem as well... I can't flash twrp because I have oem locked and I can't boot into my because it keeps restarting and getting stuck at some point, and the recovery is saying:
#fail to open recovery_cause (No such file or directory) #
#report 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]
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
How can I fix this?
Is there any update on this? I have the same issue as post #11 on a Samsung A8 sm-a530w.
Any help would be much appreciated.
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
---------- Post added at 05:54 PM ---------- Previous post was at 05:54 PM ----------
I've got the same issue on a G950F.
I bought new (sealed, G950FXXU5DSFB), and tried to flash combination file G950FXXU5ASF1 . This did not work. (no boot).
So I flashed what I thought was stock rom matching CSC.
(AP_G950FXXU5DSFB_CL16290088_QB24491245_REV00_user_low_ship_meta_OS9.tar )
The phone boots and operates fine, except for the same message you guys are getting in recovery, as well as a message about no OTA updates.
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
techyrock said:
Any news about this? for me I bought used Galaxy Note 8 it was Korean N950N Converted to N950FD, I wanted to Install TWRP and ROOT but I kept getting Failed to Mount Preload error in TWRP and read smwhere its because of messed up partition so not knowing what official firmware it came with I flashed the carrier firmware which phone's IMEI info got me also it was closest to old converted FD baseband now I bypassed this nonsense via twrp but there is not even proper root to install any other custom ROM help me solve this or kindly help me find solution to Failed to mount /preload in twrp
Click to expand...
Click to collapse
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
nmx87 said:
Same problem but my phone s8 g950n korean, Failed to mount /preload, heres what i did to solve my problem:
- MOUNT everything in TWRP Without SDCard
- WIPE everything but NOT SDCard
- FORMAT DATA
- FACTORY RESET
- Reboot Recovery
after that no more Failed to mount /preload in twrp
- Flash Custom ROM
- Rooted my device by Flashing Magisk v20.4
Click to expand...
Click to collapse
There was some very simple fix for this mate I don't recall what worked for me, ever since I have change several phones I am on S10 5G right now, so It was just once a faced it and now I dont even remember lol what was it that fixed it for me, I think maybe different TWRP or I flashed Stock Rom the full rom with CSC and everything, just remember don't touch the partitions it was a simple fix of some sorts
hs102 said:
Also a little more info. When the ODIN flash is successful it restarts to the "Install Software Update" blue screen. It reaches 32% but then begins erasing.
The following error message is also present in the recovery:
#fail to open recovery_cause (No such file or directory) #
#report 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]
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
Click to expand...
Click to collapse
Hello Everyone!
I have the same problem with Galaxy Note 8 / SM-N950F
Is there a solution for this??
Please need help, please please.
Thank you