Database Info

GPE HTC ONE has a weird Issue

Hi guys!I have a weird problem on my HTC one.which is Google Play Edition.First of all,I was updating my htc to 5.0.1 lollipop which is official via OTA.It took a lot of time and I shut down the phone.And then everything is going to worse.It stuck bootloop unfortunately usb debugging is off ,and the phone is completely stock.(stock recovery,s-on,locked bootloader) I cant do anything due to this problem.I tried "adb push" and flash ruu but they also didnt work.How can I do?Thanks for helping.

reset?
what's the sound like on it?
i know on the ones with htc sense it is hit and miss call quality (with an audible hissing sound).........

fatihlale said:
Hi guys!I have a weird problem on my HTC one.which is Google Play Edition.First of all,I was updating my htc to 5.0.1 lollipop which is official via OTA.It took a lot of time and I shut down the phone.And then everything is going to worse.It stuck bootloop unfortunately usb debugging is off ,and the phone is completely stock.(stock recovery,s-on,locked bootloader) I cant do anything due to this problem.I tried "adb push" and flash ruu but they also didnt work.How can I do?Thanks for helping.
Click to expand...
Click to collapse
You could try to erase cache using fastboot and see if it can boot. If not try a factory reset.
If factory reset still doesn't work you'll have to unlock your bootloader, flash a custom recovery and resotre a nanadroid backup or flash a stock rom of 5.0.1.

alray said:
You could try to erase cache using fastboot and see if it can boot. If not try a factory reset.
If factory reset still doesn't work you'll have to unlock your bootloader, flash a custom recovery and resotre a nanadroid backup or flash a stock rom of 5.0.1.
Click to expand...
Click to collapse
It doesn't work. How can I unlock boot loader while usb debugging is off. Is there any method?

fatihlale said:
It doesn't work. How can I unlock boot loader while usb debugging is off. Is there any method?
Click to expand...
Click to collapse
you don't need usb debugging. Usb debugging is only needed to have adb connectivity when the phone is booted in android.
for gpe device you should be able to unlock it using fastboot from the bootloader.
Code:
fastboot oem unlock
If this method doesnt work you'll need to use HTCdev.com to unlock it.
Don't forget that unlocking your bootloader will wipe everything on your phone.

alray said:
you don't need usb debugging. Usb debugging is only needed to have adb connectivity when the phone is booted in android.
for gpe device you should be able to unlock it using fastboot from the bootloader.
Code:
fastboot oem unlock
If this method doesnt work you'll need to use HTCdev.com to unlock it.
Don't forget that unlocking your bootloader will wipe everything on your phone.
Click to expand...
Click to collapse
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584

