[Bricked] Zombie FRD-L04 - Honor 8 Questions & Answers

[Bricked] Zombie FRD-L04 - Honor 8 Questions & Answers

so i recently found an honor 8 in my closet that i want to give to my little niece as a starter phone before i buy her an iphone. the problem is that its bricked. i remember flashing omniROM a few months ago and then horribly bricking the phone. the phone just boots to the EMUI boot logo and then reboots. i cant access the e-recovery and when i go into fastboot i get the following info on the screen:
Code:
FASTBOOT&RESCUE MODE
Android reboot reason:
AP_S_PANIC
data is invalid
volumnkey_down_press_process_func
PHONE Relocked
FRP Lock
the thing is, when i go into cmd i get this:
Code:
C:\honor fix>fastboot devices
RNV0216831000137 fastboot
C:\honor fix>fastboot oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.015s]
Finished. Total time: 0.019s
i have tried flashing the stock recovery it wont let me. is there any hope of saving this phone? btw, my laptop was stolen and it had by unlock code so thats gone. any help is greatly appreciated. cheers!

Related

[Q] My htc one sv will only go to boot loader

so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me

Check the guide at HTC side if you have done everything correctly, all is written how it should or copy and paste.
Without unlocked bootloader, there is no chance to rescue your phone.
Any information about your phone model and exactly the step it fails is important, too.

this problem has such a friend, and it does not solve constantly locked bootloader ...

Does anyone solved this problem?The same situation of my phone?Please help!

Hi,
i flash 2.8.4.0twrp, then make backup, after that (whit in recovery options) try to make factory reset, and after that my one sv is messed up like hell...
It is not booting...stuck for a while at htc logo, screen goes black, then loads bootloader, I am able to go to twrp (I have fresh backup of complete phone, did it with twrp above), but not able to flash anything...it fails every time, saying that is unable to mount cache...try advance wipe, but it is not able to mount any thing...
Since my phone was S-off, unlocked bootloader, superCID (it is k2ul), hboot2.0, I tryed with fastboot oem relock (to lock bootloader, and flash stock pl80img.zip) but that fails too, ends up with to many links message...and bootloader stays with tampered and unlocked sign...before flashing 2.8.4.0twrp phone was working great, but after factory reset it is not able to mount anything, and running pl80img.zip gives me all so only fail...fail...fail...
So..now i have latest twrp and totaly messed up phone...
How can U help me, anny advice???
THX in advance!

danrock1984 said:
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Click to expand...
Click to collapse
I have the same problem!!
The phone details:
Locked Bootloader
K2_UL XA SHIP S-ON RL
HBOOT 2.00.0000
T-mobile network lock
NO SuperCID
The phone doesn't boot up!
It boot to bootloader fastboot mode always!
The notification led blinks constantly!
When I wanted run the RUU (K2_UL_ICS_EUROPE...etc) the phone doesn't reboot black HTC Screen it goes back to bootloader, and it doesn't working
After I downloaded this:
https://www.androidfilehost.com/?fid=23212708291675772
After I download it rename to PL80IMG.zip and it loading after checking, and goes back to bootloader, no volume up to update option!
After I downloaded OTA_K2_UL_JB_45_S_Voda-Hutch_AU_2.14.862.9-1.17.862.9_release_3136147vue6nb55rwgyw0d.zip
After I extracted the firmware zip from it, edited the android-info.txt CID number to HTC__032 and place it to SD, rename to PL80IMG.zip after I get the same problem!
After these problems are try another method with fastboot!
fastboot flash zip flash firmware zip and I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot flash zip firmware.zip
sending 'zip' (33772 KB)...
OKAY [ 2.668s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.264s
C:\Users\Erkaft\Desktop\Új mappa>
And when i want to erase all with fastboot I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase all
erasing 'all'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: -0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: -0.000s
I also tried bootloader unlock but the last message didn't appear on the phone and it stay locked
Any idea to ressurection this phone?

You need ti unlock your phone,otherwise you can't do anything.

Softbrick, can't unlock bootloader, that's why I cant unbrick it, pls help!

So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!

GriechischerYoghurt said:
So hello! I need some help here. A friend of a friend gave me this oneplus one for repair and at first it seemed easy cause i thought oh it's only a softbrick. There is a bootloop and I can access the original recovery and Fastboot. Now when I followed the unbricking guides I could not clean install CM12S because appereantly the bootloader is not unlocked but do I need to have an unlocked bootloader to install a clean signed version of CM12S?
I am trying to solve the issue with bacon root toolkit 1.0.3. I put the OPO into fastboot mode and click on "back to stock", select a signed fastboot version cm12.1s and my device is detected as a fastboot device. But now i get these weird error codes in command prompt
" FAILED (remote: Device not unlocked cannot flash or erase)" and then just another bootloop.
So I tried to unlock the bootloader with the command "fastboot oem unlock" and it does something but then when i check it with "fastboot oem device-info" it displays
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.007s]
finished. total time: 0.008s"
hmmm.. so it does not unlock the bootloader but what does device tampered mean?
How do i unlock the bootloader and ultimately unbrick this device?
any help would be greatly appreciated!
Click to expand...
Click to collapse
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.

