Huawei P20 bricked, bootloader locked, FRP locked, USB debugging disabled, not rooted. Is there a way to restore data? - Huawei P20 Questions & Answers

Hi guys, my friends phone suddenly got bricked with error: Your Device has failed verification and may not work properly
Phone was never rooted, never unlocked bootloader, usb debugging was not enabled.
I am only able to boot to recovery. If i try recovery i always get "Get package info fail".
I did not try factory reset as the data in the phone is really important to him.
Phone is visible to fastboot, but not to ADB. Its also not visible to HiSuite.
I have been trying for 2 days but this seems to me like impossible situation, to recover the data.
anyone has any solution?

@kmet11 you can use HiSuite Proxy and Recovery OS https://github.com/ProfessorJTJ/HISuite-Proxy/wiki/System-Recovery-Rom-Instruction-(-Soft-Bricked-)

Related

[Completed] Enable USB debugging on phone stuck in bootloop

Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
mellobc said:
Hello,
I am currently in a situation where USB debugging was not enabled, CROM service status is set to "Locked". This is causing an issue on my International Galaxy S6 Edge (g9250) -- It is stuck in a boot loop and the android OS that was previously installed was wiped on accident through the stock android recovery mode.
I am unable to flash TWRP recovery to the phone, I am unable to use Odin to flash a stock ROM image to the phone, or perform any data transfer between my Windows machine to the phone. Now I am sure this is because I never enabled developer mode and turned on USB debugging, and also because this CROM service is set to lock. When I attempt to sideload using ADB I get error:closed. When using the Skipsoft Unified Android Toolkit any task performed stops at: "Waiting for USB debugging".
Is there any solution for this? I've looked all over the internet and haven't been able to solve my issue -- I'm stuck at a perpetual boot loop because there is no Android OS on the device's partition, and also am unable to flash the stock ROM using ODIN or sideload using ADB.
Is there is a way to turn on USB debugging when stuck in a bootloop? Or a way to disable CROM service on the phone to be able to flash or transfer files?
As of right now the device is completely useless and I have been researching for the past 5 days
Any help is very appreciated, please let know if there is more information needed.
Click to expand...
Click to collapse
Greetings and welcome to assist. Can you get into download mode ? If you can does smartswitch emergency firmware recovery work
Regards
Sawdoctor

Bricked my Honor 8 FRD-L09

I was flashing a custom rom, when i couldnt install GAPPS, i tried rebooting my phone, and it didnt work. So i went into TWRP and formated the device. When i reboot it get stuck on the device cant be trusted thing (from unlocking the bootloader.) So i go into the Huawei eRecovery, and try to install software with Wi-Fi. However it says getting package info failed. My PC doesnt recognise my phone either.
Is there anything i can do, please help.
I managed to fix it in some way
I fixed it, its no longer bricked.
Repair 100%
i had my honor 8 so bricked that only worked the bootloader and what worked for me was:
https://forum.xda-developers.com/honor-8/development/firmware-huawei-honor-8-frd-l19-stock-t3696902
for someone who might need it

Samsung J700T1 stuck on error

Hi,
A friend of mine bought a Samsung J700T1 in a second-hand shop, which happens to be locked by FRP.
I tried various things to unlock FRP, and now I'm in a situation where I have a blue screen error when I start the phone: "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC software".
I've tried with Smart Switch, but it's asking for a code which I don't have.
I'm able to boot the device in Download mode, but that's all. When I plug the phone to my PC, a Samsung modem is detected, but is not recognized by ADB.
What would be the next steps? Is it possible to flash a rom or will I be blocked by FRP anyway?
Thanks in advance
I reflashed the system, boot, recovery using Odin (in a rush) on a j700t. Now it has the custom binary FRP error and wont boot. I cant get it to go past the download warning screen either. Vol+ or Vol- dont do anything.
I usually use Linux. Now I cant get it to show up with dmesg or lsusb, so no adb or heimdall. Does anyone know how to get back into this phone?
Thanks

Device state locked.

This post is more like an explanation.
So my phone got bricked today, stuck at logo. I managed to access recovery and format data, but its stuck at formating data for more than 6 hour.
The only choice left is to unlock bootloader and flash firmware. Now here's the bull**** part.
When i try press fastboot oem unlock it says failed, device state locked. Device state can be set to unlock only through one method, by booting>going into settings>developer options>turning on oem unlocking. Doing this set your device in unlocked device state and thus allow it to unlock bootloader through fastboot. But, if your device got bricked and can't get into phone and your oem unlocking was off (average person will not set it to on) then you're ****ed, cuz without it you cannot unlock bootloader, thus you cannot install twrp or flash firmware.
This is so dumb, not even adb can set the device state to unlock. Read the last paragraph - (https://source.android.com/devices/bootloader/locking_unlocking)
There are so many post like these but no answer. so this post is for those guyz.
guess, i'll use feature phone for rest of my life
That an Android device's bootloader is locked by default isn't dumb, it has good reasons.
BTW: Flashing device's Stock ROM doesn't require device's bootloader got unlocked before.
tried flashing stock rom using adb sideload and fastboot. both failed. adb states that it cannot as it is a downgrade. fastboot says that device state is locked.
Yes, im aware that it is present for a good reason, but someone who's phone doesnt boot up has no way to unlock bootloader or do anything.
I'm not sure that I have the same problem but I have Samsung sm-t500 on the download mode says : device state lock and Im searching for FRP software but I think it won't happen because I tried too to connect via ADB and still can't connect.. But mine is still not bricked.. I will be very happy if you can give me some advice

Bricked after trying to relock bootloader

Hi all
I had just finished installed Lineage and twrp succesfully to setup this phone, but I then discovered that the unlocked bootleader was preventing me to install Netflix.
I then tried to re-lock it via "fastboot oem lock" which apparently worked, but the side effect was that my main system is now not booting at all.
And when I've then tried to unlocking it again, it just fails, so I'm currently closed out.
Right now I can only access fastboot mode.
Any idea if this can be saved?
thank you
It can be saved but you need to use EDL mode (Emergency Download Mode). This mode is locked by Xiaomi and you Need an authorized account to use It.
You have 2 options:
- Pay a man that have an authorized account and can flash the stock rom from EDL.
- Go to an authorized Xiaomi center.
Thank you. Luckily that was not the right answer.
I've managed to put the phone in EDL mode via hardware, after opening it up.
After bypassing also the lack of helo message error, I've finally manage to flash with Xiaomi Flash tool and regained access to it.

Categories

Resources