Hey Guys! I'm pretty new to all of this and im looking for an answer to a problem that occured to my s8+ 2 days ago.
I've never had any problems with my phone. I've flashed nearly everything and have always been able to fix it if there has been any problems but now i've got a questionmark on my head.. My phone i bought in denmark and i live in sweden and 2 days ago i went to denmark with my friends. After i came back to sweden i flashed the latest update of the custom rom i am using which is GoogleWiz and after that i enabled developer options and it turns out i cant turn on oem unlock anymore? This has never been a problem before, its always been on but now its greyed out and cant be turned on. Luckily i have TWRP installed and can still flash things but there seems to be a problem cause when i turn on developer option my phones settings change and the phone turns really slow... I tried reflashing rom without turning on developer options afterwards and then the phone works fine but i want to be able to turn of developer options on for options like usb debugging, oem and so on..
I haven't checked but i guess bootloader is locked cause i cant turn on Oem unlock?
Would appreciate help with this if anyone got a solution?
The phone is rooted with magisk and has TWRP 3.2.1.0 installed.
Related
Hi Guys,
I was cheated into buying an HTC demo phone and i cant soft reset it, i can only hard reset but even after that as soon as the reset is done i get the message that demo as started again. I cant uninstall it I tried rooting the device but the only options I see are that I have to enable developer options but they are all grayed out and i cant enable them at all. I have tried updating a standard rom 1.30.401.1 from http://forum.xda-developers.com/htc-10/how-to/stock-stock-collection-recovery-ruu-ota-t3359297
but it works and says its updated from sd card however when the phone is reconfigured it says again its a demo phone. I have been trying since three days now. I have done the S-off and Unlocked by the sunshine app after paying them. the details in download mode are
CID-HTC__002
Mid-2pS620000
ColorID-BLK00
KJ-1.0.0.0000
[email protected]
OpenDSP-v18.2.8996.00524_0321
OS-1.30.401.1
Apr 23 2016
Build Number is 1.30.401.1.8.0_g CL738269 release-keys
I AM NOT AN EXPERT BUT I BELIEVE THAT SMART PEOPLE FROM HERE CAN HELP ME OUT THANKS A TON
Solved
After factory reset and initial boot you have a minute before demo mode kicks in. Head into developer options, check the oem unlock option and USB debugging. Then you are good to go, unlock bootloader, root and run sunshine to gain s-off, change cid and flash ruu to be stock
Hi there,
It seems that you already found the best place on XDA to post your question.
Please continue your journey there.
This section is more to help new users with their problem .
Good luck!
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
cyborgium said:
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
Click to expand...
Click to collapse
You should be fine. If you go into download mode and see RMM State Prenormal then you've been locked out from flashing anything.
xxxrichievxxx said:
You should be fine. If you go into download mode and see RMM State Prenormal then you've been locked out from flashing anything.
Click to expand...
Click to collapse
Yeah I didn't see anything like that in download mode so I just went F it and I managed to flash TWRP and magisk. Just to be sure though, I did flash the RMM state fix.
I still don't quite get why my OEM was unlocked when all the other people's got theirs locked. Any ideas?
cyborgium said:
Hello,
I've read quite a bit about rooting on the new Oreo firmware and having to wait a week before you can enable the OEM unlock, meaning you wont be able to flash anything yet.
However, when I went into developer options RIGHT after I flashed the CRAP build, OEM unlock was already enabled (as shown in the screenshot). Would this indicate that I can go ahead and flash TWRP/magisk to root already?
Thanks in advance,
Cyborg.
Click to expand...
Click to collapse
what Oreo firmware did you put
After 212 Hours..... and nothing happened, OEM unlock don't appear in developer option :crying:
WalterSilverio said:
After 212 Hours..... and nothing happened, OEM unlock don't appear in developer option :crying:
Click to expand...
Click to collapse
It doesn't appear you are in developer options but, rather, About Phone, Status.
I know I'm not in the developer option, the screenshot is so you can see that it's already 7 days (168 hours) and even in the developer option it does not show me the oem unlock option
I show you
OG Pixel from Verizon, had it for years, battery has been really ****ty lately. So I had to send my phone in to get a new battery, and the cost was similar to go thru google store, so I did. Wiped the phone, restored to stock android, but left bootloader unlocked. Got the phone back today and version of android was downgraded and bootloader was locked.
How ****ed am I and what are my recourses? Tried google support, they're nearly useless.
If you never booted the device yet you can try "fastboot flashing unlock" and it will just re-unlock. Other than that I don't think you will ever see a unlock status on that phone. This is why I do my repairs myself.
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Before updating in any way... Search Verizon unlock Pixel and see if that process will unlock. If you allow update past a certain level stuck with no options then if Verizon locked.
Oh, would never allow an update. I'm not crazy. Tried the unlock method with uninstalling the phone app before you get internet access the day I got it, still no dice. Thanks tho.
I just did a credit card chargeback as they sent me back my device in an unusable condition and refused to compensate for it. We'll see how it shakes out in a few weeks probably. Bought a refurb Pixel 3 in the meantime and it was already unlocked, so all is well.
Thanks for the replies though.
-N
n8lee said:
Fastboot flashing unlock was unsuccessful, but I suspect that was because the phone was booted up for "troubleshooting" with Google "support."
I assume then there's no way to return it to the post-flash pre-boot state without some closely guarded hardware and software?
Click to expand...
Click to collapse
Can you tell me what security patch you are on? If you are somewhere around Android 9 patch (potentially Android 10 early patches) you can re-unlock. If you try ticking the OEM unlock option in Dev options or if i heard correctly the phone wont boot? If you know your exact version you can try flashing it through recovery, or trying "fastboot unlock" after ticking the oem unlock. Also remember those old workarounds of removing android.phone and such? Yeah try those. Good luck. We'll try and get you unlocked again.
I have an old Samsung J3 Eclipse (SM-J327V) that has no OEM Unlock in Developer Options. The phone is approximately 5 years old. I would like to unlock the bootloader on it. I'v tried the suggestions listed on the forum, but they are for new phones to bypass the 7 day waiting period and enable the OEM unlock. I tried them anyway, and they don't work on my J3.
Seems to me that I read that Samsung started hiding the OEM Unlock with Android version 8.0
I was thinking of loading some old version of the official firmware that was Android 7.0 or earlier (if I can find it). Then, hopefully there would be an OEM Unlock that would enable me to unlock the boot loader. Once unlocked, I could flash back to Android 8.1 (newest version for this old device). Would that work? Can you use Odin to downgrade the version of Android?
Comments welcome from all. Thanks!
I've tried following every youtube video and posting on the internet for how to get the hidden OEM unlock back into developer options. None of them work. I swear I have done the process of date resetting dozens of times and it still doesn't work.
Can anybody help? Please! I'd really like to unlock the bootloader. Is there any other way to do this?
delete
insert your sim card. worked for me
actually you only need to set time forward a week or more
Win_7 said:
actually you only need to set time forward a week or more
Click to expand...
Click to collapse
idk. for me i had to insert my simcard
ElitePrime said:
idk. for me i had to insert my simcard
Click to expand...
Click to collapse
i think theres many ways to do it
setting time forward is the easiest
Hi guys. So i bought a motorola g pure, xt2163-4 pvt1 with universal software. About 1 year ago from facebook. Phone looked new and it was "factory unlocked" However last night i had an android 12 update, wich i did, but now after the update, my network is locked. And the built in unlock tool at about phone-device unlock, wont seem to work, i get (SERVER COMMUNICATION ERROR CODE=200 MSG=SERVER_NO_CONTENT).
Isaw a couple of fixes on google, however they are for diferent divices and old, i was wondering if anyone here has a solution for this problem. I really apreciate the help. Thanks for reading.
I have the same issue but I don't have an unlocking app or was unlocked via server. Worked fine for months until after the Android 12 update.
ok so ima post a soultion that worked for me. My phone was unlocked via global unlocked, is just a gues, why? well last night i was about to unlock it with global unlock, downloaded the software, hoocked my phone, place my phone in fassboot, conected my pphone to the app, just to chekit it, i did not had any credits to use that unlock option, after reboot, phone was unlocked againg. so you might wanna give it a try. i even wipe the phone to see if the unlocked was ok after factory reset, and it was. so hope this works for someone else.