e1forall said:
Hi
Trying to help.
Your device might be tampered as the "fastboot oem device-info" result shows.
Follow the steps and see if it helps (all commands below are to be entered without quotes)
1. Download latest cm13 nightly or the cm12.1-snapshot and extract the "boot.img" from it.
2. Connect the phone in fastboot mode and check connection by "fastboot devices."
3. Enter the command "fastboot flash recovery boot.img" (the one extracted above).
4. Then enter "fastboot format cache".
5. After the boot.img is flashed, enter "fastboot reboot" to reboot the phone and the let the phone boot fully to homescreen. If stuck on bootscreen( i assume rom is not tampered with) try entering stock recovery and clear cache and dalvik-cache.
6. Now again enter bootloader by reboot or using combo and check connection by "fastboot devices".
7. Now enter "fastboot oem unlock".
8. Now check "fastboot oem device-info".
It should be unlocked like:
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
Please do reply if it helped.
Click to expand...
Click to collapse
Thanks for the reply! I tried the steps but sadly it did not work.
I downloaded cm13, extracted it to my fastboot.exe folder and did enter the commands.
"c:\unlock>fastboot devices
9c50d771 fastboot"
So my device does show up which means drivers are properly installed aren't they?
"c:\unlock>fastboot flash recovery boot.img
target reported max download size of 1073741824 bytes
sending 'recovery' (7254 KB)...
OKAY [ 0.232s]
writing 'recovery'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 0.254s"
There is the error message again, I can't flash the stock recovery becaue the bootloader is not unlocked I think but I don't know what else to do.
then:
"c:\unlock>fastboot format cache
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.068s"
I did that too, I can't tell if it formatted cache or not, I dunnoooo
and then i entered the two commands to unlock and then check the bootloader:
"c:\unlock>fastboot reboot
rebooting...
finished. total time: 0.005s
c:\unlock>fastboot devices
9c50d771 fastboot
c:\unlock>fastboot oem unlock
...
OKAY [ 10.102s]
finished. total time: 10.106s
c:\unlock>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.013s]
finished. total time: 0.014s"
sooooo it sadly did not work

smarttmd said:
Hi I had the same problem a couple of weeks ago, if you're able to boot into a custom recovery, flash this http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 it's an alternative way of getting bootloader unlocked. Hope it helps
Click to expand...
Click to collapse
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C

GriechischerYoghurt said:
I have looked into that but how do I flash it?
I tried the commands "fastboot boot -image file-" but it says i cant do that cause once again the bootloader is locked
then there is "fastboot boot recovery -image file-" but then it says " cant find directory" or something like that..
could you please give me step by stepe instruction how you solved the issue?
I am getting very frustrated here.. beginning to think it's unsolveable.
sadly i can't boot into a custom recovery :C
Click to expand...
Click to collapse
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?

smarttmd said:
You flash this zip in a custom recovery like any other mod. Luckily for me I still had my twrp installed so I managed to do it, but you should be able to temporarily boot from it. Is your custom recovery image in the active directory?
Click to expand...
Click to collapse
yes it's in the directory from where i start command prompt

Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too. Here i

