yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] segv11:
I like that wording for the second post! The Google Code docs also have a similar file, which I will update with your wording.

Sent from my stock 4.4 Manta.
[Samsung Galaxy Nexus] segv11:
New version pushed with updated wording. I'd love to nail that issue with prompting for root privs. Thank you for the feedback so far, I'm hoping I can figure out what's happening; it smells like a race condition.
[Samsung Galaxy Nexus] thegrantonstarcause:
Same issue here with SuperSU. not prompted for root access. Nexus 5, running latest 4.4.2, bootloader already unlocked and with root access.
[Samsung Galaxy Nexus] RusherDude:
I had no problems at all with a Nexus 5 (bootloader unlocked, rooted with SuperSU) running stock 4.4.2.

SuperSU never game me an issue in years..
[Samsung Galaxy Nexus] osm0sis:
Thanks! Happy to help! It's really just your wordings rearranged. ;)

I did somehow manage to typo partition as "parition" a couple times though. Fixed it in my post if you want to copy+paste again. :good:
[Samsung Galaxy Nexus] thegrantonstarcause:
Well I got to the bottom of it. Seemed XPrivacy applied a security template to the app when it was installed. After clearing this I got the SU request and it's all working.
[Samsung Galaxy Nexus] segv11:
A user reported to me in email that after flashing Franco's kernel, BootUnlocker was unable to obtain (or prompt for) root privs; reflashing the stock kernel solved the user's problem.

Anyone else experience any kernel-related issues?
[Samsung Galaxy Nexus] The Gingerbread Man:
Well who ever said that is wrong. Tested on hammerhead with Franco r30. I use SuperSu, made it forget boot loader then opened boot loader app and su prompt came up quickly. Maybe they are using the broken koush super user
[Samsung Galaxy Nexus] sordna:
I'm on Franco.kernel on a Nexus 4 (stock 4.4.2 ROM) and boot unlocker including the new tampered/untampered setting works for me. I updated bootunlocker from the play store while being on kernel r199, and SuperSU did have to prompt me to grant access after the BootUnlocker update as expected, and it worked just fine.
[Samsung Galaxy Nexus] segv11:
Well, they said they were using Kush's Superuser. But even so, it worked until he flashed Franco, and worked again after reflashing stock.

So we have a bug that appears as with a specific combination of Superuser app and kernel?!? That's just weird, and probably a race condition. I wonder what I need to do to avoid that.

Sent from my stock 4.4 Manta.
[Samsung Galaxy Nexus] The Gingerbread Man:
Advice people to use supersu
[Samsung Galaxy Nexus] sordna:
From what I see in the franco kernel threads, I think a few people reported having superuser problems in general, not for your specific app, so you don't need to do anything. By the way, I like the Tampered/Untampered wording, it's crystal clear.
[Samsung Galaxy Nexus] rockingondrums:
Wow, I was a couple versions behind. Deb support, yay! Thought the last consensus was that it couldn't be supported. Great work people!
[Samsung Galaxy Nexus] gigsaw:
Sorry for the stupid question but what happens if i relock the bootloader while I have a custom rom and a custom recovery on my device? Will I brick my phone?
[Samsung Galaxy Nexus] AK1149:
I will not brick your phone. I am doing it currently.
[Samsung Galaxy Nexus] gigsaw:
And are you able to flash roms trough custom recovery, as usual? Thank you so much for the reply
[Samsung Galaxy Nexus] AK1149:
Ya! You can flash anything from the recovery.
[Samsung Galaxy Nexus] rockingondrums:
The reason for unlocking the bootloader is primarily so you can flash a custom recovery, which in turn allows many awesome things for your phone.

Now, if you have a locked bootloader you of course won't be able to flash NEW recoveries (or radios, or bootloaders) until you unlock.

Reread OP, use app, profit.
[Samsung Galaxy Nexus] AK1149:
I flashed a flashable zip recovery without problem. I think you can't flash using the bootloader only, but you can through recovery.
[Samsung Galaxy Nexus] segv11:
Correct. You can also flash from within Android by writing directly to the raw partitions, like ROM Manager and GooManager do.

Sent from my Shiny 4.4 toro.
[Samsung Galaxy Nexus] rockingondrums:
Both true. I meant by using fastboot in bootloader. I got the new radios and forgot to unlock and it failed. I haven't used ROM manager in year(s?) or goomanager since it was down. I'm even using adb just to push music now. Stupid mtp....
[Samsung Galaxy Nexus] SEK610i:
Anything new on the Nexus S case?
[Samsung Galaxy Nexus] segv11:
We weren't able to figure out a solution for Nexus S, but it has been a while since anyone tried.

