Related
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
JulesJam said:
There is an Enable OEM Unlock option that is appearing in the Developer Options of the N6 and MX14 running 5.1 and if it is not checked, you cannot unlock your bootloader. If you unlocked via Sunshine or purchased a code for your device from the Chinese code seller, we do not know what is going to happen wrt this Enable OEM Unlock option for your phone if you upgrade to 5.1.
Until we do, it is safest to not upgrade and stay unlocked until 5.1 drops and the situation becomes clearer.
Click to expand...
Click to collapse
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
I can't imagine the OTA would lock the bootloader, but who knows...
fury683 said:
I don't think this is going to be an issue. People said in the N6 forums that they were able to unlock via fastboot without ever changing that setting in developer options. They hadn't even booted the phone into Android yet, just took it out of the box, put it in fastboot and unlocked.
Click to expand...
Click to collapse
But others relocked after unlocking and didn't check the box then flashed something, ended up in a bootloop and were unable to unlock again to repair their phones.
Regardless, you cannot rely on what happens with a Nexus device. These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
fury683 said:
I can't imagine the OTA would lock the bootloader, but who knows...
Click to expand...
Click to collapse
I don't think it will relock the bootloader either. I am more concerned about those who relock then take the update not realizing that they will not be able to unlock again.
JulesJam said:
These MX13's were never intended to have unlockable bootloaders, whereas the Nexi were intended to have unlockable bootloaders.
Click to expand...
Click to collapse
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Didn't intend to say you were wrong in my first post, just that people had the same thoughts when the N6 came out and it wasn't a problem. People freaked out when My Verizon updated a while back and it requested root permissions, too. It's an abundance of caution, I get it.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable.
Click to expand...
Click to collapse
The GSM Dev Ed is not identical to the AT&T MX13. But still, so what? None of us know how this is going to be implemented in 5.1. We can speculate all we want but we will know for sure once it is released.
fury683 said:
Regardless, I will wait until the process is confirmed and use the same process that I did to update from 4.4.2 to 4.4.4. Reflash stock /recovery and a clean /system, take OTA, then reflash TWRP and flash SuperSU. I value my root to much to risk it.
Click to expand...
Click to collapse
Rather than take the OTA, I would use Motorola Device Manager to upgrade - it leaves a copy of the fxz on your computer.
fury683 said:
, just that people had the same thoughts when the N6 came out
Click to expand...
Click to collapse
No, they could not have had the same thoughts as the N6 was always an unlockable device. You don't have to use Sunshine or purchase an unlock code to unlock the N6. So whatever thoughts anyone has had about the Enable OEM Unlock feature wrt how it would work with the N6 have nothing at all to do with this thread. The situations are totally different.
fury683 said:
and it wasn't a problem
Click to expand...
Click to collapse
On the contrary - it has been quite a problem for a lot of people with N6's who relocked their bootloaders. That is well documented on the N6 forum.
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Saythis said:
Running the soak test of Android 5.1 and there is no Enable OEM Unlock option on it..
Click to expand...
Click to collapse
The option only appears when you update to 5.1 with your bootloader locked.
fury683 said:
Except the Developer Edition units that are identical in every way to the retail versions, but the unlock code is obtainable...
Click to expand...
Click to collapse
Most would expect that for those Moto freely gives away the bootloader unlock code for (on their web site), should be ok and not impacted. At least that is what we hope, otherwise Moto could have a bunch (maybe a small bunch) of angry users on their hand
But the thought about a warning or caution was directed toward those with ATT, Republic Wireless, or Verizon (non-dev) units who either purchased their bootloader unlock code from the China seller (or middle man) when it was available, or used Sunshine in order to bootloader unlock... since those devices were not ever intended to be bootloader unlocked.... There is uncertainty over this new "check box" in the rom. Moto could leave it out for those models (especially since ATT and RW use their own roms, VZW could be a little trickier since all XT1060's, dev and non-dev use the same rom), and if so, how does that impact any user who had a code and didn't use it yet, or unlocked, and might later want to relock for some reason.
For Sunshine, the concern would be due to changes in the phone's bootloader, TZ, or other parts that might be included in the update which might close that exploited vulnerability down. Think back to how some of the early Root/WPDisable processes were said to be "permanent" only to find they were NOT when the next OTA came out and "un-did" the hack.
So yeah, as you said...
fury683 said:
It's an abundance of caution, I get it.
Click to expand...
Click to collapse
superkeest said:
Why would I relock my bootloader to take the OTA? Why would I relock for any purpose?
Click to expand...
Click to collapse
Some people relock b/c they think it is more secure if they lose their phone or it gets stolen.
it leaves a copy of the fxz on your computer.
sseuorosal said:
it leaves a copy of the fxz on your computer.
Click to expand...
Click to collapse
Motorola Device Manager does, yes if you upgrade using MDM, you will have a copy of the fxz on your computer.
Any Updates on this situation?
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
dont know about 5.1 but when i flashed 4.4.4 removing cm 12.1 on my att moto x it didnt relock my bootloader hope this stays same with 5.1 i used sunshine to unlock.
Icon000 said:
It's almost been a month. Has anything new been discovered? I'd like to know if I can update to 5.1.
Click to expand...
Click to collapse
The 5.1 OTA for ATT, Republic Wireless and Verizon hasn't been available yet, so I doubt anyone has tried it.
The only ones upgrading to 5.1 right now are those with a bootloader that is unlockable via code from Moto's web site.
I haven't seen Jcase, Beaups, or anyone related to Sunshine make any comments.
Further... I asked in the Sunshine thread...
See JCASE's response -> http://forum.xda-developers.com/showpost.php?p=61503326&postcount=3529
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
breakthestatic said:
I have an XT1060 (VZW), unlocked via Sunshine. I recently switched to T-Mo, and although the VZW build worked fine, I wanted Lollipop, so I flashed the stock T-Mo 4.4.4 build, and then sideloaded the 5.1 update. I am still unlocked and everything is working fine. I'm not sure if this totally mimics your situation, but I can say that the 5.1 update rolling out to T-Mobile doesn't affect the bootloader status for Sunshine unlocked devices.
Click to expand...
Click to collapse
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Maverick-DBZ- said:
Exactly what I've done, converted my mother's Sunshine unlocked BL Verizon Moto X into a T-Mobile one. I'm waiting for the OTA instead of sideloading to see how things go. I'm guessing by your experience she shouldn't have any problems taking the OTA update to 5.1.
Click to expand...
Click to collapse
How did you convert it, I'm considering converting my att moto x to retail version. Btw its bootloader is unlocked
Don't buy this crappy xioami.
Nowadays xioami LOCKed BOOTLOADERs
Start from RN3 RNP Mi4c
The rest will be lock too.......VIA STOCK ROM
Hugo Barra is smart
We are stupid includes me. Bcos I bought new RN3
then only learned that bootloader is LOCKed
Too much hustle to unlock.
For so many many days past by waiting for unlock code
So what, just apply for unlock and wait. For this price of hardware it's worth it. I hope there will be some reasonable custom AOSP rom.
Gibol666 said:
So what, just apply for unlock and wait. For this price of hardware it's worth it. I hope there will be some reasonable custom AOSP rom.
Click to expand...
Click to collapse
See the thing is by their terms just because you request one doesn't mean you will get it. It is up to them.
As for aosp I wouldn't count on it, most developers won't touch their devices nor do they support them.
zelendel said:
As for aosp I wouldn't count on it, most developers won't touch their devices nor do they support them.
Click to expand...
Click to collapse
Why shouldn't we cont on developers to work on this ROM? I see that the Redmi 2 has plenty of custom ROMs available right here on XDA forum.
Sent from my Redmi 3 using Tapatalk
They locked the bootloader for a reason. There has already been reports of Xiaomi refusing to provide an unlock code to users.
Most roms for Xiaomi devices are ports at best with the one exception being the one CM supports. Development teams know this, and on top of their constant gpl violations leave a bad taste.
Don't get me wrong. I hope things work out but in ref to aosp based development there won't really be much
Can anyone tell me what is bootloader for?, why is it important to unlock it?
http://www.addictivetips.com/mobile...-bootloader-on-android-phones-complete-guide/
I've recieved the unlock confirmation today. Now just waiting for developer rom to be released
Gibol666 said:
I've recieved the unlock confirmation today. Now just waiting for developer rom to be released
Click to expand...
Click to collapse
Well, so it IS possible!
For how long did you wait?
Eleven or twelve days, not that long compared to 3weeks+ that some people reported
Gibol666 said:
I've recieved the unlock confirmation today. Now just waiting for developer rom to be released
Click to expand...
Click to collapse
Is it really need to unlock bootloader in other to flash developer ROM?
I know a lot of mi4 owners who regularly use weekly developer without haven't ever unlocked their bootloader.
So is it really necessary for our redmi3 to unlock the bootloader in other to flash developer ROM?
Cause I really like to remain virgin while being able to ***** around ?
Sent from my Redmi 3 using Tapatalk
No. You got it wrong. You need to flash the developer ROM in order to unlock bootloader ( to be able to flash other ROMs.)
Gibol666 said:
No. You got it wrong. You need to flash the developer ROM in order to unlock bootloader ( to be able to flash other ROMs.)
Click to expand...
Click to collapse
so let me get this straight, i don't need to unlock bootloader in order for me to use Global ROM or Developer ROM, but if i want to use other ROM (Custom), i need to unlock it. How about if i want to root?
spiderclan said:
so let me get this straight, i don't need to unlock bootloader in order for me to use Global ROM or Developer ROM, but if i want to use other ROM (Custom), i need to unlock it. How about if i want to root?
Click to expand...
Click to collapse
Nope, rooting the device has nothing to do with the locked bootloader. But I am not entirely sure if there is a way to root the redmi 3 just yet.
Unlocked bootloader is needed for:
- Custom roms that don't use the stock kernel
- Custom kernels
- Non stock-based roms (CM for example)
unlock confirmation received
I've recieved the unlock confirmation today.
What must I do to unlock the bootloader?
The sms says:" Your unlock request has been approved. Go t XXXXXX to download the unlocking tool"
Thanks in advance
felison69 said:
I've recieved the unlock confirmation today.
What must I do to unlock the bootloader?
The sms says:" Your unlock request has been approved. Go t XXXXXX to download the unlocking tool"
Thanks in advance
Click to expand...
Click to collapse
http://en.miui.com/unlock/download_en.html
Download Mi Unlock, BUT....
http://en.miui.com/thread-202290-1-1.html
Here you can read that :
2. The unlocking procedure only supports MIUI China developer version (6.1.12 or later version) currently. MIUI China stable version will get supported in future updates
Click to expand...
Click to collapse
So we need to wait for the dev. rom for redmi 3.
According to this thread should be out anytime soon :
http://en.miui.com/thread-228054-1-1.html
BUT....
Update*
[Developer rom has been out for awhile and the latest version is now 6.2.24. However, it is currently not due for public release. Fret not as even with the latest developer rom, boot loader cannot be unlock yet as Redmi 3 has yet to be integrated into MIUI Unlock System.
Click to expand...
Click to collapse
No unlock yet =(
I am a bit confused about this locking. On most phones i had i initially booted them into fastboot then flashed TWRP then via TWRP flashed custom roms (zips). So which part did they lock ? Fastboot so you cannot flash TWRP or the bootloader itself(TWRP,CWM,etc) (theoretically you could flash it but not access) ? Thanks for clarifying for me.
csman said:
I am a bit confused about this locking. On most phones i had i initially booted them into fastboot then flashed TWRP then via TWRP flashed custom roms (zips). So which part did they lock ? Fastboot so you cannot flash TWRP or the bootloader itself(TWRP,CWM,etc) (theoretically you could flash it but not access) ? Thanks for clarifying for me.
Click to expand...
Click to collapse
You can't flash anything at will with it locked. Even in Fastboot it won't work unless signed by Xiaomi. And they are not giving everyone unlock codes. Mainly if you mention you want to remove miui. Also if you are not active in their forums they won't do it.
zelendel said:
You can't flash anything at will with it locked.
Click to expand...
Click to collapse
Nonsense. You can flash (unofficial) full roms using fastboot in download mode, no problem at all...
Only flashing in fastboot mode (recoverys, xposed, custom kernels) wouldn't work with locked bl.
I also don't like the idea of locked bootloaders but, well... you do it once, use unlocked roms and are happy with it. not big of a deal, so stop whining...
Had it on my Razr i, now on the Redmi 3. Got my approval for it after not even 2 weeks at the beginning of february, now waiting for the suitable dev rom to unlock.
Just let it all settle a bit, the device by now is just too fresh out...
zelendel said:
They locked the bootloader for a reason.
Click to expand...
Click to collapse
The reason was to prevent resellers from preinstalling tampered roms.
current account is not bound to this device. this error I get when I try to unlock bootloader of redmi 3S. what I do now??
update latest version of miui and check
same
same problem with me i am on beta global.. please tell me if u find any solution
varungajjarrock said:
same problem with me i am on beta global.. please tell me if u find any solution
Click to expand...
Click to collapse
After getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
joe34 said:
after getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
Click to expand...
Click to collapse
can i try in this one week or i should not try?
varungajjarrock said:
can i try in this one week or i should not try?
Click to expand...
Click to collapse
Read what I said again. I think it's clear.
joe34 said:
After getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
Click to expand...
Click to collapse
Got permissions on the 15th, it's now the 23rd. Still can't unlock. Going to try on the 25th again.
ZETROzky said:
Got permissions on the 15th, it's now the 23rd. Still can't unlock. Going to try on the 25th again.
Click to expand...
Click to collapse
Are you logged in with that account on your phone? Is backup phone turned on? Is find device turned on? (Tinker with the settings of the miui account. I got permission after 3 days of submitting a request and immediately unlocked the bootloader)
bekcicandrej said:
Are you logged in with that account on your phone? Is backup phone turned on? Is find device turned on? (Tinker with the settings of the miui account. I got permission after 3 days of submitting a request and immediately unlocked the bootloader)
Click to expand...
Click to collapse
Yes, yes and yes. I tried yesterday, nothing.
joe34 said:
After getting permission, you cannot unlock your bootloader immediately. You have to wait a bit, say, 1 week before you can unlock.
Click to expand...
Click to collapse
bekcicandrej said:
Are you logged in with that account on your phone? Is backup phone turned on? Is find device turned on? (Tinker with the settings of the miui account. I got permission after 3 days of submitting a request and immediately unlocked the bootloader)
Click to expand...
Click to collapse
it seems that u didnt changed ur rom from a long time and ur account got bind with ur phone before getting permission so that u can unlock after getting req immediately.. am i correct?
Still. Not. Binding.
Still. Can't. Unlock.
Sent from my land using XDA Labs
varungajjarrock said:
it seems that u didnt changed ur rom from a long time and ur account got bind with ur phone before getting permission so that u can unlock after getting req immediately.. am i correct?
Click to expand...
Click to collapse
Nope. So I got the phone. Created the miui profile, saw the Chinese apps and decided to find a way to get ride of them. Found out 2 days later that I need to unlock, applied for unlocking. 3 days later got permission. 2h later unlocked via unlocking tool. This was 8 months ago
Now I've noticed that you need to enable oem unlocking in the dev options, before going into fastboot to unlock
But one more thing comes, that I did and that's fully entering all the info on my profile (security questions etc)
And yes my miui account is bound to this​ phone, when I install miui it doesn't even ask for a account just a password
Finally unlocked it today.
Sent from my land using XDA Labs
ZETROzky said:
Finally unlocked it today.
Click to expand...
Click to collapse
Did anything special? And how much days it take?? And u were trying daily?
Have been reading a lot about this and have tried every method explained. My conclusion is, it's based on luck. XIOMI screwed the b/l unlocking method like many things and you need to be lucky to smoothly unlock it.
I assume you have already followed every single rule like waiting for some days before trying and connecting the phone and unlocking tool with same account, disabling lock screens or that find device thing they say and many others with no luck.
I believe since redmi 3s is a dual sim so if you are using another simcard your best bet is to try making a new account with that number and try the whole process again. About waiting... well, many have been waiting for months, so don't much from waiting and retrying luck.
Hopefully we will get some unofficial unblocking method someday, like note 3 has.
---------- Post added at 09:23 PM ---------- Previous post was at 09:22 PM ----------
ZETROzky said:
Finally unlocked it today.
Sent from my land using XDA Labs
Click to expand...
Click to collapse
Please tell how you were able to unlock. Were you on global stable? Which trick worked for you?
I have a Special Edition (pro prime 152mm) with the Special Edition Dev ROM.
I got the unlock approval 8 days ago, I can locate my device using MI account but the binding doesn't work. (Settings>Additional settings>Developer Options>Mi Unlock Status>Add account and device) Please retry within 1 or 2 minutes again and again and again...
I tried the tool in version 1.0.1225.2, 1.1.03171.1 and last 2.2.406.5.
Still no binding possible.
I have got my permission 1 day before
it is still not unlocking
what to do now??
1+2=3 said:
I have got my permission 1 day before
it is still not unlocking
what to do now??
Click to expand...
Click to collapse
Enable Dev settings by clicking 5 times onto MIUI Version number in settings then go in other settings > des settings > lock status and try to bind
1+2=3 said:
I have got my permission 1 day before
it is still not unlocking
what to do now??
Click to expand...
Click to collapse
1 day before? Then wait a week before trying to bind device and unlock your bootloader.
My BL is not unlocking as the account is not binding in the dev setting>unlock status and therefore unlocking stops at 99%.
If anyone facing the error 86012 had later unlocked their BL later, please tell us clearly what did you do. "I just need to know that is there someone who had unlocked without binding their account."
Sent from my land using XDA Labs
Option is greyed out on mine ... it's a Google Store phone. purchased from Google specifically so I would be able to unlock.
And I can't. I'm p*ssed. Very unhappy.
Are you saying you can't check on the OEM unlocking option under Developer Options?
I just checked and I was able to do it.
Yes, that's exactly what I'm saying. It's greyed/disabled.
and per Google, I have a VZW branded phone.
So now it's going back. $900 wasted.
_litz said:
and per Google, I have a VZW branded phone.
So now it's going back. $900 wasted.
Click to expand...
Click to collapse
Did you buy from Verizon or Google store?
dubt17 said:
Did you buy from Verizon or Google store?
Click to expand...
Click to collapse
Google Store. They are selling 3 models of Pixel 4 : unlocked, VZW locked, and Google Fi.
They sent me a VZW one.
I was able to unlock mine no problem. I bought the unlocked version from Google even though I'm on Verizon. I put my Verizon sim in, skipped all the setup, ticked to allow oem unlocking, rebooted to bootloader and unlocked no problem.
That's a bummer yo.
_litz said:
Google Store. They are selling 3 models of Pixel 4 : unlocked, VZW locked, and Google Fi.
They sent me a VZW one.
Click to expand...
Click to collapse
Are you just going to return and cancel or are they exchanging it for you?
That sucks..
For those who unlock. Do you use something for Google Pay? (That magisk thing?)
Also...do you know if device theft protection still works if stolen?
I recently tried to root my Pixel 2 but then I rolled back because I wasn't sure of these two things.
Sent from my Pixel 4 using Tapatalk
does this mean we can flash magisk root if we unlock the bootloader?
thesebastian said:
That sucks..
For those who unlock. Do you use something for Google Pay? (That magisk thing?)
Also...do you know if device theft protection still works if stolen?
I recently tried to root my Pixel 2 but then I rolled back because I wasn't sure of these two things.
Sent from my Pixel 4 using Tapatalk
Click to expand...
Click to collapse
I haven't unlocked in years but I do read about it. I think you only need Magisk if you're going to root. Bootloader unlock only needs a kernel to bypass the unlock check. But since there are no kernels yet you can't use GP if you unlock the P4.
Until Google releases the factory images for the P4, it may be hard to install Magisk. Without TWRP, we need to use the boot image modification method. Unless you are competent enough to find and extract the boot.img from your phone, you will have to wait until the factory images are released to get your hands on it.
So while it is probably technically possible to root right now, the ave person that isn't an Android OS expert probably won't have the technical skills to do it.
To those asking ... yes, I bought from google store. They sent me the verizon variant instead of the unlocked variant.
re: google pay/etc (anything requiring safetynet), Magisk can provide root, and its Magiskhide component can hide that root from SafetyNet. Installing Xposed inside Magisk, however, cannot be hidden.
re: installing magisk if you unlock the bootloader - that's a yes.
Anyone in here extracted the boot.img from the factory image yet?
I'm on a mac right now so I was hoping to just download someone elses.
My OEM unlock is available. I'm waiting for root. The only thing I want right now is hotspot. I was hoping that since it's an unlocked phone that it would work straight out of the box. I've been with LG since the G4 and I've always bought mine unlocked and the hotspot works without having to go through Verizon and pay for the subscription. I'm on the old grandfathered unlimited data plan. I'd hate to have to return this phone and go with the G8 but I don't have internet where I live and I have to have hotspot.
Spookymyo said:
My OEM unlock is available. I'm waiting for root. The only thing I want right now is hotspot. I was hoping that since it's an unlocked phone that it would work straight out of the box. I've been with LG send the G4 and I've always bought mine unlocked and the hotspot works without having to go through Verizon and pay for the subscription. I'm on the old grandfathered unlimited data plan. I'd have to have to return this phone and go with the G8 but I don't have internet where I live and I have to have hotspot.
Click to expand...
Click to collapse
You know w have root right? You don't need a custom recovery when you can use the patched boot method from magisk along with fastboot.
cntryby429 said:
You know w have root right? You don't need a custom recovery when you can use the patched boot method from magisk along with fastboot.
Click to expand...
Click to collapse
?? ...I did not... I'll do a search
cntryby429 said:
You know w have root right? You don't need a custom recovery when you can use the patched boot method from magisk along with fastboot.
Click to expand...
Click to collapse
Would you mind sharing your unpatched boot.img?
Shponglized said:
Would you mind sharing your unpatched boot.img?
Click to expand...
Click to collapse
You can get it with the system images that are available from Google. It'd be hesitant to give you the one I downloaded in case you have one of the other 2 variants of the October release (this assumes that the boot.img's are even different which in not sure).
I got a tester device so it was already unlocked. I'm just waiting for TWRP before I start messing with it.
OK so I'm posting this here because I'm eventually going to root and tweak many things (as I usually do) but this is my first pixel or Google phone of any kind.
A little background on myself. I'm always running a rooted phone (except for the last week or so) and have always ran an HTC device on the sprint network. I've done a bit of work on theming and creating skins in the past (it's been a while) but I've noticed that there isn't much need for that now that pretty much everything I'd create can be done easily with an Xposed or Magisk module.
Reason for this post.. With my current device being the Pixel 4 (not XL) that I bought from the sprint store (paid in full at time of purchase) I now have a device that's running Android 10 with no twrp and no custom rom. I want to go ahead and root but don't really need to with the exception that I want to access mobile hotspot but I don't even see a way to do that yet with the currently available Magisk modules.
I can figure out the current technique to get root access but thinking of waiting until custom recovery and roms are available but how will that be affected by carrier specific devices?
/rant
Is your bootloader locked or unlocked? You'll need to unlock that first then you can patch the boot.img file with magisk to root.
inclusive said:
Is your bootloader locked or unlocked? You'll need to unlock that first then you can patch the boot.img file with magisk to root.
Click to expand...
Click to collapse
Greyed out can't toggle
knightwolf123 said:
Greyed out can't toggle
Click to expand...
Click to collapse
I don't know if you'll be able to do it on locked carrier versions. Magisk requires you to patch that boot image in order to root unless there's another method.
I got my answer... ?
knightwolf123 said:
I got my answer...
Click to expand...
Click to collapse
Are you sure they actually understand you mean there bootloader?
vonDubenshire said:
Are you sure they actually understand you mean there bootloader?
Click to expand...
Click to collapse
The phone must be SIM unlocked before the OEM bootloader unlock option will become active. If Sprint won't SIM unlock the phone for 50 days, then there is nothing he can do.
It's becoming more and more common for carriers to SIM lock all their phones and only unlock them after an extended period of time after activation. Verizon won't SIM unlock for 60 days. They do this to prevent unsold stock from being stolen and sold by the thieves.