GriechischerYoghurt said:
I tried that too. Here i
Click to expand...
Click to collapse
Rough spot to be in then. Hopefully someone has some other ideas for you to try. Good luck bud.

meekrawb said:
Try ColorOS fix if CM doesn't work. http://forum.xda-developers.com/one...neplus-one-t3013732/post58442392#post58442392
Edit: (Only if you can't get anything else to work, though)
Click to expand...
Click to collapse
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.

I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!

GriechischerYoghurt said:
I tried that too.. Spoiler.. it did not work.
The drivers seem to work. I have my windows 10 set to testmode. The OPO is recognized by the Msm8974DownloadTool,, when I click on "start" the bar moves to 3/4 of the bar but then something happens and I get a "sahara" message". I tried it maybe over 10 times now. Sometimes it shows me the message immediately. Sometimes the green bar gets to 1/4 of the bar and then the "sahara" message. But sometimes the bar gets to 4/4 one time and then it says "(somethinsomething)usb(somethingsomething in chinese i guess)" and thats it. Only bootloop as a result. Maaaaan this is getting annoying.
Click to expand...
Click to collapse
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.

ryanmat said:
I think where something might have gone wrong was trying to use a toolkit. Try this:
Download latest fastboot images from here: http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
Then go here: http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Scroll down to #8 and follow the instructions to flash all of the images using fastboot. Hopefully, you will be able to boot the phone after that. Good luck!
Click to expand...
Click to collapse
Thanks for the reply and trying to help! but as I stated in the title my bootloader is LOCKED so i can't write anything to it. The guide of Heisenberg states clearly "Prerequisites: unlocked bootloader." so I knew it would not work but I tried it anyway.. sadly it did not work.. this is what it's giving me:
"C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>fastboot flash modem NON-HLOS.bin
target reported max download size of 1073741824 bytes
sending 'modem' (57457 KB)...
OKAY [ 1.804s]
writing 'modem'...
FAILED (remote: Device not unlocked cannot flash or erase)
finished. total time: 1.804s
C:\Users\Abdulla\Desktop\cm-12.1-YOG7DAS2K1-bacon-signed-fastboot-bed37f2e18>"
funny thing is, it's "only" a softbrick but behaves like a hardbrick. I can't do anything and I don't know what to do at this point.

meekrawb said:
I think the last time I used the ColorOS tool was on Windows 7. Windows 8/10 seems to be a real nightmare.
Click to expand...
Click to collapse
I will try the ColorOS hardbrick method on a virtual XP machine and report back.

I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.

GriechischerYoghurt said:
I tried it on a virtual XP machine but i can't get to mount the OPO, i get this error message.. now the first sentence is german and its says " the usb device Qualcomm CDMA Technologies MSM QHSUSB__BULK could not be mounted on the virtual mashine windows xp."
"Das USB-Gerät Qualcomm CDMA Technologies MSM QHSUSB__BULK konnte nicht an die virtuelle Maschine windows xp gebunden werden.
USB device 'Qualcomm CDMA Technologies MSM QHSUSB__BULK' with UUID {cdedf1ad-9235-40ef-80cf-efc72ba7678c} is busy with a previous request. Please try again later."
I don't even know if it's worth the effort trying to find a XP system and try it.. my hopes that it would work are very low at this point.. please let me know if you know a solution to this nightmare.
Click to expand...
Click to collapse
When you do a fastboot oem unlock does it reboot you back into recovery?

I used HighOnAndroid's guide to unlock bootloader, flash a custom recovery, and root.
Tutorial Video
https://www.youtube.com/watch?v=vPv2DYnH3S8&index=9&list=PLB86F041EAFE4F3E5
Step-By-Step and Downloads
http://highonandroid.com/android-smartphones/how-to-root-oneplus-one/

Why don't you flash firmware in unlocked bootloader, if possible ( please refer in the forum, as i think there's a way to flash firmware and then you can unlock bootloader )

Go to an independent repair shop. They have the equipment to flash on the motherboard.

Hard Bricked FRD-L14 "FAILED (remote: Command not allowed)

