Related
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 need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
SD008 said:
I need to relock the bootloader, but the fastboot oem lock command doesn't work saying
C:\G5>fastboot oem lock
...
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.002s]
finished. total time: 0.003s
But that option is greyed out. I'm on POTTER_NPN25.137-92 Stock ROM with unlocked bootloader (XT1686).
Please help!
Click to expand...
Click to collapse
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
acejavelin said:
Because that isn't how you lock the bootloader on Moto devices... you can't just lock your bootloader on the fly, it can only be down with a full factory image flash. In your case, it is something like this:
'fastboot oem lock ' <get prompted to make sure you want to this and enter command again>
'fastboot oem lock'
Then fastboot flash the full factory image of NPN25.137-92 or newer ROM for your device, including all wipes, and end it with
`fastboot oem lock` - but this will only work if you used oem lock at the beginning and in conjunction with a complete image flash.
There are tutorials on here how to do it, a little research in the forums here will yield a couple different tutorials.
BTW, it is well known that relocking the bootloader on the Moto G5 series is problematic... Sometimes it doesn't work, and sometimes it bricks.
Remember that regardless of if you relock or not, the bootloader unlock warning screen will always be there, and the bootloader will never go back to Status 0 - Locked, it will become Status 2 - Relocked so it is still a clear indication the phone was modified at one point.
Click to expand...
Click to collapse
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
sinchan_nohara said:
Hi I want to ask a question I restored my nandroid stock backup VoLTE , LTE everything is working fine. I have Moto stock recovery but on device bootup it shows bootloader unlocked sign.
Can I install updates when update come without any issue or will it brick my device I have stock moto recovery
Click to expand...
Click to collapse
If you haven't changed anything in /system or /vendor and your device is stock unrooted there's no problem with OTA updates. If you flashed the stock logo.bin everything is ok even when it shows BL is unlocked.
Sent from my Moto G5 Plus using XDA Labs
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
It's funny how you automatically assumed that I didn't see any of the 3 or 4 guides posted in here and just straight-up made a thread to beg for help. Obviously I flashed a stock firmware before beginning the locking process (and after it too), but as I clearly mentioned in the OP, the problem was that due to the Allow OEM switch being disabled and greyed out, the 'fastboot oem lock' command was not doing its thing. Had it worked properly, it'd tell me to proceed with flashing the system chunks, but it didn't. So yeah, what you said wasn't really helpful. Thanks anyway for taking the time to reply. Just please don't assume w/o any evidence that someone is so ignorant as to not read a guide and beg for answers. There are many people like me who only lurk and do everything by following tutorials and only ever post if all else fails.
Click to expand...
Click to collapse
I've been here a long time, didn't mean to offend... All I had to go by was your limited information of the first post, I assumed nothing that wasn't included in your post. You didn't state anything that you had tried, so of course I assumed you didn't look because you didn't state anything.
Sorry. I will just bow out and wish you luck.
SD008 said:
After a lot of Googling I was able to find the solution. Had to search high and low for it, finally found the relevant information in the Oneplus 5 subforums. What I needed to do was flash Magisk and then the OEM unlock option becomes usable again. For anyone facing a similar issue, flash either stock or a stock-based rom along woth Magisk and enable OEM unlock in the dev options and the you should be able to re-lock.
Click to expand...
Click to collapse
Man, I was having the same issue on my Moto G6 (Ali) and was like you, looking here and there with no solution, and your solution was the only one that worked!! Thank you so much!
I'm quite interested in buying this device (Nova 3i), but it's very important to me that i can root it.
I've noticed that the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country.
So the question is:
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat?
Or do I still have to unlock it using unlock key from Huawei Website (which is unavailable)?
And if not, is there any other way to root it? Has anyone had luck in rooting it (e.g. Kingroot, etc)?
Thanks in advance.
Jan oatcoal said:
I'm quite interested in buying this device (Nova 3i), but it's very important to me that i can root it.
I've noticed that the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country.
So the question is:
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat?
Or do I still have to unlock it using unlock key from Huawei Website (which is unavailable)?
And if not, is there any other way to root it? Has anyone had luck in rooting it (e.g. Kingroot, etc)?
Thanks in advance.
Click to expand...
Click to collapse
Have tried king root.... Stuck at 1 percent not hoing any further and its bootloader is still locked so we need to wait till we can get someone to unlock it
Xial Xahab said:
Have tried king root.... Stuck at 1 percent not hoing any further and its bootloader is still locked so we need to wait till we can get someone to unlock it
Click to expand...
Click to collapse
The days of kingroot working on phones are long gone
Dheeraj Menon said:
The days of kingroot working on phones are long gone
Click to expand...
Click to collapse
I knew that... But still wanted to see if that's a thing or no
Jan oatcoal said:
I'm quite interested in buying this device (Nova 3i), but it's very important to me that i can root it.
I've noticed that the option "OEM Unlock" is not greyed out, and can be easily enabled, at least in the devices that are sold in my country.
So the question is:
Is it enought to enable "OEM Unlock" in "Developer Options" from the phone settings to unlock the bootloader and I can simply install TWRP afterthat?
Or do I still have to unlock it using unlock key from Huawei Website (which is unavailable)?
And if not, is there any other way to root it? Has anyone had luck in rooting it (e.g. Kingroot, etc)?
Thanks in advance.
Click to expand...
Click to collapse
pls check PHONE status in Fastboot and rescue mode. I have the nova 3i INE-LX2 it says its unlocked.
how did you manage to unlock it? plz share
how did you manage to unlock it? plz share
jioleight said:
pls check PHONE status in Fastboot and rescue mode. I have the nova 3i INE-LX2 it says its unlocked.
Click to expand...
Click to collapse
how did you do this
How you did it
How you did it please share The method i try about 5 app no one open it
Quick and simple bc after sifting through this website I accidently figured it out. First use the script from this post - https://forum.xda-developers.com/t/oneplus-pure-debloat.4157691/ then check dev options and OEM unlocking should be ungreyed out. Grab your oneplus unlock by running this command - "fastboot oem get_unlock_code" Then go to - https://www.oneplus.com/unlock_token submit your token and serial number and wait exactly one week to the day. Download this tool https://forum.xda-developers.com/t/...ck-twrp-factory-image-stock-recovery.3358711/ and you can unlock the bootload with your unlock.bin file. After that whats next is up too you!
I don't know about SIM unlocking, however I did figure out which package specifically enables the toggle for OEM unlocking in the Developer Options.
So I took a look at the debloat thread linked above and I went through the list of packages and I was uninstalling them on my phone one by one until I found the one that enabled the toggle for OEM unlocking in the Developer Options.
When I uninstalled the package com.qualcomm.qti.uim, the toggle for OEM unlocking was no longer greyed out.
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
LLStarks said:
That's a great find. Is it enough to simply force-stop the package or does it need to be disabled/uninstalled?
Might try this on the OP9 or OP10 if I get one.
Click to expand...
Click to collapse
I didn't see if force stopping it worked or not so I wouldn't be able to answer that. I just uninstalled it with adb.
Title of tread said sim-unlocking, after reading through, it only mentions bootloader unlocking via the OnePlus website and all in one flashing tool. Yes it may bypassed the carrier restriction for bootloader unlocking, but is the phone actually sim unlocked? As you can use it with another carrier?
But I agree, finding out com.qualcomm.qti.uim being the toggle for bootloader unlock is great find.
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
kevinco1 said:
I disabled com.qualcomm.qti.uim via ADB myself and while 'OEM Unlocking" is no longer grey and you can enable the option the bootloader for me is still locked. My OnePlus 8T model is through T-Mobile
Click to expand...
Click to collapse
gotta complete the whole process homie.. AFTER doing the uninstall or disable of com.qualcomm.qti.uim, then you gotta flip the toggle and then reboot to bootloader. after that you need to run the fastboot command, "fastboot oem get_unlock_code"... copy that code to your clipboard, then go to the Oneplus website, fill out the form and paste that code in the proper field.
After that it does take exactly one week... (to the minute) and you will need to go back to this site and you will see it change to download. Download that file and flash it via fastboot, then confirm you want to unlock and its done!
Now after that you have to remember to NEVER flash a stock firmware via fastboot again, otherwise you will re-lock your bootloader. I cannot confirm whether or not you will be able to, or even need to flash the unlock token again, but in the case of Samsung phones, when you flash the bootloader unlock token, you DO NOT get a second chance. If you unlock it once, and then accidently re-lock via flashing stock, you will be stuck with a locked bl. (EDIT: you CAN flash stock with samsung, as long as the bootloader version isnt changed. If you upgrade the BL then you are stuck!)
(Now theres a simpler way around all this but you must do your research, and look into converting your TMO-US fw to TMO-EU ... this can be done without unlocking the bootloader. And after the conversion, if you disable the OP mentioned file, you can simply toggle, and run the "fastboot oem unlock" command and thats it... no token file needed! And i am in Texas, so i can confirm 100% that ALL of the bands are active and available, and i get 5g with absolutely no problem... In fact my phone runs quicker and gets better battery life on the EU fw. )
Then when your phone is fully paid off, simply flash back to the US fw and you can have them Sim unlock you and you can either go thru the normal unlocking process, or you can go back to the EU... but either way no foul, no harm!
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
kyanox said:
So to get T-Mobile to do it on their end do this.
Go on their site and facebook, keep telling them this. "I'm a developer who can't develop app's on my device, can you please allow my phone to be unlocked." Most will tell you it needs to be paid off, but you quite possibly will get that disgruntled worker or guy who just doesn't care. Took me 5 tries, then the guy I got was like, "okay I'll do it for you!" #boomdone
Social engineering at its finest.
Click to expand...
Click to collapse
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
i am shop in istanbul come to me oneplus 8t 5g t-mobile i ask whole world for simlock no one can and one of customer tell me i can unlock he take device for 3 hour he come back and device unlocked and he tell me i can do anything in oneplus phones i got crazy how he did this ? anyone know how ?
jabe78 said:
I have had this same issue. I bought the 8T+5G from OnePlus online store TMobile version (because the unlocked versions were sold out). Been back and forth betwee TMobile and OnePlus for 4 days, and OnePlus finally says they nor Tmobile can unlock the device until it has been used on Tmobile's service for 45 days (part of the unlock policy). I knew this, but thought surely someone can help me. OnePlus assured me that the IMEI number does not enter into the system as an unlockable phone until after the 45 days, and that NOBODY can unlock the phone until then... Am I screwed for 40 more days???? This in my opinion is a scam to force people to use a service they may not want.
Click to expand...
Click to collapse
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
jabe78 said:
Yeah. I'm going to wait it out. Counting down the days I'm chained to T-Mobile (38 left). I actually wanted their service so it isn't an inconvenience, but I hate being forced to do anything, much less wait to do what I wanted to do from day one, which is Flash Roms. I'm looking at Lineage too. So I will update this post once I get to that point. Here's hoping they keep their word, because my 15 day return policy on the phone runs out in two days.
Click to expand...
Click to collapse
I should've done more research myself. Galaxy was about to quit on me so I grabbed this one specifically because it was rated as one of the very top phones for development. If it wasn't such a rush I would've spent more time.
jtford said:
Alright folks I've been with Samsung over a decade and just got my first Oneplus (8T+5G KB2007) so don't start yelling at me just yet. Got this thing on Amazon and appears to be new. I'm sim/network unlocked through TMO. My OEM Unlock was never greyed out. I can toggle no problem. However, I went through the debloat described above because of the following problem: Sticks on "waiting for any device" after running "fastboot oem get_unlock_code" Please tell me this is an easy fix. I already reinstalled the google driver through SDK Manager bla bla bla.... Am I missing something simple? Any help would be appreciated. THX
Click to expand...
Click to collapse
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Xryphon said:
Have you checked if your phone is properly connected to your computer? Check using "fastboot devices" to see if your device is detected, and if it is not, then go within the Windows Device Manager and install the appropriate driver from Google, which can be found by searching "Google Fastboot Driver".
Click to expand...
Click to collapse
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
jtford said:
It doesn't show it shows under adb devices but not fastboot devices. Let me find the fastboot driver real quick and try. Thanks
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Rootk1t said:
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Click to expand...
Click to collapse
Holy ****.... finally! I just needed the OnePlus_usb_driver_setup.exe in order to install the right driver from said directory. Big thanks man. Really!
TommyQuid said:
Does this still work on the recent 8T phones? Please do keep us updated on your situation. I'm thinking about buying this phone unlock the boot-loader, Sim unlock and get Lineage on it. I don't mind 45 days if they actually unlock it
Click to expand...
Click to collapse
So it was actually 40 days, I don't know why I said 45. Anyway, even after (48 days), it took me calling TMOBILE and having someone talk to their (OEM team) and start a conversation with them. 3 days later I was able to SIM unlock the phone. I was able to toggle OEM unlocking. Did the Fastboot command to get the Unlock Code, and sent it to OnePlus for "7 days". What the crap is all of this hassle? I left Android and went to Apple for 7 years. When I left, you could unlock a bootloader in minutes. For being so keen on allowing us to unlock our phones, it seems they give you a Circus of Hoops to jump thru "on Their timeline". Anyway, I actually think I may have screwed up the code because it was displayed on two lines from Fastboot. I sent it as one line. Hoping they sort it out and I don't have to reapply and wait another 7 days. What a mess!
jabe78 said:
So it was actually 40 days, I don't know why I said 45...
Click to expand...
Click to collapse
Thanks for the update
Hello all,
how do I get the grayed out OEM unlock disabled again in the developer options on the Samsung Galaxy Tab 5e?
Thanks
Varusch said:
Hello all,
how do I get the grayed out OEM unlock disabled again in the developer options on the Samsung Galaxy Tab 5e?
Thanks
Click to expand...
Click to collapse
Do you mean how to get it enabled again?
Can you specify what all you have done to your device so far?
V0latyle said:
Do you mean how to get it enabled again?
Can you specify what all you have done to your device so far?
Click to expand...
Click to collapse
Hello, thanks for the reply.
LineageOS I wanted to install on the device according to the instructions (https://wiki.lineageos.org/devices/gts4lv/), unfortunately did not work, in the LOS forum I also asked for help, but none get useful help there. I enabled the developer option and unlocked OEM and enabled USB debugging. Then something went wrong with Odin
But now OEM is still enabled and the box is grayed out so I can't disable OEM again. But I want to disable OEM again, is there a tutorial?
Greetings Varusch
Varusch said:
Hello, thanks for the reply.
LineageOS I wanted to install on the device according to the instructions (https://wiki.lineageos.org/devices/gts4lv/), unfortunately did not work, in the LOS forum I also asked for help, but none get useful help there. I enabled the developer option and unlocked OEM and enabled USB debugging. Then something went wrong with Odin
But now OEM is still enabled and the box is grayed out so I can't disable OEM again. But I want to disable OEM again, is there a tutorial?
Greetings Varusch
Click to expand...
Click to collapse
You would need to re-lock the bootloader. If the bootloader is unlocked, OEM Unlocking remains grayed out with the message "Bootloader is already unlocked"
However, if you want to install a custom ROM, you need to leave your bootloader unlocked.
What problem did you have with LineageOS? If you have TWRP installed on your device, it should be easy to flash a GSI.
V0latyle said:
You would need to re-lock the bootloader. If the bootloader is unlocked, OEM Unlocking remains grayed out with the message "Bootloader is already unlocked"
However, if you want to install a custom ROM, you need to leave your bootloader unlocked.
What problem did you have with LineageOS? If you have TWRP installed on your device, it should be easy to flash a GSI.
Click to expand...
Click to collapse
Thanks for the reply, is there any guidance on this?
What is a GSI?
Varusch said:
Thanks for the reply, is there any guidance on this?
What is a GSI?
Click to expand...
Click to collapse
GSI = Generic SYSTEM Image. You would flash it to /system and use it with the stock kernel.