Sent from my Shiny 4.4 toro.
[Samsung Galaxy Nexus] blackdragon12:
If I unlock my Nexus 5 bootloader (using fastboot), then install SuperSU for root, then install my rooted apps, install BootUnlocker to relock the bootloader, will my rooted apps keep working?
[Samsung Galaxy Nexus] sordna:
Yes. How else would BootUnlocker be able to unlock the bootloader? It'a a rooted app itself! An unlocked boot loader is only needed to flash images like Roms and recoveries. You can still install and run rooted apps, flash zips through custom recovery, etc with a locked boot loader.
[Samsung Galaxy Nexus] droidshadow:
will this work for verizon nexus 7 32GB 2013?..

Hey guys so i have the Neuxs 7 32GB 2013 wifi only model and i already rooted that tablet, unlocked the bootloader, installed multirom and flashed several roms.

I liked the Nexus 7 tablet so much that I decided that I wanted to go with 4G model of the Neuxs 7 which is i believed

code name "DEB"

right?

My question is, I have Verizon as my wireless provider. Now I know that Verizon has a habit of encrypting their bootloaders so that no one can unlock them like they did with the S4 and the NOTE3.

If i decide to purchase the Nexus 7 2013 32GB 4G/LTE model tablet from Verizon, can I unlock the bootlader? Since Nexus is a google product i am almost certain i can, but I would hate to spend $300+ dollars and not be able to customize the tablet the way i want it!

If anyone has a verizon 4G/LTE tablet could you let me know if you had any problems unlocking the bootloader?

Thank you all so much for your assistance!

-droidshadow
[Samsung Galaxy Nexus] The Gingerbread Man:
I own a flo but being a nexus it should be as simple as fastboot OEM unlock (I think is the command off memory) i think they use the same boot loader, not 100% sure though as there is hardware differences between the two models. [MENTION=4544860]osm0sis[/MENTION] should be able to give a more precise answer
[Samsung Galaxy Nexus] osm0sis:
Identical bootloader. They just name it differently in the factory images. Should have no problems with fastboot or BootUnlocker (once you have root). :good:
[Samsung Galaxy Nexus] droidshadow:
great news!

Thank you so much osm0sis, i figured that since it is a google product that I should be able to unlock the bootloader with fastboot or this app without any problems but i wanted to be sure before i spent the money.

Thank you so much for your response!

-droidshadow
[Samsung Galaxy Nexus] segv11:
Quite true.

I wouldn't use that option, but maybe some users would appreciate the ability to hide the app from friends that borrow their phone. I put it on my list. In the meantime, people running Apex Launcher can hide _any_ app from the app tray, via a preferences option.

P.S. I like your "how to line" in your signature block. Especially #6. ;-)
[Samsung Galaxy Nexus] efrant:
This should be quite simple to implement, given that it is just one dd command.
[Samsung Galaxy Nexus] segv11:
The Play Store description mentions it that you need root:

BootUnlocker for Galaxy Nexus -- Unlock your bootloader without fastboot!
This application REQUIRES a Galaxy Nexus (GSM or Verizon) with root.

I wanted to put "[root]" in the title to make it more obvious, like Chainfire does, but it wouldn't fit in the 30 character limit.

EDIT: It would be nice if "ROOT" were one of the permissions you can declare in the Manifest so that the Play Store would let you know front-and-center that root is required. :-) That's not ever going to happen, however, for obvious reasons.
[Samsung Galaxy Nexus] efrant:
I will change it to link to your thread, now that you have your app out.

EDIT: Done! :)
[Samsung Galaxy Nexus] segv11:
True, it's simple in principle but the UI should try to protect the user form mistakes, which makes it a "bigger" feature:

To protect the user, the UI should provide you a way to browse your sdcard for recovery images, verify their MD5 hashes, and verify that they are in fact recoveries for the right phone.

It would also be appropriate to help the user choose if it is a permanent or temporary change by helping them rename their "recovery_from_boot.p" if they have one.
[Samsung Galaxy Nexus] Mach3.2:
-delete-

Pressed from my Galaxy Nexus.
[Samsung Galaxy Nexus] segv11:
I have confirmed a user-reported issue. This will get fixed in a later version:

Users of ChainsDD's Superuser app will be prompted twice for root access. This is because Superuser treats different command lines as different authorizations, and it prompts and logs each separately.

Users of Chainfire's SuperSU will not experience this issue because SuperSU authorizes by requesting app only.
[Samsung Galaxy Nexus] jimmyhook:
Clicked link, went to Play Store, and it said error file cannot be found when I attempted download. Hopefully temporary....