So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .

Kc4k12 said:
So for the past week, my phone has been bricked. Bricked by flashing the wrong firmware, so now not able to access the whole phone, and making matters worse by flashing the wrong recovery for the phone. The phone being an Honor 8, FRD-L14, 64GB.
I'm not able to use dload to rollback anything, or use that option at all, since the recovery isn't eRecovery, and doesn't even have any recovery in itself.
The problem is that I'm able to boot into "download mode" my phones unlocked, and when I type in "fastboot oem get-bootinfo", the response is:
(bootloader) unlocked
OKAY [ 0.008s]
finished. total time: 0.010s
But when trying to flash anything through fastboot in the cmd, like the command "fastboot flash recovery recovery.img" to flash a recovery on the phone, the response would then be:
target reported max download size of 471859200 bytes
sending 'recovery' (29378 KB)...
OKAY [ 0.803s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.814s
My phone is unlocked, and on the download mode screen, is shows:
PHONE Unlocked
FRP Unlock
My drivers are installed, as well as the device being shown in fastboot when typing in the command "fastboot devices"
I haven't been able to do a single thing to the phone, and have searched up a countless amount of hours to find the fix for the phone, if anyone can, please look into the problem and assist me, thanks .
Click to expand...
Click to collapse
You're in a tough situation my friend, what do you get when you try the dload method? In my opinion this is the only thing you can do. However i heard about a thing called "DC Unlocker" . It can flash a clean ROM and other good stuff for bricked Huawei phones, but you have to pay, and i don't know what the prices are. Hope you'll make it

Honor 6X - Can't flash recovery

Hello
I have a Honor 6X running EMUI 5.0.3 and BLN-L21C432B382. I unlocked my bootloader a long time ago using Huawei code.
Unfortunately, I can't flash the recovery anymore (I don't know why TWRP is not available anymore, I might have done something wrong), indeed, when I restart into fastboot mode, frp is unlock but phone is locked and when I run the flash command, I get the following error:
Code:
sudo fastboot flash boot Downloads/twrp-3.1.1-0-berlin.img
target reported max download size of 471859200 bytes
Sending 'boot' (24466 KB)...
OKAY [ 0.639s]
Writing 'boot'...
FAILED (remote: Command not allowed)
Finished. Total time: 0.706s
And it seems that the bootloader is locked:
Code:
sudo fastboot oem get-bootinfo
(bootloader) locked
OKAY [ 0.006s]
I have to say that I don't know what to do (I would like to install a newer version of Android on this phone).
Could you please help me
Thanks

Have you enabled OEM unlock in developer settings? And, how many time ago did ya unlocked the bootloader? In firmwares newer than a certain date (June 2018 if i don't remember bad) those geniuses at Huawei released builds that automatically relocked the bootloader (happened to me also), so you may have to unlock it again.
Anyway the correct command in fastboot is "fastboot flash recovery (nameofrecovery).img", not sudo flash boot because you'll end up flashing a recovery image to boot image, probably messing up stuff. Luckily this time your bootloader was locked, anyway pay attention because in Huawei's world it's easy to f**k up in a question of seconds!

Yes I enabled OEM Unlock in developer settings.
I think that you are right, I unlocked my bootloader a long time ago (probably 2 years ago). I read that Huawei does not deliver the code to unlock the bootloader anymore, is that right ? (I can't find my old code).
Regarding the command I ran, you're totally right, I tried first first fastboot flash recovery and as it was not working and wanted to make it work (.....) so I tried to run the flash on the boot (which was a pretty bad idea, I agree).
Thanks

Yeah if the unlock has been made 2 years ago, surely the bootloader is locked again now. Sadly yes, Huawei has stopped support about unlocking the bootloader last year, so unless you'll find it again you'll have to pay some third party service like DC-Phoenix/FunkyHuawei/ecc. to obtain it again.
And seriously, be careful about flashing one specific image to a different partition. This is an error that could lead to serious troubles in worst scenarios. Nothing hard to do dude, next time thank me with the dedicated button, it's there exactly for its purpose :highfive:

Google Pixel bootloop Problem

Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.

iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying:

Database Info

welcome