fatihlale said:
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
Click to expand...
Click to collapse
It have nothing to do with usb debugging! Like I said above, the only purpose of usb debugging is to enable adb connectivity when the phone is booted in android.
Even if usb debugging is turned off, you still have the ability to use fastboot commands from the bootloader (like you have tried) and to use adb commands from a custom recovery (which you don't have access to because of your locked bootloader)
With that said, I'm sorry to tell you that what you are seeing after doing "fastboot oem unlock" (PG_ERROR) is typical of the infamous GPE bootloader bug. This bug make impossible to unlock your bootloader from using oem unlock or by using HTCdev.com method. So your phone is bricked sorry.
you are not alone, see this thread: http://forum.xda-developers.com/showthread.php?t=2547894

fatihlale said:
It doesn't work bro because off usb debugging is disable. I tried many times but It doesn't work look at the attachmentView attachment 3059584
Click to expand...
Click to collapse
so my device is going to rubbish am I right?

fatihlale said:
so my device is going to rubbish am I right?
Click to expand...
Click to collapse
Maybe keep it in a drawer and hope that HTC will release a 5.11.1700.3 or higher version official RUU so you'll be able to flash it with s-on and a locked bootloader.
or maybe you could ask the guys at fonefunshop if they are able to s-off it using their method which doesnt require to boot in the rom.

Command not allowed error

After I Upload b320 Stock rom to My Phone which I Upload it rom with bootloder key before, it took root.
When I tried to upload twrp recovery again, there was a mistake command not allowed. ı tried it two different pc and two different programme

I have same Problem.The Bootloader shows unlocked,but it's locked.Unlock again and works for me.

letschky said:
I have same Problem.The Bootloader shows unlocked,but it's locked.Unlock again and works for me.
Click to expand...
Click to collapse
while I am trying to relock bootlader method, I met a new mistake failed remote root type is risk

Is FRP unlocked?

no frp is locked

ok unlock it,this is the Problem
Go into Settings-Phoneinfo and press 7 times on Build Number.(This enable Developers Option)
Go back to Developer Options and enable OEM Unlock.
You can flash Twrp,does not work unlock your Bootloader again

letschky said:
ok unlock it,this is the Problem
Go into Settings-Phoneinfo and press 7 times on Build Number.(This enable Developers Option)
Go back to Developer Options and enable OEM Unlock.
You can flash Twrp,does not work unlock your Bootloader again
Click to expand...
Click to collapse
Thank you. İ fixed problem ?

I cannot turn on the enable OEM Unlock, the option is grey disabled. What can I do? Im in nougat, should I try rollback to 6.0?

I have same problem... Is it possible that only solution is rollback??

6marcus9 said:
I have same problem... Is it possible that only solution is rollback??
Click to expand...
Click to collapse
I rollback and fix it. It's looks like nougat or beta versions disable OEM unlock

6marcus9 said:
I have same problem... Is it possible that only solution is rollback??
Click to expand...
Click to collapse
I fix It. The solution is easy but in anyway you need wipe your device
The steps are below
1 switch your phone in bootloader mode
2 with fastboot enable OEM lock , after lock the phone will be wipe
3 wait boot and configuration
4 enable develop mode e now you can disable OEM protection (FRP)
5 now switch your phone in bootloader mode and with fastboot unlock OEM
6 after wipe your phone will be with bootloader unlock and Frp unlock
Good luck
Sent from my HUAWEI NXT-L29 using XDA-Developers Legacy app

What happens if I disable OEM-Unlock in developer settings?

I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?

Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
Turned it off once by accident but turned on again.. Nothing changed

I don't think anything changes unless u relock it via fastboot, which at that point as long as u can boot back into the OS, u can always unlock it again, relocking bootloader will format ur data and u will no long be rooted or have twrp installed

locking your bootloader with root etc installed can cause major problems so before doing that you should flash a stock firmware otherwise you will be locked out

Why would you want to do this? There is no benefit to it if you plan to stay rooted.

Need to find something to do. You bored

iElvis said:
Why would you want to do this? There is no benefit to it if you plan to stay rooted.
Click to expand...
Click to collapse
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.

Your cat will get knock up..........again!

Maik_ said:
I want to disable developer options, but if I do that OEM-Unlock automatically turns off and I don't want to reboot because I dont want that I lock myself out.
Click to expand...
Click to collapse
Just turning off Developer Options won't relock your bootloader. You can only do that manually in fastboot. But you'll also lose USB debugging, which means adb won't work anymore in case something goes wrong. (But leaving USB debugging on all the time isn't the best idea anyway.)

Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .

omer123137 said:
Hello everyone
I think I did that mistake
I have twrp installed on my phone Samsung SM-G532F . my phone was working just fine but I have locked the oem for no reason .
now when I turn off the device and tried to turn it on it shows { Custom binary blocked by FRP. (boot. img) }
and when I open recovery mode it shows { Custom binary blocked by FRP. (recovery. img) }
the download mode is working and shows that the FRP lock is on .
I tried to flash the stock recovery with odin but since the FRP is locked it failed .
the adb is not working because the device cannot boot , even the battery symbol when I plug my phone with a charger is not displayed and shows the error { Custom binary blocked by FRP. (boot. img) }
any ideas will help a lot .
Click to expand...
Click to collapse
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.

If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.

iElvis said:
You cannot boot with a custom recovery and a locked bootloader. As to how to fix this, you need to ask in the Samsung forums. This is for OnePlus 6.
Click to expand...
Click to collapse
I was finally able to solve this issue with flashing the official firmware with odin . now I will never touch the oem unlock button ever again :laugh: . but thank you for your reply .
---------- Post added at 07:27 PM ---------- Previous post was at 07:22 PM ----------
Toni Moon said:
If you have a oneplus look in the forum for msmdownloadtool and follow the steps, you can revive your phone.
If your phone its a samsung, search in samsung forums for a tool to unbrick your phone.
Click to expand...
Click to collapse
I downloaded and flashed the official firmware with odin and it worked . thanks for the reply

I did this once on my OnePlus X, disabled oem unlocking in developer options. phone and recovery worked fine. I did a backup. Flashed a new rom to test it. The rom had AOSP recovery in the zip, overwriting twrp (opx has separate recovery partition). I flashed gapps affter the rom and the setup wizard was crashing so I could not boot in the home screen. Tried TWRP, its gone. Tried to boot to twrp via fastboot, oem locked. Had to do hard brick reset. Backup and data, gone.
TLDR, you should leave it on, unless you are on stock firmware.

After flash a rom you must flash twrp recovery again, restart in recovery and flash gapps and magisk

First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device

Sinankhan.official said:
First of all you have to flash combination file associated with your device model through ap slot of odin.
Then your phone will turn on and you can access settings through which you can turn on oem unlock.
Then you can install your desired rom into your device
Click to expand...
Click to collapse
This isn't a Samsung device.