EDIT: went to the Web play store and it says it is incompatible with my device. Verizon GNex.... ?
[Samsung Galaxy Nexus] Mach3.2:
Weird, the developer is using a toro.

Pressed from my Galaxy Nexus.
[Samsung Galaxy Nexus] segv11:
That is weird... Not only do I use a Verizon Galaxy Nexus, but I downloaded the app from the store to make sure it allows me to do so.

The Play Store filtering function is really weak if you want to limit to specific devices: it wants you to select on features. To get just Gnex I selected devices with normal-sized xhdpi screens, NFC, multi-touch, and 4.0+... and then I still had to manually remove 20 other devices (like SGS3) to get it down to just maguro and toro.

Could you send a copy of your build.prop (or run getprop in a shell and send the output) and I'll see if I can figure out why the Play Store isn't letting you download it. Meanwhile, the download is also hosted on Google Code if you are OK with sideloading it.

Is anyone else with a toro having issues downloading it?
[Samsung Galaxy Nexus] jimmyhook:
I'll send it this evening, but just occurred to me that I'm running Paranoid android with tablet mode/ hybrid. Perhaps dpi issue?
[Samsung Galaxy Nexus] segv11:
That's a good guess. If your custom ROM tells the store that you have a tablet-sized screen, then it won't let you download because it's set to "normal" sized only. So yeah, it could be screen size or DPI filtering that's messing you up.

In a later version, I can remove some of these restrictions, but that means that I need to manually filter out a larger number of devices. The sideload version should work OK, though. Or: can you tell your ROM not to show up as a tablet and try the Play Store again?

EDIT: According to the Play Store, seven of you have downloaded this from a toro device. Any problems?
[Samsung Galaxy Nexus] segv11:
According to the Play Store Developer Console, exactly two of you are using the app with Android 4.0-4.0.2. Whoever it is, is it working OK for you on that platform?

(PM me if you don't want to admit in public that you've not flashed 4.0.4 yet. ;-) )
[Samsung Galaxy Nexus] segv11:
Nexus 7

I'm liking what I saw of the Nexus 7. Once we can get out hands on it, I would love to see how it handles bootloader locking/unlocking.
[Samsung Galaxy Nexus] jimmyhook:
Just ran Paranoid in phone mode, and I was able to download it. Definitely was the tablet mode preventing it. Thanks for making this app and the quick response :)
[Samsung Galaxy Nexus] segv11:
It looks like you already have a resolution to the problem, but I have opened and issue for it anyways. If there are enough Tablet-mode users who are unable to download the app, I'll look into different ways of filtering on the Play Store.

Of course, if the Nexus 7 turns out to be as easy lock and unlock as the GNex, then I may be able to expand support to that device as well at some point. If any of you were at I/O and got a free N7 feel like rooting it and monkeying with its bootloader, please let me know. :-P
[Samsung Galaxy Nexus] segv11:
unavailable 2012-06-29 to 2012-07-01

I will be unavailable 2012-06-29 to 2012-07-01

If you have any urgent issues on this thread that need attention, please try to let me know in the next few hours.

After that, I will be unavailable Friday and most of the weekend. I will respond to all queries when I am able to get back on XDA: probably Monday.
[Samsung Galaxy Nexus] canofale:
Even though I am Not one of these two, I'll admit that my wife's GNex is still running 4.0.2. It's from western Europe so it never updated to 4.0.4. She just won't let me do anything fun to it. But tonight its late and I can't sleep so she's gonna wake up to some nice new Jelly Bean! I rooted it and downloaded this from the Play store and it worked Great! Now its time for some 4.1 baby. He-He-He... she is going to love it. I am so getting laid tonight!
[Samsung Galaxy Nexus] efrant:
LOL!!!
[Samsung Galaxy Nexus] sgp77:
Sorry if this is an obvious question, but does it make sense to lock your bootloader if you have a custom recovery? If you can flash any ZIP in a custom recovery, what added security does it buy you?

