Help locked out of recovery - Nexus 5 Q&A, Help & Troubleshooting

I was literally flashing something ten minutes before and then I tried going back to recovery and there were no directory so I then rebooted it says I need a password... But I never one made a password, I didn't even know there was passwords for recovery
Sent from my Nexus 5 using xda app-developers app

Never mind... Just kept rebooting then eventually the problem was gone... How can I set a password for bootloader and recovery... Just wondering if it's even possible
Sent from my Nexus 5 using xda app-developers app

You can't set a password for either (well, not to my knowledge!)

Even with a password we can fastboot flash new images.
Team Win explains this on their website.

Primokorn said:
Even with a password we can fastboot flash new images.
Team Win explains this on their website.
Click to expand...
Click to collapse
Yes and no.. Actually we can lock the bootloader so fastboot flash wont work.... All we need is for the recovery password to block the following to secure your data (on the nexus 5):
Mount of external (OTG) media
adb access
file manager capabilities
This would mean you can still boot into recovery and flash / backup (although not to removable media) until you went into a security menu to "unlock recovery". This would even mean that your automated jobs can still occur without having to face a "boot password". The password could be stored on /sdcard in clear test and there could be an option to delete the password incase you forgot it in this same recovery menu, which also wipes the device.
recovery is the only weak point of my device.
Sure, Samsung's Odin will get round this password on their devices as the BL is not locked but any device with a locked bootloader (locakbale bootloader) will benefit.
Another caveat is that this is not to prevent the device being wiped.... unlocking the bootloader will wipe the device, and this is what I want. I don't care about getting the phone back as much as I would care about securing my data. Its all backed up. Nothing is lost. I just might not want someone else getting access to it.
Although this is beyond the extent of my knowledge to achieve, I don't think it would be hard for anyone who knows what they're doing with code.

rootSU said:
Yes and no.. Actually we can lock the bootloader so fastboot flash wont work.... All we need is for the recovery password to block the following to secure your data (on the nexus 5):
Mount of external (OTG) media
adb access
file manager capabilities
This would mean you can still boot into recovery and flash / backup (although not to removable media) until you went into a security menu to "unlock recovery". This would even mean that your automated jobs can still occur without having to face a "boot password". The password could be stored on /sdcard in clear test and there could be an option to delete the password incase you forgot it in this same recovery menu, which also wipes the device.
recovery is the only weak point of my device.
Sure, Samsung's Odin will get round this password on their devices as the BL is not locked but any device with a locked bootloader (locakbale bootloader) will benefit.
Another caveat is that this is not to prevent the device being wiped.... unlocking the bootloader will wipe the device, and this is what I want. I don't care about getting the phone back as much as I would care about securing my data. Its all backed up. Nothing is lost. I just might not want someone else getting access to it.
Although this is beyond the extent of my knowledge to achieve, I don't think it would be hard for anyone who knows what they're doing with code.
Click to expand...
Click to collapse
Do u mean that you always have a locked BL?
Thanks for your feedback but one thing remains the same IMHO. Of course we can lock the BL but a thief can unlock it then flash factory images. No more custom recovery, passwords...
I'm not talking about the user data but to be able for a thieft to use a device even with locked stuff.

Primokorn said:
Do u mean that you always have a locked BL?
Thanks for your feedback but one thing remains the same IMHO. Of course we can lock the BL but a thief can unlock it then flash factory images. No more custom recovery, passwords...
I'm not talking about the user data but to be able for a thieft to use a device even with locked stuff.
Click to expand...
Click to collapse
I'm just talking about data security. That is my only concern. Devices are replaceable. Unlock bootloader, data wiped. fine!

Oh thanks everyone, I just wouldn't want a theif to use a phone they don't deserve, pretty much the only security on my phone to not go to bootloader is for no power menu on my lockscreen but you could probably use adb to get through
Sent from my Nexus 5 using xda app-developers app

That's what imei blocking is for
Sent from my Nexus 5 using Tapatalk

