Hey,
After a restart (from my running rom, which I dont remember what it was) my tablet got stuck with the message:
Supported API: 3
E: unknown fs_type "f2fs" for /cache
E: Can't mount /cache/recovery/last_locale
Periodically flashing a green droid for half a second, with the message "No Command".
I can't get into recovery or fastboot, Power + Volume down changes nothing and running "adb devices" or "fastboot devices" shows nothing. Is there anything I can do to recover it?
Thanks!
If you can get into recovery then it's possible to create cache again. Then it should stop complaining and boot
Sent from my Pixel using Tapatalk
Your currently installed ROM does not support f2fs format for the /cache partition so yoi need to reformat /cache to ext4 or install a different ROM which supports f2fs
And how to do it if you can't flash the phone via twrp fastboot if nothing starts, I downloaded the cosmic os 8.0 firmware if I'm not mistaken, since I need to download the firmware and flash the teleon I need android 9 firmware
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.
I have Nexus 6P that I was using and bootloader was unlocked.
One day, it started looping for some reason. Only time it would boot into Android (8.0) is when the phone is left unplugged and phone goes into battery saver mode.
I downloaded Nexus Root Toolkit and flashed the phone with Factory Image and it seemed to fix it.
However, bootloop returned.
I flashed some other stuff and tried to fix it and this is when I did something really stupid. I Relocked the phone by pressing OEM Lock.
Now phone shows message "Your device is corrupt. It can't be trusted and may not work properly." and stuck in GOOGLE logo.
It does not boot and phone is locked so I cannot do anything. I can get into recovery more (android robot with tummy open) but I can't do anything since device is locked.
Phone still charges and connects to Nexus Root Toolkit. I can't do any operation within Nexus Root Toolkit because it always shows failed since device is locked.
Am I screwed?
Oh...here is what shows up when I get into recovery mode
BL: angler-0.3.74
Baseband: angler-03.84
Product/Cariant: ANGLER-VN2
Serial Number: xxxxxxxxxxxxxxxx
CPU: MSM8994 0x20001
eMMC: 32GB Toshiba
DRAM: 3072MB Samsung LPDDR4
Console: NULL
Battery OK
Device is LOCKED
Ofuse Status: ENABLED
Off-mode-charge: ENGABLED
Download Mode: DISABLED
But you can boot into stock recovery ?
Edit: try this with Angler images instead,
should work with fastboot too instead of the toolkit.
https://forum.xda-developers.com/nexus-5x/help/guide-fix-bootloop-locked-bootloader-t3608679
Hi!
A friend come to me with a problem, some one was changed his system pin and now he can unlock and he can make a factory reset.
The system starts and show notifications and other thinks (so I suspect that it is not encrypted) but it obviously ask for the pin(system not sim) and do not progress
He have a twrp recovery that I have installed when he bought it.
But when I try to make a wipe I got an error: Failed to mount /data.
What I know:
Android version: Unknown.
TWRP: 3.0.2-0
Model VNS-L31
What I've tried:
Update to a newest twrp-3.1.1-0-venus.img , no luck , id does not boot I have to flash again the 3.0.2-0 version.
try to wipe all but system, without success.
fastboot erase user-data (cnomand not available)
It have a "cust "partition that I don't know what it is.
some clues?
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