Maik_ said:
I already unlocked the bootloader, happens anything if I turn off oem unlock in developer settings or will the bootloader relock?
Click to expand...
Click to collapse
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot

I restored the stock firmware using Odin, but now I see that the bootloader is still unlocked.
When try to lock it again the system says: "If OEM unlock is turned off, your phone will be reset to factory default settings after restart. This will erase all of your data... " etc.
My question is: will the firmware be still in place? I don't mind everything being wiped, because most of it will be restored anyway when I login to Google and Samsung again.

SamarSS123 said:
I also accidentally turned off oem in rooted phone , Does my bootloader locked or I can safely reboot
Click to expand...
Click to collapse
No

galaxy J327vpp

Can Oden root my phone once FRP has been turned off

82abnman said:
Can Oden root my phone once FRP has been turned off
Click to expand...
Click to collapse
Frp is not the problem if you see the option oem unlock in developer options then yes you can root your phone by flashing twrp recovery with odin then installing supersu/magisk from there

KG: Prenormal and cannot boot to OS

I have my SM-G611F's KG state set to "Prenormal". OEM unlocking is enabled. But how can I bypass or get rid of KG Prenormal without being able to boot to the OS? Because I want to flash TWRP to make progress but KG stops me. I can boot to recovery, but trying to boot to OS, it reboots automatically.

Is your bootloader unlocked? Like you went and got to the bootloader r unlock screen and it made you factory reset? If not, do that. If so, you have to setup your device (only add wifi, do not do anything else), and then go to settings, and enable dev options. The checked that Orem unlocking si enable. Only then can you flash firmware.

Arealhooman said:
Is your bootloader unlocked? Like you went and got to the bootloader r unlock screen and it made you factory reset? If not, do that. If so, you have to setup your device (only add wifi, do not do anything else), and then go to settings, and enable dev options. The checked that Orem unlocking si enable. Only then can you flash firmware.
Click to expand...
Click to collapse
I said I cannot boot to the OS. And yes, I do indeed have OEM unlocking enabled but my KG is set to Prenormal and that prevents me from flashing anything that's not official.

triangl said:
I said I cannot boot to the OS. And yes, I do indeed have OEM unlocking enabled but my KG is set to Prenormal and that prevents me from flashing anything that's not official.
Click to expand...
Click to collapse
Yea, flash stock AND UNLCOK BOOTLOADER. Enabling Oem unlock is not enoug. The setting simply lets you unlock the bootloader. Afterwards, after the reset, connect your device to wifi and enable dev settings to make sure Oem in on and grayed out.

Arealhooman said:
Yea, flash stock AND UNLCOK BOOTLOADER. Enabling Oem unlock is not enoug. The setting simply lets you unlock the bootloader. Afterwards, after the reset, connect your device to wifi and enable dev settings to make sure Oem in on and grayed out.
Click to expand...
Click to collapse
I'm once again repeating myself, I cannot boot to the OS.

flash stock

Arealhooman said:
flash stock
Click to expand...
Click to collapse
I wouldn't be here if it was just simple enough as flashing stock. I did it many times, with different countries with U3. Doesn't work.

triangl said:
I wouldn't be here if it was just simple enough as flashing stock. I did it many times, with different countries with U3. Doesn't work.
Click to expand...
Click to collapse
With csc?

Arealhooman said:
With csc?
Click to expand...
Click to collapse
Yes, with various csces. I tried NAND Erase, Re-partition and various other things but it won't boot to the OS no matter what I do. I was able to boot when I had root, the problem is I don't have TWRP so I cannot root.

triangl said:
Yes, with various csces. I tried NAND Erase, Re-partition and various other things but it won't boot to the OS no matter what I do. I was able to boot when I had root, the problem is I don't have TWRP so I cannot root.
Click to expand...
Click to collapse
did you correctly reparation after nand erase?

I think you screwed up so bad you can’t recover. With a locked bl, ur prob screwed.

At this point, you prob need edl and firehose to recover

At this point it is as bad as a hard brick from what I can tell

Arealhooman said:
At this point, you prob need edl and firehose to recover
Click to expand...
Click to collapse
What are these?

Arealhooman said:
At this point it is as bad as a hard brick from what I can tell
Click to expand...
Click to collapse
I think you didn't notice my reply, so I will ask again. What is EDL or Firehose?

You are right, I did not notice. EDL has little documentation, but ti is pretty much a mode where you can fully reflash your device, including bootloader, into a factory state. It ignores your bootloader being locked, because it operates from a higher level. You can flash a stock firehose file through edl (that’s how you operate it(. Samsung usually does not give away their firehose files, so you can do your best unless you want to send it in.