yashsingh1/xdaforums huggingface dataset:
[HTC Rezound] Cares:
Are you on v6.4? I'm using it with CleanROM DE and not having crash issues.
[Galaxy S III Themes and Apps  (US Carriers)] aznmode:
Hey guys I did not create this app nor provide support it. But I've been lurking in the SGS3 international thread trying to see how they're getting around the 11.9gb user space available on the 16gb version. It seems for us with 32gb version will suffer the same faith as there is now a partition of 12/12 pointed at by Freeza via androidcentral.com "As for storage, Sprint's offering 16- and 32-gigabyte versions. We've got the 32GB version here, and Samsung has split the storage at 12GB as internal "phone storage" (for installing apps and whatever else you want), and another 12GB that's recognized as an internal SD card". Meaning apps and data including game data is stored in the internal 12gb user space. So this is an issue for us who game a lot as we will run out of space quickly.

A post by Michael_P over at the sgs3 international thread mentioned an app called Directory Bind and have confirmed that it works. Much thanks to him for bringing this up.

http://xdaforums.com/showpost.php?p=27872500&postcount=121

Here is more info of the app as well as the dev who created it. Kudos to slig for this app.

http://xdaforums.com/showthread.php?t=1410262

For anyone who would like to give this a try please post your result. If it does work please give thanks to slig for creating this great app. He deserves all the credit.
[Galaxy S III Themes and Apps  (US Carriers)] myn:
Great post. Thanks.

We should be able to change the mounts and/or symlinks in custom roms to alleviate this issue completely.

symlink /sdcard/external_sd >> /sdcard/
[Galaxy S III Themes and Apps  (US Carriers)] lgkahn:
works fine for me thanks

didnt find it through your thread but thought i would reply..

I am not binding the whole external sd but

just the sygic dirctory with 3 gig or so

it binds

/sdcard/aura

to /mnt/extSdCard/DirectoryBind/Aura

i also turned off persistant service (saves battery and not needed) and had to turn on alternate database mgmt. (otherwise the mount was there at boot and still worked, but didnt show up in the app anymore until you restored your database and remounted (assuming you backed up database in the first place))
[Galaxy S III Themes and Apps  (US Carriers)] aznmode:
Thanks for the input! Greatly appreciated! If this works out then I may end up returning the 32gb (if I ever get it from sprint) and just go with the 16gb.
[Galaxy S III Themes and Apps  (US Carriers)] aznmode:
Some are having good luck on the original thread with their s3 as well. So good sign.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] x5starguerillaa:
Its question time again people!

