Database Info

Help locked out of recovery

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

[Q] Considering rooting the Nexus 5

So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Recently I've been thinking about rooting the device for maybe some little extras. For example, I have GTA SA installed but I would like to play it with the Cleo mod to have a little bit more fun. Or maybe I'll install some kind of adblocker so I could enjoy my brand new phone without the annoying gold diggers. Or perhaps I want to hide some apps from my app drawer so it would look neat and organised. Or I would like to install an apk that isn't available for non-rooted devices. Or in case I want to see the battery percentage next to the time display or anything like that.
As you can see I would only want to root it for rather small reasons. I definitely don't want to overclock anything because it already meets my criteria for speed, nor do I want to install any custom ROMs because I really like the pure android experience. So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!

root/unlockbootloader/install twrp&busybox no data loss
root/unlockbootloader/install twrp&busybox no data loss without P.C, okay here we go mod's remove if you think it's not helping. download towelroot by geohot,now the rest from playstore, es file exploer,super su,busybox,reboot app,nexus unlock bootloader,
make sure you have security unknowen sources ticked and verify apps unticked.
download towelroot from chrome with es file exploer open and install hit make it rain tab, next install busybox,next install super su app.unlockbootloader with in the app.,install twrp and auto install recovery for hammerhead from twrp, now you should have full root after reboot.super user and busybox unlocked bootloader and twrp installed, and you know what the reboot app is for . no data loss and without a P.C, or you could use fastboot install just look in Q&A, kind regard's joe hope this help's.

Spaceblow said:
Is my current data going to be wiped if I would want to root it?
Click to expand...
Click to collapse
Yep; when you unlock bootloader of your device (before root), all of data will be wiped.
Spaceblow said:
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
Click to expand...
Click to collapse
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
Spaceblow said:
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
Click to expand...
Click to collapse
We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
Spaceblow said:
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
Click to expand...
Click to collapse
In my case, to connect NTFS filesystem.
Spaceblow said:
And is it actually 100% safe...?
Click to expand...
Click to collapse
Maybe, but it's at your own risk.

Jongmin Kim said:
Yep; when you unlock your device (before root), all of data will be wiped.
Nope. When you upgrade to Android L, it might be overwrite existing system clearly.
No. We are using Google Nexus. Just revert with Nexus Factory Image.
http://developers.google.com/android/nexus/images
In my case, to connect NTFS filesystem.
Maybe, but it's at your own risk.
English is too difficult... I'm trying to understand right now.
Click to expand...
Click to collapse
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,

Spaceblow said:
So I have a black Nexus 5 with a capacity of 16GB. The device is only about 4 months old, so I still have it covered with warranty until June 2016. The device is as good as new and I'm very happy with it because everything is so fast and smooth.
Click to expand...
Click to collapse
First of all:
Lethargy said:
I think OP got his question reversed. Should be:
"Why buy a Nexus 5 if you're not going to root?"
:angel:
Click to expand...
Click to collapse
Spaceblow said:
So I have a few questions because I'm a total noob at the field of tweaking android:
Is my current data going to be wiped if I would want to root it?
I'm aware of the upcoming Android L release, so would I be able to update it right away (remember, I'm not going to use any custom ROMs) or would I have to unroot and reset everything first?
In case something goes wrong and I want to use my warranty, could any traces be found after I would have unrooted the device? (because rooting voids your warranty, right?)
What would be the top reasons to root the Nexus 5? For example, any features the device should've had but unfortunately hasn't.
And is it actually 100% safe...?
Click to expand...
Click to collapse
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Spaceblow said:
So regarding to the last question... A friend of mine has a rooted Moto G, he made me familiar with rooting and it's probably thanks to him that I'm considering it. Everything was going well but there were a few times that he woke up and his phone wasn't worth more than a brick. Apparently, it was because of some ROM he installed. This probably won't affect me in any way because like I said, I'm not going to install any custom ROMs, but my friend expected everything to be normal while it wasn't. He probably did everything like it should be done but then he suddenly woke up with a brick next to his head. So apparently, even if you do everything exactly like they tell you to do it, there's still a slight chance that it's going to end up badly, right?
Click to expand...
Click to collapse
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Spaceblow said:
So basically, I'm considering rooting my device but I'm still not sure what I would have to do because there are lots of tutorials and everything is quite confusing and I have some questions. All the help would be greatly appreciated, thanks in advance!
Click to expand...
Click to collapse
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.

Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore). The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
lol yeah i have to agree with you, but i find this help's when on the go,

joecool666 said:
lol yeah i have to agree with you, but i find this help's when on the go,
Click to expand...
Click to collapse
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.