Related

Clockworkmod Password

Hi All,
there's a way to protect cwm by a pass?
LOL no
No. Its called recovery for a reason
Sent from my M886
salas2324 said:
No. Its called recovery for a reason
Sent from my M886
Click to expand...
Click to collapse
What mean? if i wont to protect with password where the strange?
AleDB said:
What mean? if i wont to protect with password where the strange?
Click to expand...
Click to collapse
recovery shouldn't have a password or else you can't recovery your device if you forget password
Sent from my M886
Actually a recovery password would be great. We were discussing this over in the Anti-theft thread. If we had something like this similar to a BIOS password it would prevent anyone from wiping your device if it's stolen. Not sure why people are acting like the OP is an idiot for asking.
If there were a password for CWM you could still get into stock recovery and do a Factory Reset if you needed to, but it would be impossible for someone to wipe your system and remove more advanced anti-theft apps.
its called recovery for a reason, c'mon hahah
I had exactly the same thought yesterday .
+1 for that idea...........what if, i compile a new recovery, i would do this for security:
1.Create an online compiler that asks for the user to enter his/her phone's imei + a unique code & password and compile a unique recovery for his/her phone.
2.After compiling, i'm would give a flashable custom signed update.zip which will be used only when resetting the password.
3.If someone who stole the phone flashed a new recovery, imei & unique code would fail and cannot use any other recovery other than the one flashed already !!
balamu96m said:
+1 for that idea...........what if, i compile a new recovery, i would do this for security:
1.Create an online compiler that asks for the user to enter his/her phone's imei + a unique code & password and compile a unique recovery for his/her phone.
2.After compiling, i'm would give a flashable custom signed update.zip which will be used only when resetting the password.
3.If someone who stole the phone flashed a new recovery, imei & unique code would fail and cannot use any other recovery other than the one flashed already !!
Click to expand...
Click to collapse
If someone flash any other recovery, there is no way to protect the device - he can do everything. Anyway, it's a good idea. But instead of password I'd suggest a buttons combination. It's just less work (no need to create "recovery keyboard").
Indeed. I didn't think about that fact. Even on my phone only certain keyboard presses are recognized within recovery. Regardless, some way to protect the phone beyond what is available would be great.
cwm could integrate a keyboard password like google did with the encryption password. you do the phone presses to access, it begins to take you into recovery, then you are prompted to type in a password. same as if you were trying to access with odin.. seems like it would take a little extra effort but damn, accidents happen.
I have read a few people saying that most some phone thieves don't know what they are doing but hey, Google query: hack android phone.
There's nothing wrong with wanting to add even more security to our phones, call us paranoid.
Love the idea.. maybe with some kind of authenticator, like wow..?
Sent from my HTC Desire using xda app-developers app
W8 for other ideas
Sent from my GT-I9100 using xda app-developers app
maybe one of the developer can implement this idea in aroma installer.
Sent from my GT-I8150 using xda app-developers app
If you require password, and don't permit adb until successfully unlocked, you're starting to get secure.
You'd also need to remove root from regular boot, or prevent adb root access, and secure the system with a lock screen.
If the device has odin or similar, don't waste your time, as anyone determined will overwrite your recovery with an adb enabled one...
AleDB said:
Hi All,
there's a way to protect cwm by a pass?
Click to expand...
Click to collapse
+1 from me
pulser_g2 said:
If you require password, and don't permit adb until successfully unlocked, you're starting to get secure.
You'd also need to remove root from regular boot, or prevent adb root access, and secure the system with a lock screen.
If the device has odin or similar, don't waste your time, as anyone determined will overwrite your recovery with an adb enabled one...
Click to expand...
Click to collapse
i went on the google group android security and some one replied with a possible solution:
Code:
You'll have to implement this in the bootloader, which in most cases is
closed source, so roughly you'll have to:
- find the binary blob of the bootloader, probably in a factory image or
dump it from the device
- find the base address of the bootloader blob and disassemble it
properly (use IDA pro)
- find a place -big enough- where you can inject your own code for the
password prompt
- find a place in the early stages of device boot where you can place a
jump instruction and branch to your code, this should be right after the
bootloader code detects if the fastboot or odin button combinations are
pressed.
I'll suggest to write your code in C unless you are an arm assembly
guru, and try to make it the smallest possible... if the password is
correct, then it should jump back to the place right after where the
execution was interrupted with your initial jump and continue with the
normal bootloader process.
Also, I wouldn't do the tests by flashing your patched bootloader
directly into the phone (replacing the phone's stock bootloader), as a
small mistake in your patches can totally brick the device. To properly
test your patches, you'll need to find a way to place the bootloader in
RAM (from Android) and jump into it, and to do this you'll need to
disable interrupts, invalidate CPU caches, reset MMU, and continue
execution from physical address space where you've copied the bootloader
in RAM, this will simulate a reboot from bootloader but using your
patched one in RAM instead of the stock one in NAND, not an easy task I
guess... but if you have some progress, let us know :D
Cheers,
like with the encryption some script is ran that requires the password to be put in. since the code is already available could there be a way to just use that script and have detect if booting into recovery or odin?
password would be welcome in case my device were stolen, so anyone could make a fresh install independent of the ke or faceunlock, trackers, and everything i have
+1 for the idea... reason:
I know someone who's phone was factory reset by the police... yes, I live in Australia and what was done was illegal and he is taking legal action but once it's done, that's it, you lost everything on the device.
Password protecting recovery is a way to prevent those with enough know how to trigger a reset when you have no legal recourse not to hand over your belongings to another party on the street.
I know this is an edge case but one that has a precedent.

Nexus 5 won't prompt for decrypt on boot / TWRP fails to decrypt

So I think I am screwed here but was wondering if anyone has run into similar issue. I was running SlimKat and had the data encrypted and I used BootUnlocker to relock the bootloader after I flashed TWRP a few months back. Been working fine for a couple weeks then yesterday I pull my phone out my pocket and it looks like it factory reset prompting to input all my info. So I reboot the phone thinking could be fluke and it doesnt prompt me for decyption password and again boots to setup screen. If you do login you cannot access the internal storage and there is no data connection. So I rebooted into TWRP and it prompts for decryption password only its not working. If I put in wrong password it comes back immediately that it failed. If I try correct password it tries for 30 - 45 seconds then comes back with failed. So tried downloading factory image and flash with fasboot but was complaining about bootloader locked. So I issued fastboot oem unlock and choose yes the screen switches to unlocked but doesnt wipe anything try to flash again and I get FAILED flash write failure. When I reboot to the bootloader it shows as locked again. I think my flash took a crap. Anyone have any ideas?
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
kj2112 said:
I bought my N5 used....and guess what, it was encrypted. And i didn't know it.
Well after a series of unfortunate events, LOL, I found this.....it worked for me when I thought my brand new (new to me) N5 was bricked.
http://forum.xda-developers.com/showthread.php?t=2513937
Sent from my cell phone telephone....
Click to expand...
Click to collapse
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
what do you mean doesnt unlock it?
prestonr83 said:
Yea, I've been trying to flash a factory img but I can't due to the locked bootloader and issuing fasboot oem unlock won't unlock it.
Click to expand...
Click to collapse
very odd!
youre device is seen by fastboot(not adb)?
prestonr83 said:
Tried that doesnt work due to the locked boot loader. Issuing fasboot oem unlock doesn't actually unlock it.
Click to expand...
Click to collapse
That's a good point.
I'm afraid that if you cant flash the stock image, and you can't unlock the bootloader to try other methods....you may be at an impass.
You need to either get the stock image back on. Or unlock the bootloader, Then try my link. Not sure what else can be done here.
Sent from my cell phone telephone....
---------- Post added at 05:03 PM ---------- Previous post was at 05:01 PM ----------
Oh....and again.....you may have driver issues on the pc, and that's why fastboot isn't seeing the phone. That is the first thing that needs to be corrected.
Sent from my cell phone telephone....
Zepius said:
what do you mean doesnt unlock it?
Click to expand...
Click to collapse
I mean i put it in fastboot issue fastboot oem unlock it prompts me on the phone to choose yes or no. I choose yes it then immediately goes back to fastboot screen and shows unlocked. However when trying to flash anything it fails and upon rebooting back into fastboot it again shows as locked.
Your emmc is dead. RMA it
Sent from my Nexus 5 using Tapatalk
simms22 said:
very odd!
youre device is seen by fastboot(not adb)?
Click to expand...
Click to collapse
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
prestonr83 said:
yes fastboot is reading the phone. but issuing fastboot oem unlock doesn't actually unlock it. I tried fastboot boot recovery.img to get into stock recovery to see if it would let me do factory reset however after booting into stock recovery I am unable to get the menu to pop up to allow me to factory reset.
Click to expand...
Click to collapse
have you tried flashing clockworkmod recovery and factory resetting it there?
simms22 said:
since its been possible to encrypt with android, it has cause everyone issues, eventually. with as many people that ive known that have encrypted, every single one of them has had issues, eventually. eventually because it usually doesnt happen right away, but somewhere down the line. i constantly tell people not to encrypt, that they will have an issue later.
sounds like you will be flashing the factory img at some point.
Click to expand...
Click to collapse
Advice I would really have to disagree with as it is a built in security measure; telling people to avoid using proven security methods is sketchy in itself. I had my Nexus 4 encrypted for the last 4 months and had never had any issues. What issues are you talking about?
Encryption slows the device down... We all know that. Also, if by chance someone forgets their pw (yes... Seen it happen plenty) you lose al your stuff to get back in.
Anyway, to each their own... But I'm not important enough to worry about what's on my phone getting into the wrong hands. ?

Nexus 5 stolen / Bootloader access

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.

[Q] My Nexus 5 file systems are now read only

About 4 weeks ago my phone spontaneously rebooted itself. Once it did I lost all (including the internal SD card) data. So basically a hard factory reset. Additionally TWRP and the recovery was borked. After much struggling I managed to get adb to put TWRP back. But now. Every necessary file system is effectively read only. (I can't mount them in
TWRP at all and when in the phone via ADB. no love) I say effectively, because although it lists it in mount as being rw. I can't even do a simple touch. nothing writes. I'm still rooted, I still have the ability to configure (as in initial setup) however if you restart the phone, all is lost, and you need to reconfigure.
Any suggestions recommendations or sympathy would be appreciated. The one thing I do see is that on the ext4 file systems (which are the ones that are effectively read only) there is an error with the journal that normally is fixed by deleting the journal and trying again. Because of this I can't re-install the OS etc. Thanks again for allowing me to whimper. Sucks that it did this 2 months before the 6.... I had to bite the bullet and replace. LG and Google both say it sucks to be me. :crying:
Backup your files. Fastboot flash userdata.img
Sent from my Nexus 5 using Tapatalk
rootSU said:
Backup your files. Fastboot flash userdata.img
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
yeah, i tried that and it keeps giving me errors related to not being able to write to the file system because the bootloader is locked. Additional. the bootloader relocked, if I unlock it, it unlocks in word but the restart to bootloader shows it is again locked. Thanks for the help though. any idea appreciated.
linuxrebel said:
yeah, i tried that and it keeps giving me errors related to not being able to write to the file system because the bootloader is locked. Additional. the bootloader relocked, if I unlock it, it unlocks in word but the restart to bootloader shows it is again locked. Thanks for the help though. any idea appreciated.
Click to expand...
Click to collapse
Your NAND is fried. Device needs sending for repair
Sent from my Nexus 5 using Tapatalk

Cons of unlocking bootloader

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...

Categories

Resources