Related
I recently successfully restored my Axon 7 (A2017U) to B20 and tried to OEM lock it again. After running "fastboot oem lock", the phone rebooted, but came up with something that said "To start Android, enter your password." I didn't have a password before, so I tried something I found online called default_password to see if it would unlock (which it didn't) & then other passwords to get the phone to wipe itself and essentially perform a factory reset. However, now it is stuck in Safe Mode and says "Decryption unsuccessful: The password you entered is correct but unfortunately your data is corrupt." When I try to wipe the phone, it says it is factory resetting, but then it restarts and goes to a blank screen. (Which I suspect is because TWRP is still installed as a recovery, not stock). In addition, power+volume up no longer works since the phone is oem locked, but power+volume down takes the phone into Factory Test Mode. My computer still recognizes the phone when it shows up in Safe Mode, but I cannot see it in ADB.
Where can I go from here to factory reset the phone? Is it possible to send this to ZTE to fix since it is OEM locked at the moment?
I followed razorblader's advice and successfully got the phone into EDL mode and ran tenfar's tool. However, that made it worse and now the phone just shows ZTE for the second & the screen goes blank.
EDIT: Nevermind, I was running that program without recovery.img/boot.img in the same directory, D'OH! Luckily, I still had comms with the phone after that mistake & I re-ran the program successfully. I can now get into TWRP recovery. However, booting into system still shows the corrupt data message. I'm going to try a factory reset from TWRP and see if that fixes the issue.
OK good news, got my Axon 7 working again, stock + locked & am currently posting this from it. One reason I wanted to relock it however was to get OTAs and right now B27 is showing up. Now before I almost brick my axon again, do I need to flash stock B20 recovery before I'm able to install this update? Also, I'd like to get to B29 eventually, but I'm guessing I need to update to B27 first. (correct me if I'm wrong though)
So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
UnZoner said:
So, put my son's SM-T580 on the charger last night, it was fine (he's been using it for months), woke up this morning to it boot looping. It will not get past the initial boot screen and has that annoying red text 'Custom Binary Blocked by FRP Lock' in the upper left corner. It will not boot recovery. I can only boot to the bootloader. Of course, I can't flash anything using ODIN because of the FRP lock. I'm thinking the only options I have is to try flash a stock ROM / Recovery back onto it and start over but I was wondering if anyone else has ever seen or heard of anything like this before I do that. Thanks.
Click to expand...
Click to collapse
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
lewmur said:
The only thing that I can think of is that someone, somehow disabled the OEM Enable setting in /Developer options. This is what trigger the FRP lock.
You will need to hold Vol-, Home and Power buttons to boot to download mode and use Odin to flash a stock ROM. Then you will need your the Google Login and Password that is registered to the tablet. If you don't know those, you're in a heap of trouble.
As soon as you get stock up and running, the first thing to do is enable the developer options and make sure that OEM is enabled. After that you can flash TWRP and custom ROMS.
If you don't know the Google info, the tablet CAN be salvaged, but it is a complicated process.
Click to expand...
Click to collapse
This is what I was afraid of. It is my sons tablet so I have all his Google info. I would not be surprised if he somehow reset the developer options. He'll lose some of his game progress but that's nothing compared to losing the whole tablet. Thanks for the reply. Off to download a stock rom and start over.
[How-to] Unlock bootloader on Pixel Google Store with "OEM unlock" Disabled -
I experienced the mishap of locking back the bootloader after flashing the device with my signed custom build. The result was that i was no long able to activate the "OEM unlock" in the "Developer options".
The fact is that If you Signe your build you will not be able to rollback to stock build with ADB update / ADB Sideload / SDRAM zip ... because your Bootloader check the signature.
The only way to do it is to flash the OTA or google Factory Build by Fastboot and for that you need your Bootloader to be unlocked.
Here's in red what i did wrong :
- Activate the "OEM Unlock" in Developer options.
- Unlocked the bootloader with Fastboot
- Flash my signed ROM
- At this time the "OEM Unlock" will turn Gray and we can no more use it to activate or desactivate.
- To test some security functions, i did re-lock my bootloader with fastboot. (Forgot that the OEM unlock is disabled).
Here's what i tryed in order to solve :
I did the steps discribed in [How-to] Unlock bootloader on Verizon Pixel/XL by burduli.
That did not solve my issue but it gives me an idea where to look for. Big Thanks to @burduli (Cedit to @Qu3ntin0 and @LeoTheRomRasta)
Here's the steps i did to solve :
No need to be on internet or so on
I did notice on the Device that there was a Guest User account but i had no way to remove it.
To do so i managed to :
1 - Wipe (factory reset) : Setting / System / Advanced / Reset options / Erase all data (Factory reset) => (Find the entry according to your Built / Android version)
2- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volum down button until the device finish booting.
3- Go to setting / System / Advanced / Multiple users
4- tap on Guest, then on "Menu" the [...] on top right of the window
5- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
6- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
7- Your Device will reboot and at this time hold pressed the volum down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
8- Enable Developer mode (tap 7 times on Build number under "About phone")
9 - Goto Developer options and you are done (The OEM unlock option is back and you can enable or disable it)
You can now reboot your device in normal mode .
In Booltloader mode you can use the "Fastboot flash unlock" or Fastboot OEM unlok command to unlock the bootloader
Will this work on Verizon Android 10 ? Thanx
BelligerentGnome said:
Worked for me.
Click to expand...
Click to collapse
Really ? It worked for u on a Verizon locked bootloader ???
Do you think will work on 2xl verizon?
I just tried it out. Android 10, October update. It didn't work. There's nothing we can do at this point, I'm afraid.
BelligerentGnome said:
It did. I just got one off of Swappa, and the OEM Unlock option was greyed out. This fixed it. I'm running Lineage OS 16 now.
Click to expand...
Click to collapse
You didn't happen to take any screens during the process did you? No offense meant, but it's kind of strange that other than the OP, there's no one else confirming their success. Was it Android 10 with the October update?
Confirmed for myself, does not work. I have only taken the Android 10 update, no other updates since. OEM unlocking still disabled.
Oh verizon, still no one else to hummer this? I will donate who can sure to unlock oem method, hahaha
Going into safe mode there's no way for me to delete the guest user...was hoping it'd work for me - Pixel3/Verizon/Android 10
after doing this (unsuccessfully) my sim card is not being recognized?
This happen to anyone else?
jb
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Verizon Pixel 1 - unable to get it working still. as a note, when holding down the power down button during the 'erasing data' phase, the phone goes into Android Recovery Mode (shows me the BL, Baseband, Product/Variant, SN, CPO, UFS, DRAM, Boot-slot, Console (DISABLED), Secure Boot (PRODUCTION), Device is (LOCKED)). From here I can enter recovery mode, see barcodes, Power off, or Start.
I tried the following steps:
. Remove Google account and any kind of screen lock (fingerprint, PIN, pattern, etc.) from your device.
. Eject sim card from your device.
. Reset your device. In setup wizard, skip everything, don't connect to WiFi, don't add fingerprint or any kind of screen lock.
- Boot in Safe mode (Turn off the device / Hold the power on button till Google screen then release and hold pressed the volume down button until the device finish booting.
. Go to Developer Options and enable USB debugging.
. Connect your phone to PC.
. Open CMD in adb directory and type
Code:
adb shell pm uninstall --user 0 com.android.phone
- Go to setting / System / Advanced / Multiple users
- tap on Guest, then on "Menu" the [...] on top right of the window
- "Delete Guest User from this device" and confirm (It will seem like nothing done but don't stress it's ok)
- Ones again Setting / System / Advanced / Reset options / Erase all data (Factory reset)
- Your Device will reboot and at this time hold pressed the volume down button until the device finish booting (this time it will take longer to finish booting cause android is seting-up all stufs) . (that will boot the device in safe mode).
- Enable Developer mode (tap 7 times on Build number under "About phone")
- At this step i went to OEM Unlock and saw it was still disabled.
Is this something we can look at solving through the legal system?
I also was unable to get this to work
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
jedpublic said:
tldr = Somehow, this worked for me on my Really Blue Pixel running QP1A.191005.007.A3. Initially, my OEM locking was greyed out.
I wanted to downgrade since my Wi-Fi will not connect after updating to Android 10. However, without an unlocked device, I could not downgrade. So, after much searching and trial/error, I tried this on a whim.
While I was not able to find a way to delete the Guest account (as stated in step 4), I was able to "remove" the Guest account, after selecting it and logging into it - at which point, I went back to the Multiple Users menu, and the "remove" option was there; it logged me back in as Owner. Then, after a very long reboot and cramped hands (step 7), I enabled developers mode but, alas, OEM locking is still greyed out. I opened Chrome and visited a few sites and went back in and OEM locking was selectable. Yippee!!
Next, I followed the instructions at https://developers.google.com/android/images and was able to install a previous image. Unfortunately, for some reason, my Wi-Fi still will not stay connected and becomes "Disabled."
Click to expand...
Click to collapse
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
tronoftroy said:
after you removed the guest account, did you factory reset again?
also, when i hold Volume down during factory reset it will just go into fastboot mode. did you experience the same thing?
Click to expand...
Click to collapse
Yes I did do the 2nd factory reset, which may be significant based on other people's reports...
If I recall correctly, the second time I factory reset, I held Volume Down from the moment I confirmed the restart. Honestly, I was trying so many different things though, so everything kind of blurred together.
One thing to point out is that my Really Blue Pixel was obtained from Google directly, not Verizon.
I've just bought myself a brand new Pixel 1 XL - 128GB Factory Unlocked. Sadly I wasn't aware of all these issues with OEM unlocking via the Developer Menu. Not knowing the drawbacks, I casually breezed through all the upgrades and reached 10.0 (QP1A.191005.007.A3) state. It was then I realised I cocked up...:crying: because no matter what combination of instructions I try in this (and other) threads, I simply cannot get the greyed out menu to budge! I have tried at least a dozen factory resets, countless adb removals, with/without WiFi, with/without SIM, with/without Google sign in, with/without Safe Mode, with/without Guest User Profile delete and so on.... all to no avail:crying:
I am lost at the moment... I'm sure there's other in the same boat as me. I really do hope there is a solution for all of us out there.. any one have any ideas?
For those in previous versions, I can only think of using zero-day exploit with an app such as Qu1ckR00t. But we would need a dev or something to tailor such app for our Pixel. Any other idea is welcome!
I gave up and sold my Pixel 1 XL - thinking of getting a used Pixel 2 instead. I just need this as my backup phone and for travelling. My primary is the Pixel 4 XL.
dfx12345 said:
Got a Pixel here with 9.0.0 (PPR2.181005.003.A1, Nov 2018) and this doesn't seem to work. Am I doing something wrong or did they kill it with the November update? Anything I can do?
Edit: Wait no, this is November 2018. Why isn't this working then?
Update2: Got it working. I used a combination of the steps here, followed by the steps listed in the guide linked in the OP (the `pm uninstall --user 0 com.android.phone`). Then I had to wait a few minutes for the OEM unlock to finally become available. Thank you.
Click to expand...
Click to collapse
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Taswim said:
Can you explain the steps you used for the OEM unlock? I have the same Build and update as your device. Please help me, i tried every method possible and almost give up. I have verizon pixel 9.0.0 PPR2.181005.003.A1, Nov 2018
Click to expand...
Click to collapse
My understanding is that you're out of luck with a Verizon Pixel. Mine was a non-Verizon Pixel.
i factory reset my device and now it says "official released binaries only " in red and it wont boot at all. idk what to do.. i dont know how to force it to go into download mode i tried plugging it into the computer but it doesn't help. it just keeps restarting over and over again i only see the Samsung S10+ with the Yellow Triangle logo with that message at the top then it reboots. " anyone got any ideas how i can fix this there isn't a samsung store near me. if i plug-in the device into the computer it just keeps rebooting to the samsung s10 screen with the yellow triangle saying at the top in red "Only Official released binaries are allowed to be flashed" my issue is that i can't get the phone into download mode i tried holding down Bixby volume down power then plugin the usb cable. and even bixby volume up and power . it just keeps rebooting itself (sm-G975F)
have a quick look at this thread..... you should be able to boot into download mode, make sure u have the drivers for your phone installed on your pc. you will need to flash another firmware via odin (id recommend stock firmware to get you back on track )
https://forum.xda-developers.com/galaxy-note-9/help/official-released-binaries-allowed-to-t3893592
100000x likes.. you saved me bro.
volume down + bixby that was the magic key's to get back into download mode. i am flashing the firmware now. thank you again. i couldn't figure it out and i was going nuts .
? glad to help
meddylad said:
? glad to help
Click to expand...
Click to collapse
i lost oem unlock so i changed the date to may 1st and it showed up. but now how do i get it back to grayed out.. because when it needs internet it changes the date back to. todays date. got any ideas.
edit: when i reset up the phone after i checked oem unlock i put the the date for 10 days ago. so that the unlock stayed. anyways thanks again @meddylad
I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight
meddylad said:
I think you have no choice but to wait the 7 days (think its a knox issue)... you could turn off auto time sync but that messes up other apps.
maybe someone else might have a workaround so hold tight
Click to expand...
Click to collapse
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?
rp4k said:
I turned off auto time . And got OEM unlock then unlocked it and re installed magisk then for the final setup I put the auto time.
Question are you on asd6 or asd4 firmware?
Click to expand...
Click to collapse
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.
Visera said:
Personally I don't known an S10. However, from what I know, Samsung incorporated a fastboot-like feature. In Download Mode, when you press Up, it asks you to factory reset to unlock your bootloader. You might need to relock it (if you come from pure stock), wait the 7 days, and unlock it again.
"Only official binaries can be flashed" is due to RMM state changing to Prenormal. It happens on a factory reset. To prevent it, you need to patch it through TWRP. If you can on the S10 I don't know, but patching RMM will prevent this warning. It's basically meaning OEM Unlock is back on.
Click to expand...
Click to collapse
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.
rp4k said:
There isn't a patch for it yet on s10 because it's not possible because of how the partitions are setup. I already fixed my device already and like I stated in the lost before
You can bypass the 7 day wait.
First boot of new firmware have no internet or sim and set the date to 7 or 10 days before. Then once in the os do the developer mode unlock and click OEM unlock. Then go into download to unlock it fully then When the phone reboots to erase all data set it again to the same date . But this time once your In the OS you enable wifi but disable automatically time and date and set it to the same date as before. And OEM unlock will be grayed out. Then reboot to Download mode and flash the patched .tar from magisk. Once that finishes reboot to stock recovery do a factory wipe. Then reboot with volume+ Bixby, power to get into magisk image of os. And you will have the unlocked bootloader . But the OEM won't be grayed but it will be active.
Click to expand...
Click to collapse
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.
Visera said:
Yeah, the same trick used to work on the older phones with the OEM unlock bug. No longer works, however RMM patching fixes it. I'm sure it'll be the same as S9. S10 has the same partitions, same OneUI, simular pie vendor, all that magic. Won't take long hopefully, S9/S10 are both Treble enabled and A - only.
edit: Read S10 isn't as simular. I'm tired.
Click to expand...
Click to collapse
Well this trick works fine on the s10.
Hi, something like a year ago I rooted my phone, something like half an year ago I installed LineageOS 14.1 and succesfully rooted it with Magisk.
I used it without any problems since today: I used it this mroning, then I shut it down so that it could charge (the battery is getting old, it doesn't charge enough if it's running)
Then I turned it on, but it didn't turn on because the FRP lock suddenly turned on. ...that means, as the splash screen prompted up, the "custom binary blocked by FRP lock" message
showed up. I couldn't enter TWRP recovery, but I could go in download mode, so I decided to flash a stock rom grabbed from the internet (I used Odin).
The stock rom is not working, it gets reboots as a message saying "installing applications...." shows up.
I don't care about the system itself, I only want to get my data stuck in it, so wiping data and cache is not an option.
EDIT: I tried using 2 different stock roms, and both seem to reboot after a fixed amount of time, like 3-4 seconds. I can enter the stock recovery and download mode.
I have same problem. Installed from stock rom to viperos. Cann't boot to back os, shows only frp lock..and then shut down. Please, could some one tell me how to fix it? I don't want to back stock rom. Thank you.
vgran said:
I have same problem. Installed from stock rom to viperos. Cann't boot to back os, shows only frp lock..and then shut down. Please, could some one tell me how to fix it? I don't want to back stock rom. Thank you.
Click to expand...
Click to collapse
Hi, I gave up trying to find a solution so I simply did a factory reset (by loosing all my data).
But if you flash the stock rom, you shouldn't lose data, but you can get access to the stock recovery mode. From there, you can use the adb shell to do "things".
I personally wanted to use the shell to retrieve data from my phone, but by flashing the stock rom the "usb debugging" option got disabled, so I couldn't do anything with that adb shell.
I advise you to try finding a way to enable usb debugging using the stock adb shell only (the shell wich is in "sideload" mode), I didn't find one but I didn't search a lot on that because I've already spent hours on trying to find a solution for the frp lock.
By searching I mean something like that: "enable oem unlock/usb debugging from adb in sideload mode"
(of course if you can't access the recovery mode and you don't have a backup)