Lethargy said:
If you don't have access to a PC, or you're using a locked-down Samsung/HTC/Moto/Sony/whatever device, then sure, go ahead and use the exploit methods.
But if you do have access to a PC, and it's a Nexus device, just do it properly, it'll cause fewer possible issues.
Click to expand...
Click to collapse
i do use my p.c and lg flashtool and fastboot.just incase lol.and it is the better way of doing it, p.s when OTG rooting don't forget to bring the XDA app.

joecool666 said:
root and then unlock bootloader with the app from playstore. has to be this way. regard's p.s no data wiped ,
Click to expand...
Click to collapse
You mean Towelroot? I'm also considering this option because it would be nice to keep all my data.
Lethargy said:
First of all:
1. Unlocking the bootloader is what wipes the data partition, not root access.
2. Don't bother with OTAs to update, they're too much of a bother to try to get to work, when you can just flash factory images/zip, most likely before you even get the OTA pushed to you.
3. Depends where you bought it from. If you got it off the Play Store, then Google does not care about the software you have on your device as long as it's a legitimate manufacturing fault covered by the warranty. You can RMA to Google with a custom ROM and kernel if you wanted to. If you bought it from elsewhere, You'll have to send it to LG for repair. It's possible to reflash factory images and reset the tamper flag, there isn't anything else on the Nexus 5 that will tell LG anything. The easiest way is using LG Flashtool, which can be found in the first link of my signature. If your device is completely dead however, it doesn't matter since LG wouldn't be able to boot it up.
4. Root access is simply root access. You get access to /system, and therefore can use root apps and other modifications.
5. The root process itself is pretty much 100% safe. The Nexus 5 is really, really hard to brick, unless you flash something that isn't meant for your device or something similar, so user error is the only risk in the process. Software-wise, of course root access comes at some form of a security risk. Just be sure of what apps you're granting root access to and you should have no problem.
Most likely user error, or simply because a Moto device could be locked down more (which also makes it riskier and harder to restore) and not as easy to develop for. The Nexus 5 is one of the hardest devices to brick (again, excluding user error), and if you have any issues it would either be user error or a bug in the ROM/kernel.
Check out the first link of my signature and read some threads before proceeding blindly.
There are ways to gain root access without unlocking the bootloader and without a PC as mentioned above, but it's recommended to do it the traditional way by backing up your internal storage to a PC first and using fastboot. Those methods are useful for other devices that are more locked down. This is a Nexus device, it's better to do it properly.
Click to expand...
Click to collapse
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?

Spaceblow said:
This is some great information, thank you very much! So in case I would want to do it manually, this thread has everything I need (in combination with the 15 seconds ADB Installer)?
Click to expand...
Click to collapse
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.

Lethargy said:
Yep. :good: I also recommend using TWRP instead of CWM as your recovery. PhilZ Touch is also another good alternative, but it is no longer maintained and probably won't work for Lollipop's default encryption.
Latest SuperSU is located here, flashable in a custom recovery.
Click to expand...
Click to collapse
Thanks for helping me but I used Towelroot and it works flawlessly!

Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:

back up
Spaceblow said:
Thanks for helping me but I used Towelroot and it works flawlessly!
Click to expand...
Click to collapse
make sure you make a back up back up most important,regard's joe

To be clear, the *whole* phone including your sdcard partition will be wiped so make sure you back up before unlocking your bootloader. I would use an app like ES File Explorer and copy all your files to Dropbox or Google Drive if you dont have a computer but you'll need a computer anyway.
Sent from my Nexus 5 using XDA Free mobile app

MrObvious said:
To be clear, the *whole* phone including your sdcard partition will be wiped
Click to expand...
Click to collapse
If we want to be clear, we should also be accurate. The *whole* phone is not wiped. The /data partition is wiped, which includes /data/app (where user apps are stored) /data/data (where user settings and app data is stored) and /data/media (where /sdcard data is stored)

