Related
Good evening all!
Question I have is simply when does everyone suspect a single-click Root might come along that doesn't wipe the phone's memory? I've already had to reset my phone once (because of Verizon) and hoping to not have to do it again for awhile (restoring 12k SMS takes awhile). I know many phones in the past have eventually gotten a one-click method that doesn't wipe the phone and wondering how feasible it is that we'll see one here in a short amount of time.
Thanks in advance, all! Keep up the good work.
Rooting doesn't wipe the device, the problem is that you have to unlock the device first, which will.
champers said:
Rooting doesn't wipe the device, the problem is that you have to unlock the device first, which will.
Click to expand...
Click to collapse
Can I ask why? Many devices have had single-click roots that retained locked bootloaders. A reference would be my Atrix 4G. Motorola locked the bootloader fairly hard and I never unlocked mine, but I still managed to root the device using Z4Root, without a whipe. I downloaded the app, opened it, and clicked the "Root" button. I restarted the phone and the phone was rooted with SuperUser and BusyBox installed.
hotleadsingerguy said:
Can I ask why? Many devices have had single-click roots that retained locked bootloaders. A reference would be my Atrix 4G. Motorola locked the bootloader fairly hard and I never unlocked mine, but I still managed to root the device using Z4Root, without a whipe. I downloaded the app, opened it, and clicked the "Root" button. I restarted the phone and the phone was rooted with SuperUser and BusyBox installed.
Click to expand...
Click to collapse
Those are usually hacks that take advantage of security flaws found in the OS or other software... the same way that malware authors find holes in Windows and write software to take advantage of it to exploit your computer. The bugs that allow you to root without unlocking are the same kind of bugs that has given Microsoft a bad reputation for security over the years, and naturally Google doesn't want security flaws in Android so they try to minimize them and fix any that are found.
A hole might be found in ICS eventually.
phazerorg said:
Those are usually hacks that take advantage of security flaws found in the OS or other software... the same way that malware authors find holes in Windows and write software to take advantage of it to exploit your computer. The bugs that allow you to root without unlocking are the same kind of bugs that has given Microsoft a bad reputation for security over the years, and naturally Google doesn't want security flaws in Android so they try to minimize them and fix any that are found.
A hole might be found in ICS eventually.
Click to expand...
Click to collapse
I wasn't really asking about the ethical use of such things...just whether anyone could see it being feasibly possible in the near future. Then again, if anyone knows of a way to restore 12k SMS in 5 minutes I'm open to unlocking/rooting the old-fashioned way.
By the way, even the way unlocking/rooting is accomplished now is considered a "hack". Using ADB to unlock/root the phone isn't the way it's meant to be used. ADB stands for Android Debugging Bridge...it's meant to debug, not crack open the bootloader.
hotleadsingerguy said:
I wasn't really asking about the ethical use of such things...just whether anyone could see it being feasibly possible in the near future. Then again, if anyone knows of a way to restore 12k SMS in 5 minutes I'm open to unlocking/rooting the old-fashioned way.
Click to expand...
Click to collapse
Sorry about that, I didn't mean to imply any ethics here. I was just trying to answer the question about why there isn't a one-click root. I may have misinterpreted your "why?" question.
I don't see that happening any time soon. It's so effortless to unlock the bootloader that why would anyone waste their time trying to find a workaround.
jhuynh said:
I don't see that happening any time soon. It's so effortless to unlock the bootloader that why would anyone waste their time trying to find a workaround.
Click to expand...
Click to collapse
I wouldn't call re-configuring everything effortless lol I'd rather spend 45 minutes unlocking and rooting than spend 5 minutes doing it and another hour getting it set up...again. Restoring all of your stuff can be a pain if you don't have it empty. It downloads the apps but it doesn't set them up.
Have you tried restoring a massive number of text messages? I had to delete half of mine simply because it took well over an hour and a half to restore the first time and I had to reset the phone anyway. It's extremely time-consuming to have to clear out the phone. I'd say it was a strong 2 1/2 or 3 hours from start to finish yesterday to do it (and yes, there was a reason I couldn't unlock+root at the same time).
I've flashed a rom, kernel, radio, some UI tweaks, and I think I'm done with all that and reached a point I'm happy with. Should I relock? Will I lose root/my tweaks by doing that? What are the security risks with keeping the bootloader unlocked? I don't use google wallet or anything else super personal/detrimental if in the wrong hands, but I do have a chasebank app (that requires login every use), the standard gmail integration, and a sensitive photo here and there. I understand that I'll have to unlock it again (and deal with the wipe) if I want to do more serious customizing, but at this point I'm more curious about the pros/cons of keeping the bootloader unlocked during day to day use. In terms of used networks, I connect to my home wifi, and the occasional open wifi when out and about, but usually I forget/don't realize and just keep it on 3g/4g. I also tether every so often. Don't know which of those makes me more vulnerable than others. I live in a pretty unpopulated area so I'm not too concerned about all this, but I am curious.
Don't relock...its pointless if you're not stock
No reason to re-lock. You'll just have to do a data wipe the next time you want to change anything.
Sent from my Galaxy Nexus using Tapatalk
There truly is no reason to relock, there is no difference/point.
I understand having to unlock it again would mean another wipe, as mentioned in the OP. I'm fine with that.
All of these posts conflict with this post from this recent Q&A thread. Which is correct? Why would that user post such a thing if it isn't true?
bfroehlich said:
I would suggest locking it if you plan on doing anything remotely sensitive on your device, Google Wallet, corporate email, naked pics of your spouse, etc.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
not saying it's the case here, but a lot of people just think they know something.
@JBQ said in android-building something like
-However, if you're keeping your bootloader unlocked at all times
(which is a bad idea) and you're running an official build already,
you can flash a newer one without wiping data and that'll work fine.
Note that you can only move forward, not back. Be careful, though,
it's very easy to wipe data by accident when doing that, and the
default script does that.
Click to expand...
Click to collapse
he didn't go any further on that. source
perhaps it's a matter of privilege escalation?
relocking the bootloader help security
relocking the bootloader will help defend against "Evil Maid Attacks" amongst other things.
More background info available if you search for "evil maid goes after WhisperCore
why we need a securable bootloader"
(I'd post a link but account is too new)
Yes it will help with security. But by that point, you might as well get one of the "android lost" apps and remotely brick your phone if it's stolen, imo.
As a custom ROM user, you're responsible for your own updates. Which means you can expect to be reflashing stuff in the future. Thus, I don't think it's worth it to have your data wiped again and again.
(But then again, I flash stuff like crazy, so that might be bias on my part.)
It'd be kinda funny to to lock your bootloader for security after flashing completely custom firmware from some unknown source bit of a contradiction.
No.
In another week or so you are gonna be browsing xda and see a new kernel/rom/theme that you like and you're gonna think well I can't flash it coz for some reason I locked my bootloader and I don't want to wipe my sdcard coz I have stuff I want there.
A few days later you are gonna say f*ck it and you are gonna unlock your bootloader again and lose all your sdcard data.
Why?
Because you may not know it yet but you are now a crackflasher. You tried it once and that's all it takes to get addicted.
As others have said, there is only added security if you lose your phone and at that point if there is extremely sensitive data and you can't get it back, you can just remotely wipe it using an app from the marketplace.
Note: said app must be installed before you lose your phone
Sent from my GT-I9100 using xda premium
joshnichols189 said:
As others have said, there is only added security if you lose your phone and at that point if there is extremely sensitive data and you can't get it back, you can just remotely wipe it using an app from the marketplace.
Note: said app must be installed before you lose your phone
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Note: Said app not doesn't necessarily have to be installed before you lose your phone because you can go to Play Store, remotely install the app, and issue the commands for tracking. (But if you want it to wipe, I believe you have to give it administrative permissions, which does require you to have it installed before and set it up that way). Maybe Avast! even lets you wipe without administrative positions (haven't tried yet).
In order for you data to be secure in case of theft/loss, locking the bootloader is not enough. You need to turn off USB debugging in settings. Otherwise, if someone finds a GN, he can access all the files on it anyway. Bootloader locked or not.
It may be that mirror link is protected with the DRM keys?
Since I had my xperia unlocked mirror link does not work anymore, it also did not work when I had the unlock undone. Unfortunately, I have read to late save the TA partition
Although MirrorLink doesn't necessarily seem to enforce DRM for certification (as opposed to Miracast for example), valid keys seem to be a requirement on the device. I.e. MirrorLink and Miracast stop working after unlocking the bootloader.
And it looks as if it no longer get to work?
Is it possible to send the unit to Sony to have it recover (with costs, unless Sony is so accommodating ? I mean whether it is in principle possible.
Hello @Sully99,
Unfortunately Mirorlink and Miracast will not work without the DRM keys, and there is nothing you can do about it.
However, Throw and DLNA still works so you can use that to view content from your phone on a TV.
Keelah se'lai,
GethPrime
The good is nothing, I would like to connect the device to my Alpine INE-W928R, but since now I get the error Message "incompatible USB Device".
Not even the manufacturer is able to reset it? That can only be a joke, you make a mistake and receives a life sentence? This is worse than in a dictatorship.
Sully99 said:
The good is nothing, I would like to connect the device to my Alpine INE-W928R, but since now I get the error Message "incompatible USB Device".
Not even the manufacturer is able to reset it? That can only be a joke, you make a mistake and receives a life sentence? This is worse than in a dictatorship.
Click to expand...
Click to collapse
Hello @Sully99,
It's due to content protection and to protect Sonys propriatry technology.
Bare in mind that you're the cause of this, as bootloader unlock erases the DRM keys and this has been known for years.
Keelah se'lai,
GethPrime
Sony could (and should) definitely make it clearer that these core functions will be permanently disabled though.
Certain pre-loaded content on your device may also be inaccessible due to the removal of DRM security keys.
http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
This is in no way a sufficient warning and I wasn't aware of this as well after reading several guides, I was just lucky that I had backed up the keys before unlocking.
GethPrime said:
Hello @Sully99,
It's due to content protection and to protect Sonys propriatry technology.
Bare in mind that you're the cause of this, as bootloader unlock erases the DRM keys and this has been known for years.
Keelah se'lai,
GethPrime
Click to expand...
Click to collapse
This is going to be and I am also aware that it was a fault of mine, it is no wonder that one time something happened when one thinks of the amount of information available only on Android, ios ... and so on.
I had only one Android Tablet which there was previously no talking and that's why I thought it is not a problem here. The biggest joke is that I would not at all have to unlock it for what I wanted to do since I had to rely on false statements
I understand that the authors want to protect their work but that they must not equal disable an entire function (which in particular can not be made here again)
Sully99 said:
This is going to be and I am also aware that it was a fault of mine, it is no wonder that one time something happened when one thinks of the amount of information available only on Android, ios ... and so on.
I had only one Android Tablet which there was previously no talking and that's why I thought it is not a problem here. The biggest joke is that I would not at all have to unlock it for what I wanted to do since I had to rely on false statements
I understand that the authors want to protect their work but that they must not equal disable an entire function (which in particular can not be made here again)
Click to expand...
Click to collapse
Hello @Sully99,
The reason why It's disabled permanently is due to the deleted DRM keys which can not be recreated without a backup. These DRM keys are used to encrypt the Miracast content, therefore it's disabled if you unlock the bootloader.
Keelah se'lai,
GethPrime
GethPrime said:
Hello @Sully99,
The reason why It's disabled permanently is due to the deleted DRM keys which can not be recreated without a backup. These DRM keys are used to encrypt the Miracast content, therefore it's disabled if you unlock the bootloader.
Keelah se'lai,
GethPrime
Click to expand...
Click to collapse
The keys are still in the media Files, why must deactivate what else then except the media even if the DRM keys of the device are gone?
I can therefore only hope that it maybe is in a Custom Rom which allows another alternative to working with my Alpine, because the bootloader unlocked anyway and the DRM protection is gone all does not matter anyway. :crying:
I'm having a similar issue, but mine's a little different. I had a brand new phone, rooted and with DRM keys backed up (TA partition, etc.), and I unlocked the bootloader. Afterwards, I installed LiquidSmooth and there was an option to do screen mirroring, and it worked perfectly, perhaps even better than when I was stock. Now, I've wiped that and installed SlimKit instead (after some testing, I prefer the stock based firmware), and the screen mirroring will no longer connect. Does the custom rom not require DRM keys to screen mirror?
Edit: Can't figure out how to delete, but I think I can just restore my DRM keys and go from there to miracast on the stock rom.
DRM problems
If you get here you are interested in this:
https://www.change.org/p/sony-corpo...er-unlocking-problem-with-the-xperia-z-series
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
greves1 said:
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
Click to expand...
Click to collapse
You can search that but might as wipe in the meantime. Get yourself a working phone.
bobby janow said:
You can search that but might as wipe in the meantime. Get yourself a working phone.
Click to expand...
Click to collapse
Thanks for the reply. Going through the post-wipe setup now. Grrrr. It's just that I entered the password a bunch of times, and it always worked. Just on reboot from recovery it didnt. Now I'm afraid to go back into twrp...
Anyone know if this could be caused by some android security feature that doesnt like systemless root, xposed, etc.
greves1 said:
Hi all,
bit of an emergency here. I am running rooted Chroma rom, just went into twrp to backup my EPS, and upon reboot it is saying I need to enter my password. I have done this several times. Now, it keeps saying the password is incorrect, and after the 5th time, there is no option to reset it! Help please!! Don't feel like wiping my phone again...
Click to expand...
Click to collapse
I assume this is the same problem as the Nexus 6P. You need to disable the security before making a TWRP backup. The fix is:
After restoring the nandroid, boot into twrp and then delete /data/sytem/locksettings.db. If that doesn't fix it, delete the locksettings.db-shm and locksettings.db-wal in the same location. If that doesn't fix it either, delete gatekeeper.password.key and gatekeeper.pattern.key in the same location.
Click to expand...
Click to collapse
KennyG123 said:
I assume this is the same problem as the Nexus 6P. You need to disable the security before making a TWRP backup. The fix is:
Click to expand...
Click to collapse
Thanks for this fix. I'll keep it in mind next time. My broader question is now about security in general, since there seems to be a way to remove security from our roms?? For example, if someone got ahold of your phone, couldnt they just follow these steps to get in? Is this just a side-effect of unlocking the phone that is unavoidable? If I'm missing something about how to maintain security in the unlocked/rooted environment, please let me know. I've looked around but I haven't found any great guides for best practices regarding nandroids/security, etc. Thanks all!
greves1 said:
Thanks for this fix. I'll keep it in mind next time. My broader question is now about security in general, since there seems to be a way to remove security from our roms?? For example, if someone got ahold of your phone, couldnt they just follow these steps to get in? Is this just a side-effect of unlocking the phone that is unavoidable? If I'm missing something about how to maintain security in the unlocked/rooted environment, please let me know. I've looked around but I haven't found any great guides for best practices regarding nandroids/security, etc. Thanks all!
Click to expand...
Click to collapse
Rooting is in itself the biggest security risk. This is why carriers are working with manufacturers to make many phones fully locked and unrootable. Our main security expert Jcase does not use a rooted phone. He recommends if you need to root, go ahead, make the changes you want, then quickly unroot. So sure, if someone stole your phone they could follow that procedure to get into it. They could also just force a fresh stock version on it to wipe everything. Security and locks are meant to keep out honest people and slow down the dishonest.
KennyG123 said:
Rooting is in itself the biggest security risk. This is why carriers are working with manufacturers to make many phones fully locked and unrootable. Our main security expert Jcase does not use a rooted phone. He recommends if you need to root, go ahead, make the changes you want, then quickly unroot. So sure, if someone stole your phone they could follow that procedure to get into it. They could also just force a fresh stock version on it to wipe everything. Security and locks are meant to keep out honest people and slow down the dishonest.
Click to expand...
Click to collapse
Just so I'm clear, the only thing keeping a stock phone safe is that when its locked, it can't be unlocked/rooted because the option to allow oem unlocking/adb connections are not (or should not be) checked in the developer options, is that correct? From what you're saying, as long as those two boxes are checked, there is essentially nothing stopping someone from wiping out your password and getting into your device. I'd love to run unrooted, but would adaway still have an effect? I'm thinking that the definitions are already applied, so maybe it would work unrooted. But cf.lumen, which I love and can't find the same functionality anywhere else, seems to always "enable interactive shell" on boot. Would this work unrooted? But again, as long so you're doing all this stuff, you can't lock your bootloader again, can you? Or can you lock it on a stock rom with the kind of modifications I'm talking about. I read that locking bootloader while having a custom rom loaded can cause a brick, although I'm not quite sure why. Couldn't you just always get into fastboot to unlock it again?
greves1 said:
Just so I'm clear, the only thing keeping a stock phone safe is that when its locked, it can't be unlocked/rooted because the option to allow oem unlocking/adb connections are not (or should not be) checked in the developer options, is that correct? From what you're saying, as long as those two boxes are checked, there is essentially nothing stopping someone from wiping out your password and getting into your device. I'd love to run unrooted, but would adaway still have an effect? I'm thinking that the definitions are already applied, so maybe it would work unrooted. But cf.lumen, which I love and can't find the same functionality anywhere else, seems to always "enable interactive shell" on boot. Would this work unrooted? But again, as long so you're doing all this stuff, you can't lock your bootloader again, can you? Or can you lock it on a stock rom with the kind of modifications I'm talking about. I read that locking bootloader while having a custom rom loaded can cause a brick, although I'm not quite sure why. Couldn't you just always get into fastboot to unlock it again?
Click to expand...
Click to collapse
Pfew...so many questions...there are always vulnerabilities out there that hackers can find..like Stagefright...but a rooted phone is the most vulnerable. So having a phone with a locked bootloader and unrooted is the best security...still not guaranteed against every possible thing. But it is the best...now what are you trying to protect? Your data...or someone being able to wipe and use the phone as their own? All you can do really is try to protect from a phone being hacked remotely...and a rooted phone is like leaving the safe door open. But if someone steals your phone, there are always nefarious ways to make it usable.
KennyG123 said:
Pfew...so many questions...there are always vulnerabilities out there that hackers can find..like Stagefright...but a rooted phone is the most vulnerable. So having a phone with a locked bootloader and unrooted is the best security...still not guaranteed against every possible thing. But it is the best...now what are you trying to protect? Your data...or someone being able to wipe and use the phone as their own? All you can do really is try to protect from a phone being hacked remotely...and a rooted phone is like leaving the safe door open. But if someone steals your phone, there are always nefarious ways to make it usable.
Click to expand...
Click to collapse
Yeah, sorry for the wall of questions. I am just trying to wrap my head around some of these issues. At the end of the day, I don't really keep sensitive data on the phone, although it would not be good if a bad actor got into my gmail, for instance. I suppose I should migrate the last of my sensitive accounts to a secondary email, so no password resets could be initiated from a stolen phone. It's always a tradeoff between convenience and security I know. It's also a little worrysome that simply unlocking the phone activates it for androidpay. An unlocked phone stolen out of someone's hand is essentially the same as stealing all the credit cards in their wallet. It would be nice if android pay allowed an additional fingreprint/pin/password to make the transaction. Anyway, I'm now taking my own thread way off topic. Thanks for the insights though.
greves1 said:
Yeah, sorry for the wall of questions. I am just trying to wrap my head around some of these issues. At the end of the day, I don't really keep sensitive data on the phone, although it would not be good if a bad actor got into my gmail, for instance. I suppose I should migrate the last of my sensitive accounts to a secondary email, so no password resets could be initiated from a stolen phone. It's always a tradeoff between convenience and security I know. It's also a little worrysome that simply unlocking the phone activates it for androidpay. An unlocked phone stolen out of someone's hand is essentially the same as stealing all the credit cards in their wallet. It would be nice if android pay allowed an additional fingreprint/pin/password to make the transaction. Anyway, I'm now taking my own thread way off topic. Thanks for the insights though.
Click to expand...
Click to collapse
For most phones that have fingerprint security Android Pay can be set up that way. I won't use it anyway because it would be crazy to hand a waiter your unlocked phone, or to have to follow him to the register. It would only be useful to me in the supermarket but I am carrying a credit card anyway. But that is one thing people forget, rooting a phone means removing the main security.
KennyG123 said:
For most phones that have fingerprint security Android Pay can be set up that way. I won't use it anyway because it would be crazy to hand a waiter your unlocked phone, or to have to follow him to the register. It would only be useful to me in the supermarket but I am carrying a credit card anyway. But that is one thing people forget, rooting a phone means removing the main security.
Click to expand...
Click to collapse
N5X and android pay seems to tell me to just "unlock your phone" and hold it close to the reader. No need for an additional fingerprint. And no option to require this in settings...
greves1 said:
N5X and android pay seems to tell me to just "unlock your phone" and hold it close to the reader. No need for an additional fingerprint. And no option to require this in settings...
Click to expand...
Click to collapse
Yes, that should get you to the authorization screen and then if you have fingerprint set up should ask you for the fingerprint to authorize. Android Pay also now works on phones without fingerprint sensors so that is why they provide those simple instructions. Final authorization instructions will appear on your screen.
KennyG123 said:
Yes, that should get you to the authorization screen and then if you have fingerprint set up should ask you for the fingerprint to authorize. Android Pay also now works on phones without fingerprint sensors so that is why they provide those simple instructions. Final authorization instructions will appear on your screen.
Click to expand...
Click to collapse
Ah, great to know. Thanks.
greves1 said:
Ah, great to know. Thanks.
Click to expand...
Click to collapse
Unfortunately I can't test that theory since I am on a custom ROM and also Xposed. But everything I read says it should utilize the fingerprint if available.
KennyG123 said:
Unfortunately I can't test that theory since I am on a custom ROM and also Xposed. But everything I read says it should utilize the fingerprint if available.
Click to expand...
Click to collapse
Real word use shows that android pay does not ask for an additional fingerprint at the time of use. It's just as the instructions say, as long as your phone is unlocked at the time it is held up to the scanner, androidpay will work. I kind of wish they allowed for the additional security of an at-scan fingerprint read, but oh well. I have yet to test if the password/pin can be removed by the methods discussed in this thread, and androidpay working after defeating this security. If it does, then this is obviously a major security vulnerability of having an unlocked phone and using androidpay at the same time. Probably not more dangerous in terms of protecting against CC thieves, since they can just swipe a card stolen from your wallet at a terminal, but you probably wouldn't want to keep too many cards on your phone. Again, I haven't tested this out, if a fingerprint is still required to get in after a password database defeat, but someone should do this test.
If you have your phone lost or stolen just cancel your cards as if it happened to your wallet. Simple no?
Hi all,
My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.
I've contacted T-Mobile. They've given the green light on their end to unlock.
When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."
TMobile is saying there is nothing they can do, and google is telling me the same thing as well.
Any ideas? Just looking to get this device back to Android 12.
AwkwardUberHero said:
Hi all,
My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.
I've contacted T-Mobile. They've given the green light on their end to unlock.
When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."
TMobile is saying there is nothing they can do, and google is telling me the same thing as well.
Any ideas? Just looking to get this device back to Android 12.
Click to expand...
Click to collapse
What device unlock app?
What happens when you:
Connect to wifi.
Enable OEM Unlocking in developer options.
Download latest platform-tools
Run the fastboot command: fastboot flashing unlock
A second hand work phone Pixel 6 Pro that's already on 13. That phone has seen some **** in a very short time.
T-Mobile pushes the unlock to you. If you downloaded the app from the Play store, it's the wrong one. Using the sim unlock one in T-Mobile sim settings also doesn't seem to work.
Alekos said:
What device unlock app?
What happens when you:
Connect to wifi.
Enable OEM Unlocking in developer options.
Download latest platform-tools
Run the fastboot command: fastboot flashing unlock
Click to expand...
Click to collapse
It's connected to WiFi, but the oem unlocking item is greyed out.
I haven't tested running the command in fastboot yet. Was worried what would happen.
LLStarks said:
A second hand work phone Pixel 6 Pro that's already on 13. That phone has seen some **** in a very short time.
T-Mobile pushes the unlock to you. If you downloaded the app from the Play store, it's the wrong one. Using the sim unlock one in T-Mobile sim settings also doesn't seem to work.
Click to expand...
Click to collapse
They asked me to download the device unlock app from the app store. I did, and used it.
They said that they have approved the unlock on their end.
I'm quite confused. This is my first carrier locked pixel.
AwkwardUberHero said:
Hi all,
My work gave me a new phone with an issue. It's a pixel 6 pro, and the previous user has enrolled the device in the a13 beta. They sideloaded the OTA and didn't unlock the bootloader.
I've contacted T-Mobile. They've given the green light on their end to unlock.
When I use the device unlock app, it tells me that it is unlocked. When I check in the device settings thought, it tells me that "connect to internet or contact carrier for unlock."
TMobile is saying there is nothing they can do, and google is telling me the same thing as well.
Any ideas? Just looking to get this device back to Android 12.
Click to expand...
Click to collapse
If you get a second hand phone from work that has experimental beta software installed from a previous owner, which is clearly a massive issue for a work phone in several regards (security just one) why don't you just give it back and demand a new one? Not sure how your company acts, but mine would instantly seize that phone, there is not knowing what might have been installed on it, it might even be a non-genuine A13 build. It's simply a risk most companies would never take, at least if they have some credibility.
This is clearly not your problem to deal with. It's noble that you invest so much of your "free" time for this, but it's a waste of time imho. It's not your job to make that phone work properly. If it's not in a working, proper state at the moment of delivery from employer to employee, you need to demand a working model.
AwkwardUberHero said:
It's connected to WiFi, but the oem unlocking item is greyed out.
I haven't tested running the command in fastboot yet. Was worried what would happen.
Click to expand...
Click to collapse
If it's greyed out, the Bootloader is still locked. You'll need to contact them (either through your work or TForce) in order for them to unlock it. But corporate devices (from T-mobile) might have different policies on unlocking. Best to contact your IT Dept.
But as the @Morgrain has suggested, this phone should have been wiped and factory reset by your employer to a proper working state. It wasn't. That's concerning. Many of us have worked for companies who are, shall we say, less than competent, at IT. But it's 2022 - there's no excuse.
Alekos said:
If it's greyed out, the Bootloader is still locked. You'll need to contact them (either through your work or TForce) in order for them to unlock it. But corporate devices (from T-mobile) might have different policies on unlocking. Best to contact your IT Dept.
But as the @Morgrain has suggested, this phone should have been wiped and factory reset by your employer to a proper working state. It wasn't. That's concerning. Many of us have worked for companies who are, shall we say, less than competent, at IT. But it's 2022 - there's no excuse.
Click to expand...
Click to collapse
I was going to give it one last shot before trading it back in. TMobile said that they have set it to be unlocked on their end, and that factory resetting it and checking it again to see if the bootloader is allowed to be unlocked might be a solution.
I've flashed roms, rooted and such for many years, but I've never had one like this. If TMobile did flip the switch in their end for the permission to unlock the bootloader, then it should show this, even in a developer preview software build, right?
I doubt that factory resetting this and trying it again will do any good, but I guess it's worth a shot.
AwkwardUberHero said:
They asked me to download the device unlock app from the app store. I did, and used it.
They said that they have approved the unlock on their end.
I'm quite confused. This is my first carrier locked pixel.
Click to expand...
Click to collapse
Don't use the play store app. It doesn't work. The phone has a built in app. It doesn't work either.
The unlock doesn't need to be approved. It has to be pushed to your phone. Your phone will alert you that it's unlocked without doing anything. T-Mobile cannot be the one telling you it's unlocked. After that, you reboot and bootloader unlock should no longer be grayed out
You got a bad rep who doesn't know what they are doing.
Your IT also had no business giving you a phone this compromised.
To be clear - T-Mobile wouldn't unlock your bootloader or be able to toggle the OEM unlocking themselves, they would only make your phone carrier unlocked. It just so happens that on T-Mobile devices (and maybe some others but definitely not Verizon), that carrier-unlocking a phone permanently usually also makes it so that you can toggle OEM unlocking. It's also possible that corporate management of your phone prevents it from ever having the OEM Unlock toggle be ungrayed, but on the other hand, I would think they would have it locked down to where someone can't opt the phone into a Beta program, and it's also strange that T-Mobile would do, or attempt to do anything regarding the phone since you don't own it or pay for the phone service.
As several have said, it's not your phone, it's not your responsibility, I wouldn't even think your work would want you to be messing with it even though you're capable.
I would also add that unless your work has the capability to make their phones have OEM Unlocking ungrayed out, and re-grayed out at will, they'd never be able to fix the Android 13 DP/Beta situation themselves - they would have to go to T-Mobile et cetera, although after they fix it, I would expect them to want to toggle it back and make it so that no one else can toggle it again. I guess your work just doesn't manage their associate's phones very closely.
LLStarks said:
Don't use the play store app. It doesn't work. The phone has a built in app. It doesn't work either.
The unlock doesn't need to be approved. It has to be pushed to your phone. Your phone will alert you that it's unlocked without doing anything. T-Mobile cannot be the one telling you it's unlocked. After that, you reboot and bootloader unlock should no longer be grayed out
You got a bad rep who doesn't know what they are doing.
Your IT also had no business giving you a phone this compromised.
Click to expand...
Click to collapse
So, they approved the carrier unlock.
The app does that part. I've done that a few times. But, the oem unlock is still greyed out.
Morgrain said:
If you get a second hand phone from work that has experimental beta software installed from a previous owner, which is clearly a massive issue for a work phone in several regards (security just one) why don't you just give it back and demand a new one? Not sure how your company acts, but mine would instantly seize that phone, there is not knowing what might have been installed on it, it might even be a non-genuine A13 build. It's simply a risk most companies would never take, at least if they have some credibility.
This is clearly not your problem to deal with. It's noble that you invest so much of your "free" time for this, but it's a waste of time imho. It's not your job to make that phone work properly. If it's not in a working, proper state at the moment of delivery from employer to employee, you need to demand a working model.
Click to expand...
Click to collapse
Yes and no. Not everybody works for high security big bank or government. Depends on the employer and depends on the job for the employer.
One piece of good news is that it is VERY unlikely that its a non-original A13. After all, its locked still. That means that the build had to be signed by the appropriate keys in order to install.
roirraW edor ehT said:
To be clear - T-Mobile wouldn't unlock your bootloader or be able to toggle the OEM unlocking themselves, they would only make your phone carrier unlocked. It just so happens that on T-Mobile devices (and maybe some others but definitely not Verizon), that carrier-unlocking a phone permanently usually also makes it so that you can toggle OEM unlocking. It's also possible that corporate management of your phone prevents it from ever having the OEM Unlock toggle be ungrayed, but on the other hand, I would think they would have it locked down to where someone can't opt the phone into a Beta program, and it's also strange that T-Mobile would do, or attempt to do anything regarding the phone since you don't own it or pay for the phone service.
As several have said, it's not your phone, it's not your responsibility, I wouldn't even think your work would want you to be messing with it even though you're capable.
I would also add that unless your work has the capability to make their phones have OEM Unlocking ungrayed out, and re-grayed out at will, they'd never be able to fix the Android 13 DP/Beta situation themselves - they would have to go to T-Mobile et cetera, although after they fix it, I would expect them to want to toggle it back and make it so that no one else can toggle it again. I guess your work just doesn't manage their associate's phones very closely.
Click to expand...
Click to collapse
So, TMobile said for me to down load the device unlock app. I did that, and ran it. It told me it was carrier unlocked.
The OEM unlocking portion is greyed out in develope options though still, and saying to connect to the internet or contact my carrier. Which confuses me. If it's sim unlocked, then I should be able to unlock the bootloader, right?
AwkwardUberHero said:
So, TMobile said for me to down load the device unlock app. I did that, and ran it. It told me it was carrier unlocked.
The OEM unlocking portion is greyed out in develope options though still, and saying to connect to the internet or contact my carrier. Which confuses me. If it's sim unlocked, then I should be able to unlock the bootloader, right?
Click to expand...
Click to collapse
As I said, your work may have more control over your phone since it's their phone, not yours. They may have something in place that keeps OEM Unlocking disabled, no matter what. I'm just speculating, I don't know if that's the case. I really couldn't guess any further why it's still grayed out for you. I wouldn't even bother spending any further effort on it. If it happened to me, I would tell work about it and let them deal with it.
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.
Then again, so does Apple and Intune not being thorough enough.
LLStarks said:
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.
Then again, so does Apple and Intune not being thorough enough.
Click to expand...
Click to collapse
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?
Last attempt before I give up on it.
LLStarks said:
Google has an MDM problem if a Pixel can block bootloader unlocking but not betas.
Then again, so does Apple and Intune not being thorough enough.
Click to expand...
Click to collapse
I know with regards to non-phone Google things at the very large corporation I'm at - where we've used Google for everything (except for phones) for a decade - that some things that are under the control of our internal Google Admins in our IT department slip through and then later get corrected.
As regards to phones, I don't have a corporate phone, but they used to supply some Samsung models for a brief period where they experimented with allowing both iPhone and Android devices, but they stopped probably because it was just more work for them to manage both iPhone and Android devices. I can't speak as to whether they had the capability to keep people from unlocking their bootloader or keep folks from opting in to DPs/Betas, but that was also ~6 years ago.
AwkwardUberHero said:
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?
Last attempt before I give up on it.
Click to expand...
Click to collapse
If you can't toggle the OEM Unlocking (it's still grayed out), then you can't unlock the bootloader.
I mean, this kinda depends on whom you work for. Some companies that give out work phones choose Android as they can customize the build and can view the phone's usage. I can't remember if it was the FBI or the police somewhere who mentioned doing this exact thing in order to visibly track what is being done on these phones. So if your company is knowledgeable (which I suppose is a rarity nowadays, haha) and deals with some information that must be kept secure, then I would just confront someone in the IT department and ask them what the deal is "as the phone isn't running a stable and secure version of Android". Because if it's customized for phone usage tracking, then doing what you are doing could get you into some trouble.
Not worth taking such risks with something that isn't yours. Where I work in IT, people always mess with (and too frequently break) devices that they are borrowing - and then complain about having to pay $250 for cracking the display or destroying the case of a laptop that they are simply borrowing.
It seems that nobody reads the contracts that they are signing or has enough common sense to not destroy something that isn't theirs.
AwkwardUberHero said:
To be clear, if it is showing that it was approved in that app to be carrier unlocked, in theory, I could try and unlock the bootloader or no?
Last attempt before I give up on it.
Click to expand...
Click to collapse
To be fair, I would do anything and everything to unlock the device because I like messing with technology (even if it comes from work).
The Toggle is greyed out right - but is it on or off - because when the device is unlocked, the toggle will be greyed out (but toggled to the on position). When you boot into fastboot, does it say device state locked?
Do a factory reset in recovery mode and check again.
Alekos said:
To be fair, I would do anything and everything to unlock the device because I like messing with technology (even if it comes from work).
The Toggle is greyed out right - but is it on or off - because when the device is unlocked, the toggle will be greyed out (but toggled to the on position). When you boot into fastboot, does it say device state locked?
Do a factory reset in recovery mode and check again.
Click to expand...
Click to collapse
It's greyed out and off.
I haven't checked it in fastboot yet.