All of the discussions I am seeing are about people trying to root their new Pixel 2 devices. They are worried they won't be able to root due to the Verizon locking and/or lack of images. My question is simple. If I buy a Pixel 2 / XL from google's site, is there anyway I can prevent the phone from being rooted and/or flashed with another (custom or google) bootloader? Can the FRP help me here? I'm just getting ramped on how google's phones work and I want to know if I can prevent evil maid attacks (someone temporarily gets access and loads malicious software on it). If someone has rooted it, is there anyway I would know? Would it have been erased? If I set the OEM unlock to disabled in the developer's options, would that prevent it, or is there a way to disable that in the recovery boot environment? I know the blackberry prevents root and I'm wondering how to achieve similar security with Pixel 2 devices.
Thanks in advance
brainysmurf said:
All of the discussions I am seeing are about people trying to root their new Pixel 2 devices. They are worried they won't be able to root due to the Verizon locking and/or lack of images. My question is simple. If I buy a Pixel 2 / XL from google's site, is there anyway I can prevent the phone from being rooted and/or flashed with another (custom or google) bootloader? Can the FRP help me here? I'm just getting ramped on how google's phones work and I want to know if I can prevent evil maid attacks (someone temporarily gets access and loads malicious software on it). If someone has rooted it, is there anyway I would know? Would it have been erased? If I set the OEM unlock to disabled in the developer's options, would that prevent it, or is there a way to disable that in the recovery boot environment? I know the blackberry prevents root and I'm wondering how to achieve similar security with Pixel 2 devices.
Thanks in advance
Click to expand...
Click to collapse
If you let people spend inordinate amounts of time with your phone, there's not much you can do to prevent someone from rooting your phone... except putting a password on it and not letting people spend inordinate amounts of time with your phone.
Sent from my Pixel 2 using Tapatalk
ajrty33 said:
If you let people spend inordinate amounts of time with your phone, there's not much you can do to prevent someone from rooting your phone... except putting a password on it and not letting people spend inordinate amounts of time with your phone.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Thanks for the answer. However this has not been true for many phones, namely the blackberry, and even some models of the Pixel (verizon). I noticed you mentioned "putting a password on it". Assuming my phone is entirely feature protected (password, encryption, oem unlock disabled...), will this prevent the the standard rooting procedures? I understand exploits may be found, but I'm not considering those seeing as they will be patched. It's the standard rooting procedures I'm concerned about. I don't want rooting my phone (without me knowing) to be an enabled feature (or possible at at all if that is feasible). My only goal here is to stop that.
Thank you
brainysmurf said:
Thanks for the answer. However this has not been true for many phones, namely the blackberry, and even some models of the Pixel (verizon). I noticed you mentioned "putting a password on it". Assuming my phone is entirely feature protected (password, encryption, oem unlock disabled...), will this prevent the the standard rooting procedures? I understand exploits may be found, but I'm not considering those seeing as they will be patched. It's the standard rooting procedures I'm concerned about. I don't want rooting my phone (without me knowing) to be an enabled feature (or possible at at all if that is feasible). My only goal here is to stop that.
Thank you
Click to expand...
Click to collapse
To root you need to have an unlocked bootloader. Unlocking the bootloader requires the OEM unlocking switch to be flipped. Getting to that point requires you to enter your password twice (unlocking the phone and enabling developer options). You also need a computer with a functional fastboot setup. Unlocking the bootloader wipes the phone and all of your personal information with it. After unlocking the bootloader you have to push some files to the phone via adb or with mtp after you have logged back into your phone. Then you have to flash twrp via fastboot and in turn flash magisk. (This is all of the to of my head. You can read the root threads for the exact details.)
The point is your phone can't be rooted without you knowing it.
Sent from my Pixel 2 using Tapatalk
PiousInquisitor said:
To root you need to have an unlocked bootloader. Unlocking the bootloader requires the OEM unlocking switch to be flipped. Getting to that point requires you to enter your password twice (unlocking the phone and enabling developer options). You also need a computer with a functional fastboot setup. Unlocking the bootloader wipes the phone and all of your personal information with it. After unlocking the bootloader you have to push some files to the phone via adb or with mtp after you have logged back into your phone. Then you have to flash twrp via fastboot and in turn flash magisk. (This is all of the to of my head. You can read the root threads for the exact details.)
The point is your phone can't be rooted without you knowing it.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Excellent. That is what I was looking for. If that is true, this phone meets my security needs.
brainysmurf said:
Excellent. That is what I was looking for. If that is true, this phone meets my security needs.
Click to expand...
Click to collapse
You don't need to be rooted for malicious software to be loaded on to your phone. Just stick with installation of apps from the play store and check the reviews/ratings and if something sounds to good to be true then it's probably best to avoid it unless you have valid sources authenticating it.
flunk03 said:
You don't need to be rooted for malicious software to be loaded on to your phone. Just stick with installation of apps from the play store and check the reviews/ratings and if something sounds to good to be true then it's probably best to avoid it unless you have valid sources authenticating it.
Click to expand...
Click to collapse
right, we already have those principles down. we're just trying to understand how vulnerable we are to specific attacks that are out there, namely the evil maid attacks. our team is extremely conservative on the basics that you are speaking of. we're just filling in the blanks for some more sophisticated attacks that are possible on the pixel, which is a new platform to us.
Thanks
brainysmurf said:
right, we already have those principles down. we're just trying to understand how vulnerable we are to specific attacks that are out there, namely the evil maid attacks. our team is extremely conservative on the basics that you are speaking of. we're just filling in the blanks for some more sophisticated attacks that are possible on the pixel, which is a new platform to us.
Thanks
Click to expand...
Click to collapse
The workflow that @PiousInquisitor stated is true for, AFAIK, every modern Android device in existence.
brainysmurf said:
right, we already have those principles down. we're just trying to understand how vulnerable we are to specific attacks that are out there, namely the evil maid attacks. our team is extremely conservative on the basics that you are speaking of. we're just filling in the blanks for some more sophisticated attacks that are possible on the pixel, which is a new platform to us.
Thanks
Click to expand...
Click to collapse
So far all the above answers are correct. I'll add a couple more. Evil maid attacks are not being used on phones/android afaik. My understanding is that a computer must be booted with a USB stick while you're not looking, installing software onto your computer/laptop and then hijacking it. So I wouldn't worry about that. Even so, keeping OEM lock in the disabled state in dev options will prevent root on your device. Also do not install unapproved software and if you are that worried you might want a scanning program that will root (no pun intended) out malicious software. I think there are a few out there.
As for FRP, it's a good idea but it can be bypassed. There are people out there that can take a stolen phone and bypass FRP for a fee of around $30. Also searching for FRP bypass will give you some ways as well. So I would not rely on that. Nonetheless they would need to wipe the device to do that and by that time you would have blacklisted the IMEI and rendered the phone useless to the thieves. You and your company seem aware and cautious. I don't think you'll run into any issues with the Pixel 2. You made a good choice.
The device software is rarely the vulnerability, it's the people using the device.
If your threat model is such that the ultimate question is "what can someone do with physical access to the device", you're dealing with zero day exploits that aren't publicly known and all of our feedback is out the window.
Telperion said:
The device software is rarely the vulnerability, it's the people using the device.
If your threat model is such that the ultimate question is "what can someone do with physical access to the device", you're dealing with zero day exploits that aren't publicly known and all of our feedback is out the window.
Click to expand...
Click to collapse
The op is gone. Not sure if she was trolling but this thread is over.
Sent from my Pixel 2 using XDA-Developers Legacy app
Related
Hi everyone, I hate to ask this question since I've been rooting and flashing ROM's for a good 3 years now.
I recently accepted a promotion at my work and I am now being given access to my work's email (through the app called "Good"). My fear is that my security is extremely important where I work because my employer is a financial institution. My question is if running anything other than stock presents any kind security risk whatsoever. I love running custom ROM's, but it's not worth losing my job.
Thanks and sorry if this is the dumbest question you've ever read.
mjs2011 said:
Hi everyone, I hate to ask this question since I've been rooting and flashing ROM's for a good 3 years now.
I recently accepted a promotion at my work and I am now being given access to my work's email (through the app called "Good"). My fear is that my security is extremely important where I work because my employer is a financial institution. My question is if running anything other than stock presents any kind security risk whatsoever. I love running customer ROM's, but it's not worth losing my job.
Thanks and sorry if this is the dumbest question you've ever read.
Click to expand...
Click to collapse
"Good for Enterprise" won't run on a rooted phone..
there are ways to bypass the root detection (google xda+good+hide+root, but if the app updates, you might have to re-hide it
with a rooted nexus 5... you could buy a really cheap used phone (with wifi), don't root it, install good and tether via your nexus 5... but you'll have to carry around two phones
if you're worried about security, stock rom, no root, stock everything, locked bootloader.
By rooting your phone as you may or may not already know, you are bypassing certain security measures in order to make manufacturer level changes such as installing roms. I personally believe because of that, your rooted phone will never be as secure as a non-rooted one. If i were you i would go back to stock and use androids built in security features (data encryption, password/pin) because no matter what app you use to protect yourself, because you are rooted there will always be a risk
Hope this helps
Great thanks for the responses. Yeah, I was a little worried about that. As much as I love rooting/custom ROM's, my job means 10x more. I'll go back to stock unrooted and locked bootloader.
Thanks again!
My opinion as a corporate email administrator and IT security and compliance policy writer.... (edit - and experienced android rooter)
Although I would always ensure my policy dictates rooted phones are not used, the risk doesn't lay within root itself. Nothing can get root without your say so and applications are sandboxed meaning they cannot Install themselves without user intervention.
So long as you follow simple rules, you should be fine
1) Use reputable custom roms. Stay away from betas, tests and leaks
2) only install reputable applications from reputable sources. Stick to play and xda. Don't be an early adopter.
3) use a secure kernel. Do not opt for insecure ones (Insecure adb)
4) keep the device password protected at all times.
5) ensure the strictest settings in the supersu app. Monitor it regularly
6) use flashify to flash stock recovery and bootunlocker to lock your bootloader - your everyday state MUST be stock recovery and locked bootloader. Unlock bootloader and flash recovery to flash roms and kernels but ensure you flash stock recovery and re lock
7) exercise common sense
Although that said:
1) if your company IT /AUP policy dictates no root, you'd better comply. I've worked in similar places where they have blanked out camera plates on blackberrys and check your messages
2) if the app doesn't work with root anyway..
Personally, if you really want corporate email on your phone AND freedom, get a second phone
Sent from my Nexus 5 using Tapatalk
rootSU said:
My opinion as a corporate email administrator and IT security and compliance policy writer.... (edit - and experienced android rooter)
Although I would always ensure my policy dictates rooted phones are not used, the risk doesn't lay within root itself. Nothing can get root without your say so and applications are sandboxed meaning they cannot Install themselves without user intervention.
So long as you follow simple rules, you should be fine
1) Use reputable custom roms. Stay away from betas, tests and leaks
2) only install reputable applications from reputable sources. Stick to play and xda. Don't be an early adopter.
3) use a secure kernel. Do not opt for insecure ones (Insecure adb)
4) keep the device password protected at all times.
5) ensure the strictest settings in the supersu app. Monitor it regularly
6) use flashify to flash stock recovery and bootunlocker to lock your bootloader - your everyday state MUST be stock recovery and locked bootloader. Unlock bootloader and flash recovery to flash roms and kernels but ensure you flash stock recovery and re lock
7) exercise common sense
Although that said:
1) if your company IT /AUP policy dictates no root, you'd better comply. I've worked in similar places where they have blanked out camera plates on blackberrys and check your messages
2) if the app doesn't work with root anyway..
Personally, if you really want corporate email on your phone AND freedom, get a second phone
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks! Yeah, I think the key here is that our policy does state that the phone being used can't be modified, so it's better that I just follow the rules.
Plus, stock Android has improved so much over the years that this is a much easier decision than it would have been back in the day when I had my LG Optimus running Froyo.
mjs2011 said:
our policy does state that the phone being used can't be modified,
Click to expand...
Click to collapse
Then its best not to. Financial companies take this sort of thing very seriously and can often see breach as gross misconduct
Sent from my Nexus 5 using Tapatalk
Thankfully a lot of the stock ROM is pretty good out of the box and just needs a few minor tweaks.
Morning all,
I have recently received my CAT S60 and I have to say, I am extremely pleased with the device out of the box. It is solid, extremely well built, battery life is amazing and camera quality is far better than the reviews led me to believe. Call quality is also the best I have ever had on any handset.
Unfortunately, I have never before owned a device without root. I have rooted most of my phones + installed a custom rom within a couple of days of opening the box. Sadly, this time round I've bought a less-popular device which is quite new and there is no existing support.
I am able to do most of the root-requiring functions with this phone (flashlight via button from locked, skip tracks with volume etc) using software workarounds, but I am already butting up against things that are pissing me off because I don't have system access, and I am so used to having it.
I've read horror stories about the lockdown function Qualcomm have applied to the 617 chips, but I now see that some phones with this chip have already been rooted (Motorola) so I am wondering, what are the chances that I will see root or a root exploit for this phone in the near future?
I'm not sure that I would sell the device over not being able to gain root, but it is really really annoying me.
I would be interested too. I couldnt even figure out how to set the s60 to downloadmode (If there is such a mode at all) to flash a custom recovery like twrp. Recoverymode is the usual volume up before poweron.
heinzherbert said:
I would be interested too. I couldnt even figure out how to set the s60 to downloadmode (If there is such a mode at all) to flash a custom recovery like twrp. Recoverymode is the usual volume up before poweron.
Click to expand...
Click to collapse
Recovery mode is volume up and power button together for 3 to 4 seconds
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
bandario said:
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
Click to expand...
Click to collapse
There is an option to unlock bootloader. It's called OEM unlocking
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
bandario said:
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
Click to expand...
Click to collapse
To be honest flicking that switch does nothing for me. I am unsure how to unlock the bootloader
On S60 bootloader is locked.
No fastboot, but you will be able to select recovery mode.
bump. I'd like to see this phone rooted.
Any progress on this or has anyone tried yet?
My SONY Z1C died on me the other day and I'd need to know if there's at least a chance to root this one.
I'm considering getting the S60 but only if I'm able to root it. An unrooted phone is barely usable to me...
Greetz and thanks in advance,
Unr3aL67
haven't tried rooting mine yet. Not felt the need to yet TBH
Mine is working pretty good without root. Only reason I'd want root honestly is to make backups, and perhaps uninstall a couple apps, but the bloatware is minimal.
Sent from my S60 using Tapatalk
Since the original question was "Is this rootable?" and lately answers have come in the form of "I haven't tried rooting mine" .... which doesn't seem much like an answer at all, to be honest .... I want to join the OP in asking this question. For those of us who have grown accustomed to the freedom and flexibility of having root access to our devices, it would be really nice to know (before making a decision to purchase) whether it is possible to obtain root on the CAT S60.
Does anyone know where to get a zip of the ROM?
After the Arstechnica review this may be my next phone. However, I really require a way to root it so that I can use iptables.
Anyone had any luck?
In response to your query we regret to inform you that we do not offer any assistance or tools to root our devices.
Click to expand...
Click to collapse
I tried contacting support about help to root, got the above back. It's a work phone so maybe it's better that I don't mess with it.
If anyone is going to root or make a custom recovery, it'll need to be without any support from the manufacturer. I mostly miss Xposed Framework for adblocking, less frequent notifications and the ability to longpress the back key to enable/disable screen rotation, the ROM itself is 99% "stock" otherwise and I have no complaints on that front.
In response to your query we regret to inform you that we do not offer any assistance or tools to root our devices.
Click to expand...
Click to collapse
This is, of course, their right, and buyer beware if you wanted a rootable phone. Still, I can't keep from being annoyed at this attitude; if I'm paying them good money for my devices, I want the freedom to do with it everything that I want, including modifying it and knowingly voiding my warranty, or even breaking it outright, if that's what makes me happy. Especially now that rooting/jailbreaking is a thing. Wanting to keep on controlling and limiting how people are able to use your product after you've sold it to them always sticks in my craw.
I guess I'll be passing on what otherwise looks like a perfect phone for me, unless some shining hero (or heroine) manages to figure out how to root a CAT S60 anyway, despite what the manufacturer might wish.
Tangib1e said:
This is, of course, their right, and buyer beware if you wanted a rootable phone. Still, I can't keep from being annoyed at this attitude; if I'm paying them good money for my devices, I want the freedom to do with it everything that I want, including modifying it and knowingly voiding my warranty, or even breaking it outright, if that's what makes me happy. Especially now that rooting/jailbreaking is a thing. Wanting to keep on controlling and limiting how people are able to use your product after you've sold it to them always sticks in my craw.
I guess I'll be passing on what otherwise looks like a perfect phone for me, unless some shining hero (or heroine) manages to figure out how to root a CAT S60 anyway, despite what the manufacturer might wish.
Click to expand...
Click to collapse
It is indeed a great phone, but the camera is sub-par. The focus takes an age compared to my Z5 Compact. I would wait for the second-generation version unless you critically need FLIR as a feature.
I've done a bit of poking around. I suspect that the bootloader could be unlocked with the commands "adb reboot bootloader" followed by "fastboot oem unlock-go".
I'm not going to do that at this point because without a custom ROM to flash there is no point in me voiding my warranty, but I believe it should be possible with USB debugging enabled, and the bootloader confirmed as unlockable.
I think this is how root will arrive on this device: by way of modifying a flashable ROM and flashing it to the device using QFIL as you would any other Qualcomm device.
The tools are all there in front of us, we just need someone with the knowledge to create that modified rom file....at this point I can't even find a factory rom to flash.
Given the recent speed and quality enhancements made available through the stock camera app, I also suspect that doing this will send us backwards to a much ****tier camera as has been the case with many sony handsets in the past.
bandario said:
There is a switch in developer options to allow bootloader to be unlocked. Maybe this, combined with factory recovery menu will set us free? Flash a modified factory rom with root enabled? The stock ROM is very clean.
Click to expand...
Click to collapse
Chuggers said:
There is an option to unlock bootloader. It's called OEM unlocking
Click to expand...
Click to collapse
bandario said:
So, flicking this switch should unlock the bootloader???
That gives me a bit of hope for some development on this handset. None of the previous cat phones have seen any real development.
Click to expand...
Click to collapse
That switch is available in a lot of devices and does nothing on a lot of them
Sent from my Lenovo A7010a48 using XDA Labs
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
graycow9 said:
Hey there remaining Verizon S3 users!
Coming from my favorite device the T959V this has been quite a trip. This device's bootloader is seemingly impossible to unlock on the 4.4.2 NE1 firmware.
I've got a slightly modified Superlite rom rolling with SafeStrap already strapped. And it is great to say the least. Added some initd and utilities. Evie launcher is pretty nice btw- recommend a try :good:
However. I still really want this thing to be unlocked. The T959V has multiple working Fro, GB, ICS, JB, KK, L, M, AND Nougat ROMS. Totally different devices yes but-- even the newer S4-S6 have cracked loaders now.
There has to be a special way to change this things firmware.
Right now I have 2 ideas to throw out to the wind-
1- Would be that there could be a way to trick the device into thinking it is receiving a new update. Maybe somehow with CSC or something. Also I saw a file named authorized.xml and was reading through to find traces of knox. Would unauthorizing knox strings somehow render it useless?
2- I was reading a suggested post about AVB boots and how they can be resigned on devices such as the Google Pixel and allows the newer patches to still install. Including what was described as a forced re-sign method.
--- Could we somehow resign the bootloader on our device so as to gain control of it? Has anybody tried anything like this since around 2015?
I'll gladly talk about all of this more whenever I feel like popping on- and atm I have no web besides this service. :silly: so no DOS updates and no shiny linux for now.
Gladly tell me that it is "impossible" but I'm not asking that. I'm trying to add some ideas to possibly do the impossible.
Edit: This seems to be an interesting lead on emmc cracking this device. It's probably why people in other threads were in search of a "dev" edition.
http://forum.gsmhosting.com/vbb/f777/unlock-samsung-devices-bootloader-emmc-backdoor-2142981/
Click to expand...
Click to collapse
I've been around this and many many other forums for years now. If there was an unlock method it would of been found years ago. Devs have long moved on from the old S3. I still have my S3 lying around, bootloader unlocked but I really haven't messed around with it for quite a long time now
And yes the dev edition would of been nice had someone actually had one, it would of of course made it easier to crack the bootloader option maybe. I don't know much about the ins and outs of the device but I know many are permanently locked and will probably never be unlocked.
As far as certain other Samsung devices being unlocked those are far and few between. VZW got smart and started just locking them from the start. This is a huge reason why I left Verizon. The S3 was my last device on big red. I since have had a Nexus 5 and 6 and now a oneplus 3t. I really don't like locked devices and the ability to unlock them and customize them just intrigues me to no end. Good luck however in finding something that may work, but I highly doubt it will ever be cracked
Sent from my OnePlus 3T
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Sent from my SCH-I535 using XDA-Developers Legacy app
Also a purposely separate post- I'm building a ROM for this locked firmware and the goal is to have some specific updated apps and yet trim it nicely so as to save space and RAM it's mostly stock style-wise but it'd be cool to re-theme it. I haven't gotten things deodexed yet- being I haven't gotten my apktools working proper yet.
Is there anybody left to be interested in this? I haven't posted anything I've made before- usually just keep them lying around for emergency flashes.
Sent from my SCH-I535 using XDA-Developers Legacy app
graycow9 said:
Ya I expected your negatude Shapes. Already seen that you have been searching but it isn't just some application you run. It's an unknown exploit that I'm sure exists. There are exploits right now that can be considered viral potentially exploiting my device as we speak. Maybe not granted my semi-precautious take on things.
Quadrooter and dirty cow could be used to exploit the S3 and gain access to a quoted "all" physical memory. So I find it hard to believe that things can't work in our favor.
Being open minded here. After all, this is technically hacking your own device. Which--
Got me thinking the other day, becausr I was setting up my laptop proper- could we run a nix distro and poke through the bootloader's parameters via exploitation tools? Referencing Kali or it's elder BTrack. But I think it is possible and I just haven't gotten around this loop mounting issue.
To be clear, running a distro ON the device. My flat is already running square.
Click to expand...
Click to collapse
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
BadUsername said:
I don't think shapes was trying to act negative at all, just stating the obvious. Nobody is going to try to unlock the Verizon S3, it's pretty much a dead end.
The unlock method used on the S5 will most likely work on this phone, but we need a developer CID to rewrite to the emmc as the series chip used on the S3 likely has the same vulnerability. This is what happened on the S5.
If you read some of the other posts (sounds like you have), we looked for an S3 developer edition but had no luck in tracking one down. For one, it's an incredibly old device. Secondly, you'd have to be semi retarded to purchase one as the original unlock method was around before the developer edition was released.
So yes, if you can find a developer S3 this will likely be an unlock method. It tricks the S3 into thinking it's a developer phone and unlocks the bootloader if the method to write it works the same as in the S5.
As for your questions,
1. I think you're underestimating the amount of security that goes into the bootloader itself. If you want to learn a lot about Android security in general, in the Android security discussion section located under general forums, there's tons of info regarding how complex this all is. But basically, in order to send an update patch, it needs to be signed (you can't just fake the signature) and it must agree with the current bootloader. The way the bootloader is written, it simply won't allow a reversion back to earlier versions or it'll abort the boot.
An easier way to think of this is understanding that the changes made are preinstalled before the actual boot. There's no way for us to change this through normal methods as the emmc has to be written to directly. There is no way to do this from download or recovery mode. Wouldn't matter if you flashed it or used and update package, they are essentially the same thing.
So the only way to actually change the bootloader is to write to the emmc directly through use of the JTAG port. This changes the code of the entire bootloader before the boot and the phone will boot up with any version of the S3 bootloader you write.
2. I think I kind of answered that?
Hope it's clear.
Click to expand...
Click to collapse
Truthfully after being around the forums for as long as I have I'm really surprised there is any interest in unlocking this device at this point in time. There are just so many other options and unlocked vzw s3s are not that hard to come by.
And I wasn't being negative it's about being realistic. Thanks for sticking up for me brother
Sent from my OnePlus 3T
Are there any updates to this by any chance, I am interested :C
any hope?
Hey guys i need your advice.
Tomorrow my Pixel 7 pro arrives and i am living in an unsupported county. I have read a lot of guides about the root etc. i just want to verify that i will be able to use the full features of the device if i rooted....like call screening, 5g etc. and how risky is to be rooted nowdays because last time i root my phone was 10 years ago....if after the mandatory things i don't install any app outside of the store and don't grant access root will my device be safe ? thank you
try hentaios In the latest update it was activated 5g in unsupported countries
m3ath said:
try hentaios In the latest update it was activated 5g in unsupported countries
Click to expand...
Click to collapse
HentaiOS for Pixel 7 Pro? Is it on Telegram or another third-party place?
ekin_strops said:
HentaiOS for Pixel 7 Pro? Is it on Telegram or another third-party place?
Click to expand...
Click to collapse
yes for 7 pro and 7
They have a channel in Telegram
I am certainly not an expert. I remember the days of flashing roms. I used to sometimes flash multiple roms a day.
Now most of the features I used to use custom roms for are already in Android.
Also if you have a Pixel you have a pretty clean version of Android.
So I don't really see the point. Maybe in your situation because you are using the phone in an unsupported country you might be able to enable some features but I would think the network bands are hardware based and either your carrier is compatible with the Pixel or not?
IMHO I would not root or install custom software on a brand new phone like a Pixel or other flagship. It generally voids your warranty and if you soft brick the device and can't revive it what do you do? Also with root you have huge security vulnerability. Pixel is supposed to be one of the most secure Android phones so why would you get rid of that benefit?
Also updates would be a pain.
If I had a free cheap phone from a carrier with a crappy version of Android that I would risk rooting and maybe installing a custom ROM but I just don't see the need on a Pixel??
robbbzilla said:
IMHO I would not root or install custom software on a brand new phone like a Pixel or other flagship. It generally voids your warranty and if you soft brick the device and can't revive it what do you do? Also with root you have huge security vulnerability. Pixel is supposed to be one of the most secure Android phones so why would you get rid of that benefit?
Click to expand...
Click to collapse
1) It doesn't void your warranty on the Pixel.
2) Root isn't a security vulnerability in and of itself but the unlocked bootloader can be if someone gets ahold of your phone. Seeing how the filesystem is encrypted though, it's not so much a risk to your data as it is to the person being able to steal the phone easier.
3) Most other phones have largely been locked down so a lot of us get the Pixel *because* it can be rooted.
robbbzilla said:
Also updates would be a pain.
Click to expand...
Click to collapse
Not too bad. Pixel Flasher makes the whole process easy. Plug into the computer, launch Pixel Flasher, download the update, click the patch image button so it makes a Magisk image, select that image, flash. It's all done with a user friendly GUI. While it's not as straightforward as updating directly on the phone, it also installs faster, so it's a worthwhile trade off.
EtherealRemnant said:
1) It doesn't void your warranty on the Pixel.
2) Root isn't a security vulnerability in and of itself but the unlocked bootloader can be if someone gets ahold of your phone. Seeing how the filesystem is encrypted though, it's not so much a risk to your data as it is to the person being able to steal the phone easier.
3) Most other phones have largely been locked down so a lot of us get the Pixel *because* it can be rooted.
Not too bad. Pixel Flasher makes the whole process easy. Plug into the computer, launch Pixel Flasher, download the update, click the patch image button so it makes a Magisk image, select that image, flash. It's all done with a user friendly GUI. While it's not as straightforward as updating directly on the phone, it also installs faster, so it's a worthwhile trade off.
Click to expand...
Click to collapse
Good to know. I thought enabling root level privileges would cause system wide insecurity.
As I prefaced my comments I am no expert and it has been a long time since I rooted my phones.
That is why it is good to ask questions and learn about the state of things now.
I didn't know that you could root a Pixel device and not void the warranty. I am used to the Samsung lock down.
Also with Pixel or with previous Nexus device it was always fun to see what new features Google would add in a new update/feature drop so I never felt the need to root a Pixel phone.
However if you like rooting and can do so without much risk then why not? I can see the fun in trying different software and gaining better control over your device.
robbbzilla said:
Good to know. I thought enabling root level privileges would cause system wide insecurity.
Click to expand...
Click to collapse
Seeing how you still have to authorize the use of root and Magisk even has added support for fingerprint verification to do so, it's not much more of a risk than having an unrooted device really.
robbbzilla said:
Also with Pixel or with previous Nexus device it was always fun to see what new features Google would add in a new update/feature drop so I never felt the need to root a Pixel phone.
Click to expand...
Click to collapse
You still get this stuff when you're rooted and even on most custom ROMs for Pixel. The only downside comes from apps that don't want to play nice. As long as I can use Google Pay, which I'm able to do after using the SafetyNet fix mod, I don't mind having to use the web browser for a banking app here and there (and right now there's only one that flat out won't work, Security Service FCU, so I'm not too put out by it).
It's a pain in the ass to enable carrier features like VoLTE, VoNR, etc. Pixel features like call screening require phenotype edits, which are also a pain in the ass.
G_Vasi said:
Hey guys i need your advice.
Tomorrow my Pixel 7 pro arrives and i am living in an unsupported county. I have read a lot of guides about the root etc. i just want to verify that i will be able to use the full features of the device if i rooted....like call screening, 5g etc. and how risky is to be rooted nowdays because last time i root my phone was 10 years ago....if after the mandatory things i don't install any app outside of the store and don't grant access root will my device be safe ? thank you
Click to expand...
Click to collapse
One bit of warning/caution, I've seen/found a lot of users on this forum who are in other countries (maybe unsupported) biggest issue would be NFC pay & banking apps not working. I personally have only seen a few select apps stated on this forum that can't be launched due to root detection that SafetyNetFix and Zygisk DenyList/Shamiko wasn't able to successfully hide, but there are some -- I myself have Wallet, Gpay, 4 banking apps, Xfinity apps, working while I've discussed with some other users the same banking app not working for them -- that, no matter how much users tried, they were unable to get it working. Supposedly there are combinations of root hiding methods and modules that have blocked mostly all of the stubborn apps, but then there seems to be some apps that merely just having an unlocked bootloader is enough to restrict their use.
So if this might be your situation where you have certain apps (most likely banking) that you can't really live without and/or use daily/frequently but they are known to not run on a rooted & unlocked bootloader device, that's the only real downside to rooting.
Other than that, I believe obtaining root on our device benefits so much far outweighing the risks. If certain things stop working, usually there are workarounds to get them to work or alternatives. If anything, particularly in your case, I don't believe you can get those features of 5G and call screening and camera sound and VPN and whatever other feature is restricted in an unsupported country without root....
So there are them pros & cons...
Thank you for your answers guys.....I also think that pros are more than cons....as far as I know and from the ways I found here my Bank apps will work normally.....and also I found a tutorial here that say it will enable all the Pixel features in unsupported countries so hopefully it will work...if by any case anyone tried it I would like to hear the feedback especially for google screening.
If I lose my phone or it gets stolen how secure is my pin protected data with an unlocked bootloader as opposed to a locked bootloader?
Pretty sure you have to wipe all to get rid of a pin, so I would say it is almost the same.
Connorsdad said:
If I lose my phone or it gets stolen how secure is my pin protected data with an unlocked bootloader as opposed to a locked bootloader?
Click to expand...
Click to collapse
There are two schools of thought on locked vs. unlocked bootloader security (both which I quote below) that I saw discussed a while back on the subject. It may not directly speak on pin protecting your data -- they discuss some on how your device is encrypted behind your pin so even if stolen, it should still be secure (enough) -- but at the very least there are ways around EFS so your device might still be of some use and/or, maybe given enough time you never know what can happen; which is discussed a bit in the quote & discussion (in the thread they do it in) below...
You could click on either posts (they are made in the same thread) to follow the discussion more (they go on for a bit, but not to too much more of a degree)...
96carboard said:
Everything will work perfectly with an unlocked bootloader. It will just give you an annoying warning screen briefly when powering on.
If you want to know about security risks, they're fairly small, and ONLY apply if your phone is handled physically by someone untrusted for an extended period of time, in which the only thing they could actually do is install a modified boot image. Under those circumstances, the device security has to be assumed compromised whether the bootloader is unlocked or not.
An unlocked bootloader will NOT allow a 3rd party to access data on the device, since it is encrypted and requires your security code to unlock.
Now, you can actually tell if they've rebooted the device, which they would HAVE to do in order to install a different boot image; the unlock screen (which they are NOT able to modify without resulting in boot failure) will tell you!
And I absolutely disagree that it is shortsighted to advise immediate unlocking. Nothing of real benefit comes from having a locked bootloader. Any sense of security you gain from it is smoke and mirrors. It can only be tampered with if someone has physical access, and if somebody has physical access, it has to be assumed compromised regardless of whether it is unlocked or not. If anything, your security is improved because it is now on your mind that it could potentially be tampered with, and you are reminded of it with the id10t warning every time it reboots.
Click to expand...
Click to collapse
bobby janow said:
Everything will not work perfectly. Let's be honest here. Look it up, some banking apps work mine doesn't. Pay will work one day and not the next. And if your bank finds out your account was hacked and your phone is unlocked and/or bypasses bank security protocols who will pay for the missing funds when they find out?
A missing device can be booted into a custom recovery and adb commands will be available to take everything on your device bypassing any security you have. With a locked bootloader that is not possible. So if you know your phone can be compromised you feel more secure? That is ludicrous and really doesn't make sense. I mean talk about smoke and mirrors.
Now that being said there are a lot of folks in your camp that say you're living a pipe dream if you think the phone is more easily hacked or info stolen. I understand that argument entirely and it's possibly correct to a certain degree. But to summarily say immediately unlock your bootloader if you don't plan on rooting because.. well just in case, is really disingenuous to a great many individuals. At the very least look up some articles on why to keep your bootloader locked, especially for someone that hasn't done it in some time, if ever. The beauty of Android is the possibility if you so desire. Just be conscience of the advice you give. Many years ago Chainfire said in his blog that if you have an unlocked bootloader and have financial apps on your device you're asking for trouble and you might want to rethink that. (not in so many words) That weekend I locked my bootloader and never looked back. I haven't missed anything.. well other than flashing MVK kernel for my 6a. ;-) But then I'd need root and that brings a host of other issues.
Click to expand...
Click to collapse