To that point, I've always wondered how secure lockscreen PINs were when you're rooted. It seems like anyone could disable security from recovery by flashing the right ZIP or deleting the right file.
[Samsung Galaxy Nexus] steven676:
You're right -- locking the bootloader doesn't buy you any real security unless you also use a locked-down recovery. That said, with the ability to unlock the bootloader from the running system, you can keep the bootloader locked with a standard recovery installed, and then unlock the bootloader only when you need it. (That's exactly what I do -- I run my Galaxy Nexus with locked bootloader and stock recovery most of the time, and only unlock the bootloader when I want to make changes.) Alternately, you could use something like ROM Manager to flash a custom recovery from the running system without first unlocking the bootloader.

You can have root on the running system without having a custom recovery installed, and in that case, the screen lock should prevent anyone without access from getting far enough to be able to use root capabilities. (Again, if the bootloader's unlocked or a custom recovery is installed, all bets are off, as you note.)
[Samsung Galaxy Nexus] efrant:
I agree with most of your points above; however, even if you have a locked bootloader, stock recovery, no root and a strong lockscreen password, someone can still easily get access to your data (particularly on the Galaxy Nexus). I think I've mentioned it before in this thread, but there is certainly a link to a guide (that explains how to unlock your bootloader without root, without a custom recovery and without wiping anything) in post #2 in the stickied "Android 101" thread.

If you are worried about data security, you need encryption.
[Samsung Galaxy Nexus] steven676:
In that case, not even encryption can save you from an attacker who wants your data. If I can install arbitrary software on your device (which, if I can unlock the bootloader, is a given), I can take an image of your device, install malware on it, and then return it to you (turn it into a lost and found, leave it where it was found ...). The next time you unlock your device, it'll send the decryption key for your data to me. (There are other ways to skin this cat -- I could just install a remote access tool and then use it to grab data without having to first take a full image, for instance.)

Bottom line: if you cannot stop someone from installing software on your system, there is no security measure -- encryption, screen locking, whatever -- that can protect your data.
[Samsung Galaxy Nexus] efrant:
How do you install software on an encrypted partition without having the decryption key?

But yes, I agree: if someone wants your data, there are ways to get it even with encryption - - encryption just makes it significantly more difficult to obtain it (while a locked bootloader does not make it much more difficult to obtain it).
[Samsung Galaxy Nexus] steven676:
/boot's not encrypted. /system isn't either. (You could use secure-boot-type signature verification in the bootloader to increase the difficulty of attacking the boot chain, but as far as I know none of the Nexus devices implement that.)

"Difficulty" is relative -- encryption (with a strong password) without the ability to block software installation is probably enough to deter casual snooping, but the attack I described is well within the capability of a single reasonably skilled individual (and pretty easy if you're in industrial espionage, organized crime, or government). The question, as with all questions of security, is what your threat model is; if it includes a targeted attack by someone with a bit of time to spare, then I think we've established the Galaxy Nexus is not the phone for you. If that is part of your threat model, then a device that doesn't allow drive-by software installation is a must.
[Samsung Galaxy Nexus] Sumanji:
Hey,

Apologies if this has been asked before but searching the thread for "S" isn't very effective :p

What is the main barrier to making this app effective for the Nexus S?

Also, what are the barriers that prevent this app (or the idea behind this app) from being used on any other device? I.e. why Nexus only?

Cheers,

Su
[Samsung Galaxy Nexus] segv11:
We need "fastboot oem unlock" and "fastboot oem lock" to support a device. So far, that has been Nexus devices though we could theoretically try a Google Play Edition device, if someone has one they want to hack. Also, the device needs to write the lockstate in internal storage location that we can access through a block device (as root) from within the running Android system. If it uses NVRAM, or a magic location in the radio firmware, or worse a q-fuse, then we can't support it.

So far, we have been able to support Nexus devices, except:

Nexus One (passion): Has "fastboot oem unlock" but not "fastboot oem lock", so we can't toggle it and watch what changes.

Nexus S (crespo & crespo4g): We tried, but we couldn't see where it was changing the lockstate. We think perhaps NVRAM, but we could try again.

Nexus 7 2012 (grouper & tilapia): This uses device-specific encryption and writes the lockstate directly to the bootloader image. This is fairly dangeous to tamper with, so we don't date to support it. However, see this script from osm0sis:
[Samsung Galaxy Nexus] Sumanji:
Hi segv,

Thanks for replying! So is it only certain devices (i.e. only Nexus / GPE) that support simple unlocking via fastboot / bootloader? I have only ever done it this way (on Nexus S and Nexus 7) so I just assumed this was the same with all phones!

For example I have a Moto Razr HD which is also simply unlocked via fastboot (as per here). Could the device in theory be supported by this app?

Cheers,

Su

[edit] My bad, apparently the Razr HD doesn't support the lock command... I am keen to help on the Nexus S front in any way I can though!
[Samsung Galaxy Nexus] segv11:
I probably won't be able to devote appropriate time to the analysis for the Nexus S until late May. But perhaps others in our community could help, we have folks in here who have figure out devices that I gave up on.

Sent from my stock 4.4.2 manta.
[Samsung Galaxy Nexus] Zedd.:
Thank you for the excellent app, segv11!

I hope you don't mind but I saw a reviewer on the Play Store asking for a better logo and you asking if anyone were interested in contributing one. So, I've had a go at it (although I'm a design enthusiast and hardly a graphic designer).

Here's a larger version.

Cheers.
[Samsung Galaxy Nexus] Globespy:
Nexus 5, stock based ROM and TWRP - security question

Im running latest KangaKat with elementalx and latest TWRP.

If I encrypt my phone then use your app to relock the bootloader (TWRP works well with full phone encryption), can my device still be accessed by an intruder using something like FROST custom recovery?
[Samsung Galaxy Nexus] sordna:
The current bootunlocker icon looks just fine to me! I hope it is not changed just because a random reviewer doesn't like it.

I mean people that like it wouldn't leave reviews about it and there probably are far more users that like it than those that don't!
[Samsung Galaxy Nexus] VivaErBetis:
+1
[Samsung Galaxy Nexus] colin p:
Now easier to root and unlock bootloader

Just in case someone comes to this thread and doesn't realize that root is now possible within android using towelroot.

Not sure if I put the right info in for the URL.

[How-To] Root and unlock the bootloader without wiping data

http://xdaforums.com/nexus-4/general/how-to-root-unlock-bootloader-wiping-t2784553
[Samsung Galaxy Nexus] el_charlie:
This app is awesome on my Nexus 4.

But, do you intend to make it work in other unlockable devices? Like the Moto G?

Cheers!
[Samsung Galaxy Nexus] Polarfuchs:
I want to find out the place where the lock bit and tamper bit is on my oneplus one.

Is there a way to find the tamper flag, without unlocking and tampering the device?

EDIT: strange, my device already shows tampered. Maybe because I unlocked developer options in android.
[Samsung Galaxy Nexus] Polarfuchs:
Hi,

could you add support for the Oneplus One?

The bit for unlocked bootloader is at 0x000FFE10 in the aboot partition as you can see in my screenshot.

The tamper flag should be at 0x000FFE14
[Samsung Galaxy Nexus] huawhat:
It would be awesome if this had functionality as a tasker plugin so I can unlock bootloader at home and lock it when away
[Samsung Galaxy Nexus] SnZ:
+++1
[Samsung Galaxy Nexus] ilamaan:
If I unlock the bootloader with a custom recovery existing in it, then would I be able to flash boot.img without unlocking the bootloader?
[Samsung Galaxy Nexus] FredFS456:
Your post makes no sense.

1. Recovery does not exist 'in' the bootloader.

2. If it's unlocked, then it's... unlocked. Flash whatever you want. This app simply bypasses the data wipe originally necessary to unlock the bootloader.
[Samsung Galaxy Nexus] ilamaan:
No thanks for the helpless post.

1. I asked whether I can access the recovery if I lock bootloader whilst I had a custom recovery installed (Yeah, I have an unlocked bootloader)

2. Well yeah I am not dumb enough not to understand how this tool works.

and

3. Ignore posts that makes no sense to you.
[Samsung Galaxy Nexus] FredFS456:
Okay alright, that makes a little more sense.

1. Yes, you can access your custom recovery. I've forgotten to unlock my bootloader sometimes when flashing, it just... doesn't do anything if you don't unlock.

2. This is a tool to unlock your bootloader on demand without needing to wipe your data. Basically same as "fastboot oem unlock" and "fastboot oem lock" when attached to a PC, but without the wiping. Got it?
[Samsung Galaxy Nexus] ilamaan:
1. So it successfully flashes in locked bootloader or not?

2. Yeap, I do know the purpose of the tool, which I just mentioned that I am not dumb to not understand that.

:cyclops:
[Samsung Galaxy Nexus] FredFS456:
1. No it does not successfully flash. In fact, if I remember correctly it just fails silently, i.e. it seems like it flashes, but doesn't. Also, wiping/formatting doesn't work correctly either (again, fails silently).

2. Sorry about that, I didn't see your double negative.
[Samsung Galaxy Nexus] jpjdlv:
Hi there, i gotta send my n5 to google (warranty) i made my N5 go stock again + unrooted + locked boot.

I gotta run the Nexus BootUnlocker script too?

Or i´m ok?
[Samsung Galaxy Nexus] FredFS456:
If you already ran "fastboot oem lock", then you're fine. This app (or the script from the mighty osm0sis) does the exact same job, just in a more convenient (and less data-wipey) method.