So, is there any device out there (I'm guessing Bluetooth compliant) that could be used to remotely turn on our video recorder on our notes?

Or is it possible to re-map a hardware button to automatically set off recording? Maybe a long press on volume down will trigger it to record for example?

I'm curious for sports reasons, (not for leaving my phone in a ladies changing room or anything like that).:p
[Samsung Galaxy Nexus] segv11:
[APP][2015-01-12][root][GNex/Dev] BootUnlocker for Nexus Devices -- version 1.6.1

NEW

: beta version available!

[SIZE="+2"]BootUnlocker for Nexus Devices -- Unlock your bootloader without fastboot.[/SIZE]

This application REQUIRES a Galaxy Nexus (maguro, toro or toroplus), Nexus 4 (mako), Nexus 5 (hammerhead), Nexus 7 2013 (deb or flo), Nexus 10 (manta), OnePlus One (bacon / A0001), OnePlus 2 (OnePlus2), OnePlus X (OnePlus / ONE / E1001), YU Yuphoria (lettuce / YUPHORIA), YU Yureka (tomato / YUREKA), Lenovo Zuk Z1 (ham / Z1), InFocus M810 (VNA), InFocus M812 (VN2), or Yota Phone 2 (yotaphone2), with root.

You've rooted your device, and you are trying to decide between the security of relocking your bootloader (with stock recovery and USB Debugging off), and the flexibility of leaving it unlocked.

You know that in order to prevent an unauthorized user from accessing your data by flashing a custom recovery, "fastboot oem unlock" wipes your data. This also means that if you relock your bootloader, you will need to do a full backup-and-restore whenever you decide to unlock it again.

BootUnlocker for Nexus Devices lets you have the best of both worlds by using root privileges to unlock your bootloader from within Android, without wiping your data. This allows you to keep your bootloader locked for security, with this application safely protected behind your lockscreen password. Whenever you want to unlock or relock your bootloader, just unlock your screen and run BootUnlocker.

License

BootUnlocker for Nexus Devices is Open Source Software, licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0.html.

You can redistribute, reuse, or modify this software as permitted under this license.

Source code is maintained on GitHub.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

For support, please leave a comment on this thread, or open an issue on the GitHub page.

STABLE version

: (a) XDA post, (b) XDA download, (c) Google Play download

BETA version

: (a) XDA post, (b) XDA download

XDA:DevDB Information

BootUnlocker, App for the Samsung Galaxy Nexus

Contributors

segv11, osm0sis

Source Code: https://github.com/segv11/boot-unlocker

Version Information

Status: Stable

Current Stable Version: 1.6.1

Stable Release Date: 2015-01-12

Current Beta Version: 1.6.3

Beta Release Date: 2017-10-29

Created 2017-07-18

Last Updated 2017-10-29
[Samsung Galaxy Nexus] segv11:
How it Works

BootUnlocker for Nexus Devices avoids using "fastboot oem unlock", with its associated "userdata" wipe. When fastboot unlocks it updates a lock status flag, stored on a partition of your device's internal storage. Device partitions, positions and state values (locked/unlocked) are as follows:

On the Galaxy Nexus, the bootloader uses position 0x000007C of the "param" partition, stored as 01 / 00.

On the Nexus 10, the bootloader uses position 0x0000224 of the "param" partition, stored as 00 / 01.

On the Nexus 4 and Nexus 5, the bootloaders use position 0x0004010 of the "misc" partition, stored as 00 / 01. The Nexus 4 and Nexus 5 bootloaders also keep a "Tamper" flag at position 0x0004014 of the "misc" partition. It is stored as 00 / 01 (untampered/tampered).

On the Nexus 7 (2013), the bootloader uses position 0x04FFC00 of the "aboot" partition, stored as 00 / 02.

On the OnePlus One, the bootloader uses position 0x000FFE10 of the "aboot" partition, stored as 00 / 01. The OnePlus One has a "Tamper" flag, at position 0x000FFE14 of the "aboot" partition.

On devices with Tamper flag locations listed above, BootUnlocker for Nexus Devices can also set and clear this flag. You can also view this flag using "fastboot oem device-info".

BootUnlocker uses root privileges to write to to the appropriate location directly, bypassing fastboot. This allows you to lock and unlock your bootloader from within Android, without wiping your "userdata" partition.

The technique used was discovered through the efforts of several contributors on http://xdaforums.com/showthread.php?t=1650830&page=13

Special thanks go to those who posted raw images of their device partitions, helped with/conducted the analysis, or put their devices in harm's way to beta test: efrant, osm0sis, iuss, Archpope, AdamOutler, NCguy, Raftysworld, Mach3.2, Meep70, Polarfuchs, and others. This application could not have been written without their contributions.

To learn more about how this app works, and plans for future functionality, follow this project on GitHub, or subscribe the application's XDA thread.

Please note that the Nexus 7 (2012 version) cannot be supported in BootUnlocker. See this XDA thread for an alternative: http://xdaforums.com/showthread.php?t=2068207
[Samsung Galaxy Nexus] segv11:
Change Log

Version 1.6.1:

Adds support for bacon / A0001 (OnePlus One)

Version 1.5.2:

Updated wording for tamper flag management

Version 1.5.1:

Adds support for flo and deb (Nexus 7 2013)

Adds tamper flag management on mako (Nexus 4) and hammerhead (Nexus 5)

Version 1.5beta2:

Experimental tamper flag management on mako (Nexus 4) and hammerhead (Nexus 5)

Version 1.5beta1:

Experimental support for flo and deb (Nexus 7 2013)

Version 1.4:

Adds support for hammerhead (Nexus 5)

Version 1.3.2 Beta:

Experimental support for hammerhead (Nexus 5)

Version 1.3:

Adds support for mako (Nexus 4)

Version 1.2.5 Beta:

Experimental support for mako (Nexus 4)

Version 1.2:

Adds support for manta (Nexus 10)

Adds status area (bottom-left) to display information about the device and app

Version 1.2 Beta 1:

Adds support for manta (Nexus 10)

Version 1.1:

Adds support for toroplus (Sprint Galaxy Nexus)

Corrects multiple-su-request issue for users of ChainsDD's Superuser app

Version 1.0:

Initial Release on XDA and Play Store

Version 0.9 Beta:

Fixed race conditions from exec()ing su on the main thread

Removed the need for busybox

Version 0.8 Beta:

New launcher icons and screenshots

Version 0.7 Beta:

Device restrictions in the Manifest to prevent installation on many non-Galaxy Nexus devices

Version 0.6 Beta:

Checks that you have a toro or maguro device before doing anything.

Makes diagnostic output to logcat.

Various code cleanups

Version 0.5 ALPHA:

First testing Release on XDA
[Samsung Galaxy Nexus] segv11:
Reserved

This post is Reserved.
[Samsung Galaxy Nexus] Smabbage:
Looks pretty slick. Can't wait to try it out. Thanks.
[Samsung Galaxy Nexus] Thegodfather156:
thanks for this OP. sweet app
[Samsung Galaxy Nexus] LoveNFC:
Excellent application. But a question:

Does this now also mean that a tech-savvy thief would be able to unlock the bootloader without wiping data? Assuming that my phone is rooted and I don't place a PIN on the lockscreen.
[Samsung Galaxy Nexus] Smabbage:
I had to backup my ROM before I jumped in feet first. Tested a lock and a unlock and I can now say it worked without a hitch. Thanks to everyone involved in the production of this APP.
[Samsung Galaxy Nexus] segv11:
Yes, if your phone was rooted and you had no PIN/password the thief could use this to unlock the bootloader without wiping data. But if you were rooted with no PIN, you've got bigger problems than this app. :)

For example: a thief (or even a "visitor") could run Titanium Backup and then copy the backup off the device.
[Samsung Galaxy Nexus] NCguy:
If your phone is already rooted and you don't have a pin then the thief doesn't need to unlock, he can just walk in and help himself.
[Samsung Galaxy Nexus] NCguy:
Segv11, congrats!

If the google play GNs use this to relock their bootloaders will a fastboot unlock do a wipe or will the play store devices still fail to wipe?
[Samsung Galaxy Nexus] Mach3.2:
I don't think it will wipe. We did not even found out why it did not wipe.

Anyway OP, do state that root is requires on Play Store.

Pressed from my Galaxy Nexus.
[Samsung Galaxy Nexus] segv11:
Thank you.

I don't have a Play Store GNex so I can't say for sure, but I imagine that they will still fail to wipe. All this app does is change the lock state flag in the param partition; and from our investigations on the other thread, neither the param partition, nor the bootloader, seem to control the no-wipe-on-unlock behavior of the Play Store GNexes. In fact, we weren't able to figure out where the phone stores that flag.

If we can figure out where the phone stores that little gem, I'd be happy to include a way to set/clear it in this app too.
[Samsung Galaxy Nexus] segv11:
Play Store link is live

The app is finally live on the Google Play store, for those of us who prefer the convenience of automatic updates:

https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
[Samsung Galaxy Nexus] LoveNFC:
Don't know how realistic this is, but I'll go ahead and request it anyways.

Would it be possible to have an option to remove the application from the app drawer, but to allow it to be launched through the dialer, in the same fashion as Cerberus?
[Samsung Galaxy Nexus] Mach3.2:
I actually had this on my mind

Pressed from my Galaxy Nexus.
[Samsung Galaxy Nexus] efrant:
Not sure why it would even matter. Having an unlocked or locked bootloader makes no difference security-wise if you are booted into Android and have root.
[Samsung Galaxy Nexus] segv11:
ChainsDD's Superuser can also do this. I would find it too inconvenient to go through the dialer, however: instead I would just get a shell and issue the same "dd" command that this app makes.

However, I've added it (Issue 27 on Google Code) to my list of desired features: perhaps the user could opt in to this feature in a preference panel.

There are other other little features I'd like to add (like the ability to reboot from within the app), and one big feature: I'd like the app to be able to flash a custom recovery without a USB connection and fastboot.
[Samsung Galaxy Nexus] osm0sis:
Fantastic news! Congrats on the hat-trick of Nexus device support. :)

