Is it ok to pay bills, check bank account etc on a device that's unlocked and rooted? Or once you do that to the device you loose all security?
Thanks
Sent from my Pixel XL using XDA-Developers Legacy app
jblack41510 said:
Is it ok to pay bills, check bank account etc on a device that's unlocked and rooted? Or once you do that to the device you loose all security?
Thanks
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I wouldn't do it, at least not outside my home wifi. Your bank probably has certain protections but your data is exposed if you lose the device or it gets stolen. That being said, I have done it with no untoward effects, but that was before hacking became so prevalent. Be curious to see what others have to say.
So it's only really a threat if I loose my device?
Is there any security issue using while in possession of the device?
Sent from my Pixel XL using XDA-Developers Legacy app
jblack41510 said:
So it's only really a threat if I loose my device?
Is there any security issue using while in possession of the device?
Click to expand...
Click to collapse
Root is not an additional threat if you lose your phone. If you lose your phone to a pro you are toast, root or not. If they are not a pro root makes zero difference. Assuming you have a pin password on the phone. If you don't you are of course toast.
The danger of root is you. If you muck it up by installing unknown software, turning off encryption, stuff like that...that is where you will get in trouble.
Thanks for the reply
I know what can happen if I loose the phone. My main concern is the phones security while in my possession.
So as long as I don't install unknown software and apps while unlocked and rooted, then my information should be just as safe as if I wasn't unlocked and rooted?
I do have a few apps I have Installed from unknown sources that I use. Mostly the popular ones... Adaway and viper4andriod.
Do any of these security apps like cm, Norton, bitdefender etc. really work?
Sent from my Pixel XL using XDA-Developers Legacy app
jblack41510 said:
Thanks for the reply
I know what can happen if I loose the phone. My main concern is the phones security while in my possession.
So as long as I don't install unknown software and apps while unlocked and rooted, then my information should be just as safe as if I wasn't unlocked and rooted?
I do have a few apps I have Installed from unknown sources that I use. Mostly the popular ones... Adaway and viper4andriod.
Do any of these security apps like cm, Norton, bitdefender etc. really work?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
I've always been rooted and I use banking and pay apps on occasion, I mean all this is anecdotal so take it with a grain of salt because we can't predict the future of what exploits bring and no one knows your habits when it comes to mobile devices.
I dont put a lot of stake in to those apps you mentioned, they make money off of fear.
Keep your device up to date, don't download programs you are uncertain of, make sure you have a lock screen and pattern. At this point its a difference of 6 or 7 pad locks on the front door.
V
jblack41510 said:
Thanks for the reply
I know what can happen if I loose the phone. My main concern is the phones security while in my possession.
So as long as I don't install unknown software and apps while unlocked and rooted, then my information should be just as safe as if I wasn't unlocked and rooted?
I do have a few apps I have Installed from unknown sources that I use. Mostly the popular ones... Adaway and viper4andriod.
Do any of these security apps like cm, Norton, bitdefender etc. really work?
Click to expand...
Click to collapse
I dont consider those apps to be unknown. They come from here, have been around forever and are very popular. Adaway was on the store until Google changed the rules.
Based on what you are doing you are fine..
And I agree with thw poster above, the commercial security programs are next to useless.
And keep your phone up to date. A phone not up to date on security patches scares me far more than a rooted phone.
Do your thing you are fine.
TonikJDK said:
Root is not an additional threat if you lose your phone. If you lose your phone to a pro you are toast, root or not. If they are not a pro root makes zero difference. Assuming you have a pin password on the phone. If you don't you are of course toast.
The danger of root is you. If you muck it up by installing unknown software, turning off encryption, stuff like that...that is where you will get in trouble.
Click to expand...
Click to collapse
How are you toast with a locked bootloader, pin startup? Pro or not. Unlocked bl, flash without data wipe -w, and data is exposed. Most don't use a startup pin. I'm not questioning your knowledge just looking for the explanation.
Sent from my Pixel using XDA-Developers Legacy app
bobby janow said:
How are you toast with a locked bootloader, pin startup? Pro or not. Unlocked bl, flash without data wipe -w, and data is exposed. Most don't use a startup pin. I'm not questioning your knowledge just looking for the explanation.
Click to expand...
Click to collapse
What do you mean most don't use a start up pin? You set a pin/pattern period and the device is encrypted.
That means even if I flash factory without the -w my device won't let me in without me using my pin or pattern. Maybe I am missing some thing? Of course I flash this thing at least once every 60 days and I have literally had the same pin since my first boot up when it encrypted the file system.
Even of you reset the device unless you have the email for the original owner you can't get in.
I should have been more clear when I said 'pro'. I mean a real pro. Hackers got into a locked iPhone in the San Bernardo shooter case. Those same hackers took a run at Android and found a way to hijack an MDM system and remotely reset the pin. None of us need to worry about those kinds of attacks if we lose our phone, but the bottom line is that if you lose physical control of any device, phone, computer, tablet, your data is toast if the right person takes a run at it.
pcriz said:
What do you mean most don't use a start up pin? You set a pin/pattern period and the device is encrypted.
That means even if I flash factory without the -w my device won't let me in without me using my pin or pattern. Maybe I am missing some thing? Of course I flash this thing at least once every 60 days and I have literally had the same pin since my first boot up when it encrypted the file system.
Even of you reset the device unless you have the email for the original owner you can't get in.
Click to expand...
Click to collapse
I'm not 100% on this so bear with me. I was under the assumption that with an unlocked bootloader FRP (factory reset protection) was non functional. By startup pin I meant there is an option when setting a pin to either have it ask for the pin before anything at all happens and one to get into the device once it boots up. Most people use the latter but not the former because it's a pain. Personally, I set both with a locked bootloader so I'm pretty much in the clear. But with an unlocked bootloader and no startup pin (vs login pin) it's my understanding that you are wide open to data theft if you device is stolen.
---------- Post added at 07:16 AM ---------- Previous post was at 07:11 AM ----------
TonikJDK said:
I should have been more clear when I said 'pro'. I mean a real pro. Hackers got into a locked iPhone in the San Bernardo shooter case. Those same hackers took a run at Android and found a way to hijack an MDM system and remotely reset the pin. None of us need to worry about those kinds of attacks if we lose our phone, but the bottom line is that if you lose physical control of any device, phone, computer, tablet, your data is toast if the right person takes a run at it.
Click to expand...
Click to collapse
That I agree with. Although banking apps will ask for verification from an unknown IP address or device. The hackers that got into a locked iPhone were paid millions by us. (the government) I doubt that if your bootloader is locked and the device is lost those same hackers will be paid that kind of money for your pics of the wife and kids. But once again, I was under the assumption that unlocked the task is much, much easier.
bobby janow said:
I'm not 100% on this so bear with me. I was under the assumption that with an unlocked bootloader FRP (factory reset protection) was non functional. By startup pin I meant there is an option when setting a pin to either have it ask for the pin before anything at all happens and one to get into the device once it boots up. Most people use the latter but not the former because it's a pain. Personally, I set both with a locked bootloader so I'm pretty much in the clear. But with an unlocked bootloader and no startup pin (vs login pin) it's my understanding that you are wide open to data theft if you device is stolen.
Click to expand...
Click to collapse
So when I set up my device out the box there was no options to change frp, it asks if you want to set up a finger print and when you click yes it prompts for either a pin or pattern first.
There is no option for start up pin. Once you have a pin or pattern the device is encrypted. As per Google's policy once that happens, unless I remove the pin every power up requires a pin, if you don't use your device for say like 8 hours it requires a pin, otherwise it's a finger print.
No where can I set the pin not to activate upon boot. You either have a pin/pattern or you don't have one.
You can flash this thing all day but without my pattern you aren't getting in and I have been unlocked and rooted since November.
FRP is currently unbeatable unlocked or not. Other than the aforementioned 'pros' I guess.
There is no boot pin on Android, but there is a 'Sim Lock' that you can turn on. It is in the security settings and keeps your phone from connecting to the internet or doing much of anything until you enter it after a reboot. Alarms and so on will not work either. Even with a fingerprint set, when you reboot you still have to enter the pin.
pcriz said:
So when I set up my device out the box there was no options to change frp, it asks if you want to set up a finger print and when you click yes it prompts for either a pin or pattern first.
There is no option for start up pin. Once you have a pin or pattern the device is encrypted. As per Google's policy once that happens, unless I remove the pin every power up requires a pin, if you don't use your device for say like 8 hours it requires a pin, otherwise it's a finger print.
No where can I set the pin not to activate upon boot. You either have a pin/pattern or you don't have one.
You can flash this thing all day but without my pattern you aren't getting in and I have been unlocked and rooted since November.
Click to expand...
Click to collapse
Ok, I have 2 devices, a 5x and a Pixel and I use them both. On the 5x (Android O, locked bootloader) when I am asked to enter a PIN then the question is, " You can further protect this device by requiring your PIN before it starts up. ... Require PIN to start your device?" That is different than after you startup. I don't think on (7.1.2) the Pixel that question is asked.
Nonetheless, if you unlock the bootloader and have root (obviously I can't test this) can you flash a factory image with the -w and get in without your pin? What if you flash an image without the -w switch? Without FRP protection, as with an unlocked bootloader, don't you feel your device is less secure whether it be copying your data via adb or allowing the device to be used in case of theft or loss? Now perhaps I drank the Koolaid, but I know that if I ever lose either of my devices they are totally useless to the next person. Can you say the same thing?
---------- Post added at 07:42 AM ---------- Previous post was at 07:39 AM ----------
TonikJDK said:
FRP is currently unbeatable unlocked or not. Other than the aforementioned 'pros' I guess.
There is no boot pin on Android, but there is a 'Sim Lock' that you can turn on. It is in the security settings and keeps your phone from connecting to the internet or doing much of anything until you enter it after a reboot. Alarms and so on will not work either. Even with a fingerprint set, when you reboot you still have to enter the pin.
Click to expand...
Click to collapse
Are you sure FRP is usable with an unlocked bootloader?
edit: I was referring to this article: http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
I just reread it and they have edited it about midway through the article. It does seem that unlocking the bootloader will not disable FRP although there are conflicting reports. Now what about root? lol
bobby janow said:
Ok, I have 2 devices, a 5x and a Pixel and I use them both. On the 5x (Android O, locked bootloader) when I am asked to enter a PIN then the question is, " You can further protect this device by requiring your PIN before it starts up. ... Require PIN to start your device?" That is different than after you startup. I don't think on (7.1.2) the Pixel that question is asked.
Nonetheless, if you unlock the bootloader and have root (obviously I can't test this) can you flash a factory image with the -w and get in without your pin? What if you flash an image without the -w switch? Without FRP protection, as with an unlocked bootloader, don't you feel your device is less secure whether it be copying your data via adb or allowing the device to be used in case of theft or loss? Now perhaps I drank the Koolaid, but I know that if I ever lose either of my devices they are totally useless to the next person. Can you say the same thing?
---------- Post added at 07:42 AM ---------- Previous post was at 07:39 AM ----------
Are you sure FRP is usable with an unlocked bootloader?
edit: I was referring to this article: http://www.androidpolice.com/2015/0...evice-protection-feature-and-how-do-i-use-it/
I just reread it and they have edited it about midway through the article. It does seem that unlocking the bootloader will not disable FRP although there are conflicting reports. Now what about root? lol
Click to expand...
Click to collapse
You have two paths. You flash firmware and get presented with the initial setup screen. You will get to a point where you have to log in with the last email used in the device. Unless you have my email and password you get no further.
Otherwise the device will boot to lock screen requesting your PIN. Please explain to me how you get around this? Adb is setup to only work on my machine and you can't revoke creditentials without being in the OS.
I don't know how many different ways to say it, I guess my question is can you detail a way someone can use my device if I lose it?
pcriz said:
You have two paths. You flash firmware and get presented with the initial setup screen. You will get to a point where you have to log in with the last email used in the device. Unless you have my email and password you get no further.
Otherwise the device will boot to lock screen requesting your PIN. Please explain to me how you get around this? Adb is setup to only work on my machine and you can't revoke creditentials without being in the OS.
I don't know how many different ways to say it, I guess my question is can you detail a way someone can use my device if I lose it?
Click to expand...
Click to collapse
I don't know but I'm not a hacker nor have I researched it. So you are implying that even flashing a custom rom you cannot get into the device without a Google password? I find that intriguing to say the least. No custom roms bypass FRP?
My question to you is do you feel as safe with an unlocked bootloader as you would with it locked?
bobby janow said:
I don't know but I'm not a hacker nor have I researched it. So you are implying that even flashing a custom rom you cannot get into the device without a Google password? I find that intriguing to say the least. No custom roms bypass FRP?
My question to you is do you feel as safe with an unlocked bootloader as you would with it locked?
Click to expand...
Click to collapse
If a custom recovery can't bypass the encryption why would a rom be any different. Not to mention you cannot flash a rom without getting into twrp, twrp cannot decrypt the file system without a pin or pattern. I feel even safer because rooted I can utilize apps that can work to protect me at the system level. I can block ads at the system level.
Its like saying you have a door with 5 padlocks, but wouldnt you feel safer with six?
I'd feel safer not using a mobile phone at all but here we are.
pcriz said:
If a custom recovery can't bypass the encryption why would a rom be any different. Not to mention you cannot flash a rom without getting into twrp, twrp cannot decrypt the file system without a pin or pattern. I feel even safer because rooted I can utilize apps that can work to protect me at the system level. I can block ads at the system level.
Its like saying you have a door with 5 padlocks, but wouldnt you feel safer with six?
I'd feel safer not using a mobile phone at all but here we are.
Click to expand...
Click to collapse
That's another story for another day, but I do agree. I can't test any of this, but from days long ago wasn't there a way to boot twrp, go into file manager and delete some files or copy them? Also on a quick search there are a couple of ways to bypass FRP which I will not describe or link to here. And with an unlocked bootloader you can flash any factory image that has the exploit still unpatched.
I guess I just don't see why an unlocked bootloader is such a plus these days. I know you need it for root, but other than ad blocking (which I still get with dns66 unrooted) why allow a hacker to "possibly" compromise your system? I don't know, perhaps I'm getting old and slightly tired of flashing. Needless to say, this is an interesting conversation and certainly thought provoking.
bobby janow said:
That's another story for another day, but I do agree. I can't test any of this, but from days long ago wasn't there a way to boot twrp, go into file manager and delete some files or copy them? Also on a quick search there are a couple of ways to bypass FRP which I will not describe or link to here. And with an unlocked bootloader you can flash any factory image that has the exploit still unpatched.
I guess I just don't see why an unlocked bootloader is such a plus these days. I know you need it for root, but other than ad blocking (which I still get with dns66 unrooted) why allow a hacker to "possibly" compromise your system? I don't know, perhaps I'm getting old and slightly tired of flashing. Needless to say, this is an interesting conversation and certainly thought provoking.
Click to expand...
Click to collapse
There is also the story where Google paid a group of hackers 50 grand when they ran an exploit on a bootloader locked device that allowed them access to data on it. So even given that scenario with a locked bootloader and them not even having to touch the device, they were able access information on it.
Furthermore this is a doomsday scenario of one someone has to have my device, two they have to have the know how, 3 an image that can bypass the security checks that exist outside of the rom that is still allowed to boot without setting off tamper flags.
Also as far as removing files using twrp, again it cannot decrypt the filesystem without pin pattern so when you view the files in the twrp browser they are a bunch of folders with gibberish names and any attempt to make changes fails.
Not unlocking your bootloader is a choice. But let's not pretend that you open yourself up to a world of stolen data and exploits by unlocking it and rooting. That's the kind of scare tactics apps like AVG use to scare people into downloading them and paying for protection that is only good if you don't get attacked at the system level.
I saw the same links for frp bypass but here is the catcher. Unless fastboot is how they are passing it, they can just as easily do it on any device. Not just the bootloader unlocked ones.
pcriz said:
There is also the story where Google paid a group of hackers 50 grand when they ran an exploit on a bootloader locked device that allowed them access to data on it. So even given that scenario with a locked bootloader and them not even having to touch the device, they were able access information on it.
Furthermore this is a doomsday scenario of one someone has to have my device, two they have to have the know how, 3 an image that can bypass the security checks that exist outside of the rom that is still allowed to boot without setting off tamper flags.
Also as far as removing files using twrp, again it cannot decrypt the filesystem without pin pattern so when you view the files in the twrp browser they are a bunch of folders with gibberish names and any attempt to make changes fails.
Not unlocking your bootloader is a choice. But let's not pretend that you open yourself up to a world of stolen data and exploits by unlocking it and rooting. That's the kind of scare tactics apps like AVG use to scare people into downloading them and paying for protection that is only good if you don't get attacked at the system level.
I saw the same links for frp bypass but here is the catcher. Unless fastboot is how they are passing it, they can just as easily do it on any device. Not just the bootloader unlocked ones.
Click to expand...
Click to collapse
Yes, it was in fastboot (I'm pretty sure) and only on an unlocked bootloader of which I'm sure. If the exploit does indeed work then a locked bootloader would be the protection and an unlocked one would mean those padlocks you have are useless. But that's a big "if" and I'm not about to try it. I'm not of the mindset that my data is protected even locked. Bottom line don't lose the device to a person in the know.
I still feel better having a locked bootloader as no one can do anything with my device no matter their skill levels. I just call, blacklist the IMEI, and scrounge up some money for a replacement with no worries. Besides, I use AP all the time and I'm not about to jump through hoops after each Google server update to get it to work again with hiding root. But that is just a personal preference and not really part of this discussion.
As for TWRP, I do remember that there was a way to delete a couple of .key files in order to remove the need to use a password. But that was some time ago before all this security stuff went into effect I believe. But as to the OP question, I believe there is more danger with an unlocked bootloader and root than without. However, if you need root for some reason just make sure you know what you are doing before you do it.
Related
Hello,
I have an interesting project. My company does not use a BYOD setup for company devices, we actually purchase and deploy devices for our end users. This ensures that we have full control over the devices, how they are being used and allows for ease of support and Asset Tracking. I've always been a fan of Nexus devices simply because they are so clean out of the box (little/no bloatware). The latest generation also has the Finger Print sensor which will make using the devices much easier and more secure for our end users.
Now...we have around 250 devices in service (Galaxy S3's) that will need to be upgraded. I have been experimenting with the Nexus and I have been able to Unlock the bootloader, run a temporary Custom Recovery and take a Nandroid backup "image" of the device. This image has all of the software, settings and layout we need on the device. I then wiped everything out and restored the image successfully with only one issue...I can't figure out how to Relock the bootloader on the 5X without wiping out my loaded Nandroid image.
I've tried several ADB Commands, but they all show "Lock bootloader and factory reset phone". Is there a way to relock the bootloader without factory resetting the device? My Nandroid image was taken with stock Marshmallow.
Thanks!
ideaman924 said:
I'm pretty sure relocking the bootloader will automatically start the wiping process. No way around it, it's purely for made out of the bootloader.
You could always leave them unlocked though.
나의 Nexus 5X 의 Tapatalk에서 보냄
Click to expand...
Click to collapse
That's a massive security risk. If want your files, all I have to do is boot into the bootloader, flash twrp, boot from the bootloader to twrp, and all of your personal files are mine.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
That's a massive security risk. If want your files, all I have to do is boot into the bootloader, flash twrp, boot from the bootloader to twrp, and all of your personal files are mine.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Agreed, I don't want to leave them Unlocked for the reasons you outlined. Relocked, they will then be secured behind a Finger Print password. I found apps that could do this, but only for older Nexus models. I may be out of luck for the 5X/6P and imaging. I don't know of any other method of backup that is as all encompassing as Nandroid.
eggdashure said:
Agreed, I don't want to leave them Unlocked for the reasons you outlined. Relocked, they will then be secured behind a Finger Print password. I found apps that could do this, but only for older Nexus models. I may be out of luck for the 5X/6P and imaging. I don't know of any other method of backup that is as all encompassing as Nandroid.
Click to expand...
Click to collapse
you can leave the bootloader unlocked but still encrypt the userdata, which would keep the data secure (even with the pin request upon boot). if the phone was stolen, the recovery and bootloader could be accessed and thus the userdata could be wiped, but not unencrypted and accessed.
is this not sufficient for your needs?
2x4 said:
you can leave the bootloader unlocked but still encrypt the userdata, which would keep the data secure (even with the pin request upon boot). if the phone was stolen, the recovery and bootloader could be accessed and thus the userdata could be wiped, but not unencrypted and accessed.
is this not sufficient for your needs?
Click to expand...
Click to collapse
I believe flashing the factory images without wiping userdata would wipeout the security including the password protection. At that point you could load twrp and access the storage.
Sent from my Nexus 5X using Tapatalk
PiousInquisitor said:
I believe flashing the factory images without wiping userdata would wipeout the security including the password protection. At that point you could load twrp and access the storage.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
As far as I know, Factory images would only affect the system partition. User data is separately encrypted, so the only way to access them is with the password regardless of the rom. You might not even be able to access the data if you flash another rom to system
2x4 said:
As far as I know, Factory images would only affect the system partition. User data is separately encrypted, so the only way to access them is with the password regardless of the rom. You might not even be able to access the data if you flash another rom to system
Click to expand...
Click to collapse
Indeed. I guess that unless the kernel or system are granted permission to read/write to the /data folder during boot then there probably isnt a way to get to your personal files while encrypted.
Maybe you can contact Google and depending on how many devices you want to purchase, they could set you up with a custom bootloader that could be re-locked.
Yeah, Termination requests are never a good thing!
With only 250 devices max, I doubt Google would do anything for us. Thanks for the thoughts and ideas everyone! Looks like we may be doing these by hand again. :crying:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en
peachpuff said:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en
Click to expand...
Click to collapse
Won't do what the OP wants. Even states so in the description.
Its just not possible at this time.
peachpuff said:
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker&hl=en
Click to expand...
Click to collapse
From the app details:
"Nexus 6 and newer devices contain security measures in their bootloaders, connected with factory-reset protection. These measures make it very difficult to use root to lock/unlock the bootloader, and as a result it is unlikely that Nexus 6, Nexus 9, Nexus 5X and Nexus 6P will ever be supported."
Sent from my Nexus 5X using Tapatalk
Woops missed that part, thought that if it worked on my n5 it would work on other nexus' too. Damn google and its security...
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
iBowToAndroid said:
Even doing a SmartSwitch (or Odin) flash won't remove the lock. No amount of flashing or resetting will remove it. The lock is stored in a hidden partition that is never touched by flashes and resets.
There are ways to remove the lock, but they're paid services offered by professionals
Click to expand...
Click to collapse
I have a similar issue, could this be fixed with a Z3X Box?
you could try this method . . .
https://www.youtube.com/watch?v=ggRhkme9FC0
if for any reason didn't work try this one
https://www.youtube.com/watch?v=KRUp09bXnDA
JeffB81 said:
I have a similar issue, could this be fixed with a Z3X Box?
Click to expand...
Click to collapse
Yes it can be, do you have one?
discomaniac said:
Yes it can be, do you have one?
Click to expand...
Click to collapse
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
You took off FRP lock with software?
JeffB81 said:
No, but I was able to repair my phone with Odin and the CPI3 firmware. Thank you
Click to expand...
Click to collapse
Confirm?
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
crazynapkinman said:
I have read elsewhere that flashing the original firmware the phone was factory installed with can fix the frp lock
Click to expand...
Click to collapse
Incorrect. FRP is held in a partition that is not touched during a firmware flash
vazersecurity said:
Confirm?
Click to expand...
Click to collapse
iBowToAndroid said:
Incorrect. FRP is held in a partition that is not touched during a firmware flash
Click to expand...
Click to collapse
Then what about this Cl3? Are there steps after flashing the firmware?
crazynapkinman said:
Then what about this Cl3? Are there steps after flashing the firmware?
Click to expand...
Click to collapse
Flashing firmware can't fix an FRP lock - period.
If you want to know what that poster meant by his message, I suggest you ask him directly
Samsung phones can be frp unlocked by flashing firmware
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Bullshipcaptcha said:
I have personally FRP unlocked 2 Samsung phones by flashing the stock firmware usin Odin. A samsung j7 and a Samsung s5. I am getting so sick of people saying you can't do something when they have no clue. I have also flashed older versions into phones. That's how I rooted the s5 infact. When everyone was saying it was impossible to root at the time. As soon a I figure out how to use sp flash or something to flash different phones other than Samsung I will post saying how it worked not get on someone else's post and say it will never work it's impossible. The world of computers, phones and software is suppose to be open source not locked, hidden and full of viruses.
Click to expand...
Click to collapse
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
That doesn't matter when the phone no longer has a persistent partition.
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Bullshipcaptcha said:
You obviously think you know something and I wont argue or dispute whether you do or dont but I know what I did for sure and what I did was flash stock firmware into those phones and they where no longer FRP locked afterwards. Also When the phone is bricked the phone is flashed blank. There are no patitions if flashed blank. Even when there is persistent data it's still data that is able to be edited with a custom rom which can be flashed after you flash stock rom. I dont know much but I know what I have done personally. My wife is still using her rooted j7 with note 8 D.N.A undetected that we bought f.r.p. locked.
So ya. Just because the internet says it's not possible doesn't mean it's not possible It just means you haven't tried hard enough to prove it yourself. Brick that phone if you have to. Build with that brick.
Click to expand...
Click to collapse
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like system, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Your going to need to go against the grain her a moment . Business or no business
iBowToAndroid said:
I own a business that does FRP removals and many other software-related services for mobile devices . I've done this for years - knowing this type of thing is literally my job.
The "persistent" partition is ALWAYS there - just like tem, boot, recovery, and all the others. And I promise you, you can't remove an FRP lock by throwing it in Download mode and flashing some firmware with Odin, just like you can't remove it by booting to recovery mode and doing a factory reset. It's just not that easy.
Click to expand...
Click to collapse
I'm telling you. I'm not debating the facts. Im telling you what I did. Kinda like I did today with a Moto e4 play. I bypassed frp with flashing stock rom through Odin and then custom rom on the Samsung J7. Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked . I don't have a business in the phones field but I am a business man and sittin on 12 frp locked phones gets tire some. Thant goodness for broken digitizers and displays or I'd still have a bunch more of them. I wont dipute that you know what your doing because likely you do more so than I; we can can probably be certain. I'm just going to tell you the 100 percent fact. Upset wife as my motivating factor I successfully unlocked and rooted a j7 by flashing stock rom into it with Odin then custom reccovery then root then custom rom. The custom recovery I used by accident was for a different brand Jay 7 so mysecond time around I tried the "right" recovery and bricked it. Then again and again and again until Knox was tripped and that's when finally I took bl,ap cp, csc and flashed them in dl mode successfully from there I had Rob from simple cell unlock ( Thanks Rob your the best) remotely unlock the jay7 from T-Mobile after which I flashed the "wrong" proper twrp file giving me the ability to install custom note 8 dna rom into the system. Took two tries, first try I flashed no encrypt no verity but it custom rom frp locked. So second time I made sure I install the developer tools package with OEM unlock switch not able to be turned off then no encrypt no verity. It was a very long process since especially since it was only my second successful full root. Then vallet. Man becomes praised by wife. Man feels empowered man tears apart more phones makes mess, MAN HAPPY! WIFE HAPPY! LOL okay sorry about that part.
---------- Post added at 04:18 PM ---------- Previous post was at 04:06 PM ----------
iBowToAndroid said:
LOL.
The FRP data is stored in the "persistent" partition, which is never touched by a firmware flash, just like EFS and a bunch of other partitions.
So no.
Click to expand...
Click to collapse
None the less each developer has a different approach that being said you frp unlocking phones? I have a Samsung s8 Moto e5 five LGs one zte n835 a couple of alcatels and a few more I couple reassemble real quick If I knew some one who had the abilitby to unlock especially if said amazing developer was teaching El padawan young Como. Yo tango mucho programs, apps and software. Just need the knowledge.
Bullshipcaptcha said:
Today I bypassed frp lock with twrp on the Moto e4 with the bootloader still saying OEM locked
Click to expand...
Click to collapse
Thinking you can flash TWRP on a locked bootloader device shows me exactly what your knowledge level is when it comes to all of this. Future discussion would be futile, and no more responses from me will be had. I do wish you luck with your devices though
How frustrating you are.
Your business need some schooling it sounds like. Your business can't be doing good. Go ahead and Google the Moto e4 unlock method. You will see. You have to try before you say it won't work.
discomaniac said:
I bought a phone that was FRP locked (I know, stupid me) and cannot access the serial number in order to emergency flash it with Smart Switch. Can someone please share their serial number with me so I can reflash it? If not, does anyone have any help? I am on G920PVPU3CPF4
Click to expand...
Click to collapse
I just removed the frp lock on my s6 using a combination firmware (found here-https://firmware.gem-flash.com/index.php?a=downloads&b=folder&id=7410) which completely erased all partions and allowed me to access the settings menu to enable the OEM unlock setting. They are two different firmware there. I used the second one and it worked like a charm. Hope this helps
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.
jhs39 said:
If you didn't create a password in the first place and aren't using a stolen phone you should contact Pixel Support and see if there is a default password the phone might have set up but I haven't heard of that happening to anyone who was on stock and not using a custom recovery. If you are using a custom recovery and are rooted then the previous suggestion might work but I'm pretty sure you need to have root access to get to that file.
Click to expand...
Click to collapse
You don't need root. Just need an unlocked bootloader.
toknitup420 said:
You don't need root. Just need an unlocked bootloader.
Click to expand...
Click to collapse
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.
jhs39 said:
To delete the password file? I would have thought for security reasons that would be placed in the root directory. No wonder Google flashes a warning on its phones that your phone is not secure when the bootloader is unlocked--it really isn't. According to you if anyone steals your phone and you have the bootloader unlocked they can easily bypass any password, pin or fingerprint requirement you set up by simply deleting a file. If that's actually true there's a giant easily exploitable flaw with Android security.
Click to expand...
Click to collapse
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.
rschonfelder said:
I have a Pixel XL runing Android 8.0 beta. I restarted my phone and it asks for a passord. I don't know the password and was wondering what is the best way to recover it?
Thanks in advance.
Click to expand...
Click to collapse
Did you find the phone somewhere or is it yours legitimately? Are you trying to break into another device to get information off it? If you're honest about your intentions you really should explain accurately.
If it's a startup pin you can't bypass that. I hope for owner's sake the bootloader is locked including you if it's yours.
Sent from my Pixel using XDA-Developers Legacy app
toknitup420 said:
Yeah they have to physically take you're phone and know how to boot it to twrp to do it though. And based on these threads I see on here everyday. There's no chance of that happening.
Click to expand...
Click to collapse
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.
jhs39 said:
People who have posted on XDA in the past have seemed very likely to be phone thieves trying to get information about bypassing security on a locked phone so I wouldn't underestimate a phone thief. It's not like XDA is hard to find or a secret.
Click to expand...
Click to collapse
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.
toknitup420 said:
That's not what I meant at all. Lol. I was being a wise ass regarding all the people that on xda that can't get twrp working. I dunno if you look in the Q&A section all that often but it's riddled with people that can't get things working on this phone. It was merely a facsicous comment. On a more serious note. The ability to remove the pin from an unlocked phone is nothing more than the fault of the person who owns the phone. Not a security flaw from Google. You're bootloader doesn't come unlocked stock, and if you have a pin with a locked bootloader then you needn't worry.
Click to expand...
Click to collapse
I misinterpreted your comment then but a lot of people on XDA obviously like to flash their phones and on the Nexus 6P thread you were told by the person who wrote the flashing guides that the absolute first thing you should do with that phone when you got it was to unlock the bootloader. As for getting TWRP to work on the Pixel a lot of experienced flashers including myself have found it challenging to get TWRP to work on this particular phone. Google didn't make Pixels easy to flash on--particularly compared with their earlier Nexus devices. That said I honestly had no idea unlocking the bootloader made the phone that insecure so I sincerely thank you for the heads up.
huh
toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Don't you need the pin to even get into TWRP to delete the file?
Raegoul said:
Don't you need the pin to even get into TWRP to delete the file?
Click to expand...
Click to collapse
Ah yes I forgot about this. This trick only works on decrypted devices. Decrypted devices don't require a password or pattern to enter twrp. Pixel is encrypted by default so yes you would need the password in order to access twrp. GLO. I completely forgot about that.
toknitup420 said:
If you're bootloader is unlocked temp boot into twrp. Delete locksettings.db. That will get you in. Then just create a new pin.
Click to expand...
Click to collapse
Won't it ask for the password when op starts twrp. And if op doesn't have it it cannot decrypt the file system to delete the file you mentioned.
Edit:
NVM saw someone mentioned it
No offense to the OP, but I'm going to call it and say we probably shouldn't be saying anymore. I have never heard of someone setting up their device and then not knowing what their password is. Not saying it's not possible, but if you're on XDA, with a Pixel device on Android O, that means; a) you flashed it and should know your way around some key things on Android, b) you stole the phone, or c) you're trying to break into your significant other's device, and last but not least d) you bought it on Swappa or Cracklist or wherever and the seller didn't wipe it.
People forget their passwords ALL the time... ask my lady if you want!
Erikbronx said:
People forget their passwords ALL the time... ask my lady if you want!
Click to expand...
Click to collapse
Buy her a pen and a pad. No excuses in this day and age.
Sent from my Pixel using XDA-Developers Legacy app
Can't you just go to google.com/android/devicemanager and log in with your google account and unlock it there?
Does anyone know if there’s any way to eliminate the Google warning message that pops up every time you boot up a Pixel phone once you have unlocked the phone’s bootloader? I just saw instructions for doing this on a Samsung phone and I’m just wondering if it’s also possible on my Pixel 2 XL.
just disable dm-verity
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.
Any additional help would be appreciated.
neilth said:
Using the Universal DM-Verity, ForceEncrypt, Disk Quota Disabler, which I found in an XDA forum, I disabled DM-Verity, but the Google boot up warning message is still displayed whenever the phone boots up. Either the script didn’t work or the warning message is not DM-Verity dependent.
Any additional help would be appreciated.
Click to expand...
Click to collapse
hex edit it
The warning message is independent of dm-verity and is triggered upon unlocking the bootloader. While hacking the bootloader to have the message not be displayed may be possible, that course of action could cause an unrecoverable brick. The easiest way to not have the message show is to lock the bootloader.
Thanks for the bad news.
neilth said:
Thanks for the bad news.
Click to expand...
Click to collapse
When the message comes up, tap your power button twice.
The first press pauses booting up, the second is to continue to booting up. I do this whenever I turn on or reboot my phone, and the message is gone in less than a second.
Thanks, I guess that’s about the best solution available.
neilth said:
Thanks, I guess that’s about the best solution available.
Click to expand...
Click to collapse
It's a minor inconvenience. When I say less than a second, I mean like a quarter second or so. Part of the sh*t you get with an unlocked bootloader. The phone is obviously in your hands already if you're seeing the warning message. Just double tap the power button and it'll boot up.
Back story here, I used to use HTC devices. When you went S-Off on them, you'd get a red warning that the build was for in house HTC development purposes only, and that sharing it could lead to legal consequences (lol). That warning stayed up for at least 15 seconds. Maybe 20. And there was no way to dismiss it.
I have a 2013 Google Nexus 7 with an unlocked bootloader and the only "warning" is the appearance of an open padlock at the bottom of the boot screen. Following this the Google legal department must have decided that the current warning message was needed to protect Google from potential lawsuits over possible security issues possibly caused by having an unlocked bootloader on any of their devices.
neilth said:
I have a 2013 Google Nexus 7 with an unlocked bootloader and the only "warning" is the appearance of an open padlock at the bottom of the boot screen. Following this the Google legal department must have decided that the current warning message was needed to protect Google from potential lawsuits over possible security issues possibly caused by having an unlocked bootloader on any of their devices.
Click to expand...
Click to collapse
I have the same tablet lol.
Yeah, the warning is probably for people who don't realize that there are vulnerabilities with having an unlocked bootloader. Most of us older Android enthusiasts already know this.
I don't know about lawsuits, but it's more along their line of being "secure". Not so long ago, Android was less secure than iOS. They have changed that with the Pixel line and the monthly updates.The warning is probably tied to that. idk
Strephon Alkhalikoi said:
The easiest way to not have the message show is to lock the bootloader.
Click to expand...
Click to collapse
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
Not a stupid question. Yes you can. I don't think you'll be able to update it however, though I haven't tried.
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
Use a safetynet fix. Passing safetynet is usually all that's required. On LineageOS 20 rooted on a Pixel 5a and have all wallet, tap to pay, and problematic apps like Dasher working perfectly fine. Just have to re-flash my modified boot image after any OTA update
TheRealEdwin said:
This might be a stupid question, but is it possible to run Lineage with a locked bootloader so I can still use tap-to-pay features?
Click to expand...
Click to collapse
https://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.2 is the Git for the modded version (by the same people) of the safetynet fix plugin. (the original version of the plugin didn't work for me personally HERE is the original) install this, let it reboot, then in magisk you want to go to settings > enable Enforce DenyList > Configure DenyList(under it) and select and apps that don't work.
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