Have tmobile oneplus 8 and when trying to unlock with the cust-unlock command it gives me an error as shown in the image attached. made sure that the oem unlocking switch is enabled in the settings
This only happens when you didn't enable OEM unlocking, I know you said you did, but I'd double check. Boot the phone up, go to Settings -> About phone and tap "build number" a bunch of times til the message pops up.
Than go to Settings -> System -> Developer options and enable OEM Unlocking.
Then repeat the same steps in fastboot to unlock.
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
FoxyDrew said:
This only happens when you didn't enable OEM unlocking, I know you said you did, but I'd double check. Boot the phone up, go to Settings -> About phone and tap "build number" a bunch of times til the message pops up.
Than go to Settings -> System -> Developer options and enable OEM Unlocking.
Then repeat the same steps in fastboot to unlock.
Click to expand...
Click to collapse
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
Snekxs said:
Restarted my phone turned it off. Then restarted again and turned it on. And still no luck
Click to expand...
Click to collapse
Are you on stock T-Mo firmware, and have taken all OTA updates? I saw you said in another thread that after using MSM tool "the software update button is greyed out in the settings". If that's still the case...well it shouldn't be lol. I would MSM again back to OOS10, than immedietly try booting the phone up enabling OEM unlocking and try to unlock the bootloader again.
FoxyDrew said:
Are you on stock T-Mo firmware, and have taken all OTA updates? I saw you said in another thread that after using MSM tool "the software update button is greyed out in the settings". If that's still the case...well it shouldn't be lol. I would MSM again back to OOS10, than immedietly try booting the phone up enabling OEM unlocking and try to unlock the bootloader again.
Click to expand...
Click to collapse
Yeah. The button was greyed out but my phone still installed an update. Gonna try to use msm again and see
Curious if you found a solution to this one? Been fighting a similar situation, not the MSM tool just but the unwillingness to let me run the unlock bin token.
Related
Hey all,
So Ive tried to unlock my bootloader but its not working, ive followed the steps from this site to unlock it but its stuck on the unlock bootloader screen. I have two options to choose from yes or no I click yes but it doesnt work, yet I click no and it takes me back to choose from fastboot, recovery and normal. My phone is a Alcatel Pixi 4.
I have enabled developer mode enabled usb debugging. I also have confirmed the RSA fingerprint for the computer. Also I have enabled OEM unlock in dev settings. This is what my cmd prompt window loooks like. I will also take a photo of my alcatel frozen on bootloader screen.
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb devices
List of devices attached
5HQGTCEQCAVS7TTS device
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootloader
C:\Users\Dan\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlock
...
This is what my phone looks like that im stuck on.
https://s11.postimg.org/8e2cjxooj/IMG_20161129_172555.jpg
does anyone know why this is happening or know how to fix?
Also when I reboot my phone it takes me through the setup like I've reset my phone back to factory settings.
I've researched and found out the reason its stuck is because the bootloader is locked.
Got phone financed thru payjoy, it was cool until i realized how much control the app actually had, as stated in previous threads cannot change any options as a device administrator, and all developer options are grayed out except oem unlock, demo mode, Include bug report. Tried the master reset from recovery, states MDM doesnt allow... Come on already lol, HHHHHEEEEELLLLPPPPPP.
I wouldn't recommend it to be honest. It probably checks in with their servers regularly. They might come looking for it if it stops xD
Ok actually I have found a way to not only disable it but delete it, getting rid of it completely. I did it on my Note 5, message me
Illnoteit said:
Ok actually I have found a way to not only disable it but delete it, getting rid of it completely. I did it on my Note 5, message me
Click to expand...
Click to collapse
Why not just post the method here for everyone to use?
Pretty sure it involves setting screenlock security to reset the device after 10 wrong login attempts, then forcing those wrong attempts one after the other until the device factory resets itself
No actually it doesn't, it's been awhile see if I can refresh memory, after I figured it out, I thought wow how simple
If I remember correctly, in the security section of settings, there is a selection you can mark that forces a factory reset upon restart of device, therefore getting the pay joy as a device administrator. Then use a file manager, and find the com.app folder and delete the rest
This worked for me on a Samsung J7 Pro (G610M). Just enable OEM unlock at developer options!
1- Go to settings - lock screen and security and set a PIN lock, like 1234..
2- You will se a menu (Secure lock Settings), click on it and set "Auto factory reset". This opcion will factory reset your device after 15 wrong attempts to unlock the Screen.
3- Turn OFF the Screen and enter wrong the PIN code 15 times on your device, the the Phone automaticaly will reboot and it will perform a factory reset by it self. When it turns ON the "PLay Joy" will be erased.
Illnoteit said:
No actually it doesn't, it's been awhile see if I can refresh memory, after I figured it out, I thought wow how simple
Click to expand...
Click to collapse
Yes actually it does, see below
bullracing said:
This worked for me on a Samsung J7 Pro (G610M). Just enable OEM unlock at developer options!
1- Go to settings - lock screen and security and set a PIN lock, like 1234..
2- You will se a menu (Secure lock Settings), click on it and set "Auto factory reset". This opcion will factory reset your device after 15 wrong attempts to unlock the Screen.
3- Turn OFF the Screen and enter wrong the PIN code 15 times on your device, the the Phone automaticaly will reboot and it will perform a factory reset by it self. When it turns ON the "PLay Joy" will be erased.
Click to expand...
Click to collapse
*Detection* said:
Yes actually it does, see below
Click to expand...
Click to collapse
yes your right, i apologize, but i wanna say that on the Note 5, i didnt have to do the so many wrong attempts, I was able to do and auto factory reset upon system reboot.
at the last try it give error:
"device turned off. contact IT admininstrator"
So, any solution guys ?
Have a note 8 with payjoy, none of these methods posted here has worked.
Any help with this payjoy?
Have a note 8 as well. Jas anyone figured it out yet.
Whats your phone current firmware compilation?
Enviado desde mi SM-G930F mediante Tapatalk
why doesnt a factory firmware flash fix this? or even an unbranded flash like the U1? if the payjoy app has root/SU/admin rights and is able to make the phone a paperweight, then it should be removable with a factory flash with the regular CSC. @detection what am i missing about this? i mean after the FRP lock is bypassed that is
---------- Post added at 04:00 PM ---------- Previous post was at 04:00 PM ----------
why doesnt a factory firmware flash fix this? or even an unbranded flash like the U1? if the payjoy app has root/SU/admin rights and is able to make the phone a paperweight, then it should be removable with a factory flash with the regular CSC. @detection what am i missing about this? i mean after the FRP lock is bypassed that is
Hi there,
apparently I screwed something up while trying to prepare my 6X for Lineage
I did the OEM unlock but FRP Lock is still active and somehow this prevents me from doing anything else.
The combination of problems seems quite special, I've found (and tried) a lots of tipps for softbricked devices here but unfortunately none of them worked for me.
When restarting I get the warning that the device is not secure and will boot now - however it is stuck on "booting now" until the battery is drained.
It starts into Android when charged again but on every restart it will be stuck again.
When in "booting now" only Vol- key combination works when connected via USB to a PC. All other combinations (Vol+ , Power and Vol+/-) have no effect. Doesn't matter if connected to PC or not.
I can only get into fastboot, however I can't flash images (remote command not allowed), seems to be because of FRP lock.
The device is recognized (fastboot devices) and HiSuite sees it too. Drivers are OK IMHO.
Simply locking it again is not possible, the fastboot lock/unlock options don't work and when booted OEM unlock is greyed out in the options.
dload method is not available, because I can't get into erecovery since the key combination doesn't work.
I also tried factory reset, but:
doing it in the options doesn't work - it reboots and is then stuck in booting. After charging it everything is still there, so no reset at all.
doing it with *#*# 2846579#*#* doesn't work - says can't do it because I have a google account. Removed the device from my account, message remains.
erecovery is not available, can't get in the menue
Any help is greatly appreciated, I would be very happy to just restore it to default settings.
Cheers
Did you removed your screen lock password before unlocking bootloader?
yes, i did. At the moment I don't have a screen lock pw set. Should I set one?
Maybe you need to use dc unlocker
hm, not sure. I got the unlock code from Huwai and it worked. I read up on dc unlocker, how do you think it could help?
G4711 said:
hm, not sure. I got the unlock code from Huwai and it worked. I read up on dc unlocker, how do you think it could help?
Click to expand...
Click to collapse
Look into DC unlocked Phoenix. It can write to the phone in fastboot mode if the bootloader and frp is locked. I used it and it worked... Cost 20 dollars not better than buying a new phone
Thanks, will try it in the next days and post my results.
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
Dinesh033 said:
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
Click to expand...
Click to collapse
You get 'remote: flashing is not allowed', because you have 'Oem unlock allowed' toggle unchecked in Settings/Developer, and since you can't boot your device to allow unlock, your only option is flashing with MSM tool.
But msm also I have tried, it's getting completed but device hangs again in black screen in logo mode, I have tried 3 different msm tools too
Dinesh033 said:
But msm also I have tried, it's getting completed but device hangs again in black screen in logo mode, I have tried 3 different msm tools too
Click to expand...
Click to collapse
You can only successfully restore your phone with an EDL mode (where you turn your phone off, press and hold volume up and connect it to a computer with already started MSM tool). If the process completes, the phone should start. As a matter of fact, it should restart while the MSM tool is still working. Perhaps, it doesn't complete fully, because of a missing WIndows driver.
What did you do that has caused the problem?
optimumpro said:
You can only successfully restore your phone with an EDL mode (where you turn your phone off, press and hold volume up and connect it to a computer with already started MSM tool). If the process completes, the phone should start. As a matter of fact, it should restart while the MSM tool is still working. Perhaps, it doesn't complete fully, because of a missing WIndows driver.
What did you do that has caused the problem?
Click to expand...
Click to collapse
It was sudden by itself, it was on stock os and setting never even tried root or unlocking anything extra, I think hardware is gone bad may be storage as me and 2 more technician have used all methods but failed, now they also said hardware change required some 3500 bucks cost, I have now purchased Realme GT 5g ... Now using this from yesterday it's amazing
Noob here. I made an account just for this, but my phone is just refusing to give me that OEM unlock option.
I heard somewhere that the reason is that the KG state is prenormal, and to get it out you need to wait 7 days connected to the Internet and with a SIM card inserted.
And I don't have any SIM card, can't get one as well. I probably could if I didn't have to activate it. (which is also a question for me)
So is there any way to just bypass this SIM requirement? I would also want a 7-day bypass so I don't have to wait, but that's fine.
And this phone also can't get in download mode, like another thread on here. Just "Entering fastboot mode" red on black.
So, Instructions on fix? I know I just wrote an essay for this, and I WOULD show you a photo, but that error....
Update: KG STATUS is now COMPLETED in download mode. Yet still the option is missing....
Randomusername0345 said:
my phone is just refusing to give me that OEM unlock option.
Click to expand...
Click to collapse
If you figure out how to get the A32-5G (mine is SM326U) unlock option to show up in the Developer options, please let me know as I can't get my OEM unlock option to show up (grayed out or not).
Randomusername0345 said:
And this phone also can't get in download mode, like another thread on here. Just "Entering fastboot mode" red on black.
Click to expand...
Click to collapse
Recently I wrote up how I got mine into Download Mode, among others.
How to un-freeze an unresponsive Samsung Galaxy A32 5G with reboot, reset, factory reset, odin mode, download mode, android recovery mode & debug mode