Related
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
That's always a risk. Read playstore comments before installing anything.
Has nothing to do with being rooted or not...or boot loader state.
Sent from my Moto X cellular telephone...
Cozume said:
Does it present any security issues to unlock a bootloader without rooting? I don't mean if you lose your phone, I mean is there a security issue with any apps you install?
Click to expand...
Click to collapse
You could have asked at AC and I would answer it over there.
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified. I can flash custom recovery to your phone. Custom recovery give full root access to the phone. It is then easily possible to copy all your data from the phone and also disable the lock for your phone. Although if you encrypt your phone, then custom recovery will require the password to give access to the /data partition, which is where all the user datas are. I guess if someone is determine enough, then they can make an image copy of your phone and try to decrypt it.
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader. However, if the phone brick then you can't get back your data in the phone.
eksasol said:
Unlocking bootloader and/or running custom recovery is a big risk. When you unlocked bootloader, all the partitions in your phone can be accessed and modified.
Click to expand...
Click to collapse
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
eksasol said:
If you want to keep your data safe, disable USB Debugging (because exploits can be used with ADB to gain access to the phone), use stock recovery and lock bootloader.
Click to expand...
Click to collapse
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Cozume said:
but can an app do this? And if so, what permissions would the app need to do this. Also, I am not talking about flashing a custom recovery; just an unlocked bootloader.
Click to expand...
Click to collapse
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system. Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
but can an app do harm to your phone if you have USB debugging enabled? I know a person who finds your phone can. I am asking about apps.
Click to expand...
Click to collapse
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
If you have an older Android phone, you don't need to do anything except to enable USB Debugging and run a program to install root. But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection. But KitKat is much safer now.
You don't need root to install malware and virus to your phone. Just download an infected app or use unreliable app stores like Aptoide. Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Point I'm trying to make is, if the phone have unlocked bootloader, or even locked bootloader with custom recovery, and someone else have a hold of it, then all bets are off.
eksasol said:
If the phone isn't root, then probably not, unless there is some security holes it can exploit. With root it is possible to modify the whole system.
Click to expand...
Click to collapse
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
eksasol said:
Motorola and HTC have an extra layer to prevent simple root to modify the system partition, but as you can see, just visit dev section if you want to remove it.
Click to expand...
Click to collapse
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
eksasol said:
It is possible for apps to get access to sensitive data and change system settings with USB Debugging enabled. Helium required it turned on to make backup of your contacts, sms and apps data for example.
Click to expand...
Click to collapse
good to know!
eksasol said:
But we're trusting apps like SuperUser and SuperSU to control apps access to root, so that's a layer of protection.
Click to expand...
Click to collapse
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
eksasol said:
But KitKat is much safer now.
Click to expand...
Click to collapse
why is this?
eksasol said:
Also if you have the option "Unknown sources" enabled, which almost all of us do, the app can utilize it to automatically install other apps in the background.
Click to expand...
Click to collapse
thanks, Amazon app store required that to be enabled to load apps from their app store.
Cozume said:
great, that is what I want to know. I knew a human being in possession of your phone could do more damage if it were unlocked, which is why I got rid of the bootloader unlocked warning message.
Click to expand...
Click to collapse
BTW - do you know if flashing the original kit kat boot logo to replace the bootloader warning message presents a problem for accepting the OTA update to 4.4.2?
Ok so then on my Moto X, since flashing a new logo doesn't even require root, it shouldn't have affected any system files and then it would be safe to take the OTA after removing the bootloader unlocked warning?
Click to expand...
Click to collapse
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA.
ok, that is how I understand it. Unless I give the app access to root through SuperSU, it can't.
Click to expand...
Click to collapse
Yes. The actual component of root isn't the SuperSU app, but a 'su' binary. Without the SuperSU app, anything can have full fledged root access. You need SuperSU to control that access.
why is this?
Click to expand...
Click to collapse
For many reason, I'm not a developer so I can only talk about what I know and seen from a user perspective. It used to be that you can flash an exploited update.zip to modify the stock recovery of Android, in order to make it ignore the package signatures, so the recovery could flash any package without the correct signature. Now there are no such exploits for latest stock recovery. With USB Debugging enabled in Android 4.3 or newer, it would not even allow access when connected to a PC unless you accept to trust that PC in a pop up dialog in the phone, I'm not sure if it's mean the phone is totally invulnerable to exploits (like memory overflow), you'll have to ask someone smarter. Also apps like Framaroot that I just linked won't work anymore.
eksasol said:
That depend on the checking that the dev put in the OTA package. On the Nexus device, if you are missing any original system APK, modify the radio partition, modify GPS setting file, or modify the build.prop, etc, the OTA will fail. So I assume the same with Moto X OTA. The safest bet is to make sure all the partition are original first (except the /data partition where your data resides) before receiving an OTA. My guess is if you tried it with modified logo it will either fail or overwrite it.
Click to expand...
Click to collapse
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Cozume said:
OK, I think I am going to unroot and flash back to stock just to be sure.
Thanks again! I would hit the thanks button but I used up all my thanks today and it won't let me.
Click to expand...
Click to collapse
You already gave me enough thanks at AC.
eksasol said:
You already gave me enough thanks at AC.
Click to expand...
Click to collapse
what is your user name there?
Cozume said:
what is your user name there?
Click to expand...
Click to collapse
someguy
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Sent from my Moto X cellular telephone...
eksasol said:
someguy
Click to expand...
Click to collapse
ok great!
kj2112 said:
Why so paranoid? Have you read any posts on xda of such things....I haven't.
If you are sideloading apps the risk increases for sure. But apps on the play store would have tonnes of comments about it if the app was screwing up the system.
Click to expand...
Click to collapse
I am just trying to understand how all of this works.
Okay one thing why are you trying to unlock the bootloader without rooting?? Or did I read everything wrong? And yes unlocking the bootloader allows you to write to every partition of the phone. Except when HTC and you're s-on you have to manually flash the boot.img via fastboot. But with moto. There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty. Three it can disable functions on your phone like features, camera options I think and yeah etc. But if you follow instructions you won't have any problems ever rooting or shouldn't if you semi have a brain and know how to follow instructions if not well you can somewhat brick :$ I don't mess with moto much but I have. Sorry this thread was in my latest and scrolling through xda. Lol. You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
edit: link: http://forum.xda-developers.com/showthread.php?t=2575586&page=2
pball52998 said:
Okay one thing why are you trying to unlock the bootloader without rooting??
Click to expand...
Click to collapse
I rooted but a friend of mine is unlocked but not rooted. She wanted to be unlocked because it wipes your device so wanted to do it before she got the phone all set up. She is afraid of rooting. Anyhow, maybe she shouldn't have unlocked but she did.
pball52998 said:
There is no point in unlocking the bootloader if you're not doing anything. Two it voids your warranty.
Click to expand...
Click to collapse
She has the dev ed so it doesn't void her warranty. And she may want to Wifi tether in the future so I told her she needs to unlock and root for that so get the dev ed. She did and unlocked but is afraid to go any further.
pball52998 said:
You can unlock you're phone straight from the moto website. But if you're not rooting. Eh no point.
Click to expand...
Click to collapse
It increases the phone's resale value to unlock it.
eksasol said:
I just read this thread, particularly page 2 why we can't relock the Motorola bootloader (yet it seems), unlike Nexus devices, I think it's really bad for security.
Click to expand...
Click to collapse
I thought I saw a thread where someone could relock the Moto X bootloader.
And what about this?
Re-Lock Your Bootloader
It should just be a command like fastboot_oem_lock or something but idk. And two if she has the dev edition. Root that thing!!! XD that's what it's for!! Just install twrp via goo manager. Wipe factory reset all that good stuff. After making a back up. Notice after backing up. Then flashing rom and gapps In that order. I mean its a lot easier than htc rezound or htc one, htc in general and such lol.
Sent from my crappy apple iPad.....
pball52998 said:
Wipe factory reset all that good stuff. After making a back up.
Click to expand...
Click to collapse
well, I didn't wipe and do a factory reset when I rooted so I guess I did it wrong, lol! That is what she is afraid of - not doing it right and messing up her phone.
And I don't have a backup, but do I really need one if I can flash the factory images?
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.
goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip
I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.
goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)
Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.
I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).
Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
There is a way, I believe, by running TWRP on your PC and flashing SuperSU from your PC. However, it's not a recommended method as you will have no way of backing up. Also, if you get caught in a bootloop, you won't be able to recover without a custom recovery.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
and you don't have to "hack" a nexus as well, as google provided an easy way to unlock your bootloader and to obtain root. if you just got your nexus a few days ago, just unlock the bootloader and root it. loosing a few days of information is more than worth it for root. don't waste your time worrying over a few days of data.
Can be done but not recommended.
adb backup/restore can save a little bit of information for you, but I wouldn't go in expecting it to save everything
Sent from my Nexus 6
What did you set up? You can back up your messages, and your apps will re-download. Your photos are already syncing to Google. If it's not rooted, I can't imagine you've done that much customization.
Lesson learned: unlock should ALWAYS be the very first step you do on a new phone.
arcooke said:
I just got my N6 a few days ago, and JUST got everything all set up how I like. I went to go root it, and the method mentioned in the "All-In-One" stickied thread requires you to unlock the bootloader, which says it will factory reset the device.
I don't want to factory reset at this point, I just want to root it. I've never had to wipe a phone or unlock a bootloader to root a phone before, so this is new to me.
Thanks
Click to expand...
Click to collapse
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
danr93 said:
if you download kingroot from the internet and install it onto your phone through unknown sources. it says your not supported but just click start root anyway. and hey presto your rooted. ive done this on my nexus 6 and its worked and hasnt knackered the phone and i know a couple of other people whove done the same
the only thing i havnet worked out how to do is take the king userr off. once your finished rooting, in order to sustain root that app becomes a permanent addittion to the phone. ive deleted it before and lost root. but just reinstall and follow the steps again and you gain root again
to check root download root checker form the app market
Click to expand...
Click to collapse
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
danarama said:
Yes we're aware but we do recommend against these one-click methods usually. Rooted users cannot accept OTA updates, so the only way to update is with an unlocked bootloader unless you're going to have a custom recovery (also highly recommended) so you can flash flashable zips.
Also you MUST go into settings and enable the "Allow OEM unlock" in developer options, because If you break your OS with root, which is easily done - you're going to become stuck as you can't unlock the bootloader. Not too bad if you have TWRP recovery installed, but then that becomes a single point of failure.
Click to expand...
Click to collapse
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
danr93 said:
ok thats fair enough i didnt realise it was so risky. i downloaded twrp straight after this method worked for me and got everything backed up
Click to expand...
Click to collapse
Good stuff. Once rooted, Flashify is a great tool to flash TWRP. With the nexus 5, you could unlock the bootloader with an app that didnt wipe everything, which was great, but Nexus 6 doesn't allow that, but always do go to settings > developer options > OEM Unlock (Set to enable). Without this set, you cannot unlock the bootloader from fastboot. Also, side note, developer options doesn't show up until you go into Settings > About phone then tap "Build number" several times to make the option visible. Think its 7 times.
It's interesting saying that you need kingroot to remain on the device. Thats a bit of a pain. Does it install SuperSU or not? If not, might be interesting to see what happens if you install the SuperSU app from Play - whether it allows it to be removed then.
My preferred method however is definitely unlock the BL, fastboot flash TWRP, From TWRP flash SuperSU zip (or rooted ROM).
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
arcooke said:
For the record, I did end up factory resetting to do it the right way.
Is this easy to unroot if a new OTA update comes out?
Click to expand...
Click to collapse
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
danarama said:
Yes and no. To "unroot" you have to fastboot flash system.img and boot.img, which if the factory image is available for the version your OTA will raise you to, you're done. If there is no factory image for that new version, you must flash the system and boot(and recovery) of the expected version, then OTA. Note, recovery version isn't checked. Only system and boot. Just that recovery must be stock for OTA to flash.
To be honest, easiest way is to wait for a rooted flashable zip to be made available and flash via recovery
Click to expand...
Click to collapse
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
arcooke said:
Geez. I thought the "pure google experience" would be much less of a headache. lol. Rooting/updating/etc was so much easier on my old Verizon phones.. one-click-root, one-click-unroot, easy updates, never had to factory reset or flash roms to do anything.
I only rooted for AdAway, starting to wonder if that was a good idea or not.
Click to expand...
Click to collapse
That's lollipop for you. It changed everything.
It's still really simple.
Good to know. Thanks for the info!
Ive uploaded a fully working root method of kingoroot that roots the nexus 5 on 5.1.1 LMY48B firmware
I have used it myself with uk stock nexus 5 and all works just thought i would upload so other people can benefit from this instead of using a pc enjoy
anyone tested this yet? i am to scared to try xD
thankyoumr said:
anyone tested this yet? i am to scared to try xD
Click to expand...
Click to collapse
working fine.. tested by me
Yes, this can also root from COMPLETE stock without the need of a computer of any kind. May want to add that to thread title if possible to let others know it can be used to root LMY48B(At Least) without the need of a computer to unlock bootloader first and without the need of a custom recovery first. Just install Kingroot then use KingUser(I Believe That Is The Super User App It Installs, Do NOT Install Another SuperUser App Yet Until After Custom Recovery Installed) and use KingUser to allow custom recovery App permissions to install recovery then use that recovery to install SuperUser binaries properly.
Sent from my Nexus 5 using Tapatalk
Why? It's a Nexus.
fastboot oem unlock
flash supersu zip file.
GldRush98 said:
Why? It's a Nexus.
fastboot oem unlock
flash supersu zip file.
Click to expand...
Click to collapse
He just said why on the first post...lol
So you dont need a pc
Its just an easier method if you ask me and for unlocking bootloader you just need to download the nexus 5 unlock bootloader app from google play to unlock bootloader then just install twrp manager from google play and theres your root bootloader unlock and custom recovery but thats upto the user as other people do it there way
It's remarkable what I'm willing to download and install from XDA sometimes.
Anyway, it certainly rooted my device without needing to hook it up to a PC. Threw two "this is bypassing android security" messages. Hope it didn't do anything else :/
---------- Post added at 09:57 PM ---------- Previous post was at 09:37 PM ----------
This also leaves you with an app called Kinguser, which is used to grant root permission to other apps, which can't be removed.
I think I'll feel better if I wipe and start over...
---------- Post added at 09:57 PM ---------- Previous post was at 09:57 PM ----------
This also leaves you with an app called Kinguser, which is used to grant root permission to other apps, which can't be removed.
I think I'll feel better if I wipe and start over...
All you do is use KingUser to grant permission to TWRP Manager to install TWRP and then use SuperSU to install SU through recovery THEN you can easily use SuperSU to grant permissions to any app that'll allow you to remove KingUser. That way you always have an app that can grant SU at all times without going ANY time at all without a SuoerUser app
EPayne123 said:
All you do is use KingUser to grant permission to TWRP Manager to install TWRP and then use SuperSU to install SU through recovery THEN you can easily use SuperSU to grant permissions to any app that'll allow you to remove KingUser. That way you always have an app that can grant SU at all times without going ANY time at all without a SuoerUser app
Click to expand...
Click to collapse
Tried that but SuperSU kept failing to install. Ended up just wiping and going from scratch. The whole Kingroot sending data home to a server just didn't sit well with me. I know they've addressed that they do it to keep track of success rates and don't collect any personal data.
rbrenart said:
Tried that but SuperSU kept failing to install. Ended up just wiping and going from scratch. The whole Kingroot sending data home to a server just didn't sit well with me. I know they've addressed that they do it to keep track of success rates and don't collect any personal data.
Click to expand...
Click to collapse
Failed to install returning SuperSU?
Will this wipe all data the way unlocking the bootloader does?
Sent from my Nexus 5 using Tapatalk 2
ddimple4 said:
Will this wipe all data the way unlocking the bootloader does?
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
No, wiping data only happens when you unlock bootloader through the bootloader. . . not through the OS. I believe only of you use the Farnborough method instead of manually doing so inside of OS
Sent from my Nexus 5
My friend has nexus 5 tmobile. Will this work? If so any additional steps?
Hi. I'm a newbie in root matter. My nexus 5 is already in LMY48b 5.1.1. Hong Kong stock ROM. So far there's only one reason I want to root it, it is to let some call recorder apps to record incoming voice clearly. So at this stage I don't need to flash any custom ROM. I dug for a certain time of course I can find many teaching how to root, but most of them look like it involves many procedures, many terms or apps, unlock bootloader, android SDK, twrp, custom recovery, etc... it makes me so scared even to give it a try. Until I saw this thread and I think the kingroot app probably the simplest one for my case! In fact I can get it done with a Chinese root way, it's also very simple but I also heard that most likely there's spyware inside so I leave it.
So what I want to make sure is my thought above is it correct? I try not to annoy you guys, any answer simply either yes or no is appreciated. Of course if you guys want to tell me more it is most welcome.
我從使用 Tapatalk 的 SM-T700 發送
lookgod88 said:
Hi. I'm a newbie in root matter. My nexus 5 is already in LMY48b 5.1.1. Hong Kong stock ROM. So far there's only one reason I want to root it, it is to let some call recorder apps to record incoming voice clearly. So at this stage I don't need to flash any custom ROM. I dug for a certain time of course I can find many teaching how to root, but most of them look like it involves many procedures, many terms or apps, unlock bootloader, android SDK, twrp, custom recovery, etc... it makes me so scared even to give it a try. Until I saw this thread and I think the kingroot app probably the simplest one for my case! In fact I can get it done with a Chinese root way, it's also very simple but I also heard that most likely there's spyware inside so I leave it.
So what I want to make sure is my thought above is it correct? I try not to annoy you guys, any answer simply either yes or no is appreciated. Of course if you guys want to tell me more it is most welcome.
我從使用 Tapatalk 的 SM-T700 發送
Click to expand...
Click to collapse
may be you can try the nexus toolkit, http://www.wugfresh.com/nrt/
beware that when unlock the bootloader all data will lost (factory reset), you can use something like helium to make a backup first (for back app data)
DummyPLUG said:
may be you can try the nexus toolkit, http://www.wugfresh.com/nrt/
beware that when unlock the bootloader all data will lost (factory reset), you can use something like helium to make a backup first (for back app data)
Click to expand...
Click to collapse
Hi dummyplug, thank you for your reply and your referring. But I actually don't need to flash ROM, that's why I thought that I don't need to unlock the bootloader either. Do I?
lookgod88 said:
Hi dummyplug, thank you for your reply and your referring. But I actually don't need to flash ROM, that's why I thought that I don't need to unlock the bootloader either. Do I?
Click to expand...
Click to collapse
The reason to unlock the bootloader is because if it is locked you can't run custom recovery (not flash, just a temp boot up with custom recovery), which is need for the root process, in short, you need to unlock the boot loader before you can do anything.
something like kingroot can bypass the need of an unlocked bootloader, so you actually can use kingroot to root your nexus first, then use those bootloader unlocker from play store to unlock the bootloader, but I will stay away from those tools because I don't trust them.
the toolkit can help you to unlock the bootloader and root, and do something else.
p.s. that means you need an unlocked bootloader to root, meanwhile can keep all other things (recovery, firmware) as stock.
DummyPLUG said:
The reason to unlock the bootloader is because if it is locked you can't run custom recovery (not flash, just a temp boot up with custom recovery), which is need for the root process, in short, you need to unlock the boot loader before you can do anything.
something like kingroot can bypass the need of an unlocked bootloader, so you actually can use kingroot to root your nexus first, then use those bootloader unlocker from play store to unlock the bootloader, but I will stay away from those tools because I don't trust them.
the toolkit can help you to unlock the bootloader and root, and do something else.
Click to expand...
Click to collapse
Oh I see. Now I understand! Thank you very much. I got what I want to know.
Hey guys,
So before I go ahead an attempt to unlock my bootloader and root my phone, just wanted to clear a couple of things up first.
This is my first Huawei device, previous one was a Sony, so I'm a little unfamiliar with a few things.
1. Is unlocking the bootloader required for root? If not, could someone point me in the direction of a guide to root only?
On the Sony, as long as I had a compatible firmware, I could root without unlocking the bootloader.
2. Will I lose any DRM Keys, proprietary features (Force Touch, Themes etc) through unlocking the bootloader and/or rooting? If so, can these be restored afterwards, while retaining root?
Again, with the Sony, unlocking the bootloader would result in losing DRM Keys related to visual enhancements, and were required to be backed up (via TABackup) prior to unlocking the bootloader. These could then be restored after root, and function as normal.
3. If you do lose features, and they can't be restored while keeping root. If I flash a stock ROM back on, losing root in the process, will these features also be restored?
Thanks
djyoshii said:
Hey guys,
So before I go ahead an attempt to unlock my bootloader and root my phone, just wanted to clear a couple of things up first.
This is my first Huawei device, previous one was a Sony, so I'm a little unfamiliar with a few things.
1. Is unlocking the bootloader required for root? If not, could someone point me in the direction of a guide to root only?
On the Sony, as long as I had a compatible firmware, I could root without unlocking the bootloader.
2. Will I lose any DRM Keys, proprietary features (Force Touch, Themes etc) through unlocking the bootloader and/or rooting? If so, can these be restored afterwards, while retaining root?
Again, with the Sony, unlocking the bootloader would result in losing DRM Keys related to visual enhancements, and were required to be backed up (via TABackup) prior to unlocking the bootloader. These could then be restored after root, and function as normal.
3. If you do lose features, and they can't be restored while keeping root. If I flash a stock ROM back on, losing root in the process, will these features also be restored?
Thanks
Click to expand...
Click to collapse
1) I used the SRK Tool (http://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999) and it showed step by step on rooting. Unlocking bootloader seems to be one of the steps before rooting. Maybe you can ask somboons about it.
2) For me, unlocking the bootloader basically resets my phone. And added a warning just before the phone bootup to android (from cold state or off state) that the bootloader has been unlocked and the phone is not trusted now. Just need to restore the apps and other data through the HiSuite backups after unlocking and rooting seems to be fine. Not sure about DRM keys, and others as didn't try those out before doing bootloader unlock. But I did lost my remote set up as it was not part of the HiSuite's data backup.
3) Do a backup with HiSuite should be able to help you. Just need to identify in the HiSuite that the apps and their data is being backed up.
prismfire said:
1) I used the SRK Tool (http://forum.xda-developers.com/p9-plus/development/tool-srk-tool-huawei-bootloader-root-t3405999) and it showed step by step on rooting. Unlocking bootloader seems to be one of the steps before rooting. Maybe you can ask somboons about it.
Click to expand...
Click to collapse
Thanks mate, I did have a look at that thread as well, and another (less detailed) post. Was just wanting to confirm if there was any other method without need for bootloader unlocking. Figure the less things to modify, the less chance of something going wrong, which has worked well for me so far.
prismfire said:
2) For me, unlocking the bootloader basically resets my phone. And added a warning just before the phone bootup to android (from cold state or off state) that the bootloader has been unlocked and the phone is not trusted now. Just need to restore the apps and other data through the HiSuite backups after unlocking and rooting seems to be fine. Not sure about DRM keys, and others as didn't try those out before doing bootloader unlock. But I did lost my remote set up as it was not part of the HiSuite's data backup.
Click to expand...
Click to collapse
Any way to remove that message while retaining root? Sounds similar to the 'yellow triangle' back when I had an S2, but that was able to be removed, is this the same?
Not too worried about backing up apps & data at the moment, I haven't fully set up my phone as I realised it would most likely be lost upon rooting. But thanks for the heads up!
prismfire said:
3) Do a backup with HiSuite should be able to help you. Just need to identify in the HiSuite that the apps and their data is being backed up.
Click to expand...
Click to collapse
Sorry I was more thinking along the lines of, if any P9+ exclusive features were to be lost during root, could they easily be restored simply by flashing a stock ROM again? Apps & app data seem to be easy enough to restore via HiSuite/Titanium etc
djyoshii said:
Thanks mate, I did have a look at that thread as well, and another (less detailed) post. Was just wanting to confirm if there was any other method without need for bootloader unlocking. Figure the less things to modify, the less chance of something going wrong, which has worked well for me so far.
Any way to remove that message while retaining root? Sounds similar to the 'yellow triangle' back when I had an S2, but that was able to be removed, is this the same?
Not too worried about backing up apps & data at the moment, I haven't fully set up my phone as I realised it would most likely be lost upon rooting. But thanks for the heads up!
Sorry I was more thinking along the lines of, if any P9+ exclusive features were to be lost during root, could they easily be restored simply by flashing a stock ROM again? Apps & app data seem to be easy enough to restore via HiSuite/Titanium etc
Click to expand...
Click to collapse
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Thanks guys
prismfire said:
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Click to expand...
Click to collapse
I read ur conversation and I have been wondering if it's safe so thank you. But I still have 1 question "if I change my oem can I still use my 2 sims"?
prismfire said:
The orange colored message i read from somewhere that it's Android security implementation standard or something. There's red message also which renders the whole phone can not boot in unless being reset.
In terms of the exclusive apps, not that I know of. Checked with my friend who kept her device as it is, without all the unlock and rooting, and compare with my device which went through and upgrade, unlock and a rooting process - no missing apps noticed.
Click to expand...
Click to collapse
So i've successfully rooted the phone, and yeah I get that 'your device has been unlocked and isn't safe' message on boot. It's not too much of a bother, besides being unsightly, but I don't really reboot my phone too often anyway.
I haven't noticed anything missing either, a few minor bugs have started to appear, but that might have to do with Xposed (I would guess).
Thanks for the advice & help!
Abdo2 said:
I read ur conversation and I have been wondering if it's safe so thank you. But I still have 1 question "if I change my oem can I still use my 2 sims"?
Click to expand...
Click to collapse
Dear Abdo2,
I'm not knowledgeable about the term oem here.
But if it is an issue of dual sim usage, I presume it's built into the ROM? What I know is all P9+ are hybrid dual sim, so it should be part of the ROM that you have.
I'm using VIE-L29C636B170. And it have the dual sim support in-built...although I've not used it yet.
See if anyone knowledgeable to your question passing by here can answer you. If not, maybe you can try the question & answer thread. Or post as another new thread if really no one got your question.
Regards.
---------- Post added at 02:39 PM ---------- Previous post was at 02:29 PM ----------
djyoshii said:
So i've successfully rooted the phone, and yeah I get that 'your device has been unlocked and isn't safe' message on boot. It's not too much of a bother, besides being unsightly, but I don't really reboot my phone too often anyway.
I haven't noticed anything missing either, a few minor bugs have started to appear, but that might have to do with Xposed (I would guess).
Thanks for the advice & help!
Click to expand...
Click to collapse
Dear djyoshii,
Good to know.
About the security message, one of it is mentioned here:
https://source.android.com/security/verifiedboot/verified-boot.html
For minor bugs, I'm not sure what you have. I've 3 games and 1 app that behaves not like when I used my previous phone (on Android 5.0). That's around 3-5% of all the apps that I used (meaning, majority works fine). Of those some of them related to Android 6.0 issue (actually the apps not updated for the Android version well). So, for me generally I would think it's marshmallow thing.
Regards.
Hi,
long time htc user (always totally unlocked) but looking to get a p9 plus for my wife (this is the important part).
can someone give me a simple answer...
if i only root the phone (for titanium backup mainly and maybe some cosmetic mods) will i be able to unroot it and return it under warranty?
phones here in Dubai are all unbranded so no problems there.
I have no need to unlock bootloader (yet )
gazzacbr said:
Hi,
long time htc user (always totally unlocked) but looking to get a p9 plus for my wife (this is the important part).
can someone give me a simple answer...
if i only root the phone (for titanium backup mainly and maybe some cosmetic mods) will i be able to unroot it and return it under warranty?
phones here in Dubai are all unbranded so no problems there.
I have no need to unlock bootloader (yet )
Click to expand...
Click to collapse
Dear gazzacbr,
From what I tried (been a while since I last did this), one will have to unlock the bootloader first before rooting. Apparently rooting is the last step of the whole process (if you are using the SRK tools). Now, to go back to the status of unrooted, I just use the superSU's total unroot option to unroot. And to go further back to bootloader, there is an option within SRK tool but my last attempt failed to relock the bootloader back. Didn't spend so much time to play around with the unlocking the bootloader after that. So, I just use as is - unlocked bootloader with no root.
One thing you need to note, for titanium backup, I end up just using their own desktop application called HiSuite. It does backup app and app data for you. Not system apps' data though. For theme customisation, MIUI do have a friendly Themer app that you can use to change the look. The corresponding theme files (*.hwt) are zipped, so you can always use 7zip to open and edit the assets inside to the one that you want.
Ok, thanks for the good info @prismfire. As long as it could be rooted sometime later then thats fine. Will pick up one this weekend.
Am going to be jealous though as I guess it's a step up from my 'old' M8
Sent from my HTC One_M8 dual sim using XDA-Developers mobile app