Hi!
Got a problem, need to send my p9 lite to service bc it fell with me into water. it still works, but I assume a chip is frozen because neither the wifi nor bluetooth can be turned on. I'm afraid theyre not fixing my problem because I unlocked it.
I flashed twrp recovery, rooted, but already flashed the stock rom and unroot again.
When I tried to relock with adb and bootloader code, I got the error code root risk is too high
Tried to install other stock roms again and a lot of stuff, but none of it worked. So I tried to relock via dc-unlocker. com but didnt work. But now it says when I restart "your device has failed verification and may not work properly." instead of "Your device has been unlocked and can't be trusted." and when I tried to use adb to relock with the bootloader code it says "remote: stat not match" ~ got a new bootloader code??
I'm desperate, can anyone help me?
put update.app into dload folder in micro sd card and try 3 button method.
hey i have just the same problem and when i try the 3 button method i get the error software install failed.
but i have no revolution twrp any more and i think also no erecovery beacuse i cant do a factory reset when i tried to enter erecovery with power button , volume + button then i go automatic to software update and at the 5% i get the error software install failed i hope some body get a solution to fix my phone without dc-unlocker
ps i was on android nougat but i think there any os now because the phone dont boot sorry for my bad english hahah
Hi! Today, I decided to try to install GCam on my Mi A1 running the August 2018 update. I have successfully installed the GCam Mod on my Mi A1. But when I wanted to lock the bootloader, I accidentally wiped clean all my data and now there is a pop-up stating my system has been destroyed. I cannot boot into the stock ROM, however, I can enter fastboot. So, I tried flashing the stock ROM into my phone using the XiaoMiFlash tool. It failed and showed me an error message. That error message can be seen here: imgur.com/a/naxM0WB (sorry I haven't posted enough posts to grant me URL sharing). I assume the error was caused because my phone has a screen lock. Also, the ADB drivers don't recognize my device and my phone also failed to enter EDL mode. BTW I'm a newbie to this and I cannot do anything that will involve me opening the device.
Can anyone please help me flash the stock ROM?
Thanks,
KN
SOLVED: So, it turns out that you need to unlock your device with Mi Unlock and everything will be back to normal.
You have locked your bootloader with modified system. Unlock it and reflash stock ROM.
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
meohmy said:
It's a long story but I soft bricked my G928F.
I bought it off Gumtree in the U.K and it had an frp lock on it, the seller stated that she had wiped it off so would not take it back. I had a read around and it seemed that Wondershare Dr. Fone would take off the frp lock........it didn't, rather it messed up the stock recovery. When attempting to enter recovery I get the following message and am stuck in a bootloop:
No Support SINGLE - SKU
Supported API: 3
dm-verity error
failed code: 0x02
E: failed to mount /cache (invalid argument)
While Odin will recognise the phone Smart Switch will not so I am unable to use the emergency recovery procedure.
I have read similar posts where it implies Smart Switch is the last resort but in my case that doesn't seem to be an option
Can anyone suggest a way to recover the phone or do I throw it in the bin? Any help appreciated
Click to expand...
Click to collapse
Flash this using odin :
https://drive.google.com/uc?id=1tg9hJOCquyfuyROYtgpxyVKNbuidzdL8&export=download
Then, you will be able to flash latest version normaly, and also your will remove frp lock.
Thanks for that, I will flash it when I get home and report back.
Didn't work for me, the combination file gave an 'md5 error! Binary is invalid' message when loading into Odin, while renaming to .tar the flash failed.
firmware update start
Single download
sboot bin
param.bin
FAIL
Thanks for your suggestion though.
I tried installing firmware G928FXXS5CRH1 (VOD) but it failed at hidden system image, I removed that file and created a .tar which flashed successfully but the phone rebooted
to recovery initially but still showed a dm-verity error. I deleted the cache and then factory reset which appeared to also complete successfully but the phone would not boot up.
I then tried flashing the hidden sys image on its own but that failed and the phone went to the Smart Switch error recovery page, Smart Switch will not recognise the phone so will not allow access to the emergency recovery facility.
Still trying though if anyone has any idea's.
Hi there,
Im in the same boat. It had the verity error too.
BUT:
For me it worked to flash the 4-part firmware of the G928FXXS5CRH1 via Odin then.
The device boots again, without the verity error
It had Android 5.1 before, when I could flash the COMBINATION ROM and use it just fine.
(but it was a Android 7 combination ROM) :/
After flashing Android 7 debranded (G928FXXS5CRH1) in 4-parts (BL, AP, CC and CSC file) the FRP lock is still there of course,
but the phone is booting again without the verity error.
COMBINATION ROM will no longer let me flash it, though.
https://forum.xda-developers.com/s6-edge-plus/help/g-928f-verity-0x02-modem-bin-fail-t3886122
The download I did via the tool "samfirm" use chk32 and decrypt on downloading !
"SM-G928F_1_20180828170540_5avji4munw_fac"
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
meohmy said:
Thanks for the reply, I fixed it myself in the end. I spent 2 days over Xmas until I eventually tried the solution that you have suggested. I eventually found a 4 part software. AS to the FRP lock, be it good luck or persistence, I managed to get rid of that as well using Samsung FRP Tool.
Click to expand...
Click to collapse
Hell Friend, Not sure If you could get this message, If yes, Kindly help me., I am facing the same issue with my Samsung Galaxy Note 5 (N920G/I) but could not find 4 parts FRP unlock firmware. Do let me know If anyone finds one.
Thanks!
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
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 mapping: 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 mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[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-permission-permission] fail to mount /system as rwE:[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-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating 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'm having the same and exact problem as in this video with same brand device S7e https://youtu.be/l8-ccufk4Q0 the man could save the device by installing TWRP because frp was off. I can't do the same because I got frp on
I used to play with a whole Frp Remover Tools but nothing helped or worked, and also tried some cracked boxes but unfortunately they seem just like interfaces and didn't work as well
If I ended with frp lock turned successfully off then everything will be easy, installing TWRP then flashing through it no_verity_encryption will solve the issue and the device will boot the system successfully, I need to turn it off, if anyone has a solution please help!
TheDevelopper said:
Hi everyone! Help! Need help! As titled, i have almost tried everything, frp lock is enabled i can't acces to recovery menu and i'm unable to flash TWRP recovery or boot into normal recovery, frp lock blocked everything, i can just access to download mode
Please, I need some help with my SM-G9350 Hong-Kong Galaxy S7 edge on Binary 4
I got custom binary TWRP recovery/boot blocked by frp lock when the device was working fine running custom rom, and then I flashed stock firmware via Odin and all was just fine and Odin succeed pass, but when installing system updates in recovery it was up to 32% then erasing and then it should boot up system, but it didn't it keeps rebooting to recovery with no options at all, just showing the android guy with no command below and then when I hard it to enter in recovery menu it shows a black screen with some lines that says couldn't open recovery cause unknown and no such file directory, and device is busy, and keep doing the same thing, I did same and flashed again with latest firmware but same thing happened, and then I tried to flash TWRP in order to flash a custom rom to boot up system, but Odin fails and says in download mode custom binary recovery blocked by frp lock, known that my device's bootloader is already unlocked and I flashed before this a whole of stuff, now, I can just access to download mode, otherwise I can't do anything else even no adb , there is no a combination file for the Hong-Kong variant G9350ZH, there is only for the Open-China variant G9350ZC which is not combatible with the device, even there are no adb enabled files, if someone has a solution for this, please kindly take care of this problem?
No menu in stock recovery, it's just saying:
#fait to open recovery_cause(No such file directory)#
#Reboot Recovery Cause is [UNKNOWN]#
No Support SINGLE=SKU
File-Based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E: [libfs_mgr]Blob verification failed :255
E: Failed setting up dirty target
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 mapping: 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 mapping: Device or resource busy
E:[libfs_mgr] Couldn't create verity device!
E: Failed setting up dirty target
[omc-sysconfig-permission] fail to mount /system as rwE:[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-permission-permission] fail to mount /system as rwE:[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-res-permission] fail to mount /system as rwE:[libfs_mgr]Error creating 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
Click to expand...
Click to collapse
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Thank you man, yea, you're right cause we tried almost everything but unfortunately can't recover it too :/
klabit87 said:
[/HIDE]
This isn't good.... Unfortunately I can't help with this matter. I bricked my s7 and ended up exactly like this. I have not been able to recover it. So I gave up. Sorry to be the bearer of bad news.
What happens when you Odin your full firmware package?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
TheDevelopper said:
Odin success passed the firmware's packages without problems, and it is the right one @klabit87, actually, there is a chance to recover the phone, I have found a video on YouTube having the same and exact problem as me with same brand device S7e, the man could save the device by installing TWRP because frp was off, I can't do the same because I got frp on https://youtu.be/l8-ccufk4Q0
Click to expand...
Click to collapse
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
I think there are ways around frp though... I could be wrong though.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
If only it can be turned off, I'll flash TWRP
TheDevelopper said:
If only it can be turned off, I'll flash TWRP
Click to expand...
Click to collapse
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
q
klabit87 said:
I wonder if you could use a custom kernel with dm-verity removed altogether. You could Odin it. No need for twrp. What firmware version is currently installed? I will compile it for you if you want to try it. Maybe try verity will get you to a point where you could remove frp while booted. Is your bootloader still unlocked? As in OEM unlock I mean.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
When tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
TheDevelopper said:
qWhen tried to flash TWRP, it says custom binary recovery block by frp lock
And when tried to flash a custom boot that I took from a custom ROM and I Tared it, it says custom binary boot blocked by frp lock, I don't know if frp is related to OEM unlock or not and I don't know why it failed to Odin the boot that I took, the current firmware is CSC1 ..link for appropriated boot.img https://desktop.firmware.mobi/device:454/firmware:19931 if the device will read it as a custom one I don't think it will bypass it so, I would not disturb u if actually the phone will refuse it
But if crom service still off that means the bootloader is unlocked, once running for the first time on the device no need to use it anymore and the bootloader will be unlocked, but I don't know if OEM is enabled and it says in download mode secure download enabled
Click to expand...
Click to collapse
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
klabit87 said:
Ah ok. You're right it won't flash then. Sounding like a qcom CDMA tool might help. I've seen a couple that allow you to remove frp but I believe it requires entering qshusb mode. But it seems like options just get more and more slim now
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
Yes, playing around a right tool can remove it, searching and testing ..
Edit: @klabit87, all the tools failed
I have same model and same problem. Did you find any solution?
hi, do you have any update? I have the same problem and the same model too
Do anyone still need help in fixing this issue?
I would like you to join me in this experiment to fix your device.
how we start it ?
bawsobb said:
how we start it ?
Click to expand...
Click to collapse
Please PM me then we will first try to fix it and then post a tutorial here on XDA.
Yesterday suddenly while turning on my device it stuck at android one logo.
Device status : Bootloader locked, No Root. Never hard reset in past. it was running as it was out of the box with latest May 2020 security update.
So, i tried to unlock bootloader with adb which offcourse failed.
then i tried to hard reset, as i opened recovery mode (power + vol+) there was an error E: failed to load bcb message, failed to fsync : operation not permitted.
still i choose wipedata/factory reset. it stuck at [wiping data... formatting disk...] for 5 hours. i understood it wont proceed.
Then, i opened the device went to unlock bootloader with EDL method as shown in few videos ( by connecting pins and plugging usb to pc). it showed in the pc ( qualcomm was listed in device manager> ports)
Then i downloaded Mi flash and official rom, was unable to flash with error "ack count don't match".
Again reading here and there, i downloaded miflash-beta, it was able to flash the device successfully.
disconnected the usb, connected the battery strap and started device > Again it stuck at android one screen for 1 hour.
So, i again went to recovery mode to find out that the error " E: failed to load bcb message, failed to fsync : operation not permitted." Still exists.
Read here in some thread that it is related to partition damaged, but no solution anywhere.
Please help me with solution. This is my only phone. i don't have any job nor money to buy other phone during lockdown.
HELP.
Thanks everyone for this wonderful forum.
MIA1_Stuck said:
Yesterday suddenly while turning on my device it stuck at android one logo.
Device status : Bootloader locked, No Root. Never hard reset in past. it was running as it was out of the box with latest May 2020 security update.
So, i tried to unlock bootloader with adb which offcourse failed.
then i tried to hard reset, as i opened recovery mode (power + vol+) there was an error E: failed to load bcb message, failed to fsync : operation not permitted.
still i choose wipedata/factory reset. it stuck at [wiping data... formatting disk...] for 5 hours. i understood it wont proceed.
Then, i opened the device went to unlock bootloader with EDL method as shown in few videos ( by connecting pins and plugging usb to pc). it showed in the pc ( qualcomm was listed in device manager> ports)
Then i downloaded Mi flash and official rom, was unable to flash with error "ack count don't match".
Again reading here and there, i downloaded miflash-beta, it was able to flash the device successfully.
disconnected the usb, connected the battery strap and started device > Again it stuck at android one screen for 1 hour.
So, i again went to recovery mode to find out that the error " E: failed to load bcb message, failed to fsync : operation not permitted." Still exists.
Read here in some thread that it is related to partition damaged, but no solution anywhere.
Please help me with solution. This is my only phone. i don't have any job nor money to buy other phone during lockdown.
HELP.
Thanks everyone for this wonderful forum.
Click to expand...
Click to collapse
did you find any solution
Same with my phone. Did you find any solution ?