Hi developers,
I think I somehow managed to mess up my OPX, please help.
I unlocked the bootloader, installed TWRP and rooted my phone using this guide. Everything was fine, until the next day, when i tried to flash CM 12.1 using this guide. When i needed to flash twrp recovery- it just stated that i cannot do this due to locked phone. I then checked the bootloader status (fastboot oem device-info) and it said this:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.050s]
finished. total time: 0.060s
'WTH?!' I thought, how can it be locked, when just yesterday i successfully unlocked and rooted my phone?..
So i tried unlock the bootloader again (fastboot oem unlock), but it just reboots to TWRP with error E:failed to sysmap file '16'
Here's the full error log:
operation_start: 'OpenRecoveryScript'
Processing AOSP recovery commands...
I:command is: 'install'
I:value is: '16'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '16' on '/data/media/0'...
Unable to locate zip file '16'.
Installing '16'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: Unable to open '16': No such file or directory
E:Failed to sysMapFile '16'
E:Error installing zip file '16'
Done processing script file
Iperation_end
I have all latest drivers and ADB installed.
What is going on? Please help.
I'd like to unlock bootloader (why the hell it locked itself again at all!?) so i can install CM 12.1 on my OPX. Thanks in advance.
U n try flashing original rom oxygen os... Mk sure u enable oem bootloader unlocked option under developers option..b4 unloocking..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
OnePlusNoob said:
Hi developers,
I think I somehow managed to mess up my OPX, please help.
I unlocked the bootloader, installed TWRP and rooted my phone using this guide. Everything was fine, until the next day, when i tried to flash CM 12.1 using this guide. When i needed to flash twrp recovery- it just stated that i cannot do this due to locked phone. I then checked the bootloader status (fastboot oem device-info) and it said this:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.050s]
finished. total time: 0.060s
'WTH?!' I thought, how can it be locked, when just yesterday i successfully unlocked and rooted my phone?..
So i tried unlock the bootloader again (fastboot oem unlock), but it just reboots to TWRP with error E:failed to sysmap file '16'
Here's the full error log:
operation_start: 'OpenRecoveryScript'
Processing AOSP recovery commands...
I:command is: 'install'
I:value is: '16'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '16' on '/data/media/0'...
Unable to locate zip file '16'.
Installing '16'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: Unable to open '16': No such file or directory
E:Failed to sysMapFile '16'
E:Error installing zip file '16'
Done processing script file
Iperation_end
I have all latest drivers and ADB installed.
What is going on? Please help.
I'd like to unlock bootloader (why the hell it locked itself again at all!?) so i can install CM 12.1 on my OPX. Thanks in advance.
Click to expand...
Click to collapse
OnePlusNoob said:
Hi developers,
I think I somehow managed to mess up my OPX, please help.
I unlocked the bootloader, installed TWRP and rooted my phone using this guide. Everything was fine, until the next day, when i tried to flash CM 12.1 using this guide. When i needed to flash twrp recovery- it just stated that i cannot do this due to locked phone. I then checked the bootloader status (fastboot oem device-info) and it said this:
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_enabled: 0
(bootloader) exec_console_unconsole: 0
OKAY [ 0.050s]
finished. total time: 0.060s
'WTH?!' I thought, how can it be locked, when just yesterday i successfully unlocked and rooted my phone?..
So i tried unlock the bootloader again (fastboot oem unlock), but it just reboots to TWRP with error E:failed to sysmap file '16'
Here's the full error log:
operation_start: 'OpenRecoveryScript'
Processing AOSP recovery commands...
I:command is: 'install'
I:value is: '16'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/usb-otg'
I:Actual block device: '', current file system: 'auto'
I:Unable to mount '/external_sd'
I:Actual block device: '', current file system: 'auto'
I:Trying to find zip '16' on '/data/media/0'...
Unable to locate zip file '16'.
Installing '16'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
sysutil: Unable to open '16': No such file or directory
E:Failed to sysMapFile '16'
E:Error installing zip file '16'
Done processing script file
Iperation_end
I have all latest drivers and ADB installed.
What is going on? Please help.
I'd like to unlock bootloader (why the hell it locked itself again at all!?) so i can install CM 12.1 on my OPX. Thanks in advance.
Click to expand...
Click to collapse
Sent from my ONE E1003 using Tapatalk
kooldude7285 said:
U n try flashing original rom oxygen os... Mk sure u enable oem bootloader unlocked option under developers option..b4 unloocking..
View attachment 3578068
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
+1
Sent from my ONE E1003 using Tapatalk
kooldude7285 said:
U n try flashing original rom oxygen os... Mk sure u enable oem bootloader unlocked option under developers option..b4 unloocking..
Sent from my ONE E1003 using Tapatalk
Click to expand...
Click to collapse
I can't flash any ROM/recovery until my bootloader is locked and I can't unlock bootloader due to errors I mentioned above. 'OEM bootloader unlocked' option under developers options is enabled, as is USB debuging.
EDIT:
I thought there might be problems in recovery, so i tried to flash TWRP to stock recovery, unfortunately- no luck here too
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash recover
y oneplus_x_stock_recovery.zip
target reported max download size of 1073741824 bytes
sending 'recovery' (12792 KB)...
OKAY [ 0.410s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.433s
help anyone?
I think here you have the solution:
http://forum.xda-developers.com/showthread.php?p=64339270
Enviado do meu SM-N9005 através de Tapatalk
moinante01 said:
I think here you have the solution:
http://forum.xda-developers.com/showthread.php?p=64339270
Enviado do meu SM-N9005 através de Tapatalk
Click to expand...
Click to collapse
THANK YOU! It worked
I didn't like the CM 12.1 though, so got back to Oxygen OS
OnePlusNoob said:
THANK YOU! It worked
I didn't like the CM 12.1 though, so got back to Oxygen OS
Click to expand...
Click to collapse
I'm facing this same problem as your. I have installed latest TWRP 3.0 using TWRP Manager and using H2OS. Everythig's working fine except when it gets to installation of any other custom rom because I'm simply not able to unlock bootloader anymore nor I'm able to install incremental updates
Whenever I do fastboot oem unlock, my phone gets restarted in recovery mode with error staring "Unable to locate file '16' ";
How did you do it? Could you explain step by step?
thisbansal said:
I'm facing this same problem as your. I have installed latest TWRP 3.0 using TWRP Manager and using H2OS. Everythig's working fine except when it gets to installation of any other custom rom because I'm simply not able to unlock bootloader anymore nor I'm able to install incremental updates
Whenever I do fastboot oem unlock, my phone gets restarted in recovery mode with error staring "Unable to locate file '16' ";
How did you do it? Could you explain step by step?
Click to expand...
Click to collapse
I have the same problem as you with the same error, but I can flash roms and everything else. Just can't flash a new recovery because fastboot commands doesn't work.
you happened to be using H2OS? If yes then know this H2OS forces to override custom recovery with default /stock recovery.
Sent from my ONE E1003 using Tapatalk
Related
Hello All,
I have a problem where TWRP is not able to mount /data, although the device still works without any other problems. It has happened when i upgrade the TWRP recovery from 3.2.1-0 to 3.2.1-1
This is preventing me to install Magis modules unfortunately.
I have a OOS Open BETA 1 for the Oneplus 5T.
Here's the log:
Code:
[COLOR="Red"]Could not mount /data and unable to find crypto footer.
Failed to mount '/data' (No such device)
Unable to recreate /data/media folder.[/COLOR]
Updating partition details...
[COLOR="red"]Failed to mount '/data' (No such device)
Failed to mount '/preload' (Invalid argument)[/COLOR]
...done
Full SELinux support is present.
how can I install TWRP 3.3.0 on android Q beta 4?
I tried the following commands to install twrp 3.3.0 on pixel 2 and failed.
1. adb reboot bootloader
2. fastboot boot ~/Downloads/twrp-3.3.0-0-walleye.img
once I am in TWRP screen,
3. adb push ~/Downloads/twrp-pixel2-installer-walleye-3.3.0-0.zip /
4. install the zip file of twrp while in TWRP
Installing zip file show error message on Android Q beta 3 and 4. But not on beta 2.
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Appreciate your help.
android_ddtt said:
how can I install TWRP 3.3.0 on android Q beta 4?
I tried the following commands to install twrp 3.3.0 on pixel 2 and failed.
1. adb reboot bootloader
2. fastboot boot ~/Downloads/twrp-3.3.0-0-walleye.img
once I am in TWRP screen,
3. adb push ~/Downloads/twrp-pixel2-installer-walleye-3.3.0-0.zip /
4. install the zip file of twrp while in TWRP
Installing zip file show error message on Android Q beta 3 and 4. But not on beta 2.
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Appreciate your help.
Click to expand...
Click to collapse
So why not do
Code:
fastboot flash recovery /Downloads/twrp-3.3.0-0-walleye.img
Then do
Fastboot reboot
Then use button combo to get to twrp.
Usually volume_up plus power for 5 seconds.
Maybe this helps.
Hello,
i have a problem with my Samsung SM-T585. I have rooted it and i will go back to the original Software.
So i downloaded Odin and the newest Software from SamFirm.
I start the download mode and connect my phone to the pc.
Odin says added and i put the 4 files into Odin.
Start the process, all be fine.
The Tablet reboots and starts samsung recovery to erase and then comes a nother reboot.
The tablet is going back to recovery and then comes no command. when i push the power und volum up butten comes the follow window (text)
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File-Based OTA
Supported API: 3
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device map
ping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-sysconfig-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permmission-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creating devi
ce mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
The tablet is then rebooting and the process starts again.
Can anyone help me to fix the problem? i won't be install twrp again the tablet shold be only run the original software.
Thanks for your help
Try This
Hi there,
Have you tried to download the correct region firmware and then flash it.
Kind Regards,
KIBS2173
T585rick said:
Hello,
i have a problem with my Samsung SM-T585. I have rooted it and i will go back to the original Software.
So i downloaded Odin and the newest Software from SamFirm.
I start the download mode and connect my phone to the pc.
Odin says added and i put the 4 files into Odin.
Start the process, all be fine.
The Tablet reboots and starts samsung recovery to erase and then comes a nother reboot.
The tablet is going back to recovery and then comes no command. when i push the power und volum up butten comes the follow window (text)
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File-Based OTA
Supported API: 3
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
dm-verity verification failed...
E:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device map
ping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-sysconfig-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permmission-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creating devi
ce mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
The tablet is then rebooting and the process starts again.
Can anyone help me to fix the problem? i won't be install twrp again the tablet shold be only run the original software.
Thanks for your help
Click to expand...
Click to collapse
KIBS2173 said:
Hi there,
Have you tried to download the correct region firmware and then flash it.
Kind Regards,
KIBS2173
Click to expand...
Click to collapse
Hi KIBS2173,
i have the region firmware from my country downloaded. But it fails all the time.
T585rick said:
Hi KIBS2173,
i have the region firmware from my country downloaded. But it fails all the time.
Click to expand...
Click to collapse
Now i tried the newest version from samfirm. The message is:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No 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 v 1.0.0#
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
failed to mount '/system' (Bad file descriptor)
E:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device map
ping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I hope everyone can tell me what to do.
Try This
T585rick said:
Now i tried the newest version from samfirm. The message is:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No 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 v 1.0.0#
E:[libfs_mgr]Blob verification failed :255
E:Failed setting up dirty target
failed to mount '/system' (Bad file descriptor)
E:[libfs_mgr]Error creating device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-app-link] fail to mount /system as rwE:[libfs_mgr]Error creating device map
ping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-permission] fail to mount /system as rwE:[libfs_mgr]Error creating device m
apping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creatin
g device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[omc-res-permmission] fail to mount /system as rwE:[libfs_mgr]Error creat
ing device mapping: Device or resource busy
E:[libfs_mgr]Couldn't create verity device!
E:Failed setting up dirty target
[hwr_symlink] fail to mount /system as rw
I hope everyone can tell me what to do.
Click to expand...
Click to collapse
Hi there,
are you able to flash a custom recovery. Just try to flash a custom recovery like twrp.
and then install a custom rom.
i think the flashed failed and causing the problem.
so far i think you are facing a soft brick.
if your still having problems use different versions of odin.
and plus reinstall any samsung usb drivers.
kind regards
KIBS2173
Unfortunately I've updated my Samsung Galaxy S8(SM-G950F). Than tried to root it but not successfully. Therefore I need latest(2020.06.01) EFS file for G950FXXU9DTF1
Please, help me to find the file!
____________________________
Android Recover
Code:
[FONT="System"]#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]
dm-verity verification failed…
E:[libfs_mgr]is_dt_compatible(): firmware info was not valid : ’/proc/device-
/Firmware/android/compatible’ : No such or directory[/FONT]
_____________________________
Thanks in advance
Best regards
FYI: /efs ( read: Encrypted File System ) is a partition, not a file
I already unrooted and setup custom os on a couple of Motorola G7 play phones. But on this one, I thought I would try a different way to install twrp permanently.
which was to boot into twrp, then "install recovery ramdisk" pointing it to the recovery.img that I know works correctly with this phone.
I got these messages....
I:Switching slots to flash ramdisk to both partitions
I:Setting active slot B
Updating partition details...
Iata backup size is 867MB, free: 14022MB.
I:checking for twrp app
I:Can't probe device /dev/block/bootdevice/by-name/vendor_b
Failed to mount '/vendor' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/vendor_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/modem_b
Failed to mount '/firmware' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/modem_b', current file system: 'ext4'
I:Can't probe device /dev/block/bootdevice/by-name/dsp_b
Failed to mount '/dsp' (Invalid argument)
I:Actual block device: '/dev/block/bootdevice/by-name/dsp_b', current file system: 'ext4'
...done
Backing up Boot...
I:Reading '/dev/block/bootdevice/by-name/boot_b', writing '/tmp/repackorig//boot.emmc.win'
I:Restored default metadata for /tmp/repackorig//boot.emmc.win
I:Error unpacking /tmp/repackorig/boot.img, ret: 256!
Error unpacking image.
I:Set page: 'action_complete'
Iperation_end - status=1
At this point, I realized I didn't previously flash dtbo.img. I suspected if I reboot I would brick the phone. I decided to reboot to bootloader anyway. because to start flashing over the top of this seemed like a bad idea.
Which I in fact bricked the phone.
What should I have done at this point? Gone ahead and flashed dtbo from the PC while in twrp? flashed a copy of the boot.img (from my PC?). before I rebooted?
I actually have found NO info on why I am reflashing dtbo, or whats in these modified dtbo's, or how to tell I need to flash the dtbo. Or if it's even correct "before" commiting to unpacking/repacking the boot image.
And there are multiple links to different modified dtbo's and different instructions sometimes leave out no-verity-opt-encrypt.zip For the record I didn't do this no verity step on the last couple phones and worked fine.
What is the procedure to fix the boot before I reboot out of twrp. And how do I know I have a good copy of a modified dtbo
How can I tell I have (or not) already flashed dtbo?
So since this phone seems to have borked Slot B. Can I unbrick it somehow by going to Slot A? It does not respond to anymore to VolumeDown-Power button so it really bricked for good or not?
Sorry for all the questions, but I think this would save a ton of people wrecking phones.