Lethargy said:
Cool. :good:
Even though you now have root access, I recommend using Bootunlocker or whatever app to unlock the bootloader from within Android (which doesn't wipe), then flashing a custom recovery with fastboot while in the bootloader anyways.
Why?
If something goes wrong and your phone doesn't boot, you'll have no choice but to unlock the bootloader WITH a wipe using fastboot, then flash a custom recovery or reflash factory images, unless you've done the above, in which case you can dirty-flash (no wipe) a stock ROM zip downloadable here. :angel:
Click to expand...
Click to collapse
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
joecool666 said:
make sure you make a back up back up most important,regard's joe
Click to expand...
Click to collapse
By using Titanium Backup?

Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
Click to expand...
Click to collapse
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.

Spaceblow said:
Thanks for the tip but then I'll be unable to receive OTA updates unless I restore everything, including everything being wiped, right?
By using Titanium Backup?
Click to expand...
Click to collapse
or helium back up

Owning a Nexus makes fastboot your best friend, especially if you have issues.
Read up on adb/fastboot and forget OTA's. Nothing like a clean fresh install of a new version. And there's many options to save /backup your data and important files.
Without learning fastboot and adb.... Simple fix issues can become major headaches.
Don't be intimidated. Read, learn, then do. ?
---------- Post added at 09:49 AM ---------- Previous post was at 09:48 AM ----------
@rootSU has everything you need in his sticky roll up thread.

rootSU said:
All guides and info threads are in my signature. One such INFO thread is OTA help-desk, which explains that you can receive OTA with custom recovery, however there are extra steps.
However, please let me explain 1 thing. OTA is the ultimate noob move. Only root-noobs receive OTA updates. They are the most inconvenient method of updating your OS if you are rooted. Long before you even receive the OTA update, there will be a pre-rooted flashable.zip that can be flashed via recovery.
noobs will often say "but..but..but I wont have to wipe if I accept an OTA"... Little do they know... Even after an official OTA, things screw up. Whenever an OS is upgraded, a wipe is highly recommended as OTA's are imperfect and data between apps and settings conflicts between versions.
OTA is a fools errand if you're rooted. Now you're rooted, leave OTA to the unrooted and learn to manage your rooted device properly. All the info you could ever need is available in my signature as previously mentioned.
Click to expand...
Click to collapse
Well, you convinced me to take my N5 to a step further.
So I already Towelrooted my phone which gave me root access and an untouched bootloader and recovery. My next step would be to backup every app and all data to be sure in case something goes wrong, this would be done by using Titanium Backup. Then I should be unlocking the bootloader by simply using BootUnlocker for Nexus Devices so I wouldn't get my data wiped (I know I would be able to restore it with my backup but I rather do it a bit faster and less complex). When I did that, I have to head over to this thread and flash TWRP by following the instructions at "2. Installing a Custom Recovery".
So after all these steps my phone would have no limitations and it would be as unlocked as for example your Nexus 5, right?

King root app

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.

The cellular network won't start after root.

Hello guys, i have an oneplus one for a month or two and yesterday i rooted it using Kingroot *i haven't unlocked the bootloader or something like this, just pressed root and waited* , i have busybox , lucky patcher things like this nothing special. Since then my cellular network won't start. Is the only solution to unroot or even maybe reset the phone to the factory settings? I would preffer not to.

Kachada said:
Hello guys, i have an oneplus one for a month or two and yesterday i rooted it using Kingroot *i haven't unlocked the bootloader or something like this, just pressed root and waited* , i have busybox , lucky patcher things like this nothing special. Since then my cellular network won't start. Is the only solution to unroot or even maybe reset the phone to the factory settings? I would preffer not to.
Click to expand...
Click to collapse
root does not affect network generally .check apn settings and
unlocking bootloader does not void warranty and do not use one click root if not urgently needed

#sychrome# said:
root does not affect network generally .check apn settings and
for bootloader does not void warranty using cheese app
Click to expand...
Click to collapse
I spoke with a pro from my network provider and he made do some steps and it didn't help me, he said to me to check the sim and the sim works perfect on a non rooted android. So i guess its from the root.
Edit: he asked me if i re-softed my phone and told me to do a factory reboot if the sim is good.

Kachada said:
I spoke with a pro from my network provider and he made do some steps and it didn't help me, he said to me to check the sim and the sim works perfect on a non rooted android. So i guess its from the root.
Edit: he asked me if i re-softed my phone and told me to do a factory reboot if the sim is good.
Click to expand...
Click to collapse
reset data is setback try using custom recovery for new modems or new ROM and use titanium backup for safety it would not help in future if it is because of root.

#sychrome# said:
reset data is setback try using custom recovery for new modems or new ROM and use titanium backup for safety it would not help in future if it is because of root.
Click to expand...
Click to collapse
I don't want to change my cyanogen rom, it's great, i'll unroot it and maybe even reset it. I need the data more than the root.
Thanks!

Kachada said:
I don't want to change my cyanogen rom, it's great, i'll unroot it and maybe even reset it. I need the data more than the root.
Thanks!
Click to expand...
Click to collapse
Your best bet is to unlock bootloader, wipe system and reflash your ROM (with custom recovery) , there are COS signed flashable zips in General Section. Unlocking bootloader if you've never done it before wipes the phone so backup your data to a PC and keep it unlocked, it doesn't void your warranty and it makes troubleshooting issues much easier. Factory reset of the phone WILL NOT remove root.
Sent from my A0001 using Tapatalk

Well i already unrooted it and deleted everything.I'm afraid to unlock the bootloader because i have never done something like this, my biggest experience with androids software is to root them with android apps . Would you recommend me to re-soft it to cm 13 official build or to factory reset it? I'll look for a tutorial for the bootloader and do my best.
Oh, and by the way, if i clear it unlock the bootloader etc and i can't fix the problem what should i do?
I'm a newbie so probably what i'm asking is stupid, but isn't there any chance that the bootloader is unlocked? I can enter it idk..

Check you APN settings , erase them and rewrite them. Root does not affect network. And i don't see how you would be able to switch ROMs if you don't unlock your bootloader...

thats why i said that i will unlock the bootloader. and i did the apn checking with a pro from the orange *my provider* and nothing, he even changed my settings from their system. It has too be from the root , i used the cellular to download the apps for the root, then rooted it rebooted and no more cellular.

Oh and i have another reason to think its from the root because after i rooted the phone some apps started to fall down. Apex launcher for example.

Renosh said:
Your best bet is to unlock bootloader, wipe system and reflash your ROM (with custom recovery) , there
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
u can use bootloader unlock without data loss just search here for <zip file> at xda 1+1

#sychrome# said:
u can use bootloader unlock without data loss just search here for <zip file> at xda 1+1
Click to expand...
Click to collapse
I unlocked bootloader when I bought the phone so its not relevant to me. It's a one time operation
Sent from my A0001 using Tapatalk

Renosh said:
I unlocked bootloader when I bought the phone so its not relevant to me. It's a one time operation
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
same here but it would help others out
and i thinks that 1clickroot ripped his phone and services to this state.
moreover when <theguy> u use custom recovery do not modify system partition if u want ota
a q to <expert> is he able to flash systemless root without modifying system partition?

i tried to flash cm13 from twrp and it gave me error 7 , so ya i'm resetting it to the factory settings.

Kachada said:
i tried to flash cm13 from twrp and it gave me error 7 , so ya i'm resetting it to the factory settings.
Click to expand...
Click to collapse
So you've been on CM13 and you're flashing kingroot? #facepalm
Sent from my A0001 using Tapatalk

No, I used kingroot on 12.1 yogd7, I unrooted it and tried to flash it to 13. I'll resoft it to the stock that's my only option. Does the resoft to the stock *with a PC* void my warranty?

Kachada said:
No, I used kingroot on 12.1 yogd7, I unrooted it and tried to flash it to 13. I'll resoft it to the stock that's my only option. Does the resoft to the stock *with a PC* void my warranty?
Click to expand...
Click to collapse
Seriously go do some major reading cause you seem to know nothing and despite having issues with your phone since recently have made zero effort to use the stickies and guides in General section as well as this section where you posted this question. The information you need to learn is all over. Flashing the factory image needs an unlocked bootloader last I checked (might be wrong) and you have to do it via fastboot. There are stickies for OPO you just have to click and read or even go to YouTube lots of people have provided step by step guides.
It will not void your warranty, neither will unlocking your bootloader void your warranty on this phone.
Sent from my A0001 using Tapatalk

First you have to unlock your bootloader
Then flash firmware , now you can get your network working, if you want flash twrp recovery and root with SuperSU. Or just flash twrp recovery and flash cm13 ROM.
DON'T USE KINGROOT LIKE ONE CLICK ROOTS , AS THEY WERE WORKING UPTO KITKAT ONLY. SINCE LOLLIPOP YOU HAVE TO UNLOCK BOOT LOADER AND FLASH RECOVERY AND SUPERSU FOR ROOT.READ WHATEVER YOU NEED IN OPO XDA FORUM . IF YOU DON'T WANT TO LOSS YOUR DATA COPY YOUR INTERNAL STORAGE TO PC AND BACKUP CONTACTS ETC TO YOUR EMAIL ID, THEN YOU WILL NEVER LOSS ANYTHING. ME TOO AFRAID OF ROOTING BUT I ROOTED 6 DEVICES IN PAST 8 MONTHS , NEVER LOOSE MY DATA EVERYTHING. STICK WITH XDA AND.....
WELCOME TO THE REAL WORLD.

OK guys, thanks.

I have solved the problem with manudroid19's toolkit, thanks for your help guys.
Off-topic: Do you know what is the error 2 on twrp? i didn't find it on google, i get it when i try to flash gapps on cm13.*i try to do this because not even 1 google apps work and i gave them all the permissions.I deleted cache data etc,rebooted a few times*

Don't Re-Lock Your Bootloader

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 .