Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Just curious. There are lots of posts on the web that talk about the fact that unlocking your bootloader wipes apps and data - presumably to prevent unauthorized access to that info. But in order to unlock the bootloader, you need adb access, and with adb access, any unauthorized person could get access to that data even with the bootloader locked. So, essentially, if you've enabled usb debugging, there's no security on this info once you plug the device into a computer. If that's true, the security rationale for wiping this data on unlock is a red herring, and seems mostly to be done to scare people away from unlocking, no?

That said, I guess that raises the issue of whether you should leave usb debugging enabled on a dev mode phone. Also, does unlocking the bootloader open up other major security holes? Obviously allowing arbitrary kernels to boot could be a problem, but without entering your password on the lock screen and turning on adb access (or usb mounting), can somebody get access through the bootloader (or a flashed recovery module)?

On my nexus one, usb access required you to okay it from the phone - i.e. you had to at least enter your lockscreen password in order to say okay. Just got a nexus 4, and usb access is different - you get a choice between MTP or camera mode, but I don't remember being asked whether to grant access at all (don't have it with me to check). But assuming it wouldn't be granted without the lockscreen password having been entered, I guess that's okay.

That leaves the recovery module. I guess anybody can get access to that, and a malicious user (even on a locked phone?) could restore the phone to factory settings and wipe all your data. But could they use a custom recovery module to gain access to the data? All they can do is flash any roms you've put out there, right? - can that mechanism be used to bypass lockscreen security. And in any case, is there a way to password protect recovery?

share|improve this question

closed as not a real question by Al E., t0mm13b, Liam W, Izzy, Zuul Jan 4 '13 at 12:41

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Oh, one more thing... In Android 4.2 multi-user mode, does rooting grant superuser access to all users or just user '0'? – littlenoodles Jan 3 '13 at 16:05
I saw another post that mentioned that the SuperUser app can be configured to require a password. So far, so good. But once SuperUser has granted root to an app, is that root access there for any user that uses the app? On my Nexus One, I gave ES File Explorer persistent su, and I don't need to re-grant access every time I use it. But in a multi-user world, I'd like that access for myself, but not for another user I set up... – littlenoodles Jan 3 '13 at 16:08
One point, that I don't think warrants an answer, but I think is relevant: in order to unlock the bootloader, you need adb acces - This isn't quite correct. In order to unlock the bootloader you need fastboot, which is different than adb. You can unlock a device that doesn't have debugging enabled. Also, FWIW, some of your concern seems to be with access to mass storage data/MTP over USB being insecure. It is actually considered by the OS to be insecure by nature since it is world-writable, so no personal info (contacts, passwords, etc) is stored there. App data, however, is sandboxed. – eldarerathis Jan 3 '13 at 16:10
Yes. It's handled by the bootloader, not at the OS level. – eldarerathis Jan 3 '13 at 16:31