Related
So guys I just had my Nexus 5 stolen at the gym a couple of days ago, I'm very furious about it... I'm unable to track the device with Android Device Manager because the device was dead at the time it had been stolen and probably hasn't been turned on since.
As I imagine the thief will probably fastboot the phone and erase everything, before ever turning it on, or selling it.
My question is, is there not a way to put a startup password on the phone to prevent bootloader/download mode/adb/fastboot access to the phone?
I am also very upset because I called into Google, and there is absolutely no way to have the phones Serial/IMEI "flagged" or "blocked" with Google. Which would be technically such a simple system to implement.
This means that all those people who have had their Nexus 5's stolen, the device can just be re-registered with another Google account at a later date and nobody will blink an eye.
Views? Suggestions?
Thanks
Wow that sucks you can encrypt your phone that requires a password to startup you may have to have a password to enter fastboot if you encrypt it not sure never done it
Sent from my Nexus 5 using Tapatalk
Call your carrier to have the IMEI blacklisted. Google can not do this. It's your carrier's job to blacklist.
black listing the IMEI won't prevent somebody from re-registering that device with another Google account though. As it seem Google doesn't track or flag stolen Serial/IMEI.
BUMP to confirm Does encrypting the phone ask for a password at startup?
THE_KINGDOM said:
blacDoes encrypting the phone ask for a password at startup?
Click to expand...
Click to collapse
Yes.
THE_KINGDOM said:
black listing the IMEI won't prevent somebody from re-registering that device with another Google account though. As it seem Google doesn't track or flag stolen Serial/IMEI.
BUMP to confirm Does encrypting the phone ask for a password at startup?
Click to expand...
Click to collapse
no, but it will prevent the thief from using it on any US or Canadian carrier.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
THE_KINGDOM said:
black listing the IMEI won't prevent somebody from re-registering that device with another Google account though. As it seem Google doesn't track or flag stolen Serial/IMEI.
BUMP to confirm Does encrypting the phone ask for a password at startup?
Click to expand...
Click to collapse
Sandman-007 said:
Yes.
Click to expand...
Click to collapse
can still flash the factory img in the bootloader and not worry about the encryption. also, every single person ive known that has encrypted, eventually(weeks/months) got locked out of their own phones eventually because it wouldnt except a password, and had to flash the factory img.
simms22 said:
no, but it will prevent the thief from using it on any US or Canadian carrier.
---------- Post added at 12:56 PM ---------- Previous post was at 12:52 PM ----------
can still flash the factory img in the bootloader and not worry about the encryption. also, every single person ive known that has encrypted, eventually(weeks/months) got locked out of their own phones eventually because it wouldnt except a password, and had to flash the factory img.
Click to expand...
Click to collapse
Right but the whole point of encrypting is to protect the data not the device. So if a thief has to wipe the device to get rid of the encryption then he won't be able to access the data. It's gone.
Sandman-007 said:
Right but the whole point of encrypting is to protect the data not the device. So if a thief has to wipe the device to get rid of the encryption then he won't be able to access the data. It's gone.
Click to expand...
Click to collapse
no, its not gone. its relatively easy to recover the data, even after a factory reset, if the thief wanted to. unless the data is written over.
There is an app here on XDA as well as the play store called "bootunlocker" that allows you to lock and unlock your bootloader. Newer versions of Trickster MOD also do this. This way, if someone finds your phone and fastboot OEM unlocks it, it will wipe everything. The only thing we need to do at this point is secure the recovery. As no one seems to think a password protected recovery is necessary as no one has made one, you would have to flash the stock recovery.
If you need to make a nandroid then you would need to unlock and flash custom. This is the only way I can think of to fully ensure data gets wiped in the event someone really knows what they're doing. I might go this route, at least for a little bit to try it out
rockingondrums said:
There is an app here on XDA as well as the play store called "bootunlocker" that allows you to lock and unlock your bootloader. Newer versions of Trickster MOD also do this. This way, if someone finds your phone and fastboot OEM unlocks it, it will wipe everything. The only thing we need to do at this point is secure the recovery. As no one seems to think a password protected recovery is necessary as no one has made one, you would have to flash the stock recovery.
If you need to make a nandroid then you would need to unlock and flash custom. This is the only way I can think of to fully ensure data gets wiped in the event someone really knows what they're doing. I might go this route, at least for a little bit to try it out
Click to expand...
Click to collapse
wiping isnt a solution, as the wiped data is easily recoverable. and password protection for a recovery exists as well, twrp has it. and it also wont help as all you would have to do is flash another recovery via fastboot.
btw, heres a recent article about recovering data from a wiped phone http://www.theverge.com/2014/7/8/5881573/test-shows-data-can-be-recovered-from-wiped-android-phones
simms22 said:
no, its not gone. its relatively easy to recover the data, even after a factory reset, if the thief wanted to. unless the data is written over.
Click to expand...
Click to collapse
Fairly easy as in yes, I could do it. Fairly easy as in a random thief on the street, probably too much trouble and effort.
simms22 said:
wiping isnt a solution, as the wiped data is easily recoverable. and password protection for a recovery exists as well, twrp has it. and it also wont help as all you would have to do is flash another recovery via fastboot.
Click to expand...
Click to collapse
That's why the boatloader is locked. Yep, TWRP implemented Philz recovery lock.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
That's why the boatloader is locked. Yep, TWRP implemented Philz recovery lock.
Click to expand...
Click to collapse
Haven't tried it, but what happens if you just flash another recovery?
Lethargy said:
Haven't tried it, but what happens if you just flash another recovery?
Click to expand...
Click to collapse
How could you flash another recovery?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
How could you flash another recovery?
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
If your bootloader wasn't locked lol
Lethargy said:
If your bootloader wasn't locked lol
Click to expand...
Click to collapse
Obviously recovery lock is pointless if either android or bootloader is unlocked.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
I say keep trying to locate the device with the Android Device Manager. The thief might not have charged it yet, or even won't at all. Might not be charged until someone buys it. Keep trying, and good luck.
rootSU said:
Fairly easy as in yes, I could do it. Fairly easy as in a random thief on the street, probably too much trouble and effort.
That's why the boatloader is locked. Yep, TWRP implemented Philz recovery lock.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
the average theif, i absolutely agree. they want to steal the device and collect money for it. but if someone is specifically looking for your data, now that doesnt sound like the average thief, thats who i would want to keep away.
bootloader locked, then unlocked, back to that data being recoverable, not by your average thief.
simms22 said:
the average theif, i absolutely agree. they want to steal the device and collect money for it. but if someone is specifically looking for your data, now that doesnt sound like the average thief, thats who i would want to keep away.
bootloader locked, then unlocked, back to that data being recoverable, not by your average thief.
Click to expand...
Click to collapse
As I've said to you in another thread, there's no protection against that and that's the same with any file system.
Working on national security issues? Don't save data on your phone.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
rootSU said:
As I've said to you in another thread, there's no protection against that and that's the same with any file system.
Working on national security issues? Don't save data on your phone.
Sent from my Nexus 5 using Tapatalk < Yes, I want you to know that I'm using a mobile client
Click to expand...
Click to collapse
lmao!
whats funny is that either we misunderstood each other, or a penguin was just spotted in the sahara desert(lol), because what you said is what i keep trying to say, theres no real protection. the best protection is that tbe average person doesnt have enough knowledge, patience, time to go after your data on a serious level. but those that are specifically targeting you for your data, those are who you should fear, as the data can be gotten to, if they really want to get it.
simms22 said:
if they really want to get it
Click to expand...
Click to collapse
It's all in the "if"
In my opinion the only worth protecting against would be the sneaky little brother or sister.
Just seen this by droid modder x on YouTube will this work on our device I don't wanna screw my device up that's why I'm asking here's the link too
http://droidmodderx.com/how-to-root-any-and-all-android-devices-with-one-click-root-app
Sent from my A0001 using XDA Premium HD app
I would follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
^this will help you do the unlock, root, flash for our amazing phone. Also there are rootkits and some people say to not use them but that is a personal preference.
But would that screw up the device if I did use the king root app ?
Sent from my A0001 using XDA Premium HD app
ward24 said:
But would that screw up the device if I did use the king root app ?
Sent from my A0001 using XDA Premium HD app
Click to expand...
Click to collapse
The question is why would you even use that app when you don't need to? Exploits and hacks aren't needed on this phone, all you need to do is go to my guide that you've been linked to above and follow the instructions to unlock your bootloader and root your device.
XDA Moderator
Transmitted via Bacon
Yes sir!!!
Sent from my A0001 using XDA Premium HD app
Rooted now thanks Heisenberg!
Sent from my A0001 using XDA Premium HD app
Good Morning, just a little information, there is no way to install super SU zip file with the stock cyanogen recovery? I need root to change timestamp of some video files that I copied into my OPO (MTP chaged all of them to the date of when i copied these files) and a rooted phone is the only option.
Thanks.
kingnappa said:
Good Morning, just a little information, there is no way to install super SU zip file with the stock cyanogen recovery? I need root to change timestamp of some video files that I copied into my OPO (MTP chaged all of them to the date of when i copied these files) and a rooted phone is the only option.
Thanks.
Click to expand...
Click to collapse
No, you can't flash SuperSU with the stock recovery. You need to unlock your bootloader and install TWRP.
XDA Moderator
Transmitted via Bacon
Heisenberg said:
No, you can't flash SuperSU with the stock recovery. You need to unlock your bootloader and install TWRP.
XDA Moderator
Transmitted via Bacon
Click to expand...
Click to collapse
That's what I thought, thanks.
BTW has anyone used thik Kingroot app? Does it work? Because I don't want to unlock bootloader and lose everything again just for my videos-
kingnappa said:
That's what I thought, thanks.
BTW has anyone used thik Kingroot app? Does it work? Because I don't want to unlock bootloader and lose everything again just for my videos-
Click to expand...
Click to collapse
You don't have to lose everything, just back it up first. Of course you probably wouldn't be in this position if you had properly researched the phone when you decided to buy it.
XDA Moderator
Transmitted via Bacon
Kingroot does not root opo. Have tested several times. Maybe I was unlucky
I don't get why it is preferable to root by unlocking the bootloader and losing all apps+settings in the process when the kingroot method would provide root without losing apps+settings...
galmok said:
I don't get why it is preferable to root by unlocking the bootloader and losing all apps+settings in the process when the kingroot method would provide root without losing apps+settings...
Click to expand...
Click to collapse
Because Kingroot is an exploit, it's a hack. It's like smashing a window to get inside your house when all you need to do is open the front door (unlock bootloader, root). On top of that, unlocking the bootloader is how it was designed to be done. Also, I don't get why people even lose any data or apps by unlocking the bootloader in the first place. Anyone with any sense researches their phone properly before jumping in and knows to unlock the bootloader before committing any data to it. The fact that unlocking wipes the device isn't even specific to this phone, it's a standard across all Android devices, so anyone who's modifying their device should know this anyway.
Heisenberg said:
Because Kingroot is an exploit, it's a hack. It's like smashing a window to get inside your house when all you need to do is open the front door (unlock bootloader, root). Also, I don't get why people even lose any data or apps by unlocking the bootloader in the first place. Anyone with any sense researches their phone properly before jumping in and knows to unlock the bootloader before committing any data to it. The fact that unlocking wipes the device isn't even specific to this phone, it's a standard across all Android devices, so anyone who's modifying their device should know this anyway.
Click to expand...
Click to collapse
Actually, with my Samsung Galaxy S2 (previous phone), all I had to do was install an update via builtin bootloader and I was rooted without having unlocked the bootloader. Worked great. I assumed the OnePlus (my current Android) would offer the same. Too late did I learn that unlocking the bootloader would erase everything. It wasn't even possible to make a backup of everything, locking me in the non-root position. So, if KingRoot can root my phone, this is clearly a great option as it would allow me to make a full backup of the phone (and restore should it be necessary, e.g. after unlocking bootloader). Exploits/hacks are not bad. Often they offer features not available otherwise, like KingRoot's non-destructive rooting.
galmok said:
Actually, with my Samsung Galaxy S2 (previous phone), all I had to do was install an update via builtin bootloader and I was rooted without having unlocked the bootloader. Worked great. I assumed the OnePlus (my current Android) would offer the same. Too late did I learn that unlocking the bootloader would erase everything. It wasn't even possible to make a backup of everything, locking me in the non-root position. So, if KingRoot can root my phone, this is clearly a great option as it would allow me to make a full backup of the phone (and restore should it be necessary, e.g. after unlocking bootloader). Exploits/hacks are not bad. Often they offer features not available otherwise, like KingRoot's non-destructive rooting.
Click to expand...
Click to collapse
Actually, the entire reason you had to root that way with your Samsung is because they've locked the bootloader down so that it cannot be unlocked. That's actually why exploits like Kingroot exist in the first place, in order to root devices that cannot be rooted in the normal way. As I said, if you had done the proper research in the first place you wouldn't be in the position you're in now. Exploits aren't bad, they have a place, they have a reason to exist, but it isn't to root devices like this which are open and able to be rooted in the way that was always intended.
I see a lot of ex Samsung users complaining that they have to go through the process of unlocking the bootloader and all that to root the phone, and complaining that their usual exploit doesn't work, not realising the whole time that they've got it completely backwards; the exploit is the round-about way of doing things, unlocking the bootloader is the intended way of doing things.
Edit:
Having the bootloader unlocked is essential for insurance purposes too. If you have trouble with your phone in future and need to flash the stock images because it won't boot you'll be forced to unlock the bootloader to do so. You won't be able to salvage any data from the phone. It's better to do it now when you actually have some control over the situation.
Heisenberg said:
Actually, the entire reason you had to root that way with your Samsung is because they've locked the bootloader down so that it cannot be unlocked. That's actually why exploits like Kingroot exist in the first place, in order to root devices that cannot be rooted in the normal way. As I said, if you had done the proper research in the first place you wouldn't be in the position you're in now. Exploits aren't bad, they have a place, they have a reason to exist, but it isn't to root devices like this which are open and able to be rooted in the way that was always intended.
I see a lot of ex Samsung users complaining that they have to go through the process of unlocking the bootloader and all that to root the phone, and complaining that their usual exploit doesn't work, not realising the whole time that they've got it completely backwards; the exploit is the round-about way of doing things, unlocking the bootloader is the intended way of doing things.
Click to expand...
Click to collapse
Well, at least my OnePlus (11s) could be rooted without having the bootloader unlocked. This is perfect for me, as I should still be able to get OTA firmware upgrades (not possible as far as I have read about unlocking the bootloader and installing a custom bootloader to root). Of course, this method relies on vulnerabilities, and are not always going to be there. So I have to make a choice:
1) Hope rooting via hacks is enough and always available, but also get OTA.
2) Unlock bootloader etc., lose all files and settings (start from scratch), not get OTA, use lots of time to get apps/contacts/photos/settings back.
I don't have time for #2 which is why I am (was) still unrooted. #1 took 2 minutes (1 minut of waiting) with kingroot and for now is good enough. I will begin using a decent backup program (instead of adb backup) so I can make a hopefully smooth transition to the unlocked/replaced bootloader case.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
Oh, and the only reason I rooted was to get more details about unwanted battery usage (BetterBatteryStats).
galmok said:
Well, at least my OnePlus (11s) could be rooted without having the bootloader unlocked. This is perfect for me, as I should still be able to get OTA firmware upgrades (not possible as far as I have read about unlocking the bootloader and installing a custom bootloader to root). Of course, this method relies on vulnerabilities, and are not always going to be there. So I have to make a choice:
1) Hope rooting via hacks is enough and always available, but also get OTA.
2) Unlock bootloader etc., lose all files and settings (start from scratch), not get OTA, use lots of time to get apps/contacts/photos/settings back.
I don't have time for #2 which is why I am (was) still unrooted. #1 took 2 minutes (1 minut of waiting) with kingroot and for now is good enough. I will begin using a decent backup program (instead of adb backup) so I can make a hopefully smooth transition to the unlocked/replaced bootloader case.
---------- Post added at 11:16 AM ---------- Previous post was at 11:15 AM ----------
Oh, and the only reason I rooted was to get more details about unwanted battery usage (BetterBatteryStats).
Click to expand...
Click to collapse
You can still get OTA updates with an unlocked bootloader and root, where did you read otherwise? Whoever said that is dead wrong. You might wanna read the edit I made to my post above too.
Hi
Couldn't find any thread about it. So posting it
I red on official website that I might loose some functionalities "You may lose some key functions like telephone, radio, and audio playback.".
Can anyone put some light on what I might loose as per this? (I know data will be lost and etc but what about this line pls?
Nothing , they are just pretending . only ur warranty voids
Sent from my Moto G using Tapatalk
Sorry for posting thread in wrong section.
As far as I know you still get OTA updates as well, correct? Assuming unlocked bootloader and stock operating system.
jitin02 said:
Hi
Couldn't find any thread about it. So posting it
I red on official website that I might loose some functionalities "You may lose some key functions like telephone, radio, and audio playback.".
Can anyone put some light on what I might loose as per this? (I know data will be lost and etc but what about this line pls?
Click to expand...
Click to collapse
No data is lost for unlocking bootloader.... Believe me i have unloacked it and flashed CM rom and its working better than before..
shashidhar941997 said:
No data is lost for unlocking bootloader.... Believe me i have unloacked it and flashed CM rom and its working better than before..
Click to expand...
Click to collapse
Of course data is lost... everything on the phone is wiped clean, it is impossible at present to unlock the G3 without wiping out all user data.
To the OP, you do not lose any functionality by unlocking alone, everything will work EXACTLY as before as long as the only thing you do is unlock... that being said, if you change anything, such as adding root access, flashing Xposed, installing a custom recovery, that changes the device so it could potentially cause an issue outside of Motorola's control or outside of their supported practices. For example, you will not be able to receive OTA updates if you have modified the /system partition, the OTA system will see that that the partition has been mounted R/W and will not offer further OTA's, but you can still sideload them manually. If you install a custom recovery and nothing else, you may be offered an OTA, but it will fail since it requires stock recovery.
Basically, if you are careful and willing to do a little research and go beyond the "stock" experience, you will have to do a few things manually, and unlocking is the beginning of that process. Unlocking just for the sake of doing it and not continuing is a waste of time.
acejavelin said:
Of course data is lost... everything on the phone is wiped clean, it is impossible at present to unlock the G3 without wiping out all user data.
To the OP, you do not lose any functionality by unlocking alone, everything will work EXACTLY as before as long as the only thing you do is unlock... that being said, if you change anything, such as adding root access, flashing Xposed, installing a custom recovery, that changes the device so it could potentially cause an issue outside of Motorola's control or outside of their supported practices. For example, you will not be able to receive OTA updates if you have modified the /system partition, the OTA system will see that that the partition has been mounted R/W and will not offer further OTA's, but you can still sideload them manually. If you install a custom recovery and nothing else, you may be offered an OTA, but it will fail since it requires stock recovery.
Basically, if you are careful and willing to do a little research and go beyond the "stock" experience, you will have to do a few things manually, and unlocking is the beginning of that process. Unlocking just for the sake of doing it and not continuing is a waste of time.
Click to expand...
Click to collapse
So basically it's like my oneplus one... The ota thing. Who cares .
And yes I was thinking of rooting, xposedify, twrp .......
Tks fr info ..... But another of my worry is locking bl. Acc. To what I red is you can't lock it properly. As my devic is 1 month old (not even 1) I don't want to risk it
jitin02 said:
So basically it's like my oneplus one... The ota thing. Who cares .
And yes I was thinking of rooting, xposedify, twrp .......
Tks fr info ..... But another of my worry is locking bl. Acc. To what I red is you can't lock it properly. As my devic is 1 month old (not even 1) I don't want to risk it
Click to expand...
Click to collapse
The bootloader cannot be relocked... there is a procedure to appear locked, but it you can never actually undo the unlock procedure... One thing to keep in mind is that when you unlock you lose your warranty, but it is not based on whether your device shows it's locked or not, the minute you accept the T&C on Motorola's site and get the unlock token, your warranty is gone, it doesn't even matter if you actually unlock the device or not.
acejavelin said:
The bootloader cannot be relocked... there is a procedure to appear locked, but it you can never actually undo the unlock procedure... One thing to keep in mind is that when you unlock you lose your warranty, but it is not based on whether your device shows it's locked or not, the minute you accept the T&C on Motorola's site and get the unlock token, your warranty is gone, it doesn't even matter if you actually unlock the device or not.
Click to expand...
Click to collapse
Them I m not unlocking. Lol
shashidhar941997 said:
No data is lost for unlocking bootloader.... Believe me i have unloacked it and flashed CM rom and its working better than before..
Click to expand...
Click to collapse
better than before means do u notice quick battery darning i also unlocked nd CM 12.1 excluding battery it better than before
acejavelin said:
Of course data is lost... everything on the phone is wiped clean, it is impossible at present to unlock the G3 without wiping out all user data.
Click to expand...
Click to collapse
Is the SD Card safe or should that be removed prior to unlocking bootloader?
MrTooPhone said:
Is the SD Card safe or should that be removed prior to unlocking bootloader?
Click to expand...
Click to collapse
I would remove it if you want to keep it setup as is... It does a factory reset which will wipe the SD card.
Sent from my MotoG3 using Tapatalk
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
MrTooPhone said:
Is the SD Card safe or should that be removed prior to unlocking bootloader?
Click to expand...
Click to collapse
It will wipe SD card.
Sent from my MotoG3 using Tapatalk
acejavelin said:
I would remove it if you want to keep it setup as is... It does a factory reset which will wipe the SD card.
Sent from my MotoG3 using Tapatalk
---------- Post added at 07:44 AM ---------- Previous post was at 07:43 AM ----------
It will wipe SD card.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
It did not wipe mine. It only formats the internal partitions. Most phones you have to specify if you want the SD formatted as well.
quakeaz said:
It did not wipe mine. It only formats the internal partitions. Most phones you have to specify if you want the SD formatted as well.
Click to expand...
Click to collapse
Unlocking the bootloader should wipe all user partitions, including SD card, the bootloader unlock factory reset is a complete wipe, unless something has changed. You don't get an option of what to erase when unlocking the bootloader.
Sent from my MotoG3 using Tapatalk
acejavelin said:
Unlocking the bootloader should wipe all user partitions, including SD card, the bootloader unlock factory reset is a complete wipe, unless something has changed. You don't get an option of what to erase when unlocking the bootloader.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
I know there's no option. I've just never seen a phone that wipes SD by default, including this one. Usually wiping user data consists of the /data partition. But if you're more comfortable pulling the SD out, better safe than sorry...
Sent from my MotoG3 using Tapatalk
quakeaz said:
I know there's no option. I've just never seen a phone that wipes SD by default, including this one.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hmm... For a normal factory reset I would agree, for bootloader unlock reset it should wipe it. What's the point of the security feature of wiping the device when bootloader unlock occurs if it leaves a major security hole by not wiping the SD card?
I can't speak from experience on this, I removed mine as a precautionary measure because back in the older HTC days of Gingerbread/Jellybean, there were a few cases where the SD card would be trashed when unlocking the bootloader.
Sent from my MotoG3 using Tapatalk
Neither unlocking the bootloader nor a factory reset do ANYTHING LIKE wiping your phone. Neither would either make any sense at all.
You are not supposed be able to unlock the bootloader so what sort of software do you think could be included to detect or stop it happening? Samsung KNOX comes to mind but that ain't Moto.
Factory resets remove apps, call logs, contacts, and anything else on the internal SD. Stuff that is on the external SD is not affected, only the Data and the Cache partitions.
I unlocked my bootloader but that didn't prevent me from receiving the MM Ota update two days ago. So, unlocking void only your warranty, nothing else. It will for sure wipe your phone's data.
There are a number of reasons for unlocking Bootloader. Especially for those that cannot or do not want to return phone to manufacturer.
(1) Android can become corrupt at any time. It can happen randomly. Without an unlocked Bootloader, you may no longer be able to load Android or access your files. With a custom recovery - you still have ADB and root access to your files. Also in the event that factory firmware images do not work, you now have the option of flashing a custom ROM.
(2) Lost / accidentally deleted photos. Without an unlocked Bootloader and root access, your options are very limited. If you have root access, there are apps that can recover deleted photos. You also have the possibility of making a backup image of internal storage and transferring that to PC for use with Data recovery software.
(3) You need an unlocked Bootloader to flash a custom Kernel / ROM. These can provide better performance, improved battery-life, a greater range of features and in some cases, improved app compatibility.
(4) This one may be less of an issue, but worth considering. Having an unlocked Bootloader can get you out of a situation where phone is locked due to 'Device Protection.'
Related: http://www.androidpolice.com/2015/0...ne-you-might-trip-a-72-hour-security-lockout/
lost101 said:
(4) This one may be less of an issue, but worth considering. Having an unlocked Bootloader can get you out of a situation where phone is locked due to 'Device Protection.'
Click to expand...
Click to collapse
Though you also have to consider the other side of that medal.
With a locked bootloader and device protection active, the phone is useless to everyone except yourself.
If the phone is lost this *might* increase the chance that it's being returned to you.
And if it's stolen you at least have the satisfaction that the thief can only use it as a paperweight.
If the bootloader is unlocked, whoever found or stole the phone can overcome the device protection and can use or sell the phone...
As a friendly reminder to those unfamiliar with unlocking/re-locking their bootloaders;
Unless your on 100% stock, and planning on reselling your phone, don't re-lock the bootloader.
For some reason re-locking the bootloader while you have a custom ROM installed will cause the phone not to boot (in a way, soft bricking it.)
And, leave "OEM unlocking" in the "Developer Options" CHECKED, once that is unchecked you cannot unlock the phone once a soft brick happens.
The official advice from Essential about re-locking your phone is ONLY for the official firmware. Pretend they never said that on their site, it has caused more trouble then necessary. It's even dangerous to re-lock while running the Oreo beta.
Concerning un-bricking the device, at the moment there is no known way.
And it will be this way until someone figures out a way to exploit the bootloader or reverse engineer it.
So please don't flood this thread with asking for help to un-brick your device, I nor anyone else can help you on that at this given time, all I'm doing is trying to is prevent that happening.
So, safe unlocking! And happy holidays!
EDITS:
1) According to some reports, when you lock your bootloader it will also automatically untoggle the "OEM Unlocking" option.
2) It appears when re-locking the phone on a non-stock ROM some partitions are becoming corrupt, and resulting in the "red boot warning" screen. Under most circumstances you can fix that screen, but not while the bootloader is locked (since you need the fastboot flash command.)
3) When the partitions become corrupt you cannot boot into any mode, including the stock recovery. This is why Essential's suggestions are pointless at this stage of the brick.
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
avd said:
Should be pinned and in the OP of every mod thread
Click to expand...
Click to collapse
totally agree, i made this "trick" with one of my first android phone and it never happen me again. But new user who would flash Los or other rom should be aware of this issue, specially when jtag is not an option. As far we'll make some powerfull 500$ brick :crying:. it's our duty to make people aware of this. @invisiblek you guy made an incredible work and so fast but like he said i think you should warn people of the risk in the OP
avd said:
Should be pinned and in the OP of every mod thread
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Ellises said:
I wouldn't even know how to go about to ask to pin this.
But besides this I'm also thinking about making a thread for new users regarding common issues when installing roms at our current stage.
I'm firejackal on discord, I'm just trying to reduce the amount of people asking the same questions on there and to prevent bricked units.
Click to expand...
Click to collapse
It's very easy to ask for a thread to get stuck to the top.
Just use the report post button, and ask, whether or not becomes a sticky is up to the Mods.
How to Report a Post.
Sent from my XT1254 using XDA Labs
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
ericzhf said:
Wish I saw this earlier, my phone is already bricked few weeks ago after re-lock the boot loader. When I ask Essential support for help, they said this in the email:
"Hi Eric,
I can appreciate your concern if the device is not able to be used.
I am sorry though, we are not able to provide support for ADB or issues that you will run into with sideloading builds. We have no remote tools that will recover the device.
Although I haven't run into that same error, you might still be able to re-flash the Oreo/production build again using ADB.
I would recommend following the Oreo Beta sideload instructions available on Essential.com/developer that will walk you through the process of getting the device recognized and communicating with ADB. There are also instructions for re-flashing the current build available here. If you are still running into issues, I would recommend visiting online forums like XDA for assistance from other developers for that issue that you are noticing.
Thank you for your understanding.
Sincerely,
Erich
Essential Customer Experience Team"
Click to expand...
Click to collapse
Ellises said:
That sounds like a generic reply since it's not mentioning anything about the brick.
But I have a question regarding this; when you use the locked bootloader to boot into the stock recovery to try to sideload an official signed image, what does it do? Does it give an error, or is not able to connect to the computer?
Click to expand...
Click to collapse
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
ericzhf said:
I'm not able to boot in to stock recovery any more, it gives this error when I try recovery "Your device is corrupted. It can't be trusted and will not boot". I think that was because I rooted and installed TWRY before.
Now with locked bootloader, I can't get in to recovery and I can't flash TWRY either. I can't unlock bootloader too because I'm not able to boot so not able to enable USB-DEBUG and OEM-UNLOCK.
I tried pretty much everything and no luck at this point, I don't know what else I can do.
Click to expand...
Click to collapse
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
tech_head said:
You have bricked your phone.
Locking the bootloader with non-factory ROM causes secure boot to fail.
An unlocked bootloader doesn't care about secure boot.
If the ROM images is not signed there isn't a problem unless you have a locked bootloader.
The one thing I don't understand is why relook the BL anyway?
You have TWRP installed so you already can't take an OTA.
Click to expand...
Click to collapse
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
ericzhf said:
I bought the phone for about 2 weeks, then there was a promotion that buy phone give camera 360 for free with Sprint, so I was thinking about return this and buy again to get the free stuff. To return it I have to get it back to stock, so I factory reset my phone and try to re-lock boot loader without thinking. Turns out I didn't get the free camera and bricked my phone too, perfect example of "NOTHING IS FREE":good:
Click to expand...
Click to collapse
FDR is not "back to stock".
You must to a full flash to get back to stock.
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Ellises said:
I updated the top post with some additional information.
Also, if anyone is to contact Essential I wouldn't recommend mentioning that you tried to install custom ROMs, that's just walking into a mess like if you mentioned that to any other phone company.
I would instead say that you tried to install [their] oreo beta, went to re-lock the phone and your presented with a corruption message and unable to do anything including their instructions. Because installing their oreo beta does not void your warranty.
Click to expand...
Click to collapse
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
I could also mention on their stock build page it wants you to unlock the bootloader to manually update through the bootloader. But on the oreo beta page it mentions nothing about having to be unlocked, or locked to do it via the stock recovery. So the average user could presume they need to be unlocked.
NaterTots said:
Well, to install their Oreo beta builds you don't need to unlock the bootloader.
It's an adb side load through stock recovery
Click to expand...
Click to collapse
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
No.
WiddleyScudds said:
Am I'm safe to re-lock if I'm on stock rooted 7.1.1 NMK24B? I have a dead pixel and I need to send it back.
Click to expand...
Click to collapse
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Obamaloominaty said:
No.
Click to expand...
Click to collapse
tech_head said:
If you are rooted, you are not stock.
The boot image is modified.
Locking will brick the phone.
You must be completely stock!! No root. Nothing.
Click to expand...
Click to collapse
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
WiddleyScudds said:
Thanks for clearing that up. If I have any more questions before returning to stock, I will ask here first.
Click to expand...
Click to collapse
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
tech_head said:
Was not trying to be harsh but it can't be stressed enough that you must be completely stock to lock the boot loader and not have issues.
I wouldn't lock the BL on a side loaded beta.
Only lock if you have done a complete flash of stock, released firmware, immediately after the install.
I might be sounding like an alarmist but I don't want anyone to brick their phone.
Click to expand...
Click to collapse
I just got an ota notification for OPM1. 180104.092. think I'll be safe I I take it, then factory reset and then lock? Because I can't seem to locate stock NMK24B to flash. Maybe I'm not looking hard enough .
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Edit: I guess it just took a passion and a situation. See thread for unlock.
Edit Part 2: Electric Boogaloo: Just a quick recap of what's happened here. From the bootloader screen on my Pixel 2 (Walleye) I ran the
Code:
Fastboot flashing lock_critical
command, which then gave me a menu asking if I really want to lock it, or unlock it, I clicked unlock, and here we are. So far, only @zinchalk has confirmed this working. I would love for more people to try this out on their Verizon Pixel 2's and come back with the results. This was either the weirdest fluke of all time, or the best mistake Verizon has ever made. Either way, I hope it works for you
Edit 3: Well there's the January Patch This looks like it 'fixes' the bypass.
Correction: Nevermind, nothing is confirmed yet. And the people have decided there is no way this could be patched that quickly.
Edit 4: I'm seeing way too many people posting about bricked phones. Please don't do this UNLESS YOU KNOW WHAT YOU ARE DOING. I cannot live knowing that someone ruined their phone with this method. Please be safe.
@SoloTSi97 has confirmed this does work on the January 5th security patch!
Edit 5: There it is, we have people confirming the Verizon OTA being pushed this late January is patching the fastboot unlock method. Keep this in mind down the road guys.
D3RP_ said:
Would it be possible to modify the .bin in an OTA sideload for a root? Am I missing a key point in how this works? Or is it just, no one's done it yet?
Click to expand...
Click to collapse
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Diesel_Jeremiah said:
Have you found a way to unlock the bootloader on a Verizon phone?
Or are you thinking modify the .bin would achieve unlocking the bootloader?
As far as I've read, no one has bothered since you can purchase direct from Google and OEM unlock the bootloader. Then root through Magisk is simple.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
lmao not that I know of. But I know it's possible to update any android through adb sideload. I'm really just grasping for straws. But because of my current situation I have a Pixel 2 from Verizon, and i'm gonna have it for a while.
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
tailsthecat3 said:
I've been out of the android game for a long time; just switched back from iPhone 7, to a Pixel 2 used with Verizon. Am I correct in assuming that the device is unable to be unlocked, etc.?
Click to expand...
Click to collapse
Unless you know some magic way, it is locked. I don't even know where to start with this thing.
Sell the Verizon one to someone who doesn't care for root and buy one from Google?
I used Sunshine Root for my HTC m8 years ago. They might be an option in the future. Yet again, since the Google version is easily unlocked & rooted, I don't think anyone has even tried.
Sent from my Pixel 2 using Tapatalk
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
tailsthecat3 said:
Thanks. Glad I didn't try using the method I saw on YouTube, etc.
Click to expand...
Click to collapse
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
D3RP_ said:
Just a small update. From the fastboot menu, I did
Code:
Fastboot flashing lock_critical
Which gave me the option to ''unlock bootloader'. It can't be this easy, but uhhh. I'll keep this thread updated...
Click to expand...
Click to collapse
^^
tailsthecat3 said:
Surely it can't be that easy. I'd say start a thread if this hasn't been noted.
---------- Post added at 18:55 ---------- Previous post was at 18:54 ----------
^^
Click to expand...
Click to collapse
OEM unlocking says Bootloader is unlocked. So uh, it was that easy... Gonna root and install TWRP in a second.
Final Update
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
D3RP_ said:
So that worked. Currently rooted with TWRP on my Verizon Pixel 2. Spread the word, or don't.
Click to expand...
Click to collapse
Can you give some screenshot proof on this?
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
Does that prove anything?
D3RP_ said:
Does that prove anything?
Click to expand...
Click to collapse
This doesn't prove anything. Show us the bootloader screen with your phone's info. There will be a baseband number and the status of the bootloader. Cover your serial number.
[Edit]
You do have a custom kernel flashed though.. so I guess.
xtacocorex said:
Interesting. I've been watching to see if someone gets the bootloader unlocked for the Verizon Pixel 2. In looking at the manpage for the fastboot commands, all you've really done is tell the system to lock the critical partitions (bootloader) during flashing. Pretty cool that it brought up the unlock menu.
What happens if you run `fastboot flashing get_unlock_ability`?
Click to expand...
Click to collapse
Sorry for the late reply. When I do that, I get
Code:
(bootloader) get_unlock_ability: 0
I made a thread about this in the original Pixel XL section. In the OP I quickly jolted down what you did, can you go and explain in detail as it might also work with the OG Pixel's.
Thanks in advance :
https://forum.xda-developers.com/pixel-xl/how-to/verizon-pixel-bootloader-unlocked-t3726672
How did the OP pass the cert check and update checks?
TonikJDK said:
How did the OP pass the cert check and update checks?
Click to expand...
Click to collapse
edit
lps1014 said:
Can you give some screenshot proof on this?
Click to expand...
Click to collapse
I just ran the command like OP said and the "unlock bootloader prompt" appeared. I ran this from a stock verizon on 8.0. I now flashed twrp, magisk and have the current google 8.1 ota. I will give proof if you tell me what will suffice.