Have you given any thought to the following idea?:

Also still wondering what your take on the other two matching offsets was seeing as you're a bit better at reading these things. ;)
[Samsung Galaxy Nexus] segv11:
The idea of caching the local bootloader (in both locked an unlocked state) make sense for hackers like us. It is rather a chore for regular users, and writing the bootloader is risky (and requires overriding kernel-level permissions). It could be implemented in the app, but I would be reticent to do so, as users might start bricking their devices.

As for the other matching offsets, I don't know. Based on proximity, I would guess that they are part of the command history. The "misc" partition appears to be truly miscellaneous (befitting its name) as it contains not only bootloader stuff, but ROM stuff, and lots of other goodies.
[Samsung Galaxy Nexus] segv11:
Nexus 4 support is live in the Play Store. OP updated.
[Samsung Galaxy Nexus] osm0sis:
Fair enough. I was thinking you might feel that idea was too dangerous to trust users with, but I just wanted to make sure. I'll make up a guide in the N7 section with my script and how to alter it per-device and how to keep it updated when new bootloader versions come out. :good: :)
[Samsung Galaxy Nexus] osm0sis:
a119629c89ad06c7e49bebd260df9cf3 bootloader-grouper-4.13.img

a119629c89ad06c7e49bebd260df9cf3 bootloader-tilapia-4.13.img

Exact same bootloader on both N7 devices, so I guess now we know BootUnlocker is out of the question for it entirely.
[Samsung Galaxy Nexus] osm0sis:
Not sure if you'd like to link to it or not, but here are the guide and script for the N7 which I just posted: http://xdaforums.com/showthread.php?t=2068207 :)
[Samsung Galaxy Nexus] segv11:
Thanks. OP updated.

Sent from my 4.1.2 toro Bugless Beast.
[Samsung Galaxy Nexus] segv11:
Looks like the XDA portal finally noticed our work: http://www.xda-developers.com/andro...thout-fastboot-on-galaxy-nexus-nexus-4-and-10

Sent from my 4.1.2 toro Bugless Beast.
[Samsung Galaxy Nexus] VivaErBetis:
Thank you very much! It works like a charm in my Nexus4.

BTW: I discovered this app thanks to the portal article.
[Samsung Galaxy Nexus] azrash:
Thanks for the wonderful work! Can't wait to use it for my Nexus 4 next week!

There should be another thread for this in Nexus 4 sub forum IMO. I won't notice this without the website featuring it. I am sure more Nexus 4 users would have found this in Nexus 4 forum

Thanks again!

Sent from my Desire Z
[Samsung Galaxy Nexus] VivaErBetis:
Agreed 100%. If the developer publish a thread in Nexus⁴ sub-forum pointing to this tool, it should be massively downloaded :good:

I've put a link in my signature.
[Samsung Galaxy Nexus] segv11:
I did post a thread in Nexus 4 Themes & Apps.

http://xdaforums.com/showthread.php?t=2063388

It didn't get much traffic, so it no longer shows in your list of what's new.

Sent from my 4.1.2 toro Bugless Beast.
[Samsung Galaxy Nexus] azrash:
Hi guys, I have went through the thread trying to understand this whole thing and the benefit and danger of having an unlocked bootloader vs locked bootloader but I don't have enough knowledge to understand this. (i am still reading articles that i found on Google and xda).

i have a rough picture of how things are, but they are still unclear. I appreciate it if someone can explain this whole thing in a layman term, for us that are a little new to it and maybe link it a OP for easier reference.

another question is, if i indeed have a locked bootloader using this app, but i still have a custom recovery, what kind of security risk am I into?
[Samsung Galaxy Nexus] efrant:
There is some info in this thread.

A locked bootloader with a custom recovery is not secure, because someone can just boot into the recovery and has root and full access to your data. Same with having USB Debugging enabled: there is still a way to access your data.

To be secure, what matters really is encryption. If your device is encrypted, one will not be able to access your data without your password, bootloader unlocked or not.
[Samsung Galaxy Nexus] azrash:
Thank you very much, I am learning a lot from the referred thread

Sent from my Desire Z
[Samsung Galaxy Nexus] deltatux:
No chance of making this compatible with the Nexus S?

Cheers,

deltatux
[Samsung Galaxy Nexus] efrant:
Yes, I think segv11 could easily make it compatible with the Nexus S, however, we need someone to volunteer to pull off certain partitions from a Nexus S, both while the bootloader is locked, and while it is unlocked. Are you volunteering to help out? :D
[Samsung Galaxy Nexus] steven676:
Sure, why not -- what partitions do you need?
[Samsung Galaxy Nexus] efrant:
Awesome, thanks! Since I don't have a Nexus S, I'm not entirely sure what partitions you have. Can you drill down in the /dev/block/platform folder and find the folder "by-name" and get a list by typing "ls -l" in that folder and post the partition list here.
[Samsung Galaxy Nexus] osm0sis:
Here are segv11's instructions from earlier in the thread:

Also here is me following those instructions for the Nexus 7 (2012) if you want to make sure you're following the steps correctly (also example dd commands):

http://xdaforums.com/showthread.php?p=33986295#post33986295

Cheers! :)
[Samsung Galaxy Nexus] efrant:
It's actually easier if he runs ls -l in the "by-name" folder, rather than in the "block" folder. That way we don't have to search for the names corresponding to the partition numbers.
[Samsung Galaxy Nexus] steven676:
We have both MTD (OneNAND) and eMMC flash on crespo. For the MTD flash:

shell@android:/ $ cat /proc/mtd
dev: size erasesize name
mtd0: 00200000 00040000 "bootloader"
mtd1: 00140000 00040000 "misc"
mtd2: 00800000 00040000 "boot"
mtd3: 00800000 00040000 "recovery"
mtd4: 1d580000 00040000 "cache"
mtd5: 00d80000 00040000 "radio"
mtd6: 006c0000 00040000 "efs"

I can dump any of these partitions for you if you like.

For the eMMC (I very much doubt the information you need is here, but for posterity):

shell@android:/ $ ls -l /dev/block/platform/s3c-sdhci.0/by-name
lrwxrwxrwx root root 2013-01-13 19:32 media -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-01-13 19:32 system -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-01-13 19:32 userdata -> /dev/block/mmcblk0p2
[Samsung Galaxy Nexus] efrant:
I would hazard a guess that the misc partition is what we are interested in. Can you dump that while the bootloader is unlocked, then again while locked?
[Samsung Galaxy Nexus] steven676:
Can't be that ...

$ sha1sum misc-*
e75a589cf46253fa7d602f38dff1e9d2041aaf7b misc-locked.img
e75a589cf46253fa7d602f38dff1e9d2041aaf7b misc-unlocked.img
[Samsung Galaxy Nexus] osm0sis:
On the other hand the boot blocks are in there and that's the only way to get at them since they don't have a by-name link.

Hmm misc was my guess too. If you're sure you dumped it correctly then I guess the only option is to dump all of them from the dir segv11 suggested (which would be the EMMCs I guess) and the mtds? Any mmcblk0boot0 or boot1, etc. partitions would also be interesting to see. Since you gave us the by-name we can just match them up with the platform dumps later. That media emmc one jumps at me too, is that the sdcard or something else?

Edit: Please give us that ls -Rl /dev/block output too just so we can see better what we're dealing with. :)
[Samsung Galaxy Nexus] efrant:
I guess then the best thing to do would be to dump all of them in /dev/block/ except for 1, 2 and 3 (as the lock flag wouldn't be stored in system, media or userdata). Nor would it be in boot, and unlikely in efs or bootloader.

Edit: ninja'd by osm0sis!
[Samsung Galaxy Nexus] segv11:
What version of Android are you running? Pre-ICS kernels didn't make the boot0/boot1 devices visible.

Sent from my stock 4.2.1 manta
[Samsung Galaxy Nexus] osm0sis:
Hmm not sure what to tell you.. misc still seems like the only place it could be.
[Samsung Galaxy Nexus] efrant:
Not sure what dm-0 and loop0 - loop7 are. Maybe it's in there?

I don't think it would be in any of the other ones you listed. If it is like the N1, and the lock flag is in the NVRAM, i doubt it will be possible to get it to work.
[Samsung Galaxy Nexus] osm0sis:
The GN has all those loop and more dm mounts as well. Not sure what they do, though on kernels that support zram I've seen them mount it to a new loop..
[Samsung Galaxy Nexus] steven676:
dm-* are used by the device mapper -- the kernel infrastructure which supports installing Android apps to SD card. The loop* devices are loopback devices, which are used when you want to pretend that a regular file is actually a disk.

I'm beginning to fear that this may well be the case.

Those are from ClockworkMod Recovery 5.0.2.0 -- which, come to think of it, would be a Gingerbread-era kernel. I'll try with a more recent kernel.

EDIT:

$ sha1sum mmcblk0boot*
3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3 mmcblk0boot0-locked.img
3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3 mmcblk0boot0-unlocked.img
3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3 mmcblk0boot1-locked.img
3b71f43ff30f4b15b5cd85dd9e95ebc7e84eb5a3 mmcblk0boot1-unlocked.img

All of those files are 1 MB full of null bytes.
[Samsung Galaxy Nexus] segv11:
This is a nice try, but it seems the boot0/boot1 are empty like on the Galaxy Nexus. Bootchain maybe starts in radio firmware then onto OneNAND partitions...

If we've checked all the visible OneNAND and eMMC partition, then it's either in a hidden partition or it's in NVRAM. This is going to be more difficult than we thought. Wonder why Sammy didn't do a param partition on this device...

Sent from my stock 4.2.1 manta
[Samsung Galaxy Nexus] osm0sis:
So is there a nvram dir in /data/ on the Nexus S? I also read dd can still access hidden partitions if you can actually track one down.

Edit: Hmm, or wait, it's a Samsung so the nvram usually lives in efs, no? And we found those were unchanged..

Would it be worth dumping the loops to see if any of them change with lock state, like nvram?
[Samsung Galaxy Nexus] steven676:
Would probably be easier just to see what files/disk blocks are behind those devices. I can try this at some point, though I'm not terribly hopeful (I strongly suspect they're all unattached.)