Related
I have a brand new sealed Samsung S9 SM-G960F/DS which is most probably Exynos variant however I couldn't find OEM Unlock after activating the developer tools. I've googled that and was surprised that this is a recent Samsung policy and as mentioned by most users they've waited more than 7 days to see OEM Unlock so they can root the device. Any one was able to find an alternative or workaround solution instead of waiting 7 days since I don't have that much time to wait I need to root urgently before a birthday.
Your help much appreciated.
Nope, wait the 7 days
My G960F had OEM unlock available on day 1, check in download mode it is the model you think
Flashing Firmware
*Detection* said:
Nope, wait the 7 days
My G960F had OEM unlock available on day 1, check in download mode it is the model you think
Click to expand...
Click to collapse
Do you think flashing a new firmware will show the OEM lock?
c05338 said:
Do you think flashing a new firmware will show the OEM lock?
Click to expand...
Click to collapse
Factory resetting resets the 7 day timer, switching CSCs requires a reset, you'll have to wait it out
*Detection* said:
Factory resetting resets the 7 day timer, switching CSCs requires a reset, you'll have to wait it out
Click to expand...
Click to collapse
I'll wait but actually I don't have much time I should finish it before Monday and today is Saturday so far it's 25 hours up so I'm yet searching for a solution. Anyway to root the device without OEM unlock?
c05338 said:
I'll wait but actually I don't have much time I should finish it before Monday and today is Saturday so far it's 25 hours up so I'm yet searching for a solution. Anyway to root the device without OEM unlock?
Click to expand...
Click to collapse
No solution, read the forums, you cannot root without it, you have to wait no matter how many times you ask
c05338 said:
I have a brand new sealed Samsung S9 SM-G960F/DS which is most probably Exynos variant however I couldn't find OEM Unlock after activating the developer tools. I've googled that and was surprised that this is a recent Samsung policy and as mentioned by most users they've waited more than 7 days to see OEM Unlock so they can root the device. Any one was able to find an alternative or workaround solution instead of waiting 7 days since I don't have that much time to wait I need to root urgently before a birthday.
Your help much appreciated.
Click to expand...
Click to collapse
flash a combination ROM and oem unlock shows since first moment, unlock and flash the normal firmware that you want.
acabreram said:
flash a combination ROM and oem unlock shows since first moment, unlock and flash the normal firmware that you want.
Click to expand...
Click to collapse
Are you sure man? Any wrong stop will cause me issues to reset the time and wait another 7 days and I'm in an urgent time.
c05338 said:
Are you sure man? Any wrong stop will cause me issues to reset the time and wait another 7 days and I'm in an urgent time.
Click to expand...
Click to collapse
http://www.techzai.com/combination-rom-galaxy-devices/
I found this link to download Combination ROM does it fit?
c05338 said:
http://www.techzai.com/combination-rom-galaxy-devices/
I found this link to download Combination ROM does it fit?
Click to expand...
Click to collapse
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
The combination ROM will allow you to "OEM unlock" your device, but the RMM prenormal state will prevent you from flashing anything custom. I tried this when I first got my S9.
You need to wait the 7 days on stock in order to be able to actually bootloader unlock your device. Make sure to keep a SIM card in, connect a Samsung and Google account, and don't power it off. There is no workaround for this.
*Detection* said:
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
Click to expand...
Click to collapse
that's me LOL
if we can get it to boot up on s9/ plus
then the oem lock thing wouldn't be an issue
TheUndertaker21 said:
that's me LOL
if we can get it to boot up on s9/ plus
then the oem lock thing wouldn't be an issue
Click to expand...
Click to collapse
Wonder if it was because the combination ROM firmware is older than the current on the device
Did it factory reset after the flash? If not that might be causing the bootloop, or if the bootloader version is older on combination
*Detection* said:
Wonder if it was because the combination ROM firmware is older than the current on the device
Did it factory reset after the flash? If not that might be causing the bootloop, or if the bootloader version is older on combination
Click to expand...
Click to collapse
i mean i'm on ARD6 and i don't think there's any combination for this firmware
i flashed the latest combination i found on many times
TheUndertaker21 said:
i mean i'm on ARD6 and i don't think there's any combination for this firmware
i flashed the latest combination i found on many times
Click to expand...
Click to collapse
The way to check the bootloader is here
G960FXXU1BRE5
Version 1
If you boot into Download mode it should say at the bottom BL:1 or whatever version you are currently running, downgrading the BL is usually not possible from what I see lately
*Detection* said:
The way to check the bootloader is here
G960FXXU1BRE5
Version 1
If you boot into Download mode it should say at the bottom BL:1 or whatever version you are currently running, downgrading the BL is usually not possible from what I see lately
Click to expand...
Click to collapse
this is my version
but i flashed this one
COMBINATION_OXM_FA80_G965FXXU1ARB4_OXMFAC
and
COMBINATION_OXM_FA80_G965FXXU1ARB7_OXMFAC_CL13084894_QB17151834
COMBINATION_OXM_FA80_G965FXXU1ARC3
Bootloader version 1 for both yours and the comb'n firmware so doesn't seem to be that
Did you factory reset after flashing combination? That's the only thing I can think of that would cause the loop if you didn't
*Detection* said:
Bootloader version 1 for both yours and the comb'n firmware so doesn't seem to be that
Did you factory reset after flashing combination? That's the only thing I can think of that would cause the loop if you didn't
Click to expand...
Click to collapse
yeah i factory reset it after still nada
weird though
i can wait since i have youtube vanced, everything i always used besides titanium
TheUndertaker21 said:
yeah i factory reset it after still nada
weird though
i can wait since i have youtube vanced, everything i always used besides titanium
Click to expand...
Click to collapse
Yea I used Vanced too, much better than the original YT app
I always did full TWRP nandroid backups rather than TiBu, but it's a good app
Not really impressed with the lengths Samsung are going to to prevent us (the phone OWNERS) from doing what we want with OUR own phones tbh
There was a workaround to update system apps with Nougat, literally no harm done to Samsung with us doing that but they still patched it in Oreo
Starting to feel more like an iPhone than an Android, wasn't the whole point of Android that it was basically open and unlocked for us to play with?
Thing is though, Samsung make one of the best android devices available and they know locking it down isn't going to hurt their sales
*Detection* said:
A member tested the combination ROM theory yesterday for the same purpose and it bootlooped their phone
Click to expand...
Click to collapse
I appreciate if you can share his thread maybe he got the wrong ROM that bricked the phone.
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
GunnermanBill said:
Hey, trying to use skipsoft to unlock my bootloader, install twrp, etc. I select the unlock bootloader option, it reboots to fastboot, notes that the bootloader is locked, but then says bootloader already unlocked no data will be wiped rebooting to android. What can I try to get around this? Thanks
Click to expand...
Click to collapse
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
v12xke said:
Which phone variant do you have? What is the status of the "Allow OEM Unlocking toggle" under Developer Settings? That has to be toggled on first. It should be clearly "on" and not greyed out. If you have the 2XL, you can run the IMEI through this link to verify the variant you have. Under Buyer Name It should say "Google_Open_64GB" or similar.
Click to expand...
Click to collapse
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
GunnermanBill said:
variant is GOOGLE_VRZ_128G
Allow Oem Unlocking Toggle is greyed out for some reason.
Click to expand...
Click to collapse
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
v12xke said:
Well unfortunately there is your reason. Your bootloader cannot be unlocked because your variant is Verizon. Verizon's are bootloader locked and this cannot be overcome. As such you will not be able to flash a custom recovery, flash full Google factory images, or root the phone.
Click to expand...
Click to collapse
Well that's new as far as google phones go
GunnermanBill said:
Well that's new as far as google phones go
Click to expand...
Click to collapse
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
v12xke said:
Sorry to say but it's not new for Verizon variants of Pixel or Nexus (or almost any other phone Verizon sells with very few exceptions). Verizon refuses to allow their users to unlock their own bootloader- including Google phones. Your Verizon phone is bootloader-locked and there is nothing you can do about it. Verizon phones are sometimes sold at deep discounts with the hook of a multi-year service agreement. Have you ever heard the term "The Red Devil" used for Verizon? It's not new either. Sorry to bring you the bad news, but it is true. There are many threads here on XDA which will confirm this. Best of luck.
Click to expand...
Click to collapse
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
GunnermanBill said:
It's no big deal, my gf took the upgrade to Pie and hates it and I was just gonna root mine before it started prompting me. Someone will get it unlocked in a year or something like always. As far as I can tell the pixel line is the first that Verizon did this with, we had Galaxy Nexus' a long time ago and those weren't locked.
Click to expand...
Click to collapse
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
xunholyx said:
Verizon users have been hoping for an unlock method since the 2XL's release.
Look at this thread for more information on that.
Click to expand...
Click to collapse
i mean it only happened for the regular pixels in 2016. I'm in no rush, like i said NBD
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
kickenwing13 said:
I'm also trying to relock, just used your link. I'm on the google version running android p. I unlocked a long time ago, but never ended up doing anything with it. I have an RMA coming and the option is grayed out and wugs is failing ... .. Thought about trying to downgrade to O and trying my luck on "android o"
Click to expand...
Click to collapse
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
v12xke said:
You may not have unlocked critical. There are two separate commands. Anyway, since your RMA is on the way just wait until it arrives, update it to Pie and then do a data transfer for all your settings/data. Once your new phone is set up, just do a FDR before sending it back. You do NOT need to relock the phone. They do not care. Just FDR to wipe your personal data off the phone. Lastly, you want to de-register or remove that old phone from your Google account before sending it back. Best of luck.
Click to expand...
Click to collapse
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
kickenwing13 said:
Thank you so much dude. I know you're right . I used the toolkit and nothing after unlocking ever worked and I'm assuming it's because of that .... I've been telling myself I need to learn it the old fashioned way but have never been able to properly install adb and all that stuff..
Click to expand...
Click to collapse
I would encourage you to just "install" adb/fastboot. It is literally opening a zip file and extracting everything into a new folder. Then adding that folder to your path statement (Windows) means you can use the command from anywhere. For example I created a folder c:\adb and just dumped the files in there. I see you already have opened the flash-all.bat script and are poking around ... so in the beginning you can just cut and paste those commands if you want to do things manually -or- just run the script. You can always get the latest standalone binaries direct from Google. Ditch the toolkits and you will be glad you did. It is just not that hard, and you will know how to get yourself out of a jam later. :good:
I DID IT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It was cake. Thanks for the awesome directions. I just opened up through cmd insead of your second step, but dude! clutch . I relocked it.. took 2 seconds once my buddy helped me tpye my first command. But thank you again! Now debating getting more into it. This is the first phone i haven't installed a custom ROM on because the unlock and root stuff absolutely failed...
I can't seem to find a consistent guide on this. Any help to to get me rooted and using an unlocked bootloader is greatly appreciated. If anyone knows a great, recent guide or knows how to do this, please link it.
Blaze Uchiha said:
I can't seem to find a consistent guide on this. Any help to to get me rooted and using an unlocked bootloader is greatly appreciated. If anyone knows a great, recent guide or knows how to do this, please link it.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-j2/help/j2-core-sm-j260g-help-t3921806
2nd comment which is my comment. It should work.
Unlocking bootloader for Samsung device seems to be only turn on OEM unlocking
Prove N. said:
https://forum.xda-developers.com/galaxy-j2/help/j2-core-sm-j260g-help-t3921806
2nd comment which is my comment. It should work.
Unlocking bootloader for Samsung device seems to be only turn on OEM unlocking
Click to expand...
Click to collapse
There's no OEM unlocking option in my developer's options. I thought it was weird but this phone is brand new as I just got it today
Blaze Uchiha said:
There's no OEM unlocking option in my developer's options. I thought it was weird but this phone is brand new as I just got it today
Click to expand...
Click to collapse
So its your carrier's problem then. TMobile to be exact. Are you on a contract or anything? Can you issue an unlock request if no contract?
(I dont know much how US-locked phone works~)
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Snippititgood said:
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Click to expand...
Click to collapse
Help me man lol
Sent from my SM-J260T1 using XDA Labs
Snippititgood said:
So I've got mine unlocked, almost absolutely 0 information on the product. Researched about 3 hrs now and still only got the info obtained from devcheck. Will provide anything required. Looking to root magisk, wanna try out lineage. I'll be a tester, i am a noob.
Model- sm-j260t1
Device- j2corepltemtr
2019
Build-M1ajq.j260t1uvu1asa3
Made 1-10-2019
8.1.0 os
build-13.18.14-15262773
If instructed how to back up I'd be happy to share kernel/firmware.
Tia
Snip
Click to expand...
Click to collapse
Yes did anything ever come of this? Also when you unlock it, does it you to root it?
So is there a way to get the OEM option to appear in the dev options or a way to install a bootloader without OEM?
I'm having the same exact problem with my phone. Same model and everything and I also do not have the unlocking option In my dev options. I've tried every exploit known to me and have no luck. I tried flashing TWRP theough Odin without the OEM unlocking and I get a fail because of a secure check fail which I'm not sure is related to the bootloader not being unlocked or something else. I'd love to get an answer to this so I can get lineageos on here
Has anyone found anything yet on how to unlock or enable OEM unlocking
As I understand it the OEM unlock setting is only available after owning the device for 160 days.
Samsung Galaxy J2 (Metro PCS) [SM-J260T1]
Sircrysalotz said:
Has anyone found anything yet on how to unlock or enable OEM unlocking
Click to expand...
Click to collapse
Firmware info of Samsung Galaxy J2 (Metro PCS) [SM-J260T1]
Android version - 8.1.0 (Oreo)
Build # M1AJQ.J260T1UVS6ATG2
There is no OEM unlock option in the dev options for this phone.
The most I could do is to get in to go into download mode, no bootloader came up.
I Used ADB Command: adb reboot bootloader
Another PC app I seen on xda forums is called "ADBAppControl".
There is an option reboot your phone with adb built in to do it too.
---------- Post added at 05:45 AM ---------- Previous post was at 05:17 AM ----------
Blaze Uchiha said:
So is there a way to get the OEM option to appear in the dev options or a way to install a bootloader without OEM?
Click to expand...
Click to collapse
My J2 is new and No at this Point, One Reply in here said after 160 days of owning it the option opens up, so I will have wait for the 160 days are up to check again.
Update, it been Over 160 Days and still do not see anything in the dev options. I bought the phone 4-12-2020. So i guess it lockout code that releases the option i suppose. or it just not available with this phone.
Was thinking of flashing my old stock 4.1 on it. cause 4.1 i had no trouble rooting it.
Yes,I'm new to the forum. I also have the same model phone unlocked from the carrier(Metro PCS). I've tried several ways to root this device but I don't have access to a PC I also get the security error code to pop up when I tried to install custom OS. I can't seem to get the recovery backup or to actually Flash the proper image to the bootloader I've also tried kingroot, kingoroot, l root, and some other one click root options. My understanding of using team Win Recovery Project without PC is limited I'm also trying to use magisk with it.In A novice in understanding...Does anyone have any advice..
Better find a friend with a computer to help you . Apps are crappier than Microsoft.
I'm not able to use some data services, most importantly MMS. This was an issue on my last phone, also (LG G6.) However, if I inserted an AT&T sim card and added my carriers APN settings, then inserted my carrier sim, the settings would stick. I recall doing this before the Android 10 update on this device (Pixel 2 XL) and it worked, but now nothing seems to.
I've tried rooting the phone as well, unsuccessfully. I've followed a guide here on XDA and the procedure would simply fail, even when all steps were followed meticulously. I'm not new to rooting, so needless to say I got very annoyed because I had to factory reset the device, which was a pain to have to set up again...
If anyone has any ideas, please let me know. This isn't isolated to just me, on the Google forums as well as Reddit, many others have this problem. Thanks guys.
ruffyreborn said:
I'm not able to use some data services, most importantly MMS. This was an issue on my last phone, also (LG G6.) However, if I inserted an AT&T sim card and added my carriers APN settings, then inserted my carrier sim, the settings would stick. I recall doing this before the Android 10 update on this device (Pixel 2 XL) and it worked, but now nothing seems to.
I've tried rooting the phone as well, unsuccessfully. I've followed a guide here on XDA and the procedure would simply fail, even when all steps were followed meticulously. I'm not new to rooting, so needless to say I got very annoyed because I had to factory reset the device, which was a pain to have to set up again...
If anyone has any ideas, please let me know. This isn't isolated to just me, on the Google forums as well as Reddit, many others have this problem. Thanks guys.
Click to expand...
Click to collapse
I'm not sure what guide you used to root, but Android 10 requires a different root method than what you'd normally use on 9. You should get the 7.4.1 magisk manager apk and install it on your phone then use it to patch a boot image which you'll then flash to your phone with fastboot. Also, make sure you have the latest sdk platform tools, fastboot.
When you tried to add an apn did you got to the three dot for menu under APNs?
jd1639 said:
I'm not sure what guide you used to root, but Android 10 requires a different root method than what you'd normally use on 9. You should get the 7.4.1 magisk manager apk and install it on your phone then use it to patch a boot image which you'll then flash to your phone with fastboot. Also, make sure you have the latest sdk platform tools, fastboot.
When you tried to add an apn did you got to the three dot for menu under APNs?
Click to expand...
Click to collapse
Dang JD! Where you been hiding my friend? Good to see ya! ??
Badger50 said:
Dang JD! Where you been hiding my friend? Good to see ya!
Click to expand...
Click to collapse
I'm still around. These forums are getting a little slow so it's been hit or miss whether there's something i can help with. It's good to see you too. It's been awhile
jd1639 said:
I'm still around. These forums are getting a little slow so it's been hit or miss whether there's something i can help with. It's good to see you too. It's been awhile
Click to expand...
Click to collapse
Roger that my friend. I've got 2 grandsons now that think I'm their personal slave! Bwahahahahaha...it's awesome!!! ????
jd1639 said:
I'm not sure what guide you used to root, but Android 10 requires a different root method than what you'd normally use on 9. You should get the 7.4.1 magisk manager apk and install it on your phone then use it to patch a boot image which you'll then flash to your phone with fastboot. Also, make sure you have the latest sdk platform tools, fastboot.
When you tried to add an apn did you got to the three dot for menu under APNs?
Click to expand...
Click to collapse
Hey, thanks so much for replying. This is the root guide I followed.
But the issue I had was "OEM unlocking" was disabled and grayed out. At no point could I toggle it. And that isn't including all the problems I had trying to get ADB to detect my phone while connected to my computer, even with all drivers updated and debugging enabled.
Yes I have tried the menu up top. The only option there is "reset to default"
Here are some screenshots
ruffyreborn said:
Hey, thanks so much for replying. This is the root guide I followed.
But the issue I had was "OEM unlocking" was disabled and grayed out. At no point could I toggle it. And that isn't including all the problems I had trying to get ADB to detect my phone while connected to my computer, even with all drivers updated and debugging enabled.
Yes I have tried the menu up top. The only option there is "reset to default"
Here are some screenshots
Click to expand...
Click to collapse
If oem unlock is greyed out its most likely a Verizon phone and cannot be rooted. Unless something has changed
So, is there no way to edit a locked Verizon APN without root?
jmjudd99 said:
So, is there no way to edit a locked Verizon APN without root?
Click to expand...
Click to collapse
You can only edit the APN if you have a GSM SIM inserted such as from AT&T or T-Mobile. Android automatically hides the APN settings when a Verizon SIM is inserted, as Verizon is not a GSM-based carrier and configures the device settings automatically using the network. You need to find out if Bluegrass has AT&T or T-Mobile-compatible SIM cards you can use in the device. Those SIM cards should allow you to edit the APN.
If OEM Unlocking is grayed out, you have a Verizon device and you cannot unlock the bootloader. Using the device on other carriers however is still possible as Verizon does not SIM lock devices.
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
truckerdewd said:
I got my device from T-Mobile and yes the bootloader is locked. I was on the A13 beta and opted out. I am now back on A12. Yes it took some extra steps to get back to A12 but you can do it with a locked bootloader.
Click to expand...
Click to collapse
Not everyone has been so lucky. Glad it worked for you, though.
roirraW edor ehT said:
Not everyone has been so lucky. Glad it worked for you, though.
Click to expand...
Click to collapse
True. I posted the steps I followed in this thread.
Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that...
forum.xda-developers.com
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Lughnasadh said:
I'm a firm believer that unless you are using some apps (mostly banking apps) that will absolutely not work with these enabled, that before doing anything you should toggle on "OEM unlocking" and "USB debugging", regardless if you're using Stable or Beta or whatever you're doing. It will open up a bunch of possibilities to recover your phone if you hit a glitch in the matrix.
For me it's the very 1st thing I do when getting a new phone.
Click to expand...
Click to collapse
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
V0latyle said:
I'm not sure toggling these would trip device security. As long as the bootloader remains locked the device should meet HARDWARE_BACKED integrity (key attestation), and if the firmware is factory the device should meet BASIC integrity as well.
Click to expand...
Click to collapse
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
gpvecchi said:
Sorry, but if you just enable the OEM unlock? Then, just in case things go bad, you can unlock bootloader...
Click to expand...
Click to collapse
Basically yes, as long as you have an unlockable bootloader, can get into fastboot, etc..
For example, if things go haywire for you and you have OEM unlocking enabled, you can use Android Flash Tool to help recover your device. Or you can use fastboot to manually unlock the bootloader and flash whatever.
Lughnasadh said:
We are not actually talking about tripping device security or being able to pass Play Integrity API, etc.. Even with the bootloader locked, apps can still check to see whether OEM Unlocking and USB Debugging are enabled, and if so, make it so the app fails to work properly, if at all. Apps can even check to see if you have Developer Options enabled.
USB debugging definitely does interfere with some apps being able to work. I have to disable it to use one of my apps and many others have reported the same for a variety of apps. I have also seen having OEM Unlocking enabled interfere with some apps as well, as reported by others.
In my case I just disable USB Debugging, use the app, then re-enable when done using the app.
Click to expand...
Click to collapse
Yeah I think my brain was somewhere else. Interesting though.
@Lughnasadh Just curious which apps? I've not come across any.
bobby janow said:
@Lughnasadh Just curious which apps? I've not come across any.
Click to expand...
Click to collapse
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Lughnasadh said:
Of the ones I use, Spectrum TV requires USB Debugging to be disabled.
Click to expand...
Click to collapse
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
bobby janow said:
I obviously do not use Spectrum TV. I almost always have debugging on and have never come across a need to turn it off, I actually didn't even know it was a thing. But it makes sense since it is an opening into the device. One thing I have noticed when I flip the OEM switch though. I only keep it active when I'm either sideloading or, heaven forbid, install a beta or custom rom. After it's done and booted I flip the switch back off and it has me reboot for added security that is not available when the switch is active. What's that all about?
Click to expand...
Click to collapse
Yeah, if you go through the Magisk, SafetyNet and similar threads you'll see people who have come across apps that won't work when USB Debugging is enabled. It's really up to the app developer as to whether it checks for it or not.
I'm not entirely sure why after you switch OEM Unlocking off that it has you reboot as I've never switched it off once switched on. My guess would be that a reboot is needed to set ro.oem_unlock_supported to 0. But that's just a guess.
V0latyle said:
If your bootloader is locked, one of the dumbest things you can do is try to install potentially unstable firmware. If something goes wrong, you won't be able to recover your device.
If you did anyway, the only way you should try to return to stock is with the Android Flash Tool, which should work as long as OEM Unlocking is enabled.
If you're on a device that cannot be unlocked, you should wait the Android 13 official release.
Click to expand...
Click to collapse
The way Google implements there otas and installs now is a fail safe, the devices will not be bricked what so ever, if on stock that is