Trying to root my phone but the OEM Unlock option does not show up in the developer options..I've searched around and couldn't find anything.
johnronin said:
Trying to root my phone but the OEM Unlock option does not show up in the developer options..I've searched around and couldn't find anything.
Click to expand...
Click to collapse
Who's your carrier?
T-Mobile has it
Verizon
johnronin said:
Trying to root my phone but the OEM Unlock option does not show up in the developer options..I've searched around and couldn't find anything.
Click to expand...
Click to collapse
I know it was there on 12A. Also if you are on VS995 Verizon, why do you need OEM Unlock. I don't remember seeing anywhere in the dirtysanta instructions that you need to do OEM unlock.
I have checked on both firmware available for the vs995..neither has it as an option.
The instructions don't say to check oem unlock ..but they also don't say to make sure the phone is in debug mode either. ...and every dirtysanta tutorial I looked up had oem unlock and debug as prerequisites except for the xda tut...
...I tried rooting and got all the way to step 3 but twrp would not let me format the data ...I'll try one more time before heading to sleep.
We don't have OEM UNLOCK on Verizon V20. Did you finish the dirtysanta successfully?
Sent from my VS995 using XDA-Developers Legacy app
johnronin said:
I have checked on both firmware available for the vs995..neither has it as an option.
The instructions don't say to check oem unlock ..but they also don't say to make sure the phone is in debug mode either. ...and every dirtysanta tutorial I looked up had oem unlock and debug as prerequisites except for the xda tut...
...I tried rooting and got all the way to step 3 but twrp would not let me format the data ...I'll try one more time before heading to sleep.
Click to expand...
Click to collapse
my suggestion would be to ask for help in the dirtysanta thread, you will get more help there
That's a good suggestion but it wouldn't let me post in that forum... I should have enough posts now though...
I was able to go through all of the steps and get twrp and booted up but root checker says no root access
Verizon removed that option from the menu. No Verizon V20 has it. That being said--it isn't needed if you follow the dirty santa instructions.
Related
hello all,
im currently working on a samsung S4 (GT-I9515) and i ran into a small problem.
i have rooted phones more then ones and i know the drill more or less.
but when i tried to sellect the unlock oem option in the dev options it was not there.
normally it is located under bluetooth HCI-snooplog and above Process stats but the oem unlock option seems to be non existing on this phone
can someone tell me whats wrong or is it not needed ? Because i did get a message when i tried to install something trough the default recovery menu that the system was still locked. (also it runs android 5.0.1(lolipop))
Best regards,
Darkdevel
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
true i also tried using twrp but when in boot twrp i cant swipe/select anything of the first screen do you have another idea what i can use ?
What are you trying to unlock with "unlock OEM option"?
audit13 said:
What are you trying to unlock with "unlock OEM option"?
Click to expand...
Click to collapse
well as far as i know i need it so i can try to flash a new android version on it im trying force 6.0 on it and yes i know there is no S4 (i9515) android 6.0 version but i still want to try and do it its a old phone anyway
ppl you can forget about this post i found the problem more or less first off i had the wrong twrp version that caused the bug on twrp afterward it was all smooth sailing
for all the other ppl who want a non official android 6.0
go to youtube and look for:
install Android 6.0.1 Marshmallow Galaxy S4 GT-I9515
posted by ما لا تعلم ?
all the files you need are in the discription
Best regards,
Darkdevel
Pwnycorn said:
You can't install anything unsigned with the stock recovery. No phone gives you such privileges. That's why people made custom recoveries.
Click to expand...
Click to collapse
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.
FurySh0ck said:
But you can't install a CR without OEM unlocked.
I am having the same problem right now (same device, gt-i9515), no OEM unlock option in developer options.
I kinda need it to install TWRP, it won't let me do it otherwise. I openned a new thread about it and explained the issue I have in more details.
Click to expand...
Click to collapse
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.
Pwnycorn said:
Dude, all S4 models, except for the Verizon and AT&T models, have an UNLOCKED BOOTLOADER.
An OEM Unlock option is, therefore, redundant because there is absolutely nothing to unlock. And the ones that do have a locked bootloader CAN'T BE UNLOCKED.
If you want TWRP follow a guide on how to install it. They even have one on the TWRP website and nowhere does it say that you need to OEM unlock. In fact, no S4 rooting/twrp flashing guide will mention any OEM unlock option.
If it does, it's garbage.
Click to expand...
Click to collapse
It's very strange then. When I had a root (same device gt-i9515 for SURE), I managed to flash TWRP on my first try, no mistakes.
I recently flashed a firmware (from sammobile. I9515XXU1BOE3_I9515DBT1BOE1_DBT, because my PDA is i9515xxu1boe3) and wiped everything. It's like a new device now.
In it's current state (non-root) I couldn't install TWRP via the same method I did before (ODIN + TWRP.tar).
About the comment on the other thread, yes, I am sure it's gt-i9515 and I know that if the USB is getting disconnected, ODIN writes it on screen, so I could see it.
Here's the guide that told me about OEM: http://www.theandroidsoul.com/how-to...ry-using-odin/ (I understand that it's a trash guide lol)
Update:
I finally did it, explained here: https://forum.xda-developers.com/ga...p-cr-galaxy-s4-gt-i9515-t3668461#post73680660
Thanks for your help!
Hi all,
I don't have this phone yet, but was wondering if the bootloader can be unlocked. If it can then it will be possible to root.
Here is a simple guide, if there is anyone here that would like to try. No software required.
http://techbeasts.com/how-to-enable-oem-unlock-on-android-nougat/
If OEM Unlock shows up in the developers options menu.. good news!! If OEM Unlock doesn't show up, then there is no way to unlock the bootloader.
Please let me know if your phone is the Amazon Prime version. The Prime version may be locked down.
Thanks for any replies!
Prime version is indeed locked down. Also, at any point that you change anything on the phone to do anything with the software, Amazon will not provide you updates again.
I was able to unlock developer options in my Amazon version but now what? I'm assuming that the bootloader is now unlocked and theoretically, I should be able to flash a new rom? Problem is, does one exist? Cheers.
Just an FYI that my Prime Version did allow me to activate Developer Options/OEM Unlocking. Next step is trying to find a rom or even flash it to regular factory default. That I have not found yet.
Quick question SDACymru - I'm getting this phone in a few days... how did you perform the OEM unlock in dev options?
The normal way. Just tapping on the option for 5 or 6 times.
SDACymru said:
The normal way. Just tapping on the option for 5 or 6 times.
Click to expand...
Click to collapse
Thanks. Is there a reason we shouldn't be able to restore from a backup of a non-ads phone stock image and at least get that running on ad-based versions? From my understanding they are exactly the same hardware-wise, so should be possible...
Being able to expose "Developer option" and access to "OEM unlock" still don't make this is developer-friendly device, but I quite surprised that the Amazon Prime version even show the "OEM unlock" in the "Developer option". Anyway, it is close, if you can also perform the last 2 steps, then this device can be considered as developer-friendly.
The next 2 steps are:
- Reboot into fastboot
- fastboot oem unlock (from adb console)
Some devices with full fastboot implementation can check the device lock state by
- fastboot getvar all
If all these commands work, then the device will have good developer support. In addition, if all these commands work on the Amazon Prime version, then it is a piece of cake to remove the Amazon ads.
did anyone every try any of this? ADB Shell temp root has been achieved on this model, I have the temp root xploit but it's useless unless people know what they are doing with it. You can easily brick your phone. I don't physically have this phone but what I do have is a little knowledge, access to the stock rom and a way to flash it. I also know that the recovery can be swapped with TWRP during that flash process. Hit me up on Telegram: https://t.me/PizzaG
So being that I have actually gained temp root access (all credit to PizzaG, he knows his stuff)
Should I go ahead and give the fastboot steps a go? Would the persdata\nvdata remove the temp root access with a reboot or am I way off course?
Any input appreciated
Sent from my Alcatel 6060C using XDA Labs
DelRi0 said:
So being that I have actually gained temp root access (all credit to PizzaG, he knows his stuff)
Should I go ahead and give the fastboot steps a go? Would the persdata\nvdata remove the temp root access with a reboot or am I way off course?
Any input appreciated
Sent from my Alcatel 6060C using XDA Labs
Click to expand...
Click to collapse
Just rebooting you will lose temp root access. all you have to do is run the commands again any time you want adb shell temp root.
Please check out my new thread in the idol 5 forum. I have some things and ideas brewing
Magisk working
Thanks to the Mtk Easy Su app I have magisk working without flashing anything. How do ya get to fastboot on this thing? Recovery sucks, factory mode is pointless, so where's the good boot mode 99?
My guide to unlock bootloader and install twrp recovery.
https://androidforums.com/threads/6060c-bootloader-unlock.1327876/
Hello:
I am trying to follow the instructions to unlock the bootloader on my Sprint G900P Galaxy S5.
I installed the ADB SDK, the Samsung USB driver, turned on USB debugging on my phone, and connected it to my computer.
I typed adb reboot bootloader and the phone rebooted into a screen to download software to it.
Next, I typed fastboot oem unlock and I get a message on the screen < waiting for any device >
and it does nothing.
This is strange because obviously the computer was able to send the adb command to the phone so there is communication.
Why would is stop at the fastboot step?
Any ideas?
Thanks,
Neil
Ummm dude your booloader is already unlocked since it's from Sprint. You just go into your Dev options and toggle on OEM UNLOCK and your all set
gurnsey101 said:
Ummm dude your booloader is already unlocked since it's from Sprint. You just go into your Dev options and toggle on OEM UNLOCK and your all set
Click to expand...
Click to collapse
When I go to Developer Options, I do not see an OEM UNLOCK option. Any ideas?
NeilAgg said:
When I go to Developer Options, I do not see an OEM UNLOCK option. Any ideas?
Click to expand...
Click to collapse
It's most likely already unlocked.
kicker63 said:
It's most likely already unlocked.
Click to expand...
Click to collapse
I went to Google Play Store and installed the Root Checker by Clivin Inc.
When I ran the app, it says: Your device is not rooted
I am not sure where to go from here.
NeilAgg said:
I went to Google Play Store and installed the Root Checker by Clivin Inc.
When I ran the app, it says: Your device is not rooted
I am not sure where to go from here.
Click to expand...
Click to collapse
Hi,
Just wondering what are you going to achieve ...
1. Don't bother with any "oem unlock" options as there is no any in your phone model. Your bootloader is uncloked by default and that's it.
2. Rooting is different story - if you didn't root your device yet then the root checkers will tell you exactly this -> so you need to root your phone to get different reply
Many40 said:
Rooting is different story
Click to expand...
Click to collapse
I did not realize that. Thanks for the info.
I used the SkipSoft Unified Toolkit to root the device.
Thanks,
Neil
I've been searching the forums and internet for a while, but I cant seem to find any twrp that is specifically for the ZTE Maven 3 (z835). I have very little knowledge about this, and I really do not need a new paperweight. I already got the developer options, I know about the OEM unlocking and was looking at another option that I believe might be relevant which is "USB debugging," I feel like that would be important to activate to once I begin the steps of getting twrp installed because it allows file sharing between the device and computer. Ultimately, my goal is to root this phone if that becomes possible, but in the past I've bricked an Alcatel Ideal while messing around with my newly found power since I had no clue what I was really doing (I successfully got the root on that phone, tried flashing SuperSU without clearing the dalvik cache first and soft-bricked it) I wasn't able to fix that since I didn't have a custom recovery installed, that is why Id like to get twrp on this ZTE so if I make a mistake in the future it wont leave me without a phone.
Isaac0900 said:
I've been searching the forums and internet for a while, but I cant seem to find any twrp that is specifically for the ZTE Maven 3 (z835). I have very little knowledge about this, and I really do not need a new paperweight. I already got the developer options, I know about the OEM unlocking and was looking at another option that I believe might be relevant which is "USB debugging," I feel like that would be important to activate to once I begin the steps of getting twrp installed because it allows file sharing between the device and computer. Ultimately, my goal is to root this phone if that becomes possible, but in the past I've bricked an Alcatel Ideal while messing around with my newly found power since I had no clue what I was really doing (I successfully got the root on that phone, tried flashing SuperSU without clearing the dalvik cache first and soft-bricked it) I wasn't able to fix that since I didn't have a custom recovery installed, that is why Id like to get twrp on this ZTE so if I make a mistake in the future it wont leave me without a phone.
Click to expand...
Click to collapse
Just found a method for unlocking the bootloader and that seems very simple if it goes as planned, Installing the twrp after that is what I'm unsure of now
Isaac0900 said:
Just found a method for unlocking the bootloader and that seems very simple if it goes as planned, Installing the twrp after that is what I'm unsure of now
Click to expand...
Click to collapse
Please share. How do you unlock the bootloader?
blankulus said:
Please share. How do you unlock the bootloader?
Click to expand...
Click to collapse
He was just trolling. Nobody has figured out an unlock for the bootloader for ZTE Maven 3 (Z835) yet. I really would like to figure out a root method, as it's a great quality device for such a low price. Seriously lacking in storage though, which is where a root would really come in clutch for this devices popularity. I hope at least a TWRP is available soon.
Unlocking the bootloader is in the developer options menu.
blankulus said:
Please share. How do you unlock the bootloader?
Click to expand...
Click to collapse
Triforce0fWisdom said:
He was just trolling. Nobody has figured out an unlock for the bootloader for ZTE Maven 3 (Z835) yet. I really would like to figure out a root method, as it's a great quality device for such a low price. Seriously lacking in storage though, which is where a root would really come in clutch for this devices popularity. I hope at least a TWRP is available soon.
Click to expand...
Click to collapse
Not sure what you're talking about Triforce. Unlocking the bootloader is a standard, supported feature of this device.
1) Go to About -> Build in the Settings menu.
2) Tap until you unlock Developer options in Settings.
3) Go into Developer options.
4) Enable OEM unlocking.
There really isn't anything to "figure out" here as far as the bootloader is concerned.
Now, TWRP, root, and SIM unlock, those would be useful to figure out.
gamescan said:
Not sure what you're talking about Triforce. Unlocking the bootloader is a standard, supported feature of this device.
1) Go to About -> Build in the Settings menu.
2) Tap until you unlock Developer options in Settings.
3) Go into Developer options.
4) Enable OEM unlocking.
There really isn't anything to "figure out" here as far as the bootloader is concerned.
Now, TWRP, root, and SIM unlock, those would be useful to figure out.
Click to expand...
Click to collapse
If you had this phone you would know our struggles I have already done these steps and have used adb reboot bootloader and adb reboot recovery and selected reboot to bootloader which has not worked and the device does not work with fastboot commands and I don't think it has the feature to do so.
Sent from my ZTE Z835 using XDA Labs
Bump
Sent from my ZTE Z835 using XDA Labs
Guys, big news! We are getting a dedicated forum for the ZTE Maven 3! It will be up within the next day or so.
Sent from my ZTE Z835 using XDA Labs
no root on a china phone yet.. now thats an issue.
Bowserman16162 said:
Guys, big news! We are getting a dedicated forum for the ZTE Maven 3! It will be up within the next day or so.
Sent from my ZTE Z835 using XDA Labs
Click to expand...
Click to collapse
Last reply was a year ago. Is there now a bootloader unlock?
I am trying to unlock my bootloader and root my phone but I am unable to turn on the OEM unlocking feature in developers options. Several months ago I returned/restored the phone's stock image. I previously rooted my phone but decided to unroot it. Now I am attempting to root it again but I cannot unlock the bootloader by switching on OEM unlocking.
The OEM Unlocking option is greyed out and appears to be locked or inaccessible. I have attached a screen shot.
Can someone tell me what I must do to fix this.
LeoG360 said:
I am trying to unlock my bootloader and root my phone but I am unable to turn on the OEM unlocking feature in developers options. Several months ago I returned/restored the phone's stock image. I previously rooted my phone but decided to unroot it. Now I am attempting to root it again but I cannot unlock the bootloader by switching on OEM unlocking.
The OEM Unlocking option is greyed out and appears to be locked or inaccessible. I have attached a screen shot.
Can someone tell me what I must do to fix this.
Click to expand...
Click to collapse
Are you sure the BL is locked now? If not boot into BL and check it. In any case Google is your friend:
https://www.theandroidsoul.com/how-to-fix-oem-unlock-greyed-out-or-oem-unlock-disabled-problem/
That's why I don't see any sense in relocking, I can't find any advantage in it.
Sent from my Moto G5 Plus using XDA Labs
Wolfcity said:
That's why I don't see any sense in relocking, I can't find any advantage in it.
Sent from my Moto G5 Plus using XDA Labs
Click to expand...
Click to collapse
I hear you Wolfcity. And it is something that seems to come up on every device I have owned starting with the Moto G2 (G3, G4, G5+, & G5s+). I have had users flat out tell me I am wrong and that you need to relock the device in order to go back to stock or remove root. :silly: